lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 Oct 2006 17:24:39 +0100 From: David Johnson <dj@...id-web.co.uk> To: Jarek Poplawski <jarkao2@...pl> Cc: Linux Kernel <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org Subject: Re: Hardware bug or kernel bug? 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@...r.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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists