Volker Armin Hemmann wrote:
From systemrescuecd, ahci in bios, no nomsi:
CPU0 CPU1
0: 147 1 IO-APIC-edge timer
1: 0 607 IO-APIC-edge i8042
8: 0 61 IO-APIC-edge rtc
9: 0 1 IO-APIC-fasteoi acpi
12: 0 4 IO-APIC-edge i8042
14: 0 0 IO-APIC-edge libata
15: 0 0 IO-APIC-edge libata
18: 0 16 IO-APIC-fasteoi aic7xxx
21: 0 0 IO-APIC-fasteoi ohci_hcd:usb2
22: 2 8428 IO-APIC-fasteoi ehci_hcd:usb1
1274: 0 0 PCI-MSI-edge ahci
1275: 0 222 PCI-MSI-edge eth0
NMI: 0 0 Non-maskable interrupts
LOC: 14777 16785 Local timer interrupts
RES: 7250 6100 Rescheduling interrupts
CAL: 41 52 function call interrupts
TLB: 1866 1876 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
SPU: 0 0 Spurious interrupts
ERR: 6
With my 'own' kernel, AHCI has interrupt 315. I will try and make a more
monolithic kernel so I might be able to boot from a usb-flash device.
.
.
.
which didn't work. Hm, I am too stupid for that today...
Hmmm...
I will reboot from systemresucecd later today and post some results with
ahci-mode set, no nomsi. Just can't try patches that way.
Is sytemrescuecd using the same kernel? Otherwise, it will only add
more to the confusion.
almost. A heavily patched 2.6.24.2. That is why I don't sent a dmesg ... just
cat /proc/interrupts. I can send you lspci -vv and dmesg from systemrescuecd
if you want.
Aiee.... Can you please try 2.6.25-rc8 with both configurations? And
w/o systemrescuecd? Just seeing whether things mount properly or not is
good enough. There isn't much risk of losing data.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
