[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#369167: DRI probably broken: where to reportbug



On Sun, 2006-06-04 at 17:33 +0200, Wolfgang Pfeiffer wrote:
> On Tue, May 30, 2006 at 08:32:32AM +0200, Michel Dänzer wrote:
> > On Tue, 2006-05-30 at 01:57 +0200, Wolfgang Pfeiffer wrote:
> > > On Mon, May 29, 2006 at 09:53:39AM +0200, Michel Dänzer wrote:
> > > 
> > > BTW: Is it possible to ssh into such a crashed system/machine and shut
> > > it down cleanly instead of stupidly pressing the power button I was
> > > doing so far after these crashes?
> > 
> > Depends how hard the crash is. Would be interesting to know at any rate.
> > [ ... ]
> 
> It's possible :)
> 
> But first this: I learned SSH the last days (I really didn't know
> anything about it before, except that it *somehow* might provide a way
> to access one computer with another one),  [...]

Wow, you were missing out.


> I did a 'kill -s 9 2986', after that kdm was gone, but 'top' still
> showed 'Xorg' swallowing ~99% CPU.
> 
> '/etc/init.d/x11-common status' gave me zero output, ditto a
> '/etc/init.d/xserver-xorg status'
> 
> Perhaps not being so important, but anyway:
> 
> Could someone tell me what exactly 'top' means by 'Xorg'? 

The X server.

> Because if there are other, so far unknown instances of the xorg-server I should
> know about, I'd like to try close them down instead of shutting down
> the whole system.

Not sure what you mean. If the X server process doesn't go away after
killing it, it may be spinning in kernel mode.


> Michel: Do you want to do me more tests on this alu-book around the
> time it crashes, before I try to install the DRM you suggested to try?

No, it's a hardware lockup of the graphics card, all the symptoms you
described can be explained with that, but they don't say anything about
the cause, which is extremely hard to identify after the fact.


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer




Reply to: