mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Teodor Iacob <Teodor.Iacob@astral.ro>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel E1000 and IDE problems
Date: Thu, 20 Nov 2003 08:32:31 +0200	[thread overview]
Message-ID: <20031120063231.GD19239@speedy.b.astralnet.ro> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102CBDCE4@orsmsx402.jf.intel.com>

I put them at first on the same slots.. then I changed the slots to see if the trouble goes away
and got the same results. There are no shared interrupts. At this moment at PCI Device Listing
I get the NICs on irq 10 and 11, the 1st IDE on 14 and VGA on 15 ( the 2nd IDE is disabled )

I disabled DMA on ide ( with hdparm -d 0 /dev/hda ), but now I see after a few hours of traffic
going through this machine errors in logs like hell:
end_request: I/O error, dev 03:02 (hda), sector 16515104
end_request: I/O error, dev 03:02 (hda), sector 16777248
end_request: I/O error, dev 03:03 (hda), sector 524344
end_request: I/O error, dev 03:03 (hda), sector 7864352
end_request: I/O error, dev 03:03 (hda), sector 14155920
end_request: I/O error, dev 03:03 (hda), sector 524320


vmstat 1 shows like this:
 0  0  0      0 343764  38464  35004   0   0     0     0 5901  1025   0  26  74
 0  0  0      0 343756  38472  35004   0   0     0     8 5919   906   0  30  70
 0  0  0      0 343756  38472  35004   0   0     0     0 5712   915   0  30  70
 0  0  1      0 343756  38472  35004   0   0     0     0 5641   929   0  28  72


00:09.0 Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
        Subsystem: Intel Corp. PRO/1000 MT Server Adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (63750ns min), cache line size 08
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at e2c00000 (64-bit, non-prefetchable) [size=128K]
        Region 4: I/O ports at d000 [size=64]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [e4] PCI-X non-bridge device.
                Command: DPERE- ERO+ RBC=0 OST=0
                Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
        Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000

00:0b.0 Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
        Subsystem: Intel Corp. PRO/1000 MT Server Adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (63750ns min), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at e2c20000 (64-bit, non-prefetchable) [size=128K]
        Region 4: I/O ports at d400 [size=64]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [e4] PCI-X non-bridge device.
                Command: DPERE- ERO+ RBC=0 OST=0
                Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-
        Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000


Btw.. I don't know what you mean on the same bus segment.

On Wed, Nov 19, 2003 at 07:02:27PM -0800, Feldman, Scott wrote:
> > I recently put up 2 intel network adapters:
> > 00:09.0 Ethernet controller: Intel Corp. 82545EM Gigabit 
> > Ethernet Controller (Copper) (rev 01)
> > 00:0b.0 Ethernet controller: Intel Corp. 82545EM Gigabit 
> > Ethernet Controller (Copper) (rev 01)
> > 
> > ( I replaced some Intel PRO1000 Desktop which I had before ) and now
> > I get serious problems with the hda disk:
> 
> Did you put the 82545 nics in the same slots where you had the desktop
> nics?
> 
> Are the 82545 nics on the same bus segment as the disk controller?  Are
> there any shared interrupts?  See lcpci -vvv.
> 
> -scott
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
      Teodor Iacob,
Manager Infrastructura Nationala
Astral Telecom Internet

  reply	other threads:[~2003-11-20  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  3:02 Feldman, Scott
2003-11-20  6:32 ` Teodor Iacob [this message]
2003-11-20 11:22 ` Teodor Iacob
2003-11-20 12:45   ` Teodor Iacob
2003-11-20 13:46     ` Teodor Iacob
  -- strict thread matches above, loose matches on Subject: below --
2003-11-19 12:02 Teodor Iacob

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=20031120063231.GD19239@speedy.b.astralnet.ro \
    --to=teodor.iacob@astral.ro \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@intel.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

all inboxes | Powered by JetHome®