* oops with pci=biosirq in 2.4.22 (not in 2.4.18)
@ 2003-11-01 2:36 Brad Langhorst
2003-11-01 2:43 ` Mike Fedyk
0 siblings, 1 reply; 3+ messages in thread
From: Brad Langhorst @ 2003-11-01 2:36 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: oops with pci=biosirq in 2.4.22 (not in 2.4.18)
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
2003-11-01 3:48 ` Brad Langhorst
0 siblings, 1 reply; 3+ messages in thread
From: Mike Fedyk @ 2003-11-01 2:43 UTC (permalink / raw)
To: Brad Langhorst; +Cc: linux-kernel
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...
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: oops with pci=biosirq in 2.4.22 (not in 2.4.18)
2003-11-01 2:43 ` Mike Fedyk
@ 2003-11-01 3:48 ` Brad Langhorst
0 siblings, 0 replies; 3+ messages in thread
From: Brad Langhorst @ 2003-11-01 3:48 UTC (permalink / raw)
To: Mike Fedyk; +Cc: linux-kernel
On Fri, 2003-10-31 at 21:43, Mike Fedyk wrote:
> On Fri, Oct 31, 2003 at 09:36:56PM -0500, Brad Langhorst wrote:
> > 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...
i feared as much - unfortunately i just don't have time to spend on this
at the moment.
I figure a weak ass bug report is better than no bug report - at least
somebody googling might be able to save some time now...
It's working in 2.6.0 so i guess 2.4 will just have to live with the
bug.
thanks for the response!
brad
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-11-01 3:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2003-11-01 3:48 ` Brad Langhorst
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).