Re: LOR: ufs vs bufwait
On 2010-May-08 12:20:05 +0200, Ulrich Spörlein u...@spoerlein.net wrote: This LOR also is not yet listed on the LOR page, so I guess it's rather new. I do use SUJ. lock order reversal: 1st 0xc48388d8 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:502 2nd 0xec0fe304 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_softdep.c:11363 3rd 0xc49e56b8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2091 I'm seeing exactly the same LOR (and subsequent deadlock) on a recent -current without SUJ. -- Peter Jeremy pgpMf1YAwM1mI.pgp Description: PGP signature
Re: SC_PIXEL_MODE in GENERIC on i386/amd64?
08.05.2010 20:31, Anonymous пишет: - jfbterm - boot splash - apps that use libvgl (e.g. mplayer) - other uses for graphic modes Is there a way to avoid recompiling kernel just to use them? may be need include SC_PIXEL_MODE into GENERIC for amd64 and i386? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
During transition to multi-user mode on first reboot after upgrading from r207812 - r207844; from the sserial console: 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 0 3 @DY GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #154 r207844: Mon May 10 06:03:54 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3614.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 uart0: 16550 or compatible port 0x3f8-0x3ff irq 4
Re: kmem_map too small: 3832475648 total allocated
On Friday 30 April 2010 09:11:49 Gary Jennejohn wrote: A number of variables go into calculating vm.kmem_size (see kmeminit() in kern_malloc.c). In the end, the kernel won't allocate more than twice the physical memory size _which it has discovered_. The question is, how much of your physical memory does the kernel actually see? It would appear that the maximum value for vm.kmem_size is twice the amount of avail memory - as opposed to the real memory. I have 6GB installed; 6144MB gets detected but only 5873MB is available. Setting vm.kmem_size to 12G fails but 10G works. -- Bruce Cran ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote: ... You don't happen to have a backtrace? Oops -- sorry; got caught up in getting ready to head in to work: db bt Tracing pid 20 tid 100067 td 0xc5a19000 _mtx_lock_flags(58,0,c0cd2d5b,570,80,...) at _mtx_lock_flags+0x46 flowtable_free_stale(c0e28f40,0,c0cd2d5b,600,0,...) at flowtable_free_stale+0x2fb flowtable_cleaner(0,e9bc6d38,c0cbf058,343,c5f362a8,...) at flowtable_cleaner+0xd0 fork_exit(c094f920,0,e9bc6d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xe9bc6d70, ebp = 0 --- db Anything else that might be useful or interesting, please let me know; as noted earlier, I left the machine in that state. (I normally power it off after the morning's build/test festivities, as it's loud uses a fair amount of power.) Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpHvtGLX3oQp.pgp Description: PGP signature
RE: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while inkernel mode
Hi David, I will take a look later this afternoon PST. Thanks, -- Qing -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- curr...@freebsd.org] On Behalf Of David Wolfskill Sent: Monday, May 10, 2010 11:26 AM To: Ed Schouten Cc: curr...@freebsd.org Subject: Re: Panic @r207844;current process: flowcleaner Fatal trap 12: page fault while inkernel mode On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote: ... You don't happen to have a backtrace? Oops -- sorry; got caught up in getting ready to head in to work: db bt Tracing pid 20 tid 100067 td 0xc5a19000 _mtx_lock_flags(58,0,c0cd2d5b,570,80,...) at _mtx_lock_flags+0x46 flowtable_free_stale(c0e28f40,0,c0cd2d5b,600,0,...) at flowtable_free_stale+0x2fb flowtable_cleaner(0,e9bc6d38,c0cbf058,343,c5f362a8,...) at flowtable_cleaner+0xd0 fork_exit(c094f920,0,e9bc6d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xe9bc6d70, ebp = 0 --- db Anything else that might be useful or interesting, please let me know; as noted earlier, I left the machine in that state. (I normally power it off after the morning's build/test festivities, as it's loud uses a fair amount of power.) Peace, david -- David H. Wolfskillda...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote:
Hello Gustau, I'm so sorry for belated response that I had no time to
read and work email and wireless stuffs.
Could you please test this symptom with attached patch? It looks in
CURRENT it missed to initialize a ratectl when it associates with AP.
The patch made the machine to panic. I think it happened when launching
the supplicant. In fact, right now it works by putting the RF switch to
OFF. As soon as I change it to ON the machine panics.
It get a trap 12, with two reasons : page fault and bufwrite, buffer is
not busy?
I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision).
Do you want me to test anything else ?
OK. The patch is ready to test. Could you please test it with attached
patch?
regards,
Weongyo Jeong
Index: if_bwn.c
===
--- if_bwn.c (revision 207881)
+++ if_bwn.c (working copy)
@@ -8329,6 +8329,7 @@
static int
bwn_newstate(struct ieee80211vap *vap, enum ieee80211_state nstate, int arg)
{
+ const struct ieee80211_txparam *tp;
struct bwn_vap *bvp = BWN_VAP(vap);
struct ieee80211com *ic= vap-iv_ic;
struct ifnet *ifp = ic-ic_ifp;
@@ -8377,6 +8378,11 @@
bwn_set_pretbtt(mac);
bwn_spu_setdelay(mac, 0);
bwn_set_macaddr(mac);
+
+ /* Initializes ratectl for a node. */
+ tp = vap-iv_txparms[ieee80211_chan2mode(ic-ic_curchan)];
+ if (tp-ucastrate == IEEE80211_FIXED_RATE_NONE)
+ ieee80211_ratectl_node_init(vap-iv_bss);
}
BWN_UNLOCK(sc);
@@ -8994,7 +9000,7 @@
struct bwn_stats *stats = mac-mac_stats;
struct ieee80211_node *ni;
struct ieee80211vap *vap;
- int slot;
+ int retrycnt = 0, slot;
BWN_ASSERT_LOCKED(mac-mac_sc);
@@ -9027,7 +9033,7 @@
status-ack ?
IEEE80211_RATECTL_TX_SUCCESS :
IEEE80211_RATECTL_TX_FAILURE,
- NULL, 0);
+ retrycnt, 0);
break;
}
slot = bwn_dma_nextslot(dr, slot);
@@ -9048,7 +9054,7 @@
status-ack ?
IEEE80211_RATECTL_TX_SUCCESS :
IEEE80211_RATECTL_TX_FAILURE,
- NULL, 0);
+ retrycnt, 0);
}
bwn_pio_handle_txeof(mac, status);
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: LOR: ufs vs bufwait
2010/5/10 Peter Jeremy peterjer...@acm.org: On 2010-May-08 12:20:05 +0200, Ulrich Spörlein u...@spoerlein.net wrote: This LOR also is not yet listed on the LOR page, so I guess it's rather new. I do use SUJ. lock order reversal: 1st 0xc48388d8 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:502 2nd 0xec0fe304 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_softdep.c:11363 3rd 0xc49e56b8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2091 I'm seeing exactly the same LOR (and subsequent deadlock) on a recent -current without SUJ. I think this LOR was reported since a long time. The deadlock may be new and someway related to the vm_page_lock work (if not SUJ). Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: kmem_map too small: 3832475648 total allocated
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10-5-2010 20:09, Bruce Cran wrote: On Friday 30 April 2010 09:11:49 Gary Jennejohn wrote: A number of variables go into calculating vm.kmem_size (see kmeminit() in kern_malloc.c). In the end, the kernel won't allocate more than twice the physical memory size _which it has discovered_. The question is, how much of your physical memory does the kernel actually see? It would appear that the maximum value for vm.kmem_size is twice the amount of avail memory - as opposed to the real memory. I have 6GB installed; 6144MB gets detected but only 5873MB is available. Setting vm.kmem_size to 12G fails but 10G works. real memory = 8589934592 (8192 MB) avail memory = 8257212416 (7874 MB) So I'm setting it to 14G and reboot. (Which is a pain on my Areca card, since it keeps losing disks bu thatt is for another topic) Ans now it gives me: vm.kmem_size: 15032385536 So perhaps somebody should anotate /boot/defaults/loader.conf and/or list this op more positions.. - --WjW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJL6GM8AAoJEP4k4K6R6rBhUEkH/30RkWpqcNnxK3rc0TTl1TWw vNDxNRx+daq3lTjq7H21aM4mblmqhyTDTE+8+JtZA8Imy2hDpgK5dna4YVz5fLX+ Z5bFod2nVFlY1JfsCVpJTP0w2mdlH+DqYFh1C0bqeVLczc9W8BwPPrs8ucatmy2y Fhtgh3T4wKDkb43jneWVxOBpzjXUR3AekvFyL1Dh52WS65KjfgyRPsBnISYs6+iO /ysB2DGXjBwEuPxlEKXWItW/ghA3bnLRGsCqzu16rULIDRaDr2G85sRkMcR0CmSn NNodAW1qOQetmV7RUkwejZqPsxl/pumIK4CbCVjz9hDoXSrApPJE8O4spZyvZiA= =c4Bz -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
Could you please try with 207902? Thanks, Kip On Mon, May 10, 2010 at 11:26 AM, David Wolfskill da...@catwhisker.org wrote: On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote: ... You don't happen to have a backtrace? Oops -- sorry; got caught up in getting ready to head in to work: db bt Tracing pid 20 tid 100067 td 0xc5a19000 _mtx_lock_flags(58,0,c0cd2d5b,570,80,...) at _mtx_lock_flags+0x46 flowtable_free_stale(c0e28f40,0,c0cd2d5b,600,0,...) at flowtable_free_stale+0x2fb flowtable_cleaner(0,e9bc6d38,c0cbf058,343,c5f362a8,...) at flowtable_cleaner+0xd0 fork_exit(c094f920,0,e9bc6d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xe9bc6d70, ebp = 0 --- db Anything else that might be useful or interesting, please let me know; as noted earlier, I left the machine in that state. (I normally power it off after the morning's build/test festivities, as it's loud uses a fair amount of power.) Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Mon, May 10, 2010 at 2:32 PM, K. Macy km...@freebsd.org wrote: Could you please try with 207902? And if not, please get a coredump with a backtrace with symbols. Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Weongyo Jeong wrote: Do you want me to test anything else ? OK. The patch is ready to test. Could you please test it with attached patch? No panic this time. I also don't get these messages any more: May 10 23:25:36 mini kernel: bwn0: unsupported rate 0 May 10 23:26:13 mini last message repeated 2 times May 10 23:28:29 mini last message repeated 320 times May 10 23:28:32 mini last message repeated 61 times May 10 23:29:42 mini shutdown: reboot by ianf: It still doesn't associate with my AP until I destroy the wlan interface and create it again: wlan0: Ethernet address: 00:26:5e:57:23:33 bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: need multicast update callback bwn0: need multicast update callback and then I get lots of these but no where near the rate of the'unsupported rate' messages: May 10 23:31:39 mini kernel: bwn0: RX decryption attempted (old 0 keyidx 0x1) May 10 23:32:10 mini last message repeated 13 times May 10 23:34:09 mini last message repeated 34 times Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... First, thanks for the response. OK; I grabbed r207902 applied it (via patch -p1), then rebuilt the kernel rebooted; here's the panic now: 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 9 3 @DY GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #155 r207844M: Mon May 10 14:55:41 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3610.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0:
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
Are you not able to dump core? Thanks, Kip On Mon, May 10, 2010 at 3:08 PM, David Wolfskill da...@catwhisker.org wrote: On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... First, thanks for the response. OK; I grabbed r207902 applied it (via patch -p1), then rebuilt the kernel rebooted; here's the panic now: 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 9 3 �...@dy GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #155 r207844M: Mon May 10 14:55:41 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3610.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 atrtc0: AT realtime clock port
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Mon, May 10, 2010 at 03:52:07PM -0700, David Wolfskill wrote: On Mon, May 10, 2010 at 03:39:11PM -0700, K. Macy wrote: Are you not able to dump core? Here's the crash summary; I can put the dump on my Web server on request. (It weighs in at 89MB.) Compression reduced the resulting file to 10MB; it may be found at http://www.catwhisker.org/~david/FreeBSD/vmcore.0.gz. I'll be leaving the office to head home between 16:50 - 16:55, and I'll be off-Net until I get home (no earlier than 18:00, but probably before 19:00 -- depending on errands being run). Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpJaft5n9JXz.pgp Description: PGP signature
Re: PT_ATTACH resumes suspended process
Looking at the sendsig label in sys_process.c:kern_ptrace() makes it clear what's happening - in your testing the process was already stopped so the code sets td_xsig to SIGSTOP and wakes it up to send it the signal. But td_xsig doesn't seem to be used anywhere to set pending signals. Maybe I missed the place where that happens. The assumption seems to be that a process being traced will only be stopped if the debugger is already attached and that any signals being sent to it are coming from the debugger itself. This assumption is wrong if the process being attached to was already stopped. It seems to me that checking for req == PT_ATTACH when the process is already stopped and doing a break; in that case might be a solution. Could you be more specific? It seems to me even if you had a special case in kern_ptrace to handle PT_ATTACH when the process is suspended, the code would end up being almost identical to ptracestop(). Unless I didn't follow you. Because of this, I think what I suggested initially, esentially resuming the thread with a pending SIGSTOP (by checking the value of xsig when the thread switches back in issignal) would be a better approach. The hack I put in bothers me a bit because some of the other threads may resume, and even run for a while, but it's still better than the existing behavior. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
