Issue 482 in xmonad: Full system freeze
Status: New Owner: ---- New issue 482 by witsqu...@lavabit.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 What steps will reproduce the problem? 1. Run xmonad with nvidia graphics card is the only know constant 2. 3. What is the expected output? What do you see instead? The system completely freezes, no response to keyboard or mouse input, cannot switch TTYs. Cannot SSH into the machine. This does not occur for me in other WMs (openbox, xfce). What version of the product are you using? On what operating system? 0.9.2 from cabal on Archlinux. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. There are a number of users on the Arch forum experiencing this same issue. The bug may be in xorg, but only xmonad users are getting this issue, so I wanted to notify you guys and see if we can get your input on this. https://bbs.archlinux.org/viewtopic.php?id=129439
Comment #1 on issue 482 by norbert....@gmail.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 I'm running xmonad on nvidia on arch, too, without problems, at least so far. There's currently quite some chatter on the archlinux mailing list about lockups using the 3.1 kernel and other graphics-related issues that cropped up after upgrade to the latest kernel. I would in general expect that a graphics-related complete system freeze has its causes somewhere deeper in the system stack, in the interaction between the display driver and the kernel.
Comment #2 on issue 482 by allber...@gmail.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 Agreed; xmonad can't cause a system hang all by itself, but it's been known to tickle bugs in various display drivers (most notably the proprietary Nvidia drivers).
Comment #3 on issue 482 by norbert....@gmail.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 ...in which case it still makes no sense to report this as an issue against xmonad, particularly following the discussion on the referenced archlinux thread. If the brakes in your car don't work (car = display driver), you'd get the brakes fixed instead of advising people to find alternate means of stopping.
Comment #4 on issue 482 by daniel.w...@gmail.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 Errr... I find your analogy lacking. If you found out the brakes don't work, you wouldn't tell the mechanic that the problem was that you couldn't stop while turning left and therefore the steering wheel was broken. If the display driver is broken, no change to xmonad can fix that.
Comment #5 on issue 482 by witsqu...@lavabit.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 Look if the bug report is the wrong place for this, I'm sorry. However, I think it is of concern to xmonad due to the fact that many users see this in xmonad exclusively, regardless of the source of the issue (xorg, nvidia or otherwise). I'm not saying xmonad is the root cause, but perhaps it is triggering a bug elsewhere that other WMs do not. Is that not of interest to xmonad devs? If there's a better venue to discuss this then please close this bug. I wanted to alert the community of a problem with a growing number of me toos.
Comment #6 on issue 482 by daniel.w...@gmail.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 Thanks for the report. I wasn't intending to discourage serious discussion of the problem, its repercussions, and what to do about it. It also turns out I misunderstood the comment I was replying to. Going forward, it's a bit tough to identify what we can do to make the experience better. Do you have a good way of reproducing the problem on demand? Perhaps if you do we can find exactly what it is that xmonad does that confuses the display driver and work out a way to avoid doing that for people with broken drivers (until the drivers are fixed, of course =).
Comment #7 on issue 482 by witsqu...@lavabit.com: Full system freeze http://code.google.com/p/xmonad/issues/detail?id=482 I'm going to see what I can do to isolate it over the weekend.
participants (1)
-
codesite-noreply＠google.com