** 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
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.
** 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
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
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.
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)
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
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,
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
** 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
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
...@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
/
** 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
** 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
101 - 114 of 114 matches
Mail list logo
