Re: kernel panic at boot on any 6.x OS *SOLVED!*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sort of... Thanks for everybody that has helped me! It turns out I had a couple of rc.d scripts in /usr/local/etc/rc.d that were doing kldloads: rtc.sh and kqemu.sh - one of these was causing the panic. It might be worthwhile adding to the world rebuild doc a suggestion to grep kldload /usr/local/etc/rc.d and disable/ remove these services... Or, simply moving /usr/local/etc/rc.d might also be worthwhile test. I guess the trick here was not considering that user space apps would be trying to do a kldload, and that calling upon a module that is either missing in /boot/kernel or /boot/modules or resides outside of /boot can trigger these panics. Always the most simple of solutions that kicks you in the ass, isn't it? =) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4894CgdfeCwsL5ERAlvfAKCiLEGZMTsGonn0OrdlTTMCp9GeZACePQ2V WCwXuHBFh/FOVsDJLa84Yks= =85PR -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Unfortunately, my /boot/modules is already empty =( On Feb 26, 2007, at 9:51 PM, Kip Macy wrote: It looks like it may be loading an out of sync kernel module. Cleaning out /boot/modules might help. -Kip On 2/26/07, Joe Auty <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, My system does boot off of disc 1 of the FreeBSD 6.2 CD. However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode. I've run a memtest, and it checked out fine. There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point... If you have any other ideas, I'm all ears! Here is my error message again (with verbose logging enabled, although that has no effect on this output): > WARNING: Device driver " > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x40 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc06d4614 > stack pointer = 0x28:0xf015491c > frame pointer = 0x28:0xf015491c > code segment = base 0x0, limit 0xff, type 0x1b >= DPL 0, pres 1, def32 1, gran 1 > processor eflags = interupt enabled, resume, IOPL = 0 > current process = 898 (kldload) > trap number = 12 > panic: page fault > uptime: 36s > cannot dump. No dump device defined > automatic reboot in 15 seconds Thanks again for your time! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD4DBQFF42FSCgdfeCwsL5ERArNQAJ9pEyu3ZT3BXe4YhEsgRsid6fB+SwCXeGjO fO0GeeBUPKKYq4N5rRHDTw== =PgI8 -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers- [EMAIL PROTECTED]" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF47d2CgdfeCwsL5ERAg/iAKCLVp7f+SB/f2xbT43lu4IeQWJxuACfa+L1 tpwQkQetPAVf53uCTA3hr6A= =ej7q -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, My system does boot off of disc 1 of the FreeBSD 6.2 CD. However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode. I've run a memtest, and it checked out fine. There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point... If you have any other ideas, I'm all ears! Here is my error message again (with verbose logging enabled, although that has no effect on this output): WARNING: Device driver " Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds Thanks again for your time! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD4DBQFF42FSCgdfeCwsL5ERArNQAJ9pEyu3ZT3BXe4YhEsgRsid6fB+SwCXeGjO fO0GeeBUPKKYq4N5rRHDTw== =PgI8 -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic at boot on any 6.x OS
On Feb 26, 2007, at 8:01 AM, Ted Mittelstaedt wrote: - Original Message - From: "Joe Auty" <[EMAIL PROTECTED]> To: "Ted Mittelstaedt" <[EMAIL PROTECTED]> Cc: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]>; "Kip Macy" <[EMAIL PROTECTED]>; ; Sent: Sunday, February 25, 2007 10:39 PM Subject: Re: kernel panic at boot on any 6.x OS -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: "Joe Auty" <[EMAIL PROTECTED]> To: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]> Cc: "Kip Macy" <[EMAIL PROTECTED]>; [EMAIL PROTECTED]>; Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). If wiping the disk really isn't an option then you have one or more of the following problems: 1) Production system with a lack of hardware spares 2) inadequate backup plan and execution. People who state that wiping the disk isn't an option are screaming at the top of their lungs for the hardware gremlins to explain what MTBF is all about. The gremlins will visit you, I guarentee. And they always pick the very best times for it too. I just hope (if this is your workplace) that your job survives. My production system is backed up daily to two different sites, that's not an issue. The system I'm thinking of upgrading to 6.2 is my test server I run out of my house that stores movie files and other non-essential files. Technically, wiping it clean *would* be an option if it came down to it, just an inconvenience. Perhaps I should invest in another HD to use for instances such as this. For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) The problem is that all of the ports and packages that you put on a server change from release to release. The developers of openssl, for example, don't give a tinkers damn about how FreeBSD's upgrade process works, when they are making changes in their code. I run a number of FreeBSD servers and what I do is simply keep them patched with security updates. Every once in a while a security hole will be discovered in a non-core program and if it's serious enough I'll go into the port and do a "make deinstall" followed by downloading and compiling the program the "old fashioned way" I shoot for a min of 3 years on the OS before even thinking about updating, and when it's time to update the hardware has generally reached the old rag stage anyway. Do you run any non-production machines where you test running newer OSes and test software updates and such? --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: "Joe Auty" <[EMAIL PROTECTED]> To: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]> Cc: "Kip Macy" <[EMAIL PROTECTED]>; ; Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) Thanks again! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4oC3CgdfeCwsL5ERAj3vAJ9bMYSj33hg/jU5jU6RyIjXqJ/YLwCfVumh FsunyXJGMjXHEHKso7xWzcI= =0p6j -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 11:14 AM, Joe Auty wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print
out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can
only have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw->d_version != D_VERSION_01) {
printf(
"WARNING: Device driver \"%s\" has wrong
version %s\n",
devsw->d_name == NULL ? "???" : devsw->d_name,
"and is disabled. Recompile KLD module.");
Looks like the kernel and the modules are out of sync.
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=myconfig
Shouldn't this have installed a fresh kernel plus only essential
modules?
Here is a diff of my kernel config (which I've called, rather
uncreatively, 6.x) against GENERIC:
nothing unusual, just IPFIREWALL and Linux compat stuff, right?
Forgot to add that I believe I've also tried building a GENERIC
kernel and ran into this same problem. It's been a while since I
tried this though, so I'll gladly try this again if you think it
would be a useful test! =)
# diff 6.x GENERIC
19c19
< # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01
00:15:12 scottl Exp $
- ---
> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09
18:41:36 simon Exp $
30,42c30
< options IPFIREWALL
< options IPFIREWALL_VERBOSE
< options IPFIREWALL_VERBOSE_LIMIT=10
< options IPFIREWALL_DEFAULT_TO_ACCEPT
< options IPDIVERT
< #options VFS_AIO
< #options HZ=1200
< #options SMP # Symmetric
MultiProcessor Kernel
< #device pf
< #device pflog
< #device pfsync
< options COMPAT_LINUX
< options BRIDGE
- ---
> makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
44,49d31
< # Enable the linux-like proc filesystem support (requires
COMPAT_LINUX and PSEUDOFS)
< options LINPROCFS
<
< #makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
<
< #options SCHED_ULE # ULE scheduler
77,80d58
< options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
< # output. Adds ~128k to
driver.
< options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
< # output. Adds ~215k to
driver.
103a82,83
> options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
> # output. Adds ~128k to
driver.
104a85,86
> options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
> # output. Adds ~215k to
driver.
226a209
> devicestge# Sundance/Tamarack TC9021
gigabit Ethernet
248a232,234
> devicewlan_wep# 802.11 WEP support
> devicewlan_ccmp # 802.11 CCMP support
> devicewlan_tkip # 802.11 TKIP support
249a236,238
> deviceath # Atheros pci/cardbus NIC's
> deviceath_hal # Atheros HAL (Hardware
Access Layer)
> deviceath_rate_sample # SampleRate tx rate
control for ath
On 2/24/07, Joe Auty <[EMAIL PROTECTED]> wrote:
Hello,
(sorry, don't know whether kernel problems should go to
questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release,
but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the
following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build
and
installed cleanly without any errors...
WARNING: Device driver "
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d461
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Kip, I'd gladly try a snapshot kernel, but I'm not sure which one to pick out of this list: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/kernels Any suggestions? On Feb 25, 2007, at 2:59 AM, Kip Macy wrote: It looks as if you've hit a device driver that is trying to print out a null string. The message you've given doesn't provide any more information than that. If you install a snapshot kernel it will probably have ddb compiled in which will allow you to at least get a backtrace. I'm sorry you're having trouble. -Kip On 2/24/07, Joe Auty <[EMAIL PROTECTED]> wrote: Hello, (sorry, don't know whether kernel problems should go to questions or hackers, or both).. This has been a long-standing problem of mine, but I always ignored it hoping it would go away on its own with a future 6.x release, but it remains... No matter whether I boot into safe mode or regular mode, with all kernel extensions disabled in /boot/loader.conf, I get the following panic late at boot of a fresh RELENG_6_2 kernel (with only a few services left to bring up). The 6.x kernels I've tried all build and installed cleanly without any errors... > WARNING: Device driver " > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x40 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc06d4614 > stack pointer = 0x28:0xf015491c > frame pointer = 0x28:0xf015491c > code segment = base 0x0, limit 0xff, type 0x1b >= DPL 0, pres 1, def32 1, gran 1 > processor eflags = interupt enabled, resume, IOPL = 0 > current process = 898 (kldload) > trap number = 12 > panic: page fault > uptime: 36s > cannot dump. No dump device defined > automatic reboot in 15 seconds This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Thanks in advance for your help! --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers- [EMAIL PROTECTED]" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4bZMCgdfeCwsL5ERAv0zAJ4zRjih+XoXGjF8Bc4hd2Yj7I0WNQCfeEb5 5mLoo1jTuYnJpa2z1EJqbUY= =Jwsg -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can only
have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw->d_version != D_VERSION_01) {
printf(
"WARNING: Device driver \"%s\" has wrong
version %s\n",
devsw->d_name == NULL ? "???" : devsw->d_name,
"and is disabled. Recompile KLD module.");
Looks like the kernel and the modules are out of sync.
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=myconfig
Shouldn't this have installed a fresh kernel plus only essential
modules?
Here is a diff of my kernel config (which I've called, rather
uncreatively, 6.x) against GENERIC:
nothing unusual, just IPFIREWALL and Linux compat stuff, right?
# diff 6.x GENERIC
19c19
< # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01
00:15:12 scottl Exp $
- ---
> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09
18:41:36 simon Exp $
30,42c30
< options IPFIREWALL
< options IPFIREWALL_VERBOSE
< options IPFIREWALL_VERBOSE_LIMIT=10
< options IPFIREWALL_DEFAULT_TO_ACCEPT
< options IPDIVERT
< #options VFS_AIO
< #options HZ=1200
< #options SMP # Symmetric MultiProcessor
Kernel
< #device pf
< #device pflog
< #device pfsync
< options COMPAT_LINUX
< options BRIDGE
- ---
> makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
44,49d31
< # Enable the linux-like proc filesystem support (requires
COMPAT_LINUX and PSEUDOFS)
< options LINPROCFS
<
< #makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
<
< #options SCHED_ULE # ULE scheduler
77,80d58
< options AHC_REG_PRETTY_PRINT# Print register bitfields in
debug
< # output. Adds ~128k to driver.
< options AHD_REG_PRETTY_PRINT# Print register bitfields in
debug
< # output. Adds ~215k to driver.
103a82,83
> options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
> # output. Adds ~128k to
driver.
104a85,86
> options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
> # output. Adds ~215k to
driver.
226a209
> devicestge# Sundance/Tamarack TC9021
gigabit Ethernet
248a232,234
> devicewlan_wep# 802.11 WEP support
> devicewlan_ccmp # 802.11 CCMP support
> devicewlan_tkip # 802.11 TKIP support
249a236,238
> deviceath # Atheros pci/cardbus NIC's
> deviceath_hal # Atheros HAL (Hardware
Access Layer)
> deviceath_rate_sample # SampleRate tx rate control
for ath
On 2/24/07, Joe Auty <[EMAIL PROTECTED]> wrote:
Hello,
(sorry, don't know whether kernel problems should go to questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release, but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build and
installed cleanly without any errors...
WARNING: Device driver "
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime: 36s
cannot dump. No dump device defined
automatic reboot in 15 seconds
Thi
kernel panic at boot on any 6.x OS
Hello, (sorry, don't know whether kernel problems should go to questions or hackers, or both).. This has been a long-standing problem of mine, but I always ignored it hoping it would go away on its own with a future 6.x release, but it remains... No matter whether I boot into safe mode or regular mode, with all kernel extensions disabled in /boot/loader.conf, I get the following panic late at boot of a fresh RELENG_6_2 kernel (with only a few services left to bring up). The 6.x kernels I've tried all build and installed cleanly without any errors... WARNING: Device driver " Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Thanks in advance for your help! --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] PGP.sig Description: This is a digitally signed message part
