From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: Re: 2.6.27-rc4: 90% system time because of khubd, unable to reboot
Date: Fri, 22 Aug 2008 21:57:22 +0400 [thread overview]
Message-ID: <200808222157.29299.arvidjaar@mail.ru> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0808221333110.2230-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 2891 bytes --]
On Friday 22 August 2008, Alan Stern wrote:
> On Fri, 22 Aug 2008, Andrey Borzenkov wrote:
>
> > > > reverting 38b375d9610e2467cb793a84d17c6f65e44cdb39 fixed it
> > > >
> > >
> > > ... that is:
> > >
> > > commit 38b375d9610e2467cb793a84d17c6f65e44cdb39
> > > Author: Alan Stern <stern@rowland.harvard.edu>
> > > Date: Mon Jul 21 09:56:26 2008 -0400
> > >
> > > USB: OHCI: fix system hang caused by earlier patch
> > >
> > > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > > Tested by: Andrey Borzenkov <arvidjaar@mail.ru>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > >
> > > so it apparently used to work for you at that time. What gives?
> > >
> >
> > Well, you should not commit a fix without commiting code that has been
> > fixed first :)
>
> Actually the code to be fixed _was_ committed first -- but then it was
> reverted before the fix was accepted, so the fix was merged without it.
>
> My advice is not to worry about it. That code has been sent once again
> to Linus -- it's not merged yet but presumably it will be soon.
> Certainly before 2.6.27-rc5 appears.
>
> On the other hand, I still have to wonder how the fix could have caused
> your problem without the original patch in place. The fix itself
> should have been totally innocuous.
>
It looks even funnier. Right now I am running with commits
38b375d9610e2467cb793a84d17c6f65e44cdb39 *and*
e872154921a6b5256a3c412dd69158ac0b135176 reverted. I.e. this should be
the state which hopelessly failed in 2.6.26-rc. It seems to be doing
quite well now in 2.6.27-rc.
"git revert e872154921a6b5256a3c412dd69158ac0b135176" gives me this
one liner patch:
commit f3cf9ad86ee76077d1c6be9af7d197aa13ccdff9
Author: Andrey Borzenkov <arvidjaar@mail.ru>
Date: Fri Aug 22 21:15:26 2008 +0400
Revert "USB: don't explicitly reenable root-hub status interrupts"
This reverts commit e872154921a6b5256a3c412dd69158ac0b135176.
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 107e1d2..d30f822 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -3086,6 +3086,11 @@ static void hub_events(void)
if (!hdev->parent && !hub->busy_bits[0])
usb_enable_root_hub_irq(hdev->bus);
+ /* If this is a root hub, tell the HCD it's okay to
+ * re-enable port-change interrupts now. */
+ if (!hdev->parent && !hub->busy_bits[0])
+ usb_enable_root_hub_irq(hdev->bus);
+
loop_autopm:
/* Allow autosuspend if we're not going to run again */
if (list_empty(&hub->event_list))
Either my git tree is completely botched or most parts were already reverted
before.
So the problem seems to have cured by itself between 2.6.26 and 2.6.27?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-22 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 16:26 2.6.27-rc4: 90% system time because of khubd, unable to reboot Andrey Borzenkov
2008-08-22 16:53 ` Andrey Borzenkov
2008-08-22 17:04 ` Rafael J. Wysocki
2008-08-22 17:09 ` Andrey Borzenkov
2008-08-22 17:39 ` Alan Stern
2008-08-22 17:57 ` Andrey Borzenkov [this message]
2008-08-22 18:25 ` Alan Stern
2008-08-23 6:27 ` Andrey Borzenkov
2008-08-23 18:30 ` Alan Stern
2008-08-22 18:29 ` Rafael J. Wysocki
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=200808222157.29299.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.