From: Michael Poole <poole@troilus.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100/usb interrupts stop with 2.4.x kernels?
Date: 10 May 2001 23:35:43 -0400 [thread overview]
Message-ID: <m34rush81c.fsf@troilus.org> (raw)
In-Reply-To: <E14y9Mt-0002GH-00@the-village.bc.nu>
In-Reply-To: <E14y9Mt-0002GH-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > What seems to happen is that the kernel stops seeing interrupts on the
> > IRQ shared by eth0 (my outside interface) and usb-uhci. I can still
> > ssh in on eth1, and when I do, syslog contains things like "eth0:
> > Interrupt timed out" and usb-uhci griping about devices that failed to
> > accept new endpoints.
>
> Do you see this if you run a -ac kernel or apply the APIC 440BX patch ?
I haven't tried either, but I'm about to reboot into 2.4.4-ac4 to see
if it helps. If it still happens, I'll get more of the syslog output
and try to figure out what got wedged.
-- Michael
next prev parent reply other threads:[~2001-05-11 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 0:17 eepro100/usb interrupts stop with 2.4.x kernels? Michael Poole
2001-05-11 9:37 ` Alan Cox
2001-05-11 3:35 ` Michael Poole [this message]
2001-05-12 22:42 ` Kevin Buhr
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=m34rush81c.fsf@troilus.org \
--to=poole@troilus.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox