kernel panic on boot
I'd a little trouble getting the OS installed; after installing SILO, I didn't know how to get the prom to boot it (eventually, I guessed right, and boot disk0:0 worked). However, on first boot, base-config was run, and immediately caused a (reproducable) kernel-panic. I'm not quite sure what to do - this is a bog-standard Ultra10, that was happily running solaris until yesterday. It's crashing in install-keymap somewhere. The first line of the dump is; data_access_exception: SFSR[0801009] SFAR[033890020040] If anyone can help, I can copy the whole thing into a mail etc. John
Re: kernel panic on boot
On Tue, Sep 24, 2002 at 08:54:33AM +0100, John P. Looney mentioned: However, on first boot, base-config was run, and immediately caused a (reproducable) kernel-panic. I'm not quite sure what to do - this is a bog-standard Ultra10, that was happily running solaris until yesterday. It's crashing in install-keymap somewhere. Turns out during the install I had selected a type5 instead of a type6 keyboard. I booted into single user mode, and changed the /root/dbootstrap_settings file to say I'd a type6 keyboard, and it stopped crashing. That's kinda a serious bug in the kernel, no ? Kate
Re: kernel panic on boot
On Tue, 24 Sep 2002 09:33:40 +0100 John P. Looney [EMAIL PROTECTED] wrote: However, on first boot, base-config was run, and immediately caused a (reproducable) kernel-panic. I'm not quite sure what to do - this is a bog-standard Ultra10, that was happily running solaris until yesterday. It's crashing in install-keymap somewhere. I had this one the other week, too. Nobody else on #sparc seemed to have heard of it which I found surprising. I got round it (eventually) by booting into single user mode and installing with apt, and then persuading base-config that it had already run. I'm not certain it's related to the keyboard though - I could log in on the second VC and work away happily (aside from base-config having a lock on the config database.) However, killing any part of the base-config process tree locked the machine solid instantly. The only error message I was getting on boot was about the RTC - I'd not selected the rtc.o module to be loaded at boot and so it couldn't set the hardware clock. I thought that I did have a type5 keyboard - it's set up as type5 at the moment and it works perfectly. Did any Ultra10s come with type5 keyboards? The machine in question is one of our oldest U10s. Perhaps there's a deeper bug that base-config triggers? The box has been working flat out for about a week now on an intensive CFD problem and not shown the slightest instability at all. Regards, AJ MacLeod
Re: kernel panic on boot
AJ MacLeod [EMAIL PROTECTED] writes: I had this one the other week, too. Nobody else on #sparc seemed to have heard of it which I found surprising. I don't know whether it's the same thing, but I've long had a bug open against kernel 2.4.18 (I think) about a kernel oops loading the sunt5-uk keymap. (In my case, I have a different keymap file which works to give me a usable keyboard.)
Re: Official 2.2rev2 CD Kernel Panic on boot
Make sure cdrom block size is set to 512 bytes. There may be a block jumper on the cdrom near where termination is set. Standard PeeCee block size of 2048 will not work. L1-A == Stop-A Tad Ken Teague wrote: I just downloaded and burned 2.2rev2 and attempted to use it to boot my SS20. Durring boot I get: snip> cdrom: open failed VFS: Cannot open root device 0b:00 Press L1-A to return to the boot prom snip> In the past I've used CD-ROM drives (Sony, and others) pulled from old PowerPC boxes to boot Solaris and Debian without problems. Today I have a NEC SICD-12x hooked up on ID6. Looking at the error above it would appear that this CD-ROM drive may not be fully compatible for booting or whatnot. Can anyone confirm this? I don't have my 2.2rev1 CD's around to confirm if it's a bug with the rev2 CD's. Also, what does "Press L1-A" mean? Stop-A? Thanks. - Ken -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Tad Bilby Rave Computer Assoc. 800-966-7283
Official 2.2rev2 CD Kernel Panic on boot
I just downloaded and burned 2.2rev2 and attempted to use it to boot my SS20. Durring boot I get: snip cdrom: open failed VFS: Cannot open root device 0b:00 Press L1-A to return to the boot prom snip In the past I've used CD-ROM drives (Sony, and others) pulled from old PowerPC boxes to boot Solaris and Debian without problems. Today I have a NEC SICD-12x hooked up on ID6. Looking at the error above it would appear that this CD-ROM drive may not be fully compatible for booting or whatnot. Can anyone confirm this? I don't have my 2.2rev1 CD's around to confirm if it's a bug with the rev2 CD's. Also, what does Press L1-A mean? Stop-A? Thanks. - Ken
