From: Stephen Hemminger <shemminger@osdl.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Prakash Punnoor <prakash@punnoor.de>,
Adrian Bunk <bunk@stusta.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, hnguyen@de.ibm.com, perex@suse.cz
Subject: Re: [Alsa-devel] [RFC: 2.6.19 patch] snd-hda-intel: default MSI to off
Date: Wed, 18 Oct 2006 09:01:56 -0700 [thread overview]
Message-ID: <20061018090156.1fbb1abf@freekitty> (raw)
In-Reply-To: <s5hmz7tapl5.wl%tiwai@suse.de>
On Wed, 18 Oct 2006 12:24:54 +0200
Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 17 Oct 2006 14:40:53 -0700,
> Stephen Hemminger wrote:
> >
> > On Tue, 17 Oct 2006 23:13:01 +0200
> > Adrian Bunk <bunk@stusta.de> wrote:
> >
> > > On Thu, Oct 05, 2006 at 11:08:57PM +0200, Prakash Punnoor wrote:
> > > > Am Donnerstag 05 Oktober 2006 19:30 schrieb Fatih A????c??:
> > > > > 2006/10/5, Prakash Punnoor <prakash@punnoor.de>:
> > > > > > Hi,
> > > > > >
> > > > > > subjects say it all. Without irqpoll my nic doesn't work anymore. I added
> > > > > > Ingo
> > > > > > to cc, as my IRQs look different, so it may be a prob of APIC routing or
> > > > > > the
> > > > > > like.
> > > >
> > > > > > Can you try booting with pci=nomsi ? I have a similar problem with my
> > > >
> > > > I used snd-hda-intel.disable_msi=1 and this actually helped! Now the nforce
> > > > nic works w/o problems. So it was the audio driver causing havoc on the nic.
> > > >...
> > >
> > > Unless someone finds and fixes what causes such problems, I'd therefore
> > > suggest the patch below to let MSI support to be turned off by default.
> > >
> > > cu
> > > Adrian
> > >
> >
> > It shouldn't be that hard to write a small bit of code to force an interrupt
> > and catch it, that's what other drivers do to workaround the BIOS braindamage
> > that seems to be rampant (until M$ Vista comes out and supports MSI).
>
> OK, what about a patch like below?
>
> It's against the latest ALSA tree, so please pull alsa.git from
> git://kernel.org/pub/scm/linux/kernel/git/perex/alsa.git
> before applying it (this tree includes only patches to be pushed to
> 2.6.19).
>
Looks good, I'll try it
next prev parent reply other threads:[~2006-10-18 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 7:38 2.6.19-rc1: forcedeth, nobody cared Prakash Punnoor
2006-10-05 8:03 ` Prakash Punnoor
2006-10-05 11:42 ` Gene Heskett
2006-10-05 17:34 ` Fatih Aşıcı
[not found] ` <5aa69f860610051030l7323ec2el545873570052f077@mail.gmail.com>
2006-10-05 21:08 ` Prakash Punnoor
2006-10-17 21:13 ` [RFC: 2.6.19 patch] snd-hda-intel: default MSI to off Adrian Bunk
2006-10-17 21:29 ` Randy Dunlap
2006-10-18 8:00 ` Takashi Iwai
2006-10-17 21:40 ` Stephen Hemminger
2006-10-18 10:12 ` Prakash Punnoor
2006-10-18 10:24 ` [Alsa-devel] " Takashi Iwai
2006-10-18 16:01 ` Stephen Hemminger [this message]
2006-10-18 17:02 ` Stephen Hemminger
2006-10-18 17:12 ` Takashi Iwai
2006-10-18 17:21 ` Takashi Iwai
2006-10-22 20:29 ` Prakash Punnoor
2006-10-23 12:11 ` Takashi Iwai
2006-10-31 6:56 ` Fatih Asici
2006-10-31 8:37 ` Prakash Punnoor
2006-10-18 4:16 ` Fatih Asici
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=20061018090156.1fbb1abf@freekitty \
--to=shemminger@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=hnguyen@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=perex@suse.cz \
--cc=prakash@punnoor.de \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox