linux-kernel - Re: [patch] ohci1394: don't leave interrupts enabled during suspend/resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Dec 2008 22:46:51 +0100
From:	Frans Pop <elendil@...net.nl>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Robert Hancock <hancockr@...w.ca>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] ohci1394: don't leave interrupts enabled during suspend/resume

On Wednesday 10 December 2008, Stefan Richter wrote:
> Frans Pop wrote:
> > Any suggestions how to try and trace if that's what's happening?
>
> Test after booting with the kernel parameter nomsi.

With pci=nomsi I still get the same "irq 19: nobody cared".

The devices that normally get MSI now get assigned as follows:
- pcieport-driver: IRQ 16 and 17
- iwlagn: irq 17
- e1000e: irq 22

ohci1394 remains the only driver at irq 19.

Except for the changes due to the nomsi option I see no significant 
changes in dmesg for boot plus one suspend/resume cycle.
--
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/