SMP stability ? [was Re: more info from panic from running dnet on SMP kernel]

2002-11-17 Thread Thierry Herbelot
Le Sunday 17 November 2002 10:50, Joel M. Baldwin a écrit :
 running dnet on a SMP kernel causes the kernel to panic.



[Hijacking another thread ?]

I haven't been able to complete a full buildworld with an SMP on a Abit BP6 
(bi-celeron) board for two weeks (the kernel config is just a full GENERIC 
with SMP and APICIO options enabled).

The same machine runs happily strings of make -j48 buildworld's when running 
with the straight GENERIC UP kernel, so I think the hardware seems to be 
working OK.

Even make -j1 buildworld with the SMP kernel ends with a complete freeze of 
the machine (the kernel does not go to a panic where I could try a backtrace)

The hardware config of the machine is pretty dull (see dmesg later).

One point that could be better is that the sources are NFS mounted from a 
4.7-Stable server, over an rl(4) board, which may be unstable (/usr/obj is 
local, on the Maxtor drive)

TfH

PS : the machine was re-installed anew from the 5.0-20021027-CURRENT snapshot, 
then upgraded via make buildworld/buildkernel and mergemaster

PS2 : full dmesg (when running the stable, UP, GENERIC)

Copyright (c) 1992-2002 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 5.0-CURRENT #17: Sat Nov 16 19:16:25 CET 2002

XXX@YYY:/usr/obj/files2/src-free/src/sys/GENERIC
Preloaded elf kernel /boot/kernel/kernel at 0xc0662000.
Timecounter i8254  frequency 1193182 Hz
Timecounter TSC  frequency 334092192 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x665  Stepping = 5
  
Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
real memory  = 536870912 (512 MB)
avail memory = 514818048 (490 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
Using $PIR table, 8 entries at 0xc00fdef0
pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xe000-0xe3ff at 
device 0.0 on pci0
pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on 
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xd000-0xd01f irq 10 at 
device 7.2 on pci0
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0: bridge, PCI-unknown at device 7.3 (no driver attached)
rl0: RealTek 8139 10/100BaseTX port 0xd400-0xd4ff mem 0xe500-0xe5ff 
irq 10 at device 17.0 on pci0
rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode
rl0: Ethernet address: 00:40:95:30:38:36
miibus0: MII bus on rl0
rlphy0: RealTek internal media interface on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
atapci1: HighPoint HPT366 ATA66 controller port 
0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.0 on pci0
ata2: at 0xd800 on atapci1
atapci2: HighPoint HPT366 ATA66 controller port 
0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 11 at device 19.1 on pci0
ata3: at 0xe400 on atapci2
orm0: Option ROMs at iomem 0xc6800-0xc7fff,0xc-0xc5fff on isa0
pmtimer0 on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x100
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0303 can't assign resources (port)
unknown: PNP0a03 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
unknown: PNP0400 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
Timecounters tick every 10.000 msec
ad0: 6149MB Maxtor 86480D6 [13328/15/63] at ata0-master UDMA33
acd0: CDROM NEC CD-ROM DRIVE:28B at ata1-master PIO4
Mounting root from ufs:/dev/ad0s2a


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: SMP stability ? [was Re: more info from panic from running dnet on SMP kernel]

2002-11-17 Thread Robert Watson

On Sun, 17 Nov 2002, Thierry Herbelot wrote:

 Even make -j1 buildworld with the SMP kernel ends with a complete freeze
 of the machine (the kernel does not go to a panic where I could try a
 backtrace) 

I've seen several reports that using a serial break to get into ddb is now
quite a bit more reliable than a keyboard break.  If you're not already
using a serial console, you might want to give it a try (make sure to turn
on BREAK_TO_DEBUGGER and/or ALT_BREAK_TO_DEBUGGER). 

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: SMP stability ? [was Re: more info from panic from running dnet on SMP kernel]

2002-11-17 Thread Thierry Herbelot
Le Sunday 17 November 2002 20:46, Robert Watson a écrit :

 I've seen several reports that using a serial break to get into ddb is now
 quite a bit more reliable than a keyboard break.  If you're not already
 using a serial console, you might want to give it a try (make sure to turn
 on BREAK_TO_DEBUGGER and/or ALT_BREAK_TO_DEBUGGER).

OK, I'll do so

TfH

PS : I think one other BP6 user is Grog

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message