Kernel Panic at boot with -CURRENT (last 2-3 days)
Background: --- Work recently assigned me a Gateway GP7-500 (PIII-500mhz, 96M RAM) to replace my older 333mhz PII that's been running FreeBSD 3.2.. Of course, as my testing machine, I wanted to run FreeBSD 4.0-CURRENT on it, and installed the 19990806 snapshot without a problem, and then cvsupped it to -CURRENT. Problem: This was on 17AUG, my kernel panic'd, I just assumed I left something out, but then I saw that GENERIC panic'd as well, and has panic'd since 17AUG, and continues to do so with the -CURRENT snapshot of an hour ago. However, GENERIC from 19990806 works just fine. I decided that after 3 days of kernel panics that it's a real problem and not just some little -CURRENT breakage. I decided yesterday that maybe I need to make world first, so I did. No dice there. And an hour ago, I also rm -Rf'd /usr/src, cvsupped to -CURRENT, made world again, and attempted to rebuild the kernel. Boot Sequence: -- If you want to see dmesg.boot from the 4.0-19990806-CURRENT snapshot, it's at http://haloblack.org/misc/dmesg.boot FreeBSD 4.0-CURRENT #0: thu Aug 19 12:44:12 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC+DDB Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III (498.67-MHz 686-class CPU) Origin = "Genuine Intel" Id = 0x672 Stepping = 2 Features = blah blah blah real memory = 100663296 (98304K bytes) config di lnc0 config di le0 .. .. config q avail memory = 93708288 (91512K bytes) Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x58:0xbc28 stack pointer = 0x10:0xed4 frame pointer = 0x10:0xf20 code segment= base 0xc00f, limit 0x, type 0x1b = DPL 0, pres 1, def32 0, gran 0 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam kernel: type 9 trap, code=0 Stopped at 0xbc28: repeat, DDB? -- Med vanlig halsingar, thomas stromberg [TRS40/SM0VVW]: smtp([EMAIL PROTECTED]) systems guru / asst. is manager: http(www.afterthought.org) research triangle consultants, inc : pots(919.380.9771 x3210) http://www.rtci.com: fax(919.380.1727) FreeBSD: The Power to Serve! : icq(17468041) BeOS Developer ID: 18330 : efnet(Mithra) : "if you do nothing enough, something's bound to happen.." : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel Panic at boot with -CURRENT (last 2-3 days)
See my earlier post today, it is due to the PnP probe. If you boot a kernel which is older than Mikes commit, you can boot the new kernel after a soft reboot... Poul-Henning In message [EMAIL PROTECTED], Thomas Stromberg writes: Background: --- Work recently assigned me a Gateway GP7-500 (PIII-500mhz, 96M RAM) to replace my older 333mhz PII that's been running FreeBSD 3.2.. Of course, as my testing machine, I wanted to run FreeBSD 4.0-CURRENT on it, and installed the 19990806 snapshot without a problem, and then cvsupped it to -CURRENT. Problem: This was on 17AUG, my kernel panic'd, I just assumed I left something out, but then I saw that GENERIC panic'd as well, and has panic'd since 17AUG, and continues to do so with the -CURRENT snapshot of an hour ago. However, GENERIC from 19990806 works just fine. I decided that after 3 days of kernel panics that it's a real problem and not just some little -CURRENT breakage. I decided yesterday that maybe I need to make world first, so I did. No dice there. And an hour ago, I also rm -Rf'd /usr/src, cvsupped to -CURRENT, made world again, and attempted to rebuild the kernel. Boot Sequence: -- If you want to see dmesg.boot from the 4.0-19990806-CURRENT snapshot, it's at http://haloblack.org/misc/dmesg.boot FreeBSD 4.0-CURRENT #0: thu Aug 19 12:44:12 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC+DDB Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III (498.67-MHz 686-class CPU) Origin = "Genuine Intel" Id = 0x672 Stepping = 2 Features = blah blah blah real memory = 100663296 (98304K bytes) config di lnc0 config di le0 .. .. config q avail memory = 93708288 (91512K bytes) Fatal trap 9: general protection fault while in kernel mode instruction pointer= 0x58:0xbc28 stack pointer = 0x10:0xed4 frame pointer = 0x10:0xf20 code segment = base 0xc00f, limit 0x, type 0x1b = DPL 0, pres 1, def32 0, gran 0 processor eflags = interrupt enabled, resume, IOPL = 0 current process= Idle interrupt mask = net tty bio cam kernel: type 9 trap, code=0 Stopped at 0xbc28: repeat, DDB? -- Med vanlig halsingar, thomas stromberg [TRS40/SM0VVW]: smtp([EMAIL PROTECTED]) systems guru / asst. is manager: http(www.afterthought.org) research triangle consultants, inc : pots(919.380.9771 x3210) http://www.rtci.com: fax(919.380.1727) FreeBSD: The Power to Serve! : icq(17468041) BeOS Developer ID: 18330 : efnet(Mithra) : "if you do nothing enough, something's bound to happen.." : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel Panic at boot with -CURRENT (last 2-3 days)
This appears to be due to our PnP BIOS invocation not being sufficiently bug-compatible with some BIOSsen. I'm going to need to do some more work on this, and if you have time I'd like to get you involved in the testing process. Meanwhile I'll be disabling the PnP BIOS scan which should get you back on the rails. Boot Sequence: -- If you want to see dmesg.boot from the 4.0-19990806-CURRENT snapshot, it's at http://haloblack.org/misc/dmesg.boot FreeBSD 4.0-CURRENT #0: thu Aug 19 12:44:12 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC+DDB Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III (498.67-MHz 686-class CPU) Origin = "Genuine Intel" Id = 0x672 Stepping = 2 Features = blah blah blah real memory = 100663296 (98304K bytes) config di lnc0 config di le0 .. .. config q avail memory = 93708288 (91512K bytes) Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x58:0xbc28 stack pointer = 0x10:0xed4 frame pointer = 0x10:0xf20 code segment = base 0xc00f, limit 0x, type 0x1b = DPL 0, pres 1, def32 0, gran 0 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask= net tty bio cam kernel: type 9 trap, code=0 Stopped at0xbc28: repeat, DDB? -- Med vanlig halsingar, thomas stromberg [TRS40/SM0VVW]: smtp([EMAIL PROTECTED]) systems guru / asst. is manager: http(www.afterthought.org) research triangle consultants, inc : pots(919.380.9771 x3210) http://www.rtci.com: fax(919.380.1727) FreeBSD: The Power to Serve! : icq(17468041) BeOS Developer ID: 18330 : efnet(Mithra) : "if you do nothing enough, something's bound to happen.." : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
