On Mon, Apr 01, 2013 at 09:29:46AM -0700, Xin Li wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 4/1/13 5:25 AM, Jeremy Chadwick wrote:
On Mon, Apr 01, 2013 at 05:45:48AM -0400, Ryan McIntosh wrote:
I can confirm that works as intended. I appreciate the prompt
response and it
I had to get some sleep lol. Yes Jeremy, I do completely understand that
and likewise FreeBSD was unusable without any type of semi-hack fix, let
alone fixing it properly, as without msix the system was pretty slow. If
you'd like access or are up for trying to fix the driver I'm all for being
a
On Wed, 6 Feb 2013 14:02:44 +0100
Jens Jahnke jan0...@gmx.net wrote:
JJ On Wed, 06 Feb 2013 14:40:47 +0200
JJ Andriy Gapon a...@freebsd.org wrote:
JJ
JJ AG error 6 is ENXIO, which usually corresponds to a disappearing
JJ AG device or some such. Do you get anything in logs (or other
JJ AG
Hi,
recently I've switched from 8.3 to 9.1 on my home box and are quite
pleased but occasionally I get a kernel panic like this:
Feb 5 19:55:45 magni kernel: /dev: got error 6 while accessing filesystem
Feb 5 19:55:45 magni kernel: panic: softdep_deallocate_dependencies:
unrecovered I/O error
on 06/02/2013 10:29 Jens Jahnke said the following:
Hi,
recently I've switched from 8.3 to 9.1 on my home box and are quite pleased
but occasionally I get a kernel panic like this:
Feb 5 19:55:45 magni kernel: /dev: got error 6 while accessing filesystem
Feb 5 19:55:45 magni kernel
On Wed, 06 Feb 2013 14:40:47 +0200
Andriy Gapon a...@freebsd.org wrote:
AG error 6 is ENXIO, which usually corresponds to a disappearing
AG device or some such. Do you get anything in logs (or other
AG objective experience) that could look like that?
Nothing found so far. System ran stable for
On 1/20/13 6:07 PM, Willem Jan Withagen wrote:
On 17-1-2013 4:18, Ian Lepore wrote:
On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs?
Sami
From src/sys/conf/NOTES
in advance
Sami
בתאריך 20 בינו 2013 16:07, מאת Willem Jan Withagen w...@digiware.nl:
On 17-1-2013 4:18, Ian Lepore wrote:
On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs
On 17-1-2013 4:18, Ian Lepore wrote:
On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs?
Sami
From src/sys/conf/NOTES, this may be what you're looking for...
#
# Don't
16, 2013 2:25:33 pm Sami Halabi wrote:
Hi everyone,
I have a production box, in which I want to install new kernel
without
any
remotd kvn.
my problem is its 2 hours away, and if a kernel panic occurs I got a
problem.
I woner if I can seg failsafe script to load
On Wednesday, January 16, 2013 4:27:53 pm Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs?
Unless you've added DDB and KDB to your kernel it will reboot by default
on a panic. Stable kernel configs also
Hi everyone,
I have a production box, in which I want to install new kernel without any
remotd kvn.
my problem is its 2 hours away, and if a kernel panic occurs I got a
problem.
I woner if I can seg failsafe script to load the old kernel in case of
psnic.
Sami
On Wednesday, January 16, 2013 2:25:33 pm Sami Halabi wrote:
Hi everyone,
I have a production box, in which I want to install new kernel without any
remotd kvn.
my problem is its 2 hours away, and if a kernel panic occurs I got a
problem.
I woner if I can seg failsafe script to load the old
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs?
Sami
On Wed, Jan 16, 2013 at 10:13 PM, John Baldwin j...@freebsd.org wrote:
On Wednesday, January 16, 2013 2:25:33 pm Sami Halabi wrote:
Hi everyone,
I have a production box
On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs?
Sami
From src/sys/conf/NOTES, this may be what you're looking for...
#
# Don't enter the debugger for a panic. Intended
Its only a kernel option? There is no flag to pass to the loader?
SAMI
בתאריך 17 בינו 2013 05:18, מאת Ian Lepore i...@freebsd.org:
On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic
:18, מאת Ian Lepore i...@freebsd.org:
On Wed, 2013-01-16 at 23:27 +0200, Sami Halabi wrote:
Thank you for your response, very helpful.
one question - how do i configure auto-reboot once kernel panic occurs?
Sami
From src/sys/conf/NOTES, this may be what you're looking
to the loader?
~% sysctl -ad | grep panic
kern.stop_scheduler_on_panic: stop scheduler upon entering panic
kern.sync_on_panic: Do a sync before rebooting from a panic
debug.trace_on_panic: Print stack trace on kernel panic
debug.debugger_on_panic: Run debugger on kernel panic
Hello,
When playing a lot Urban Terror, the system panic with ACPI related issues :
Fatal trap 9: general protection fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer = 0x20:0x802c6f15
stack pointer = 0x28:0xff80d89ac6c0
frame pointer =
Hi,
Please file a PR? We can bump it to the ACPI person who has been
busily making this stuff updated and stable.
Thanks!
Adrian
On 24 December 2012 05:52, David Demelier demelier.da...@gmail.com wrote:
Hello,
When playing a lot Urban Terror, the system panic with ACPI related issues :
Hello :-)
After days of problem with my system storage (?) I think I have located the
issue, or at least I am able to reproduce it, please take a look at
attached picture (photo of a crash).
http://i45.tinypic.com/23qtcx.jpg
At first I thought that was the Ext2 filesystem issue, but then I have
This problem was caused by corrupted UFS2-SU+J (9.x default) filesystem
marked as clean where journal showed no issues, running fsck -t ufs -fy
solved the issue!
http://i47.tinypic.com/35m1qxk.jpg
I guess filesystem related kernel panic should enforce full filesystem
chceck (some filesystem flag
kernel panic in FreeBSD 8.3:
I'm not seeing how bd_sbuf would be NULL here. Any ideas?
Since I've not had any replies, I hope nobody minds if I reply with more
information.
This panic seems to be occasionally triggered now that my user land code is
changing the packet filter a while after
, Guy Helmer guy.hel...@gmail.com wrote:
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
I'm not seeing how bd_sbuf would be NULL here. Any ideas?
Since I've not had any replies, I hope nobody minds if I reply with more
information.
This panic seems to be occasionally triggered
On Oct 10, 2012, at 1:37 PM, Alexander V. Chernikov melif...@freebsd.org
wrote:
On 10.10.2012 00:36, Guy Helmer wrote:
On Oct 8, 2012, at 8:09 AM, Guy Helmer guy.hel...@gmail.com wrote:
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
I'm not seeing how bd_sbuf would be NULL
On 10.10.2012 00:36, Guy Helmer wrote:
On Oct 8, 2012, at 8:09 AM, Guy Helmer guy.hel...@gmail.com wrote:
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
I'm not seeing how bd_sbuf would be NULL here. Any ideas?
Since I've not had any replies, I hope nobody minds if I reply
On Oct 8, 2012, at 8:09 AM, Guy Helmer guy.hel...@gmail.com wrote:
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
#0 doadump () at pcpu.h:224
224 __asm(movq %%gs:0,%0 : =r (td));
(kgdb) #0 doadump () at pcpu.h:224
#1 0x804c82e0 in boot (howto=260
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
#0 doadump () at pcpu.h:224
224 __asm(movq %%gs:0,%0 : =r (td));
(kgdb) #0 doadump () at pcpu.h:224
#1 0x804c82e0 in boot (howto=260) at ../../../kern/kern_shutdown.c:441
#2 0x804c8763 in panic (fmt=0x0
Subject: Re: Kernel Panic on 9.0 and 9.1 with carp on BCE network interface
On Thu, Aug 30, 2012 at 02:39:10PM +, Jean-Luc Dupont wrote:
J Sorry, it seems that I didn't put the right backtrace :
J
J #0 doadump (textdump=Variable textdump is not available.
J ) at /usr/src/sys/kern
are connected HBA-1-2-3-4-5 and HBA-5-4-3-2-1.
* I've configured a ZFS on top, with 6 RAID-Z2 arrays of 8+2 disks each.
This setup should be able to survive a disk failure. However, manually
ejecting one of the disks causes a kernel panic. I've manually OCR'd it
below. The panic is not triggered
In article 504f4049.9080...@dest-unreach.be, nio...@dest-unreach.be
writes:
I'm under the illusion that I've found a bug in the FreeBSD kernel, but
since I'm new to FreeBSD, a quiet voice tells me it's probably a case of
you're doing it wrong.
Nope. It's a known bug in the version of
Date: Fri, 7 Sep 2012 17:14:41 +0400
From: gleb...@freebsd.org
To: jl.dup...@outlook.com
CC: freebsd-stable@FreeBSD.org
Subject: Re: Kernel Panic on 9.0 and 9.1 with carp on BCE network interface
On Thu, Aug 30, 2012 at 02:39:10PM +, Jean-Luc Dupont wrote:
J Sorry, it seems that I
On Thu, Aug 30, 2012 at 02:39:10PM +, Jean-Luc Dupont wrote:
J Sorry, it seems that I didn't put the right backtrace :
J
J #0 doadump (textdump=Variable textdump is not available.
J ) at /usr/src/sys/kern/kern_shutdown.c:271
J 271 dumpsys(dumper);
J (kgdb) #0 doadump
Hello,
We are using Freebsd 9.0 on dell poweredge servers with broadcom (bce)
integrated interfaces and intel pci-x cards.
This server is used as gateway/firewall (IPFW) with several VLANs and each
interface and carp for redundancy with another identical server.
We encounter a kernel panic
,
frame=0xff82e97a3c40) at /usr/src/sys/kern/kern_fork.c:992
#23 0x80abdbae in fork_trampoline ()
at /usr/src/sys/amd64/amd64/exception.S:602
From: jl.dup...@outlook.com
To: freebsd-stable@freebsd.org
Date: Thu, 30 Aug 2012 14:33:20 +
Subject: Kernel Panic on 9.0
On Wednesday, August 08, 2012 8:26:56 pm mnln.l4 wrote:
I finally have some time to take a closer look at this issue. Yes, it
is caused by SMI#. DragonflyBSD has tried to fix the similar problem
(see
On Thu, Jul 19, 2012 at 11:36 PM, Olivier Smedts oliv...@gid0.org wrote:
2012/7/19 Greg Bonett g...@bonett.org:
Hello,
I'm experiencing a kernel panic that appears to be caused by zfs.
No errors are making it into /var/log/messages, but here is the error
message that appears on my screen
wrote:
I get a kernel panic at early boot time on 9.0-stable (r237150),
GENERIC,
AMD64.
Repro step:
1. Boot, wait for welcome screen.
2. Repeat pressing Enter key rapidly (so kernel is loading, don't stop
pressing Enter key).
3. See the following message at early boot
So don't
Hi all,
I sent a PR [1] but I decided to also send the problem here.
If you try to destroy a geom_virstor that does not exist, this causes a
kernel panic immediately.
Just try:
gvirstor load
gvirstor destroy tatata
# uname -a
FreeBSD zeus..xxx.br 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE
On Fri, Aug 3, 2012 at 5:06 AM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi all,
I sent a PR [1] but I decided to also send the problem here.
If you try to destroy a geom_virstor that does not exist, this causes a
kernel panic immediately.
Just try:
gvirstor load
gvirstor destroy
Em 03/08/2012 13:49, Jim Harris escreveu:
===
--- sys/geom/virstor/g_virstor.c(revision 238909)
+++ sys/geom/virstor/g_virstor.c(working copy)
@@ -235,6 +235,12 @@
return;
}
On Fri, Aug 3, 2012 at 10:04 AM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi Jim,
When I applied the patch gave this error:
# patch /root/patch.diff
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|---
Em 03/08/2012 14:22, Jim Harris escreveu:
On Fri, Aug 3, 2012 at 10:04 AM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi Jim,
When I applied the patch gave this error:
# patch /root/patch.diff
Hmm... Looks like a unified diff to me...
The text leading up to this was:
Em 03/08/2012 14:22, Jim Harris escreveu:
On Fri, Aug 3, 2012 at 10:04 AM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi Jim,
When I applied the patch gave this error:
# patch /root/patch.diff
Hmm... Looks like a unified diff to me...
The text leading up to this was:
On Fri, Aug 3, 2012 at 1:12 PM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi Jim,
Perfect!!!
# gvirstor destroy tudo
gvirstor: Don't know anything about 'tudo'
Patch applied to head as r239021. I have requested approval from re@
to merge to stable/9.
Thank you for confirming the
Hello,
I'm experiencing a kernel panic that appears to be caused by zfs.
No errors are making it into /var/log/messages, but here is the error
message that appears on my screen after panic (transcribed):
panic solaris assert BSWAP_32(sa_hdr_phys-sa_magic) == SA_MAGIC,
file:
/src/sys/modules
2012/7/19 Greg Bonett g...@bonett.org:
Hello,
I'm experiencing a kernel panic that appears to be caused by zfs.
No errors are making it into /var/log/messages, but here is the error
message that appears on my screen after panic (transcribed):
panic solaris assert BSWAP_32(sa_hdr_phys
User-Agent: All mail clients suck. This one just sucks less.
On Mon, Jun 25, 2012 at 07:34:25AM +0300, mbsd wrote:
Hi stable users.
Hi.
Like this good guy:
http://www.freebsd.org/cgi/query-pr.cgi?pr=159629cat=
I'm bad guy also have kernel panic.
1;2802;0c Maybe it's doesn't matter good
://www.freebsd.org/cgi/query-pr.cgi?pr=159629cat=
I'm bad guy also have kernel panic.
1;2802;0c Maybe it's doesn't matter good or bad gay you are.
It happened first time around Freebsd 9 ~ beta 2 or three. I don't
remember exactly.
All what I have is
?? ~ ??? cat /etc/ipsec.conf
Hi stable users.
Like this good guy:
http://www.freebsd.org/cgi/query-pr.cgi?pr=159629cat=
I'm bad guy also have kernel panic.
Maybe it's doesn't matter good or bad gay you are.
It happened first time around Freebsd 9 ~ beta 2 or three. I don't
remember exactly.
All what I have is
Ξ ~ → cat
Thanks for explaining the cause!
On Tue, Jun 19, 2012 at 4:54 AM, John Baldwin j...@freebsd.org wrote:
On Sunday, June 17, 2012 2:35:14 pm mnln.l4 wrote:
I get a kernel panic at early boot time on 9.0-stable (r237150), GENERIC,
AMD64.
Repro step:
1. Boot, wait for welcome screen.
2
On Sunday, June 17, 2012 2:35:14 pm mnln.l4 wrote:
I get a kernel panic at early boot time on 9.0-stable (r237150), GENERIC,
AMD64.
Repro step:
1. Boot, wait for welcome screen.
2. Repeat pressing Enter key rapidly (so kernel is loading, don't stop
pressing Enter key).
3. See
I get a kernel panic at early boot time on 9.0-stable (r237150), GENERIC,
AMD64.
Repro step:
1. Boot, wait for welcome screen.
2. Repeat pressing Enter key rapidly (so kernel is loading, don't stop
pressing Enter key).
3. See the following message at early boot
*
*
*ACPI APIC Table: ALASKA A M I
On 4/18/2012 6:34 AM, Konstantin Belousov wrote:
So your other core failed to start. You might try a lack posting exact
model/bios version of the machine and mainboard. But indeed, this is
most often BIOS bugs. Sometimes in the strange areas like USB, e.g.
SMI handler for emulating legacy PS/2
On Wed, Apr 18, 2012 at 12:24:17AM -0400, Chad C wrote:
Updated the mainboard UEFI to latest version but am still getting the
same kernel page fault.
I compiled options DDB and options GDB into the generic kernel.
After rebooting and entering DDB I get the following from various commands:
Hello,
I posted to the FreeBSD forum and was told to seek help on the stable
mailing list. I recently build a new system and attempted to install
FreeBSD 9 amd64 using the dvd. Shortly after the boot loader menu while
the kernel attempts to detect the processor cores I receive a kernel
On Apr 18, 2012 2:23 AM, Chad C c...@psys.us wrote:
The first suggestion from a forum poster was bad memory but I swapped out
the memory and still received the panics. Also tested the memory with
memtest86+ and the bios memory test feature. Both reported no errors. I
finally was able to get
On Tue, Apr 17, 2012 at 12:52:28PM -0400, Chad C wrote:
Hello,
I posted to the FreeBSD forum and was told to seek help on the stable
mailing list. I recently build a new system and attempted to install
FreeBSD 9 amd64 using the dvd. Shortly after the boot loader menu while
the kernel
Updated the mainboard UEFI to latest version but am still getting the
same kernel page fault.
I compiled options DDB and options GDB into the generic kernel.
After rebooting and entering DDB I get the following from various commands:
On bootup I am now getting the following:
real memory =
Hi :)
On Thu, 26 Jan 2012 17:54:30 -0800
Jeremy Chadwick free...@jdc.parodius.com wrote:
I'll also point out, though the OP isn't using snapshots, that it's
confirmed use of snapshots on SU+J can result in a full filesystem hang.
Confirmation is from Kirk McKusick (author of SU and designer
On 01/26/2012 16:40, António Trindade wrote:
Cheers.
I recently updated my system to FreeBSD-9.0 and activated softupdate
journaling for a number of file systems (name /home, /var, /usr).
Since then I have been experiencing kernel panics:
kernel: panic: softdep_sync_buf: Unknown type
experiencing kernel panics:
kernel: panic: softdep_sync_buf: Unknown type jnewblk
Yesterday, Jan 26th, I got 6 (six) automatic reboots due to these kernel
panics.
I have now disabled softupdates journaling in the hope that the panics
disappear.
I am sorry for not providing more
on 03/08/2011 01:39 maestro something said the following:
hm userland and CTF not that I know. I only recompiled the kernel with CTF.
Do I
have to recompile userland (and would that be make world?) If so can i just
pass
the same WITH_CTF=1 option to make?
I _think_ (as in: not sure) that
on 03/08/2011 01:46 maestro something said the following:
What do I have to recompile for the patch to be picked up?
make libproc in /usr/src/lib
Correct way is:
$ cd /usr/src/lib/libproc
$ make obj
$ make depend
$ make
$ make install
--
Andriy Gapon
on 03/08/2011 03:47 maestro something said the following:
now it seems that the ustack() action on i386 and FreeBSD-9.0BETA1 almost
works.
Almost because dtrace still exits (this time without an error message) The
process for which the ustack should be genereated is terminated
Here are the
on 03/08/2011 11:42 Andriy Gapon said the following:
on 03/08/2011 03:47 maestro something said the following:
now it seems that the ustack() action on i386 and FreeBSD-9.0BETA1 almost
works.
Almost because dtrace still exits (this time without an error message) The
process for which the
Hi,
just finished installing FreeBSD-9BETA1 and recompiling the kernel with
dtrace.
This is even worse, I have the same behavior as mentioned here:
http://freebsd.1045724.n5.nabble.com/bin-158431-dtrace-crash-in-dt-proc-lookup-when-attaching-to-PID-assert-dpr-NULL-tt4535367.html#none
i.e.,
Hi,
This is even worse, I have the same behavior as mentioned here:
http://freebsd.1045724.n5.nabble.com/bin-158431-dtrace-crash-in-dt-proc-lookup-when-attaching-to-PID-assert-dpr-NULL-tt4535367.html#none
i.e., dtrace regardless of whether with or without any probes just quits
with the
on 02/08/2011 20:46 maestro something said the following:
Hi,
just finished installing FreeBSD-9BETA1 and recompiling the kernel with
dtrace.
This is even worse, I have the same behavior as mentioned here:
on 03/08/2011 00:03 Andriy Gapon said the following:
I tried to run dtruss (as you did) and I got this pre-amble before the
assertion:
[some dtrace script body]
: probe description proc:::exit does not match any probes
I guess that in my case I got it because my userland was not compiled
Hi,
http://freebsd.1045724.n5.nabble.com/bin-158431-dtrace-crash-in-dt-proc-lookup-when-attaching-to-PID-assert-dpr-NULL-tt4535367.html#none
Kind of a mentoring note: it would be much shorter and much more useful to
paste
PR 158431 or, even better, an http URL to the said PR in FreeBSD PR
Hi,
diff --git a/lib/libproc/proc_create.c b/lib/libproc/proc_create.c
index c372a47..9bd24a2 100644
--- a/lib/libproc/proc_create.c
+++ b/lib/libproc/proc_create.c
@@ -79,12 +79,11 @@ proc_attach(pid_t pid, int flags, struct proc_handle
**pphdl)
else
phdl-status =
On Tue, Aug 2, 2011 at 3:46 PM, maestro something maestr...@gmail.com wrote:
Hi,
diff --git a/lib/libproc/proc_create.c b/lib/libproc/proc_create.c
index c372a47..9bd24a2 100644
--- a/lib/libproc/proc_create.c
+++ b/lib/libproc/proc_create.c
@@ -79,12 +79,11 @@ proc_attach(pid_t pid, int
Hi,
Hi,
diff --git a/lib/libproc/proc_create.c b/lib/libproc/proc_create.c
index c372a47..9bd24a2 100644
--- a/lib/libproc/proc_create.c
+++ b/lib/libproc/proc_create.c
@@ -79,12 +79,11 @@ proc_attach(pid_t pid, int flags, struct proc_handle
**pphdl)
else
Running the same example on amd64 has the same behavior as on i386 (granted
the backtrace is slightly different).
That is, the kernel panics immediately when you use the ustack() action.
Furthermore, the crashdump does not provide the nececcary information to get
at the root of the cause (i.e.,
Hi,
I just tried your test on -STABLE + 1 fix from current [1] and got no trap.
dtrace: buffer size lowered to 2m
CPU IDFUNCTION:NAME
4 42224accept:return nc accept:return
Assertion failed: (dpr != NULL), file
();
}
% dtrace -s test.d
then running
% nc -vl 8080
on one shell and
% nc localhost 8080
on another would make the kernel panic
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
on 30/07/2011 00:27 maestro something said the following:
on 30/07/2011 10:50 Andriy Gapon said the following:
#7 0xc11012d7 in dtrace_panic_trigger () from /boot/kernel/dtrace.ko
Previous frame inner to this frame (corrupt stack?)
(kgdb)
what am I doing wrong and what do I have to do
8080
on another would make the kernel panic
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
then running
% nc -vl 8080
on one shell and
% nc localhost 8080
on another would make the kernel panic
--
Andriy Gapon
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http
then running
% nc -vl 8080
on one shell and
% nc localhost 8080
on another would make the kernel panic
--
Andriy Gapon
--
Andriy Gapon
___
freebsd-stable@freebsd.org
the kernel panic
--
Andriy Gapon
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
On Sat, Jul 30, 2011 at 12:05:33PM -0700, maestro something wrote:
Hi,
Have you started kgdb with the correct kernel and core file?
If yes, then I am out of ideas.
I hope so, I only recompiled the kernel once according to the DTRACE wiki
instructions and I certainly only have one
on 30/07/2011 22:05 maestro something said the following:
fb82i386# cat /etc/make.conf
CFLAGS= -O
(accodring to man make.conf only -O and -O2 is supported for CFLAGS anyways)
kernel.debug is the newly compiled kernel (according to the timestamp)
fb82i386# kgdb kernel.debug
Hi,
On Sat, Jul 30, 2011 at 12:52 PM, Andriy Gapon a...@freebsd.org wrote:
on 30/07/2011 22:05 maestro something said the following:
fb82i386# cat /etc/make.conf
CFLAGS= -O
(accodring to man make.conf only -O and -O2 is supported for CFLAGS
anyways)
kernel.debug is the newly
on 30/07/2011 23:03 maestro something said the following:
(kgdb) list *dtrace_probe+0xfd6
No source file for address 0xc10fa6a6.
Are the sources on the same machine?
This is probably the last idea from me.
--
Andriy Gapon
___
Hi,
on 30/07/2011 23:03 maestro something said the following:
(kgdb) list *dtrace_probe+0xfd6
No source file for address 0xc10fa6a6.
Are the sources on the same machine?
This is probably the last idea from me.
Yes all is done on the same (virtual 32bit) machine. Sources are there too.
Hi,
This is i386, right ?
I think the cause is that assembler routine panic_trigger does not
establish the standard i386 frame. Basically, you need either this,
or dwarf annotations, for gdb to be able to walk over the frame.
You need to add the standard prologue
pushl %ebp
Hi,
This is i386, right ?
I think the cause is that assembler routine panic_trigger does not
establish the standard i386 frame. Basically, you need either this,
or dwarf annotations, for gdb to be able to walk over the frame.
You need to add the standard prologue
pushl %ebp
localhost 8080
on another would make the kernel panic
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
and
% nc localhost 8080
on another would make the kernel panic
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr
Hello,
I have a ZFS raid1 from 2 drives to 1TB WDC WD1001FALS-00E8B0 05.00K05.
Recently, my system OS: FreeBSD 8.2-RELEASE has crashed, with kernel panic:
panic: solaris assert: ss-ss_end = end (0x6a80753600 = 0x6a80753800),
file:
/usr/src/sys/modules/zfs
On Fri, Jun 17, 2011 at 12:32:22PM +0400, Aleksey wrote:
Hello,
[snip]
You posted this issue to freebsd-fs two days ago. Let's continue the
discussion there please?
http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011775.html
--
| Jeremy Chadwickjdc
ok)
2011/6/17 Jeremy Chadwick free...@jdc.parodius.com
On Fri, Jun 17, 2011 at 12:32:22PM +0400, Aleksey wrote:
Hello,
[snip]
You posted this issue to freebsd-fs two days ago. Let's continue the
discussion there please?
Hi all,
The following script seems to cause a guaranteed kernel panic on 8.1-R,
8.2-R and 8-STABLE as of today (2011-03-16), with both ZFS v14/15, and
v28 on 8.2-R with mm@ patches from 2011-03. I suspect it may also affect
9-CURRENT but have not tested this yet.
#!/usr/local/bin/bash
export
On Wednesday, 29 December 2010, jhell jh...@dataix.net wrote:
Another note too, I think I read that you mentioned using the L2ARC and
slog device on the same disk You simply shouldn't do this it could
be contributing to the real cause and there is absolutely no gain in
either sanity or
Hi
On 27 December 2010 16:04, jhell jh...@dataix.net wrote:
1) Set vfs.zfs.recover=1 at the loader prompt (OK set vfs.zfs.recover=1)
2) Boot into single user mode without opensolaris.ko and zfs.ko loaded
3) ( mount -w / ) to make sure you can remove and also write new
zpool.cache as needed.
On 29 December 2010 03:15, Jean-Yves Avenard jyaven...@gmail.com wrote:
# zpool import
load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.11r 0.00u 0.03s 0% 2556k
load: 0.00 cmd: zpool 405 [spa_namespace_lock] 15.94r 0.00u 0.03s 0% 2556k
load: 0.00 cmd: zpool 405 [spa_namespace_lock] 16.57r
On Tue, Dec 28, 2010 at 9:39 AM, Jean-Yves Avenard
Now, I haven't tried using cache and log from a different disk. The
motherboard on the server has 8 SATA ports, and I have no free port to
add another disk. So my only option to have both a log and cache
device in my zfs pool, is to use two
Please don't consider these patches as production-ready.
What we want to do is find and resolve as many bugs as possible.
To help us fix these bugs, a way to reproduce the bug from a clean start
(e.g. in virtualbox) would be great and speed up finding the cause for
the problem.
Your problem
101 - 200 of 649 matches
Mail list logo
