Joe Auty <[EMAIL PROTECTED]> writes:
> 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.
That is
ED]>;
;
Sent: Monday, February 26, 2007 8:36 AM
Subject: Re: kernel panic at boot on any 6.x OS
> > 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
&g
- Original Message -
From: "Joe Auty" <[EMAIL PROTECTED]>
To: "Ted Mittelstaedt" <[EMAIL PROTECTED]>
Cc: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]>; "Kip Macy"
<[EMAIL PROTECTED]>; ;
Sent: Monday, February 26, 2007 10:01
-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
-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
On 2007-Feb-26 17:38:10 -0500, Joe Auty <[EMAIL PROTECTED]> wrote:
>My system does boot off of disc 1 of the FreeBSD 6.2 CD.
That's a good start. Together with your memtest results, it
suggests that your hardware is OK.
> However,
>even when copying the /boot directory from the CD to my machin
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 w
-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 checke
In <[EMAIL PROTECTED]>, Ted Mittelstaedt <[EMAIL PROTECTED]> typed:
> > 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)?
For the record, I do a rebuild between point releases - actually, I
track -stabl
MAIL 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]>
- 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 P
>; ;
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=mycon
- 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
-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 th
-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
info
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 3:01 AM, LI Xin wrote:
Hi,
Joe Auty wrote:
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 tr
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 a
Hi,
Joe Auty wrote:
> 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?
Which .ko are you trying to load? try removing them and see if thin
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 ha
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
21 matches
Mail list logo
