Re: Dead lock
On Wednesday 13 June 2007 08:30, Stefan Bethke wrote: Am 30.05.2007 um 16:32 schrieb Roger Miranda: As of right now the machine goes into dead lock within a few hours (only when on the network). I get no WITNESS errors (LORs), or kernel dumps, or anything in the logs that look like an error or out of the ordinary. Is there anything else I could try? or am I looking at a hardware failure? What specifically do you mean by deadlock? Does Caps Lock or Num Lock still toggle the indicator? Can you enter the debugger? If so, there's a couple of things you could try from there, including saving a dump by entering call doadump or panic. Hi Stefan, Caps Lock nor Num Lock Toggles. We can not enter the debugger. It's a completly locked up system. At first I thought it was a Hardware or NIC issue. But we have tried new Hardware and 3com nics instead of the em (intel) NICs. Roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Hang, nothing in logs / no panics
On Friday 11 May 2007 16:47, Kris Kennaway wrote: Am I possible looking at a hardware issue? If so what is the best way to test for it? If that doesn't work then in my experience it is likely to be hardware-related. The usual debugging procedure then involves trying to replicate on an unrelated machine, and/or swapping out hardware components. Kris, Sorry for the time delay. But we have confirmed this is not a hardware issue. We have is dead locking across multiple systems, when bridge a moderate amount of tcp connections. I have no idea how to debug this. Could it be an issues with if_config of pf? We are using the latest drivers form intel. But have ruled it out as being an driver or network card related problem. Roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Dead lock
Good Day, I've brought up this issue in the past. I've now got a bit more information but still no solution. I am looking for a way to debug this anyway I can. We got a freebsd 6.2 (FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0) machine running if_bridge as a intercept proxy. We have added the following kernel options: options DDB options KDB options BREAK_TO_DEBUGGER options INVARIANTS options INVARIANTS_SUPPORT options WITNESS options DEBUG_VFS_LOCKS options DEBUG_MEMGUARD We were getting an LOR but fixed it but removing kern.polling.enable in /etc/sysctl.conf As of right now the machine goes into dead lock within a few hours (only when on the network). I get no WITNESS errors (LORs), or kernel dumps, or anything in the logs that look like an error or out of the ordinary. Is there anything else I could try? or am I looking at a hardware failure? see demsg below. Roger ---DMESG output Copyright (c) 1992-2007 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 6.2-RELEASE #0: Wed May 23 10:21:44 UTC 2007 root@:/usr/obj/usr/src/sys/TINYBSD WARNING: WITNESS option enabled, expect reduced performance. MEMGUARD DEBUGGING ALLOCATOR INITIALIZED: MEMGUARD map base: 0xc327d000 MEMGUARD map limit: 0xc42ed000 MEMGUARD map size: 17235968 (Bytes) ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193510 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2792.83-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 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=0x441dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,b14 real memory = 535691264 (510 MB) avail memory = 514809856 (490 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button 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 3.0 on pci0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection Version - 6.3.9 port 0xc000-0xc01f mem 0xf200-0xf201 irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:30:48:86:97:62 pcib2: ACPI PCI-PCI bridge at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: base peripheral at device 29.4 (no driver attached) pci0: base peripheral, interrupt controller at device 29.5 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus on pcib3 pci3: display, VGA at device 9.0 (no driver attached) em1: Intel(R) PRO/1000 Network Connection Version - 6.3.9 port 0xd100-0xd13f mem 0xf100-0xf101 irq 19 at device 10.0 on pci3 em1: Ethernet address: 00:30:48:86:97:63 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel 6300ESB SATA150 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_tz0: Thermal Zone on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2792827369 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v4.1.13 initialized. Default = pass all, Logging = enabled ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default ad0: 977MB SanDisk SDCFH-1024 HDX 3.19 at ata0-master PIO4 ad2: 76319MB Seagate ST380811AS 3.AAB at ata1-master SATA150 Trying to mount root from ufs:/dev/ad0s1a em0: link state changed to DOWN bridge0: Ethernet address: 72:59:fa:79:40:73 em0: promiscuous mode enabled em1: promiscuous mode enabled em0: link state changed to UP em1: link state changed to UP ___ freebsd-stable@freebsd.org mailing list
Re: ghosthunting: machine freeze 6.2R
On Friday 25 May 2007 04:07, Volker wrote: Kris, Roger all, well, we replaced the broken machine (totally different hardware), took one of the mirrored hard disks into this replacement machine and took this replacement into production. Unfortunately it took less than 16 hours for this replacement machine to also freeze. My assumption is, the freeze itself has nothing to do with bad hardware, as it's now happening on two different machines. This replacement doesn't have em NICs but gives the same bad behavior (so I also think, it's not em related). As I really do want to know what's going on, I'm now compiling a new world + kernel with WITNESS and INVARIANTS support and see if I can catch something. I'm using the following additional kernel options: makeoptions DEBUG=-g options KDB options KDB_UNATTENDED options KDB_TRACE options DDB options WITNESS options WITNESS_SKIPSPIN options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC options PANIC_REBOOT_WAIT_TIME=60 Volker Kris, Sorry for kind of hi-jacking your thread. Just hopefully we all can work together to fix this issue (if there is one). Out machine did goto in to a hard lock. Nothing showed up on the screen or logs. I did see something from WITNESS in dmesg. See below. But this does not show up at the time of the crash. If I remember correctly this show up at boot time. We have added the following kernel options: options DDB options KDB options BREAK_TO_DEBUGGER options INVARIANTS options INVARIANTS_SUPPORT options WITNESS options DEBUG_VFS_LOCKS options DEBUG_MEMGUARD -dmesg--- softdep_waitidle: Failed to flush worklist for 0xc44ffcf8 em1: link state changed to DOWN bridge0: Ethernet address: 66:9e:c9:a6:f5:27 em0: promiscuous mode enabled em1: promiscuous mode enabled em1: link state changed to UP lock order reversal: 1st 0xc06e0820 polling (polling) @ /usr/src/sys/kern/kern_poll.c:422 2nd 0xc473070c if_bridge (if_bridge) @ /usr/src/sys/net/if_bridge.c:1976 KDB: stack backtrace: witness_checkorder(c473070c,9,c068bfbc,7b8) at witness_checkorder+0x55c _mtx_lock_flags(c473070c,0,c068bfbc,7b8,c473070c,...) at _mtx_lock_flags+0x41 bridge_input(c43d9000,c474,c43a828c,c43a8000,c474,...) at bridge_input+0x80 ether_input(c43d9000,c474,c43a828c,0,c0675f3c,...) at ether_input+0x122 e1000_rxeof(d43f2cbc,c0524e5d,d43f2ca8,1,5,...) at e1000_rxeof+0x19b e1000_poll(c43d9000,0,5) at e1000_poll+0x46 netisr_poll(0) at netisr_poll+0x70 swi_net(0,c4315438,c4323a80,c050a484,c4322648,...) at swi_net+0xb0 ithread_loop(c430f700,d43f2d38,c430f700,c050a484,0,...) at ithread_loop+0x1de fork_exit(c050a484,c430f700,d43f2d38) at fork_exit+0x7d fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd43f2d6c, ebp = 0 --- softdep_waitidle: Failed to flush worklist for 0xc44ffcf8 em0: link state changed to UP ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
On Tuesday 22 May 2007 14:03, Kris Kennaway wrote: What happens if you enable INVARIANTS and/or WITNESS? I have enabled WITNESS, I have no experienced a freeze yet. But i did notice on boot an WITNESS message for if_bridge. See attached. Could this be causing the freeze? softdep_waitidle: Failed to flush worklist for 0xc44ffcf8 em1: link state changed to DOWN bridge0: Ethernet address: 66:9e:c9:a6:f5:27 em0: promiscuous mode enabled em1: promiscuous mode enabled em1: link state changed to UP lock order reversal: 1st 0xc06e0820 polling (polling) @ /usr/src/sys/kern/kern_poll.c:422 2nd 0xc473070c if_bridge (if_bridge) @ /usr/src/sys/net/if_bridge.c:1976 KDB: stack backtrace: witness_checkorder(c473070c,9,c068bfbc,7b8) at witness_checkorder+0x55c _mtx_lock_flags(c473070c,0,c068bfbc,7b8,c473070c,...) at _mtx_lock_flags+0x41 bridge_input(c43d9000,c474,c43a828c,c43a8000,c474,...) at bridge_input+0x80 ether_input(c43d9000,c474,c43a828c,0,c0675f3c,...) at ether_input+0x122 e1000_rxeof(d43f2cbc,c0524e5d,d43f2ca8,1,5,...) at e1000_rxeof+0x19b e1000_poll(c43d9000,0,5) at e1000_poll+0x46 netisr_poll(0) at netisr_poll+0x70 swi_net(0,c4315438,c4323a80,c050a484,c4322648,...) at swi_net+0xb0 ithread_loop(c430f700,d43f2d38,c430f700,c050a484,0,...) at ithread_loop+0x1de fork_exit(c050a484,c430f700,d43f2d38) at fork_exit+0x7d fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd43f2d6c, ebp = 0 --- softdep_waitidle: Failed to flush worklist for 0xc44ffcf8 em0: link state changed to UP ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
On Tuesday 22 May 2007 08:15, Volker wrote: Hi! Starting yesterday I'm experiencing machine freezes on a 6.2-R system (remote to me). The strange thing: It occurs twice a day, in the morning hours (both freezes are within 1-2 hours) and for the rest of the day everything runs fine. The machine does not respond anymore (no net, no keyboard interaction) but does not panic. We also have been experiencing the same type of behavior (as explained in a previous post). freeze times vary throughout the day. However, if we have no network connections attached to the box, It stays up consistantly. Could you take it off your network and see if it still freezes up ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
On Tuesday 22 May 2007 11:41, Volker wrote: There's nothing of interest in the logs (I suspect it's too late to have any daemon write something to syslogd as the system is then dead). As I also think, this is somehow related to network traffic, I'll try to monitor it's traffic starting tomorrow. The tech guys at the office there have to install a hub first (yes, it's remote to me which makes investigation harder). As I think (well, guesswork) this might be related to GRE traffic (the poptop server), I may stop this traffic at the firewall (and take the service to another machine). What's the version of the system you're having trouble with? Is it pre-6.2? I'm wondering if your machine also passes GRE traffic? Does it provide pptp services? I've attached the latest dmesg, can you see any similarities (as it still might be a hardware issue)? Volker, Yes. We get nothing in the logs, No kernel panics, and we can not break to the kernel debugger. We are not running an GRE traffic or PPTP Servers. Our current version is: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0 Looks like you are also using the EM network adapter driver. We are suspecting the driver or Network adapters them self. Our other boxes are using xl0 (3com) and are working fine. I have also attached my dmesg output. Roger Copyright (c) 1992-2007 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 6.2-RELEASE #0: Wed May 9 17:48:30 UTC 2007 root@:/usr/obj/usr/src/sys/TINYBSD WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193520 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2792.85-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 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=0x441dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,b14 real memory = 535691264 (510 MB) avail memory = 51964 (494 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button 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 3.0 on pci0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection Version - 6.3.9 port 0xc000-0xc01f mem 0xf200-0xf201 irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:30:48:86:97:62 em0: [GIANT-LOCKED] pcib2: ACPI PCI-PCI bridge at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: base peripheral at device 29.4 (no driver attached) pci0: base peripheral, interrupt controller at device 29.5 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus on pcib3 pci3: display, VGA at device 9.0 (no driver attached) em1: Intel(R) PRO/1000 Network Connection Version - 6.3.9 port 0xd100-0xd13f mem 0xf100-0xf101 irq 19 at device 10.0 on pci3 em1: Ethernet address: 00:30:48:86:97:63 em1: [GIANT-LOCKED] isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel 6300ESB SATA150 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_tz0: Thermal Zone on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2792849472 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v4.1.13 initialized. Default = pass all, Logging = enabled ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default ad0: 977MB SanDisk SDCFH-1024 HDX 3.19 at ata0-master PIO4 ad2: 76319MB Seagate ST380811AS 3.AAB at ata1-master SATA150 Trying to mount root from ufs:/dev/ad0s1a em1: link state
Re: ghosthunting: machine freeze 6.2R
What happens if you enable INVARIANTS and/or WITNESS? Thanks Kris. I am going to compile that into the kernel right now. Well keep the list posted on any issues. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Hard Hang, nothing in logs / no panics
Good Day everyone. I have this one system setup with If_bridge to filter traffic. It does work quite good. I am running FreeBSD 6.2 but as a TINYBSD Image. The one problem I have is I place the machine at the perimeter on our network with 27 seats. At that time anywhere between 15min - 24hours the entire system goes into a Hard Lock (Physical reboot needed). The thing is there is no logs or kernel panics or anything. No IRQ Conflicts exists. I am looking for any inputs or any ways to go after looking how to even diagnosed this. Here is a copy of my dmesg. Copyright (c) 1992-2007 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 6.2-RELEASE #0: Wed May 9 17:48:30 UTC 2007 root@:/usr/obj/usr/src/sys/TINYBSD WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193520 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2792.85-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 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=0x441dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,b14 real memory = 535691264 (510 MB) avail memory = 51964 (494 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button 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 3.0 on pci0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection Version - 6.3.9 port 0xc000-0xc01f mem 0xf200-0xf201 irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:30:48:86:97:62 em0: [GIANT-LOCKED] pcib2: ACPI PCI-PCI bridge at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: base peripheral at device 29.4 (no driver attached) pci0: base peripheral, interrupt controller at device 29.5 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus on pcib3 pci3: display, VGA at device 9.0 (no driver attached) em1: Intel(R) PRO/1000 Network Connection Version - 6.3.9 port 0xd100-0xd13f mem 0xf100-0xf101 irq 19 at device 10.0 on pci3 em1: Ethernet address: 00:30:48:86:97:63 em1: [GIANT-LOCKED] isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel 6300ESB SATA150 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_tz0: Thermal Zone on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2792849472 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v4.1.13 initialized. Default = pass all, Logging = enabled ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default ad0: 977MB SanDisk SDCFH-1024 HDX 3.19 at ata0-master PIO4 ad2: 76319MB Seagate ST380811AS 3.AAB at ata1-master SATA150 Trying to mount root from ufs:/dev/ad0s1a em1: link state changed to DOWN em0: link state changed to DOWN bridge0: Ethernet address: 46:e0:af:c9:e6:b7 em0: promiscuous mode enabled em1: promiscuous mode enabled em0: link state changed to UP em1: link state changed to UP em1: link state changed to DOWN em1: link state changed to UP Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 0 done All buffers synced. Uptime: 47m5s Copyright (c) 1992-2007 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
Re: Hard Hang, nothing in logs / no panics
On Friday 11 May 2007 16:00, Kris Kennaway wrote: See the developers handbook chapter on kernel debugging. Kris, I have gone through the kernel debugging sections of the developers handbook. The one problem is when I get a hard hang, I do not get any error or panics. And there is no crash or dump data on reboot. Yes. I have enabled DDB and KDB and a dumpdir (in /etc/rc.conf) Am I missing something in the kernel debugging section? I see 11.9 Debugging Deadlocks talk about Deadlocks. But at the time of the lock I have no way of doing a ps or really anything as the system is locked up solid. Roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Hang, nothing in logs / no panics
You missed that the debugger is there to debug bugs (including deadlocks). Break to the debugger and obtain the necessary debugging I should've been more clear. I can not break to the debugger (CTRL-ALT-ESC) when the system locks up. Am I possible looking at a hardware issue? If so what is the best way to test for it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
