2.4.20-rc4-ac1 SiS IDE driver troubles

2.4.20-rc4-ac1 SiS IDE driver troubles

[Murray J. Root]

P4S533 (SiS645DX chipset)
P4 2GHz
1G PC2700 RAM

After booting and initscripts I get some kind of error like a BUG() but
I can't see what it is because it scrolls off with repeated "unable to
handle kernel paging request" messages. The first error shows a stack trace
(briefly) but all the rest just show the offsets without the text.

If I choose just Generic IDE then I can boot (of course I don't get to
use ATA/133). No mouse, but since that error has been there since 2.4.20
pre8 I'm pretty sure it's not related.

There are no error messages in the logs - just a long series of <nul>
where the messages would be.

-- 
Murray J. Root
------------------------------------------------
DISCLAIMER: http://www.goldmark.org/jeff/stupid-disclaimers/
------------------------------------------------
Mandrake on irc.freenode.net:
  #mandrake & #mandrake-linux = help for newbies 
  #mdk-cooker = Mandrake Cooker 

Re: 2.4.20-rc4-ac1 SiS IDE driver troubles

[Alan Cox]

> After booting and initscripts I get some kind of error like a BUG() but
> I can't see what it is because it scrolls off with repeated "unable to
> handle kernel paging request" messages. The first error shows a stack trace
> (briefly) but all the rest just show the offsets without the text.

Stick a while(1); at the end of the stack dump code and you should get
jus tthe first oops you can read

Re: 2.4.20-rc4-ac1 SiS IDE driver troubles

[Bill Davidsen]

On Wed, 27 Nov 2002, Alan Cox wrote:

> > After booting and initscripts I get some kind of error like a BUG() but
> > I can't see what it is because it scrolls off with repeated "unable to
> > handle kernel paging request" messages. The first error shows a stack trace
> > (briefly) but all the rest just show the offsets without the text.
> 
> Stick a while(1); at the end of the stack dump code and you should get
> jus tthe first oops you can read

You may want to block interrupts as well, I've used this trick (given by
akpm) before, and sometimes whatever is wrong will generate a double panic
on interrupt shortly after the first OOPS output.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.