From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: linux-rt-users@vger.kernel.org
Subject: 2.6.33.3-rt16: WARNING: at fs/namespace.c:1197 umount_tree+0x127/0x175()
Date: Tue, 27 Apr 2010 17:27:50 -0300 [thread overview]
Message-ID: <20100427202750.GC2679@uudg.org> (raw)
Hello!
I see this warning during system boot and it hangs while loading X and even
though I can change from one VT to another (ctrl+alt+F<num>) no keys
pressed seem to have any effect.
------------[ cut here ]------------
WARNING: at fs/namespace.c:1197 umount_tree+0x127/0x175()
Hardware name: KQ260AA-AC4 a6540br
Modules linked in: i915 drm_kms_helper drm video output ipt_MASQUERADE iptable_nat nf_nat bridge stp llc vfat fat sunrpc ipv6 xt_physdev ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state iptable_filter ip_tables x_tables dm_mirror dm_region_hash dm_log dm_multipath scsi_dh dm_mod kvm_intel kvm uinput tuner_simple tuner_types wm8775 tda9887 tda8290 tuner snd_hda_codec_realtek cx25840 snd_hda_intel snd_hda_codec snd_hwdep snd_seq usb_storage snd_seq_device ivtv snd_pcm i2c_algo_bit cx2341x v4l2_common videodev snd_timer firewire_ohci snd firewire_core v4l1_compat v4l2_compat_ioctl32 ir_common ir_core i2c_i801 soundcore crc_itu_t tveeprom i2c_core iTCO_wdt snd_page_alloc sr_mod intel_agp iTCO_vendor_support serio_raw pcspkr sg button r8169 mii cdrom ahci libata sd_mod scsi_mod cr
c_t10dif ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode]
Pid: 2267, comm: libvirtd Not tainted 2.6.33.3-rt16 #28
Call Trace:
[<ffffffff81040e3b>] warn_slowpath_common+0x7c/0x94
[<ffffffff81040e67>] warn_slowpath_null+0x14/0x16
[<ffffffff81115a7f>] umount_tree+0x127/0x175
[<ffffffff81116d1d>] put_mnt_ns+0xc2/0xf0
[<ffffffff81061a1d>] free_nsproxy+0x1f/0x86
[<ffffffff81061abc>] switch_task_namespaces+0x38/0x3c
[<ffffffff81061ad0>] exit_task_namespaces+0x10/0x12
[<ffffffff81044ae3>] do_exit+0x595/0x738
[<ffffffff81360626>] ? rt_mutex_unlock+0xe/0x10
[<ffffffff81360db8>] ? lockdep_sys_exit_thunk+0x35/0x67
[<ffffffff81044d10>] do_group_exit+0x8a/0xb9
[<ffffffff81044d56>] sys_exit_group+0x17/0x1b
[<ffffffff81002d32>] system_call_fastpath+0x16/0x1b
---[ end trace 348d259112b3e793 ]---
The warning comes from:
WARN_ON(!(p->mnt_flags & MNT_MOUNTED));
Regards,
Luis
--
[ Luis Claudio R. Goncalves Bass - Gospel - RT ]
[ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9 2696 7203 D980 A448 C8F8 ]
next reply other threads:[~2010-04-27 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 20:27 Luis Claudio R. Goncalves [this message]
2010-04-27 20:53 ` 2.6.33.3-rt16: WARNING: at fs/namespace.c:1197 umount_tree+0x127/0x175() Thomas Gleixner
2010-04-28 1:21 ` john stultz
2010-04-29 6:35 ` john stultz
2010-04-29 12:54 ` Luis Claudio R. Goncalves
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=20100427202750.GC2679@uudg.org \
--to=lclaudio@uudg.org \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).