[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#663269: [3.2.7 -> 3.2.9 regression] rt flavor: Hard freezes when starting KDM



Hi Jonathan,

Thank you for a fast reply.

> Can you toggle capslock, use ctrl-alt-delete or the magic sysrq key,
> or ssh into the machine in this state?

No, I can't:
* There is no any disk activity (follow indicator of front side of laptop).
* There is no any network activity. Nor ping, nor ssh don't work.
  (Devices are connected in LAN via wi-fi router)
* [Caps Lock] and [Num lock] keys produce no reaction.
* Ctrl + Alt + Delete shortcut produces no reaction.
* Alt + SysRq + R E I S U B shortcut produces no reaction.
* Alt + SysRq + H shortcut produces no reaction.

> Does a text-only (e.g., "single user mode") boot work ok?  If so,
> does running
> 
> 	dmesg >dmesg.before; startx; dmesg >dmesg.after
> 
> reveal anything interesting?

Yes, it works. startx command launched LXDE (I have both KDE and LXDE) and it
worked normally. But I finished it very quickly to avoid any system destruction.
(I think this is bad idea to use any DE with root privileges)

There was no any strange strings in dmesg output. So I type `exit' and booting
was continued. KDM was launched and system was freezed again.

> Which is the newest working version you tested?

I have latest version of packages from Debian Sid.

For example, in this system I have:

$ dpkg -l | grep linux-image | grep rt | mawk '{print $2 "\t" $3}'
linux-image-3.2.0-2-rt-686-pae  3.2.9-1
linux-image-rt-686-pae  3.2+44

$ dpkg -l | grep linux-headers | grep rt | mawk '{print $2 "\t" $3}'
linux-headers-3.2.0-2-common-rt 3.2.9-1
linux-headers-3.2.0-2-rt-686-pae        3.2.9-1
linux-headers-rt-686-pae        3.2+44

> Erm, that idea was insane.  I guess the simplest way to get diagnostic
> info from after starting X would be to look in /var/log/dmesg and
> /var/log/Xorg.0.log or /var/log/Xorg.1.log after rebooting,

Xorg.1.log was modified last time in 2011. So it is useless.
Xorg.0.log is in attachment. But I don't see any strange in it.
dmesg log is attached. But it also useless I think.
When system freezes logs are not updated...

> or to set up netconsole or serial console:
> 
>   http://www.kernel.org/doc/Documentation/networking/netconsole.txt
>   http://www.kernel.org/doc/Documentation/serial-console.txt

Hmm, it something new for me. I'll read it a little bit later.
And I'll try it if you need this for debugging.

Regards,
Boris

Attachment: Xorg.0.log
Description: Binary data

Attachment: dmesg
Description: Binary data


Reply to: