Hi Boris,

Boris Pek wrote:

> During launching KDM system freezes and don't react of anything.
> Only reset solves the problem.

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

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? Does the X fbdev driver behave any
better? (See [1] for details on setting it up.)

[...]
> Previous kernels linux-image-3.2.0-1-rt-* work fine for me on all
> these devices.

Which is the newest working version you tested?

Thanks for an interesting report, and hope that helps.

Sincerely,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120309234503.GB1965@burratino">http://lists.debian.org/20120309234503.GB1965@burratino

Jonathan Nieder wrote:

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

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, 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

Sorry for the nonsense.
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120309235933.GC1965@burratino">http://lists.debian.org/20120309235933.GC1965@burratino

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 " " $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 " " $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

> Which is the newest working version you tested?

Sorry I missed the word `working'. Unfortunately, I don't remember this.
It was the latest version of linux-image-3.2.0-1-rt-686-pae package just
before it was deleted from Sid.

Regards,
Boris

severity 663379 important
merge 663269 663379
quit

Boris Pek wrote:

> startx command launched LXDE (I have both KDE and LXDE) and it
> worked normally.

Thanks --- this is a very useful detail. So probably non-accelarated
rendering works fine, and it is something in 3d codepaths that makes it
freeze.

> dmesg log is attached. But it also useless I think.
> When system freezes logs are not updated...

The attached log seems to be for a boot with the non-rt kernel. Am I
understanding correctly?

Ciao,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120311151348.GA3866@burratino">http://lists.debian.org/20120311151348.GA3866@burratino

Hi,

> > startx command launched LXDE (I have both KDE and LXDE) and it
> > worked normally.
>
> Thanks --- this is a very useful detail. So probably non-accelarated
> rendering works fine, and it is something in 3d codepaths that makes it
> freeze.

Ok. I saw interesting instructions in bug report #663379. Could I help in
a same way? I can build kernel (or few modules) with patches for tests.
Today I have a little free time for this. But I have only 32 system for tests...

> > dmesg log is attached. But it also useless I think.
> > When system freezes logs are not updated...
>
> The attached log seems to be for a boot with the non-rt kernel. Am I
> understanding correctly?

Yes, you are right. Sorry, but I don't know how I can get logs from previous
boot. As I wrote earlier /var/log/Xorg.1.log is outdated.

Regards,
Boris

Uwe Kleine-König wrote:

> I could reproduce your issue and commited a patch that fixes the issue
> for me.

Thanks! FWIW, the patch makes sense to my undertrained eyes.

aufs is used by debian-live rather than the installer. I'm not sure
if there's much interest in a livecd with the realtime kernel on it or
not (my guess would be "not").

> If you're impatient, you can build from svn:
>
> apt-get builddep linux-2.6
> wget http://ftp.cz.debian.org/debian/pool/main/l/linux-2.6/linux-2.6_3.2.9.orig.tar.gz
> tar xzf linux-2.6_3.2.9.orig.tar.gz
> cd linux-2.6-3.2.9
> svn export svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6/debian debian

.../dists/sid/...

> debian/rules debian/control
> make -j4 -f debian/rules.gen build_amd64_rt_amd64 DEBIAN_KERNEL_USE_CCACHE=1
> fakeroot make -f debian/rules.gen binary-arch_amd64_rt_amd64

Cheers,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120311165121.GD3586@burratino">http://lists.debian.org/20120311165121.GD3586@burratino

On Sun, Mar 11, 2012 at 07:37:51PM +0400, Boris Pek wrote:
> Hi,
>
> > > startx command launched LXDE (I have both KDE and LXDE) and it
> > > worked normally.
> >
> > Thanks --- this is a very useful detail. So probably non-accelarated
> > rendering works fine, and it is something in 3d codepaths that makes it
> > freeze.
>
> Ok. I saw interesting instructions in bug report #663379. Could I help in
> a same way? I can build kernel (or few modules) with patches for tests.
> Today I have a little free time for this. But I have only 32 system for tests...
>
> > > dmesg log is attached. But it also useless I think.
> > > When system freezes logs are not updated...
> >
> > The attached log seems to be for a boot with the non-rt kernel. Am I
> > understanding correctly?
>
> Yes, you are right. Sorry, but I don't know how I can get logs from previous
> boot. As I wrote earlier /var/log/Xorg.1.log is outdated.

Maybe check /var/log/Xorg.0.log.old (logs between Xorg.0.log and Xorg.1.log)?



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120311211752.GA22162@tiikeri.vuoristo.local">htt p://lists.debian.org/20120311211752.GA22162@tiikeri.vuoristo.local

Hi,

I rebuilt package with new patch in my 32-bit system and can confirm
that the problem is solved. Thanks!

Regards,
Boris