Description of problem:
During boot-up of kernel-2.6.19-1.2895 on a P4 with HT I get a call trace.
Please have a look at the attached output of dmesg.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 147273 [details]
output of dmesg
Created attachment 147282 [details]
Yet another dmesg output this time from an FC7T1 system x86_64
Attached another dmesg output, this time from an FC7T1 x86_64 system (DELL
Latitude D620 laptop).
BTW: There is no product / version for FC7T1 in Bugzilla yet.
Can you test the kernel on http://people.redhat.com/arozansk/ptytest/fc6/ and tell
me if you can reproduce the problem?
Just installed the i686 ptytest kernel on the FC6 PIV HT system. I couldn't see
the error message so far. Is there any way to trigger the error?
Created attachment 149770 [details]
This testcase (compile with gcc -lpthread -o pty_testcase pty_testcase.c)
the error much more easily on some machines. You may test this testcase with
unpatched kernel to check if it triggers then boot on the patched kernel to
Beware: this message you're hitting may cause another bigger bug that makes
impossible to allocate more ptys, thus you won't be able to open other openssh
sessions, so it's recommended it's tested in a local machine.
Ok, tested pty_testcase on 2.6.19-1.2911.6.5.fc6 (latest FC6 kernel update). On
this kernel the bug is 100% reproducible and fills /var/log/messages with call
I can't reproduce the problem on the test kernel 2.6.20-1.2922.fc6.ptytest.
ptytest keeps running with no output at all and nothing is logged to
I just checked and the fix were included on the latest FC-6 CVS kernel, so it'll
be available on the next update. If it's still reproducible on kernel versions
newer than 2.6.20-1.2925, please reopen this ticket.