Interesting, this looks like a oops in usbdevfs_put_super.  The trace
looks like:

usbdevfs_put_super
kern_mount
sys_umount
sys_oldumount
system_call

So - do you have any USB devices attached to your machine?  If so,
what are they?  Do you know what kind of usb controller is in your
machine?  You might want to try booting with "linux nousb" (first) or
"linux nousbstorage" (second, if "linux nousb" didn't work).

Cheers,

Matt

On Tue, Oct 01, 2002 at 12:04:09PM -0700, Alameida wrote:
>  I've reproduced this bug sevral times on Psyche (infact its all I can do)
> No matter what instal type I try.. custom, in X, text, workstation, etc. I get a 
>crash after 
> all packages are installed, it gets about half way done with "Performing post 
>install configuration"
> Then it :
> 
> # I had to write all this by hand but i "think" its mostly lowercase and all 
>0's(zeros) not O's
> 
> ------------------------ cut ----------------------------
> 
> 
> kernel BUG at inode.c:1051 !
> invalid operand: 0000
> cpu:0
> EIP:0010:[<c0147948>] Not tainted
> EFLAGS: 00010246
> 
> EIP is at (2.4.18-14BOOT)
> eax:c13ec370 EBX:c13ec370 ECX:c13ec484 EDX:c13ec484
> ESI:c1341400 ED:00000000 EBP: c0277a40 ESP:c3ff9f4c
> DS:0018 ES:0018 SS:0018ents 
> Process anaconda (pid:12, stackpage=c3ff9000)
> Stack: c13f1400 c13f14e0 c3fafea0 c01cb19f c13ec370 c13f1440 c13f1400 c013a33c
>        c13f14oo c0277a8c 00000000 c3ff9f8c 08941b4c bffff218 c0149368 c13f1400
>        c3fafea0 c1253390 00000000 00000000 3d996170 00000009 00000001 c3ff8000
> 
> call trace:[<c01cb19f>] (0xc3ff9f58))
> [<c013a33c7>] (0xc3ff9f68))
> [<c0149368>]  (0xc3ff9f84))
> [<c01493c3>]  (0xc3ff9fb4))
> [<c0108943>]  (0xc3ff9fc0))
> 
> code: 0f 0b 1b 04 b2 3b 23 c0 e9 74 fe ff ff 90 89 f6 8b 54 24 04
> install exited abnormally -- Received signal 11
> ------------------------ cut ----------------------------
>  Since I can duplicate this please let me know whatever info you need me to get, & 
>how to get it. and especially
> if you have an idea for a workaround, this is my second day of downtime.
> I cannot get into the shell by f2 once crash happens so typing there is pointless. 
>f1 & f3(i think) was how I got this dump info
> also tried ctrl+fn and nothing..
> 
> * checked md5sums
> * did media check on disks 1, 2 and 3 (dont have 4, 5.)
> * had limbo 2 running before.
> 
> 
> 
> 
> 
> 
> -- 
> Psyche-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/psyche-list




Reply via email to