** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
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/1647793
Title:
Yakkety: arm64: CONFIG_ARM64_ERRATUM_8
** Description changed:
-
- CONFIG_ARM64_ERRATUM_845719 should be enabled in Yakkety, but it isn't.
+ CONFIG_ARM64_ERRATUM_845719 should have been enabled in Yakkety, but
+ it isn't actually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
CONFIG_ARM64_ERRATUM_845719 should be enabled in Yakkety, but it isn't.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
On Thu, Nov 3, 2016 at 5:42 AM, Kamal Mostafa wrote:
> Ming Lei comment #2 says you're the author of this patch to the hio
> driver:
>
> +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
> + blk_queue_split(q, &bio, q->bio_split);
> +#endif
> +
On Tue, May 17, 2016 at 12:12 PM, Ming Lei wrote:
> On Mon, May 16, 2016 at 5:25 PM, Ming Lei wrote:
>> On Fri, May 13, 2016 at 7:22 AM, dann frazier
>> wrote:
>>> I used ftrace to do some duration measuring of the timer function
>>> fb_flashcursor(). I notice
On Mon, May 16, 2016 at 5:25 PM, Ming Lei wrote:
> On Fri, May 13, 2016 at 7:22 AM, dann frazier
> wrote:
>> I used ftrace to do some duration measuring of the timer function
>> fb_flashcursor(). I noticed several places where this timer takes around
>> 98 ms to complet
On Fri, May 13, 2016 at 7:22 AM, dann frazier
wrote:
> I used ftrace to do some duration measuring of the timer function
> fb_flashcursor(). I noticed several places where this timer takes around
> 98 ms to complete. This time seems to be due to multiple calls to
> __memcpy_toio() in ast_dirty_upd
On Tue, May 3, 2016 at 1:14 PM, Radha Mohan Chintakuntla
wrote:
> Ming,
> The "-I" option of tcpdump is monitoring mode typically applicable only to
> wifi interfaces. So even if you run it on Thunder's NIC interfaces it will
> return saying that this is not supported.
>
Even without the '-I',
On Tue, May 3, 2016 at 10:35 AM, dann frazier
wrote:
> On Fri, Apr 29, 2016 at 2:06 AM, Ming Lei <1574...@bugs.launchpad.net> wrote:
>> It can be triggered 100% by running 'tcpdump -I ethX'.
>
> Thanks Ming. I let that run for a few hours, but was unable to
>
It can be triggered 100% by running 'tcpdump -I ethX'.
--
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/1574814
Title:
ThunderX: soft lockup in cursor_timer_handler() Edit
Status in linux
On Thu, Apr 28, 2016 at 9:55 PM, Tim Gardner wrote:
> Ming - please try the kernel at
> http://people.canonical.com/~rtg/lp1575506/ - I've updated AUFS to the
> latest stable branch. Source at git://kernel.ubuntu.com/rtg/ubuntu-
> xenial.git aufs
Looks no difference by installing the new kernel o
On Wed, Apr 27, 2016 at 4:31 PM, Ming Lei <1575...@bugs.launchpad.net> wrote:
> Upstream 4.6-rc6 hasn't this problem
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1575506
>
> Title:
Upstream 4.6-rc6 hasn't this problem
--
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/1575506
Title:
Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
virtual address 00
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1575506
Title:
Xenial: ARM64: Unable to handle kernel NULL pointer der
The issue can be reproduced on '4.4.0-22-generic #38' too
--
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/1575506
Title:
Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
Public bug reported:
When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following
kernel oops is triggered.
[ 93.309158] Unable to handle kernel NULL pointer dereference at virtual
address 0038
[ 93.309160] pgd = 8007a5914000
[ 93.309163] [0038] *pgd=0047a5
Finally figured out that the 'msi_irqs' directory can't show once the tg3
interface is down.
When I make it up manually, the directory can appear.
So looks an invalide report.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Invalid
--
You received this bug notification becaus
Public bug reported:
When I test xenial kernel about PCI function on one ARM64 box, I see
the PCI device does work, and this device is shown with MSI capability.
But the msi_irqs directory can't be found under:
./platform/soc/1f2b.pcie/pci:00/:00:00.0/:01:00.0/
When I trace the
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1548207
Title:
xenial 4.4.0-7-generic: kernel oops during load module
*** This bug is a duplicate of bug 1547718 ***
https://bugs.launchpad.net/bugs/1547718
** This bug has been marked a duplicate of bug 1547718
4.4.0-7.22 no longer boots on arm64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Public bug reported:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
L3c Cache: 8MB
[0.587986] kernel BUG at /build/linux-RKt9qy/linux-4.4.0/mm/memory.c:1887!
[0.594918] Internal error: Oop
On Mon, Feb 22, 2016 at 4:37 PM, Ming Lei wrote:
> Looks it is enough to just revert
> 'e96e20134729121689a0089537c6ed(module: clean up RO/NX handling)'
> for fixing the issue.
>
> But the interesting thing is that there isn't the problem in upstream kernel
> 4.5-
Looks it is enough to just revert
'e96e20134729121689a0089537c6ed(module: clean up RO/NX handling)'
for fixing the issue.
But the interesting thing is that there isn't the problem in upstream kernel
4.5-rc5, and the commit(module: clean up RO/NX handling) isn't reverted
in upstream yet.
So looks
When this commit c8d73ebfe19daac81b7cb5c8d1dd(module: clean up RO/NX handling)
is reverted, the issue disappeares.
So the above commit should be the cause.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Dann,
In my test, the issue is nothing to do with kernel, and only related
with modules built by the affected gcc 5.3.
For example, the kernel running is built from gcc 5.2, then I rebuilt some
modules by gcc 5.3, the issue comes
when I try to load the just built module.
BTW, '-mcmodel=large' i
On Fri, Jan 15, 2016 at 6:29 PM, Matthias Klose wrote:
> please attach the preprocessed source and the exact command line options
> to build the libahci module.
Not only libahci modules, all built modules has the problem.
Follows the command line for building libahci.ko:
1) apt-get source linux
Looks the latest proposed gcc-5.3.1-6ubuntu1 has the problem too.
--
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/1533009
Title:
arm64: "unsupported RELA relocation"
Status in gcc-5 pac
Hi,
Wrt. the build environment, the built kernel/modules can work fine just after
switching gcc from gcc-5 to gcc-4.9 and keep other things not changed
in Xenial.
So I am sure the issue is in Xenial gcc-5, and the bug should be introduced
after 5.2.1-22ubuntu2 because Wily gcc-5 hasn't this probl
0108 (Ubuntu/Linaro 5.3.1-5ubuntu2)
On Wed, Jan 13, 2016 at 9:11 AM, Ming Lei wrote:
> When I built 4.3.0-7-generic on arm64(mustang) Wily with the following steps,
>
> fakeroot debian/rules clean
> fakeroot debian/rules binary-generic
>
> by this compiler:
&
When I built 4.3.0-7-generic on arm64(mustang) Wily with the following
steps,
fakeroot debian/rules clean
fakeroot debian/rules binary-generic
by this compiler:
ubuntu@ubuntu:~$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/5/lt
Looks there isn't crash during the ifconfig up/down test any more after applying
the patch in the following link, but ifconfig still may hang during the test:
https://www.mail-archive.com/netdev@vger.kernel.org/msg88060.html
See test log in the attachment.
** Attachment added: "ifconfig hangs d
On Tue, Oct 27, 2015 at 11:03 PM, Fathi Boudra wrote:
> Ming Lei,
>
> yes, on Mustang. We're using U-Boot.
OK, we found the issue is triggered during booting, and finally
APM's fix on firmware can make the issue disappeared, but
it isn't released yet.
>
> --
> Y
The issue can be fixed by disabling 'ARM64_DT_NUMA', so it is definitley caused
by the following commit:
commit ecbd5d083f9d668436cd0cc18f06094233c1c336
Author: Ganapatrao Kulkarni
Date: Fri Sep 18 15:44:40 2015 -0600
UBUNTU: SAUCE: arm64, numa, dt: adding dt based numa support using
dt n
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1509221
Title:
wily: arm64: warning in numa_init() during booting
Sta
Riku,
Did you reproduce the issue with UEFI booting or U-boot booting? And it
is on Mustang?
Thanks,
--
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/1440536
Title:
Oops __d_lookup+0x88/
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1509221
Title:
wily: arm64: warning in numa_init() during booting
Status in
Public bug reported:
[0.00] [ cut here ]
[0.00] WARNING: CPU: 0 PID: 0 at
/build/linux-vmnY7Y/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-16-gener
Public bug reported:
1, Wily kernel crashed with attached log on APM mustang(ARM64)
2, how to reproduce
2.1 start iperf first
- run 'iperf -s' on mustang board
- run 'iperf -c IP_OF_MUSTANG' on another machine, and make the client point to
mustang
2.2 run the following 'ifconfig eth0 up/down' t
On Tue, Sep 1, 2015 at 11:27 PM, dann frazier
wrote:
> Sorry, I missed the request for more information. I retested yesterday,
> and it is still possible to crash the system with the above stress-ng
> command 4.2.0-6.6 from ppa:canonical-kernel-team/ppa. In fact, it seems
> to be 100% reproducible
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
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/1473818
Title:
vivid kernel can't boot on APM xgene2 Soc
vivid kernel can't support ACPI on arm64, so marked it as invalid
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Public bug reported:
Turns out the following commits are required:
c2d33bd drivers: net: xgene: Check for IS_ERR rather than NULL for clock.
822e34a drivers: net: xgene: Add ACPI support for SGMII0 and XFI1 interface of
2nd H/W version
2c7be0a drivers: net: xgene: Implement the backward compati
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1474171
Title:
Wily boot failure on HP proliant m400 server
Status in
Finally, I figured out it is the following patchset which can fix the issue.
That is said
the issue disappears if these patches are applied to v4.0 kernel:
9a6d729 of: Calculate device DMA masks based on DT dma-range size
22b3c18 arm: dma-mapping: limit IOMMU mapping size
de335bb4 PCI: Update DMA
** Package changed: irqbalance (Ubuntu) => linux (Ubuntu)
--
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/1474171
Title:
Wily boot failure on HP proliant m400 server
Status in linux pack
Public bug reported:
Starting kernel ...
L3C: 8MB
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 3.19.8-ckt3+ (ming@r815) (gcc version 4.8.2 20140110 (prerelease)
[ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision 205847] (Ubuntu/Linaro
4.8.2-13ubuntu1) ) #
ubuntu@ms10-40-mcdivittA3:~$ uname -a
Linux ms10-40-mcdivittA3 3.16.0-44-generic #59-Ubuntu SMP Tue Jul 7 02:18:58
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ms10-40-mcdivittA3:~$
ubuntu@ms10-40-mcdivittA3:~$
ubuntu@ms10-40-mcdivittA3:~$
ubuntu@ms10-40-mcdivittA3:~$ iperf -c 10.229.0.101
ubuntu@am2:~$ iperf -c 10.228.0.2 -P 8 -t 120
Client connecting to 10.228.0.2, TCP port 5001
TCP window size: 85.0 KByte (default)
[ 10] local 10.228.66.98 port 59722 connected
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.19.0-23-generic #24-Ubuntu SMP Tue Jul 7 18:58:44 UTC 2015
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ubuntu:~$ sudo ethtool eth2
sudo: unable to resolve host ubuntu
Settings for eth2:
Supported ports: [ MII ]
Supported link modes: 1000baseT
** Changed in: irqbalance (Ubuntu Vivid)
Status: In Progress => Confirmed
--
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/1469214
Title:
HP ProLiant m400 Server crashes with unhand
On Tue, Jul 7, 2015 at 11:16 AM, Ming Lei wrote:
> Looks there are two kinds of translation fault from irqbalance:
>
> 1) happend in place_irq_in_node() which can reproduce in vivid package
>
> 2) the 2nd one happened in glib2, which is built by myself, because
> irqbalance can
Looks there are two kinds of translation fault from irqbalance:
1) happend in place_irq_in_node() which can reproduce in vivid package
2) the 2nd one happened in glib2, which is built by myself, because
irqbalance can choose to use its own local glib if there isn't glib2 available,
and the glib2
On Tue, Jul 7, 2015 at 2:37 AM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> captured irqbalance segfaulting:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00408f8c in place_irq_in_node (info=0x2c3d0050, data=0x0) at
> placement.c:145
> 145 if (irq_numa_n
On Mon, Jul 6, 2015 at 9:28 PM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> I re-ran this today with the following script as a non-root user:
>
> #!/bin/bash
> tests="affinity aio bigheap brk bsearch cache chdir chmod clock context cpu
> crypt dentry dir dup epoll eventfd fstat fallocate
Hi Colin,
On Sat, Jul 4, 2015 at 12:43 AM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> I was able to hit the following translation fault running sudo ./stress-
> ng --seq 0 -t 60 --syslog --metrics --times -v
I suggest to not run stress-ng as root, otherwise it can be less
serious becaus
Hi Colin,
That looks one progress, but still takes time to reproduce that,
and I will use your new approach to reproduce that.
When you are doing that, could you dump the file of /proc/$(pidof
irqbalance)/maps so that we can see where the faulted address are
in the process's vm space?
thanks,
This one looks a problem of systemd-timesyncd, from pmap log[1],
both the PC and faulted address aren't valid, which drop in heap area,
but the faulted address(0x7fa8ea6008) shouldn't have been allocated
and is far away from the start address(0x7f9eb27000) of hear area.
[1] pmap log
ubuntu@ms10
The night before yesterday, I have run stress-ng for one night, looks it isn't
crashed on
mcdivitt.
Yesterday, I found my system is upgraded from trysty to vivid directly and the
'systemd'
package isn't installed, then 'systemd-timesyn' can't be found, so I install
the package
and make sure sys
Some static code analysis:
1), looks not possbile in scsi request submit path
- preempt is disabled for arm64 vivid
- the timer is always added just before submitting to hardware
- once it can't be submitted to hardware, the timer is disabled
2), another possibility is in ata's completion path
-
Wrt. disk read failure in Colin's report, looks the sectors themselves invoved
in timeout are good, becasue the following
test runs well in ms10-34 now:
sudo dd if=/dev/sda skip=9741420 iflag=direct of=/dev/null bs=512
count=1K
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copie
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
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/1469859
Title:
HP ProLiant m400: NULL pointer dereference PC is at
ctx
Given 'stress-ng --all 64' is quite heavy and system-wide stress, and
thousands of tasks are created for
running lots of stress concurrently which may touch most areas of kernel, the
triggered issue is quite difficult
to reproduce, so please add the detailed log information for further
invesit
BTW, about the sata read timeout issue, I have run fio to verify sata disk
read/randread/write/randwrite, and looks
it works fine
--
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/1469218
Ti
For #5's log, the fault happened in the following code snippet of
kernel/sched/cputime.c:
for_each_thread(tsk, t) {
ffcd3dc0: f9445760ldr x0, [x27,#2216]
ffcd3dc4: f8410c03ldr x3, [x0,#16]!
ffcd3dc8: f90037a3
But another kernel oops is just found on one mustang with vivid:
Call trace:
Unable to handle kernel NULL pointer dereference at virtual address 0018
pgd = ffc105652000
[0018] *pgd=00432d9dc003Unable to handle kernel NULL pointer
dereference at virtual address 0030
pgd = f
BTW, it can't be reproduced on mustang when running vivid too.
--
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/1469218
Title:
HP ProLiant m400 Server sda timeout causes file system hang
I can't reproduce it after running half a day on ms10-36, and OOM is
often triggered .
--
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/1469218
Title:
HP ProLiant m400 Server sda timeout c
Oops, the test result in #4 is for LP1469218 instead of this one.
--
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/1469214
Title:
HP ProLiant m400 Server crashes with unhandled level 3 tra
I can't reproduce it after running half a day on ms10-36, and OOM is often
triggered .
--
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/1469214
Title:
HP ProLiant m400 Server crashes with
Turns out the firmware on this server is a bit old(U-Boot 2013.04 (Oct 01 2014
- 15:18:17)), and the problem
doesn't exit on another server which firmware is U-Boot 2013.04 (Mar 26 2015 -
11:31:01).
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug not
Public bug reported:
1, upgrade to vivid from trysty
2, boot the server, then the following log in [1] can be observed
[1] kernel booting log
Starting kernel ...
L3C: 8MB
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializ
ubuntu@am6:~$ uname -a
Linux am6 3.16.0-43-generic #58-Ubuntu SMP Fri Jun 19 11:04:11 UTC 2015 aarch64
aarch64 aarch64 GNU/Linux
ubuntu@am6:~$ sudo ethtool eth2
Settings for eth2:
Supported ports: [ MII ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
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/1458042
Title:
[SRU] xgene-enet: add SGMII based 1GbE s
Verification on utopic:
ubuntu@am6:~$ sudo crash vmlinux
[sudo] password for ubuntu:
crash 7.0.8
Copyright (C) 2002-2014 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyrigh
verification on vivid:
ubuntu@ubuntu:~/test$ sudo dpkg -l crash
sudo: unable to resolve host ubuntu
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Verification on trusty:
ubuntu@am2:~$ sudo crash vmlinux
[sudo] password for ubuntu:
crash 7.0.3
Copyright (C) 2002-2013 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyrigh
ubuntu@am2:~$ sudo crash vmlinux
[sudo] password for ubuntu:
crash 7.0.3
Copyright (C) 2002-2013 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linu
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Ming Lei (tom-leiming)
--
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/1458042
Title:
[SRU] xgene-enet: add SGMII ba
Public bug reported:
On trusty, some BT commands are missed for ARM64.
[Impact]
some BT commands aren't usable, such as bt -e, bt -l, ...
[Test Case]
- start crash
- run bt -e
crash> bt -e
PID: 2113 TASK: ffc3e3446180 CPU: 5 COMMAND: "crash"
bt: arm64_eframe_search: function not implem
** Description changed:
+ [Impact]
- [Impact]
-
- crash can't be used on ubuntu trusty, utopic and vivid
+ crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
+ debugging a new kernel like 4.1-rc+
[Test Case]
sudo crash ~/vmlinux
+ crash will exit with failure log o
And the patches in below links can fix the above crashs(#14, #15)
http://kernel.ubuntu.com/git/ming/ubuntu-trusty.git/commit/?h=apm-enet-
fix&id=a19b2c0bdd12e59a482717664312b18407284ee5
http://kernel.ubuntu.com/git/ming/ubuntu-utopic.git/commit/?h=arm64-net-
backport&id=d46456e3ed9153e743f2add6e0
** Attachment added: "crash log in utopic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416914/+files/dmesg-utopic.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Finally I figured out one approach to reproduce it quickly, see the
attachment log.
** Attachment added: "crash log in trusty"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416913/+files/dmesg-trusty.log
--
You received this bug notification because you are a mem
>From the original report, the issue happened since 3.17, so close it on trysty
>because we can't reproduce it
on trusty too.
I've seen this with mainline since somewhere in v3.17 and on several
hardware boards stress testing KVM by running workloads in VMs.
** Changed in: lin
** Description changed:
+
+ [Impact]
+
+ crash can't be used on ubuntu trusty, utopic and vivid
+
+ [Test Case]
+
+ sudo crash ~/vmlinux
+
+ [Regression Potential]
+
+ The proposed patch has been merged upstream, so there shouldn't be
+ potential regression
+
+ [Other Info]
+
+
Whe
** Description changed:
+
+ [Impact]
+
+ crash can't be used on ubuntu trusty, utopic and vivid
+
+ [Test Case]
+
+ sudo crash ~/vmlinux
+
+ [Regression Potential]
+
+ The proposed patch has been merged upstream, so there shouldn't be
+ potential regression
+
+ [Other Info]
+
+
Aft
*** This bug is a duplicate of bug 1440536 ***
https://bugs.launchpad.net/bugs/1440536
** This bug has been marked a duplicate of bug 1440536
Oops __d_lookup+0x88/0x194
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
>From dann's reports:
1) system1
Code: 1412 f9400273 b4000213 d1002274 (b9402280)
2) system2
Code: 1412 f9400273 b4000213 d1002274 (b9402280)
And the upstem report in #15,
Code: 1403 f9400273 b4000213 d1002274 (b9402282)
The code snippet should be the following in __d_lookup(): fs/d
BTW, looks it isn't related with specific filesystem, and from the recent
triger, it happened when
walking path inside proc filesystem:
[24993.562923] Call trace:
[24993.565357] [] __d_lookup+0x88/0x194
[24993.570467] [] d_lookup+0x38/0x64
[24993.575319] [] d_hash_and_lookup+0x54/0x6c
[24993.5809
Looks there was similar report from upstream:
http://marc.info/?l=linux-fsdevel&m=142865378923064&w=2
but still don't have resolution or further report.
Also I tried to use fbench to create lots of files, list dirs concurently for
reproducing
the issue, but can't reproduce it yet.
--
You rec
** Attachment added: "dmesg log of 'poweroff'"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4411589/+files/dmesg.log
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member
The problem can be fixed by applying the following commit:
commit db07dbf5a7e19806b1629bd4125e6643978c6f9f
Author: Dave Anderson
Date: Thu Feb 19 16:16:33 2015 -0500
Prepare for the future increment of Linux 3.x to 4.x.
(ander...@redhat.com)
--
You received this bug notification beca
Public bug reported:
When I build crash from wily, the failure in [1] can be
triggered if the kernel is 4.0+.
[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
crash 7.0.8
Copyright (C) 2002-2014 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright
Public bug reported:
After running crash from trusty, the failure log in [1] can be observed.
Then I built crash from wily directly, the similar failure[2] can be
observed too.
[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux
crash 7.0.3
Copyright (C) 2002-2013 Red Hat, Inc
The issue can be fixed by the following upstream commit:
commit 7623eee9046015b65a1f63f6bf07ab7805c36eb4
Author: Dave Anderson
Date: Tue May 19 10:20:04 2015 -0400
Fix for the ARM64 page size determination on Linux 4.1 and later
kernels. Without the patch, the crash session fails duri
** Tags removed: verification-needed-trusty
** Tags added: verification-done-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/1438585
Title:
no console when starting VM from cloud
[tom@vm-test]$vim arm64-qemu
[tom@vm-test]$./arm64-qemu
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.13.11-ckt20+ (tom@tom-T450) (gcc version 4.8.2
20140110 (prerelease) [ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision
205847] (Ubuntu/Linaro 4.8.2-13ubuntu1
[1] kvm psci v0.2 patchset
http://comments.gmane.org/gmane.linux.ubuntu.devel.kernel.general/56676
** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current
arm64 VM with the kvm psci v0.2 patchset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachmen
** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current
arm64 VM"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4400723/+files/dmesg-before-applying-patches.log
--
You received this bug notification because you are a member of Kernel
Packages
** Tags added: kernel-fixed-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/1455372
Title:
Trausty arm64 VM doesn't support 'reboot' and 'powerdown'
Status in linux package in U
1 - 100 of 151 matches
Mail list logo
