From owner-freebsd-stable@FreeBSD.ORG Thu Dec 9 13:52:15 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC3BD16A4CE for ; Thu, 9 Dec 2004 13:52:15 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B8B243D66 for ; Thu, 9 Dec 2004 13:52:15 +0000 (GMT) (envelope-from michael.schuh@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so610916rng for ; Thu, 09 Dec 2004 05:52:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=IYkfAZhh+B4avXLqjYN2EmHOXdwNa9b+jiMh/uv4v19KQlrIgPOWigRMrJpJ309UAuaDKf+blffDyQuIulfAA+yy9mtv1EBfVj/VYo4tKw1z80kdiZYpP2MI+Bm+WZxgD1bTHsf9eNhPRIiMYNmrh1Ofg5mVnlRHOoH4xETStfY= Received: by 10.38.74.77 with SMTP id w77mr876202rna; Thu, 09 Dec 2004 05:52:14 -0800 (PST) Received: by 10.38.207.71 with HTTP; Thu, 9 Dec 2004 05:52:14 -0800 (PST) Message-ID: <1dbad31504120905523c64367e@mail.gmail.com> Date: Thu, 9 Dec 2004 14:52:14 +0100 From: Michael Schuh To: freebsd-stable@freebsd.org In-Reply-To: <20041209021125.5233216A50C@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <20041209021125.5233216A50C@hub.freebsd.org> Subject: Re:SOLVVED vinum crashes the Box... WRONG POSTING X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Michael Schuh List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 13:52:15 -0000 Hello, sorry for my wrong posting, it was late at night and i have *not* doublechecked my configuration. Sorry for the Trouble. Greetings michael On Thu, 9 Dec 2004 02:11:25 +0000 (GMT), freebsd-stable-request@freebsd.org wrote: > Send freebsd-stable mailing list submissions to > freebsd-stable@freebsd.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > or, via email, send a message with subject or body 'help' to > freebsd-stable-request@freebsd.org >=20 > You can reach the person managing the list at > freebsd-stable-owner@freebsd.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-stable digest..." >=20 > Today's Topics: >=20 > 1. Re: crashdumps not working (Michael Nottebrock) > 2. Re: crashdumps not working (Michael Nottebrock) > 3. vinum crashes the Box by using more then ten disks on > RELENG_4 (Michael Schuh) > 4. Re: crashdumps not working (Robert Watson) > 5. Re: crashdumps not working (Michael Nottebrock) > 6. vinum crashes by using more then 11 disks on RELENG_4 > (Michael Schuh) > 7. Re: crashdumps not working (Michael Nottebrock) > 8. Re: crashdumps not working (Michael Nottebrock) > 9. devfs rules (Ivan Voras) > 10. Re: devfs rules (Ivan Voras) > 11. Re: devfs rules (Michael Nottebrock) > 12. Re: devfs rules (Frank Mayhar) > 13. Re: devfs rules (Frank Mayhar) > 14. Re: crashdumps not working (David Gilbert) > 15. Re: devfs rules (Ivan Voras) > 16. Re: trouble installing 5.3 on soekris net4801 (Lapo Nustrini) > 17. Re: crashdumps not working (Robert Watson) > 18. no internet after build world-kern install (whitevamp) > 19. ULE scheduler broken and not documented (Nuno Teixeira) > 20. Re: ULE scheduler broken and not documented (Ceri Davies) > 21. 5.3R crashing repeateadly (Crist?v?o Dalla Costa) > 22. Re: 5.3R crashing repeateadly (Brooks Davis) > 23. Re: trouble installing 5.3 on soekris net4801 (Crucio) > 24. Re: ULE scheduler broken and not documented (Donald J. O'Neill) > 25. Re: 5.3R crashing repeateadly (Crist?v?o Dalla Costa) > 26. Re: 5.3R crashing repeateadly (Mike Tancsa) > 27. More WRITE_DMA problems on 5.3 (Rob) > 28. Re: crashdumps not working (Greg 'groggy' Lehey) >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Wed, 8 Dec 2004 13:16:46 +0100 > From: Michael Nottebrock > Subject: Re: crashdumps not working > To: Robert Watson > Cc: freebsd-stable@freebsd.org > Message-ID: <200412081316.50578.michaelnottebrock@gmx.net> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On Wednesday, 8. December 2004 12:54, Robert Watson wrote: > > On Wed, 8 Dec 2004, Michael Nottebrock wrote: > > > On Wednesday, 8. December 2004 12:20, Robert Watson wrote: > > > > On Tue, 7 Dec 2004, Michael Nottebrock wrote: > > > > > I recently enabled SW_WATCHDOG in my kernel, but when watchdog > > > > > triggers a panic, no crashdump is taken although dumps are enable= d. > > > > > What could be causing this? > > > > > > > > If you drop to the debugger by using the debug.kdb.enter sysctl, an= d do > > > > "call doadump", followed by a reset, does a dump get generated > > > > successfully? > > > > > > I don't have kdb enabled in my kernel configuration at all... > > > > I'm guessing it might be useful at this point, if possible :-). >=20 > Useful for what exactly? I'm mainly interested in getting this machine to > auto-reboot after a (watchdog-triggered) panic, crashdumps are a bonus. A= t > the moment, it will just hang on a panic (even if I do not enable crashdu= mps > in rc.conf, it won't reset), and since it's usually running X, it will ju= st > stand there while the CRTs burn in. If you think you can get a clue as to= why > it wouldn't crashdump or reset by something I can do in kdb, I will enabl= e > it ... >=20 > > Do you > > have a serial console on the box, or could you set one up? >=20 > Nope, this is the only machine with a keyboard and a monitor attached. >=20 > > > > > > I.e., are they completely broken on your system, or is this > > > > somehow a property of the particular hang you're seeing. > > > > > > See my other mail, a different (non-watchdog) panic didn't trigger a = dump > > > either. I even had the panic message in dmesg: > > > > > > kernel trap 12 with interrupts disabled > > > > > > Fatal trap 12: page fault while in kernel mode > > > fault virtual address =3D 0x14c > > > fault code =3D supervisor write, page not present > > > instruction pointer =3D 0x8:0xc0521397 > > > stack pointer =3D 0x10:0xe9794b84 > > > frame pointer =3D 0x10:0xe9794b90 > > > code segment =3D base 0x0, limit 0xfffff, type 0x1b > > > =3D DPL 0, pres 1, def32 1, gran 1 > > > processor eflags =3D resume, IOPL =3D 0 > > > current process =3D 1281 (beep-media-player) > > > trap number =3D 12 > > > panic: page fault > > > > This is a NULL pointer dereference; you can use addr2line or gdb on you= r > > kernel.debug to turn it into a line number even without a core. That > > might well be worth doing, as we might be able to debug that even witho= ut > > getting dumping working on the box. >=20 > It's a SCHED_ULE + PREEMPTION triggered panic, probably there's no point = in > investigating it at this point, as _ULE has been demoted to abandonware := -(. >=20 > > Syncing on panic is, in general, probably not going to make it work bet= ter > > than not. I guess there's no chance the box has an NMI button? >=20 > Right. I just enabled it for the SW_WATCHDOG experiments (which made me > discover that this machine would just get stuck on panics in the first > place), I already turned it off again. >=20 > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041= 208/0f3ca746/attachment-0001.bin >=20 > ------------------------------ >=20 > Message: 2 > Date: Wed, 8 Dec 2004 13:19:09 +0100 > From: Michael Nottebrock > Subject: Re: crashdumps not working > To: Robert Watson > Cc: freebsd-stable@freebsd.org > Message-ID: <200412081319.10357.michaelnottebrock@gmx.net> > Content-Type: text/plain; charset=3D"iso-8859-15" >=20 > On Wednesday, 8. December 2004 13:16, Michael Nottebrock wrote: >=20 > > > > panic: page fault > > > > > > This is a NULL pointer dereference; you can use addr2line or gdb on y= our > > > kernel.debug to turn it into a line number even without a core. That > > > might well be worth doing, as we might be able to debug that even wit= hout > > > getting dumping working on the box. > > > > It's a SCHED_ULE + PREEMPTION triggered panic, probably there's no poin= t in > > investigating it at this point, as _ULE has been demoted to abandonware > > :-(. >=20 > N.B., I'm running now SCHED_4BSD again. >=20 > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041= 208/a7df61b9/attachment-0001.bin >=20 > ------------------------------ >=20 > Message: 3 > Date: Wed, 8 Dec 2004 13:25:42 +0100 > From: Michael Schuh > Subject: vinum crashes the Box by using more then ten disks on > RELENG_4 > To: freebsd-stable@freebsd.org > Message-ID: <1dbad31504120804251d841790@mail.gmail.com> > Content-Type: text/plain; charset=3DUS-ASCII >=20 > Hi, >=20 > Ihas following System dmesg: >=20 > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1= 994 > The Regents of the University of California. All rights reserv= ed. > FreeBSD 4.10-STABLE #1: Tue Nov 30 14:26:29 CET 2004 > root@pdc.sarcom.de:/usr/obj/usr/src/sys/MYGENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: Intel Pentium III (993.33-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x686 Stepping =3D 6 > Features=3D0x383fbff OV,PAT,PSE36,MMX,FXSR,SSE> > real memory =3D 1342169088 (1310712K bytes) > config> en apm0 > config> q > avail memory =3D 1299566592 (1269108K bytes) > Changing APIC ID for IO APIC #0 from 0 to 2 on chip > Changing APIC ID for IO APIC #1 from 0 to 3 on chip > Programming 16 pins in IOAPIC #0 > Programming 16 pins in IOAPIC #1 > FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 > io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 > Preloaded elf kernel "kernel" at 0xc0564000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc056409c. > Pentium Pro MTRR support enabled > md0: Malloc disk > Using $PIR table, 11 entries at 0xc00fc320 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > IOAPIC #1 intpin 15 -> irq 2 > IOAPIC #1 intpin 1 -> irq 10 > IOAPIC #1 intpin 0 -> irq 11 > pci0: on pcib0 > pcib1: at device 2.= 0 on pci0 > IOAPIC #1 intpin 14 -> irq 13 > pci1: on pcib1 > ahc0: port 0xfc00-0xfcff mem > 0xfcfff000-0xf > cffffff irq 13 at device 6.0 on pci1 > ahc0: port 0xfc00-0xfcff mem 0xfcfff= 000-0xf > cffffff irq 13 at device 6.0 on pci1 > aic7880: Ultra Single Channel A, SCSI Id=3D7, 16/253 SCBs > aac0: mem 0xf4000000-0xf7ffffff irq 2 at device 2.1 = on pci0 > aac0: i960RX 100MHz, 54MB cache memory, no battery support > aac0: Kernel 2.8-0, Build 6089, S/N c10d0 > aac0: Supported Options=3D2558 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec80-0xecff mem > 0xfe103000-0xfe10 > 307f irq 10 at device 4.0 on pci0 > xl0: Ethernet address: 00:10:5a:d0:09:69 > miibus0: on xl0 > xlphy0: <3Com internal media interface> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: port 0xec40-0xec7f mem > 0xfe000000-0xfe0ffff > f,0xfe102000-0xfe102fff irq 11 at device 8.0 on pci0 > fxp0: Ethernet address 00:b0:d0:ab:58:dd > inphy0: on miibus1 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pci0: at 14.0 > isab0: at device 15.0 on pci0 > isa0: on isab0 > ohci0: mem 0xfe100000-0xfe100fff > irq 5 at device > 15.2 on pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > pcib2: on motherboard > IOAPIC #1 intpin 12 -> irq 14 > IOAPIC #1 intpin 8 -> irq 16 > IOAPIC #1 intpin 4 -> irq 17 > pci2: on pcib2 > isp0: port 0xdc00-0xdcff mem > 0xef000000-0xef > 000fff irq 14 at device 6.0 on pci2 > xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0xd880-0xd8ff mem > 0xef001400-0xef00 > 147f irq 16 at device 10.0 on pci2 > xl1: Ethernet address: 00:50:04:ed:af:2f > miibus2: on xl1 > xlphy1: <3Com internal media interface> on miibus2 > miibus2: on xl1 > xlphy1: <3Com internal media interface> on miibus2 > xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl2: <3Com 3c905B-TX Fast Etherlink XL> port 0xd800-0xd87f mem > 0xef001000-0xef00 > 107f irq 17 at device 14.0 on pci2 > xl2: Ethernet address: 00:50:04:53:9e:63 > miibus3: on xl2 > xlphy2: <3Com internal media interface> on miibus3 > xlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > orm0: