From: Luca Tettamanti <kronos.it@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: WARNING: at drivers/char/tty_ldisc.c:465 tty_ldisc_close
Date: Mon, 22 Jun 2009 22:01:50 +0200 [thread overview]
Message-ID: <20090622200149.GA4257@nb-core2.darkstar.lan> (raw)
Hello,
with current git I see the following warning when rebooting the machine:
[ 287.872699] ------------[ cut here ]------------
[ 287.874306] WARNING: at /home/kronos/src/linux-2.6.git/drivers/char/tty_ldisc.c:465 tty_ldisc_close+0x27/0x4d()
[ 287.875829] Hardware name: F3Sa
[ 287.877387] Modules linked in: af_packet btusb bridge stp llc bnep sco rfcomm l2cap bluetooth ipv6 binfmt_misc acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table kvm_intel kvm deflate zlib_deflate twofish_x86_64 twofish_common aes_x86_64 aes_generic blowfish des_generic cbc sha256_generic sha1_generic af_key ext3 jbd coretemp hwmon microcode loop snd_hda_codec_realtek arc4 ecb snd_hda_intel snd_hda_codec iwlagn snd_hwdep iwlcore snd_pcm mac80211 snd_seq snd_timer rtc_cmos snd_seq_device snd cfg80211 rtc_core soundcore video pcspkr evdev psmouse rtc_lib asus_laptop snd_page_alloc rfkill output processor battery ac button ext4 mbcache jbd2 crc16 usbhid hid dm_mod sg sr_mod cdrom sdhci_pci sdhci mmc_core ohci1394 sd_mod ieee1394 led_class ata_piix ahci uhci_hcd libata scsi_mod ehci_hcd usbcore intel_agp thermal fan unix
[ 287.885243] Pid: 4098, comm: login Not tainted 2.6.30-07769-gf234012 #127
[ 287.886049] Call Trace:
[ 287.886858] [<ffffffff8104eb92>] ? finish_wait+0x5d/0x65
[ 287.887654] [<ffffffff811b5daa>] ? tty_ldisc_close+0x27/0x4d
[ 287.888455] [<ffffffff8103ae06>] warn_slowpath_common+0x77/0xa4
[ 287.889269] [<ffffffff8103ae42>] warn_slowpath_null+0xf/0x11
[ 287.890039] [<ffffffff811b5daa>] tty_ldisc_close+0x27/0x4d
[ 287.890814] [<ffffffff811b5fdd>] tty_ldisc_reinit+0x15/0x4c
[ 287.891581] [<ffffffff811b66f9>] tty_ldisc_hangup+0xfd/0x188
[ 287.892351] [<ffffffff811af84d>] do_tty_hangup+0x104/0x335
[ 287.893117] [<ffffffff811afdd8>] disassociate_ctty+0x52/0x23d
[ 287.893870] [<ffffffff8103e287>] do_exit+0x2b2/0x70a
[ 287.894615] [<ffffffff8103e752>] do_group_exit+0x73/0xa0
[ 287.895363] [<ffffffff810481d7>] get_signal_to_deliver+0x380/0x3a1
[ 287.896133] [<ffffffff8100b057>] do_notify_resume+0x8b/0x70b
[ 287.896887] [<ffffffff8126e25c>] ? _spin_unlock_irqrestore+0x12/0x2b
[ 287.897644] [<ffffffff8103dd46>] ? do_wait+0x238/0x361
[ 287.898398] [<ffffffff81034766>] ? default_wake_function+0x0/0xf
[ 287.899154] [<ffffffff8103df10>] ? sys_wait4+0xa1/0xb3
[ 287.899906] [<ffffffff8100bc05>] sysret_signal+0x6d/0xb7
[ 287.900669] ---[ end trace 256501a14a678d82 ]---
It's not 100% reproducible, but I have a few instances of the warning with
different (post 2.6.30) kernel builds (I tend to build daily).
Luca
reply other threads:[~2009-06-22 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090622200149.GA4257@nb-core2.darkstar.lan \
--to=kronos.it@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®