From: m0sia <m0sia@plotinka.ru>
To: Chmouel Boudjnah <chmouel@chmouel.com>, linux-kernel@vger.kernel.org
Subject: Re: scheduler crash 2.6.2-rc1-mm2
Date: Mon, 26 Jan 2004 22:25:44 +0500 [thread overview]
Message-ID: <20040126222544.125764ab.m0sia@plotinka.ru> (raw)
In-Reply-To: <m3fze2vb90.fsf@dark.chmouel.fr>
On 26 Jan 2004 19:02:51 +0100
Chmouel Boudjnah <chmouel@chmouel.com> wrote:
> Hi,
>
> I don't have a proper way to reproduce it (it crashed while the
> cmputer was idle and i was in the shower) but i am going to test -rc2
> and -rc1-mm3
>
> version:
> 2.6.2-rc1-mm2 : gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-4mdk)
>
> dmesg:
>
> request_module: failed /sbin/modprobe -- char-major-81-0. error = 256
> 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 -- sound-service-1-0. error = 256
> request_module: failed /sbin/modprobe -- sound-service-1-0. error = 256
> request_module: failed /sbin/modprobe -- char-major-116-0. error = 256
> request_module: failed /sbin/modprobe -- char-major-116-0. error = 256
> request_module: failed /sbin/modprobe -- char-major-116-0. error = 256
> request_module: failed /sbin/modprobe -- sound-service-1-0. error = 256
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> Badness in interruptible_sleep_on_timeout at kernel/sched.c:2245
> Call Trace:
> [<c011d765>] interruptible_sleep_on_timeout+0xf5/0x130
> [<c011d290>] default_wake_function+0x0/0x10
> [<e08fbdcf>] cm_write+0x51f/0x7b0 [cmpci]
> [<c0154de0>] vfs_write+0xb0/0x110
> [<c0154ee8>] sys_write+0x38/0x60
> [<c02488a6>] sysenter_past_esp+0x43/0x65
>
> request_module: failed /sbin/modprobe -- char-major-116-0. error = 256
> request_module: failed /sbin/modprobe -- sound-service-1-0. error = 256
> request_module: failed /sbin/modprobe -- sound-service-1-0. error = 256
>
> Cheers,
>
> --
> Travel's around the world - http://www.chmouel.com/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I had the same problem on 2.6.1-love3. I simply disabled ACPI in kernel.
next prev parent reply other threads:[~2004-01-26 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 18:02 scheduler crash 2.6.2-rc1-mm2 Chmouel Boudjnah
2004-01-26 17:25 ` m0sia [this message]
2004-01-27 0:57 ` Chmouel Boudjnah
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=20040126222544.125764ab.m0sia@plotinka.ru \
--to=m0sia@plotinka.ru \
--cc=chmouel@chmouel.com \
--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