public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	Prakash Punnoor <prakash@punnoor.de>,
	mingo@redhat.com, linux-kernel@vger.kernel.org,
	Stephen Hemminger <shemminger@osdl.org>,
	perex@suse.cz, alsa-devel@alsa-project.org, hnguyen@de.ibm.com
Subject: Re: [RFC: 2.6.19 patch] snd-hda-intel: default MSI to off
Date: Wed, 18 Oct 2006 10:00:09 +0200	[thread overview]
Message-ID: <s5h4pu25a0m.wl%tiwai@suse.de> (raw)
In-Reply-To: <20061017142957.b4f0c1fe.randy.dunlap@oracle.com>

At Tue, 17 Oct 2006 14:29:57 -0700,
Randy Dunlap wrote:
> 
> On Tue, 17 Oct 2006 23:13:01 +0200 Adrian Bunk 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.
> 
> MSI works with my sound, ethernet, and SATA:
> 
>  66:    1131814          0         PCI-MSI  libata
>  98:      89556          0         PCI-MSI  HDA Intel
> 106:     943530          0         PCI-MSI  eth0
> 
> so maybe this should be done for nforce chipsets or
> whatever is seeing the problem?

I agree that this is pretty much depending on the hardware, so
disabling all might be exaggerated.
The sound with MSI works on all of my test machines with Intel
chipset, so far.


Takashi

  reply	other threads:[~2006-10-18  8:00 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 [this message]
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
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=s5h4pu25a0m.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --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=randy.dunlap@oracle.com \
    --cc=shemminger@osdl.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