[Bug 1087860] Re: [Precise/Quantal] MISC: hpilo, remove pci_disable_device
** Tags removed: verification-needed-quantal ** Tags added: verification-done-quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087860 Title: [Precise/Quantal] MISC: hpilo, remove pci_disable_device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089623] Re: [Quantal] Include hpsa: gen8plus Smart Array IDs
verified that the driver has the pci ids needed for smary array for Gen8Plus servers. ** Tags removed: verification-needed-quantal ** Tags added: verification-done-quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1089623 Title: [Quantal] Include hpsa: gen8plus Smart Array IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087860] Re: [Precise/Quantal] MISC: hpilo, remove pci_disable_device
** Tags removed: verification-needed-precise ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087860 Title: [Precise/Quantal] MISC: hpilo, remove pci_disable_device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
Both controller ports are NIC types. But i can see the same MAC address for both NIC iSCSI type of device and it may cause the biosdevname not to act correctly. Here are the NICs MAC address exposed to the system. Only option i have here in BIOS is either iSCSI or FCOE for four embedded ports. I am contacting with NIC team to find out is there any way to overcome having same MAC for different type of NIC and iSCSI. NIC Port 1 00:17:a4:77:3c:00 NIC Port 2 00:17:a4:77:3c:02 NIC Port 9 00:17:a4:77:3c:04 NIC Port 10 00:17:a4:77:3c:06 NIC Port 3 00:17:a4:77:3c:08 iSCSI Port 1 00:17:a4:77:3c:08 NIC Port 4 00:17:a4:77:3c:0a iSCSI Port 2 00:17:a4:77:3c:0a NIC Port 11 00:17:a4:77:3c:0c iSCSI Port 3 00:17:a4:77:3c:0c NIC Port 12 00:17:a4:77:3c:0e iSCSI Port 4 00:17:a4:77:3c:0e NIC Port 5 b4:99:ba:a6:b9:18 NIC Port 7 b4:99:ba:a6:b9:19 NIC Port 6 b4:99:ba:a6:b9:1c NIC Port 8 b4:99:ba:a6:b9:1d NIC Port 13 b4:99:ba:a6:b9:20 NIC Port 15 b4:99:ba:a6:b9:21 NIC Port 14 b4:99:ba:a6:b9:24 NIC Port 16 b4:99:ba:a6:b9:25 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] [NEW] biosdevname gives name of device as rename7 in Quantal
Public bug reported: In Quantal kernel biosdevname feature is not working as it suppose to be. On hardware we are seeing an issue where few of the network interface names are named as rename7 etc.. while biosdevname -d utility provides the correct biosname while kernel name have been messed up. There are total 16 network interfaces on the server which are ALOMs for Emulex card connected to system. It seems this issue is a race condition and will get fixed in Fedora 18. But having fix in Quantal will help also. https://bugzilla.redhat.com/show_bug.cgi?id=782145 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: quantal ** Attachment added: Screenshotfrom2012-12-0615:20:56.png https://bugs.launchpad.net/bugs/1090002/+attachment/3459206/+files/Screenshotfrom2012-12-0615%3A20%3A56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
can not run the apport-collect on the machine as machine is not on the network. And proxys are not allowing me to run the same successfully. there is no crash in the package or utility so i don't think apport will collect any useful information from the system. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
I am attaching the logs you also. also i am attaching the logs of biosdevname -d which will give you info that biosname of device is correct. I am seeing 70-persistent-net.rules is empty and rules to generate the name is in 71-biosdevname.rules which i am attaching. After commenting the line in 71-biosdevname.rules which generates the name en1-16 and rename i am seeing all devices are named as eth0-17 and 70-persistent-net.rules contain the mapping of MAC address with the eth0-15 device name. I am attaching the below required logs. - /var/log/syslog - /var/log/udev - output of dmesg - output of ifconfig -a - /etc/udev/rules.d/70-persistent-net.rules - /lib/udev/rules.d/71-biosdevname.rules - biosdevname -d ** Attachment added: Attaching the required logs https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+attachment/3459300/+files/1090002.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
adding debug.tar which we got after running few biosdevname command during udev. ** Attachment added: debug.tar https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+attachment/3459417/+files/debug.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
debug logs for lspci, dmidecode and biosdecode have been attached. ** Attachment added: debuglog.tar https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+attachment/3459482/+files/debuglog.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053306] Re: iscsiadm hangs in recvmsg()
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053306 Title: iscsiadm hangs in recvmsg() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1053306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053306] Re: iscsiadm hangs in recvmsg()
I tried the same with p4500 SAN box and I am able to reproduce the issue in our lab with the script provided by Dann. I have downloaded, build and install open-iscsi-2.0-873.tar.gz version of paxkage and and running then now without any issues so far. Will keep an eye on it and let you guys knows in case find different option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053306 Title: iscsiadm hangs in recvmsg() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1053306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1042903] Re: mgag200 driver hangs on HP ProLiant Gen 8 platform
HP offshore team tried 3.5.0-13.13 kernel and they were seeing the same problem. On 08/28/2012 04:24 PM, Leann Ogasawara wrote: I wanted to relay the following here in the bug report...I was notified of a commit in the latest upstream v3.5.3 release. I thought it would be interesting to test the latest Ubuntu 3.5.0-13.13 which was rebased to this latest v3.5.3 upstream stable release. Narinder and I didn't originally test this latest Ubuntu kernel as I only uploaded it yesterday. Anyways, I see the following commit included there: commit be67f30591ffe86e250955645a97e3d68f5a2cdf Author: Dave Airlie airl...@gmail.com Date: Thu Aug 9 15:00:15 2012 +1000 drm/mgag200: fix G200ER pll picking algorithm commit 9830605d4c070b16ec5c24a75503877cc7698409 upstream. The original code was misported from the X driver, a) an int went to unsigned int, breaking the downward counting testm code b) the port did the vco/computed clock bits completely wrong. This fixes an infinite loop on modprobe on some Dell servers with the G200ER chipset variant. Found in internal testing. Signed-off-by: Dave Airlie airl...@redhat.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org So the issue which was being seen might be the fix with the above and thus allow us to keep the mgag200 driver enabled. I figured it wouldn't hurt to test anyways. Thanks. -- Thanks and Regards, Narinder Gupta (PMP) narinder.gu...@canonical.com Technical Account Manager Canonical, Ltd.narindergupta [irc.freenode.net] +1.281.736.5150narindergupta2007[skype] Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042903 Title: mgag200 driver hangs on HP ProLiant Gen 8 platform To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1042903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1042903] Re: mgag200 driver hangs on HP ProLiant Gen 8 platform
I have added a Bugzilla at kernel.org and here is the bugzilla details. *Bug 46591* https://bugzilla.kernel.org/show_bug.cgi?id=46591 - Matrox g200 driver mgag200 hangs on HP ProLiant Gen8 Platform (edit https://bugzilla.kernel.org/post_bug.cgi#) On 08/28/2012 02:28 PM, Leann Ogasawara wrote: After an extensive series of tests, we've determined that the following kernel config change is the root cause of the issue: commit 682f607fd4a57d273db9ecc360589a8fa9cec8e6 Author: Andy Whitcroft a...@canonical.com Date: Fri Jul 20 21:33:43 2012 +0100 UBUNTU: [Config] Enable CONFIG_DRM_AST/_CIRRUS_QEMU/_MGAG200 The above config change enabled the mgag200 driver which is described as follows: config DRM_MGAG200 tristate Kernel modesetting driver for MGA G200 server engines depends on DRM PCI EXPERIMENTAL select FB_SYS_FILLRECT select FB_SYS_COPYAREA select FB_SYS_IMAGEBLIT select DRM_KMS_HELPER select DRM_TTM help This is a KMS driver for the MGA G200 server chips, it does not support the original MGA G200 or any of the desktop chips. It requires 0.3.0 of the modesetting userspace driver, and a version of mga driver that will fail on KMS enabled devices. This driver is marked as EXPERIMENTAL. Our default config policy is to enable device specific experimental options to promote testing and feedback. However, should any experimental option produce adverse affects, we will disable them. As such, I've built a test kernel with CONFIG_DRM_MGAG200 disabled and we have confirmed this resolves the issue [1]. I've committed this change to the Quantal kernel git repository. It should be included in the subsequent 3.5.0-13.14 or newer upload. This however may unfortunately not land in time for the Quantal Beta-1 release. However, it will land well in advance of 12.10 being final. A temporary workaround aside from running the test kernel [1] is to blacklist the mgag200 driver. [1] http://people.canonical.com/~ogasawara/lp1039178/ ** Project changed: linux = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed -- Thanks and Regards, Narinder Gupta (PMP) narinder.gu...@canonical.com Technical Account Manager Canonical, Ltd.narindergupta [irc.freenode.net] +1.281.736.5150narindergupta2007[skype] Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042903 Title: mgag200 driver hangs on HP ProLiant Gen 8 platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042903] Re: mgag200 driver hangs on HP ProLiant Gen 8 platform
** Bug watch added: Linux Kernel Bug Tracker #46591 http://bugzilla.kernel.org/show_bug.cgi?id=46591 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042903 Title: mgag200 driver hangs on HP ProLiant Gen 8 platform To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1042903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
