From: Andrew Morton <akpm@osdl.org>
To: Reuben Farrelly <reuben-lkml@reub.net>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
jgarzik@pobox.com, greg@kroah.com,
linux-usb-devel@lists.sourceforge.net, neilb@cse.unsw.edu.au,
linux-acpi@vger.kernel.org
Subject: Re: Re: 2.6.15-mm3 [USB lost interrupt bug]
Date: Fri, 20 Jan 2006 21:47:23 -0800 [thread overview]
Message-ID: <20060120214723.79111715.akpm@osdl.org> (raw)
In-Reply-To: <43D1C4E9.7030901@reub.net>
Reuben Farrelly <reuben-lkml@reub.net> wrote:
>
>
>
> On 16/01/2006 4:46 p.m., Alan Stern wrote:
> > On Mon, 16 Jan 2006, Reuben Farrelly wrote:
> >
> >>> From the information presented here, it looks like -mm1 correctly routes
> >>> the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> >>> -mm3 incorrectly routes the 1d.3 controller to IRQ 193. That would make
> >>> it an ACPI problem.
> >> Is this likely to be the same or similar issue to the IRQ 0 problem I see quite
> >> frequently on the SATA ports on later -mm releases?
> >> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)
> >
> > I doubt they are at all related. In the USB problem the resource is there
> > but ACPI is routing it wrongly. In the SATA problem the resource isn't
> > there to begin with.
> >
> > But then I know almost nothing about ACPI, so I could be wrong...
> >
> > Alan Stern
>
> Some good news. I think it's fixed in 2.6.16-rc1-mm2. In fact a whole boatload
> of problems I was having are fixed in this -mm release, including a nasty libata
> oops that seemed to have a few people scratching their heads.
OK, but probably that libata error-path bug is still in there. It's just
that you're no longer taking the error paths. And now we've lost our means
to reproduce it.
> I've now done in excess of 20 reboots with this code and haven't had either
> problem show up at all.
>
> So for now I'll keep a record of things for a bit longer, but I guess I've
> reason to be fairly confident that both this USB/IRQ problem and my ATA/IRQ
> problem are now fixed.
>
> It does make me wonder if the ACPI update in rc1-mm2 fixed it, and was actually
> the cause of most of my problems......it would be nice to know for sure.
We probably won't know. Did you ever test 2.6.16-rc1 plus 2.6.16-rc1-mm1's
acpi.patch? If that plays up we'd have confirmation.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2006-01-21 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060111042135.24faf878.akpm@osdl.org>
[not found] ` <43C5D537.7020800@reub.net>
[not found] ` <43C5D537.7020800-MwA23MxOyI4@public.gmane.org>
2006-01-12 4:33 ` 2.6.15-mm3 Andrew Morton
[not found] ` <20060111203332.50c45031.akpm-3NddpPZAyC0@public.gmane.org>
2006-01-12 4:38 ` 2.6.15-mm3 Reuben Farrelly
2006-01-12 8:54 ` 2.6.15-mm3 [USB lost interrupt bug] Reuben Farrelly
[not found] ` <43C6194C.1070107-MwA23MxOyI4@public.gmane.org>
2006-01-12 15:53 ` [linux-usb-devel] " Alan Stern
[not found] ` <Pine.LNX.4.44L0.0601121052190.5383-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2006-01-15 22:50 ` Reuben Farrelly
[not found] ` <43CAD1BB.60301-MwA23MxOyI4@public.gmane.org>
2006-01-16 3:22 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0601152212340.1929-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2006-01-16 3:28 ` Reuben Farrelly
[not found] ` <43CB12EA.3040309-MwA23MxOyI4@public.gmane.org>
2006-01-16 3:46 ` Alan Stern
2006-01-21 5:21 ` Reuben Farrelly
2006-01-21 5:47 ` Andrew Morton [this message]
2006-01-21 7:58 ` Reuben Farrelly
2006-01-21 8:32 ` [PATCH] " Jeff Garzik
2006-01-21 10:41 ` Reuben Farrelly
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=20060120214723.79111715.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=neilb@cse.unsw.edu.au \
--cc=reuben-lkml@reub.net \
--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