lkml.org 
[lkml]   [2003]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectHard lock on 2.6-test9 (More Info)
Both SMP kernels (2.4 and 2.6) appear to have the same interrupt map 
(cat /proc/interrupts):

Kernel 2.4:

CPU0 CPU1
0: 10942 8009 IO-APIC-edge timer
1: 199 208 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 1 0 IO-APIC-edge rtc
12: 2275 1615 IO-APIC-edge PS/2 Mouse
14: 57 56 IO-APIC-edge ide0
16: 118 0 IO-APIC-level usb-uhci, eth0
17: 5267 3420 IO-APIC-level ohci1394, Intel ICH4, nvidia
18: 0 0 IO-APIC-level usb-uhci
19: 0 0 IO-APIC-level usb-uhci
23: 0 0 IO-APIC-level ehci_hcd
24: 9083 3661 IO-APIC-level ioc0
25: 42 0 IO-APIC-level ioc1
NMI: 0 0
LOC: 18878 18807
ERR: 0
MIS: 0

Kernel 2.6:

CPU0 CPU1
0: 75737 51102 IO-APIC-edge timer
1: 152 278 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
8: 1 0 IO-APIC-edge rtc
12: 61 0 IO-APIC-edge i8042
14: 22 1 IO-APIC-edge ide0
16: 92 0 IO-APIC-level eth0
17: 3 0 IO-APIC-level ohci1394, Intel 82801DB-ICH4
23: 0 0 IO-APIC-level ehci_hcd
24: 2635 715 IO-APIC-level ioc0
25: 42 0 IO-APIC-level ioc1
NMI: 0 0
LOC: 126582 126581
ERR: 0
MIS: 0

When I boot X under kernel 2.6, I see the additional nvidia interrupt
path as per the 2.4 output (which was taken whilst I was running X).

But, within seconds of this additional interrupt assignment appearing,
2.6 dies a horrible death whilst 2.4 just keeps on rolling.

Cheers,

Dan.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:58    [from the cache]
©2003-2011 Jasper Spaans