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

Bug#279698: x-window-system and drm bug



retitle 279698 xlibmesa-dri: [i830_dri] causes lockup on system shutdown
reassign 279698 xlibmesa-dri
tag 279698 + upstream moreinfo
thanks

On Thu, Nov 04, 2004 at 01:51:02PM -0500, ejd wrote:
> Package:  x-window-system

This wasn't the right package to file this bug against.  x-window-system is
a dummy package.

Package: x-window-system
[...]
Version: 4.3.0.dfsg.1-8
Depends: x-window-system-core, lbxproxy, proxymngr, twm, xdm, xfs, xfwp, xnest, xprt-xprintorg, xterm, xvfb
Description: X Window System
 This metapackage provides substantially all the components of the X Window
 System as developed by the XFree86 Project, as well as a set of historically
 popular accessory programs.
 .
 Development and debugging versions of the X protocol client libraries and
 other libraries provided with XFree86 are not provided by this metapackage.
 .
 Note that Xprint.org's implementation of an XPRINT server is depended upon
 by this package until XFree86's XPRINT server is operational.

> Every time I have a hardware reboot the machine (Dell with an i845 Extreme 
> Graphics Accellerator) locks up.  I am running kernel-image-2.4.27-1-686 and 
> libc6 version 2.3.2.ds1-18.
> 
> Oddly enough shutting the machine off and letting fsck remount the screwed up 
> filesystem seems to "fix" the problem.  It's locked up twice in a row the 
> same way, and in just the same way trying to start it again has worked both 
> times.  I'm not going to be shutting it off much any more so I don't know how 
> consistent that behavior will be...
> 
> Also I am sure that it didn't start right after I got the new version of 
> x-window-system going.  Anyway, here are the relevent logs.  I will also 
> submit a report to the XFree people.

I have a couple of questions:

1) Why do you suppose this is not a bug in the Linux kernel's i830 DRM
   driver?

2) Does this problem go away if you remove the xlibmesa-dri package?
   It sounds like you'll have to reboot the machine and cope with the
   lockup one more time after removing it to truly diagnose this
   workaround.

-- 
G. Branden Robinson                |     Never attribute to conspiracy that
Debian GNU/Linux                   |     which can be adequately explained
branden@debian.org                 |     by economics.
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature


Reply to: