Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 227203

Summary: idr_remove called for id=0 which is not allocated.
Product: [Fedora] Fedora Reporter: Bernd Bartmann <bernd.bartmann>
Component: kernelAssignee: Aristeu Rozanski <arozansk>
Status: CLOSED NEXTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: arozansk, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-12 15:05:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
output of dmesg
none
Yet another dmesg output this time from an FC7T1 system x86_64
none
testcase none

Description Bernd Bartmann 2007-02-03 14:29:15 UTC
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):
kernel-2.6.9-1.2895

How reproducible:


Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bernd Bartmann 2007-02-03 14:29:16 UTC
Created attachment 147273 [details]
output of dmesg

Comment 2 Bernd Bartmann 2007-02-03 21:02:54 UTC
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.

Comment 3 Aristeu Rozanski 2007-03-09 20:36:50 UTC
Can you test the kernel on http://people.redhat.com/arozansk/ptytest/fc6/ and tell
me if you can reproduce the problem?
Thanks,


Comment 4 Bernd Bartmann 2007-03-10 11:11:06 UTC
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?

Comment 5 Aristeu Rozanski 2007-03-10 14:26:27 UTC
Created attachment 149770 [details]
testcase

This testcase (compile with gcc -lpthread -o pty_testcase pty_testcase.c)
triggers
the error much more easily on some machines. You may test this testcase with
your
unpatched kernel to check if it triggers then boot on the patched kernel to
verify.

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.

Comment 6 Bernd Bartmann 2007-03-10 19:36:49 UTC
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
traces.

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
/var/log/messages.



Comment 7 Aristeu Rozanski 2007-03-12 15:05:48 UTC
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.
Thanks