Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi Good news (I hope). With kernel option maxcpus=1, I can not get a lock, so the system is stable and running. Where could be a problem? Best regards, Rok Ingo Molnar wrote: >> Hi >> >> I have recompiled kernel with OPROFILE disabled. I am sending in >> attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and >> netconsole log. Lockup in the lock is software made with ./lockup. The >> kernel still locks 4-5minutes after boot without any further messages >> (waited more than 2 minutes). Any ideas? > > no good ideas :-( I suspect this one: > > [ 185.600900] hdc: lost interrupt > > was a side-effect of lockup.c too? > > does the lockup go away if you boot with maxcpus=1? > > Ingo > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
* Rok Markovic <[EMAIL PROTECTED]> wrote: > Hi > > I have recompiled kernel with OPROFILE disabled. I am sending in > attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and > netconsole log. Lockup in the lock is software made with ./lockup. The > kernel still locks 4-5minutes after boot without any further messages > (waited more than 2 minutes). Any ideas? no good ideas :-( I suspect this one: [ 185.600900] hdc: lost interrupt was a side-effect of lockup.c too? does the lockup go away if you boot with maxcpus=1? Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? Rok Ingo Molnar wrote: > could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI > watchdog? > > how does /proc/interrupts look like shortly after bootup? Does a simple > "intentional lockup" piece of code, which provokes a hard lockup from > user-space, get properly zapped by the NMI watchdog (within a minute or > so): > > the NMI watchdog should produce a console message similar to: > > BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers: > ... > > ( if you test ./lockup and get the message properly then i'd suggest a > new reboot - i think we inhibit further console output after an NMI > printout. ) > > Ingo > > CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:206 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24 84 IO-APIC-edge ide1 19: 3 0 IO-APIC-fasteoi bttv0 20: 8873 0 IO-APIC-fasteoi sata_via 21: 11741 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:253194 LOC: 61512 64324 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:286 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24120 IO-APIC-edge ide1 19: 5 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 12641 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 61993 64918 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:292 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24144 IO-APIC-edge ide1 19: 15 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 13169 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 62237 65219 ERR: 0 [ 177.078312] [ 190.712608] ide-cd: cmd 0x1e timed out [ 190.731121] hdc: lost interrupt [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #5 SMP PREEMPT RT Sat Oct 13 09:36:19 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT
Re: 2.6.23-rt1 lockup after loading HAL deamon
* Rok Markovic <[EMAIL PROTECTED]> wrote:
> I enabled netconsole but I am affraid that it won't help. In
> attachment I am sending complete log over netconsole. While I was
> trying to make everything, I got a lockup on linux-2.6.23-rc8, but I
> am not sure into this. But all lockups happend in VGA console mode.
> Any ideas.
hm:
[ 104.224904] oprofile: using NMI interrupt.
could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI
watchdog?
how does /proc/interrupts look like shortly after bootup? Does a simple
"intentional lockup" piece of code, which provokes a hard lockup from
user-space, get properly zapped by the NMI watchdog (within a minute or
so):
# cat > lockup.c
int main(void)
{
iopl(3);
for (;;)
asm("cli");
}
Ctrl-D
# make lockup
# ./lockup
the NMI watchdog should produce a console message similar to:
BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers:
...
( if you test ./lockup and get the message properly then i'd suggest a
new reboot - i think we inhibit further console output after an NMI
printout. )
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
* Rok Markovic [EMAIL PROTECTED] wrote:
I enabled netconsole but I am affraid that it won't help. In
attachment I am sending complete log over netconsole. While I was
trying to make everything, I got a lockup on linux-2.6.23-rc8, but I
am not sure into this. But all lockups happend in VGA console mode.
Any ideas.
hm:
[ 104.224904] oprofile: using NMI interrupt.
could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI
watchdog?
how does /proc/interrupts look like shortly after bootup? Does a simple
intentional lockup piece of code, which provokes a hard lockup from
user-space, get properly zapped by the NMI watchdog (within a minute or
so):
# cat lockup.c
int main(void)
{
iopl(3);
for (;;)
asm(cli);
}
Ctrl-D
# make lockup
# ./lockup
hard hang
the NMI watchdog should produce a console message similar to:
BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers:
...
( if you test ./lockup and get the message properly then i'd suggest a
new reboot - i think we inhibit further console output after an NMI
printout. )
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? Rok Ingo Molnar wrote: could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI watchdog? how does /proc/interrupts look like shortly after bootup? Does a simple intentional lockup piece of code, which provokes a hard lockup from user-space, get properly zapped by the NMI watchdog (within a minute or so): the NMI watchdog should produce a console message similar to: BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers: ... ( if you test ./lockup and get the message properly then i'd suggest a new reboot - i think we inhibit further console output after an NMI printout. ) Ingo CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:206 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24 84 IO-APIC-edge ide1 19: 3 0 IO-APIC-fasteoi bttv0 20: 8873 0 IO-APIC-fasteoi sata_via 21: 11741 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:253194 LOC: 61512 64324 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:286 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24120 IO-APIC-edge ide1 19: 5 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 12641 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 61993 64918 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:292 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24144 IO-APIC-edge ide1 19: 15 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 13169 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 62237 65219 ERR: 0 [ 177.078312] [ 190.712608] ide-cd: cmd 0x1e timed out [ 190.731121] hdc: lost interrupt [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #5 SMP PREEMPT RT Sat Oct 13 09:36:19 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT 3FFB0450, 3CF4 (r1
Re: 2.6.23-rt1 lockup after loading HAL deamon
* Rok Markovic [EMAIL PROTECTED] wrote: Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? no good ideas :-( I suspect this one: [ 185.600900] hdc: lost interrupt was a side-effect of lockup.c too? does the lockup go away if you boot with maxcpus=1? Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi Good news (I hope). With kernel option maxcpus=1, I can not get a lock, so the system is stable and running. Where could be a problem? Best regards, Rok Ingo Molnar wrote: Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? no good ideas :-( I suspect this one: [ 185.600900] hdc: lost interrupt was a side-effect of lockup.c too? does the lockup go away if you boot with maxcpus=1? Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
I forgot attachment. Rok Rok Markovic wrote: > Hi > > I enabled netconsole but I am affraid that it won't help. In attachment > I am sending complete log over netconsole. While I was trying to make > everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into > this. But all lockups happend in VGA console mode. Any ideas. > > Rok > > > Ingo Molnar wrote: >>> I tried to recompile with those options enabled, kernel and linux >>> boots and loads fine, but after few minutes (if i try to recompile >>> kernel in console) the system locks completely (hard reset) without >>> any messages. Is there anything I can do, maybe console on serial >>> port? My new config is atached. >> yes, serial console (or netconsole) output would be useful, if you can >> solve that. Another way would be to boot with nmi_watchdog=2, do the >> kernel recompile in a VGA text console, and wait for the lockup to >> occur. Either you get some crash message to the text console >> immediately, or you should get the NMI watchdog print something within a >> minute or so. If neither happens you just get a blank hard lockup then >> the wedge is very deep ... >> >> (also make sure that the NMI counter in /proc/interrupts is increasing >> on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are >> increasing their NMI counters once per second then the NMI watchdog wont >> be able to print out a stackdump.) >> >> Ingo [ 859.950668] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 859.951294] sd 2:0:0:1: [sdc] Write Protect is off [ 859.951313] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 860.618633] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 860.619414] sd 2:0:0:1: [sdc] Write Protect is off [ 860.619433] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 1007.878314] nfsd: last server has exited [ 1007.926075] nfsd: unexporting all filesystems [ 1324.899757] nfsd: last server has exited [ 1324.952596] nfsd: unexporting all filesystems [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #4 SMP PREEMPT RT Fri Oct 12 22:07:05 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT 3FFB0450, 3CF4 (r1 75D8P 75D8P0044 INTL 2002026) [0.00] ACPI: FACS 3FFC, 0040 [0.00] ACPI: APIC 3FFB0390, 0078 (r1 A M I OEMAPIC 12000521 MSFT 97) [0.00] ACPI: MCFG 3FFB0410, 003C (r1 A M I OEMMCFG 12000521 MSFT 97) [0.00] ACPI: OEMB 3FFC0040, 0046 (r1 A M I AMI_OEM 12000521 MSFT 97) [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 262064 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: IOAPIC (id[0x03] address[0xfecc] gsi_base[24]) [0.00] IOAPIC[1]: apic_id 3, address 0xfecc, GSI 24-47 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [0.00] Setting APIC routing to flat [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Allocating PCI
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I enabled netconsole but I am affraid that it won't help. In attachment I am sending complete log over netconsole. While I was trying to make everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into this. But all lockups happend in VGA console mode. Any ideas. Rok Ingo Molnar wrote: >> I tried to recompile with those options enabled, kernel and linux >> boots and loads fine, but after few minutes (if i try to recompile >> kernel in console) the system locks completely (hard reset) without >> any messages. Is there anything I can do, maybe console on serial >> port? My new config is atached. > > yes, serial console (or netconsole) output would be useful, if you can > solve that. Another way would be to boot with nmi_watchdog=2, do the > kernel recompile in a VGA text console, and wait for the lockup to > occur. Either you get some crash message to the text console > immediately, or you should get the NMI watchdog print something within a > minute or so. If neither happens you just get a blank hard lockup then > the wedge is very deep ... > > (also make sure that the NMI counter in /proc/interrupts is increasing > on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are > increasing their NMI counters once per second then the NMI watchdog wont > be able to print out a stackdump.) > > Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi again! I tried to boot into VGA mode with NMI watchdog=2. System loads OK, nmi counter is increasing on both CPUs (procesor is HT), but when I start to load the CPU (compiling kernel), system locks without any message. Even blinking cursor disapears. I will try to do netconsole loging, but I can't promise any results for today. Rok Ingo Molnar wrote: >> I tried to recompile with those options enabled, kernel and linux >> boots and loads fine, but after few minutes (if i try to recompile >> kernel in console) the system locks completely (hard reset) without >> any messages. Is there anything I can do, maybe console on serial >> port? My new config is atached. > > yes, serial console (or netconsole) output would be useful, if you can > solve that. Another way would be to boot with nmi_watchdog=2, do the > kernel recompile in a VGA text console, and wait for the lockup to > occur. Either you get some crash message to the text console > immediately, or you should get the NMI watchdog print something within a > minute or so. If neither happens you just get a blank hard lockup then > the wedge is very deep ... > > (also make sure that the NMI counter in /proc/interrupts is increasing > on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are > increasing their NMI counters once per second then the NMI watchdog wont > be able to print out a stackdump.) > > Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
* Rok Markovic <[EMAIL PROTECTED]> wrote: > I tried to recompile with those options enabled, kernel and linux > boots and loads fine, but after few minutes (if i try to recompile > kernel in console) the system locks completely (hard reset) without > any messages. Is there anything I can do, maybe console on serial > port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
does anything get printed prior the lockup if you enable all of these: # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_LIST is not set # CONFIG_FRAME_POINTER is not set ? Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
does anything get printed prior the lockup if you enable all of these: # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_LIST is not set # CONFIG_FRAME_POINTER is not set ? Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi again! I tried to boot into VGA mode with NMI watchdog=2. System loads OK, nmi counter is increasing on both CPUs (procesor is HT), but when I start to load the CPU (compiling kernel), system locks without any message. Even blinking cursor disapears. I will try to do netconsole loging, but I can't promise any results for today. Rok Ingo Molnar wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
* Rok Markovic [EMAIL PROTECTED] wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
I forgot attachment. Rok Rok Markovic wrote: Hi I enabled netconsole but I am affraid that it won't help. In attachment I am sending complete log over netconsole. While I was trying to make everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into this. But all lockups happend in VGA console mode. Any ideas. Rok Ingo Molnar wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo [ 859.950668] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 859.951294] sd 2:0:0:1: [sdc] Write Protect is off [ 859.951313] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 860.618633] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 860.619414] sd 2:0:0:1: [sdc] Write Protect is off [ 860.619433] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 1007.878314] nfsd: last server has exited [ 1007.926075] nfsd: unexporting all filesystems [ 1324.899757] nfsd: last server has exited [ 1324.952596] nfsd: unexporting all filesystems [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #4 SMP PREEMPT RT Fri Oct 12 22:07:05 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT 3FFB0450, 3CF4 (r1 75D8P 75D8P0044 INTL 2002026) [0.00] ACPI: FACS 3FFC, 0040 [0.00] ACPI: APIC 3FFB0390, 0078 (r1 A M I OEMAPIC 12000521 MSFT 97) [0.00] ACPI: MCFG 3FFB0410, 003C (r1 A M I OEMMCFG 12000521 MSFT 97) [0.00] ACPI: OEMB 3FFC0040, 0046 (r1 A M I AMI_OEM 12000521 MSFT 97) [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] DMA324096 - 1048576 [0.00] Normal1048576 - 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 - 159 [0.00] 0: 256 - 262064 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: IOAPIC (id[0x03] address[0xfecc] gsi_base[24]) [0.00] IOAPIC[1]: apic_id 3, address 0xfecc, GSI 24-47 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [0.00] Setting APIC routing to flat [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bee0) [
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I enabled netconsole but I am affraid that it won't help. In attachment I am sending complete log over netconsole. While I was trying to make everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into this. But all lockups happend in VGA console mode. Any ideas. Rok Ingo Molnar wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
