[Kernel-packages] [Bug 1807974] Re: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370
Bionic was rock solid for me - Focal has been a nightmare of crashes. I
can disconnect from the AP and reconnect and it comes back to life.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807974
Title:
Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless
regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
on Dell XPS 13 9370
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease:
[Kernel-packages] [Bug 1605137] Re: Can still ping container IP address after removing container
I'm going to have to put this on the back burner for a while, sorry. I've got a ton of other stuff to do before I can return to this. I want to set up a VM that I can snapshot and destroy for any testing that you need. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1605137 Title: Can still ping container IP address after removing container Status in linux package in Ubuntu: Triaged Bug description: Using version 2.0.3-0ubuntu2~ubuntu16.04.1~ppa1 I created a container, and then put a tagged vlan on top of lxdbr0 so that I can talk to the host and other containers on a second network. I gave the host's lxdbr0.1215 an IP address, and made eth0.1215 in the container also with its own IP address. After removing the container, I can still ping the address on the VLAN! It also responds with duplicates: $ arping -I lxdbr0.1215 192.168.15.20 ARPING 192.168.15.20 from 192.168.15.1 lxdbr0.1215 Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.599ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.607ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.609ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.534ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.541ms $ ping 192.168.15.20 PING 192.168.15.20 (192.168.15.20) 56(84) bytes of data. 64 bytes from 192.168.15.20: icmp_seq=1 ttl=64 time=0.108 ms 64 bytes from 192.168.15.20: icmp_seq=1 ttl=64 time=0.126 ms (DUP!) 64 bytes from 192.168.15.20: icmp_seq=1 ttl=64 time=0.144 ms (DUP!) 64 bytes from 192.168.15.20: icmp_seq=2 ttl=64 time=0.051 ms Bizarrely: $ nmap 192.168.15.20 Starting Nmap 7.01 ( https://nmap.org ) at 2016-07-21 19:01 AEST Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.02 seconds (Supplying -Pn shows all ports are closed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Changed in: maas Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Fix Released Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304808] Re: All USB ports/devices randomly stop working
@Joseph: It's stopped happening for me now the only change I made was to revert to the older nvidia driver available in trusty as the newer one causes Xorg crashes for me. Can the USB problems really be linked to other kernel modules like this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304808 Title: All USB ports/devices randomly stop working Status in “linux” package in Ubuntu: Confirmed Bug description: I do not know how to reliably reproduce this, but since an update in trusty a couple of days ago I am getting a random USB device stop working and then they all start going one by one. The mouse and keyboard included in this of course. This has happened to me before and it was fixed in saucy. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 2480 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 9 15:07:40 2014 HibernationDevice: RESUME=UUID=73dd7b46-df18-4ae4-9a16-7e635959e1b1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-01-20 (78 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202 dmi.board.name: M3N72-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304808] Re: All USB ports/devices randomly stop working
I am unable to test the upstream kernel as X no longer works; it said it had built my nvidia module but it still failed to load under the new kernel, which leaves me with no desktop. ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304808 Title: All USB ports/devices randomly stop working Status in “linux” package in Ubuntu: Confirmed Bug description: I do not know how to reliably reproduce this, but since an update in trusty a couple of days ago I am getting a random USB device stop working and then they all start going one by one. The mouse and keyboard included in this of course. This has happened to me before and it was fixed in saucy. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 2480 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 9 15:07:40 2014 HibernationDevice: RESUME=UUID=73dd7b46-df18-4ae4-9a16-7e635959e1b1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-01-20 (78 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202 dmi.board.name: M3N72-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304808] Re: All USB ports/devices randomly stop working
In fact previously installed kernels are not working for the same reason. How can I fix this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304808 Title: All USB ports/devices randomly stop working Status in “linux” package in Ubuntu: Confirmed Bug description: I do not know how to reliably reproduce this, but since an update in trusty a couple of days ago I am getting a random USB device stop working and then they all start going one by one. The mouse and keyboard included in this of course. This has happened to me before and it was fixed in saucy. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 2480 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 9 15:07:40 2014 HibernationDevice: RESUME=UUID=73dd7b46-df18-4ae4-9a16-7e635959e1b1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-01-20 (78 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202 dmi.board.name: M3N72-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304808] [NEW] All USB ports/devices randomly stop working
Public bug reported: I do not know how to reliably reproduce this, but since an update in trusty a couple of days ago I am getting a random USB device stop working and then they all start going one by one. The mouse and keyboard included in this of course. This has happened to me before and it was fixed in saucy. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 2480 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 9 15:07:40 2014 HibernationDevice: RESUME=UUID=73dd7b46-df18-4ae4-9a16-7e635959e1b1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-01-20 (78 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202 dmi.board.name: M3N72-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304808 Title: All USB ports/devices randomly stop working Status in “linux” package in Ubuntu: New Bug description: I do not know how to reliably reproduce this, but since an update in trusty a couple of days ago I am getting a random USB device stop working and then they all start going one by one. The mouse and keyboard included in this of course. This has happened to me before and it was fixed in saucy. This is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 2480 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 9 15:07:40 2014 HibernationDevice: RESUME=UUID=73dd7b46-df18-4ae4-9a16-7e635959e1b1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-01-20 (78 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202 dmi.board.name: M3N72-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Changed in: maas Status: New = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Ok so here's the bug: maas_ipmi_autodetect.py looks for a user slot called maas, and reprograms that first. If it does not exist then it defaults to User10. User10 does not exist on this hardware. What it should be doing: * Look for a user called maas and re-use or re-program * Failing that, look for an empty slot * Failing that, go for User4 (or perhaps make this depend on the type of BMC detected?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
