linux-kernel - X unusable rebooting with kexec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 4 Aug 2011 12:41:03 -0300 (BRT)
From:	Frédéric L. W. Meunier 
	<fredlwm@...dlwm.net>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: X unusable rebooting with kexec

For the first time I used kexec, and decided to test it to reboot from 
3.0.0 to 3.0.1-rc1. Apparently, all went well until startx. As soon as 
my window manager appeared, the graphics were so corrupt and didn't show 
any text, that the only solution was to reboot, after retrying startx a 
few times. I also tried kexec a second time, rebooting the same 
3.0.1-rc1 kernel, with no luck.

Doing a diff against both dmesg, I noticed the following changes:

MTRR variable ranges enabled:
...
-  2 disabled
+  2 base 00D0000000 mask FFF0000000 write-combining

pci 0000:01:00.0: Boot video device
-PCI: CLS 4 bytes, default 64
+PCI: CLS mismatch (4 != 32), using 64 bytes

What can I do, if anything, to find the cause of this corruption and 
make kexec work as expected ?

The video card is a Radeon HD 5450.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/