Tetsuo, see my comments above for the diagnosis of two different bugs.
I've already identified (b) as well and it's completely orthogonal to
the bug in question. No idea about (a), though, your comment is
interesting.
--
You received this bug notification because you are a member of Kernel
Packag
Pretty sure that's it. -12 is -ENOMEM, and there are two sites in that
commit that return -ENOMEM, right when we have an error message from the
failure to spawn the SCSI error handler thread.
Note that the oops/backtrace is a red herring. There is a secondary,
unrelated bug in the mptsas code that
Well, Pierre gave the full output, so the answer to your question is yes
(that's really easy to verify).
The merge commit doesn't look like having any relevant code changes, so
this is a dead end.
I actually think that limiting to drivers/scsi was a bad idea from the
start. The v3.12..v3.13-rc1 d
We're also experiencing the same issue when booting the trusty installer
on a Dell PowerEdge R610 with a Dell SAS 6/iR controller (LSI SAS1068E),
resulting in the inability to install/run this system. This is an
extremely popular controller, prevalent in a signifcant portion of Dell
systems (or sys
4 matches
Mail list logo
