From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>, XFS List <linux-xfs@oss.sgi.com>
Subject: Re: [2.6.2-rc1-mm3] Badness in interruptible_sleep_on.
Date: Wed, 28 Jan 2004 12:40:08 -0500 [thread overview]
Message-ID: <1075311607.3551.3.camel@blaze.homeip.net> (raw)
In-Reply-To: <1075140703.2291.8.camel@blaze.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
On Mon, 2004-01-26 at 13:11, Paul Blazejowski wrote:
> Hello Andrew,
>
> I see these panics related to pagebuf from XFS on:
>
> Linux blaze 2.6.2-rc1-mm3 #1 Sun Jan 25 18:24:01 EST 2004 i686 AMD
> Athlon(tm) XP 3200+ AuthenticAMD GNU/Linux
>
> Code snip:
>
> Badness in interruptible_sleep_on at kernel/sched.c:2242
> Call Trace:
> [<c011cb93>] interruptible_sleep_on+0x103/0x110
> [<c011c740>] default_wake_function+0x0/0x20
> [<c0209db0>] pagebuf_daemon+0x0/0x260
> [<c0209ff4>] pagebuf_daemon+0x244/0x260
>
> ret_from_fork+0x6/0x14
> [<c0209d80>] pagebuf_daemon_wakeup+0x0/0x30
> [<c0209db0>] <6>hda: 58633344 sectors (30020 MB) w/2048KiB Cache,
> CHS=58168/16/63, UDMA(100)
> hda: hda1
> pagebuf_daemon+0x0/0x260
> [<c0108e49>] kernel_thread_helper+0x5/0xc
>
> Also this creeps in:
>
> atkbd.c: Unknown key released (translated set 2, code 0x7a on
> isa0060/serio0).
> atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
> atkbd.c: Unknown key released (translated set 2, code 0x7a on
> isa0060/serio0).
> atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
> request_module: failed /sbin/modprobe -- block-major-11-0. error = 256
Hello folks,
Just to add the same happens under 2.6.2-rc2-mm1 kernel i just compiled.
Badness in interruptible_sleep_on at kernel/sched.c:2239
Call Trace:
[<c011cc13>] interruptible_sleep_on+0x103/0x110
[<c011c7c0>] default_wake_function+0x0/0x20
[<c0209ef0>] pagebuf_daemon+0x0/0x260
[<c020a134>] pagebuf_daemon+0x244/0x260
ret_from_fork+0x6/0x14
[<c0209ec0>] pagebuf_daemon_wakeup+0x0/0x30
hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=58168/16/63,
UDMA(100)
hda: hda1
[<c0209ef0>] pagebuf_daemon+0x0/0x260
[<c0108e49>] kernel_thread_helper+0x5/0xc
Regards,
Paul B.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-28 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 18:11 Paul Blazejowski
2004-01-28 17:40 ` Paul Blazejowski [this message]
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=1075311607.3551.3.camel@blaze.homeip.net \
--to=paulb@blazebox.homeip.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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®