public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Cc: Johannes Erdfelt <johannes@erdfelt.com>, Greg KH <greg@kroah.com>,
	Milton Miller <miltonm@bga.com>,
	linux-kernel@vger.kernel.org
Subject: Re: USB problem. 'irq 9: nobody cared!' (FIXED!)
Date: Tue, 30 Sep 2003 12:30:44 -0700	[thread overview]
Message-ID: <3F79D9E4.4060701@pacbell.net> (raw)
In-Reply-To: <200309301141.18595.arekm@pld-linux.org>

Arkadiusz Miskiewicz wrote:
> On Thursday 25 of September 2003 21:11, David Brownell wrote:
> 
> 
>>The problem is that nobody has ever reported back with results from
>>testing any updated patch (see attachment, the guts of this being
>>from Alan Stern).  Sort of makes trying be a moot point ... :)
> 
> So I'm the first one? ;)

Since then I got mixed reports -- not sure I trust them.


> Your patch (http://www.ussg.iu.edu/hypermail/linux/kernel/0309.3/0341.html) 
> FIXES things for me :-)

OK, that's good to hear.  There are two patches that seem
to work to various degrees.  This isn't the least conservative
fix (that'd be http://lkml.org/lkml/2003/9/29/74, returning
to that odd "reset before kicking bios off" sequence) but it's
good to know this also behaves.

- Dave



> This time I've tried 2.6.0test6 + all acpi patches from 2.6.0-mm1 (ls *acpi* 
> in akpm broken-out directory) + your patch and things work fine :)
> Note that 2.6.0+all acpi patches from 2.6.0-mm1 without your patch doesn't 
> work.
> 
> [arekm@mobarm arekm]$ cat /proc/interrupts
>            CPU0
>   0:     698946          XT-PIC  timer
>   1:       1712          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   3:       1561          XT-PIC  irda0
>   5:          4          XT-PIC  yenta
>   8:          0          XT-PIC  rtc
>   9:       2657          XT-PIC  acpi, eth0
>  10:      77708          XT-PIC  VIA686A, uhci-hcd, uhci-hcd
>  12:         18          XT-PIC  i8042
>  14:      12408          XT-PIC  ide0
>  15:         20          XT-PIC  ide1
> NMI:          0
> ERR:          0
> 
> More details about my case in lkml archives and 
> http://bugme.osdl.org/show_bug.cgi?id=905
> 
> 
>>It's OK with me if you just revert the patch that adds a uhci_reset()
>>entry, but based on what I saw with EHCI and OHCI that'll just turn
>>up a different set of problems with certain BIOS configurations (none
>>of which I have) ... which will need to be fixed by having a UHCI
>>reset sequence that works correctly from _all_ initial states.
>>
>>- Dave
> 
> 



  reply	other threads:[~2003-09-30 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 22:57 USB problem. 'irq 9: nobody cared!' Milton Miller
2003-09-25  4:23 ` Yaroslav Halchenko
2003-09-25 18:00   ` Greg KH
2003-09-25 19:11     ` David Brownell
2003-09-30  9:41       ` USB problem. 'irq 9: nobody cared!' (FIXED!) Arkadiusz Miskiewicz
2003-09-30 19:30         ` David Brownell [this message]
2003-09-26  3:14 ` USB problem. 'irq 9: nobody cared!' Yaroslav Halchenko

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=3F79D9E4.4060701@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=arekm@pld-linux.org \
    --cc=greg@kroah.com \
    --cc=johannes@erdfelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    /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