Skip to contentSkip to conversation

oops with pci=biosirq in 2.4.22 (not in 2.4.18)

DISCUSSION Brad Langhorst 2 participants 3 messages Nov 1, 2003

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 10 lines · Brad Langhorst

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...

#2 lore raw
Quoted 6 lines · Mike Fedyk
Quoted 4 lines · Brad Langhorst

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.

Quoted 8 lines

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