From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Mike Isely <isely@pobox.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Oliver Neukum <oliver@neukum.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)]
Date: Mon, 20 Oct 2008 13:03:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0810201251490.6072@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0810201142270.12643@cnc.isely.net>
On Mon, 20 Oct 2008, Mike Isely wrote:
> On Mon, 20 Oct 2008, Justin Piszcz wrote:
>
>>
>>
>> On Mon, 20 Oct 2008, Mike Isely wrote:
>>
>>>
>>> There's already a patch coming up through v4l-dvb that should remove the
>>> need for the reset completely for the pvrusb2 driver. The reset had
>>> been there as "chicken soup" previously - it didn't hurt but its
>>> utility wasn't really that great at the time. Now that it is hurting,
>>> I just removed it.
>>>
>>> -Mike
>>>
>>
>> Should I wait for the patch coming up through v4l-dvb or test Alan's patch?
>> 2.6.27.2 has quite a few issues:
>>
>> 1. xfs is broken w/barrier (there is a patch for this)
>> 2. usb hangs (patch below)
>> 3. abit-guru (comsetic issue only, doesn't find mobo) (there is a patch for
>> this now as well)
>>
>> So I am sticking with 2.6.26.5 right now, let me know if you need me
>> to test Alan's patch to see if it fixes the issue.
>
> I'm sorry I didn't post my patch immediately in my previous response.
> It is however posted as a link in a followup, and for the record here it
> is again:
>
> http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4
>
> I have tested it, and it works as expected. I've done all I can
> according to the process there to ready it for kernel inclusion and I've
> asked in my pull request there to get this patch into the next 2.6.27.x
> stable release.
>
> The driver really didn't "need" the reset anyway, and so from where I'm
> sitting the simplest thing is just to remove it which is what my patch
> does. (I had put in that reset a long time ago when working on
> improving hardware stability. I had never positively established that
> this actually helped during initialization, but it didn't hurt either so
> I left it in place. Now that it is causing pain, it's best just to get
> it out of there.) I don't see much point in testing Alan's patch.
Ok, so the following patche are what I have applied to 2.6.27.2:
1. http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4
--
1. aw9d-max-dmi-detection.diff
2. pvrusb2-hdw.patch
3. xfs-fix-remount-rw-with-unrecognized-options.patch
Rebooting 2.6.27.2 with applied patches (all 3) and will check to make
sure everything is back to normal.
Done, after reboot with the [3] applied patches above, it has fixed all
the problems I was having.
Justin.
next prev parent reply other threads:[~2008-10-20 17:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 11:26 Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE) Justin Piszcz
2008-10-19 11:28 ` Justin Piszcz
2008-10-19 15:34 ` Oliver Neukum
2008-10-19 16:51 ` Justin Piszcz
2008-10-20 14:02 ` Alan Stern
2008-10-20 15:21 ` Justin Piszcz
2008-10-20 16:17 ` Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)] Alan Stern
2008-10-20 16:21 ` Mike Isely
2008-10-20 16:33 ` Justin Piszcz
2008-10-20 16:50 ` Mike Isely
2008-10-20 17:03 ` Justin Piszcz [this message]
2008-10-20 17:16 ` Alan Stern
2008-10-20 16:37 ` Mike Isely
2008-10-20 17:29 ` Greg KH
2008-10-20 18:01 ` Michael Krufky
2008-10-23 16:27 ` Mike Isely
2008-10-23 19:15 ` Greg KH
2008-10-23 19:54 ` Mike Isely
2008-10-23 22:04 ` Michael Krufky
2008-10-23 22:11 ` Justin Piszcz
2008-10-24 5:43 ` Mike Isely
2008-10-24 15:29 ` Michael Krufky
2008-10-24 21:30 ` Greg KH
2008-10-19 15:34 ` Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE) Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0810201251490.6072@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=isely@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®