From: Andrew Morton <akpm@osdl.org>
To: Wu Fengguang <wfg@mail.ustc.edu.cn>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [SCSI BUG 2.6.15-rc3-mm1] scheduling while atomic on boot time
Date: Fri, 2 Dec 2005 11:31:47 -0800 [thread overview]
Message-ID: <20051202113147.600b80cd.akpm@osdl.org> (raw)
In-Reply-To: <20051202141455.GA10038@mail.ustc.edu.cn>
Wu Fengguang <wfg@mail.ustc.edu.cn> wrote:
>
> My server occasionally crashes on boot time, this has been happening in many
> recent kernel versions(at least from 2.6.14-rcx). It is rare enough, I setup
> netconsole and rebooted numerous times, but still failed to catch it. Luckily
> it happened again this time, and does not panic. Here is the logs.
>
> Thanks,
> Wu
>
> Error messages:
> [4294676.927000] scheduling while atomic: ksoftirqd/0/0x00000200/3
> [4294676.927000] [dump_stack+21/32] dump_stack+0x15/0x20
> [4294676.927000] [schedule+3563/3584] schedule+0xdeb/0xe00
> [4294676.927000] [__down+138/272] __down+0x8a/0x110
> [4294676.927000] [__sched_text_start+10/16] <6>scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices
> [4294676.927000] __down_failed+0xa/0x10
> [4294676.927000] [.text.lock.main+43/71] .text.lock.main+0x2b/0x47
> [4294676.928000] [device_del+62/112] device_del+0x3e/0x70
> [4294676.928000] [scsi_target_reap+137/176] scsi_target_reap+0x89/0xb0
> [4294676.928000] [scsi_device_dev_release+251/400] scsi_device_dev_release+0xfb/0x190
> [4294676.928000] [device_release+23/80] device_release+0x17/0x50
> [4294676.928000] [kobject_cleanup+116/128] kobject_cleanup+0x74/0x80
> [4294676.928000] [kobject_release+11/16] kobject_release+0xb/0x10
> [4294676.929000] [kref_put+52/160] kref_put+0x34/0xa0
> [4294676.929000] [kobject_put+20/32] kobject_put+0x14/0x20
> [4294676.929000] [put_device+17/32] put_device+0x11/0x20
> [4294676.929000] [scsi_next_command+48/64] scsi_next_command+0x30/0x40
> [4294676.929000] [scsi_end_request+165/192] scsi_end_request+0xa5/0xc0
> [4294676.929000] [scsi_io_completion+540/1152] scsi_io_completion+0x21c/0x480
> [4294676.929000] [scsi_generic_done+43/64] scsi_generic_done+0x2b/0x40
> [4294676.930000] [scsi_finish_command+146/240] scsi_finish_command+0x92/0xf0
> [4294676.930000] [scsi_softirq+215/320] scsi_softirq+0xd7/0x140
> [4294676.930000] [__do_softirq+216/240] __do_softirq+0xd8/0xf0
> [4294676.930000] [do_softirq+74/96] do_softirq+0x4a/0x60
> [4294676.930000] =======================
Which device driver are you using?
This is just a warning - it won't necessarily cause a crash and in this
case it didn't appear to do so.
I seem to recall diagnosing this exact locking problem a month or so ago,
and cc'ing linux-scsi on that analysis.
next parent reply other threads:[~2005-12-02 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051202141455.GA10038@mail.ustc.edu.cn>
2005-12-02 19:31 ` Andrew Morton [this message]
2005-12-03 2:26 ` Wu Fengguang
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=20051202113147.600b80cd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=wfg@mail.ustc.edu.cn \
/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
Powered by JetHome