From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Hard lock on 2.6-test9 (More Info)
Date: Mon, 17 Nov 2003 13:32:56 +0000 [thread overview]
Message-ID: <3FB8CE08.6070001@dcrdev.demon.co.uk> (raw)
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.
next reply other threads:[~2003-11-17 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 13:32 Dan Creswell [this message]
2003-11-17 16:32 ` Hard lock on 2.6-test9 (More Info) Linus Torvalds
2003-11-17 16:46 ` Dan Creswell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FB8CE08.6070001@dcrdev.demon.co.uk \
--to=dan@dcrdev.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.