@m.morana - to my knowledge modern kernel's still don't have a namespace
aware ISCSI netlink implementation. In an OpenStack context, I recall
seeing something about changing nova's volume attach code to use qemu's
native iSCSI support which may be a workaround for iscsiadm and native
block device
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 prope
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 tim
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.
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
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 su
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 press
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: one
** 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:
h
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.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263405/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263404/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263401/+files/Lspci.txt
--
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:
Trus
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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263400/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263403/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
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 Ubun
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263406/+files/UdevDb.txt
--
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:
Tr
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263402/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1394032/+attachment/4263407/+files/UdevLog.txt
--
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:
** 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 modu
I have seen mentions of isci and libsas getting timeout fixes, and I
know that 3.18 is using newer libsas and isci code than we have in 3.13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394032
Titl
dmesg output of the driver initializing:
$ dmesg -T | grep iscsi
[Mon Nov 17 19:42:20 2014] isci: Intel(R) C600 SAS Controller Driver - version
1.1.0
[Mon Nov 17 19:42:20 2014] isci :02:00.0: driver configured for rev: 6
silicon
[Mon Nov 17 19:42:20 2014] isci :02:00.0: OEM parameter tab
Public bug reported:
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
error code') and the kernel gets a bit upset.
I have 12 diffe
I'm also curious about an update on this issue. I'm running 14.04.1,
Kernel 3.13.0-39-generic and LXC 1.0.6-0ubuntu0.1. 'strace' output of
open-scsi looks basically the same as above.
As I understand it, this is related to iSCSI's Netlink implementation
not being namespace aware? I would love t
Sorry, I left that out... :\
I've tried America/Montreal and America/Detroit -- both with no luck.
America/Montreal is my preferred.
--
Evolution displays wrong time after new dst
https://launchpad.net/bugs/91637
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
I'm running a fully patched Dapper and after installing the flurry of
evolution updates yesterday (killing processes and doing a full reboot)
all of my appointments are still an hour off (I have a reoccurring
appointment that is the proper time on March 5th and the wrong time on
March 12th).
Have
Public bug reported:
Binary package hint: evolution-data-server
Ubuntu Dapper fully up-to-date according to apt.
Package version information:
$ dpkg -l | grep -i evolution | awk {'print $2 " - "$3 '}
beagle-backend-evolution - 0.2.6-1ubuntu5
evolution - 2.6.1-0ubuntu7
evolution-data-server - 1.6
I've run the timezone updater as well, to fix my local JVM's zone
database but the package really should be synchronized with Sun's latest
1.5.X release (which does have proper DST values).
--
Java reports time zone incorrectly during CDT (US Daylight saving time)
https://launchpad.net/bugs/49068
I've run into this problem now as well, and consider it fairly serious.
Not having my multi-terabyte RAID array attached to my shiny new Ubuntu
NAS-head is a major blocker on my Ubuntu deployment.
Any chance that we're going to see this patch included in an update
sometime very soon?
--
mdrun fa
30 matches
Mail list logo