From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 187381] New: 4.9.-rc4 produces hundreds of unusable scsi devices.
Date: Wed, 09 Nov 2016 20:20:08 +0000 [thread overview]
Message-ID: <bug-187381-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=187381
Bug ID: 187381
Summary: 4.9.-rc4 produces hundreds of unusable scsi devices.
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.9-rc4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: samuel.silbory@hds.com
Regression: No
Created attachment 244091
--> https://bugzilla.kernel.org/attachment.cgi?id=244091&action=edit
Debian's kernel log file. Note that this contains functional boots with older
kernels as well earlier in the file.
With both my hand compiled 4.9-rc4 from kernel.org sources and Ubuntu's
4.9.0-040900rc4-generic the kernel creates hundred of useless /dev/sd??
devices. This system is fine with various 4.4, and 4.8 kernels.
The logs are spammed with messages like these
2016-11-09T12:17:00.021765-08:00 Node001 kernel: [75590.503155] Dev sdjm:
unable to read RDB block 1
2016-11-09T12:17:00.021767-08:00 Node001 kernel: [75590.503188] sdjm: unable
to read partition table
2016-11-09T12:17:00.021769-08:00 Node001 kernel: [75590.503191] sdjm: partition
table beyond EOD, enabling native capacity
2016-11-09T12:17:00.021776-08:00 Node001 kernel: [75590.504463] sd 1:3:126:0:
[sdjl] Sector size 0 reported, assuming 512.
2016-11-09T12:17:00.021778-08:00 Node001 kernel: [75590.504486] sd 1:3:127:0:
[sdjm] Sector size 0 reported, assuming 512.
2016-11-09T12:17:00.025711-08:00 Node001 kernel: [75590.504624] Dev sdjl:
unable to read RDB block 1
2016-11-09T12:17:00.025720-08:00 Node001 kernel: [75590.504625] Dev sdjm:
unable to read RDB block 1
2016-11-09T12:17:00.025722-08:00 Node001 kernel: [75590.504635] sdjm: unable
to read partition table
2016-11-09T12:17:00.025724-08:00 Node001 kernel: [75590.504687] sdjm: partition
table beyond EOD, truncated
2016-11-09T12:17:00.025725-08:00 Node001 kernel: [75590.504697] sdjl: unable
to read partition table
2016-11-09T12:17:00.025727-08:00 Node001 kernel: [75590.504701] sdjl: partition
table beyond EOD, truncated
2016-11-09T12:17:00.025728-08:00 Node001 kernel: [75590.505084] sd 1:3:127:0:
[sdjm] Sector size 0 reported, assuming 512.
2016-11-09T12:17:00.025730-08:00 Node001 kernel: [75590.505088] sd 1:3:126:0:
[sdjl] Sector size 0 reported, assuming 512.
2016-11-09T12:17:00.025732-08:00 Node001 kernel: [75590.505115] sd 1:3:126:0:
[sdjl] Attached SCSI disk
2016-11-09T12:17:00.025733-08:00 Node001 kernel: [75590.505151] sd 1:3:127:0:
[sdjm] Attached SCSI disk
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-11-09 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 20:20 bugzilla-daemon [this message]
2016-11-09 20:25 ` [Bug 187381] 4.9.-rc4 produces hundreds of unusable scsi devices bugzilla-daemon
2016-11-09 20:49 ` [Bug 187381] New: " James Bottomley
2016-11-09 21:19 ` Samuel Silbory
2016-11-09 23:07 ` Samuel Silbory
2016-11-09 21:50 ` [Bug 187381] " bugzilla-daemon
2016-11-09 23:08 ` bugzilla-daemon
2016-11-10 13:15 ` 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-187381-11613@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).