*sigh* found this sitting on the "not done" pile from over a week ago... 8-/
Dave Wickberg wrote: > On 8/19/05, Nick Holland <[EMAIL PROTECTED]> wrote: >> Dave Wickberg wrote: >> > Hi, >> > >> > I've just recently installed OpenBSD 3.7 (Release) on a Celeron 466 w/ >> > 256MB of RAM. >> > >> > I created a boot floppy and from there the install went flawlessly. >> > However, after booting the systems for first time I am getting a >> > kernel page fault error as soon as I try to type in a userid. >> > >> > This is what I'm seeing after waiting for the login prompt and hitting one >> > key: >> > --- >> > OpenBSD/i386 (wormy.starbase) (ttyC0) >> > >> > login: kernel: page fault trap, code = 0 >> > Stopped at pckbc_enqueue_cmd+0x7d: sbbb 0(%eax),%al >> > ddb> kernel: page fault trap, code = 0 >> > Faulted in DDB; continuing... >> > ddb> >> > --- >> do you happen to see a message about including a "ps" and "trace" with >> your problem report? >> > > Actually no, just what I have above - I guess that would have come > after the "Faulted in DDB; continuing..." line? Here's the output from > ps and trace respectively: interesting. I think that's what is refered to as a double fault...and yes, the "ps" and "trace" warning probably got smushed by the second fault. > PID PPID PGRP UID S FLAGS WAIT COMMAND > 17210 6950 17210 0 3 0x4086 ttyin csh > 8950 2863 6950 0 3 0x4084 select sshd > 28407 1 28407 0 3 0x4086 ttyin getty > 11599 1 11599 0 3 0x4086 ttyin getty > 2024 1 2024 0 3 0x4086 ttyin getty > 3200 1 3200 0 3 0x4086 ttyin getty > 20666 1 20666 0 3 0x4086 ttyin getty > 14322 1 14322 0 3 0x84 select cron > 18567 1 18567 0 3 0x40184 select sendmail > 2863 1 2863 0 3 0x84 select sshd > 19286 1 19286 0 3 0x184 select inetd > 6021 1 6021 0 3 0x84 poll ntpd > 21199 1 13058 83 3 0x186 poll ntpd > 3268 31864 31864 73 3 0x184 poll syslogd > 31864 1 31864 0 3 0x84 netio syslogd > 16126 1 16126 77 3 0x184 poll dhclient > 2558 1 13058 0 3 0x86 poll dhclient > 11 0 0 0 3 0x100204 crypto_wa crypto > 10 0 0 0 3 0x100204 aiodoned aiodoned > 9 0 0 0 3 0x100204 syncer update > 8 0 0 0 3 0x100204 cleaner cleaner > 7 0 0 0 3 0x100204 reaper reaper > 6 0 0 0 3 0x100204 pagedaemon pagedaemon > 5 0 0 0 3 0x100204 usbtask usbtask > 4 0 0 0 3 0x100204 usbevt usb0 > 3 0 0 0 3 0x100204 apmev amp0 > 2 0 0 0 3 0x100204 kmalloc kmthread > 1 0 0 0 3 0x4084 wait init > 0 0 0 0 3 0x80204 scheduler swapper > > > pckbc_enqueue_cmd(d05aad20,0,d06d3d86,2,0) at pckbc_enqueue_cmd+0x7d > pckbd_set_leds(d0b5dd00,f10e,f103,80) at pckbd_set_leds+0x3c > wskbd_translate(d05aa480,2,1d,1d) at wskbd_translate+0x101 > wskbd_input(d0b5fe00,2,1d,1) at wskbd_input+0x3e > pckbd_input(d0b5dd00,1d,80dd,160000) at pckbd_input+0x53 > pckbcintr(d0b5dd80) at pckbcintr+0x9f > Xrecurse_legacy1() at Xrecurse_legacy1+0x86 > --- interrupt --- > idle_loop(d065ed80,28,0,0,80000000) at idle_loop+0x21 > bpendtsleep(d05b2260,4,d04f5931,0,0,ffffffff,d04afc2c,0) at bpendsleep > uvm_scheduler(d05b2258,3,0,d04afc2c,fff0000) at uvm_scheduler+0x6b > check_console(0,0,0,0,0) at check_console > >> you have a few "extra" things in there -- I'd remove them. The ISA NIC, >> the audio card (if possible, disable in BIOS if not possible to >> physically remove), see if the thing settles down. >> >> The ISA NIC has got my attention. I'm not certain how that would mess >> it up in this way, but it's the best idea I have at the moment. > > Makes sense. I first took out the ISA NIC and then disabled the > on-board sound checking each time to see if there was any change - in > each case the problem still occurred. New dmesg is: hm. ok, a couple other tests... 1) What happens if you try to bring the system up in Single User mode (boot -s from the "boot>" prompt). I'm not sure what conclusion to draw either way on that...but... 2) What happens if you install a snapshot kernel? (that should have been my first suggestion, find out if the problem is already fixed! :) Nick.
