From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 14214] BUG at drivers/scsi/scsi_lib.c:1108!
Date: Thu, 1 Oct 2009 09:02:35 GMT [thread overview]
Message-ID: <200910010902.n9192ZMU007722@demeter.kernel.org> (raw)
In-Reply-To: <bug-14214-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14214
--- Comment #6 from Plamen Petrov <pvp-lsts@fs.ru.acad.bg> 2009-10-01 09:02:34 ---
Some of the notable differences between the bad and good .config are:
good had CONFIG_SLOW_WORK=y;
IO schedulers: bad used CONFIG_DEFAULT_DEADLINE=y while good is with
CONFIG_DEFAULT_NOOP=y
bad had CONFIG_X86_MPPARSE=y, where good does not;
good has CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y, bad didn't;
bad had CONFIG_HOTPLUG_CPU=y, good does not;
I did not list the new config options which 2.6.32-rc1 has, and 2.6.31-git12
does not;
NOTE: these are both SMP enabled configs;
I will try and build 2.6.32-rc1 with the exact same config I used with
2.6.31-git12 to see how it fares, so we will know if the problem was fixed in
2.6.32-rc1; I will use gcc 4.4.1, though, and the kernel which did not allow me
to reboot or shutdown was built with gcc 4.3.3.
Thanks!
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2009-10-01 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 11:13 [Bug 14214] New: BUG at drivers/scsi/scsi_lib.c:1108! bugzilla-daemon
2009-09-23 11:14 ` [Bug 14214] " bugzilla-daemon
2009-09-30 20:55 ` bugzilla-daemon
2009-09-30 21:19 ` bugzilla-daemon
2009-10-01 7:07 ` bugzilla-daemon
2009-10-01 8:42 ` bugzilla-daemon
2009-10-01 8:49 ` bugzilla-daemon
2009-10-01 9:02 ` bugzilla-daemon [this message]
2009-10-01 9:30 ` bugzilla-daemon
2009-10-01 9:35 ` bugzilla-daemon
2009-10-01 10:32 ` bugzilla-daemon
2009-10-02 17:32 ` bugzilla-daemon
2009-10-02 17:32 ` 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=200910010902.n9192ZMU007722@demeter.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).