From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IRQ issues, (nobody cared, disabled), not USB
Date: Fri, 9 Jul 2004 07:32:57 -0800 [thread overview]
Message-ID: <20040709153257.GA2363@iarc.uaf.edu> (raw)
In-Reply-To: <20040708220522.73839ea3.akpm@osdl.org>
Andrew,
* Andrew Morton <akpm@osdl.org> [2004-Jul-08 21:05 AKDT]:
> Christopher Swingley <cswingle@iarc.uaf.edu> wrote:
> >
> > 03:27:26 kernel: irq 7: nobody cared!
> > ...
> > I've tried booting without ACPI, and I've tried an eepro100 card
> > instead of the 8139too that's causing the error above.
>
> hmm, so the eepro100 failed in the same way as the rtl8139?
Yes indeed. I had the eepro100 in there initially and after it started
dropping out, I figured I'd see if an 8139too would (I know it sounds
odd. . .) work better.
> It would be useful if you could go back to 2.6.5 for a while, so we
> can mostly-eliminate a hardware glitch.
I'm back in 2.6.5 now. Any other tests I can perform to help eliminate
the potential for a hardware problem? The timing of the failure is so
irregular that it would seem to point to a hardware flaw, but who knows.
I can no longer recall when this first started happening, but there's a
good chance this happened when I was running 2.6.5 too. I track the
vanilla releases pretty closely.
Thanks,
Chris
--
Christopher S. Swingley email: cswingle@iarc.uaf.edu (work)
Intl. Arctic Research Center cswingle@gmail.com (personal)
University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle/
next prev parent reply other threads:[~2004-07-09 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 15:53 IRQ issues, (nobody cared, disabled), not USB Christopher Swingley
2004-07-09 5:05 ` Andrew Morton
2004-07-09 15:32 ` Christopher Swingley [this message]
2004-07-11 8:39 ` Ville Herva
2004-07-13 10:49 ` Ville Herva
2004-07-12 14:38 ` Christopher Swingley
[not found] <A6974D8E5F98D511BB910002A50A6647615FFACC@hdsmsx403.hd.intel.com>
2004-07-11 2:48 ` Len Brown
2004-07-12 14:43 ` Christopher Swingley
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=20040709153257.GA2363@iarc.uaf.edu \
--to=cswingle@iarc.uaf.edu \
--cc=akpm@osdl.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.