[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A014F53.9000701@gmail.com>
Date: Wed, 06 May 2009 10:50:27 +0200
From: Jiri Slaby <jirislaby@...il.com>
To: Shaohua Li <shaohua.li@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"arjan@...radead.org" <arjan@...radead.org>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>
Subject: Re: kexec defunct -- sd-async-shutdown [mmotm 2009-04-30-17-55]
On 05/06/2009 02:51 AM, Shaohua Li wrote:
> On Tue, May 05, 2009 at 05:36:17PM +0800, Jiri Slaby wrote:
>> On 05/01/2009 02:55 AM, akpm@...ux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2009-04-30-17-55 has been uploaded to
>> ...
>>> sd-async-shutdown.patch
>> Hi,
>>
>> this one causes kexec to hang.
> Can you give more info about the hang, like the log? Is patch
> synchronize-device-shutdown.patch applied? kexec takes the same way
> to shutdown device, so does shutdown work in the system?
Ah, I though it silently hangs, but no, I had forgotten to switch a
logging console. There is nobody-cared interrupt 19 followed by plenty
of sata ports resets. The same happens on reboot.
According to /proc/interrupts, irq 19 is usb specific:
19: 0 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
But ahci enables the legacy one at 19 too:
ahci 0000:00:1f.2: version 3.0
alloc irq_desc for 19 on cpu 0 node 0
alloc kstat_irqs on cpu 0 node 0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
alloc irq_desc for 27 on cpu 0 node 0
alloc kstat_irqs on cpu 0 node 0
ahci 0000:00:1f.2: irq 27 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports ? Gbps 0x3f impl SATA
mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pmp pio slum part ems
ahci 0000:00:1f.2: setting latency timer to 64
Is this that ahci frees msi and interrupts at all at the shutdown stage
and you "schedule" and wait for an interrupt afterwards? (And then the
interrupt comes, but usb says: no, it's not mine.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists