control: tags -1 moreinfo C M Reinehr: > Package: linux-image-3.2.0-4-686-pae > ... > Linux 2.6.32-5-amd64
It's ambiguous: do you use 32-bit or 64-bit kernel on affected system? > the screen would become completely corrupted and the system > would freeze, requiring a power cycle hard reboot. Does it really hangs up? Maybe, it still reacts to Magic SysRq key: http://en.wikipedia.org/wiki/Magic_SysRq_key or even to <Ctrl> + <Alt> + <F1...6> combination. > Later, it sometimes would > just spontaneously reboot. > ... > I have tried different video drivers and different GUI's. What drivers & "GUIs" did you use? > The only thing that > helped was to swap out monitors, from a new one with a resolution of 1920x108 > to an older one with a resolution of 1280x1024. > ... > The video chipset is Intel Sandybrook, but > the problem occurred whether using the intel driver or the fbdev driver. It's hard to debug without some details, sorry. First of all, attach a "lspci -v" log to get exact chipset and other hardware names. Kernel error logs are welcome; try to capture dmesg log before it freezes, e. g.: dmesg > ~/dmesg_01.log If there are some error message appearing at the screen and you're unable to capture them, try to take a photo. ---- Best wishes, Bob
