Why is the bug listed against linux/3.2.39-2, when that kernel works fine? It occurs in the latest 3.2.41-2 kernel. My guess is that it is in the common KMS code, triggered by multiple display controllers, where one of the controllers is unused, but can't be disconnected, such as being on the motherboard. The system hangs up prior to the network being configured, so I have no way to log into the system. -- Barry Fishman