Re: Hardware bug or kernel bug?
On Monday 16 October 2006 11:25, Jarek Poplawski wrote: Was this lock-up effect visible during above 2.6.19-rc1 tests? No, I've not seen anything in Linux other than the reboots, which are instant without any preceding lock-up. If not I'd try to continue linux debbuging: - is 2.6.19-rc1 working with normal config (use make oldconfig to upgrade .config), With 2.6.19-rc1 and a normal config, I get the reboots as usual. - is 2.6.17 working with minimal config (use make oldconfig), Yes. - changing one or two options at a time try to find which one makes the effect returns (acpi, smp...). I've found the culprit - CPU Frequency Scaling. With it enabled I get the reboots, with it disabled I don't. That's the same with every kernel version I've tried (2.6.19-rc1+rc2, 2.6.17.13 Centos' 2.6.9) The system was using the p4-clockmod driver and the ondemand governor. I'm still not sure exactly what the problem is - the reboots only happen in the circumstances I've mentioned and are not triggered by changes in clock speed alone - but disabling cpufreq seems to make it go away... Thanks for your help, David. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
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 [EMAIL PROTECTED] 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 netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
