linux-kernel - Re: 2.6.20-rc1-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Dec 2006 16:42:20 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc1-mm1

On Mon, 18 Dec 2006 16:29:02 -0800
Randy Dunlap <randy.dunlap@...cle.com> wrote:

> On Thu, 14 Dec 2006 22:59:13 -0800 Andrew Morton wrote:
> 
> Got this on booting up on x86_64 test box.
> Didn't happen on next boot.
> 
> 
> BUG: scheduling while atomic: hald-addon-stor/0x20000000/3300
> 
> Call Trace:
>  [<ffffffff8020ac30>] show_trace+0x34/0x47
>  [<ffffffff8020ac55>] dump_stack+0x12/0x17
>  [<ffffffff8050c2dd>] __sched_text_start+0x5d/0x7ba
>  [<ffffffff8022b3f0>] __cond_resched+0x1c/0x44
>  [<ffffffff8050cb4d>] cond_resched+0x29/0x30
>  [<ffffffff8050e7aa>] __reacquire_kernel_lock+0x26/0x44
>  [<ffffffff8050cae6>] thread_return+0xac/0xea
>  [<ffffffff8022b3f0>] __cond_resched+0x1c/0x44
>  [<ffffffff8050cb4d>] cond_resched+0x29/0x30
>  [<ffffffff8050cb83>] wait_for_completion+0x17/0xd2
>  [<ffffffff80337a19>] blk_execute_rq+0x98/0xb8
>  [<ffffffff80413e7b>] scsi_execute+0xd4/0xf1
>  [<ffffffff80413f51>] scsi_execute_req+0xb9/0xde
>  [<ffffffff80413faf>] scsi_test_unit_ready+0x39/0x75
>  [<ffffffff804443cd>] sd_media_changed+0x40/0x87
>  [<ffffffff8029cde0>] check_disk_change+0x1f/0x76
>  [<ffffffff8044417e>] sd_open+0x80/0x113
>  [<ffffffff8029d4c4>] do_open+0x9f/0x2a7
>  [<ffffffff8029d8bc>] blkdev_open+0x2e/0x5d
>  [<ffffffff8027afeb>] __dentry_open+0xd9/0x1a7
>  [<ffffffff8027b16a>] do_filp_open+0x2a/0x38
>  [<ffffffff8027b1bc>] do_sys_open+0x44/0xc8
>  [<ffffffff8020956e>] system_call+0x7e/0x83

Bit 29 of current->preempt_count got set.  I don't think there's any way in
which that can happen normally.  So probably some hardware or software
error reached out and flipped that bit.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/