All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Poole <poole@troilus.org>
To: linux-kernel@vger.kernel.org
Subject: eepro100/usb interrupts stop with 2.4.x kernels?
Date: 10 May 2001 20:17:49 -0400	[thread overview]
Message-ID: <m3wv7od9hu.fsf@troilus.org> (raw)

Since about 2.4.2, I have been seeing intermittent hangs on my system;
usually once or twice a week, but once just 10 minutes after rebooting.

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.

I'm not sure if for some reason my chipset stopped passing these
interrupts on to the kernel, or if the kernel got into some funny
state and stopped accepting those interrupts.  Any hints on where I
should look?

>From /proc/interrupts now:
           CPU0       CPU1       
  0:     243741     233914    IO-APIC-edge  timer
  1:          4          0    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  8:          0          0    IO-APIC-edge  rtc
 10:          0          0   IO-APIC-level  EMU10K1
 11:      18775      17937   IO-APIC-level  usb-uhci, eth0
 12:       1221       1236   IO-APIC-level  eth1
 14:      84039      68162    IO-APIC-edge  ide0
 15:         18         18   IO-APIC-level  BusLogic BT-950
NMI:          0          0 
LOC:     477548     477547 
ERR:          0

-- Michael

             reply	other threads:[~2001-05-11  0:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11  0:17 Michael Poole [this message]
2001-05-11  9:37 ` eepro100/usb interrupts stop with 2.4.x kernels? Alan Cox
2001-05-11  3:35   ` Michael Poole
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=m3wv7od9hu.fsf@troilus.org \
    --to=poole@troilus.org \
    --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.