On Saturday, 23 April 2011 19:09:30 -0300, Daniel Bareiro wrote: > > > Here I found a thread [1] with a problem quite like this (although > > > in my case the hardware is different: A8V-MX motherboard and AMD > > > Athlon 64 Processor 3500+) in the xen-users mailing list. And > > > another thread [2] which is derived from the above. > > > > > > I'll try using "cpuidle=off" or "max_cstate=1" at xen cmdline in > > > /boot/grub/grub.conf. > > It's probably worth trying cpuidle=off but it looks like the > > max_cstate=1 thing is Intel specific. It's not clear to me in either > > case if the root cause of the issue this fixes is a h/w or s/w > > issue. > > Using "cpuidle=off" and xen-hypervisor-4.0-amd64 package had no > effect. After an uptime of 20:26:44, everything became frozen again. > Now I'm trying with the "max_cstate=1" option. > > This time there was no visual evidence in the disk activity LED when > the problem occurred, but I do not see revealing information in system > logs. > > Do you have irqbalanced installed/running? > No, I'm not using irqbalance. This is a uniprocessor system (AMD > Athlon(tm) 64 Processor 3500+ with A8V-MX motherdoard). Using "max_cstate=1" it did not have effect either. What I observed on several occasions is that when making a rsync or scp of several Gigabytes, the computer froze. The loss of network connection made me think that it might be a problem with the network card, but from the moment the screen also stops responding if I connect a monitor to the computer, this makes me think that perhaps there is some other problem. But it seems the problem could be linked to high network transfer rate. Regards, Daniel -- Daniel Bareiro - GNU/Linux registered user #188.598 Proudly running Debian GNU/Linux with uptime: 01:59:15 up 15 days, 11:55, 10 users, load average: 0.08, 0.04, 0.00
Attachment:
signature.asc
Description: Digital signature