From: Takashi Iwai <tiwai@suse.de>
To: Daniel J Blueman <daniel@quora.org>
Cc: Dave Airlie <airlied@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [3.6-rc7] switcheroo race with Intel HDA...
Date: Tue, 09 Oct 2012 12:07:21 +0200 [thread overview]
Message-ID: <s5hr4p8ez6u.wl%tiwai@suse.de> (raw)
In-Reply-To: <s5htxu4ezc7.wl%tiwai@suse.de>
At Tue, 09 Oct 2012 12:04:08 +0200,
Takashi Iwai wrote:
>
> At Tue, 9 Oct 2012 00:34:09 +0800,
> Daniel J Blueman wrote:
> >
> > On 8 October 2012 20:58, Takashi Iwai <tiwai@suse.de> wrote:
> > > At Tue, 25 Sep 2012 13:20:05 +0800,
> > > Daniel J Blueman wrote:
> > >> On my Macbook with a discrete Nvidia GPU, there is a race between
> > >> selecting the integrated GPU and putting the discrete GPU into D3 [1],
> > >> reliably causing a kernel oops [2].
> > >>
> > >> Introducing a delay of ~1s between the calls prevents this. When the
> > >> second 'OFF' write path executes, it looks like struct azx at
> > >> card->private_data hasn't yet been allocated yet [3], so there is
> > >> likely some locking missing.
> > >
> > > It's rather pci_get_drvdata() returning NULL (i.e. card is NULL, thus
> > > card->private_data causes Oops). Could you check the patch like below
> > > and see whether you get a kernel warning (but no Oops) or the problem
> > > gets fixed by shifting the assignment of pci drvdata?
> > [...]
> >
> > Good patching. Calling pci_set_drvdata later prevents the oops in HDA,
> > though we see unexpected 0x0 responses in the response ring buffer
> > [1], which we don't see when there's a >~1.5s delay between IGD and
> > OFF.
>
> If the previous patch fixed, it means that the switching occurred
> during the device was being probed. Maybe a better approach to
> register the VGA switcheroo after the proper initialization.
>
> The patch below is a revised one. Please give it a try.
Also, it's not clear which card spews the spurious response.
Apply the patch below in addition.
thanks,
Takashi
---
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index f09ff6c..9a0a29d 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -829,8 +829,9 @@ static void azx_update_rirb(struct azx *chip)
smp_wmb();
chip->rirb.cmds[addr]--;
} else
- snd_printk(KERN_ERR SFX "spurious response %#x:%#x, "
+ snd_printk(KERN_ERR SFX "%s: spurious response %#x:%#x, "
"last cmd=%#08x\n",
+ pci_name(chip->pci),
res, res_ex,
chip->last_cmd[addr]);
}
next prev parent reply other threads:[~2012-10-09 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 5:20 Daniel J Blueman
2012-10-08 12:58 ` Takashi Iwai
2012-10-08 16:34 ` Daniel J Blueman
2012-10-09 10:04 ` Takashi Iwai
2012-10-09 10:07 ` Takashi Iwai [this message]
2012-10-09 11:23 ` Daniel J Blueman
2012-10-09 13:04 ` Takashi Iwai
2012-10-09 14:26 ` Daniel J Blueman
2012-10-10 12:34 ` Takashi Iwai
2012-10-12 15:08 ` Daniel J Blueman
2012-10-12 15:26 ` Takashi Iwai
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=s5hr4p8ez6u.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=airlied@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@quora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®