linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Brad Langhorst <brad@langhorst.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops with pci=biosirq in 2.4.22 (not in 2.4.18)
Date: Fri, 31 Oct 2003 18:43:56 -0800	[thread overview]
Message-ID: <20031101024356.GB3907@matchmail.com> (raw)
In-Reply-To: <1067654215.19557.412.camel@up>

On Fri, Oct 31, 2003 at 09:36:56PM -0500, Brad Langhorst wrote:
> 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.

Most likely not.

Did you get any problems with 2.4.21?

What about 2.4.23-pre?

Too much between 2.4.22 and 2.4.18 changed to use this little info to track
anything down...

  reply	other threads:[~2003-11-01  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01  2:36 oops with pci=biosirq in 2.4.22 (not in 2.4.18) Brad Langhorst
2003-11-01  2:43 ` Mike Fedyk [this message]
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=20031101024356.GB3907@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).