Re: WARNING: at drivers/tty/tty_ldisc.c:766 tty_ldisc_reinit+0x52/0x90()[3.0]

[Dave Young]

On Fri, Sep 2, 2011 at 4:59 AM, Jiri Slaby <jslaby@xxxxxxx> wrote:
> On 08/28/2011 03:15 PM, Dave Jones wrote:
>>
>> Just saw this on a box that was recieving an rsync while I ssh'd in.
>> The ssh session hung.
>
> Yes, could you apply the attached debug patch and post a dmesg output?

I see this problem as well, the debug patch reports the refcount is 2

You can produce the WARN as below:
in xterm run:

exec 0<>/dev/console 1<>/dev/console 2<>/dev/console

>
>> WARNING: at drivers/tty/tty_ldisc.c:766 tty_ldisc_reinit+0x52/0x90()
>> Hardware name:
>> Modules linked in: nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc
>> p4_clockmod freq_table speedstep_lib nf_conntrack_ipv4 nf_defrag_ipv4
>> xt_state nf_conntrack microcode serio_raw snd_hda_codec_realtek i2c_i801
>> snd_hda_intel snd_hda_codec iTCO_wdt snd_hwdep iTCO_vendor_support snd_seq
>> snd_seq_device snd_pcm snd_timer snd r8169 soundcore mii snd_page_alloc
>> pata_sil680 i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last
>> unloaded: mperf]
>> Pid: 1381, comm: sshd Not tainted 2.6.40-4.fc15.x86_64.debug #1
>> Call Trace:
>> Â[<ffffffff81058e74>] warn_slowpath_common+0x83/0x9b
>> Â[<ffffffff81058ea6>] warn_slowpath_null+0x1a/0x1c
>> Â[<ffffffff812f8e18>] tty_ldisc_reinit+0x52/0x90
>> Â[<ffffffff812f9415>] tty_ldisc_hangup+0x13f/0x1e1
>> Â[<ffffffff812f21b6>] __tty_hangup+0x111/0x35f
>> Â[<ffffffff812f2429>] tty_vhangup+0xe/0x10
>> Â[<ffffffff812faade>] pty_close+0x128/0x132
>> Â[<ffffffff812f3404>] tty_release+0x1d8/0x4dc
>> Â[<ffffffff81087a2e>] ? lock_release_holdtime.part.8+0x6b/0x72
>> Â[<ffffffff8100eebf>] ? native_sched_clock+0x34/0x36
>> Â[<ffffffff8113cdb2>] fput+0x127/0x1f5
>> Â[<ffffffff81139d90>] filp_close+0x70/0x7b
>> Â[<ffffffff81139e91>] sys_close+0xf6/0x13b
>> Â[<ffffffff814fdf02>] system_call_fastpath+0x16/0x1b
>
>
>
> --
> js
> suse labs
>



-- 
Regards
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/