Yes, 3.13.0-43.72 now has the upstream updates up to kernel 3.13.11.11.
The latest upstream 3.13 kernel is not available at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11-ckt12-trusty/
Does the 3.13.0-43.72 kernel still exhibit this bug?
--
You received this bug notification because
3.13.0-43.72 does not exhibit this bug with testing, so I think we can
close this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
Title:
Trusty isci module doesn't handle timeouts
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I assume yesterday's released 3.13.0-43.72 build contains the mainline
updates for the 3.13 series?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
Title:
Trusty isci module doesn't handle
I've installed 3.13.0-41.70 on four machines for testing. Will report
back shortly.
# dpkg -l | grep 3.13.0-41
ii linux-headers-3.13.0-413.13.0-41.70
all Header files related to Linux kernel version 3.13.0
ii linux-headers-3.13.0-41-generic
I've confirmed that 3.13.0-41.70 isn't affected by bug #1346917 (KVM
NUMA stability), so this is an improvement over 3.13.11.11.
I will continue to test 3.13.0-41.70 for isci stability.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The 3.13.11.11 updates are now in the 3.13.0-41.70 kernel. Can you
apply the latest updates and see if the 3.13.0-41.70 kernel resolves
this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems that this 3.13.11 build is affected by this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917
Windows guests running on this kernel are very unstable and lose network
connectivity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I now 3.13.11-0313-generic running on four machines (all identical
hardware) at the moment and am stress testing on all nodes. The boot
behaviour is still similar to the 3.18-r5 kernel, thought the isci
driver still identifies itself as version 1.1 (and not 1.2).
I will continue to keep
Would it be possible to also test the latest upstream 3.13 kernel to see
if the fix already made it into stable updates? If it did not, we can
perform a reverse bisect to see the exact commit that fixes this issue.
The 3.13 upstream kernel can be downloaded from:
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
Title:
Trusty isci module doesn't handle timeouts properly
To manage notifications about this bug go to:
After a night of stress testing with the 3.18-rc5 packages I have not
been able to reproduce an unhandled SAS/SCSI event (the new kernel did
intensely dislike NTP and apparmour, but that's an other issue
altogether).
There were only two 'sas_scsi_recover_host' events early in the boot
process:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
I've installed the 3.18.0-031800rc5.201411162035 kernel packages and am
running load on the box now to see if I can get it to hiccough. Will
report back shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
Title:
Trusty isci module doesn't handle timeouts properly
To manage notifications about this bug go to:
** Summary changed:
- isci 1.1.0 doesn't handle timeouts properly
+ Trusty isci module doesn't handle timeouts properly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
Title:
Trusty isci
I had already attached apport output, but in the event that this was
insufficient I ran apport-collect as asked above.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Tags added: apport-collected
** Description changed:
I'm currently running linux 3.13.0-39 on trusty with a disks plugged
into an Intel C602 SATA/SAS controller. Occasionally, a timeout and/or
SAS event (I'm not 100% sure which..) isn't handled properly ('Unhandled
18 matches
Mail list logo
