All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] ohci1394: don't leave interrupts enabled during suspend/resume
Date: Wed, 10 Dec 2008 22:46:51 +0100	[thread overview]
Message-ID: <200812102246.52798.elendil@planet.nl> (raw)
In-Reply-To: <49402CBD.9020706@s5r6.in-berlin.de>

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.

  reply	other threads:[~2008-12-10 21:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 12:16 ohci1394: "irq 19: nobody cared" during resume from suspend to ram Frans Pop
2008-12-06 13:11 ` Stefan Richter
2008-12-06 13:37   ` Frans Pop
2008-12-06 14:36 ` [patch] ohci1394: don't leave interrupts enabled during suspend/resume Frans Pop
2008-12-06 16:12   ` Stefan Richter
2008-12-06 21:03   ` Robert Hancock
     [not found]     ` <tkrat.fd592eed61e41b8f@s5r6.in-berlin.de>
2008-12-07  3:28       ` Robert Hancock
2008-12-07  9:19         ` Stefan Richter
2008-12-07 18:57           ` Robert Hancock
2008-12-10 13:24             ` Frans Pop
2008-12-10 20:55               ` Stefan Richter
2008-12-10 21:46                 ` Frans Pop [this message]
2008-12-10 22:25                   ` Stefan Richter
2008-12-11 16:02                     ` Frans Pop
2008-12-10 13:23           ` Frans Pop

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=200812102246.52798.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.