On 10/26/05, Dave Airlie <[email protected]> wrote: > > If anyone has an idea on what to do to try and reproduce > > and/or debug further, that'd be cool. > > > > Box is a Dell Latitude C640 laptop, [email protected], > > 1GB RAM, with a USR2210 802.11b wireless > > PC Card; video card is a Radeon 7500 M7 LW. > > > > Your getting an X hang which is usually a DRM/AGP or X configuartion problems.. > > Please send me your /etc/X11/xorg.conf and /var/log/Xorg.0.log after a hang.. > > did it work with any kernel before? and suddenly break recently? It's intermittent. It looks like more recent kernels have a tendency to trigger it more easily - in fact I just happened to have another occurrence, this time without even loading the acx driver, just 1. boot 2. login as non-root 3. startx but it works most times. I lied however - the keyboard is _not_ dead, despite not lighting the CapsLock led, and I can Alt-SysRQ-<x>. Luckily, I have both the current working Xorg.0.log and the one coming from the hang. I'm attaching both, and my xorg.conf. Thanks :) --alessandro "All it takes is one decision A lot of guts, a little vision to wave Your worries, and cares goodbye" (Placebo - "Slave To The Wage")
Attachment:
xorg.conf
Description: Binary data
Attachment:
Xorg.0.log.good
Description: Binary data
Attachment:
Xorg.0.log.bad
Description: Binary data
- Follow-Ups:
- References:
- Prev by Date: Re: sata_nv + SMP = broken?
- Next by Date: Re: [PATCH] fix alpha breakage
- Previous by thread: Re: X unkillable in R state sometimes on startx , /proc/sysrq-trigger T output attached
- Next by thread: Re: X unkillable in R state sometimes on startx , /proc/sysrq-trigger T output attached
- Index(es):
 |