From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 60758] module scsi_wait_scan not found kernel panic on boot
Date: Tue, 03 Sep 2013 05:09:51 +0000 [thread overview]
Message-ID: <bug-60758-11613-2VFQJdVTo8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60758-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60758
--- Comment #22 from Jeff Zhou <jz.researcher@yahoo.com> ---
(In reply to zakrzewskim from comment #21)
> Here you are: http://www.upemax.user.icpnet.pl/3.10.4-1.el6.lst
Yes then we see the scsi_scan_wait is not in 3.10.4 either, otherwise there
will be a line :"drivers/scsi/scsi_wait_scan.ko".
The rc.sysinit file in your system might need adjustment to remove the
reference to scsi_wait_scan module.
But that might not be the root cause, since 3.10.4 without scsi_wait_scan works
fine under this script.
There could be a regression between 3.10.4 to 3.10.5 cause your system hang,
might be or might not be scsi problem.
To find the root cause and fix it, probably need to roll back between 3.10.5 to
3.10.4, build and test the kernel for booting, git bisect could be helpful.
Then we can check the details to see why the commit crashing the specific
machine.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-09-03 5:09 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 19:17 [Bug 60758] New: module scsi_wait_scan not found kernel panic on boot bugzilla-daemon
2013-08-16 19:18 ` [Bug 60758] " bugzilla-daemon
2013-08-16 23:32 ` bugzilla-daemon
2013-08-29 5:13 ` bugzilla-daemon
2013-08-30 7:35 ` bugzilla-daemon
2013-08-31 3:39 ` bugzilla-daemon
2013-08-31 4:00 ` bugzilla-daemon
2013-08-31 16:02 ` bugzilla-daemon
2013-08-31 16:49 ` bugzilla-daemon
2013-08-31 17:01 ` bugzilla-daemon
2013-08-31 17:03 ` bugzilla-daemon
2013-08-31 20:50 ` bugzilla-daemon
2013-08-31 21:03 ` bugzilla-daemon
2013-08-31 21:26 ` bugzilla-daemon
2013-08-31 22:26 ` bugzilla-daemon
2013-08-31 22:39 ` bugzilla-daemon
2013-09-01 0:17 ` bugzilla-daemon
2013-09-01 0:48 ` bugzilla-daemon
2013-09-01 2:16 ` bugzilla-daemon
2013-09-02 14:48 ` bugzilla-daemon
2013-09-02 19:45 ` bugzilla-daemon
2013-09-02 19:55 ` bugzilla-daemon
2013-09-03 5:09 ` bugzilla-daemon [this message]
2013-09-03 10:33 ` bugzilla-daemon
2013-09-03 15:41 ` bugzilla-daemon
2013-09-03 15:44 ` bugzilla-daemon
2013-09-04 4:48 ` bugzilla-daemon
2013-09-04 9:15 ` bugzilla-daemon
2013-09-04 9:16 ` bugzilla-daemon
2013-09-22 8:23 ` bugzilla-daemon
2013-09-22 13:38 ` bugzilla-daemon
2013-09-22 13:55 ` bugzilla-daemon
2013-09-22 14:15 ` bugzilla-daemon
2013-09-22 21:01 ` bugzilla-daemon
2013-09-22 22:23 ` bugzilla-daemon
2013-09-22 22:23 ` bugzilla-daemon
2013-09-22 22:31 ` bugzilla-daemon
2013-09-22 23:16 ` bugzilla-daemon
2013-09-23 9:24 ` bugzilla-daemon
2013-10-19 15:38 ` bugzilla-daemon
2013-10-22 6:24 ` bugzilla-daemon
2013-10-23 11:21 ` bugzilla-daemon
2013-10-23 11:23 ` bugzilla-daemon
2013-10-23 13:48 ` bugzilla-daemon
2013-11-06 11:55 ` bugzilla-daemon
2013-11-06 15:52 ` bugzilla-daemon
2013-11-08 15:34 ` bugzilla-daemon
2013-11-13 22:06 ` bugzilla-daemon
2013-11-14 11:19 ` bugzilla-daemon
2013-12-06 21:18 ` bugzilla-daemon
2013-12-06 21:19 ` bugzilla-daemon
2013-12-26 9:00 ` bugzilla-daemon
2013-12-26 22:20 ` bugzilla-daemon
2013-12-27 1:14 ` bugzilla-daemon
2013-12-31 6:22 ` bugzilla-daemon
2014-01-22 21:17 ` bugzilla-daemon
2014-01-29 10:19 ` bugzilla-daemon
2014-02-07 15:54 ` bugzilla-daemon
2014-02-21 5:31 ` bugzilla-daemon
2014-02-21 5:35 ` bugzilla-daemon
2014-02-21 5:53 ` bugzilla-daemon
2015-10-08 2:55 ` bugzilla-daemon
2024-06-10 6:03 ` bugzilla-daemon
2024-06-10 6:51 ` bugzilla-daemon
2024-06-10 8:12 ` bugzilla-daemon
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=bug-60758-11613-2VFQJdVTo8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).