On Mit, 2002-10-30 at 05:01, John Goerzen wrote: > > I tried downgrading to 4.2.1-1 (from 4.2.1-3) to see if that would improve > matters. It apparently did not, although after one sleep my mouse alone > remained responsive. > > However, I discovered that the machine was still listening on its airport > interface and was able to log in and do some more debugging. > > It turns out that when X throws one of these fits, it's spinlocking. > Running strace on it yields this sort of result, repeated over and over: > > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > --- SIGALRM (Alarm clock) --- > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > --- SIGALRM (Alarm clock) --- > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > ioctl(6, 0x20006444, 0) = -1 EBUSY (Device or resource busy) > > Now, looking at the X server process, I see that fd 6 is attached to > /dev/dri/card0. Maybe a clue.
As discussed many times on the debian-powerpc list, make sure APM emulation is enabled in the kernel, that /dev/apm_bios exists and that the X server log contains contains a line (II) Open APM successful Failing that, the X server can't react to the sleep cycle, and you need to switch to console for sleep. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]