Re: Lock-up with CPU busy at r217145; seems OK now at r217189

2011-01-11 Thread Andriy Gapon
on 09/01/2011 20:36 Michael Butler said the following:
 automoc4 spawns a child during a KDE-4 build which
 turns into a zombie but is never seen to return and the build stalls -
 weird :-(

I believe that this one particular issue should be fixed by r217253.
The problem resolved by the commit resulted in some signals being lost
sometimes, in particular SIGCHLD.

-- 
Andriy Gapon
___
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


Lock-up with CPU busy at r217145; seems OK now at r217189

2011-01-09 Thread David Wolfskill
As usual, I have been tracking, building,  booting head daily on my
laptop for a while.

Yesterday, having built head at r217090, I had updated to r217145,
built, and booted it OK.  (I then booted from my stable/8 slice for the
rest of the day, as usual.)

This morning, I updated to r217189, but on 3 out of 3 attempts to
perform make -j4 buildworld while running head at r217145, the
machine became unresponsive (while the fans were at top speed and
the screen remained lit).  I have DDB in the kernel config, but was
unable to break to the debugger.

After the 3 tries, I booted from the r217090 kernel; the make -j4
buildworld was successful.

After booting head at r217189, I re-ran the make -j4 buildworld just
to see if it survived the attempt; it did.

So it *appears* that something after r217090 and before r217146 caused a
problem, and something after r217145 and before r217190 has fixed or
circumvented it.  Of course, this isn't an exhaustive test, so take it
with an appropriate grain of salt.

I've attached dmseg.boot for those iinterested.

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.
Copyright (c) 1992-2011 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 #99 r217189: Sun Jan  9 08:17:44 PST 2011
r...@g1-222.catwhisker.org.:/usr/obj/usr/src/sys/CANARY i386
WARNING: WITNESS option enabled, expect reduced performance.
WARNING: DIAGNOSTIC option enabled, expect reduced performance.
MEMGUARD DEBUGGING ALLOCATOR INITIALIZED:
MEMGUARD map base: 0xc700
MEMGUARD map limit: 0xc900
MEMGUARD map size: 32768 KBytes
CPU: Intel(R) Core(TM)2 Duo CPU T9600  @ 2.80GHz (2793.07-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x10676  Family = 6  Model = 17  Stepping = 6
  
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=0x8e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
  AMD Features=0x2010NX,LM
  AMD Features2=0x1LAHF
  TSC: P-state invariant
real memory  = 4294967296 (4096 MB)
avail memory = 3656601600 (3487 MB)
Event timer LAPIC quality 400
ACPI APIC Table: DELL   M09
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: DELL M09 on motherboard
hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Timecounter HPET frequency 14318180 Hz quality 900
Event timer HPET frequency 14318180 Hz quality 450
Event timer HPET1 frequency 14318180 Hz quality 440
Event timer HPET2 frequency 14318180 Hz quality 440
Event timer HPET3 frequency 14318180 Hz quality 440
acpi0: reservation of 0, 9f000 (3) failed
acpi0: reservation of 10, df351c00 (3) failed
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
acpi_ec0: Embedded Controller: GPE 0x11 port 0x930,0x934 on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
vgapci0: VGA-compatible display port 0xdf00-0xdf7f mem 
0xf500-0xf5ff,0xe000-0xefff,0xf200-0xf3ff irq 16 at 
device 0.0 on pci1
em0: Intel(R) PRO/1000 Network Connection 7.1.8 port 0xefe0-0xefff mem 
0xf6fe-0xf6ff,0xf6fdb000-0xf6fdbfff irq 22 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:21:70:d5:28:dd
uhci0: Intel 82801I (ICH9) USB controller port 0x6f60-0x6f7f irq 20 at device 
26.0 on pci0
uhci0: LegSup = 0x2f00
usbus0: Intel 82801I (ICH9) USB controller on uhci0
uhci1: Intel 82801I (ICH9) USB controller port 0x6f80-0x6f9f irq 21 at device 
26.1 on pci0
uhci1: LegSup = 0x2f00
usbus1: Intel 82801I (ICH9) USB controller on uhci1
uhci2: Intel 82801I (ICH9) USB controller port 0x6fa0-0x6fbf irq 22 at device 
26.2 on pci0
uhci2: LegSup = 0x2f00
usbus2: Intel 82801I (ICH9) USB controller on uhci2
ehci0: Intel 82801I (ICH9) USB 2.0 controller mem 0xfed1c400-0xfed1c7ff irq 
22 at device 26.7 on pci0
usbus3: EHCI version 1.0
usbus3: Intel 82801I (ICH9) USB 2.0 controller on ehci0
hdac0: Intel 82801I High Definition Audio Controller mem 
0xf6fdc000-0xf6fd irq 21 at device 27.0 on pci0
hdac0: HDA Driver Revision: 20100226_0142
pcib2: ACPI PCI-PCI bridge at device 28.0 on pci0
pci11: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge at device 28.1 on pci0
pci12: ACPI PCI bus on pcib3
iwn0: 

Re: Lock-up with CPU busy at r217145; seems OK now at r217189

2011-01-09 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/09/11 12:57, David Wolfskill wrote:
 As usual, I have been tracking, building,  booting head daily on my
 laptop for a while.
 
 Yesterday, having built head at r217090, I had updated to r217145,
 built, and booted it OK.  (I then booted from my stable/8 slice for the
 rest of the day, as usual.)
 
 This morning, I updated to r217189, but on 3 out of 3 attempts to
 perform make -j4 buildworld while running head at r217145, the
 machine became unresponsive (while the fans were at top speed and
 the screen remained lit).  I have DDB in the kernel config, but was
 unable to break to the debugger.

I too have been seeing *really* odd things - dump randomly stops in the
middle of a backup, automoc4 spawns a child during a KDE-4 build which
turns into a zombie but is never seen to return and the build stalls -
weird :-(

Having checked out and built SVN revision 217202 - I'll try again ..

imb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk0qAEgACgkQQv9rrgRC1JL9xwCgyHO8V8EE2wEXYpVifE4WjWve
h/oAnjmJgG8GzJTF9v/mQxR3q+VllWZ7
=mMUo
-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