Crash with 1.3.71 on Alpha with IDE drive

Nigel Metheringham (Nigel.Metheringham@theplanet.net)
Fri, 08 Mar 1996 12:52:31 +0000


I have spent a couple of days trying to figure this one out without
success. I'm hoping someone can give me a pointer....

I'm using a DEC Alpha Noname board, 24MB RAM, Red Hat AXP 2.1
distribution.
If I use any kernel compiled with any options that I've tried
(basically minimal, and with networking), it crashes fairly late in
the boot sequence.
This crash is strongly linked to the IDE drive - A Quantum Fireball,
1039MB drive. If I use a SCSI or an alternate Quantum IDE drive (A
trailblazer 820MB) it boots OK. If I use a 1.3.69 kernel its OK.
This also happens using a kernel built by David M-T which works on
his system (with IDE).
I have rebuilt the entire system on that IDE drive to check nothing
on there was corrupted.

The Red Hat stuff uses hdparm on the IDE drives soon after INIT is
started to set maxmult to 16, if I change this line (to maxmult=8 -
the max the drive will take) it crashes at this point (still OK under
1.3.69), if I take it out altogether then behaviour doesn't change -
it crashes at the point where INIT should be running the
/etc/rc.d/rc3.d/* scripts. Since twiddling with that it now crashes
at an early stage - like at the point where the hdparm is performed -
even if the hdparm commands are restored to their original state!
(And I have power cycled, not just reset - 1.3.69 still works).

The Oops message is:-
Unable to handle kernel paging request at virtual address
fffffe000002be88
rc.sysinit(8): Oops 0
pc = [<fffffc0000331230>] ps = 0000
rp = [<fffffc00003270b8>] sp = fffffc0002787e40
r0=7 r1=fffffe0000022000 r2=fffffe000002be88 r3=27a2000
r8=1
r16=0 r17=0 r18=0 r19=0
r20=40000000000 r21=fffffc00004543a0 r22=0 r23=fffffc000041be1c
r24=fffffc0000311838 r25=277 r26=fffffc00003270b8 r27=fffffc0000331030
r28=7 r29=fffffc0000436bc0 r30=fffffc0002787e40
Code: a4210000 4841b682 40410642 <a5420000> e5400026 213fffff
454a040f 25290001 47ff041f

The pc is in free_pages, this message repeats a few 10s of times, and
then I get
free_one_pgd: bad directory entry fffffc000043a988
free_one_pgd: bad directory entry 00002800
free_one_pgd: bad directory entry fffffc0000318720
free_one_pgd: bad directory entry fffffc0000301250
free_one_pgd: bad directory entry fffffc000031544c

and similar repeating more times than you care to count....

any clues for this greatfully received....

Nigel.

-- 
[ Nigel.Metheringham@theplanet.net   - Unix Applications Engineer ]
[ *Views expressed here are personal and not supported by PLAnet* ]
[ PLAnet Online : The White House     Tel : +44 113 2345566 x 612 ]
[ Melbourne Street, Leeds LS2 7PS UK. Fax : +44 113 2345656       ]