From: Thunder from the hill <thunder@ngforever.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: In kernel 2.4.0 in alloc_uhci when doing request_irq()
Date: Thu, 25 Jan 2001 14:23:18 -0700 [thread overview]
Message-ID: <3A709946.51505EF6@ngforever.de> (raw)
Hi,
I am using an usual VIA MPV3 onboard USB device (on a AMD K6-II 400
machine), and it has ever worked fine on Linux (until including
2.4.0-test10). Now I wanted to use the "retail" 2.4.0-kernel, and USB
gets stuck while booting. Last messages are:
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.251 $time 07:06:37 Jan 14 2001
usb-uhci.c: high bandwidth mode enabled
PCI: Assigned IRQ 10 for device 00:07.2
usb-uhci.c: USB UHCI at I/O 0xe400, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
That's all.
I debugged a while and noticed that the error occurs beyond
drivers/usb/usb-uhci.c in the function alloc_uhci() after start_hc (s);
when calling request_irq(), the line reads:
if (request_irq (irq, uhci_interrupt, SA_SHIRQ, MODNAME, s)) {
The called function crashes somewhere on top, as I noticed.
Is there a patch avariable, or should I do further investigation?
Thunder
---
I did a "cat /boot/vmlinuz >> /dev/audio" - and I think I heard god...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-25 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 21:23 Thunder from the hill [this message]
2001-01-25 21:36 ` In kernel 2.4.0 in alloc_uhci when doing request_irq() Johannes Erdfelt
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 17:47 Thunder from the hill
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=3A709946.51505EF6@ngforever.de \
--to=thunder@ngforever.de \
--cc=linux-kernel@vger.kernel.org \
/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.