From: Teodor Iacob <Teodor.Iacob@astral.ro>
To: linux-kernel@vger.kernel.org
Subject: Intel E1000 and IDE problems
Date: Wed, 19 Nov 2003 14:02:02 +0200 [thread overview]
Message-ID: <20031119120202.GD15974@speedy.b.astralnet.ro> (raw)
Hello,
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:
Nov 19 12:42:28 firelog2 kernel: hda: status timeout: status=0x82 { Busy }
Nov 19 12:42:28 firelog2 kernel:
Nov 19 12:42:28 firelog2 kernel: hda: DMA disabled
Nov 19 12:42:28 firelog2 kernel: hda: drive not ready for command
Nov 19 12:42:33 firelog2 kernel: ide0: reset: success
Nov 19 12:43:53 firelog2 kernel: hda: status timeout: status=0x80 { Busy }
Nov 19 12:43:53 firelog2 kernel:
Nov 19 12:43:53 firelog2 kernel: hda: drive not ready for command
Nov 19 12:43:54 firelog2 kernel: ide0: reset: success
Nov 19 12:46:19 firelog2 kernel: hda: status timeout: status=0x80 { Busy }
Nov 19 12:46:19 firelog2 kernel:
Nov 19 12:46:19 firelog2 kernel: hda: drive not ready for command
Nov 19 12:46:19 firelog2 kernel: ide0: reset: success
>From time to time I cannot even boot the system ( even the e1000 module
is not loaded )
The kernel version is 2.4.22 and the intel driver version is : 5.2.20
( I was using the same intel driver and the same kernel version before with
Intel PRO1000 Desktop adapter )
Can anybody help me track down this? to see if it's something hardware related,
only software... is it DMA related?
Teo
next reply other threads:[~2003-11-19 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 12:02 Teodor Iacob [this message]
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
2003-11-20 13:46 ` 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=20031119120202.GD15974@speedy.b.astralnet.ro \
--to=teodor.iacob@astral.ro \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®