I hit this bug after upgrade from testing systemd repo
[ 15.630389] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() [ 15.630393] Hardware name: HP 550 [ 15.630396] Modules linked in: snd_hda_codec_analog iwlagn snd_hda_intel iwlcore snd_hda_codec snd_hwdep snd_seq uinput snd_seq_device hp_wmi btusb mac80211 snd_pcm cfg80211 bluetooth rfkill snd_timer joydev serio_raw wmi shpchp snd soundcore e1000e iTCO_wdt snd_page_alloc iTCO_vendor_support ipv6 i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] [ 15.630460] Pid: 123, comm: plymouthd Not tainted 2.6.36-1.fc15.x86_64 #1 [ 15.630464] Call Trace: [ 15.630472] [<ffffffff810511bc>] warn_slowpath_common+0x85/0x9d [ 15.630479] [<ffffffff810511ee>] warn_slowpath_null+0x1a/0x1c [ 15.630485] [<ffffffff812d3c3a>] tty_open+0x29c/0x49b [ 15.630493] [<ffffffff8112eb90>] chrdev_open+0x122/0x14b [ 15.630499] [<ffffffff8112ea6e>] ? chrdev_open+0x0/0x14b [ 15.630506] [<ffffffff8112963f>] __dentry_open+0x1c2/0x338 [ 15.630514] [<ffffffff8121316e>] ? devcgroup_inode_permission+0xea/0x117 [ 15.630521] [<ffffffff8112a4c0>] nameidata_to_filp+0x3f/0x50 [ 15.630527] [<ffffffff81136adc>] do_last+0x432/0x5af [ 15.630533] [<ffffffff81246491>] ? __raw_spin_lock_init+0x31/0x50 [ 15.630539] [<ffffffff81136e89>] do_filp_open+0x230/0x5e1 [ 15.630546] [<ffffffff81010588>] ? native_sched_clock+0x35/0x37 [ 15.630553] [<ffffffff8107275e>] ? local_clock+0x36/0x4d [ 15.630561] [<ffffffff8107ff01>] ? lock_release+0x19a/0x1a6 [ 15.630568] [<ffffffff81140e16>] ? alloc_fd+0x16a/0x17c [ 15.630574] [<ffffffff8112a531>] do_sys_open+0x60/0xfc [ 15.630582] [<ffffffff8149cb0d>] ? trace_hardirqs_on_thunk+0x3a/0x3f [ 15.630588] [<ffffffff8112a5ed>] sys_open+0x20/0x22 [ 15.630594] [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b [ 15.630599] ---[ end trace 740a8a695fc86592 ]--- [ 16.275231] init[1]: tmpwatch.service: main process exited, code=exited, status=203 [ 16.279501] init[1]: Unit tmpwatch.service entered failed state. [ 16.410415] ------------[ cut here ]------------ [ 16.410427] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() [ 16.410431] Hardware name: HP 550 [ 16.410434] Modules linked in: snd_hda_codec_analog iwlagn snd_hda_intel iwlcore snd_hda_codec snd_hwdep snd_seq uinput snd_seq_device hp_wmi btusb mac80211 snd_pcm cfg80211 bluetooth rfkill snd_timer joydev serio_raw wmi shpchp snd soundcore e1000e iTCO_wdt snd_page_alloc iTCO_vendor_support ipv6 i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] [ 16.410499] Pid: 123, comm: plymouthd Tainted: G W 2.6.36-1.fc15.x86_64 #1 [ 16.410504] Call Trace: [ 16.410515] [<ffffffff810511bc>] warn_slowpath_common+0x85/0x9d [ 16.410522] [<ffffffff810511ee>] warn_slowpath_null+0x1a/0x1c [ 16.410528] [<ffffffff812d3c3a>] tty_open+0x29c/0x49b [ 16.410535] [<ffffffff8112eb90>] chrdev_open+0x122/0x14b [ 16.410542] [<ffffffff8112ea6e>] ? chrdev_open+0x0/0x14b [ 16.410549] [<ffffffff8112963f>] __dentry_open+0x1c2/0x338 [ 16.410557] [<ffffffff8121316e>] ? devcgroup_inode_permission+0xea/0x117 [ 16.410564] [<ffffffff8112a4c0>] nameidata_to_filp+0x3f/0x50 [ 16.410571] [<ffffffff81136adc>] do_last+0x432/0x5af [ 16.410577] [<ffffffff81246491>] ? __raw_spin_lock_init+0x31/0x50 [ 16.410583] [<ffffffff81136e89>] do_filp_open+0x230/0x5e1 [ 16.410590] [<ffffffff81010588>] ? native_sched_clock+0x35/0x37 [ 16.410598] [<ffffffff8107275e>] ? local_clock+0x36/0x4d [ 16.410605] [<ffffffff8107ff01>] ? lock_release+0x19a/0x1a6 [ 16.410612] [<ffffffff81140e16>] ? alloc_fd+0x16a/0x17c [ 16.410619] [<ffffffff8112a531>] do_sys_open+0x60/0xfc [ 16.410627] [<ffffffff8149cb0d>] ? trace_hardirqs_on_thunk+0x3a/0x3f [ 16.410633] [<ffffffff8112a5ed>] sys_open+0x20/0x22 [ 16.410639] [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b [ 16.410644] ---[ end trace 740a8a695fc86593 ]---
https://bugzilla.redhat.com/show_bug.cgi?id=630464
Regards, Michal
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
I hit this bug after upgrade from testing systemd repo
[ 15.630389] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() [ 15.630393] Hardware name: HP 550 [ 15.630396] Modules linked in: snd_hda_codec_analog iwlagn snd_hda_intel iwlcore snd_hda_codec snd_hwdep snd_seq uinput snd_seq_device hp_wmi btusb mac80211 snd_pcm cfg80211 bluetooth rfkill snd_timer joydev serio_raw wmi shpchp snd soundcore e1000e iTCO_wdt snd_page_alloc iTCO_vendor_support ipv6 i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] [ 15.630460] Pid: 123, comm: plymouthd Not tainted 2.6.36-1.fc15.x86_64 #1
Do you remember if this turned up when systemd was enabled in fc14? I have a feeling this is going to be a nasty race as a result of the BKL removal from the TTY code...
--Kyle
2010/10/21 Kyle McMartin kyle@mcmartin.ca:
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
I hit this bug after upgrade from testing systemd repo
[ 15.630389] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() [ 15.630393] Hardware name: HP 550 [ 15.630396] Modules linked in: snd_hda_codec_analog iwlagn snd_hda_intel iwlcore snd_hda_codec snd_hwdep snd_seq uinput snd_seq_device hp_wmi btusb mac80211 snd_pcm cfg80211 bluetooth rfkill snd_timer joydev serio_raw wmi shpchp snd soundcore e1000e iTCO_wdt snd_page_alloc iTCO_vendor_support ipv6 i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] [ 15.630460] Pid: 123, comm: plymouthd Not tainted 2.6.36-1.fc15.x86_64 #1
Do you remember if this turned up when systemd was enabled in fc14?
No, I did not seen this bug before.
I noticed it today after systemd update - I grepped /var/log/messages grep drivers/char/tty_io.c messages Oct 21 20:28:53 dio kernel: [ 15.630389] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 20:28:53 dio kernel: [ 16.410427] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 20:45:05 dio kernel: [ 14.682062] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 20:45:05 dio kernel: [ 16.568228] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 20:57:21 dio kernel: [ 14.515496] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 20:57:21 dio kernel: [ 15.976412] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 20:57:21 dio kernel: [ 16.781814] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 21:01:56 dio kernel: [ 14.792913] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 21:01:56 dio kernel: [ 15.902248] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() Oct 21 21:01:56 dio kernel: [ 16.629255] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b()
I have a feeling this is going to be a nasty race as a result of the BKL removal from the TTY code...
It's not nasty - it's repeatable on my system :)
(and I bet that on the others too, after systemd upgrade - systemd 11 somehow triggers this bug)
--Kyle
Regards, Michal
On Thu, Oct 21, 2010 at 09:21:40PM +0200, Micha? Piotrowski wrote:
No, I did not seen this bug before.
Ok, cool. Thanks! I'll look into it.
It's not nasty - it's repeatable on my system :)
(and I bet that on the others too, after systemd upgrade - systemd 11 somehow triggers this bug)
Yeah, it's just unlikely other distros will hit it because they probably don't enable cgroups yet like we do (because of systemd.)
--Kyle
Yeah, it's just unlikely other distros will hit it because they probably don't enable cgroups yet like we do (because of systemd.)
Well I'm *other distro* and this same warning with the same backtrace is happening on my system running 2.6.36_rc7 under VBox. I don't use systemd but play with cgroups while experimenting the LXC.
Should this be reported to upstream?
--- Ozan Çağlayan TUBITAK/UEKAE - Pardus Linux http://www.pardus.org.tr/eng
2010/10/21 Kyle McMartin kyle@mcmartin.ca:
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
I hit this bug after upgrade from testing systemd repo
[ 15.630389] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b() [ 15.630393] Hardware name: HP 550 [ 15.630396] Modules linked in: snd_hda_codec_analog iwlagn snd_hda_intel iwlcore snd_hda_codec snd_hwdep snd_seq uinput snd_seq_device hp_wmi btusb mac80211 snd_pcm cfg80211 bluetooth rfkill snd_timer joydev serio_raw wmi shpchp snd soundcore e1000e iTCO_wdt snd_page_alloc iTCO_vendor_support ipv6 i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] [ 15.630460] Pid: 123, comm: plymouthd Not tainted 2.6.36-1.fc15.x86_64 #1
Do you remember if this turned up when systemd was enabled in fc14?
I'm using 2.6.36-1.fc14.x86_64 for three days on my devel server and I have not noticed this problem.
It seems to me that this bug should be no problem on F14 systems that do not use cgroups.
Best regards, Michal
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
[ 16.410415] ------------[ cut here ]------------ [ 16.410427] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b()
So, I stopped seeing this on rawhide with my 2.6.37-rc2 kernels. Could you try http://koji.fedoraproject.org/koji/taskinfo?taskID=2617334 when it completes (it's only a scratch build so it gets auto-reaped since I've already done a build today.)
Thanks! Kyle
Kyle McMartin (kyle@mcmartin.ca) said:
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
[ 16.410415] ------------[ cut here ]------------ [ 16.410427] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b()
So, I stopped seeing this on rawhide with my 2.6.37-rc2 kernels. Could you try http://koji.fedoraproject.org/koji/taskinfo?taskID=2617334 when it completes (it's only a scratch build so it gets auto-reaped since I've already done a build today.)
I'm actually not seeing it with 2.6.36-5. Wonder if something else is going on.
Bill
On Mon, Nov 22, 2010 at 05:34:51PM -0500, Bill Nottingham wrote:
Kyle McMartin (kyle@mcmartin.ca) said:
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
[ 16.410415] ------------[ cut here ]------------ [ 16.410427] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b()
So, I stopped seeing this on rawhide with my 2.6.37-rc2 kernels. Could you try http://koji.fedoraproject.org/koji/taskinfo?taskID=2617334 when it completes (it's only a scratch build so it gets auto-reaped since I've already done a build today.)
I'm actually not seeing it with 2.6.36-5. Wonder if something else is going on.
That's pretty messed up... Michal Jaegermann just reported he's still seeing it with 2.6.36.1 in https://bugzilla.redhat.com/show_bug.cgi?id=630464...
--Kyle
Hi,
2010/11/22 Kyle McMartin kyle@mcmartin.ca:
On Mon, Nov 22, 2010 at 05:34:51PM -0500, Bill Nottingham wrote:
Kyle McMartin (kyle@mcmartin.ca) said:
On Thu, Oct 21, 2010 at 08:38:10PM +0200, Micha? Piotrowski wrote:
[ 16.410415] ------------[ cut here ]------------ [ 16.410427] WARNING: at drivers/char/tty_io.c:1325 tty_open+0x29c/0x49b()
So, I stopped seeing this on rawhide with my 2.6.37-rc2 kernels. Could you try http://koji.fedoraproject.org/koji/taskinfo?taskID=2617334 when it completes (it's only a scratch build so it gets auto-reaped since I've already done a build today.)
I'm actually not seeing it with 2.6.36-5. Wonder if something else is going on.
Me too.
That's pretty messed up... Michal Jaegermann just reported he's still seeing it with 2.6.36.1 in https://bugzilla.redhat.com/show_bug.cgi?id=630464...
It seems to me that this kernel doesn't fix this bug. Bill and I do not see it, because we have an updated SystemD and Lennart has fixed something.
--Kyle
Best regards, Michal
On Tue, Nov 23, 2010 at 01:39:33PM +0100, Micha? Piotrowski wrote:
That's pretty messed up... Michal Jaegermann just reported he's still seeing it with 2.6.36.1 in https://bugzilla.redhat.com/show_bug.cgi?id=630464...
It seems to me that this kernel doesn't fix this bug. Bill and I do not see it, because we have an updated SystemD and Lennart has fixed something.
Hrm, but there's some people reporting they see it on one version and not the other. :/
2010/11/23 Kyle McMartin kyle@mcmartin.ca:
On Tue, Nov 23, 2010 at 01:39:33PM +0100, Micha? Piotrowski wrote:
That's pretty messed up... Michal Jaegermann just reported he's still seeing it with 2.6.36.1 in https://bugzilla.redhat.com/show_bug.cgi?id=630464...
It seems to me that this kernel doesn't fix this bug. Bill and I do not see it, because we have an updated SystemD and Lennart has fixed something.
Hrm, but there's some people reporting they see it on one version and not the other. :/
Ok, I still got it on 2.6.36-5.fc15.x86_64. I checked logs and with 2.6.36-5 this bugs shows up spontaneously. Logs attached.
Kind regards, Michal
On Tue, Nov 23, 2010 at 02:30:47PM +0100, Micha? Piotrowski wrote:
Ok, I still got it on 2.6.36-5.fc15.x86_64. I checked logs and with 2.6.36-5 this bugs shows up spontaneously. Logs attached.
Try this one? http://kyle.fedorapeople.org/kernel/2.6.37-0.rc3.git3.2/x86_64/
Hi,
2010/11/29 Kyle McMartin kyle@mcmartin.ca:
On Tue, Nov 23, 2010 at 02:30:47PM +0100, Micha? Piotrowski wrote:
Ok, I still got it on 2.6.36-5.fc15.x86_64. I checked logs and with 2.6.36-5 this bugs shows up spontaneously. Logs attached.
Try this one? http://kyle.fedorapeople.org/kernel/2.6.37-0.rc3.git3.2/x86_64/
So far so good - a few reboots and bug did not appear. Thanks!
On Mon, Nov 29, 2010 at 02:03:02PM +0100, Michał Piotrowski wrote:
Ok, I still got it on 2.6.36-5.fc15.x86_64. I checked logs and with 2.6.36-5 this bugs shows up spontaneously. Logs attached.
Try this one? http://kyle.fedorapeople.org/kernel/2.6.37-0.rc3.git3.2/x86_64/
So far so good - a few reboots and bug did not appear. Thanks!
Thanks go to Jiri Slaby for fixing to, I'm just the messenger. ;-)
kernel@lists.fedoraproject.org
-
Bill Nottingham -
Kyle McMartin -
Michał Piotrowski -
Ozan Çağlayan