as
server,
I have loaded the module using kldload and communication between
user and kernel module works fine,
when I try to load the kernel module from loader.conf -
auto load the kernel module at boot up leads to kernel panic
as the file system is not ready and kern_connect fails.
How to notify
between
user and kernel module works fine,
when I try to load the kernel module from loader.conf -
auto load the kernel module at boot up leads to kernel panic
as the file system is not ready and kern_connect fails.
How to notify kernel module that File system is ready?
(any specific event flags
the module using kldload and communication between
user and kernel module works fine,
when I try to load the kernel module from loader.conf -
auto load the kernel module at boot up leads to kernel panic
as the file system is not ready and kern_connect fails.
How to notify kernel module that File
I was going ahead and attempting to install libreoffice 3.5.7 and it was
going along nicely until the kernel panicked. When I rebooted, I tried
to start the install again but it aborted so I went to make clean in
/usr/ports/editors/libreoffice when the kernel panicked again. I have
two of all
Hi All,
I posted a blog yesterday with regards to a FreeBSD kernel panic in
FreeBSD 8.3 at
http://blog.hostileadmin.com/2012/11/05/freebsd-kernel-panic-in-udp_input/
in case anyone has any interest...
--
Take care
Rick Miller
___
freebsd-questions
telecommunication business, yesterday night we experience a strange kernel
panic and our server hanged, just contact collocation as asked for physical
reboot,
in attached, you can find screen shot of rebooting the server . i really thank
full if you take a look and advise me any update.
looking forward
on it and do
telecommunication business, yesterday night we experience a strange
kernel panic and our server hanged, just contact collocation as asked
for physical reboot,
in attached, you can find screen shot of rebooting the server . i
really thank full if you take a look and advise me any
Hi,
I had several kernel panics, and I finally understood that one of memory was
bad. I removed it. But now, each time I try to import my pool, I get a kernel
panic
I'm using freebsd 9.0-release generic
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual
Hi,
On 25 May 2012 20:01:44 -
John Levine jo...@iecc.com wrote:
JL panic: ffs_clusteralloc: map mismatch
JL
JL Something's fairly badly screwed up on your disk. My advice would
JL be to boot from a CD or USB key and run fsck to try to repair it.
the disk was pretty much f...ed up. I
Hi,
as a happy freebsd user since about 2 years I have experienced my first kernel
panic and have no idea what to do.
My main machine crashed an hour ago and since then I can't get it to boot.
The panic message:
panic: ffs_clusteralloc: map mismatch
cpuid = 0
KDB: stack backtrace
#0
panic: ffs_clusteralloc: map mismatch
Something's fairly badly screwed up on your disk. My advice would be
to boot from a CD or USB key and run fsck to try to repair it.
R's,
John
___
freebsd-questions@freebsd.org mailing list
:
Feb 13 08:05:13 snake kernel: panic: handle_written_inodeblock: Invalid
link count 65535 for inodedep 0xfe01d557f000
Feb 13 08:05:13 snake kernel: cpuid = 1
Feb 13 08:05:13 snake kernel: KDB: stack backtrace:
Feb 13 08:05:13 snake kernel: #0 0x808680fe at kdb_backtrace+0x5e
Feb 13 08:05:13
Greetings,
A server of mine kernel panicked and in the serial console it prints non stop
these messages which
are repeated again and again..
KDB: stack backtrace:
#0 0x802fec5e at kdb_backtrace+0x5e
#1 0x80287e57 at hardclock+0x117
#2 0x804610a2 at
or touch them, provoke the
kernel panic and crash. If you mount the file system on a
rescue disk, it crashes that. We've tried mounting on a debian
rescue disk that supported zfs and it didn't crash, but hung.
A coworker ran the debug version of our kernel and it
complained about values being
On Fri, February 10, 2012 11:43 am, Martin McCormick wrote:
Does this sound familiar to anybody? This is the first
zfs installation I have used and I am not real wild about trying
it again if we can't solve this mystery. We can't seem to
duplicate the problem. Any ideas are
You will see a message on this group from Ryan Frederick
who is a coworker of mine and who also posted a question about
this same issue. There was a little confusion about which
FreeBSD support group had been asked so my question and his are
about the same machine. He submitted the stack
I'm attempting to remove a number of old files within a directory that
was rsynced over from another box. However a number of files (old
symlinks and regular files in this instance) cause a kernel panic when
attempting to remove them using rm or unlink.
This is the panic message output:
Fatal
a kernel panic when
attempting to remove them using rm or unlink.
This is the panic message output:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x160
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x81476306
On 31.12.2011 17:05, Bernt Hansson wrote:
Hello list!
FreeBSD FQDN 8.2-STABLE FreeBSD 8.2-STABLE #0: Wed Sep 21 17:29:38 CEST 2011
root@FQDN:/usr/obj/usr/src/sys/DESKTOP amd64
testbox#
If I press enter 4+ times during a cold boot I get a kernel panic.
I call hardware problem. Maybe your
On 8/9/11 10:33 PM, Daryl Sayers wrote:
I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
had a few kernel panics over the last few weeks and would like to capture
a core dump. I have added the following to /etc/rc.conf
dumpdev=AUTO
dumpdir=/var/crash
The
On 8/9/11 10:33 PM, Daryl Sayers wrote:
I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
had a few kernel panics over the last few weeks and would like to capture
a core dump. I have added the following to /etc/rc.conf
dumpdev=AUTO
dumpdir=/var/crash
The
I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
had a few kernel panics over the last few weeks and would like to capture
a core dump. I have added the following to /etc/rc.conf
dumpdev=AUTO
dumpdir=/var/crash
The /var/crash is a 5G filesystem (with 4.8G free).
When the
hey folks,
i have a problem related to a fresh-installed freebsd8.2-server,
acting as host for 7 jails(mysql, apache, solr, ...).
we are using AMD64 / GENERIC at the moment.
this kind of kernel-panic occurs from time to time(about once a month,
no regular basis
I just pressed the power button on my desktop computer - it seemed
like it was attempting to do an ACPI suspend instead of a power down
like I expected - but I'm not sure.
Either way:
When It got close to the end
I got
Kernel trap 12: page fault in kernel mode
followed by the fault address,
On 12/10/10 14:47, Eitan Adler wrote:
I just pressed the power button on my desktop computer - it seemed
like it was attempting to do an ACPI suspend instead of a power down
like I expected - but I'm not sure.
Either way:
When It got close to the end
I got
Kernel trap 12: page fault in kernel
was spent with options by default (ACPI ON) as at ACPI OFF, the system
isn't loaded in general on this notebook (into networks there were similar
cases on this model laptop). Drops out too kernel panic at loading if it is
necessary - then I will write log.
Any thoughts to solve this problem?
best
Hi everyone!
I followed tut at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ to install
FreeBSD Root on ZFS using GPT on my VMWARE virtual machine.
When I go to step Install FreeBSD to zroot kernel-panic appeared!
My virtual machine detail:
RAM: 512MB HDD: 10GB vmware workstation: 7.1.0 build
kernel-panic appeared!
It sounds like you are either low on ram, or are using i386. Look at
http://wiki.freebsd.org/ZFSTuningGuide and follow the steps here in the loader
prompt on the live system, and also add the same options to your loader.conf
when you install the system.
My virtual
that it was
fix in a r200768 now it is clear that i do not know that that code means
(in my eyes it's a bsd build or smth) but i'm currently running the latest
8.0-RELEASE-p3 available. Please advise on how to patch the kernel panic.
___
freebsd-questions@freebsd.org
the fix. Giovanni Trematerra gave a response that it was
fix in a r200768 now it is clear that i do not know that that code means
(in my eyes it's a bsd build or smth) but i'm currently running the latest
8.0-RELEASE-p3 available. Please advise on how to patch the kernel panic.
r200768 uniquely
How can I enforce this? Presently the system just hangs.
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
-Original Message-
From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
questi...@freebsd.org] On Behalf Of Paul Halliday
Sent: Tuesday, April 13, 2010 3:17 PM
To: questi...@freebsd.org
Subject: Force reboot after kernel panic.
How can I enforce this? Presently
in /boot/loader.conf. When I
rebooted I got a kernel panic.
Should this be considerd normal or is it something I should report?
Secondly I see there'a a reference to the lagg(4) man page. I think it
would help future readers of the above page if a comment about loading
if_lagg_load=YES
I have set upp aggregation of my wlan and and wired NIC following the
instructions in the handbook.
http://www.freebsd.org/doc/handbook/network-aggregation.html
I forgot to add the if_lagg_load=YES in /boot/loader.conf. When I
rebooted I got a kernel panic.
Should this be considerd normal
Leslie Jensen wrote:
I have set upp aggregation of my wlan and and wired NIC following the
instructions in the handbook.
http://www.freebsd.org/doc/handbook/network-aggregation.html
I forgot to add the if_lagg_load=YES in /boot/loader.conf. When I
rebooted I got a kernel panic.
Should
. When I
rebooted I got a kernel panic.
Should this be considerd normal or is it something I should report?
No, it's not normal. Please, report it in an explicit way, commands
given and/or changes to rc.conf, loader.conf etc. Try first here
questions@ and then n...@.
Nonetheless I see
it causes a kernel panic?
If that's the case, you should report it to n...@. If you
could include a backtrace of the panic, it would be most helpful.
I have if_lagg_load=YES in /boot/loader.conf
and the following in /etc/rc.conf
wpa_supplicant_enable=YES
ifconfig_em0=up
# ifconfig_iwn0=ether
Hi folks.
I updated my server from 7.0 to 7.2 over the Christmas period (sources
updated to 26th Dec I think).
I have long suspected there was an issue with a hard drive in the server
but the hosts told me that the useless messages logged by 7.0 were
normal. Well it turns out one of the
It's a little difficult to tell from the lack of info you've provided,
but I'd assume you're running a release to which the patch has not
been applied. To do this, you'd need to upgrade to 7-STABLE,
8-RELEASE, or 8-STABLE. CURRENT would work too, but that's not really
a candidate for
On Tue, Jan 5, 2010 at 3:59 PM, Colin Waring
free...@southportcomputers.co.uk wrote:
My supfile uses the tag
*default release=cvs tag=RELENG_7_2
The docs on stable say to use RELENG_7 for which I assumed was out of date
with the docs not always being updated frequently. Is there a different
You may wish to check and see if your firmware is up-to-date on all of your
disk drives, and your controller.
On Mon, Dec 21, 2009 at 10:40:10PM +0200, Alex thus spake:
Dear John,
Any progress for bellow?
I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512
It's not RAID, but
On Tue, Dec 22, 2009 at 11:52 AM, Jason jhelf...@e-e.com wrote:
=
Any progress for bellow?
I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512
It's not RAID, but when copying to HDD:
LOG---
ad6:FAILURE - device detached
Dear John,
Any progress for bellow?
I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512
It's not RAID, but when copying to HDD:
LOG---
ad6:FAILURE - device detached
g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6
/usr: got error 6
Здравствуйте, Freebsd-questions.
Fatal trap 18: integer divide fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0xc0af79b5
stack pointer = 0x28:0xc1b55cb8
frame pointer = 0x28:0xc1b55cb8
code segment= base 0x0, limit 0xf, type
Здравствуйте, Mel.
Вы писали 12 августа 2009 г., 19:59:39:
MF On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote:
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
Aug 12 15:59:08 host savecore: writing core to vmcore.4
How to obtain which process cause system
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
Aug 12 15:59:08 host savecore: writing core to vmcore.4
How to obtain which process cause system to reboot?
--
С уважением,
Коньков mailto:kes-...@yandex.ru
On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote:
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
Aug 12 15:59:08 host savecore: writing core to vmcore.4
How to obtain which process cause system to reboot?
kgdb /boot/kernel/kernel /var/crash/vmcore.4
--
Mel
The FreeBSD Developers' Handbook describes how to get panic information (and
dig out further details).
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN
Was there any output before ad7: FAILURE - device detached? Losing the drive
in the
Hi guys,
I use mount_smbfs on my notebook and I have a little nasty problem..
Sometimes I have kernel panic when resuming after the suspend. The
issue seems to happen when I go to suspend with my USB network (WiFi)
adapter plugged in (I do use /etc/rc.d/netif stop rum0 before going
to suspend
,
at least. But I'm hesitant to just 'call it good' - I'd like this to
be a stable server (:
I manually transcribed the bulk of the output - is there a nicer way
to get the output of a kernel panic so I can copy/paste?
I didn't find an obvious command, though I'm no FreeBSD guru. If
someone could tell me
...
# mount -t xfs -o ro /dev/ad0s2 /mnt
# ls /mnt
# cp /mnt/my_file /home/zbigniew
I forgot add here that I do then
# umount /mnt
and after that was kernel panic.
I'm sorry for the mistake.
Zbigniew
___
freebsd-questions@freebsd.org mailing list
Hello,
I have a Dabian 5.0 and FreeBSD 7.2-RELEASE-p2 on i386 athlon-xp. I have two
partitions under Debian. They are xfs file system.
So I mount it from FreeBSD
# mount -t xfs -o ro /dev/ad0s1 /mnt
# ls /mnt
# umount /mnt
Everything is OK, but now I do the following
# mount -t xfs -o ro
On Friday 22 May 2009 05:30:42 Shawn Badger wrote:
Hi, I installed FreeBSD 7.2 Release on a mini nettop (Intel
Atom/945gc/ICH7 hardware), and everything seemed to go smoothly.
However, when I boot the system and the filesystem checks have been
going for awhile, it always ends in a panic.
Hi, I installed FreeBSD 7.2 Release on a mini nettop (Intel
Atom/945gc/ICH7 hardware), and everything seemed to go smoothly.
However, when I boot the system and the filesystem checks have been
going for awhile, it always ends in a panic. Here's the dump:
dev = ad4s1f, block = 1, fs = /usr
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives.
Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system
corruption when attempting to burn a cd using the burncd utility. I can
avoid this easily enough by using cdrecord and growisofs which work
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives.
Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system
corruption when attempting to burn a cd using the burncd utility. I can
avoid this easily enough by using cdrecord and growisofs which work
prefer a simple error message and not a
kernel panic, I can change the disk with a hotspare remotely. Impossible
when the server is down.
Big thanks,
Jan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
I had just closed Firefox 3 and went to open the Thunar file manager
from XFCE and my machine locked up. After ~20 seconds, it rebooted,
leaving a 310MB vmcore.0 in /var/crash along with a bounds and info.0
file.
I have no idea how to investigate these problems, so please excuse the
ignorance
Hi,
7.1-RELEASE installs fine on the machine, but when I try to start
xorg I get kernel page fault.
it's Intel G45 GMA-4500HD. I saw a thread back in September 2008 that
added support for the G45 chipset, did it make its way into the 7.1
release?
Thanks,
Howard
[long number] too short/too long appear
for several minutes. When /stand/sysinstall running as init on vty0
is finally reached, more of the messages appear. Finally, sysinstall
is started, but keyboard response is very slow. After, a few minutes
a kernel panic occurs spin lock held too long
Peter Jeremy peterjer...@optushome.com.au writes:
Kamlesh Patel shilp.ka...@yahoo.com writes:
How do i recover the system from this error. I can't reload the
loader.old
If you press any key during the first spinner [...] You can then
enter the name of the program you wish to run - eg
On Mon, Jan 12, 2009 at 6:50 AM, Dag-Erling Smørgrav d...@des.no wrote:
Peter Jeremy peterjer...@optushome.com.au writes:
Kamlesh Patel shilp.ka...@yahoo.com writes:
How do i recover the system from this error. I can't reload the
loader.old
If you press any key during the first spinner
Garrett Cooper yanef...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
Peter Jeremy peterjer...@optushome.com.au writes:
If you press any key during the first spinner [...] You can then
enter the name of the program you wish to run - eg /boot/loader.old
That won't work - he
On 2009-Jan-09 00:05:47 -0800, Kamlesh Patel shilp.ka...@yahoo.com wrote:
How do i recover the system from this error. I can't reload the loader.old
If you press any key during the first spinner, you should get a prompt
similar to the following:
FreeBSD/i386 BOOT
Default: 0:ad(0,a)/boot/loader
Kamlesh Patel shilp.ka...@yahoo.com writes:
Hi there,
I changed the following file of FreeBSD 7.0:
sys/boot/forth/beastie.4th
variable rebootkey
variable mykey (added line)
I built and installed kernel, then i reboot the system, it gives me the
following error:
Hi there,
I changed the following file of FreeBSD 7.0:
sys/boot/forth/beastie.4th
variable rebootkey
variable mykey (added line)
I built and installed kernel, then i reboot the system, it gives me the
following error:
---
panic: free:
Update of kernel panic.
Rebuilt kernel without 80211node, seems to have cured the panics.
Removed all wireless support for now.
Thanks to Toni Schmidbauer
--- On Thu, 1/1/09, Mark Busby redt...@sbcglobal.net wrote:
From: Mark Busby redt...@sbcglobal.net
Subject: kernel panic
To: help help
At Thu, 1 Jan 2009 12:05:25 -0800 (PST),
Mark Busby wrote:
Jan 1 08:56:39 mars savecore: reboot after panic: kmem_malloc(12288):
kmem_map too small: 128778240 total allocated
as you probably already know this means you ran out of kernel memory.
80211node 8081 21705K - 8081
I've had a few panics. Attached are the output from vmsat -m then -z.
uname -a
FreeBSD mars.sbcglobal.net 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 24
23:03:01 CST 2008 box...@mars.sbcglobal.net:/usr/src/sys/i386/compile/MARS
i386
Jan 1 08:56:39 mars savecore: reboot after
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
Hello all, I keep getting a kernel panic every Saturday night, so I
figured I would go through the core dump.
# uname -a
FreeBSD xx.fsklaw.com 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Wed Apr 23
08:01:10 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST amd64
# kgdb kernel.symbols /var
Thanks, that took care of it.
On Wed, Oct 1, 2008 at 4:49 PM, Manolis Kiagias [EMAIL PROTECTED] wrote:
Walter Venable wrote:
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical memory: 1971 MB
dumping 78MB: 63 47 31 15
The system then immediately reboots, and hits the panic, reboots, etc.
What can I do??
Walter Venable wrote:
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical memory: 1971 MB
dumping 78MB: 63 47 31 15
The system then immediately reboots, and hits the panic, reboots,
Hey folks,
First, please 'reply-all' as I'm not on the list.
I've got a backup server that, every night, offloads things to a
secondary, USB attached hard disk. We've got two of these disks,
which we rotate so as to have a fairly recent off-site version, in the
event of a disaster. One
Eric Crist wrote:
Hey folks,
First, please 'reply-all' as I'm not on the list.
I've got a backup server that, every night, offloads things to a
secondary, USB attached hard disk. We've got two of these disks, which
we rotate so as to have a fairly recent off-site version, in the event
of a
I get a kernel panic whenever I connect my digital camera (Olympus
C-2040Z) on my 7.0 system. It looks like a rev. 7 related problem,
everything works fine on the same PC if I boot into rev. 6.3.
This might already be covered by PR usb/117313: [umass] [panic] panic on
usb camera
, IOPL = 0
Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41
,
gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags =
interrupt enabled, resume, IOPL = 0
Jun 12 23:02:41 UnixBox2 kernel: current process= 925
(cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined.
This is a regular occurrence, but varies by source. Brand new fBSD 6.3
machine
process= 1385 (cp)
Jun 13 14:32:21 UnixBox2 kernel: trap number= 12
Jun 13 14:32:21 UnixBox2 kernel: panic: page fault
Jun 13 14:32:21 UnixBox2 kernel: cpuid = 1
Jun 13 14:32:21 UnixBox2 kernel: Uptime: 4h54m13s
Jun 13 14:32:21 UnixBox2 kernel: Cannot dump. No dump
= interrupt
enabled, resume, IOPL = 0
Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime
process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device
: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device
I'm sure. I could get different RAM this weekend, but that just makes me
angry. I bought all the items from recommended lists on NewEgg two weeks
ago. This is probably the 11th crash in 12 days.
It's quite likely to be due to bad hardware though.
Kris
[Don't top-post, please.]
It's quite likely to be due to bad hardware though.
Ryan Coleman [EMAIL PROTECTED] writes:
I'm sure. I could get different RAM this weekend, but that just makes
me angry. I bought all the items from recommended lists on NewEgg two
weeks ago. This is probably the
:41 UnixBox2 kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel: Cannot
Hello All,
Last week, one half of my dual port Qlogic fibre channel interface
started causing a page fault panic while probing the second port at
boot time.
I was able to get the system back up by disabling the BIOS on the
second port. The system still sees the 2nd port, but politely
Greg Himes wrote:
Hello All,
Last week, one half of my dual port Qlogic fibre channel interface
started causing a page fault panic while probing the second port at boot
time.
I was able to get the system back up by disabling the BIOS on the
second port. The system still sees the 2nd port,
with backtrace, it looks like:
[EMAIL PROTECTED] STORAGE kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free
since i activate ataidle i have this errors:
ad8: FAILURE - WRITE_DMA48 timed out LBA=314770799
+ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=12207
+ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing
request directly
after disable it, this messages are gone.
so
At Tue, 20 May 2008 07:59:19 +0200,
Thomas Herzog wrote:
cat /var/crash/info.1
follow this guide:
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
and post the results. if nobody answers, open a pr (problem report)
http://www.freebsd.org/send-pr.html
hth,
toni
--
hi,
[EMAIL PROTECTED] STORAGE kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU
Hi,
ich have the second core since 3 days, with following info:
cat /var/crash/info.1
Dump header from device /dev/da0s1b
Architecture: amd64
Architecture Version: 2
Dump Length: 284737536B (271 MB)
Blocksize: 512
Dumptime: Mon May 19 09:27:46 2008
Hostname: xxx.yyy.zz
Magic:
On Monday 12 of May 2008 22:22:12 Roland Smith wrote:
It might also be a hardware problem. Testing the RAM would be a good
place to start.
I bought new RAM and tested it with 'memtest' and now is OK (no error was
found). Hover I still got kernel panic when I do:
# Xorg -configure
# Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote:
It might also be a hardware problem. Testing the RAM would be a good
place to start.
Yes. You are right. I tested my memory with 'memtest' and got one error:
Tst Pass Failing AddressGood BadErr-Bits Count
50
Hello!
I decide to go on FreeBSD 7.0-RELEASE. Before I used 6.3-RELEASE.
But now I cannot get working Xorg. I almost get the kernel panic.
I install fresh 7.0-RELEASE and update ports by portsnam and everything
compiled by ports system. After instalign 'xorg' ports I do the following
steps
On Mon, May 12, 2008 at 12:51:26PM +0200, Zbigniew Komarnicki wrote:
Hello!
I decide to go on FreeBSD 7.0-RELEASE. Before I used 6.3-RELEASE.
But now I cannot get working Xorg. I almost get the kernel panic.
I install fresh 7.0-RELEASE and update ports by portsnam and everything
compiled
- minimal
system. Next I used portsnap to download ports:
portsnap fetch
[...]
Then go to /usr/ports/x11/xorg and:
make install clean
After that, when I log as normal user and typed:
startx
got the first kernel panic. Then I used:
Xorg -configure
X -config /root/xorg.conf.new
and again I got kernel
-bootonly.iso
Then burn on CD and then install fresh 7.0-RELEASE on hard disk - minimal
system. Next I used portsnap to download ports:
portsnap fetch
[...]
Did you do a 'portsnap extract' as well? Fetching alone isn't enough.
got the first kernel panic. Then I used:
Xorg -configure
X -config
1 - 100 of 392 matches
Mail list logo
