Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Packard Bell F2011HC-125GE running a Debian Squeeze-based Linux.

After a few days of usage i found the system freezes from time to time. It's obvious the freezes happen, when X starts while another terminal is active(e.g. tty1).

Some scenarios are: -Suspending while in text-terminal (e.g. ctrl+alt+f2). This includes freezing when closing the lid. On resume the screensaver from tty7 is showing, but doesn't react to input. Sometimes it is still possible to switch to another terminal and do something like 'echo 1 > /dev/tty7' and switch back with ctrl+alt+f7. Then input is possible. Though, most of the time it's completely frozen.

-Choosing to logout from KDE-session and switching instantly to ttyX < 7. Then input works for a few seconds before it switches to the KDE-login-screen but doesn't react to input anymore. In that case the power-button does still work and i am able to shut down. When i logout and wait for the login-screen to be ready i am able to switch tty without problems.

-X crashes while ttyX<7 is active. No switch-back. Can only hold power button and reset. I'm able to see crashes in log-file. Reasons are unimportant for this matter. Freezes occur whatever the reason is.

This does not happen when tty7,8 is active while X crashes. Also, i can startx from terminal, wait and everything works fine.

My chipset is HM77-7 Series (Intel) and some of my hardware is not supported by ACPI/ALSA from the debian-repo. I've backported 3.2 with the same issue, customized 3.6.6, which works better than both debian-repo kernels, but still with the issues mentioned above. I'm currently trying to use 3.7.1, but i have with problems with ath9k (wireless-module) being present in both kernel in userspace, same with ntfs. (I dont want to use FUSE). The X-problems seem to be the same with whatever kernel.

How do i find what the source of the problem is? Where do i look? udev? X? I can't image it being the kernel, because somebody else must have noticed; Though, i'm sure it's some kind of problem with input-redirection.

I am sorry for the long text, hope not to bother you too much with a rather specific problem and would really appreciate any kind of hint or help.


share|improve this question
Post a link to your /var/log/Xorg.0.log for starters? – user13742 Jan 15 '13 at 15:06
Try compiling a kernel without any ACPI support. This may mean you have to yank the battery to turn it off, but at least you can then eliminate one of the more likely candidates (if the problem is still the same). – goldilocks Jan 15 '13 at 15:31
@goldilocks, that is overkill. acpi=off as kernel parameter on boot should be enough. – vonbrand Jan 24 '13 at 14:18
What graphics card has that machine? What graphics driver are you using, what kernel version? A while back there were recurrent hangs with nVidia and nouveau. If you have an oldish kernel/installation, perhaps updating fixes your woes? – vonbrand Jan 24 '13 at 14:20
Xorg.0.log does not yield any information, it thinks its waiting for input. – Banyoghurt Jan 25 '13 at 14:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.