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 14:45:35 +0200	[thread overview]
Message-ID: <20031120124535.GA32427@speedy.b.astralnet.ro> (raw)
In-Reply-To: <20031120112217.GA22057@speedy.b.astralnet.ro>

One more thing to add:

After a few of those kind of freezes the BIOS won't even recognize the
Harddisk anymore, I had to turn on the machine without the harddisk in it
then I forced the bios to update ESCD and the put back the harddrive in it
and worked. Somehow those cards affect the system anyway. ( even only in
CMOS setup )

On Thu, Nov 20, 2003 at 01:22:17PM +0200, Teodor Iacob wrote:
> I found something really interesting. I am now able to reproduce problems 
> exactly at the same point:
> 
> If I boot the machine without ethernet cables connected before loading
> the kernel the machine seems to work fine for a while. If I put for
> example a crossover cable between the cards I cannot even boot the system!
> right after the kernel initialization after it starts the init I get
> IDE errors and then freezes because it cannot run the commands in
> rc.sysinit.
> 
> I have to mention I also tried the built-in driver of intel e1000.
> The 5.2.20 of course it was loaded as a module at network scripts
> initialization.
> 
> So the problems trims down to how can those NICs can affect the IDE
> only when they have cables connected ( even though without the driver
> initialization they don't have the led link on ) even without traffic
> going through them.
> 
> 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 12:45 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
2003-11-20 11:22 ` Teodor Iacob
2003-11-20 12:45   ` Teodor Iacob [this message]
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=20031120124535.GA32427@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®