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/180
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
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
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
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/
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:
ar
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
Ti
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:
arm6
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
245715cb
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),
> 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)
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
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
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
CONFI
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 a
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 e
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
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
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 kno
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 -ser
ree 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
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 kern
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=965
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
24 matches
Mail list logo
