From: David Johnson <dj@david-web.co.uk>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: Hardware bug or kernel bug?
Date: Fri, 13 Oct 2006 17:24:39 +0100 [thread overview]
Message-ID: <200610131724.40631.dj@david-web.co.uk> (raw)
In-Reply-To: <20061013130648.GC1690@ff.dom.local>
On Friday 13 October 2006 14:06, Jarek Poplawski wrote:
>
> Probably - but only with networking. So I'd try with this debugging
> like in my first reply plus maybe 2.6.19-rc1 (e1000 - btw. I hope
> this other tested card was different model - and locking improved)
> and resend conclusions to netdev@vger.kernel.org.
>
OK I built a 2.6.19-rc1 kernel with a minimal config as you describe and I
cannot reproduce the reboots with this kernel. My .config:
http://www.david-web.co.uk/download/config
The other NIC I tried was a D-Link DL10050-based card which I think uses the
dl2k module.
I tried to reproduce the problem under Windows (2k), which didn't reboot but
did still suffer from it I believe. Randomly during an scp transfer (using
the PuTTY scp client) Windows will lock-up for about 30 seconds, making an
entry in the event log indicating that there was a time-out talking to the
IDE controller, then continuing. Could the same thing be happening in Linux?
If Linux can't talk to the IDE controller when trying to write to disk, how
does it handle that?
Regards,
David.
next parent reply other threads:[~2006-10-13 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061013085605.GA1690@ff.dom.local>
[not found] ` <200610131256.54546.dj@david-web.co.uk>
[not found] ` <20061013130648.GC1690@ff.dom.local>
2006-10-13 16:24 ` David Johnson [this message]
2006-10-13 17:11 ` Hardware bug or kernel bug? Alan Cox
2006-10-16 10:25 ` Jarek Poplawski
2006-10-16 14:32 ` David Johnson
2006-10-17 7:10 ` Jarek Poplawski
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=200610131724.40631.dj@david-web.co.uk \
--to=dj@david-web.co.uk \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).