All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 06 Dec 2013 21:18:11 +0000	[thread overview]
Message-ID: <bug-60758-11613-qUmQyluOSS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60758-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=60758

Vincent Li <vincent.mc.li@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vincent.mc.li@gmail.com

--- Comment #48 from Vincent Li <vincent.mc.li@gmail.com> ---
oddly, I can boot into 3.12.0-rc4 but not 3.13.0-rc3, neither of them has
scsi_wait_scan.ko compiled. I see error message "FATAL: Module scsi_wait_scan
not found" for both 3.12.0-rc4 and 3.13.0-rc3. but it only appears once for
3.12.0-rc4. it repeated many times for 3.13.0-rc3 and finally kernel Panic:

FATAL: Module scsi_wait_scan not found.
FATAL: Module scsi_wait_scan not found.
FATAL: Module scsi_wait_scan not found.
FATAL: Module scsi_wait_scan not found.

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100

CPU: 3 PID: 1 Comm: init Tainted: GF            3.13.0-rc3 #27
Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2007
 0000000000000001 ffff8802108f3d98 ffffffff8156c50b 000000000000fffe
 ffffffff817e0d00 ffff8802108f3e18 ffffffff8156c298 ffffffff00000010
 ffff8802108f3e28 ffff8802108f3dc8 ffff8802108f17b8 ffff8802108f3dd8
Call Trace:
 [<ffffffff8156c50b>] dump_stack+0x49/0x5e
 [<ffffffff8156c298>] panic+0xbb/0x1d5
 [<ffffffff8104e74b>] find_new_reaper+0x17b/0x180
 [<ffffffff8104f8d5>] forget_original_parent+0x45/0x1c0
 [<ffffffff8111e110>] ? perf_cgroup_switch+0x180/0x180
 [<ffffffff8104fa67>] exit_notify+0x17/0x130
 [<ffffffff8104fd6e>] do_exit+0x1ee/0x480
 [<ffffffff81050051>] do_group_exit+0x51/0xc0
 [<ffffffff810500d7>] SyS_exit_group+0x17/0x20
 [<ffffffff81578dd2>] system_call_fastpath+0x16/0x1b

I tried comment out the scsi_wait_scan in rc.sysinit and kernel boot parameter
with 'scsi_mod.scan=async', no help

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2013-12-06 21:18 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
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 [this message]
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-qUmQyluOSS@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.