On Mon, Oct 16, 2006 at 03:32:38PM +0100, David Johnson wrote:
...
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
On Fri, Oct 13, 2006 at 05:24:39PM +0100, David Johnson wrote:
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
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
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
Ar Gwe, 2006-10-13 am 17:24 +0100, ysgrifennodd David Johnson:
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?
It will timeout and then retry the command. It's not
