[Bug 1801052] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207817/+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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207818/+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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207815/+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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207813/+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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207816/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207819/+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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207820/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207814/+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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] Re: arm64 kvm-unit-tests timer test failing on 18.04
apport information ** Tags added: apport-collected ** Description changed: kvm-unit-tests performs 12 timer tests in the latest version, one of them failing with the latest Ubuntu LTS kernel. This issue has been fixed in mainline commits 7afc4ddbf299a13aaf28406783d141a34c6b4f5a and 245715cbe83ca934af5d20e078fd85175c62995e (part of 4.19.0 release), which are tagged with "Cc: Stable # 4.15+" and "Fixes: ...". Could you please backport them to your tree? "patch" applies them with some fuzz only (no additional fixing needed). Here is what I did: - Boot 4.15.0-38-generic on an ARM Juno r1 board (but every arm64 h/w would do). - Run kvm-unit-tests: $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git $ cd kvm-unit-tests $ ./configure && make $ ./run_tests.sh This will mark the timer test as failed: FAIL timer (12 tests, 1 unexpected failures) A more detailed log can be get by: $ arm/run arm/timer.flat I then fetched the official Ubuntu kernel (apt-get source), applied the two patches mentioned above and rebuilt the kernel (with the .config from /boot). This will report the timer as pass: PASS timer (12 tests) So could you please backport those two patches to make kvm-unit-tests (and its users) happy? Btw: I was wondering whether you have some process to find those stable fixes, even with the 4.15 base kernel being EOL for quite a while now. Please bear with me if you do and I was just too impatient ;-) Thanks! Andre + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 28 2018 seq + crw-rw 1 root audio 116, 33 Jan 28 2018 timer + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-38-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=vt220 + PATH=(custom, no user) + XDG_RUNTIME_DIR= + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: console=ttyAMA0,115200n8 root=/dev/sda3 rw rootwait earlycon=pl011,0x7ff8 debug + ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-38-generic N/A + linux-backports-modules-4.15.0-38-generic N/A + linux-firmware 1.173.1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-38-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1801052/+attachment/5207812/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801052] [NEW] arm64 kvm-unit-tests timer test failing on 18.04
Public bug reported: kvm-unit-tests performs 12 timer tests in the latest version, one of them failing with the latest Ubuntu LTS kernel. This issue has been fixed in mainline commits 7afc4ddbf299a13aaf28406783d141a34c6b4f5a and 245715cbe83ca934af5d20e078fd85175c62995e (part of 4.19.0 release), which are tagged with "Cc: Stable # 4.15+" and "Fixes: ...". Could you please backport them to your tree? "patch" applies them with some fuzz only (no additional fixing needed). Here is what I did: - Boot 4.15.0-38-generic on an ARM Juno r1 board (but every arm64 h/w would do). - Run kvm-unit-tests: $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git $ cd kvm-unit-tests $ ./configure && make $ ./run_tests.sh This will mark the timer test as failed: FAIL timer (12 tests, 1 unexpected failures) A more detailed log can be get by: $ arm/run arm/timer.flat I then fetched the official Ubuntu kernel (apt-get source), applied the two patches mentioned above and rebuilt the kernel (with the .config from /boot). This will report the timer as pass: PASS timer (12 tests) So could you please backport those two patches to make kvm-unit-tests (and its users) happy? Btw: I was wondering whether you have some process to find those stable fixes, even with the 4.15 base kernel being EOL for quite a while now. Please bear with me if you do and I was just too impatient ;-) Thanks! Andre ** 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/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config
> There are numerous drivers disabled... The 64-bit Allwinner SoCs share a lot of devices with their 32-bit predecessors (or siblings), so we also share some config symbols, most prominently ARCH_SUNXI. However some of those supported devices are only in older SoCs (Sun4i generation, for instance), and will never be needed for an *arm64* kernel (take Sun4i sound drivers, for example). In the wake of avoiding to bloat the kernel (or the number of modules) needlessly, we can safely disable drivers for which there is no AArch64 capable SoC using those devices. I marked those as "not in 64-bit Allwinner SoCs" in the list above. > The way we normally handle boot-critical modules ... I understand that, and can see the reasons why. It's just for my work (hacking and testing kernels, and not being on Ubuntu) it's very inconvenient to always build a matching initrd, and it's just those two symbols needed to boot into an SD card based rootfs without one. If this is of no concern for you, then it's fine to leave them as =m. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config
So I checked out the latest Ubuntu kernel (based on 4.12.8) and enabled the options as mentioned above, which leads to the (attached) diff against the config grabbed from here: http://kernel.ubuntu.com/~kernel-ppa/config/artful/linux/4.12.0-12.13/arm64-config.flavour.generic These options should comply with the Ubuntu .config rules as I understand them (=m whenever possible), but require an initramfs to boot (from SD card). Compiling in CONFIG_MMC_SUNXI and CONFIG_REGULATOR_FIXED_VOLTAGE allow to access the rootfs without modules (handy for bootstrapping). ** Patch added: ".config diff to enable Allwinner arm64 support" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+attachment/4936707/+files/ubuntu_config_sunxi.diff ** Changed in: linux (Ubuntu Artful) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config
Back from holidays, so here is the list of options for the arm64 kernel .config. I copied your list from above and changed the options accordingly, adding comments with explanations. Let me know if you need more information. CONFIG_ARCH_SUNXI=y # CONFIG_AHCI_SUNXI is not set ## no SATA in 64-bit Allwinner SoCs CONFIG_DMA_SUN6I=m # CONFIG_DWMAC_SUNXI is not set ## no GMAC in 64-bit Allwinner SoCs CONFIG_IR_SUNXI=m # CONFIG_KEYBOARD_SUN4I_LRADC is not set ## not in 64-bit Allwinner SoCs # CONFIG_MDIO_SUN4I is not set ## not in 64-bit Allwinner SoCs # CONFIG_MFD_AC100 is not set## not used on boards with 64-bit Allwinner SoCs CONFIG_MFD_AXP20X_RSB=m CONFIG_MFD_SUN4I_GPADC=m CONFIG_MFD_SUN6I_PRCM=y CONFIG_MMC_SUNXI=m # CONFIG_MTD_NAND_SUNXI is not set ## not used on boards with 64-bit Allwinner SoCs CONFIG_NET_VENDOR_ALLWINNER=y CONFIG_NVMEM_SUNXI_SID=m CONFIG_PHY_SUN4I_USB=m # CONFIG_PHY_SUN9I_USB is not set## not in 64-bit Allwinner SoCs # CONFIG_PINCTRL_SUN4I_A10 is not set CONFIG_PINCTRL_SUN50I_A64=y CONFIG_PINCTRL_SUN50I_A64_R=y CONFIG_PINCTRL_SUN50I_H5=y # CONFIG_PINCTRL_SUN5I is not set # CONFIG_PINCTRL_SUN6I_A31 is not set # CONFIG_PINCTRL_SUN6I_A31_R is not set # CONFIG_PINCTRL_SUN7I_A20 is not set # CONFIG_PINCTRL_SUN8I_A23 is not set # CONFIG_PINCTRL_SUN8I_A23_R is not set # CONFIG_PINCTRL_SUN8I_A33 is not set # CONFIG_PINCTRL_SUN8I_A83T is not set # CONFIG_PINCTRL_SUN8I_H3 is not set CONFIG_PINCTRL_SUN8I_H3_R=y # CONFIG_PINCTRL_SUN8I_V3S is not set # CONFIG_PINCTRL_SUN9I_A80 is not set # CONFIG_PINCTRL_SUN9I_A80_R is not set CONFIG_PINCTRL_SUNXI=y CONFIG_PWM_SUN4I=m CONFIG_RESET_SUNXI=y # CONFIG_RTC_DRV_AC100 is not set## not used on boards with 64-bit Allwinner SoCs CONFIG_RTC_DRV_SUN6I=y # CONFIG_SERIO_SUN4I_PS2 is not set ## not in 64-bit Allwinner SoCs # CONFIG_SND_SUN4I_CODEC is not set ## not in 64-bit Allwinner SoCs # CONFIG_SND_SUN4I_I2S is not set## not in 64-bit Allwinner SoCs # CONFIG_SND_SUN4I_SPDIF is not set ## not in 64-bit Allwinner SoCs CONFIG_SND_SUN8I_CODEC_ANALOG=m # CONFIG_SPI_SUN4I is not set## not in 64-bit Allwinner SoCs CONFIG_SPI_SUN6I=m # CONFIG_SUN4I_EMAC is not set ## not in 64-bit Allwinner SoCs # CONFIG_SUN4I_GPADC is not set ## not (yet?) supported CONFIG_SUN50I_A64_CCU=y CONFIG_SUN8I_H3_CCU=y## drives the H5 as well CONFIG_SUN8I_R_CCU=y CONFIG_SUNXI_CCU=y CONFIG_SUNXI_CCU_DIV=y CONFIG_SUNXI_CCU_FRAC=y CONFIG_SUNXI_CCU_GATE=y CONFIG_SUNXI_CCU_MP=y CONFIG_SUNXI_CCU_MUX=y CONFIG_SUNXI_CCU_NK=y CONFIG_SUNXI_CCU_NKM=y CONFIG_SUNXI_CCU_NKMP=y CONFIG_SUNXI_CCU_NM=y CONFIG_SUNXI_CCU_PHASE=y CONFIG_SUNXI_RSB=m ## supported in upcoming kernels CONFIG_SUNXI_SRAM=y CONFIG_SUNXI_WATCHDOG=m # CONFIG_TOUCHSCREEN_SUN4I is not set## not (yet?) supported CONFIG_USB_MUSB_SUNXI=m Not covered by the default config when enabling ARCH_SUNXI, but please add: CONFIG_I2C_MV64XXX=m ## the I2C controller used in both A64 and H5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config
Hi, Thanks for having a look, and sorry for the delay. Yes, CONFIG_PHY_SUN4I_USB=m is OK. We can at least disable (=n) the following options: CONFIG_AHCI_SUNXI=n CONFIG_DWMAC_SUNXI=n CONFIG_MFD_AC100=n CONFIG_MTD_NAND_SUNXI=n CONFIG_RTC_DRV_AC100=n CONFIG_SERIO_SUN4I_PS2=n CONFIG_SPI_SUN4I=n CONFIG_SUN4I_EMAC=n as these devices are in older SoCs which don't have arm64 cores. There are probably more options which we don't need, but I need to check them later on a Linux box (just on a lousy tablet here, atm). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config
This is really more of a feature request than a bug report, but I couldn't find a better place or tag to file this. So my apologies if this isn't the right way of requesting this. For a way to reproduce this: Without ARCH_SUNXI a kernel does not contain the pinctrl and clock drivers crucial for any kind of I/O. The only thing that should work is "earlycon=uart,mmio32,0x1c28000". Enabling ARCH_SUNXI should make the proper UART driver work, so "console=ttyS0,115200" would give any output. Enabling the other symbols mentioned above allow mass storage via uSD card and USB. ** 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/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701137] [NEW] enable ARCH_SUNXI (and friends) in arm64 kernel .config
Public bug reported: The mainline support for the ARM64 Allwinner SoCs (featured on the Pine64 boards and the Pinebook notebook, for instance, as well as other development boards like the BananaPi-M64) has come a long way by now, since 4.11 we have MMC and USB support working. Now can we just enable the proper .config bits to make the official Ubuntu kernel support those boards? The latest mainline U-Boot can load an EFI grub from some UEFI ESP partition, so any standard EFI installer should work. Apart from some minor hiccup (a missing MBR bootable flag/MBR at all) this works already with the Debian-testing netinst installer. The config symbols needed for decent support are (all enabled by the latest Debian kernel and the official mainline defconfig): ARCH_SUNXI=y CONFIG_USB_MUSB_SUNXI=m CONFIG_MMC_SUNXI=m CONFIG_RTC_DRV_SUN6I=y CONFIG_PHY_SUN4I_USB=y Those enable MMC and USB (the mandatory clocks, pinctrl and UART are enabled by default) and make those boards quite usable already. The on-SoC Ethernet driver will probably be merged into 4.13-rc1. Optionally: CONFIG_I2C_MV64XXX=m CONFIG_SPI_SUN6I=m give us I2C and SPI support as well. So can we add those symbols to the Ubuntu kernel .config to give users an out-of-the-box experience? Cheers, Andre. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701137 Title: enable ARCH_SUNXI (and friends) in arm64 kernel .config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196946] [NEW] installer lacks support for Calxeda ECX-2000
Public bug reported: On a Calxeda ECX-2000 (aka Midway) system the device tree model name is different than that on Highbank, so the installer reports "unknown" instead of the expected "generic". Easy fix is to add a matching line for Midway. The name comes from the kernel device tree: arch/arm/boot/dts/ecx-2000.dts ** Affects: libdebian-installer (Ubuntu) Importance: Undecided Status: New ** Patch added: "libdebian-installer_ecx_2000.patch" https://bugs.launchpad.net/bugs/1196946/+attachment/3721814/+files/libdebian-installer_ecx_2000.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196946 Title: installer lacks support for Calxeda ECX-2000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdebian-installer/+bug/1196946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556480] Re: kernel crash under KVM when on AMD Magny-Cours
I have now built the kernel from source (with the server config). It crashes on KVM with -cpu host on a AMD Magny-Cours or with -cpu phenom,model=9 on every AMD box with 2.6.31-21-server_2.6.31-21.59. After having applied the mentioned patch (from 2.6.32.12: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=787814b206766e5a6f21aa2aac0c6685b46821d3) the new kernel boots fine with both settings. So please apply this patch. If you move to 2.6.32.12, plese get back to me, as that release contains at least one similar bug. -- kernel crash under KVM when on AMD Magny-Cours https://bugs.launchpad.net/bugs/556480 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
[Bug 556480] Re: kernel crash under KVM when on AMD Magny-Cours
OK, I found the binary .debs myself on the page with the source packages.
I tested linux-image-2.6.32-22-{generic,server,virtual}_2.6.32-22.33_amd64.deb,
all three were crashing.
linux-image-2.6.31-21-server_2.6.31-21.59_amd64.deb from karmic in contrast is
working fine.
>From earlier tests I know that anything starting from 2.6.33-rc1 is also OK.
Will do the source build after having got some sleep
--
kernel crash under KVM when on AMD Magny-Cours
https://bugs.launchpad.net/bugs/556480
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
[Bug 556480] Re: kernel crash under KVM when on AMD Magny-Cours
I tested the kernel from the netinst mini.iso. It is still affected. How to reproduce: 1. Install KVM (userspace tools) 2. load KVM kernel modules (modprobe kvm-amd or kvm-intel) 3. Lauch KVM with a kernel: $ kvm -kernel /boot/vmlinuz -append "console=ttyS0,115200n8" -m 1G -cpu phenom,model=9 -serial stdio This should give you the kernel boot output directly on your terminal. Working kernels will crash while looking for their root device, this is OK (since there is none). Failing kernels will panic earlier with the above crash dump. Another option is to boot the ISOs directly: $ kvm -cdrom mini.iso -cpu phenom,model=9 This will currently crash with the latest netinst .iso, model=8 will work. Please note that model=8 is not a possbile workaround, since -cpu host will imply model=9 on an AMD Magny-Cours machine. The bug fix is already in mainline 2.6.32.12, although I believe this release has introduced another bug :-( Jeremy, is there a binary kernel .deb I can test? I will build a kernel from source as soon as possible and will confirm if the proposed fix solves the issue. -- kernel crash under KVM when on AMD Magny-Cours https://bugs.launchpad.net/bugs/556480 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
Re: [Bug 556480] Re: kernel crash under KVM when on AMD Magny-Cours
Jeremy Foshee wrote: Jeremy, Thanks for following up on this. > Please be sure to confirm this issue exists with the latest development > release of Ubuntu. > ISO CD images are available from http://cdimage.ubuntu.com/releases/. Can you provide me the latest Linux kernel binary (the vmlinuz-... file from /boot)? The kernel crashed very early, so that is all I need to confirm this. I don't want to download a whole DVD image just for a few MBs. Or can you point me to a place where I can download the latest .deb package for the kernel? This would also help. > If the issue remains, please run the following command from a Terminal > (Applications->Accessories->Terminal). It will automatically gather > and attach updated debug information to this report. > > apport-collect -p linux 556480 Beside the fact that I don't have an Ubuntu installation handy here, this would not help much because the kernel crashes very early, before even initrd is started. So I cannot get to the commandline. But I can copy you the crash dump output (although I already know what the problem is and also know the fix). If you need more info, feel free to contact me again. Regards, Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 488-3567-12 to satisfy European Law for business letters: Advanced Micro Devices GmbH Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 -- kernel crash under KVM when on AMD Magny-Cours https://bugs.launchpad.net/bugs/556480 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
[Bug 556480] Re: kernel crash under KVM when on AMD Magny-Cours
Frank, good observation, that should be the same thing in Xen. Here it is even worse, as by default Xen always injects the host's CPUID into the guest, so it will trigger every time you start it as a Xen guest (on every Xen host OS) The bad part of it is that you can hardly patch the guest's kernel in an ISO image to workaround this and online updates are not possible because the kernel crashes so early. I think that seriously affects Ubuntu's experience: It cannot be used as a guest on AMD Magny-Cours systems. So please seriously consider the mentioned fix (which is already queued for 2.6.32.x)! Thanks! -- kernel crash under KVM when on AMD Magny-Cours https://bugs.launchpad.net/bugs/556480 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
[Bug 556480] Re: kernel crash under KVM when on AMD Magny-Cours
GregKH has just commited the original 2.6.33 patch to the stable 2.6.32.x tree: http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=blob;f=queue-2.6.32/x86-amd-get-multi-node-cpu-info-from-nodeid-msr-instead-of-pci-config-space.patch;h=f0fed9e496ac136c6ed220bf8ac93a620aa81a34;hb=9659d8acdb341eeb9fe74837b05c60c0dd5ff6ee So please pick it up from there -- kernel crash under KVM when on AMD Magny-Cours https://bugs.launchpad.net/bugs/556480 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
[Bug 556480] [NEW] kernel crash under KVM when on AMD Magny-Cours
Public bug reported: When using Ubuntu Lucid as a KVM guest and either a) propagating the host CPU to the guest (-cpu host) on an AMD Opteron 61xx processor (Magny-Cours) or b) forcing the guest CPU to be a Magny-Cours (-cpu qemu64,family=16,model=9,vendor=AuthenticAMD) the guest kernel crashes early with a panic related to a division error: -- [0.074409] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [0.075503] CPU: L2 Cache: 512K (64 bytes/line) [0.076227] divide error: [#1] SMP [0.076870] last sysfs file: [0.077332] CPU 0 [0.077673] Modules linked in: [0.078169] Pid: 0, comm: swapper Not tainted 2.6.32-16-generic #25-Ubuntu Bochs [0.079284] RIP: 0010:[] [] init_amd+0x29c/0x3bd [0.08] RSP: 0018:817adea8 EFLAGS: 00010246 [0.08] RAX: RBX: 8185b380 RCX: 880001c0 [0.08] RDX: RSI: RDI: [0.08] RBP: 817adef8 R08: R09: 0001 [0.08] R10: 0004 R11: R12: 8185b394 [0.08] R13: R14: R15: 00013800 [0.08] FS: () GS:880001c0() knlGS: [0.08] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [0.08] CR2: CR3: 01001000 CR4: 06b0 [0.08] DR0: DR1: DR2: [0.08] DR3: DR6: 0ff0 DR7: 0400 [0.08] Process swapper (pid: 0, threadinfo 817ac000, task 817d4600) [0.08] Stack: [0.08] 817adfa8 00013800 817adef8 8154e1d9 [0.08] <0> 80802001078bfbfd 00100f910800 8185b380 [0.08] <0> 81973000 817adfa8 817adf18 8154e2d4 [0.08] Call Trace: [0.08] [] ? generic_identify+0x12e/0x13e [0.08] [] identify_cpu+0xeb/0x1db [0.08] [] identify_boot_cpu+0x10/0x3e [0.08] [] check_bugs+0x9/0x2d [0.08] [] start_kernel+0x348/0x365 [0.08] [] x86_64_start_reservations+0x125/0x129 [0.08] [] x86_64_start_kernel+0xfa/0x109 [0.08] Code: 8b b3 b2 00 00 00 4d 63 f6 0f b6 d2 4a 8b 0c f5 00 b7 85 81 48 c7 c0 f4 e3 00 00 8d 14 72 66 89 14 08 0f b7 83 b4 00 00 00 31 d2 <41> f7 f5 66 89 93 b4 00 00 00 48 89 df e8 13 fc ff ff 81 7b 0c [0.08] RIP [] init_amd+0x29c/0x3bd [0.08] RSP [0.080017] ---[ end trace a7919e7f17c0a725 ]--- This is caused by an unchecked PCI config space access in arch/x86/kernel/cpu/amd.c:amd_fixup_dcm(), which is only called when a family 10h model 9 processor (aka Magny-Cours) is detected. Since KVM does not provide an emulation of the AMD Northbridge PCI device, the resulting values are bogus and trigger a division by zero error. The upstream patch: commit 9d260ebc09a0ad6b5c73e17676df42c7bc75ff64 Author: Andreas Herrmann Date: Wed Dec 16 15:43:55 2009 +0100 removes this PCI access and replaces it with the more virtualization friendly MSR access to get the same information. -cpu host will become the new default for KVM, so please seriously consider back-porting this patch (which simplifies the code) and is upstream since 2.6.33-rc1 If not back-ported, KVM guests with Ubuntu Lucid will not run on AMD Magny-Cours machines in the future. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- kernel crash under KVM when on AMD Magny-Cours https://bugs.launchpad.net/bugs/556480 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
