linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: David Brownell <david-b@pacbell.net>
Cc: Greg KH <greg@kroah.com>,
	arjanv@redhat.com, Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [More Info] Re: 2.6.0test 1 fails on eth0 up (arjanv RPM's - all needed rpms installed)
Date: 31 Jul 2003 02:42:57 -0400	[thread overview]
Message-ID: <1059633777.4720.7.camel@aurora.localdomain> (raw)
In-Reply-To: <3F21C5FA.5020507@pacbell.net>

On Fri, 2003-07-25 at 20:06, David Brownell wrote:

> See if this patch resolves it.
> 
> The patch adds an explicit reset to HCD initialization, and then makes
> EHCI use it.  (OHCI could do so even more easily ... but nobody's reported
> firmware acting that type of strange with OHCI.)   It should prevent IRQs
> being enabled while the HC is still in an indeterminate state.
> 
> This also fixes a missing local_irq_restore() that was generating some
> annoying might_sleep() messages, and a missing readb() that affects some
> ARM (and other) PCI systems.
> 
> - Dave

Applied it against test2.  I think the problem is indeed ACPI handling
PCI irqs.  This is an nVidia nForce2 board, I should check to see if the
patch someone posted fixes this (Did it get folded into test2?).

Anyway, the first oops only happens if I have the mouse plugged in as
USB (Intellimouse USB... I usually use the dumb little PS/2 adapter). 
The second happens now, but didn't before.  It is 1394 related. 
Interrupts are at 100k+ on both usb and 1394 ohci almost instantly with
ACPI on.

irq 11: nobody cared!
Call Trace:
[<c010c12a>] __report_bad_irq+0x2a/0x90
[<c010c21c>] note_interrupt+0x6c/0xb0
[<c010c42d>] do_IRQ+0xed/0x110
[<c010a9f8>] common_interrupt+0x18/0x20
[<c011f780>] do_softirq+0x40/0xa0
[<c010c414>] do_IRQ+0xd4/0x110
[<c010a9f8>] common_interrupt+0x18/0x20
[<c010c84e>] setup_irq+0x6e/0xb0
[<e087f350>] usb_hcd_irq+0x0/0x60 [usbcore]
[<c010c4d0>] request_irq+0x80/0xd0
[<e08824e0>] usb_hcd_pci_probe+0x200/0x4a0 [usbcore]
[<e087f350>] usb_hcd_irq+0x0/0x60
[<c01aa1f2>] pci_device_probe_static+0x52/0x70
[<c01aa30c>] __pci_device_probe+0x3c/0x50
[<c01aa34f>] pci_device_probe+0x2f/0x50
[<c01eb695>] bus_match+0x45/0x80
[<c01eb7ac>] driver_attach+0x5c/0x60
[<c01eba97>] bus_add_driver+0xa7/0xc0
[<c01ebf1f>] driver_register+0x2f/0x40
[<c01aa600>] pci_register_driver+0x70/0xa0
[<e0824021>] init+0x21/0x4f [ehci_hcd]
[<c0130afb>] sys_init_module+0x10b/0x200
[<c010a839>] sysenter_past_esp+0x52/0x71

handlers:
[<e087f350>] (usb_hcd_irq+0x0/0x60 [usbcore])
Disabling IRQ #11
ehci_hcd 0000:00:02.2: irq 11, pci mem e0815000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1


irq 4: nobody cared!
Call Trace:
[<c010c12a>] __report_bad_irq+0x2a/0x90
[<c010c21c>] note_interrupt+0x6c/0xb0
[<c010c42d>] do_IRQ+0xed/0x110
[<c010a9f8>] common_interrupt+0x18/0x20
[<c011f780>] do_softirq+0x40/0xa0
[<c010c414>] do_IRQ+0xd4/0x110
[<c010a9f8>] common_interrupt+0x18/0x20
[<c010c84e>] setup_irq+0x6e/0xb0
[<e08536d0>] ohci_irq_handler+0x0/0x720 [ohci1394]
[<c010c4d0>] request_irq+0x80/0xd0
[<e0855603>] ohci1394_pci_probe+0x3d3/0x580 [ohci1394]
[<e08536d0>] ohci_irq_handler+0x0/0x720 [ohci1394]
[<c01aa1f2>] pci_device_probe_static+0x52/0x70
[<c01aa30c>] __pci_device_probe+0x3c/0x50
[<c01aa34f>] pci_device_probe+0x2f/0x50
[<c01eb695>] bus_match+0x45/0x80
[<c01eb7ac>] driver_attach+0x5c/0x60
[<c01eba97>] bus_add_driver+0xa7/0xc0
[<c01ebf1f>] driver_register+0x2f/0x40
[<c01aa600>] pci_register_driver+0x70/0xa0
[<e0817013>] ohci1394_init+0x13/0x3d [ohci1394]
[<c0130afb>] sys_init_module+0x10b/0x200
[<c010a839>] sysenter_past_esp+0x52/0x71

handlers:
[<e08536d0>] (ohci_irq_handler+0x0/0x720 [ohci1394])
Disabling IRQ #4

Anyway, so either it is ACPI and fixable, or I just forget pci routing
with ACPI.

Trever Adams
--
"If a revolution destroys a systematic government, but the systematic
patterns of thought that produced that government are left intact, then
those patterns will repeat themselves in the succeding government." --
Robert M. Pirsig


  reply	other threads:[~2003-07-31  6:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 18:56 Trever L. Adams
2003-07-14 19:06 ` Jeff Garzik
2003-07-14 19:15   ` Arjan van de Ven
2003-07-14 21:20     ` Trever L. Adams
2003-07-15 20:10       ` [More Info] " Trever L. Adams
2003-07-15 21:02         ` Greg KH
2003-07-15 20:55           ` jds
2003-07-15 23:15           ` David Brownell
2003-07-26  0:06           ` David Brownell
2003-07-31  6:42             ` Trever L. Adams [this message]
2003-07-31 17:15               ` David Brownell
2003-07-16 18:59 ` Zwane Mwaikambo
2003-07-17  3:11   ` Trever L. Adams
     [not found]     ` <Pine.LNX.4.53.0307170254500.32541@montezuma.mastecende.com>
2003-07-17 14:46       ` Trever L. Adams

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=1059633777.4720.7.camel@aurora.localdomain \
    --to=tadams-lists@myrealbox.com \
    --cc=arjanv@redhat.com \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [More Info] Re: 2.6.0test 1 fails on eth0 up (arjanv RPM'\''s - all needed rpms installed)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).