[Bug 1609130] Re: IOError: [Errno 13] Permission denied: '/var/log/ovirt-guest-agent/ovirt-guest-agent.log'
There are multiple inconsistencies, actually. I had to use this cloud-init script to get the guest agent to launch: packages: - ovirt-guest-agent runcmd: - [ ln, -s, /dev/virtio-ports/ovirt-guest-agent.0, /dev/virtio-ports/com.redhat.rhevm.vdsm ] - [ chown, ovirtagent, /var/log/ovirt-guest-agent ] - [ chown, ovirtagent, /dev/virtio-ports/com.redhat.rhevm.vdsm ] - [ service, ovirt-guest-agent, start ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609130 Title: IOError: [Errno 13] Permission denied: '/var/log/ovirt-guest-agent /ovirt-guest-agent.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovirt-guest-agent/+bug/1609130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680774] Re: scsi device that can't be deleted
Previously, I was using kernel 3.19 and I don't remember having the issue. I don't really want to test an unstable kernel on production infrastructure. I was hoping for some concrete tips to troubleshoot scsi layer problems. Anyways, if I deployed it now, I could confirm that it does NOT happen in no less than half a year. The particular machine that failed now had an uptime of 119 days, another one with the same software has 135 days and counting. But taken together, I'm experiencing the same problem about every month in the cloud cluster. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680774 Title: scsi device that can't be deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680774] [NEW] scsi device that can't be deleted
Public bug reported: I'm using OpenStack on Ubuntu 14.04 with the 4.4.0-47 kernel. Volumes are being attached over Fibre Channel (qla2xxx adapter) with multipath. About once a month, a compute node fails to detach a volume. After that, the scsi device is left in a semi-deleted state: Normal device: root@cmp02:/sys/dev/block/65:96/device# ls /sys/dev/block/65:80/device block generic scsi_device bsg inquiry scsi_disk delete iocounterbits scsi_generic device_blocked iodone_cntscsi_level device_busy ioerr_cnt state dh_stateiorequest_cnt subsystem driver modalias timeout eh_timeout model type evt_capacity_change_reportedpower uevent evt_inquiry_change_reported queue_depth vendor evt_lun_change_reported queue_ramp_up_period vpd_pg80 evt_media_changequeue_typevpd_pg83 evt_mode_parameter_change_reported rescan evt_soft_threshold_reached rev Half-deleted device: root@cmp02:/sys/dev/block/65:96/device# ls /sys/dev/block/65:96/device block scsi_disk There is nothing interesting in /var/log/messages or /var/log/kern.log. multipath -l gives empty output, which pretty much blocks all operation of OpenStack on that node and forces me to reboot it. Tried issuing rescan on the FC adapters without success. The scsi device seems to be detached from the adapter. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680774 Title: scsi device that can't be deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Re: Dangling UDEV links after removing FC LUNs
It seems that the solution exists upstream: Udev version 213 implements locking. multipath-tools version 0.6.1 reads it. Is there a way to get these changes into Ubuntu 14.04? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799781 ** Bug watch added: Debian Bug tracker #799781 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799781 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631795] Re: Udev has a race condition with device mapper devices
Is my bug https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067 in series 14.04 a duplicate of this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631795 Title: Udev has a race condition with device mapper devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/631795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Re: Dangling UDEV links after removing FC LUNs
My feeling is that it is a race condition inside udev. There is a lot of
multipath devices on the system and I'm sometimes seeing messages that
udev is reaching its max children limit of 40.
The multipath -l call issues a lot of change events to udev.
OpenStack calls it and immediately begins deleting the scsi devices that
it gets in the reply. Udev processes the messages in a multithreaded way
and the change event arrives after the delete event. It is possible?
OpenStack does this and the device sdbc is the one affected by the bug:
016-12-05 10:38:40.646 500 INFO nova.compute.manager
[req-f5e6d9ff-1a0e-4455-8f60-0f9baea9d413 35c0bc8aaf3e43cea3f265b89c1216ee
e18099f000534ae89b8a978ec8e9b82c - - -]
[instance: a25caee0-2c74-4f91-a87b-e872cbd237e5] Detach volume
2992050a-d40d-4a6a-baa9-1a8f8624c838 from mountpoint /dev/vdb
2016-12-05 10:38:41.008 500 DEBUG oslo_concurrency.lockutils
[req-f5e6d9ff-1a0e-4455-8f60-0f9baea9d413 35c0bc8aaf3e43cea3f265b89c1216ee
e18099f000534ae89b8a978ec8e9b82c
- - -] Lock "connect_volume" acquired by "disconnect_volume" :: waited 0.000s
inner /usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:444
2016-12-05 10:38:41.009 500 DEBUG oslo_concurrency.processutils
[req-f5e6d9ff-1a0e-4455-8f60-0f9baea9d413 35c0bc8aaf3e43cea3f265b89c1216ee
e18099f000534ae89b8a978ec8e9b
82c - - -] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf
multipath -l 360002ac06b3800014ee8 execute
/usr/lib/python2.7/dist-packages/
oslo_concurrency/processutils.py:223
2016-12-05 10:38:41.333 500 DEBUG oslo_concurrency.processutils
[req-f5e6d9ff-1a0e-4455-8f60-0f9baea9d413 35c0bc8aaf3e43cea3f265b89c1216ee
e18099f000534ae89b8a978ec8e9b
82c - - -] CMD "sudo nova-rootwrap /etc/nova/rootwrap.conf multipath -l
360002ac06b3800014ee8" returned: 0 in 0.324s execute
/usr/lib/python2.7/dist-package
s/oslo_concurrency/processutils.py:254
2016-12-05 10:38:41.334 500 DEBUG nova.storage.linuxscsi
[req-f5e6d9ff-1a0e-4455-8f60-0f9baea9d413 35c0bc8aaf3e43cea3f265b89c1216ee
e18099f000534ae89b8a978ec8e9b82c - -
-] Found multipath device = /dev/mapper/360002ac06b3800014ee8
find_multipath_device
/usr/lib/python2.7/dist-packages/nova/storage/linuxscsi.py:135
2016-12-05 10:38:41.334 500 DEBUG nova.virt.libvirt.volume
[req-f5e6d9ff-1a0e-4455-8f60-0f9baea9d413 35c0bc8aaf3e43cea3f265b89c1216ee
e18099f000534ae89b8a978ec8e9b82c -
- -] devices to remove = [{'device': '/dev/sdbc', 'host': '1', 'id': '1',
'channel': '0', 'lun': '11'}, {'device': '/dev/sdbb', 'host': '1', 'id': '0',
'channel': '0',
'lun': '11'}, {'device': '/dev/sdbg', 'host': '2', 'id': '1', 'channel': '0',
'lun': '11'}, {'device': '/dev/sdbd', 'host': '2', 'id': '0', 'channel': '0',
'lun': '11'
}] disconnect_volume
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py:1403
2016-12-05 10:38:41.335 500 DEBUG nova.storage.linuxscsi [-] Trying (1) to
remove device /dev/sdbc _wait_for_remove
/usr/lib/python2.7/dist-packages/nova/storage/linuxs
csi.py:77
2016-12-05 10:38:41.335 500 DEBUG oslo_concurrency.processutils [-] Running cmd
(subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf tee -a
/sys/bus/scsi/drivers/sd
/1:0:1:11/delete execute
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:223
2016-12-05 10:38:41.455 500 DEBUG oslo_concurrency.processutils [-] CMD "sudo
nova-rootwrap /etc/nova/rootwrap.conf tee -a
/sys/bus/scsi/drivers/sd/1:0:1:11/delete" ret
urned: 0 in 0.119s execute
/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:254
2016-12-05 10:38:41.456 500 DEBUG oslo_concurrency.processutils [-] Running cmd
(subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf sginfo -r execute
/usr/lib/pyth
on2.7/dist-packages/oslo_concurrency/processutils.py:223
2016-12-05 10:38:41.543 500 DEBUG oslo_concurrency.processutils [-] CMD "sudo
nova-rootwrap /etc/nova/rootwrap.conf sginfo -r" returned: 0 in 0.087s execute
/usr/lib/py
thon2.7/dist-packages/oslo_concurrency/processutils.py:254
... and the same for the other 3 devices
Udev log, which is pretty unreadable because of all the multithreading, shows
this:
found 'b67:96' claiming
'/run/udev/links/\x2fdisk\x2fby-path\x2fpci-:05:00.0-fc-0x21120002ac014ee8-lun-11'
creating link '/dev/disk/by-path/pci-:05:00.0-fc-0x21120002ac014ee8-lun-11'
to '/dev/sdbc'
preserve already existing symlink
'/dev/disk/by-path/pci-:05:00.0-fc-0x21120002ac014ee8-lun-11' to
'../../sdbc'
...
handling device node '/dev/sdbc', devnum=b67:96, mode=0600, uid=0, gid=0
can not stat() node '/dev/sdbc' (No such file or directory)
created db file '/run/udev/data/b67:96' for
'/devices/pci:00/:00:02.0/:05:00.0/host1/rport-1:0-1/target1:0:1/1:0:1:11/block/sdbc'
adding watch on '/dev/sdbc'
inotify_add_watch(6, /dev/sdbc, 10) failed: No such file or directory
created db file '/run/udev/data/b67:96' for
[Bug 1647067] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786941/+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/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786943/+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/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786940/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786942/+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/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Re: Dangling UDEV links after removing FC LUNs
apport information ** Tags added: apport-collected trusty ** Description changed: We're using Q-Logic QLE2562 Fibre Channel adapters (qla2xxx driver) against a HPE 3PAR 7400c storage array in an OpenStack environment. The OpenStack 3PAR driver manages volume attachments from the array to the servers. There is 4 path multipath to every volume. As the LUNs are removed, sometimes udev does not remove all links, particularly in /run/udev/links and /dev/disk/by-path. The symptoms are multiple records in one by-path directory under /run/udev/links, broken links to no longer attached luns in dev/disk/by-path and links between wrong LUNs and scsi devices there. OpenStack relies on these links. When another volume is attached using a LUN that has these leftover links and it happens that it is the first of the 4 paths, OpenStack incorrectly identifies the volume and attaches the same volume to multiple instances, leading to data loss. What could be causing this behavior? Ubuntu version 14.04 Linux version Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24 udev 204-5ubuntu20.19 + --- + ApportVersion: 2.14.1-0ubuntu3.21 + Architecture: amd64 + CustomUdevRuleFiles: 20-3par-unmap.rulez + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2015-10-01 (429 days ago) + InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + MachineType: HP ProLiant DL380 Gen9 + Package: udev 204-5ubuntu20.19 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/hostname--vg-root ro + ProcVersionSignature: Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24 + Tags: trusty + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 4.4.0-47-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/03/2014 + dmi.bios.vendor: HP + dmi.bios.version: P89 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL380 Gen9 + dmi.sys.vendor: HP ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786936/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786944/+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/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786938/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786937/+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/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786939/+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/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1647067/+attachment/4786945/+files/UdevDb.txt ** Changed in: udev (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Re: Dangling UDEV links after removing FC LUNs
** Package changed: linux (Ubuntu) => udev (Ubuntu) ** Changed in: udev (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] Re: Dangling UDEV links after removing FC LUNs
** Description changed: We're using Q-Logic QLE2562 Fibre Channel adapters (qla2xxx driver) against a HPE 3PAR 7400c storage array in an OpenStack environment. The OpenStack 3PAR driver manages volume attachments from the array to the servers. There is 4 path multipath to every volume. As the LUNs are removed, sometimes udev does not remove all links, particularly in /run/udev/links and /dev/disk/by-path. The symptoms are multiple records in one by-path directory under /run/udev/links, broken links to no longer attached luns in dev/disk/by-path and links between wrong LUNs and scsi devices there. OpenStack relies on these links. When another volume is attached using a LUN that has these leftover links and it happens that it is the first of the 4 paths, OpenStack incorrectly identifies the volume and attaches the same volume to multiple instances, leading to data loss. What could be causing this behavior? + + Ubuntu version 14.04 + Linux version Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24 + udev 204-5ubuntu20.19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647067] [NEW] Dangling UDEV links after removing FC LUNs
Public bug reported: We're using Q-Logic QLE2562 Fibre Channel adapters (qla2xxx driver) against a HPE 3PAR 7400c storage array in an OpenStack environment. The OpenStack 3PAR driver manages volume attachments from the array to the servers. There is 4 path multipath to every volume. As the LUNs are removed, sometimes udev does not remove all links, particularly in /run/udev/links and /dev/disk/by-path. The symptoms are multiple records in one by-path directory under /run/udev/links, broken links to no longer attached luns in dev/disk/by-path and links between wrong LUNs and scsi devices there. OpenStack relies on these links. When another volume is attached using a LUN that has these leftover links and it happens that it is the first of the 4 paths, OpenStack incorrectly identifies the volume and attaches the same volume to multiple instances, leading to data loss. What could be causing this behavior? Ubuntu version 14.04 Linux version Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24 udev 204-5ubuntu20.19 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647067 Title: Dangling UDEV links after removing FC LUNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254837] Re: hostap_cs causes kernel oops on 2.6.26 with senao nl-2511cd
Greetings, have you seen this article? http://www.aircrack-ng.org/doku.php?id=hostap What you are experiencing may be the shared irq bug in hostap. The patch they have there helped me. I cannot confirm the script, because I didn't have orinoco_cs compiled before I patched the kernel, but I managed to insert the card after some fiddling with modprobe and cardctl, so it may work as well. The kernel is also 2.6.24, though the distro is far from Ubuntu. wondra -- hostap_cs causes kernel oops on 2.6.26 with senao nl-2511cd https://bugs.launchpad.net/bugs/254837 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
