From: "Colin Harrison" <colin.harrison@virgin.net>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel 2.6.12-rc4 with realtime-preempt-2.6.12-rc4-V0.7.47-03 patch breaks running mplayer
Date: Mon, 16 May 2005 13:41:07 +0100 [thread overview]
Message-ID: <200505161241.j4GCf2ql001963@StraightRunning.com> (raw)
Hi
As an experiment I built a 2.6.12-rc4 kernel with the
realtime-preempt-2.6.12-rc4-V0.7.47-03 patch.
Runs fine until I play mplayer (cvs), then I get the following in
/var/log/messages.
May 16 12:02:00 chamonix kernel: BUG: mplayer/1659, active lock
[d554d49c(d554d480-d554d580)] freed!
May 16 12:02:00 chamonix kernel: [check_no_locks_freed+323/466]
check_no_locks_freed+0x143/0x1d2 (8)
May 16 12:02:00 chamonix kernel: [<c012a376>]
check_no_locks_freed+0x143/0x1d2 (8)
May 16 12:02:00 chamonix kernel: [kfree+86/368] kfree+0x56/0x170 (60)
May 16 12:02:00 chamonix kernel: [<c013c2ea>] kfree+0x56/0x170 (60)
May 16 12:02:00 chamonix kernel: [rt_up+204/226] rt_up+0xcc/0xe2 (8)
May 16 12:02:00 chamonix kernel: [<c012ca50>] rt_up+0xcc/0xe2 (8)
May 16 12:02:00 chamonix kernel: [pg0+576581227/1069986816]
fusion_entry_destroy+0xd2/0x11e [fusion] (36)
May 16 12:02:00 chamonix kernel: [<e2971e6b>]
fusion_entry_destroy+0xd2/0x11e [fusion] (36)
May 16 12:02:00 chamonix kernel: [pg0+576585565/1069986816]
skirmish_ioctl+0x39/0xde [fusion] (36)
May 16 12:02:00 chamonix kernel: [<e2972f5d>] skirmish_ioctl+0x39/0xde
[fusion] (36)
May 16 12:02:00 chamonix kernel: [do_ioctl+101/150] do_ioctl+0x65/0x96 (16)
May 16 12:02:00 chamonix kernel: [<c0161c3d>] do_ioctl+0x65/0x96 (16)
May 16 12:02:00 chamonix kernel: [vfs_ioctl+104/474] vfs_ioctl+0x68/0x1da
(28)
May 16 12:02:00 chamonix kernel: [<c0161df7>] vfs_ioctl+0x68/0x1da (28)
May 16 12:02:00 chamonix kernel: [fget_light+131/133] fget_light+0x83/0x85
(8)
May 16 12:02:00 chamonix kernel: [<c0151603>] fget_light+0x83/0x85 (8)
May 16 12:02:00 chamonix kernel: [sys_ioctl+61/99] sys_ioctl+0x3d/0x63 (20)
May 16 12:02:00 chamonix kernel: [<c0161fa6>] sys_ioctl+0x3d/0x63 (20)
May 16 12:02:00 chamonix kernel: [sysenter_past_esp+84/117]
sysenter_past_esp+0x54/0x75 (24)
May 16 12:02:00 chamonix kernel: [<c0102743>] sysenter_past_esp+0x54/0x75
(24)
May 16 12:02:00 chamonix kernel: [d554d49c] {(struct semaphore
*)(&entry->lock)}
May 16 12:02:00 chamonix kernel: .. held by: mplayer: 1659
[d6bccd90, 101]
May 16 12:02:00 chamonix kernel: ... acquired at:
fusion_entry_destroy+0x95/0x11e [fusion]
May 16 12:02:00 chamonix kernel: slab size-256[c14d3680] (256), obj:
d554d480
May 16 12:02:00 chamonix kernel: `IRQ 8'[12] is being piggy. need_resched=0,
cpu=0
May 16 12:02:00 chamonix kernel: Read missed before next interrupt
May 16 12:02:00 chamonix kernel: wow! That was a 23 millisec bump
May 16 12:02:00 chamonix kernel: bug in rtc_read(): called in state S_IDLE!
May 16 12:02:00 chamonix kernel: `IRQ 8'[12] is being piggy. need_resched=0,
cpu=0
May 16 12:02:00 chamonix kernel: Read missed before next interrupt
May 16 12:02:01 chamonix kernel: wow! That was a 20 millisec bump
etc with last 'piggy?' messages repeating.
More information/testing can be supplied/performed, if anyone is interested?
Perhaps this is more an mplayer or fusion problem, and I'm reporting on the
wrong list!
I am experimenting with mplayer, matroxfb, freevo and fusion, compiling the
2.6.12-rc4 kernel CONFIG_PREEMPT=y. This combination usually runs reliably
and gives spectacularly beautiful results.
Thanks
Colin Harrison
reply other threads:[~2005-05-16 12:41 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=200505161241.j4GCf2ql001963@StraightRunning.com \
--to=colin.harrison@virgin.net \
--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