Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
Alban Hertroys wrote: > Besides that, it is probably not a very good idea to mirror your swap. I > am certain it is bad for performance, if it'd gain you reliability is > beyond my knowledge. This has been discussed before, you probably want > to check the archives. On the contrary, it is a very good idea indeed to mirror the swap partition if your aim is to make your machine resilient against disk failure. Losing the swap will kill a machine just as dead as losing a filesystem. The performance of a mirrored root drive is a bit slower on write but generally faster on read -- it tends to pretty much even out in the end. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
fOn Sep 25, 2006, at 09:55 , Alban Hertroys wrote:
On Sep 25, 2006, at 8:36, Johan Ström wrote:
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I
have no clue why it
It means exactly that. IIRC kernel dumps are created in swap space
and on the next boot are moved to ${dumpdir}. I'm pretty certain
this is explained nicely in the handbook[1].
Probably is, yes I know what it means, I was just pretty upset at the
moment..;)
AFAIK kernels can only be dumped on real devices, not on virtual
devices like /dev/mirror/*. In that case your setup is not going to
get you any dumps.
In earlier FBSD (6.0 i think?) one got an ioctl error when trying to
dumpon to a gmirror device, but if I dont recall wrong this has been
changed since (I dont get an ioctl error anymore at least...)
Besides that, it is probably not a very good idea to mirror your
swap. I am certain it is bad for performance, if it'd gain you
reliability is beyond my knowledge. This has been discussed before,
you probably want to check the archives.
Performance yes, but I think I've read that it is "best" anyway, if
one of your disks dies, youd dont want to loose half your swap since
that would not be very good if there is anything swapped out to that
disk..
[1] Which I didn't check as I'm about to be in a hurry...
--
Alban Hertroys
Priest to alien: "We want to know, is there a higher
being?".
Alien: "Well, actually that's why we're here,
we're sheer out of virgins".
!DSPAM:259,45178b407241208415560!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
On Sep 25, 2006, at 08:45 , Jiawei Ye wrote:
On 9/25/06, Johan Ström <[EMAIL PROTECTED]> wrote:
Fcking great.. Waking up and noting that the box has rebooted it self
during the night... Yay!!... No kernel dumps, nothing in message
log.. Nada... (this was on the "first" box, that is the one first in
this thread)
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I have
no clue why it crashed at all and if it even did try to dump kernel
or if it just blacked out as when i tried to debug clamd...
--
Johan
It means that the system died and released the sphincter when it did.
If you have dumpdev='AUTO'
dumpdir='/var/crash'
in your rc.conf, then you can find the crash dump in ${dumpdir}, then
you can use kgdb to retrieve the backtrace from the dump.
I got dumpdev="/dev/mirror/gm0s1b", savecore doesnt extract any dumps :/
Jiawei
--
"If it looks like a duck, walks like a duck, and quacks like a duck,
then to the end user it's a duck, and end users have made it pretty
clear they want a duck; whether the duck drinks hot chocolate or
coffee is irrelevant."
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-
[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
On Sep 25, 2006, at 8:36, Johan Ström wrote:
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I have
no clue why it
It means exactly that. IIRC kernel dumps are created in swap space
and on the next boot are moved to ${dumpdir}. I'm pretty certain this
is explained nicely in the handbook[1].
AFAIK kernels can only be dumped on real devices, not on virtual
devices like /dev/mirror/*. In that case your setup is not going to
get you any dumps.
Besides that, it is probably not a very good idea to mirror your
swap. I am certain it is bad for performance, if it'd gain you
reliability is beyond my knowledge. This has been discussed before,
you probably want to check the archives.
[1] Which I didn't check as I'm about to be in a hurry...
--
Alban Hertroys
Priest to alien: "We want to know, is there a higher
being?".
Alien: "Well, actually that's why we're here,
we're sheer out of virgins".
!DSPAM:74,45178b3f7241469027555!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
On 9/25/06, Johan Ström <[EMAIL PROTECTED]> wrote:
Fcking great.. Waking up and noting that the box has rebooted it self
during the night... Yay!!... No kernel dumps, nothing in message
log.. Nada... (this was on the "first" box, that is the one first in
this thread)
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I have
no clue why it crashed at all and if it even did try to dump kernel
or if it just blacked out as when i tried to debug clamd...
--
Johan
It means that the system died and released the sphincter when it did.
If you have dumpdev='AUTO'
dumpdir='/var/crash'
in your rc.conf, then you can find the crash dump in ${dumpdir}, then
you can use kgdb to retrieve the backtrace from the dump.
Jiawei
--
"If it looks like a duck, walks like a duck, and quacks like a duck,
then to the end user it's a duck, and end users have made it pretty
clear they want a duck; whether the duck drinks hot chocolate or
coffee is irrelevant."
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
Fcking great.. Waking up and noting that the box has rebooted it self during the night... Yay!!... No kernel dumps, nothing in message log.. Nada... (this was on the "first" box, that is the one first in this thread) What exactly does kernel dumps on /dev/mirror/gm0s1b mean? Not that it saves any kernel dumps at least.. But otoh I have no clue why it crashed at all and if it even did try to dump kernel or if it just blacked out as when i tried to debug clamd... -- Johan On Sep 24, 2006, at 14:23 , Johan Ström wrote: Okay, I got some problems here now... I'm trying to get clamav's clamd to work.. Failes with an abort in libc: It coredumps directly on start, trace: http://sial.org/pbot/19922 Truss output: www.stromnet.org/~johan/clamd.log Okay...something seems to be f*cked in the nss/ldap stuff.. Anyway,, when running with gdb --args /usr/local/sbin/clamd --debug it works fine!... No coredump or anything, untill i decide to kill clamd.. kill breaks into gdb, and when I run continue to process the signal and let it die, the whole fcking box dies! Screen goes black and reboot.. No panic messages or anything... I have reproduced this two times now on the box in the dmesg in earlier mail... Then i moved the disk to another box pretty similar, same chipset i thikn but not exactly same mobo.. tried the above commands, and bam exactly same problem.. screen just goes black and the box reboots... Dmesg from that box: if i can get the crap up running. now the fs is broken or some shit get this on boot, after started a few services: Starting jails:/usr: bad dir ino 32125198 at offset 512: mangled entry panic: ufs_dirbad: bad dir Uptime: 54s GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed GEOM_MIRROR: Device gm0 destroyed. Cannot dump. No dump device defined. Automatic reboot in 15 seconds... Ok, now i rebooted to singeluser mode and enalbed the dumpdev in rc.conf... , then saw it continune booting and i chcked for the line saying kernel dumps on /dev/mirror/gm0s1b... it was there... and then it booted further and got by the place it crashed before, but a minute later when i try to login to crashes on the same inode... AND STILL!.. it says Cannot dump. No dump device defined... WTF??... brokeness brokeness.. Okay, after some fscking its back up. dmesg from second box which i can crash with clamd...: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE-p7 #0: Wed Sep 20 09:21:41 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ELFI Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2210.09-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Features=0x78bfbffE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> AMD Features=0xe0500800 real memory = 1073676288 (1023 MB) avail memory = 1024299008 (976 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci0: on pcib0 agp0: mem 0xf000-0xf7ff at device 0.0 on pci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfe02f000-0xfe02 irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xfe02e000-0xfe02efff irq 22 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem 0xfe02d000-0xfe02d0ff irq 23 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered nve0: port 0xf000-0xf007 mem 0xfe02c000-0xfe02cfff irq 21 at device 5.0 on pci0 nve0: Ethernet address 00:11:09:c5:fc:9e miibus0: on nve0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:11:09:c5:fc:9e pci0: at device 6.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xdc00-0xdc0f at device 8.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc800-0xc80f, 0xc400-0xc47f irq 23 at device 9.0 on pci0 ata2:
Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
Okay, I got some problems here now... I'm trying to get clamav's clamd to work.. Failes with an abort in libc: It coredumps directly on start, trace: http://sial.org/pbot/19922 Truss output: www.stromnet.org/~johan/clamd.log Okay...something seems to be f*cked in the nss/ldap stuff.. Anyway,, when running with gdb --args /usr/local/sbin/clamd --debug it works fine!... No coredump or anything, untill i decide to kill clamd.. kill breaks into gdb, and when I run continue to process the signal and let it die, the whole fcking box dies! Screen goes black and reboot.. No panic messages or anything... I have reproduced this two times now on the box in the dmesg in earlier mail... Then i moved the disk to another box pretty similar, same chipset i thikn but not exactly same mobo.. tried the above commands, and bam exactly same problem.. screen just goes black and the box reboots... Dmesg from that box: if i can get the crap up running. now the fs is broken or some shit get this on boot, after started a few services: Starting jails:/usr: bad dir ino 32125198 at offset 512: mangled entry panic: ufs_dirbad: bad dir Uptime: 54s GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed GEOM_MIRROR: Device gm0 destroyed. Cannot dump. No dump device defined. Automatic reboot in 15 seconds... Ok, now i rebooted to singeluser mode and enalbed the dumpdev in rc.conf... , then saw it continune booting and i chcked for the line saying kernel dumps on /dev/mirror/gm0s1b... it was there... and then it booted further and got by the place it crashed before, but a minute later when i try to login to crashes on the same inode... AND STILL!.. it says Cannot dump. No dump device defined... WTF??... brokeness brokeness.. Okay, after some fscking its back up. dmesg from second box which i can crash with clamd...: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE-p7 #0: Wed Sep 20 09:21:41 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ELFI Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2210.09-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Features=0x78bfbffMCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> AMD Features=0xe0500800 real memory = 1073676288 (1023 MB) avail memory = 1024299008 (976 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci0: on pcib0 agp0: mem 0xf000-0xf7ff at device 0.0 on pci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfe02f000-0xfe02 irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xfe02e000-0xfe02efff irq 22 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem 0xfe02d000-0xfe02d0ff irq 23 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered nve0: port 0xf000-0xf007 mem 0xfe02c000-0xfe02cfff irq 21 at device 5.0 on pci0 nve0: Ethernet address 00:11:09:c5:fc:9e miibus0: on nve0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:11:09:c5:fc:9e pci0: at device 6.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xdc00-0xdc0f at device 8.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc800-0xc80f, 0xc400-0xc47f irq 23 at device 9.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xb000-0xb00f, 0xac00-0xac7f irq 20 at device 10.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 11.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 14.0 on pci0 pci2: on pcib2 pci2: at device 8.0 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x8800-0x887f mem 0xfdfff000-0xfdfff07f irq 19 at device 9.0 on pci2 miibus1: on xl0 xlphy0: <3Com internal media interface> on
