public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prakash Punnoor <prakash@punnoor.de>
To: "Fatih Aşıcı" <asici.f@gmail.com>
Cc: mingo@redhat.com, manfred@colorfullife.com,
	"Linux List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc1: forcedeth, nobody cared
Date: Thu, 5 Oct 2006 23:08:57 +0200	[thread overview]
Message-ID: <200610052309.01155.prakash@punnoor.de> (raw)
In-Reply-To: <5aa69f860610051030l7323ec2el545873570052f077@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

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. 
But (I noticed this with the kernel booted with irqpoll, as well) IRQ 
balancing seems not to work anymore:

           CPU0       CPU1
  0:      53826          0   IO-APIC-edge     timer
  1:         66          0   IO-APIC-edge     i8042
  7:          0          0   IO-APIC-edge     parport0
  8:          0          0   IO-APIC-edge     rtc
  9:          0          0   IO-APIC-fasteoi  acpi
 12:       1650          0   IO-APIC-edge     i8042
 14:         63          0   IO-APIC-edge     ide0
 16:       2095          0   IO-APIC-fasteoi  nvidia
 19:          6          0   IO-APIC-fasteoi  ohci1394
 20:          0          0   IO-APIC-fasteoi  ohci_hcd:usb1
 21:         66          0   IO-APIC-fasteoi  ehci_hcd:usb2
 22:       5652          0   IO-APIC-fasteoi  libata
 23:       5105          0   IO-APIC-fasteoi  HDA Intel, eth0
NMI:        155         75
LOC:      53715      53649
ERR:          0


-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-10-05 21:09 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 [this message]
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
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=200610052309.01155.prakash@punnoor.de \
    --to=prakash@punnoor.de \
    --cc=asici.f@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=mingo@redhat.com \
    /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