can someone explain to me, please, why i get a kernel panic on boot w/ the
latest 7.1 when i have something plugged into a usb port?
thx.
david coder
network engineer emeritus
verio/ntt
___
freebsd-questions@freebsd.org mailing list
http
When I try to boot FreeBSD, it cycles through all of my hardware etc.
as with a regular boot then says:
panic: ohci_add_done: addr 0x7fef16d0 not found
and tells me that it's rebooting, and just keeps doing this.
I was told that it was most likely a USB issue, especially if I had
recently added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Meaghan Hayes wrote:
When I try to boot FreeBSD, it cycles through all of my hardware etc.
as with a regular boot then says:
panic: ohci_add_done: addr 0x7fef16d0 not found
and tells me that it's rebooting, and just keeps doing this.
I
What modules are loaded from loader.conf?
I had two distinct issues on one machine that were entirely due to
module loading. One was sound, using snd_driver instead of a specific
sound driver caused the machine to reboot. The other issue was
nvidia. The binary nvidia driver caused an instant
At 07:32 PM 12/15/2007, jekillen wrote:
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
On Dec 16, 2007, at 7:58 AM, Derek Ragona wrote:
At 07:32 PM 12/15/2007, jekillen wrote:
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and reconfigure, software wise, and hardware wise. The first was a new
case which I got
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and reconfigure, software wise, and
hardware RAID card.
The panic only occurs when the machine is cold-booted (not on reboot)
when acpi.ko is loaded.
http://home.cyberleo.net/cyberleo/workspace/Zip/Bugs/fbsd-20070716-panic/boot-dump.log
Any ideas what I can do to debug or correct this issue, or of a more
appropriate group
8006-2LP
SATA hardware RAID card.
The panic only occurs when the machine is cold-booted (not on
reboot) when acpi.ko is loaded.
http://home.cyberleo.net/cyberleo/workspace/Zip/Bugs/fbsd-2007
0716-panic/boot-dump.log
Any ideas what I can do to debug or correct this issue
Tamouh H. wrote:
The first thing I'd try is boot direct to the drive, without the RAID card.
It seems from the dump it paniced after loading the 3ware drivers:
RocketRAID 232x controller driver v1.02 (Jul 16 2007 17:38:56)
panic: pmap_mapdev: Couldn't alloc kernel virtual memory
cpuid = 0
: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
thinking about updating, and when it's time to update the hardware has
generally reached
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
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]; freebsd-questions
: 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
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 -stable on
-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
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
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 machine,
-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
-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
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]; freebsd-questions@freebsd.org
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
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 things
, 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
-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
, 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
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
...
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
- Original Message -
From: Joe Auty [EMAIL PROTECTED]
To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED]
Cc: Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org;
freebsd-hackers@freebsd.org
Sent: Sunday, February 25, 2007 8:14 AM
Subject: Re: kernel panic at boot on any 6.x OS
Any
@freebsd.org
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
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
Hello,
I'm testing 6.0 on my test machine, and even in safe mode the machine
kernel panics on boot. Where is the file that contains the kernel
panic dumps, and where should I send my report to?
---
Joe Auty
NetMusician: web publishing software for musicians
, installed again as
drive #1, same problem and panic.
- I tried with only that one harddrive with FBSD 5.4 installed (all
other HDs removed) - same panic
- I tried with no HDs, just to see if the cd would boot - same panic.
- I tried with 4.9 release CD, ISO from Monday oct 27 , 2003, same
Norberto Meijome wrote:
lspci -v : attached
dmesg (linux knoppix 3.8): attached
list server blocked the attachments. Please find them here:
lspci -v : http://meijome.net/files/fbsd/arsmagna_lspci-v.txt
dmesg (linux knoppix 3.8): http://meijome.net/files/fbsd/arsmagna_dmesg.txt
thanks
beto
I woke up this morning to find that my computer had rebooted and panicked as
soon as the kernel had started to run. it said:
The rights of the University...
panic: vm_page_insert: alredy inserted
uptime: 0s
in bright white on the screen. All I could do was switch it off and on and it
just did
On Saturday 29 January 2005 08:15 am, Xian wrote:
I woke up this morning to find that my computer had rebooted
and panicked as soon as the kernel had started to run. it said:
The rights of the University...
panic: vm_page_insert: alredy inserted
uptime: 0s
in bright white on the screen.
On Saturday 29 January 2005 13:15, Xian wrote:
I woke up this morning to find that my computer had rebooted and panicked
as soon as the kernel had started to run. it said:
The rights of the University...
panic: vm_page_insert: alredy inserted
uptime: 0s
in bright white on the screen. All
On Saturday 29 January 2005 13:41, Mike Hauber wrote:
On Saturday 29 January 2005 08:15 am, Xian wrote:
I woke up this morning to find that my computer had rebooted
and panicked as soon as the kernel had started to run. it said:
The rights of the University...
panic: vm_page_insert:
Greg 'groggy' Lehey said:
The current status of Vinum in -CURRENT is that it is being
rewritten. The introduction of the GEOM layer has badly broken Vinum,
and it has been decided better to rewrite it than to fix it. It'll be
a while before it's smooth again.
This would be a good note to
On Thursday, 8 July 2004 at 2:21:30 -0500, Mario Doria wrote:
Hi,
Another vinum question. I have a machine running 5-CURRENT sources from
yesterday (yes I know the dangers of running CURRENT and I did read the
mailing list archives).
Well, the issue was discussed there.
I think I found
Hi,
Another vinum question. I have a machine running 5-CURRENT sources from
yesterday (yes I know the dangers of running CURRENT and I did read the
mailing list archives). I think I found a bug, if I add
start_vinum=YES to /etc/rc.conf, at boot I get a panic with a message
saying:
panic:
Hi again,
Sorry for replying to my own post, I wanted to add some more details.
Here's a more detailed message about the panic on boot:
Mounting root from ufs:/dev/ad0s1a
Pre-seeding PRNG: kickstart.
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart
On a Prostar model 2253 (Series 2200T) laptop,
with 512Meg ram, P3 1.2 GHz, I tried to install
freeBSD using boot floppies kern.flp and mfsroot.flp
The bootup panics immediately after probing pccard0
with page fault.
This is consistently the case with release 5.1, 5.2,
and
5.2.1.
Any help would
Arya Nasha [EMAIL PROTECTED] writes:
On a Prostar model 2253 (Series 2200T) laptop,
with 512Meg ram, P3 1.2 GHz, I tried to install
freeBSD using boot floppies kern.flp and mfsroot.flp
The bootup panics immediately after probing pccard0
with page fault.
This is consistently the case with
in boot/loader.rc:
.
.
set hint.acpi.0.disabled=1
.
.
So ACPI is dispabled.
Arya
--- Lowell Gilbert
[EMAIL PROTECTED] wrote:
Arya Nasha [EMAIL PROTECTED] writes:
On a Prostar model 2253 (Series 2200T) laptop,
with 512Meg ram, P3 1.2 GHz, I tried to install
freeBSD using boot
Hello,
we've a FreeBSD 5.1 box at a hosting company. As we need a lot more
maxsockets and resources, I added the following lines to /boot/loader.conf:
kern.ipc.maxsockets=64
kern.maxusers=4096
kern.ipc.nmbclusters=12
Some would say, these are somewhat crazy values for this options, but
George Hartzell wrote:
George Hartzell writes:
I've been trying to install something 5-ish on a Sony PCG-GRX570
laptop.
I started off trying to boot off of the 5.1 release CD, normally,
w/out acpi, and safe. Every option panic-ed, with essentially the
same message (see below), although
Remington writes:
George Hartzell wrote:
George Hartzell writes:
I've been trying to install something 5-ish on a Sony PCG-GRX570
laptop.
I started off trying to boot off of the 5.1 release CD, normally,
w/out acpi, and safe. Every option panic-ed, with
On Tue, Jul 08, 2003 at 01:05:18PM -0400 or thereabouts, Michael E. Mercer wrote:
On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote:
On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote:
Alrighty then,
Ok, after following FAQ 18.13 on the freebsd web site,
Josh,
Is there an easy way to capture this without me having to handwrite all
that info down myself?
Michael Mercer
On Wed, 2003-07-09 at 13:19, Joshua Oreman wrote:
On Tue, Jul 08, 2003 at 01:05:18PM -0400 or thereabouts, Michael E. Mercer wrote:
On Tue, 2003-07-08 at 12:11, Joshua Oreman
On Wed, Jul 09, 2003 at 04:38:09PM -0400 or thereabouts, Michael E. Mercer wrote:
Josh,
Is there an easy way to capture this without me having to handwrite all
that info down myself?
Unless you have a serial console, no.
However, some kernel programmer on this list may be able to give a
On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote:
Alrighty then,
Ok, after following FAQ 18.13 on the freebsd web site,
I've been struggling for the last 4 hours trying to get this thing to
dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf
On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote:
On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote:
Alrighty then,
Ok, after following FAQ 18.13 on the freebsd web site,
I've been struggling for the last 4 hours trying to get this thing to
dump core but
Anybody?!?!?!
Hello peoples,
I have posted this before and unfortunately I still have this problem.
During the boot sequence, when it probes for the USB devices, it causes
a kernel panic (page fault) if there is either (or both) a USB mouse
and/or keyboard attached.
If I remove the mouse and
On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote:
Anybody?!?!?!
Hello peoples,
I have posted this before and unfortunately I still have this problem.
During the boot sequence, when it probes for the USB devices, it causes
a kernel panic (page fault) if
Alrighty then,
Ok, after following FAQ 18.13 on the freebsd web site,
I've been struggling for the last 4 hours trying to get this thing to
dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf
and also read about kernel init problems need to have dumpdev added to
the loader. So I
Hello peoples,
I have posted this before and unfortunately I still have this problem.
During the boot sequence, when it probes for the USB devices, it causes
a kernel panic (page fault) if there is either (or both) a USB mouse
and/or keyboard attached.
If I remove the mouse and keyboard and let
Hello peoples,
I have posted this before and unfortunately I still have this problem.
During the boot sequence, when it probes for the USB devices, it causes
a kernel panic (page fault) if there is either (or both) a USB mouse
and/or keyboard attached.
If I remove the mouse and keyboard and let
Hello!
I am use FreeBSD 5.0-RELEASE on Sun Ultra 5.
I want use my Sun Ultra 5 (UltraSparc IIi) as small dial-in server
(two modems on two serial ports). For this I am add to kernel-config
file one string:
device sio
After compile and install kernel, I am reboot. And during boot-time,
kernel
60 matches
Mail list logo