mode program acts 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
On 20.08.2013 11:21, Patrick Lamaiziere wrote:
> Le Fri, 09 Aug 2013 23:06:01 +0200,
> David Demelier a écrit :
>
>> Hello,
>>
>> I can reproduce a panic by just starting a virtual machine with
>> VirtualBox 4.2.16_2.
>>
>> Unfortunately, as the
Le Fri, 09 Aug 2013 23:06:01 +0200,
David Demelier a écrit :
> Hello,
>
> I can reproduce a panic by just starting a virtual machine with
> VirtualBox 4.2.16_2.
>
> Unfortunately, as the kmod driver is not built with debug symbols I
> could not provide much information.
Hello,
I can reproduce a panic by just starting a virtual machine with VirtualBox
4.2.16_2.
Unfortunately, as the kmod driver is not built with debug symbols I could not
provide much information.
Is this problem already reported?
Fatal trap 9: general protection fault while in kernel mode
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
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)
Is
On 14/06/2013 23:33, Ewald Jenisch wrote:
On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote:
Just guessing from what I see -
The panic is "No usable event timer found!"
I did say just guessing and thought someone more knowledgeable may have
spoken by now. One thing
On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote:
> Just guessing from what I see -
>
> The panic is "No usable event timer found!"
>
> .
Hi Shane,
Thanks much for the hints you sent me. Since I'm pretty swamped with
work it took me a couple of day
ering
kern.eventtimer.periodic=1
kern.eventtimer.timer="LAPIC"
and booting the install-DVD with these settings
(I once could boot and older HP-server using these settings, so
I tried them here too)
("FreeBSD-install-crash-HP-Proliant-DL580-G5-04.jpg" shows the actual
panic/st
Hi,
Several days ago I got a HP Proliant DL580 G5 that I wanted to install
FreeBSD 9.1 (64bit) on - till now without any success :-(.
Symptoms: Upon booting off the installation DVD the system freezes
(when running the installation "non-verbose") or installation stops
with a panic foll
Dear Guys;
When we kldload alq module, after that kldunload alq and after that init 0,
system crashes!
we are using FreeBSD 9. Could anybody help in this regard?
thanks in advance
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/ma
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 t
Hi,
My system has been encountering kernel panic every time it accesses
large number of files over NFSv4.
The backtrace left after reboot (I haven't saved the core dump):
Dec 4 17:35:56 freebsd syslogd: kernel boot file is
/boot/kernel/kernel
Dec 4 17:35:56 freebsd kernel: panic:
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
Здравствуйте, FreeBSD.
Fatal double fault:
eip = 0xc0e538e8
esp = 0xc7945004
ebp = 0xc7945c64
cpuid = 3; apic id = 03
panic: double fault
cpuid = 3
KDB: stack backtrace:
#0 0xc0af724f at kdb_backtrace+0x4f
#1 0xc0ac3c4f at panic+0x16f
#2 0xc0e68aab at dblfault_handler+0x9b
Uptime: 17h57m50s
uname -a
FreeBSD newflux 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #4 r239949: Fri Aug 31
16:57:42 EEST 2012 root@newflux:/usr/obj/usr/src/sys/KES_KERN_v9 i386
Fatal double fault:
eip = 0xc0e538e8
esp = 0xc7945004
ebp = 0xc7945c64
cpuid = 3; apic id = 03
panic: double fault
cpuid = 3
KDB: stack
with: FreeBSD/amd64 system compiler
> Thread model: posix
> gcc version 4.2.1 20070831 patched [FreeBSD]
What was the actual panic message/assert that was hit?
Thanks,
-Garrett
PS Please don't cross-post.
___
freebsd-questions@freebsd.org mailing
Looks like my screen shot was stripped. You can find it here:
http://www.pki2.com/hp.JPG
Also:
Granny> cc -v
Using built-in specs.
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070831 patched [FreeBSD]
On Sun, 2012-08
Looks like my screen shot was stripped. You can find it here:
http://www.pki2.com/hp.JPG
Also:
Granny> cc -v
Using built-in specs.
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070831 patched [FreeBSD]
On Sun, 2012-08
I have a number of HP servers and on two of them (so far) I am getting
similar panics on every reboot. I've enclosed a screen shot of one of
the panics.
A common denominator, so far, is both are compiled using the 4.2+ C
compiler and both are CVSUP mirrors. My other HP machines have not yet
shown
application installed 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
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 to
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 vi
Hi,
On 25 May 2012 20:01:44 -
"John Levine" 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 prett
>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 mail
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 backtra
Hi,
Today I have got a panic under the following scenario:
* FreeBSD 9.0-RELEASE in VMWare ESXi virtualized host
* Very busy host (java compilers, NFS server, lot of UFS snapshots)
* apache web server
* pgsql and mysql databases
* GENERIC kernel
The panic happened after:
1- to umount a UFS
On Fri, 27 Apr 2012, Eric Schuele wrote:
All,
I've been using fusefs-ntfs for quite a while with no issues for my ntfs
needs in 8.x
I recently updated to 9.0-RELEASE, and now my machine panics upon
writing to an ntfs mount. I did rebuild all fusefs-ntfs ports after the
upgrade.
Anyone else e
All,
I've been using fusefs-ntfs for quite a while with no issues for my ntfs
needs in 8.x
I recently updated to 9.0-RELEASE, and now my machine panics upon
writing to an ntfs mount. I did rebuild all fusefs-ntfs ports after the
upgrade.
Anyone else experiencing this or similar?
Thanks,
Eric
On 03/09/12 01:45, Dean E. Weimer wrote:
I am having problems with my system panicking and crashing during
Bacula backups. Is there any way short of enabling full memory dumps
to log the output of the crash? After a reboot there is no
information in the messages log, and dmesg generally only
I am having problems with my system panicking and crashing during
Bacula backups. Is there any way short of enabling full memory dumps to
log the output of the crash? After a reboot there is no information in
the messages log, and dmesg generally only shows the information since
the reboot st
ck up:
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:
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 lapic_handle_timer+0xd
cause 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:0x814
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:
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 tr
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 apprecia
delete them 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
comp
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
cYT033775: Losing
./qfp8NCucYT033775: savemail panic
Sep 23 13:56:38 mech-aslap239 sm-mta[33775]: p8NCucYT033775: SYSERR(root):
savemail: cannot save rejected email anywhere
so that I cannot send any mail from it.
I've read this:
http://www.brandonhutchinson.com/savemail_panic_in_Sendmail.html
but it
> 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
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
>
> Th
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 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 th
edu:/usr/obj/usr/src/sys/GENERIC
Panic String: page fault
Dump Parity: 2017522204
Bounds: 0
Dump Status: good
The size of vmcore.0 is 767M. It is probably incomplete.
In /var/log/messages I have:
Jun 8 12:59:31 server savecore: reboot after panic: page fault
Jun 8 12:59:31 server savec
ouble fault" error. This configuration was
working for 32-bit machine very well. I am trying to debug the tmpfs
module.
Panic message on console is:
Fatal double fault
rip = 0x80552be1
rsp = 0x006f5000
rbp = 0x006f5000
cpuid = 0; apic id = 00
panic: do
Hello,
I am having a system panic issue with the Intel D510MO motherboard. It uses
an Intel D510 Atom CPU, that is a hyperthreaded, dual core CPU that supports
Intel 64 Technology. I am using FreeBSD 8.1_RELEASE AMD64 with the GENERIC
kernel, and the system crashes with the following error
On Thu, 2011-01-06 at 17:47 +, Paul Macdonald wrote:
> On 06/01/2011 17:04, Lydia Rowe wrote:
> > cannot save rejected email anywhere
>
> "savemail panics" occur when sendmail is unable to deliver a bounced
> message to the postmaster alias.
> (from googling :)
> http://www.brandonhutchinson
Lydia Rowe wrote:
> Hi!
>
> I'm encountering this most curious error on a fairly new FreeBSD 8
> machine and I'm just not sure where to go with this.
>
> The Error:
> Jan 6 12:56:31 sendmail[1600]: p06HuRGB001600:
> Losing ./qfp06HuRGB001600: savemail pani
On 06/01/2011 17:04, Lydia Rowe wrote:
cannot save rejected email anywhere
"savemail panics" occur when sendmail is unable to deliver a bounced
message to the postmaster alias.
(from googling :)
http://www.brandonhutchinson.com/savemail_panic_in_Sendmail.html
--
-
Pa
Hi!
I'm encountering this most curious error on a fairly new FreeBSD 8
machine and I'm just not sure where to go with this.
The Error:
Jan 6 12:56:31 sendmail[1600]: p06HuRGB001600:
Losing ./qfp06HuRGB001600: savemail panic
Jan 6 12:56:31 sendmail[1600]: p06HuRGB001600: S
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
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, inst
On Wed, 8 Dec 2010 10:58:48 +0300, "K. Yura" wrote:
> I got that error SYSERR(root): savemail: cannot save rejected email anywhere
> Losing ./qfob86....:savemail panic. How can I fix it? Thanks.
See the first line in df -h:
> Filesystem SizeUsed Avail Capacity
%/var
--
I got that error SYSERR(root): savemail: cannot save rejected email anywhere
Losing ./qfob86:savemail panic. How can I fix it? Thanks.
___
freebsd-questions@freebsd.org
5 seconds - press a key on the console to abort or switch
> off the system now
>
> ---
>
> Loading 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
t;Install FreeBSD to zroot" 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 i
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 workstat
On 08/27/10 03:12, Tijl Coosemans wrote:
On Thursday 26 August 2010 05:55:42 Rem P Roberti wrote:
In an attempt to diagnose why my Thinkpad R51 completely locks up when
trying to access X I have done the following. I built a debugging
kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC
On Thursday 26 August 2010 05:55:42 Rem P Roberti wrote:
> In an attempt to diagnose why my Thinkpad R51 completely locks up when
> trying to access X I have done the following. I built a debugging
> kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC in addition
> to *BREAK_TO_DEBUGGER. N
In an attempt to diagnose why my Thinkpad R51 completely locks up
when trying to access X I have done the following. I built a
debugging kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC
in addition to *BREAK_TO_DEBUGGER. None of these things have yielded
any progress in isolating
In an attempt to diagnose why my Thinkpad R51 completely locks up when
trying to access X I have done the following. I built a debugging
kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC in addition
to *BREAK_TO_DEBUGGER. None of these things have yielded any progress
in isolating t
On 02/08/2010 05:59, n dhert wrote:
> Sometimes my FreeBSD8.0-p4 machine does an automatic reboot after
> panic: page fault. (Fatal trap 12: page fault while in kernel mode)
> It's at random times.
> What in general can be the cause of that?
> Is it always due to hardware mem
Sometimes my FreeBSD8.0-p4 machine does an automatic reboot after
panic: page fault. (Fatal trap 12: page fault while in kernel mode)
It's at random times.
What in general can be the cause of that?
Is it always due to hardware memory errors?
What else can be a cause, how to find out ?
I
>but i did not get 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 adv
t 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.
> -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
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"
On Mon, Mar 22, 2010 at 9:28 AM, Paul Halliday wrote:
> I have a couple VM's that randomly halt with this error:
>
> Sleeping thread (tid 10018, pid 1058) owns a non-sleepable lock
> panic: sleeping thread
> cpuid = 0
> Uptime 11h14m31s
> Cannot dump. Device
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 or is it something I should report?
>
>
>
> Secondly I see there'a a reference to the lagg(4) man page. I think it
>
I have a couple VM's that randomly halt with this error:
Sleeping thread (tid 10018, pid 1058) owns a non-sleepable lock
panic: sleeping thread
cpuid = 0
Uptime 11h14m31s
Cannot dump. Device not defined or unavailable.
FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC
n't comment the line 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=&quo
in /boot/loader.conf. 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...@.
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 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.
Shou
I get the message:
panic: No BIOS smap info from loader:
When trying to boot amd64 on my server. It has an Intel s5000vcl board
w/ a 5000v mem controller and 6321esb i/o controller.
I'd really like to move from Debian to FreeBSD on this box, but have not
been able to find a worka
Hello-
I have a server box with an Intel s5000vcl motherboard and 2 dual-core
Xeon procs. I was hoping to run FreeBSD 8 on it, but when I try to boot
the amd64 media I get
panic: No BIOS smap info from loader:
I've Googled about and found chatter relating to the message, but no
work-a
s
>>>>> during this last run
>>>>
>>>> Is that with or without panicking?
>>>>
>>> with a panic
>>>
>>>
>>>> If the system did panic then it looks like the problem is a memory
>>>> leak somewhere else
On Thu, January 14, 2010 08:50, Ivan Voras wrote:
> 2010/1/14 Doug Poland :
>>>>
>>>> kstat.zfs.misc.arcstats.size
>>>>
>>>> seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
>>>> during this last run
>>>
>
I was watching ):
>>>>
>>> I failed to mention that
>>>
>>> kstat.zfs.misc.arcstats.size
>>>
>>> seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
>>> during this last run
>>
>> Is that with or without panicking?
>>
> with a pan
;> kstat.zfs.misc.arcstats.size
>>
>> seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
>> during this last run
>
> Is that with or without panicking?
>
with a panic
> If the system did panic then it looks like the problem is a memory
> leak somewh
with or without panicking? If the system did panic then it looks
like the problem is a memory leak somewhere else in the kernel, which
you could confirm by monitoring vmstat -z.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
>>
>>
> Ok, I re-ran with same config, but this time monitoring the sysctls
> you requested* ( and the rest I was watching ):
>
I failed to mention that
kstat.zfs.misc.arcstats.size
seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
during this last run
--
Regards,
Doug
_
d be very
> helpful if you could monitor the kstat.zfs.misc.arcstats.size sysctl
> while you are doing the tests to document what is happening to the
> system. If it by any chance stays the same you should probably monitor
> "vmstat -m".
>
>
Ok, I re-ran with same config, but this time monit
On Wed, January 13, 2010 13:57, Ivan Voras wrote:
> 2010/1/13 Doug Poland :
>> This is the state of the machine when it panicked this time:
>>
>> panic: kmem_malloc(131072): kmem_map too small: 1296957440 total
>> allocated
>> cpuid = 1
>>
>
at "arc_max" is just a guideline, not a hard
>> limit... the ZFS ARC usage can and will spike to much larger values,
>> usually in the most inopportune moment.
>>
> This is the state of the machine when it panicked this time:
>
> panic: kmem_malloc(131072): kmem_map
can and will spike to much larger values,
> usually in the most inopportune moment.
>
This is the state of the machine when it panicked this time:
panic: kmem_malloc(131072): kmem_map too small: 1296957440 total
allocated
cpuid = 1
/boot/loader.conf: vfs.zfs.arc_max=512M
vfs.numvnodes: 660
2010/1/13 Doug Poland :
>
> On Wed, January 13, 2010 11:55, Ivan Voras wrote:
>> Doug Poland wrote:
>>
>>> So the question is, can ZFS be tuned to not panic or hang no matter
>>> what I throw at it?
>>
>> Apparently not.
>>
>> &
On Wed, January 13, 2010 11:55, Ivan Voras wrote:
> Doug Poland wrote:
>
>> So the question is, can ZFS be tuned to not panic or hang no matter
>> what I throw at it?
>
> Apparently not.
>
> > I began with a system with no tunables in /boot/loader.conf
>
Doug Poland wrote:
So the question is, can ZFS be tuned to not panic or hang no matter
what I throw at it?
Apparently not.
> I began with a system with no tunables in /boot/loader.conf
> (vm.kmem_size and vm.kmem_size_max). Then I tried increasing
> vm.kmem_size and vm.kmem_size_ma
exhaustion, until I
used the 4GB settings. At that time, the system system became
unresponsive and had to be reset.
So the question is, can ZFS be tuned to not panic or hang no matter
what I throw at it? In this case, it's the ancient and innocuous
unixbench utility.
This is a test box ri
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 dif
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 pro
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 drive
ad6:FAILURE - device detached
>> g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6
>> /usr: got error 6 while accessing filesystem
>> panic: softdep_deallocate_dependencies: unrecovered I/O error
>> cpuid = 0
>> Uptime: 2m18s
>> Physical me
, 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 while accessing filesystem
panic: softdep_deallocate_dependencies: unrecovered I/O error
cpuid = 0
Uptime: 2m18s
Physical m
ror 6 while accessing filesystem
panic: softdep_deallocate_dependencies: unrecovered I/O error
cpuid = 0
Uptime: 2m18s
Physical memory: 243 MB
Dumping 58 MB:unknown: timeout waiting to issue command
unknown: error issuing WRITE_DMA command
** DUMP FAILED (ERROR 5) **
Automatic reboot in 15 se
Bas Smeelen wrote:
So basically it would be advisable to recommend to look in the vmkernel
and san logs around the same timestamps as I see this happening in the
FreeBSD guest?
Yes, try that.
___
freebsd-questions@freebsd.org mailing list
http://lis
>> vmware environments, but never encountered these type of errors before.
>> There is no filesystem corruption after these messages or after the
>> panic mentioned in the subject. This situation is now happening
>> approximately once every six weeks.
>
> I have a numbe
error = 5
I have been running FreeBSD for a long time on real hardware and in
vmware environments, but never encountered these type of errors before.
There is no filesystem corruption after these messages or after the
panic mentioned in the subject. This situation is now happening
approximately once
1 - 100 of 1049 matches
Mail list logo
