From: Brad Langhorst <brad@langhorst.com>
To: linux-kernel@vger.kernel.org
Subject: oops with pci=biosirq in 2.4.22 (not in 2.4.18)
Date: Fri, 31 Oct 2003 21:36:56 -0500 [thread overview]
Message-ID: <1067654215.19557.412.camel@up> (raw)
Unfortunately I can't get a copy of the oops because
the screen immediately fills with hex addresses
(looks like a looping call trace)
2.6.0test9 does not suffer from this problem.
I don't have time to try more kernels and narrow the window at the
moment.
perhaps this is enough information for somebody who knows where to look.
brad
next reply other threads:[~2003-11-01 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 2:36 Brad Langhorst [this message]
2003-11-01 2:43 ` oops with pci=biosirq in 2.4.22 (not in 2.4.18) Mike Fedyk
2003-11-01 3:48 ` Brad Langhorst
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=1067654215.19557.412.camel@up \
--to=brad@langhorst.com \
--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.