from:"Ming Lei"

[Bug 1647793] Re: Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

2017-01-04 Thread Ming Lei

** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647793

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647793/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647793] Re: Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

2016-12-06 Thread Ming Lei

** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647793

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647793/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647793] [NEW] Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

2016-12-06 Thread Ming Lei

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647793

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647793/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1638700] Re: hio: SSD data corruption under stress test

2016-11-02 Thread Ming Lei

On Thu, Nov 3, 2016 at 5:42 AM, Kamal Mostafa <ka...@canonical.com> 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, , q->bio_split);
> +#endif
> +
>
> Can you provide us with a short explanation for the git log, and also
> your Signed-off-by line for that patch?

Sure, please see the attachment.

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1638700
>
> Title:
>   hio: SSD data corruption under stress test
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Xenial:
>   In Progress
> Status in linux source package in Yakkety:
>   In Progress
> Status in linux source package in Zesty:
>   In Progress
>
> Bug description:
>   {forward from James Troup}:
>
>   Just to followup to this with a little more information, we have now
>   reproduced this in the following scenarios:
>
>* Ubuntu kernel 4.4 (i.e. 16.04) and kernel 4.8 (i.e. HWE-Y)
>* With and without Bcache involved
>* With both XFS and ext4
>* With HIO driver versions 2.1.0-23 and 2.1.0-25
>* With HIO Firmware 640 and 650
>* With and without the following two patches
> - 
> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=7290fa97b945c288d8dd8eb8f284b98cb495b35b
> - 
> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=901a3142db778ddb9ed6a9000ce8e5b0f66c48ba
>
>   In all cases, we applied the following two patches in order to get hio
>   to build at all with a 4.4 or later kernel:
>
> 
> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=0abbb90372847caeeedeaa9db0f21e05ad8e9c74
> 
> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=a0705c5ff3d12fc31f18f5d3c8589eaaed1aa577
>
>   We've confirmed that we can reproduce the corruption on any machine in
>   Tele2's Vienna facility.
>
>   We've confirmed that, other than 1 machine, the 'hio_info' command
>   says the health is 'OK'.
>
>   Our most common reproducer is one of two scenarios:
>
>a) http://paste.ubuntu.com/23405150/
>
>b) http://paste.ubuntu.com/23405234/
>
>   In the last example, it's possible to see corruption faster by
>   increasing the 'count' argument to dd and avoid it by lowering it.
>   e.g. on the machine I'm currently testing on count=52450 doesn't
>   appear to show corruption, but a count of even 53000 would show it
>   immediately every time.
>
>   I hope this helps - please let us know what further information we can
>   provide to debug this problem.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638700/+subscriptions


** Patch added: 
"0001-hio.c-splitting-bio-in-the-entry-of-.make_request_fn.patch"
   
https://bugs.launchpad.net/bugs/1638700/+attachment/4771506/+files/0001-hio.c-splitting-bio-in-the-entry-of-.make_request_fn.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638700

Title:
  hio: SSD data corruption under stress test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638700/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1592074] Re: ubuntu-core is change in progress after interrupt "snap install"

2016-08-31 Thread Ming Lei

With Shuduo's help, looks the only solution for this issue is to run reset-state
by the tools in the following link:

https://github.com/zyga/devtools/blob/master/reset-state

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592074

Title:
  ubuntu-core is change in progress after interrupt "snap install"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1592074/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1612020] Re: arm64: virt machine: no virtio devices emulated

2016-08-10 Thread Ming Lei

Just found that it is caused by missing one '\'

** Changed in: qemu (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612020

Title:
  arm64: virt machine: no virtio devices emulated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1612020/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1612020] [NEW] arm64: virt machine: no virtio devices emulated

2016-08-10 Thread Ming Lei

Public bug reported:

1, script

QEMU=qemu-system-aarch64

$QEMU \
-enable-kvm \
-m 4096 \
-smp 4 \
-cpu host \
-M virt,gic-version=host \
-vga none  \
-nographic \
-kernel $1 \
-initrd $2 \
-append "earlycon=pl011,0x900 console=ttyAMA0 root=/dev/vda2"
-drive if=none,file=$3,id=hd0,format=raw \
-device virtio-blk-pci,drive=hd0 \
-netdev type=user,id=net0 \
-device virtio-net-pci,netdev=net0,mac=00:12:34:56:78:89

2, result:

no any virtio devices(blk, net,,,) found by guest kernel

ubuntu@merlin1:~/kvm$ sudo ./start2 ./vmlinuz ./initrd ./dd.img 
[sudo] password for ubuntu: 
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.0-34-generic (buildd@bos01-arm64-016) (gcc 
version 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed 
Jul 27 16:07:06 UTC 2016 (Ubuntu 4.4.0-34.53-generic 4.4.15)
[0.00] Boot CPU: AArch64 Processor [501f]
[0.00] earlycon: Early serial console at MMIO 0x900 (options '')
[0.00] bootconsole [uart0] enabled
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x00013fff]
[0.00] NUMA: Adding memblock [0x4000 - 0x13fff] on node 0
[0.00] NUMA: Initmem setup node 0 [mem 0x4000-0x13fff]
[0.00] NUMA: NODE_DATA [mem 0x13fff2280-0x13fff3fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x00013fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x4000-0x00013fff]
[0.00] Initmem setup node 0 [mem 0x4000-0x00013fff]
[0.00] psci: probing for conduit method from DT.
[0.00] psci: PSCIv0.2 detected in firmware.
[0.00] psci: Using standard PSCI v0.2 function IDs
[0.00] psci: Trusted OS migration not required
[0.00] PERCPU: Embedded 17 pages/cpu @8000fff8d000 s31128 r8192 
d30312 u69632
[0.00] Detected PIPT I-cache on CPU0
[0.00] Built 1 zonelists in Node order, mobility grouping on.  Total 
pages: 1032192
[0.00] Policy zone: Normal
[0.00] Kernel command line: earlycon=pl011,0x900 console=ttyAMA0 
root=/dev/vda2
[0.00] log_buf_len individual max cpu contribution: 4096 bytes
[0.00] log_buf_len total cpu_extra contributions: 12288 bytes
[0.00] log_buf_len min size: 16384 bytes
[0.00] log_buf_len: 32768 bytes
[0.00] early log buf free: 13712(83%)
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] software IO TLB [mem 0xfbfff000-0xf000] (64MB) mapped at 
[8000bbfff000-8000bfffefff]
[0.00] Memory: 4013772K/4194304K available (8752K kernel code, 1022K 
rwdata, 3792K rodata, 760K init, 786K bss, 180532K reserved, 0K cma-reserved)
[0.00] Virtual kernel memory layout:
[0.00] vmalloc : 0x - 0x7bffbfff   (126974 
GB)
[0.00] vmemmap : 0x7bffc000 - 0x7fffc000   (  4096 
GB maximum)
[0.00]   0x7bffc000 - 0x7bffc400   (64 
MB actual)
[0.00] fixed   : 0x7a7fd000 - 0x7ac0   (  4108 
KB)
[0.00] PCI I/O : 0x7ae0 - 0x7be0   (16 
MB)
[0.00] modules : 0x7c00 - 0x8000   (64 
MB)
[0.00] memory  : 0x8000 - 0x8001   (  4096 
MB)
[0.00]   .init : 0x80cc2000 - 0x80d8   (   760 
KB)
[0.00]   .text : 0x8008 - 0x80cc2000   ( 12552 
KB)
[0.00]   .data : 0x80d91000 - 0x80e90a00   (  1023 
KB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 64.
[0.00]  RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[0.00] NR_IRQS:64 nr_irqs:64 0
[0.00] GICv2m: range[0x802:0x8020fff], SPI[80:144]
[0.00] Architected cp15 timer(s) running at 50.00MHz (virt).
[0.00] clocksource: arch_sys_counter: mask: 0xff 
max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns
[0.02] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 
4398046511100ns
[0.001882] Console: colour dummy device 80x25
[0.002787] Calibrating

[Bug 1584602] Re: internal compiler error: in fixup_reorder_chain, , at cfgrtl.c:3336

2016-05-24 Thread Ming Lei

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584602

Title:
  internal compiler error: in fixup_reorder_chain,,  at cfgrtl.c:3336

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1584602/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584602] Re: internal compiler error: in fixup_reorder_chain, , at cfgrtl.c:3336

2016-05-23 Thread Ming Lei

Please see the gcc-4.8 crash log on trusty/arm64, which includes the gcc
flag and PreprocessedSource.


** Attachment added: "gcc-4.8 crash log on trusty/arm64"
   
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1584602/+attachment/4669037/+files/_usr_lib_gcc_aarch64-linux-gnu_4.8_cc1.0.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584602

Title:
  internal compiler error: in fixup_reorder_chain,,  at cfgrtl.c:3336

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1584602/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584602] Re: internal compiler error: in fixup_reorder_chain, , at cfgrtl.c:3336

2016-05-23 Thread Ming Lei

Follos the steps to reproduce the issue:

1, find a arm64 machine or VM, which is installed trusty

2, prepare for building samba:
sudo apt-get -y install dpkg-dev fakeroot
sudo apt-get -y build-dep samba

3, download the following samba source:
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/samba_4.3.9+dfsg.orig.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/samba_4.3.9+dfsg-0ubuntu0.14.04.1.debian.tar.gz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/samba_4.3.9+dfsg-0ubuntu0.14.04.1.dsc

4, start the building:

dpkg-source -x samba_4.3.9+dfsg-0ubunntu0.14.04.1.dsc
cd samba-4.3.9+dfsg
fakeroot debian/rules clean;
CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot debian/rules binary

5, then the gcc crash can be observed

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584602

Title:
  internal compiler error: in fixup_reorder_chain,,  at cfgrtl.c:3336

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1584602/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584602] [NEW] internal compiler error: in fixup_reorder_chain, , at cfgrtl.c:3336

2016-05-23 Thread Ming Lei

Public bug reported:

When building samba package on trusty/arm64 with gcc-4.8, the following
build crash can be observed, and it can be triggered with gcc-4.7 too.


01:07:10 runner /usr/bin/gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -fPIC -D_REENTRANT
-D_POSIX_PTHREAD_SEMANTICS --
DSTATIC_LOCKING_MODULES=NULL -DSTATIC_LOCKING_MODULES_PROTO=extern
void __LOCKINN
G_dummy_module_proto(void) -MD -D_FORTIFY_SOURCE=2 -Idefault/source3
-I../sourcee
3 -Idefault/source3/include -I../source3/include -Idefault/source3/lib
-I../sourr
ce3/lib -Idefault/source4/heimdal/lib/com_err
-I../source4/heimdal/lib/com_err --
Idefault/source4/heimdal/lib/krb5 -I../source4/heimdal/lib/krb5
-Idefault/sourcee
4/heimdal/lib/gssapi -I../source4/heimdal/lib/gssapi
-Idefault/source4/heimdal_bb
uild -I../source4/heimdal_build
-Idefault/bin/default/source4/heimdal/lib/asn1 --
Idefault/source4/heimdal/lib/asn1 -Idefault/include/public
-I../include/public --
Idefault/source4 -I../source4 -Idefault/lib -I../lib
-Idefault/source4/lib -I..//
source4/lib -Idefault/source4/include -I../source4/include
-Idefault/include -I..
./include -Idefault/lib/replace -I../lib/replace -Idefault -I..
-Idefault/librpcc
 -I../librpc -Idefault/libcli/security -I../libcli/security
-Idefault/source3/lii
brpc -I../source3/librpc -Idefault/libcli/util -I../libcli/util
-Idefault/lib/utt
il/charset -I../lib/util/charset -Idefault/dynconfig -I../dynconfig
-Idefault/lii
b/compression -I../lib/compression -Idefault/libcli/nbt
-I../libcli/nbt -Idefaull
t/lib/crypto -I../lib/crypto -I/usr/local/include -D_SAMBA_BUILD_=4
-DHAVE_CONFII
G_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../source3/locking/brlock.c -c
-o default/source3/locking/brlock_92.o
../source3/smbd/notify.c: In function ‘change_notify_create’:
../source3/smbd/notify.c:297:1: internal compiler error: in
fixup_reorder_chain,,
 at cfgrtl.c:3336
../source3/smbd/notify.c: In function ‘change_notify_create’:
../source3/smbd/notify.c:297:1: internal compiler error: in
fixup_reorder_chain,,
 at cfgrtl.c:3336
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- 
- When building samba package on trusty with gcc-4.8, the following build crash 
can be observed,
- and it can be triggered with gcc-4.7 too.
+ When building samba package on trusty/arm64 with gcc-4.8, the following
+ build crash can be observed, and it can be triggered with gcc-4.7 too.
  
  
  01:07:10 runner /usr/bin/gcc -g -O2 -fstack-protector 
--param=ssp-buffer-size=4
  -Wformat -Werror=format-security -fPIC -D_REENTRANT
  -D_POSIX_PTHREAD_SEMANTICS --
  DSTATIC_LOCKING_MODULES=NULL -DSTATIC_LOCKING_MODULES_PROTO=extern
  void __LOCKINN
  G_dummy_module_proto(void) -MD -D_FORTIFY_SOURCE=2 -Idefault/source3
  -I../sourcee
  3 -Idefault/source3/include -I../source3/include -Idefault/source3/lib
  -I../sourr
  ce3/lib -Idefault/source4/heimdal/lib/com_err
  -I../source4/heimdal/lib/com_err --
  Idefault/source4/heimdal/lib/krb5 -I../source4/heimdal/lib/krb5
  -Idefault/sourcee
  4/heimdal/lib/gssapi -I../source4/heimdal/lib/gssapi
  -Idefault/source4/heimdal_bb
  uild -I../source4/heimdal_build
  -Idefault/bin/default/source4/heimdal/lib/asn1 --
  Idefault/source4/heimdal/lib/asn1 -Idefault/include/public
  -I../include/public --
  Idefault/source4 -I../source4 -Idefault/lib -I../lib
  -Idefault/source4/lib -I..//
  source4/lib -Idefault/source4/include -I../source4/include
  -Idefault/include -I..
  ./include -Idefault/lib/replace -I../lib/replace -Idefault -I..
  -Idefault/librpcc
-  -I../librpc -Idefault/libcli/security -I../libcli/security
+  -I../librpc -Idefault/libcli/security -I../libcli/security
  -Idefault/source3/lii
  brpc -I../source3/librpc -Idefault/libcli/util -I../libcli/util
  -Idefault/lib/utt
  il/charset -I../lib/util/charset -Idefault/dynconfig -I../dynconfig
  -Idefault/lii
  b/compression -I../lib/compression -Idefault/libcli/nbt
  -I../libcli/nbt -Idefaull
  t/lib/crypto -I../lib/crypto -I/usr/local/include -D_SAMBA_BUILD_=4
  -DHAVE_CONFII
  G_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../source3/locking/brlock.c 
-c
  -o default/source3/locking/brlock_92.o
  ../source3/smbd/notify.c: In function ‘change_notify_create’:
  ../source3/smbd/notify.c:297:1: internal compiler error: in
  fixup_reorder_chain,,
-  at cfgrtl.c:3336
+  at cfgrtl.c:3336
  ../source3/smbd/notify.c: In function ‘change_notify_create’:
  ../source3/smbd/notify.c:297:1: internal compiler error: in
  fixup_reorder_chain,,
-  at cfgrtl.c:3336
-  }
-  ^
+  at cfgrtl.c:3336
+  }
+  ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584602

Title:
  internal

Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-16 Thread Ming Lei

On Tue, May 17, 2016 at 12:12 PM, Ming Lei <ming@canonical.com> wrote:
> On Mon, May 16, 2016 at 5:25 PM, Ming Lei <ming@canonical.com> wrote:
>> On Fri, May 13, 2016 at 7:22 AM, dann frazier
>> <dann.fraz...@canonical.com> 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_update():
>>>
>>> for (i = y; i <= y2; i++) {
>>> /* assume equal stride for now */
>>> src_offset = dst_offset = i * afbdev->afb.base.pitches[0] + 
>>> (x * bpp);
>>> memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram + 
>>> src_offset, (x2 - x + 1) * bpp);
>>>
>>>
>>> My theory is that this is causing mod_timer() to block on the other CPU, 
>>> resulting in the soft lockup.
>>>
>>> Also - I built a custom d-i using pristine 4.6-rc7, and I am able to
>>> easily reproduce this. I think the next step here is to report this to
>>> upstream.
>>
>> Hi Dann,
>>
>> Andrew asked me to take a look at the issue, and from my tracing,
>> most of times, the cpu 'hangs' in the following line of code:
>>
>> __mod_timer():
>> 
>> out_unlock:
>>  spin_unlock_irqrestore(>lock, flags);
>>
>> If I added two trace points around the above line, most of times only
>> the trace point before the line is dumped, and the one after the line
>> can't dumped.
>
> Looks the above issue is caused by passing 'jiffies' to mod_timer,
> and 'ops->cur_blink_jiffies' is observed as zero in cursor_timer_handler()
> when the issue happened.
>
> The following patch(workaround) can make the issue disappeared:
>
> diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
> index 6e92917..5e880ee 100644
> --- a/drivers/video/console/fbcon.c
> +++ b/drivers/video/console/fbcon.c
> @@ -1095,6 +1095,8 @@ static void fbcon_init(struct vc_data *vc, int init)
> con_copy_unimap(vc, svc);
>
> ops = info->fbcon_par;
> +   if (vc->vc_cur_blink_ms)

oops, it should be 'if (!vc->vc_cur_blink_ms)'

> +   vc->vc_cur_blink_ms = 125;
> ops->cur_blink_jiffies = msecs_to_jiffies(vc->vc_cur_blink_ms);
> p->con_rotate = initial_rotation;
> set_blitting_type(vc, info);
>
> Thanks,
>
>>
>> Thanks,
>>
>>>
>>> --
>>> You received this bug notification because you are subscribed to linux
>>> in Ubuntu.
>>> https://bugs.launchpad.net/bugs/1574814
>>>
>>> Title:
>>>   ThunderX: soft lockup in cursor_timer_handler() Edit
>>>
>>> Status in linux package in Ubuntu:
>>>   Confirmed
>>>
>>> Bug description:
>>>   I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso 
>>> via virtual media:
>>> 
>>> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>>>
>>>   During boot I observed the following lockup on the serial console:
>>>
>>>   [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using 
>>> xhci_hcd
>>>   [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
>>> [swapper/14:0]
>>>   [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
>>> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
>>> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
>>> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>>>   [ 84.922749]
>>>   [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 
>>> 4.4.0-21-generic #37-Ubuntu
>>>   [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>>>   [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
>>> 801f6c9e8000
>>>   [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>>>   [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>>>   [ 84.922778] pc : [] lr : [] pstate: 
>>> 00400145
>>>   [ 84.922781] sp : 801f6c9ebc20
>>>   [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>>>   [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>>>   [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>>>   [ 84.922798] x23: 801f

Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-16 Thread Ming Lei

On Mon, May 16, 2016 at 5:25 PM, Ming Lei <ming@canonical.com> wrote:
> On Fri, May 13, 2016 at 7:22 AM, dann frazier
> <dann.fraz...@canonical.com> 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_update():
>>
>> for (i = y; i <= y2; i++) {
>> /* assume equal stride for now */
>> src_offset = dst_offset = i * afbdev->afb.base.pitches[0] + 
>> (x * bpp);
>> memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram + 
>> src_offset, (x2 - x + 1) * bpp);
>>
>>
>> My theory is that this is causing mod_timer() to block on the other CPU, 
>> resulting in the soft lockup.
>>
>> Also - I built a custom d-i using pristine 4.6-rc7, and I am able to
>> easily reproduce this. I think the next step here is to report this to
>> upstream.
>
> Hi Dann,
>
> Andrew asked me to take a look at the issue, and from my tracing,
> most of times, the cpu 'hangs' in the following line of code:
>
> __mod_timer():
> 
> out_unlock:
>  spin_unlock_irqrestore(>lock, flags);
>
> If I added two trace points around the above line, most of times only
> the trace point before the line is dumped, and the one after the line
> can't dumped.

Looks the above issue is caused by passing 'jiffies' to mod_timer,
and 'ops->cur_blink_jiffies' is observed as zero in cursor_timer_handler()
when the issue happened.

The following patch(workaround) can make the issue disappeared:

diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index 6e92917..5e880ee 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console/fbcon.c
@@ -1095,6 +1095,8 @@ static void fbcon_init(struct vc_data *vc, int init)
con_copy_unimap(vc, svc);

ops = info->fbcon_par;
+   if (vc->vc_cur_blink_ms)
+   vc->vc_cur_blink_ms = 125;
ops->cur_blink_jiffies = msecs_to_jiffies(vc->vc_cur_blink_ms);
p->con_rotate = initial_rotation;
set_blitting_type(vc, info);

Thanks,

>
> Thanks,
>
>>
>> --
>> You received this bug notification because you are subscribed to linux
>> in Ubuntu.
>> https://bugs.launchpad.net/bugs/1574814
>>
>> Title:
>>   ThunderX: soft lockup in cursor_timer_handler() Edit
>>
>> Status in linux package in Ubuntu:
>>   Confirmed
>>
>> Bug description:
>>   I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
>> virtual media:
>> 
>> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>>
>>   During boot I observed the following lockup on the serial console:
>>
>>   [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>>   [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
>> [swapper/14:0]
>>   [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
>> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
>> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
>> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>>   [ 84.922749]
>>   [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
>> #37-Ubuntu
>>   [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>>   [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
>> 801f6c9e8000
>>   [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>>   [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>>   [ 84.922778] pc : [] lr : [] pstate: 
>> 00400145
>>   [ 84.922781] sp : 801f6c9ebc20
>>   [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>>   [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>>   [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>>   [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
>>   [ 84.922802] x21: 0100 x20: 8000f94398d8
>>   [ 84.922807] x19: 8000f9439800 x18: c76a5358
>>   [ 84.922811] x17: 97bbd2a8 x16: 802a5040
>>   [ 84.922816] x15: 3e4cf1e0 x14: 0008
>>   [ 84.922820] x13:  x12: 003d0900
>>   [ 84.922824] x11: 003d0900 x10: 8090f200
>>   [ 84.922829] x9 : 3d09 x8 : 000e
>>   [ 84.922833] x7 : 801f7b3c5008 x6 : 
>

Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-16 Thread Ming Lei

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_update():
>
> for (i = y; i <= y2; i++) {
> /* assume equal stride for now */
> src_offset = dst_offset = i * afbdev->afb.base.pitches[0] + 
> (x * bpp);
> memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram + 
> src_offset, (x2 - x + 1) * bpp);
>
>
> My theory is that this is causing mod_timer() to block on the other CPU, 
> resulting in the soft lockup.
>
> Also - I built a custom d-i using pristine 4.6-rc7, and I am able to
> easily reproduce this. I think the next step here is to report this to
> upstream.

Hi Dann,

Andrew asked me to take a look at the issue, and from my tracing,
most of times, the cpu 'hangs' in the following line of code:

__mod_timer():

out_unlock:
 spin_unlock_irqrestore(>lock, flags);

If I added two trace points around the above line, most of times only
the trace point before the line is dumped, and the one after the line
can't dumped.

Thanks,

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1574814
>
> Title:
>   ThunderX: soft lockup in cursor_timer_handler() Edit
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
> virtual media:
> 
> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>
>   During boot I observed the following lockup on the serial console:
>
>   [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
> [swapper/14:0]
>   [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>   [ 84.922749]
>   [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
> #37-Ubuntu
>   [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>   [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
> 801f6c9e8000
>   [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>   [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>   [ 84.922778] pc : [] lr : [] pstate: 
> 00400145
>   [ 84.922781] sp : 801f6c9ebc20
>   [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>   [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>   [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>   [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
>   [ 84.922802] x21: 0100 x20: 8000f94398d8
>   [ 84.922807] x19: 8000f9439800 x18: c76a5358
>   [ 84.922811] x17: 97bbd2a8 x16: 802a5040
>   [ 84.922816] x15: 3e4cf1e0 x14: 0008
>   [ 84.922820] x13:  x12: 003d0900
>   [ 84.922824] x11: 003d0900 x10: 8090f200
>   [ 84.922829] x9 : 3d09 x8 : 000e
>   [ 84.922833] x7 : 801f7b3c5008 x6 : 
>   [ 84.922837] x5 :  x4 : 0001
>   [ 84.922842] x3 :  x2 : 801f6c899e05
>   [ 84.922846] x1 : 801f667d99e0 x0 : 
>   [ 84.922850]
>   [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 101.342677] random: nonblocking pool is initialized
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-02 Thread Ming Lei

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', the issue still can be triggered.


> And BTW, what is eth7 ?
> >From 16.04 release all interfaces are coming up as "enP2x"

Yeah, maybe this box isn't shipped with 16.04, and its kernel is

ubuntu@arm64:~$ uname -a
Linux arm64 4.2.0 #2 SMP Mon Dec 14 04:01:19 CST 2015 aarch64 aarch64
aarch64 GNU/Linux


but the log is very similar with Dann's report:

[337056.617650] PC is at _raw_spin_unlock_irqrestore+0x30/0x40
[337056.617657] LR is at mod_timer+0x110/0x238


>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1574814
>
> Title:
>   ThunderX: soft lockup in cursor_timer_handler() Edit
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
> virtual media:
> 
> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>
>   During boot I observed the following lockup on the serial console:
>
>   [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
> [swapper/14:0]
>   [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>   [ 84.922749]
>   [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
> #37-Ubuntu
>   [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>   [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
> 801f6c9e8000
>   [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>   [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>   [ 84.922778] pc : [] lr : [] pstate: 
> 00400145
>   [ 84.922781] sp : 801f6c9ebc20
>   [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>   [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>   [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>   [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
>   [ 84.922802] x21: 0100 x20: 8000f94398d8
>   [ 84.922807] x19: 8000f9439800 x18: c76a5358
>   [ 84.922811] x17: 97bbd2a8 x16: 802a5040
>   [ 84.922816] x15: 3e4cf1e0 x14: 0008
>   [ 84.922820] x13:  x12: 003d0900
>   [ 84.922824] x11: 003d0900 x10: 8090f200
>   [ 84.922829] x9 : 3d09 x8 : 000e
>   [ 84.922833] x7 : 801f7b3c5008 x6 : 
>   [ 84.922837] x5 :  x4 : 0001
>   [ 84.922842] x3 :  x2 : 801f6c899e05
>   [ 84.922846] x1 : 801f667d99e0 x0 : 
>   [ 84.922850]
>   [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 101.342677] random: nonblocking pool is initialized
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-02 Thread Ming Lei

On Tue, May 3, 2016 at 10:35 AM, dann frazier
<dann.fraz...@canonical.com> 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
> reproduce. Are you seeing the same traceback along w the softlockup
> msg?

Yes, it can be always triggered by 'tcpdump -I eth7' on cvm13.

>
>-dann
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1574814
>
> Title:
>   ThunderX: soft lockup in cursor_timer_handler() Edit
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
> virtual media:
> 
> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>
>   During boot I observed the following lockup on the serial console:
>
>   [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
> [swapper/14:0]
>   [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>   [ 84.922749]
>   [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
> #37-Ubuntu
>   [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>   [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
> 801f6c9e8000
>   [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>   [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>   [ 84.922778] pc : [] lr : [] pstate: 
> 00400145
>   [ 84.922781] sp : 801f6c9ebc20
>   [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>   [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>   [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>   [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
>   [ 84.922802] x21: 0100 x20: 8000f94398d8
>   [ 84.922807] x19: 8000f9439800 x18: c76a5358
>   [ 84.922811] x17: 97bbd2a8 x16: 802a5040
>   [ 84.922816] x15: 3e4cf1e0 x14: 0008
>   [ 84.922820] x13:  x12: 003d0900
>   [ 84.922824] x11: 003d0900 x10: 8090f200
>   [ 84.922829] x9 : 3d09 x8 : 000e
>   [ 84.922833] x7 : 801f7b3c5008 x6 : 
>   [ 84.922837] x5 :  x4 : 0001
>   [ 84.922842] x3 :  x2 : 801f6c899e05
>   [ 84.922846] x1 : 801f667d99e0 x0 : 
>   [ 84.922850]
>   [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>   [ 101.342677] random: nonblocking pool is initialized
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-04-29 Thread Ming Lei

It can be triggered 100% by running 'tcpdump -I ethX'.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

2016-04-28 Thread Ming Lei

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 of 'Linux ubuntu
4.4.0-23-generic #39' on arm64.

Kernel oops can happen immediately by running the following command:

   stress-ng --remap 64 --timeout 60 -v


Thanks,
Ming

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1575506
>
> Title:
>   Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
>   virtual address 0038
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>
>   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=0047a5b15003, *pud=0047a5b16003, 
> *pmd=
>   [   93.309167] Internal error: Oops: 9606 [#1] SMP
>   [   93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 
> algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
> nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
> nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
> bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
> iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce 
> sha1_ce xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core 
> i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio 
> gpio_keys rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene 
> gpio_dwapb sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb
>   [   93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 
> 4.4.0-15.31-generic #31+clk.1
>   [   93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 
> 2.04.08-beta Feb  2 2016
>   [   93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 
> 8007a7a3
>   [   93.309217] PC is at fput+0x20/0xd0
>   [   93.309222] LR is at vma_do_fput+0x24/0x48
>   [   93.309223] pc : [] lr : [] pstate: 
> 6145
>   [   93.309224] sp : 8007a7a33e20
>   [   93.309226] x29: 8007a7a33e20 x28: 8007a7a3
>   [   93.309228] x27: 0003 x26: 8007a59886e8
>   [   93.309229] x25: 800746248ed8 x24: 8011
>   [   93.309231] x23:  x22: 8091b780
>   [   93.309232] x21: 1000 x20: 
>   [   93.309233] x19:  x18: 1140
>   [   93.309235] x17: 8915f2c0 x16: 80133de0
>   [   93.309236] x15: 893c2000 x14: 
>   [   93.309237] x13: 0003e800 x12: 734b0200
>   [   93.309239] x11: 003d0f00 x10: 0930
>   [   93.309240] x9 :  x8 : 
>   [   93.309242] x7 : 80074645ac10 x6 : 00680f43
>   [   93.309243] x5 : 00680f4f x4 : 0064
>   [   93.309245] x3 : 00680f53 x2 : 0038
>   [   93.309246] x1 : 8091b780 x0 : 801fe1f4
>
>   [   93.309248] Process stress-ng-remap (pid: 2062, stack limit = 
> 0x8007a7a30020)
>   [   93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000)
>   [   93.309252] 3e20: 8007a7a33e40 801fe1f4  
> 8007a59886e8
>   [   93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 
> 80d8e000
>   [   93.309255] 3e60: c85b2280 80085c70  
> 88301000
>   [   93.309257] 3e80:  89161ea8 8000 
> 0015
>   [   93.309258] 3ea0: 011d 00ea 80901000 
> 8007a7a3
>   [   93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 
> 1000
>   [   93.309261] 3ee0:    
> 0200
>   [   93.309262] 3f00: 00d1 00d1 00ea 
> 2626
>   [   93.309264] 3f20: 0101010101010101 001e 0018 
> 0003e800
>   [   93.309266] 3f40:  893c2cc0 004828c0 
> 89161ea0
>   [   93.309267] 3f60: 1140 0050 88301000 
> 1000
>   [   93.309269] 3f80: 1000 c85b2368 88d96fd0 
> 4650
>   [   93.309270] 3fa0: 004558f0 c85b34b8 0048f000 
> c85b2280
>   [   93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 
> 8000
>   [   93.309273] 3fe0: 8830 00ea 8007a7a33fe8 
>

Re: [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

2016-04-28 Thread Ming Lei

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:
>   Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
>   virtual address 0038
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>
>   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

The issue is caused by the following commit:

commit 3df6b7b72fd8cb3fd8dd1bee6916b1c91c74d441
Author: Tim Gardner <tim.gard...@canonical.com>
Date:   Wed Dec 2 07:28:37 2015 -0700

UBUNTU: SAUCE: AUFS

Signed-off-by: Tim Gardner <tim.gard...@canonical.com>

Once it is reverted, no oops is observed any more.

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575506

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 0038

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

2016-04-27 Thread Ming Lei

Upstream 4.6-rc6 hasn't this problem

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575506

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 0038

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

2016-04-27 Thread Ming Lei

** 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/1575506

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 0038

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

2016-04-27 Thread Ming Lei

The issue can be reproduced on '4.4.0-22-generic #38' too

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575506

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 0038

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575506] [NEW] Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

2016-04-27 Thread Ming Lei

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=0047a5b15003, *pud=0047a5b16003, 
*pmd=
[   93.309167] Internal error: Oops: 9606 [#1] SMP
[   93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce 
xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core 
i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys 
rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb 
sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb
[   93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 
4.4.0-15.31-generic #31+clk.1
[   93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta 
Feb  2 2016
[   93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 
8007a7a3
[   93.309217] PC is at fput+0x20/0xd0
[   93.309222] LR is at vma_do_fput+0x24/0x48
[   93.309223] pc : [] lr : [] pstate: 
6145
[   93.309224] sp : 8007a7a33e20
[   93.309226] x29: 8007a7a33e20 x28: 8007a7a3 
[   93.309228] x27: 0003 x26: 8007a59886e8 
[   93.309229] x25: 800746248ed8 x24: 8011 
[   93.309231] x23:  x22: 8091b780 
[   93.309232] x21: 1000 x20:  
[   93.309233] x19:  x18: 1140 
[   93.309235] x17: 8915f2c0 x16: 80133de0 
[   93.309236] x15: 893c2000 x14:  
[   93.309237] x13: 0003e800 x12: 734b0200 
[   93.309239] x11: 003d0f00 x10: 0930 
[   93.309240] x9 :  x8 :  
[   93.309242] x7 : 80074645ac10 x6 : 00680f43 
[   93.309243] x5 : 00680f4f x4 : 0064 
[   93.309245] x3 : 00680f53 x2 : 0038 
[   93.309246] x1 : 8091b780 x0 : 801fe1f4 

[   93.309248] Process stress-ng-remap (pid: 2062, stack limit = 
0x8007a7a30020)
[   93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000)
[   93.309252] 3e20: 8007a7a33e40 801fe1f4  
8007a59886e8
[   93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 
80d8e000
[   93.309255] 3e60: c85b2280 80085c70  
88301000
[   93.309257] 3e80:  89161ea8 8000 
0015
[   93.309258] 3ea0: 011d 00ea 80901000 
8007a7a3
[   93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 
1000
[   93.309261] 3ee0:    
0200
[   93.309262] 3f00: 00d1 00d1 00ea 
2626
[   93.309264] 3f20: 0101010101010101 001e 0018 
0003e800
[   93.309266] 3f40:  893c2cc0 004828c0 
89161ea0
[   93.309267] 3f60: 1140 0050 88301000 
1000
[   93.309269] 3f80: 1000 c85b2368 88d96fd0 
4650
[   93.309270] 3fa0: 004558f0 c85b34b8 0048f000 
c85b2280
[   93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 
8000
[   93.309273] 3fe0: 8830 00ea 8007a7a33fe8 

[   93.309274] Call trace:
[   93.309277] [] fput+0x20/0xd0
[   93.309280] [] vma_do_fput+0x24/0x48
[   93.309283] [] SyS_remap_file_pages+0x258/0x2a0
[   93.309287] [] el0_svc_naked+0x24/0x28
[   93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) 
[   93.309308] ---[ end trace e42a31bddbea7038 ]---
[   93.672808] Unable to handle kernel NULL pointer dereference at virtual 
address 0038
[   93.672809] pgd = 8007d8f22000
[   93.672813] [0038] *pgd=0047d9123003, *pud=0047d9124003, 
*pmd=
[   93.672817] Internal error: Oops: 9606 [#2] SMP
[   93.672853] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce

[Bug 1564653] Re: trusty: arm64: no grub.efi generated by d-i

2016-03-31 Thread Ming Lei

** Branch linked: lp:~tom-leiming/debian-installer/trusty-for-
generating-netboot-tarball

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564653

Title:
  trusty: arm64: no grub.efi generated by d-i

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1564653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1564653] [NEW] trusty: arm64: no grub.efi generated by d-i

2016-03-31 Thread Ming Lei

Public bug reported:


[Impact]

- no grub.efi generated by d-i on arm64, and arm64 server have been switching 
to uefi/grub already,
so arm64 server can't be installed via trusty d-i

[Test Case]

- no grub.efi generated from the following link:
  
http://ports.ubuntu.com/dists/trusty-updates/main/installer-arm64/current/images

[Regression Potential]

- we can only generate grub.efi & netboot.tar.gz for netboot, so all files 
should be added-only,
no potential regression 

[Other Info]

Given netboot.tar.gz have been genereated on Wily & Xenial, this patch also 
takes this way and
generate netboot.tar.gz too.

** Affects: debian-installer (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/1564653

Title:
  trusty: arm64: no grub.efi generated by d-i

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1564653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1546439] Re: ISST:LTE: Regression: roselp2 Oops in kernel during setup io

2016-03-29 Thread Ming Lei

Hi,

The attached patch should fix one related issue, could anyone test it?

Thanks,

** Patch added: "fix crash"
   
https://bugs.launchpad.net/ubuntu/+bug/1546439/+attachment/4615924/+files/0001-block-partition-initialize-percpuref-before-sending-.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546439

Title:
  ISST:LTE: Regression: roselp2 Oops in kernel during setup io

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1546439/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553934] Re: xenial: 'msi_irqs' directory isn't show under pci device capable of MSI

2016-03-14 Thread Ming Lei

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553934

Title:
  xenial: 'msi_irqs' directory isn't show under pci device capable of
  MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553934] [NEW] xenial: 'msi_irqs' directory isn't show under pci device capable of MSI

2016-03-07 Thread Ming Lei

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 kernel and I found populate_msi_sysfs() is run successfully
from this path(pci_enable_msi), but it looks weird.


[1] lspci: 
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722
Gigabit Ethernet PCI Express
Subsystem: Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet
PCI Express
Flags: bus master, fast devsel, latency 0, IRQ 93
Memory at c14000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] Vendor Specific Information: Len=78 
Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-10-18-ff-fe-55-33-0d
Capabilities: [16c] Power Budgeting 
Kernel driver in use: tg3

** 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/1553934

Title:
  xenial: 'msi_irqs' directory isn't show under pci device capable of
  MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1547718] Re: 4.4.0-7.22 no longer boots on arm64

2016-02-22 Thread Ming Lei

On Mon, Feb 22, 2016 at 4:37 PM, Ming Lei <ming@canonical.com> 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-rc5, and the commit(module: clean up RO/NX handling) isn't reverted
> in upstream yet.
>
> So looks there is one real fix in upstream kernel.

The issue was fixed by 57adec866c0440976c96a4b8f5b59f
(arm64: mm: avoid calling apply_to_page_range on empty range), and
this patch is marked as -stalbe.

I have sent this patch outto uk list already.

Thanks,

>
> Thanks,
>
> On Mon, Feb 22, 2016 at 12:07 PM, Tim Gardner <tim.gard...@canonical.com> 
> wrote:
>> ** Changed in: linux (Ubuntu Xenial)
>>  Assignee: (unassigned) => Chris J Arges (arges)
>>
>> --
>> You received this bug notification because you are subscribed to linux
>> in Ubuntu.
>> https://bugs.launchpad.net/bugs/1547718
>>
>> Title:
>>   4.4.0-7.22 no longer boots on arm64
>>
>> Status in linux package in Ubuntu:
>>   Confirmed
>> Status in linux source package in Xenial:
>>   Confirmed
>>
>> Bug description:
>>   Observed on X-Gene and ThunderX.
>>
>>   [2.059489] kernel BUG at 
>> /build/linux-RKt9qy/linux-4.4.0/mm/memory.c:1887!
>>   [2.066418] Internal error: Oops - BUG: 0 [#1] SMP
>>   [2.071185] Modules linked in:
>>   [2.074234] CPU: 1 PID: 156 Comm: systemd-udevd Not tainted 
>> 4.4.0-7-generic #22-Ubuntu
>>   [2.082109] Hardware name: APM X-Gene Mustang board (DT)
>>   [2.087393] task: 8001f679d780 ti: 8001df4a4000 task.ti: 
>> 8001df4a4000
>>   [2.094840] PC is at apply_to_page_range+0x330/0x378
>>   [2.099780] LR is at change_memory_common+0x94/0x148
>>   [2.104717] pc : [] lr : [] pstate: 
>> 6145
>>   [2.112073] sp : 8001df4a7b30
>>   [2.115369] x29: 8001df4a7b30 x28: 
>>   [2.120671] x27: 7c00f000 x26: 7c009550
>>   [2.125974] x25: 8009aa18 x24: 7c009500
>>   [2.131276] x23: 8001df4a7c38 x22: 8009a878
>>   [2.136579] x21: 80d56000 x20: 7c00f000
>>   [2.141881] x19: 7c00f000 x18: 8090f928
>>   [2.147183] x17: 8001df4a79e8 x16: b4cc9cbc209fc557
>>   [2.152485] x15:  x14: 
>>   [2.157788] x13:  x12: 0010
>>   [2.163091] x11: 0018 x10: 0101010101010101
>>   [2.168393] x9 :  x8 : 7f7f7f7f7f7f7f7f
>>   [2.173694] x7 : 636e712cff646b61 x6 : 00802e726f64
>>   [2.178996] x5 : 646f722e x4 : 8001df4a7c38
>>   [2.184298] x3 : 8009a878 x2 : 
>>   [2.189601] x1 : 7c00f000 x0 : 8009a964
>>   [2.194902]
>>   [2.196384] Process systemd-udevd (pid: 156, stack limit = 
>> 0x8001df4a4020)
>>   [2.203568] Stack: (0x8001df4a7b30 to 0x8001df4a8000)
>>   [2.209283] 7b20:   8001df4a7bf0 
>> 8009a964
>>   [2.217073] 7b40: 7c00f000 7c00f000 80d56000 
>> 0008
>>   [2.224862] 7b60: 0080 7c009500 8009aa18 
>> 7c009550
>>   [2.232651] 7b80: 8001df4a7df0  80f11800 
>> 7c00efff
>>   [2.240440] 7ba0: 7c00f000 7c00f000 7c00f000 
>> 8000
>>   [2.248227] 7bc0: 7c00efff  80d93af0 
>> 80d93af0
>>   [2.256016] 7be0: 8001df4a7c40 80d93af0 8001df4a7c50 
>> 8009aac8
>>   [2.263805] 7c00: 7c00f000  7c009300 
>> 80d56000
>>   [2.271594] 7c20: 80d8 0080 0008 
>> 0080
>>   [2.279383] 7c40: 0008 cb88537fdc8ba602 8001df4a7c70 
>> 80145400
>>   [2.287172] 7c60: 7c009550 8009aa98 8001df4a7c90 
>> 80147350
>>   [2.294961] 7c80: 7c009300 8009aa98 8001df4a7cb0 
>> 801499cc
>>   [2.302750] 7ca0: 7c009318 8001df4a7e68 8001df4a7e30 
>> 80149ec8
>>   [2.310539] 7cc0: 80d56000  0006 
>> 94668108
>>   [2.318327] 7ce0: 8000 0015 000

[Bug 1548207] Re: xenial 4.4.0-7-generic: kernel oops during load module

2016-02-22 Thread Ming Lei

*** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548207

Title:
  xenial 4.4.0-7-generic: kernel oops during load module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1547718] Re: 4.4.0-7.22 no longer boots on arm64

2016-02-22 Thread Ming Lei

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 there is one real fix in upstream kernel.

Thanks,

On Mon, Feb 22, 2016 at 12:07 PM, Tim Gardner  wrote:
> ** Changed in: linux (Ubuntu Xenial)
>  Assignee: (unassigned) => Chris J Arges (arges)
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1547718
>
> Title:
>   4.4.0-7.22 no longer boots on arm64
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux source package in Xenial:
>   Confirmed
>
> Bug description:
>   Observed on X-Gene and ThunderX.
>
>   [2.059489] kernel BUG at 
> /build/linux-RKt9qy/linux-4.4.0/mm/memory.c:1887!
>   [2.066418] Internal error: Oops - BUG: 0 [#1] SMP
>   [2.071185] Modules linked in:
>   [2.074234] CPU: 1 PID: 156 Comm: systemd-udevd Not tainted 
> 4.4.0-7-generic #22-Ubuntu
>   [2.082109] Hardware name: APM X-Gene Mustang board (DT)
>   [2.087393] task: 8001f679d780 ti: 8001df4a4000 task.ti: 
> 8001df4a4000
>   [2.094840] PC is at apply_to_page_range+0x330/0x378
>   [2.099780] LR is at change_memory_common+0x94/0x148
>   [2.104717] pc : [] lr : [] pstate: 
> 6145
>   [2.112073] sp : 8001df4a7b30
>   [2.115369] x29: 8001df4a7b30 x28: 
>   [2.120671] x27: 7c00f000 x26: 7c009550
>   [2.125974] x25: 8009aa18 x24: 7c009500
>   [2.131276] x23: 8001df4a7c38 x22: 8009a878
>   [2.136579] x21: 80d56000 x20: 7c00f000
>   [2.141881] x19: 7c00f000 x18: 8090f928
>   [2.147183] x17: 8001df4a79e8 x16: b4cc9cbc209fc557
>   [2.152485] x15:  x14: 
>   [2.157788] x13:  x12: 0010
>   [2.163091] x11: 0018 x10: 0101010101010101
>   [2.168393] x9 :  x8 : 7f7f7f7f7f7f7f7f
>   [2.173694] x7 : 636e712cff646b61 x6 : 00802e726f64
>   [2.178996] x5 : 646f722e x4 : 8001df4a7c38
>   [2.184298] x3 : 8009a878 x2 : 
>   [2.189601] x1 : 7c00f000 x0 : 8009a964
>   [2.194902]
>   [2.196384] Process systemd-udevd (pid: 156, stack limit = 
> 0x8001df4a4020)
>   [2.203568] Stack: (0x8001df4a7b30 to 0x8001df4a8000)
>   [2.209283] 7b20:   8001df4a7bf0 
> 8009a964
>   [2.217073] 7b40: 7c00f000 7c00f000 80d56000 
> 0008
>   [2.224862] 7b60: 0080 7c009500 8009aa18 
> 7c009550
>   [2.232651] 7b80: 8001df4a7df0  80f11800 
> 7c00efff
>   [2.240440] 7ba0: 7c00f000 7c00f000 7c00f000 
> 8000
>   [2.248227] 7bc0: 7c00efff  80d93af0 
> 80d93af0
>   [2.256016] 7be0: 8001df4a7c40 80d93af0 8001df4a7c50 
> 8009aac8
>   [2.263805] 7c00: 7c00f000  7c009300 
> 80d56000
>   [2.271594] 7c20: 80d8 0080 0008 
> 0080
>   [2.279383] 7c40: 0008 cb88537fdc8ba602 8001df4a7c70 
> 80145400
>   [2.287172] 7c60: 7c009550 8009aa98 8001df4a7c90 
> 80147350
>   [2.294961] 7c80: 7c009300 8009aa98 8001df4a7cb0 
> 801499cc
>   [2.302750] 7ca0: 7c009318 8001df4a7e68 8001df4a7e30 
> 80149ec8
>   [2.310539] 7cc0: 80d56000  0006 
> 94668108
>   [2.318327] 7ce0: 8000 0015 011d 
> 0111
>   [2.326116] 7d00: 808d7000 8001df4a4000 00adb000 
> 80e35220
>   [2.333905] 7d20: 80e354a0 7c00f000 00aef878 
> 808e7f68
>   [2.341693] 7d40: 0072 80010064 8001006e 
> 003f
>   [2.349482] 7d60: 7c00f000 0018 8001df4a7e30 
> 80149e8c
>   [2.357271] 7d80: 80d56000  0006 
> 94668108
>   [2.365060] 7da0:    
> 8000
>   [2.372849] 7dc0:  81a4  
> 
>   [2.380638] 7de0:   6c656e72656b 
> 
>   [2.388427] 7e00:    
> 
>   [2.396216] 7e20:

[Bug 1548207] Re: xenial 4.4.0-7-generic: kernel oops during load module

2016-02-22 Thread Ming Lei

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548207

Title:
  xenial 4.4.0-7-generic: kernel oops during load module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1548207] Re: xenial 4.4.0-7-generic: kernel oops during load module

2016-02-22 Thread Ming Lei

** 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/1548207

Title:
  xenial 4.4.0-7-generic: kernel oops during load module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1548207] [NEW] xenial 4.4.0-7-generic: kernel oops during load module

2016-02-21 Thread Ming Lei

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: Oops - BUG: 0 [#1] SMP
[0.599685] Modules linked in:
[0.602738] CPU: 7 PID: 164 Comm: systemd-udevd Not tainted 4.4.0-7-generic 
#22-Ubuntu
[0.610616] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta 
Feb  2 2016
[0.618493] task: 8007f95dcb00 ti: 8000fac44000 task.ti: 
8000fac44000
[0.625941] PC is at apply_to_page_range+0x330/0x378
[0.630881] LR is at change_memory_common+0x94/0x148
[0.635819] pc : [] lr : [] pstate: 
6145
[0.643175] sp : 8000fac47b20
[0.646470] x29: 8000fac47b20 x28:  
[0.651774] x27: 7c00c000 x26: 7c0067d0 
[0.657079] x25: 8009aa18 x24: 7c006780 
[0.662383] x23: 8000fac47c28 x22: 8009a878 
[0.667686] x21: 80d56000 x20: 7c00c000 
[0.672990] x19: 7c00c000 x18: 8090f928 
[0.678293] x17: 8000fac479e8 x16: 40362c49a8665c46 
[0.683597] x15:  x14:  
[0.688900] x13:  x12: 0010 
[0.694203] x11: 0018 x10: 0101010101010101 
[0.699506] x9 : fffb x8 : 7f7f7f7f7f7f7f7f 
[0.704810] x7 : 636e712cff646b61 x6 : 00802e726f64 
[0.710113] x5 : 646f722e x4 : 8000fac47c28 
[0.715416] x3 : 8009a878 x2 :  
[0.720719] x1 : 7c00c000 x0 : 8009a964 
[0.726022] 
[0.727504] Process systemd-udevd (pid: 164, stack limit = 
0x8000fac44020)
[0.734688] Stack: (0x8000fac47b20 to 0x8000fac48000)
[0.740404] 7b20: 8000fac47be0 8009a964 7c00c000 
7c00c000
[0.748193] 7b40: 80d56000 0008 0080 
7c006780
[0.755982] 7b60: 8009aa18 7c0067d0 8000fac47df0 

[0.763770] 7b80: 8000fac47df0  80f11800 
7c005fff
[0.771559] 7ba0: 7c00c000 7c005fff 7c006000 
7c006000
[0.779347] 7bc0: 80e4c000 8000 7c005fff 
80d93af0
[0.787136] 7be0: 8000fac47c40 8009aac8 7c00c000 

[0.794924] 7c00: 8009aa98 80d56000 80d8 
80d56000
[0.802712] 7c20: 80d8 0080 0008 
cb88537fdc8ba602
[0.810501] 7c40: 8000fac47c60 80146604 7c00c000 
7c0067dc
[0.818289] 7c60: 8000fac47c90 80147344 7c006580 
8009aa98
[0.826078] 7c80: 7c006580 8009aa98 8000fac47cb0 
801499cc
[0.833866] 7ca0: 7c006598 8000fac47e68 8000fac47e30 
80149ec8
[0.841655] 7cc0: 80d56000  0005 
84475948
[0.849443] 7ce0: 8000 0015 011d 
0111
[0.857232] 7d00: 808d7000 8000fac44000 002d3000 
80e35220
[0.865020] 7d20: 80e354a0 7c00c000 002e3dd8 
808e7f68
[0.872808] 7d40: 0072 8064 806e 
003f
[0.880597] 7d60: 7c00c000 0018 8000fac47e30 
80149e8c
[0.888385] 7d80: 80d56000  0005 
84475948
[0.896174] 7da0:   7c004028 
8019
[0.903962] 7dc0:  81a4  

[0.911751] 7de0:   6c656e72656b 

[0.919539] 7e00:    

[0.927328] 7e20:  cb88537fdc8ba602 f8415d90 
80085c70
[0.935116] 7e40:  370b5810  
843008b4
[0.942905] 7e60: 011d 002d3000 00010e58 
002e3598
[0.950693] 7e80: 002e3420 002dda70 7000 
9520
[0.958482] 7ea0:  0001 00220021 
0016001b
[0.966270] 7ec0: 0012 cb88537fdc8ba602 0005 
84475948
[0.974059] 7ee0:  0005  

[0.981847] 7f00:   0111 
fefefefefeff0110
[0.989635] 7f20:  0007 0038 
0800
[0.997424] 7f40: 656e72656b206f6b 84382590 84300890 
844881d0
[1.005212] 7f60: f8415af0 370b2bf0

[Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-18 Thread Ming Lei

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' is only passed to gcc when modules are builting,
and it isn't used for building kernel.


Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-15 Thread Ming Lei

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-image-`uname -r`

2) cd linux-#only one directory is generated

3) make -C /usr/src/linux-headers-`uname -r` M=`pwd`
drivers/ata/libahci.ko

then the libahci.ko will be generated.

BTW, the issue can only be reproduced on Xenial.

Thanks,


>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1533009
>
> Title:
>   arm64: "unsupported RELA relocation"
>
> Status in gcc-5 package in Ubuntu:
>   New
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
>   (and therefore boot). It emits messages like the following for each
>   attempted module load:
>
>   [2.156817] module libahci: unsupported RELA relocation: 275
>
>   This is reminiscent of LP: #1502946 - except that fix appears to still
>   be in-tact. What has changed, however, is the build environment. If I
>   rebuild the same kernel source in a wily chroot, it boots fine.
>
>   Marking "Confirmed" because Paulo Pisatti reported this to me, and I
>   reproduced.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1533009/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1533009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-15 Thread Ming Lei

Looks the latest  proposed gcc-5.3.1-6ubuntu1 has the problem too.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1533009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-13 Thread Ming Lei

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 problem.

thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1533009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-13 Thread Ming Lei

When same kernel tree is built with gcc 5.3.1 from Xenial, the generated modlues
can't be loaded any more and '-mcmodel=large' is still passed to gcc
during kernel
building, so it looks like a compiler bug:

ubuntu@ubuntu:~/git$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/5/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
5.3.1-5ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
--prefix=/usr --program-suffix=-5 --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libquadmath --enable-plugin --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-arm64/jre
--enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-arm64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-arm64
--with-arch-directory=aarch64
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-multiarch
--disable-werror --enable-checking=release --build=aarch64-linux-gnu
--host=aarch64-linux-gnu --target=aarch64-linux-gnu
Thread model: posix
gcc version 5.3.1 20160108 (Ubuntu/Linaro 5.3.1-5ubuntu2)


On Wed, Jan 13, 2016 at 9:11 AM, Ming Lei <ming@canonical.com> 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:
>
> ubuntu@ubuntu:~$ gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/5/lto-wrapper
> Target: aarch64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 5.2.1-22ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
> --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
> --prefix=/usr --program-suffix=-5 --enable-shared
> --enable-linker-build-id --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --libdir=/usr/lib
> --enable-nls --with-sysroot=/ --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
> --disable-libquadmath --enable-plugin --with-system-zlib
> --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-arm64/jre
> --enable-java-home
> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-arm64
> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-arm64
> --with-arch-directory=aarch64
> --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-multiarch
> --disable-werror --enable-checking=release --build=aarch64-linux-gnu
> --host=aarch64-linux-gnu --target=aarch64-linux-gnu
>
>
> the built image just works well:
>
>   ubuntu@ubuntu:~$ uname -a
>   Linux ubuntu 4.3.0-7-generic #18 SMP Tue Jan 12 10:19:24 EST 2016
>   aarch64 aarch64 aarch64 GNU/Linux
>
>
> But I can see the issue when booting a kernel from the following package[1]:
>
>  
> http://launchpadlibrarian.net/230287220/linux-image-4.3.0-5-generic_4.3.0-5.16_arm64.deb
>
> It is a build environment issue instead of kernel issue, please see
> comments from Ard Biesheuvel <ard.biesheu...@linaro.org> [2]:
>
> RELA #275 is the relocation against ADRP instructions, which GCC
> should not emit anymore when -mcmodel=large is in effect.
>
> Can you confirm that the modules have been rebuilt with this config as
> well? Can you double check the GCC command line (with V=1) when doing
> 'make modules' to ensure that '-mcmodel=large' is being passed? Can
> you check with 'readelf -r' which objects still contain
> R_AARCH64_ADR_PREL_PG_HI21 relocations?
>
> I have checked the gcc flag in my building environment, and '-mcmodel=large' 
> is
> passed, and CONFIG_ARM64_ERRATUM_843419 is enabled too.
>
> I don't know how the image in [1] is built, so could anyone check the build
> environment for this building?
>
>
> [1] 
> http://launchpadlibrarian.net/230287220/linux-image-4.3.0-5-generic_4.3.0-5.16_arm64.deb
> [2] http://www.spinics.net/lists/arm-kernel/msg449991.html
>
>
> On Tue, Jan 12, 2016 at 7:47 PM, Raghuram Kota
> <raghuram.k...@canonical.com> wrote:
>> ** Tags added: hs-arm64
>>
>> --
>> You received this bug notification because you are subscribed to linux
>> in Ubuntu.
>> https://bugs.launchpad.ne

Re: [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-12 Thread Ming Lei

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/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
5.2.1-22ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
--prefix=/usr --program-suffix=-5 --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libquadmath --enable-plugin --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-arm64/jre
--enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-arm64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-arm64
--with-arch-directory=aarch64
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-multiarch
--disable-werror --enable-checking=release --build=aarch64-linux-gnu
--host=aarch64-linux-gnu --target=aarch64-linux-gnu


the built image just works well:

  ubuntu@ubuntu:~$ uname -a
  Linux ubuntu 4.3.0-7-generic #18 SMP Tue Jan 12 10:19:24 EST 2016
  aarch64 aarch64 aarch64 GNU/Linux


But I can see the issue when booting a kernel from the following package[1]:

 http://launchpadlibrarian.net/230287220/linux-
image-4.3.0-5-generic_4.3.0-5.16_arm64.deb

It is a build environment issue instead of kernel issue, please see
comments from Ard Biesheuvel  [2]:

RELA #275 is the relocation against ADRP instructions, which GCC
should not emit anymore when -mcmodel=large is in effect.

Can you confirm that the modules have been rebuilt with this config as
well? Can you double check the GCC command line (with V=1) when doing
'make modules' to ensure that '-mcmodel=large' is being passed? Can
you check with 'readelf -r' which objects still contain
R_AARCH64_ADR_PREL_PG_HI21 relocations?

I have checked the gcc flag in my building environment, and '-mcmodel=large' is
passed, and CONFIG_ARM64_ERRATUM_843419 is enabled too.

I don't know how the image in [1] is built, so could anyone check the build
environment for this building?


[1] 
http://launchpadlibrarian.net/230287220/linux-image-4.3.0-5-generic_4.3.0-5.16_arm64.deb
[2] http://www.spinics.net/lists/arm-kernel/msg449991.html


On Tue, Jan 12, 2016 at 7:47 PM, Raghuram Kota
 wrote:
> ** Tags added: hs-arm64
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1533009
>
> Title:
>   arm64: "unsupported RELA relocation"
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
>   (and therefore boot). It emits messages like the following for each
>   attempted module load:
>
>   [2.156817] module libahci: unsupported RELA relocation: 275
>
>   This is reminiscent of LP: #1502946 - except that fix appears to still
>   be in-tact. What has changed, however, is the build environment. If I
>   rebuild the same kernel source in a wily chroot, it boots fine.
>
>   Marking "Confirmed" because Paulo Pisatti reported this to me, and I
>   reproduced.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533009/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1521612] Re: Continued TFTP timeouts when PXE booting via grub

2015-12-21 Thread Ming Lei

Hi Dann,

On Mon, Dec 21, 2015 at 11:59 PM, dann frazier
 wrote:
> @Ming can you clarify which build(s) you tested (trusty, vivid, and/or
> wily)? It isn't clear to me if "three grub changes" means you tested all

All three have been tested on both two kinds of arm64.

thanks,

> 3 builds, or if you tested one build comprising 3 source changes.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1521612
>
> Title:
>   Continued TFTP timeouts when PXE booting via grub
>
> Status in grub2 package in Ubuntu:
>   Fix Released
> Status in grub2-signed package in Ubuntu:
>   Fix Released
> Status in grub2 source package in Trusty:
>   Fix Committed
> Status in grub2-signed source package in Trusty:
>   Fix Committed
> Status in grub2 source package in Vivid:
>   Fix Committed
> Status in grub2-signed source package in Vivid:
>   Fix Committed
> Status in grub2 source package in Wily:
>   Fix Committed
> Status in grub2-signed source package in Wily:
>   Fix Committed
> Status in grub2 source package in Xenial:
>   Fix Released
> Status in grub2-signed source package in Xenial:
>   Fix Released
>
> Bug description:
>   [Impact]
>   While the Grub2 patches described in LP#1508893 reduce the TFTP time-out, 
> HP ProLiant m400 servers when booting via UEFI, may still experience TFTP 
> timeouts.
>
>   [Test Case]
>   PXE boot a UEFI-based system (d-i or MAAS) and monitor the time it takes 
> for GRUB to download the kernel/initrd. tcpdump will show TFTP timeouts and 
> packet retries, and it can take on the order of minutes to begin running the 
> kernel.
>
>   [Regression Risk]
>   The fix is restricted to UEFI-based systems.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1521612/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521612

Title:
  Continued TFTP timeouts when PXE booting via grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1521612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521612] Re: Continued TFTP timeouts when PXE booting via grub

2015-12-20 Thread Ming Lei

The three grub changes have been tested fine on both APM arm64 board and HP 
m400, looks
all works fine.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521612

Title:
  Continued TFTP timeouts when PXE booting via grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1521612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1527047] [NEW] arm64: wily: hanging during reboot

2015-12-16 Thread Ming Lei

Public bug reported:


Inside VM wily kernel which is installed via wily d-i installer, reboot hangs, 
see the following message:

[   40.294727] reboot: Restarting system

And never return to UEFI UI.


The issue can be observed too in d-i installing too.

** Affects: edk2 (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/1527047

Title:
  arm64: wily: hanging during reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1527047/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521612] Re: Continued TFTP timeouts when PXE booting via grub

2015-12-14 Thread Ming Lei

Now grub2 for Xenial just works fine on mcdivitt in case of netboot, especially 
during loading kernel image
via tftp.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521612

Title:
  Continued TFTP timeouts when PXE booting via grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1521612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508893] Re: TFTP timeout when booting from grub that was PXE loaded

2015-11-26 Thread Ming Lei

On HP ProLiant m400 Server, when booting via UEFI, TFTP still may timeout when 
loading kernel by
netboot.

Looks only the commit 49426e9fd2( efinet: open Simple Network Protocol 
exclusively) isn't enough, and the
following three commits are required too for grub working well on HP m400 ARM64 
server:

  7b386b703154c0901c4616(efidisk: move device path helpers in core for 
efinet)
  c52ae40570c3bfbcca22d21(efinet: skip virtual IPv4 and IPv6 devices when 
enumerating cards)
 f348aee7b33dd85e7da62b(efinet: enable hardware filters when opening 
interface)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893

Title:
  TFTP timeout when booting from grub that was  PXE loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1507653] Re: Wily kernel crashed when running ifconfig eth0 up/done test

2015-11-23 Thread Ming Lei

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 during ifconfig up/down test"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507653/+attachment/4524380/+files/enet-ifconfig-down-up.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507653

Title:
  Wily kernel crashed when running ifconfig eth0 up/done test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1517582] Re: flash-kernel causes postinsts to fail when it happens to be installed on an unsupported system

2015-11-19 Thread Ming Lei

The following should fix the issue of flash-kernel, could anyone give a test in 
MAAS?

diff --git a/functions b/functions
index 97bbdd9..e753054 100644
--- a/functions
+++ b/functions
@@ -429,6 +429,10 @@ fi
 kfile_suffix=$(get_kfile_suffix "$kfile")
 
 if ! check_supported "$machine"; then
+   # do nothing if one unsupported platform is booted from EFI
+   if [ -d /sys/firmware/efi ]; then
+   exit 0
+   fi
error "Unsupported platform."
 fi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517582

Title:
  flash-kernel causes postinsts to fail when it happens to be installed
  on an unsupported system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1517582/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1508893] Re: TFTP timeout on ARM64 hw when booting from grub that was PXE loaded

2015-11-03 Thread Ming Lei

On Tue, Nov 3, 2015 at 11:48 PM, Newell Jensen
 wrote:
> Ming,
>
> Trying to use your bootnetaa64.efi file from
> http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi
>
> I am not able to test this because I cannot PXE boot:
>
> TianoCore 2.0.0 UEFI 2.4.0 Sep  1 2015 12:48:07
> CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
>  32 KB ICACHE, 32 KB DCACHE
>  SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 66MHz
> Board: X-Gene Merlin Board
> Slimpro FW:
> Ver: 3.4 (build 2015/07/22)
> PMD: 980 mV
> SOC: 950 mV
> The default boot selection will start in   3 seconds
> [1] ubuntu
> [2] PXE on MAC :3C
> [3] nfs boot via TFTP
> [4] Shell
> [5] Boot Manager
> [6] Reboot
> [7] Shutdown
> Start: 2
> ..PXE-E23: Client received TFTP error from server.
> [1] ubuntu
> [2] PXE on MAC :3C
> [3] nfs boot via TFTP
> [4] Shell
> [5] Boot Manager
> [6] Reboot
> [7] Shutdown
> Start: 2
> ..PXE-E23: Client received TFTP error from server.
> [1] ubuntu
> [2] PXE on MAC :3C
> [3] nfs boot via TFTP
> [4] Shell
> [5] Boot Manager
> [6] Reboot
> [7] Shutdown
> Start:

I can't see the failure, and looks it is fine for me today, see following log:
TianoCore 2.0.0 UEFI 2.4.0 Sep  1 2015 12:48:07
CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
 32 KB ICACHE, 32 KB DCACHE
 SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 66MHz
Board: X-Gene Merlin Board
Slimpro FW:
Ver: 3.4 (build 2015/07/22)
PMD: 980 mV
SOC: 950 mV
The default boot selection will start in   3 seconds
[1] ubuntu
[2] PXE on MAC :3C
[3] nfs boot via TFTP
[4] Shell
[5] Boot Manager
[6] Reboot
[7] Shutdown
Start: 2
..

then follows grub menu.

If you are online a bit early tomorrow, I can test it with you together.

Thanks,




>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1508893
>
> Title:
>   TFTP timeout on ARM64 hw when booting from grub that was  PXE loaded
>
> Status in grub2 package in Ubuntu:
>   New
>
> Bug description:
>   This issue was discovered  with Ubuntu Wily (15.10) on a currently in
>   development ARM64 HW.
>
>   When loading kernel via tftp in grub on this hardware, the system
>   stops receiving new packets (times out )  after receiving initial few
>   tens of tftp data packets , which then causes kernel load failure.
>
>   Running tcpdump before loading kernel in grub menu shows timeouts
>   occurring,  as captured in the below log  :
>
> http://kernel.ubuntu.com/~ming/grub/apm.tcpdump
>
>   Following are the  detailed reproduction steps :
>
>   1) setup PXE boot entry in UEFI(no any parameter to grub)
>   2) build one grub from upstream (and/or Wily)  and put it in PXE server
>   3) setup grub config, suppose the shape is like below:
>menuentry 'Install for arm64' {
> linux /ubuntu-installer/arm64/Image --- console=ttyS0,115200
> initrd /ubuntu-installer/arm64/initrd.gz
>   }
>   4) start PXE booting in UEFI
>   5) grub prompt is coming
>   6) select 'Install for arm64' menu item and press 'enter' to start
>   loading kernel
>   7) then hangs inside loading kernel
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893

Title:
  TFTP timeout on ARM64 hw when booting from grub that was  PXE loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512193] Re: arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after a fresh install

2015-11-02 Thread Ming Lei

1) write environment failure

 grub> save_env 123
 error: failure writing sector 0xe153800 to `hd0'.

2) LBA of grub environment variable file
ubuntu@ubuntu:~$ sudo hdparm --fibmap /boot/grub/grubenv
[sudo] password for ubuntu: 

/boot/grub/grubenv:
 filesystem blocksize 4096, begins at LBA 1050624; assuming 512 byte sectors.
 byte_offset  begin_LBAend_LBAsectors
   0  236271616  236271623  8
=> 0xE153800 - 0xE153807

3) From 1) and 2), the sector number to be wroten is correct

4) debug message:
lib/disk.c:61: Writing `hd0'...
disk/efi/efidisk.c:602: writing 0x2 sectors at the sector 0xe153800 to hd0
kern/disk.c:295: Closing `hd0'.
disk/efi/efidisk.c:553: closing hd0
error: failure writing sector 0xe153800 to `hd0'.

grub_efidisk_write()
->grub_efidisk_readwrite()
  ->efi_call_5()...

5) so looks the issue should be related with APM's UEFI firmware:
X-Gene Merlin Board
Boot firmware (version 2.0.0 built at 12:52:11 on Sep  1 2015)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512193

Title:
  arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after
  a fresh install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1512193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508087] Re: Unhandled UDP error during manual enlistment of xgene-2

2015-11-02 Thread Ming Lei

This one should be same with LP1508738, and can anyone to try to use the 
customerised grub to see if it
can fix the issue?

   http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508087

Title:
  Unhandled UDP error during manual enlistment of xgene-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1508087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508087] Re: Unhandled UDP error during manual enlistment of xgene-2

2015-11-02 Thread Ming Lei

This one should be same with LP1508738, and can anyone to try to use the 
customerised grub to see if it
can fix the issue?

   http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/1508087

Title:
  Unhandled UDP error during manual enlistment of xgene-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1508087/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1512193] Re: arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after a fresh install

2015-11-01 Thread Ming Lei

That can be reproduced by running 'save_env' command in grub shell:

 grub> save_env 123
 error: failure writing sector 0xe14d800 to `hd0'.


Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512193

Title:
  arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after
  a fresh install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1512193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512193] Re: arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after a fresh install

2015-11-01 Thread Ming Lei

The issue can be work around by commenting 'recordfail' in the boot entry of 
'Ubuntu'.

And it can be reproduced on upstrem grub too.

Looks the sectors wroten to hd0 is out of range in the partition, and it
should be bug in grub.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512193

Title:
  arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after
  a fresh install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1512193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512193] [NEW] arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after a fresh install

2015-11-01 Thread Ming Lei

Public bug reported:

1, grub boot log

TianoCore 2.0.0 UEFI 2.4.0 Sep  1 2015 12:48:07
CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
 32 KB ICACHE, 32 KB DCACHE
 SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 66MHz
Board: X-Gene Merlin Board
Slimpro FW:
Ver: 3.4 (build 2015/07/22)
PMD: 980 mV
SOC: 950 mV
The default boot selection will start in   3 seconds
[1] ubuntu
[2] PXE on MAC :3C
[3] Shell
[4] Boot Manager
[5] Reboot
[6] Shutdown
Start: 1
error: no suitable video mode found.
error: failure writing sector 0x19df788 to `hd0'.


2, disk information
2.1 parted
ubuntu@ubuntu:~$ sudo parted /dev/sda -- print
Model: ATA Corsair Neutron (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End SizeFile system Name  Flags
 1  1049kB  538MB   537MB   fat16   EFI System Partition  boot, esp
 2  538MB   87.1GB  86.5GB  ext4
 3  87.1GB  120GB   32.9GB  linux-swap(v1)

2.2 hdparm -I
ubuntu@ubuntu:~$ sudo hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
Model Number:   Corsair Neutron GTX SSD 
Serial Number:  1344790897140140
Firmware Revision:  M311
Transport:  Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, 
SATA Rev 2.5
Standards:
Supported: 8 7 6 5 
Likely used: 8
Configuration:
Logical max current
cylinders   16383   0
heads   16  0
sectors/track   63  0
--
LBAuser addressable sectors:  234441648
LBA48  user addressable sectors:  234441648
Logical/Physical Sector size:   512 bytes
device size with M = 1024*1024:  114473 MBytes
device size with M = 1000*1000:  120034 MBytes (120 GB)
cache/buffer size  = unknown
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16  Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4 
 Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
Enabled Supported:
   *SMART feature set
Security Mode feature set
   *Power Management feature set
   *Write cache
   *Look-ahead
   *Host Protected Area feature set
   *WRITE_BUFFER command
   *READ_BUFFER command
   *NOP cmd
   *DOWNLOAD_MICROCODE
   *48-bit Address feature set
   *Mandatory FLUSH_CACHE
   *FLUSH_CACHE_EXT
   *SMART error logging
   *SMART self-test
   *WRITE_{DMA|MULTIPLE}_FUA_EXT
WRITE_DMA_QUEUED_FUA_EXT
   *WRITE_UNCORRECTABLE_EXT command
   *{READ,WRITE}_DMA_EXT_GPL commands
   *Gen1 signaling speed (1.5Gb/s)
   *Gen2 signaling speed (3.0Gb/s)
   *Gen3 signaling speed (6.0Gb/s)
   *Native Command Queueing (NCQ)
   *Host-initiated interface power management
   *Phy event counters
   *Device automatic Partial to Slumber transitions
   *READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
Non-Zero buffer offsets in DMA Setup FIS
DMA Setup Auto-Activate optimization
Device-initiated interface power management
In-order data delivery
   *Software settings preservation
   *Data Set Management TRIM supported (limit 1 block)
Security: 
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

** Affects: grub2 (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/1512193

Title:
  arm64: report 'error: failure writing sector 0x19df788 to `hd0'' after
  a fresh install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1512193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1440536] Re: Oops __d_lookup+0x88/0x194

2015-10-27 Thread Ming Lei

On Tue, Oct 27, 2015 at 11:03 PM, Fathi Boudra <fathi.bou...@linaro.org> 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.

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1440536
>
> Title:
>   Oops __d_lookup+0x88/0x194
>
> Status in Linux:
>   Unknown
> Status in linux package in Ubuntu:
>   Triaged
> Status in linux source package in Vivid:
>   Triaged
>
> Bug description:
>   This started happening on a Mustang board after upgrading to
>   3.19.0-9.9 and persists in 3.19.0-11.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: linux-image-3.19.0-11-generic 3.19.0-11.11
>   ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
>   Uname: Linux 3.19.0-11-generic aarch64
>   AlsaDevices:
>total 0
>crw-rw 1 root audio 116,  1 Dec 31  1969 seq
>crw-rw 1 root audio 116, 33 Dec 31  1969 timer
>   AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
>   ApportVersion: 2.17-0ubuntu1
>   Architecture: arm64
>   ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
> '/dev/snd/seq'] failed with exit code 1:
>   CRDA: Error: [Errno 2] No such file or directory: 'iw'
>   Date: Sun Apr  5 08:32:28 2015
>   HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b
>   IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
>   Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to 
> initialize libusb: -99
>   PciMultimedia:
>
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB:
>
>   ProcKernelCmdLine: console=ttyS0,115200n8 ro 
> earlyprintk=uart8250-32bit,0x1c02
>   RelatedPackageVersions:
>linux-restricted-modules-3.19.0-11-generic N/A
>linux-backports-modules-3.19.0-11-generic  N/A
>linux-firmware 1.143
>   RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
>   SourcePackage: linux
>   SystemImageInfo:
>current build number: 0
>device name: ?
>channel: daily
>last update: Unknown
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440536

Title:
  Oops __d_lookup+0x88/0x194

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508893] Re: TFTP timeout on ARM64 hw when booting from grub that was PXE loaded

2015-10-26 Thread Ming Lei

> A build from upstream git shows this problem as well.

Looks it is thought as one AMI firmware's issue, so the patch should be merged 
to grub, otherwise
grub can't run on APM's UEFI firmware.

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893

Title:
  TFTP timeout on ARM64 hw when booting from grub that was  PXE loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1509221] Re: wily: arm64: warning in numa_init() during booting

2015-10-25 Thread Ming Lei

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 node property arm, as

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509221

Title:
  wily: arm64: warning in numa_init() during booting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1509221] Re: wily: arm64: warning in numa_init() during booting

2015-10-25 Thread Ming Lei

** 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/1509221

Title:
  wily: arm64: warning in numa_init() during booting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

2015-10-24 Thread Ming Lei

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440536

Title:
  Oops __d_lookup+0x88/0x194

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1509221] [NEW] wily: arm64: warning in numa_init() during booting

2015-10-23 Thread Ming Lei

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-generic 
#19-Ubuntu
[0.00] Hardware name: APM X-Gene Merlin board (DT)
[0.00] Call trace:
[0.00] [] dump_backtrace+0x0/0x178
[0.00] [] show_stack+0x20/0x30
[0.00] [] dump_stack+0x7c/0x98
[0.00] [] warn_slowpath_common+0xa0/0xe0
[0.00] [] warn_slowpath_null+0x38/0x50
[0.00] [] numa_init+0x8c/0x398
[0.00] [] arm64_numa_init+0x30/0x40
[0.00] [] bootmem_init+0x74/0x12c
[0.00] [] paging_init+0x198/0x224
[0.00] [] setup_arch+0x284/0x624
[0.00] [] start_kernel+0xf0/0x424
[0.00] ---[ end trace f24b6c88ae00fa9a ]---

** 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/1509221

Title:
  wily: arm64: warning in numa_init() during booting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508893] Re: TFTP timeout on ARM64 hw when booting from grub that was PXE loaded

2015-10-23 Thread Ming Lei

Dann, I just run a quick test on cvm0 and looks the grub.efi built from wily 
plug the patch just works fine, and
attached my build commandline.

./autogen.sh
./configure --host=x86_64-linux-gnu --target=aarch64-linux-gnu 
--build=x86_64-linux-gnu --with-platform=efi 
--prefix=/tmp/grub64-efi_installed-wily

make -j 24
make -j8 install

cd /tmp/grub64-efi_installed-wily
modules="boot chain configfile configfile efinet ext2 fat gettext help hfsplus 
linux loadenv lsefi normal normal ntfs ntfscomp part_gpt part_msdos part_msdos 
read search search_fs_file search_fs_uuid search_label terminal terminfo tftp"

bin/grub-mkimage -v -o grub.efi -O arm64-efi -p "bootw" $modules

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893

Title:
  TFTP timeout on ARM64 hw when booting from grub that was  PXE loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1509221] Re: wily: arm64: warning in numa_init() during booting

2015-10-23 Thread Ming Lei

** Changed in: linux (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509221

Title:
  wily: arm64: warning in numa_init() during booting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508893] Re: TFTP timeout on ARM64 hw when booting from grub that was PXE loaded

2015-10-23 Thread Ming Lei

Today I have applied this patch(efinet: open Simple Network Protocol 
exclusively) against grub on wily, looks it
does fix the issue on mustang/merlin.

Dann, could you build one upstrem grub and test it on thunder to see if
there is the synchronous exception issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508893

Title:
  TFTP timeout on ARM64 hw when booting from grub that was  PXE loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1507653] [NEW] Wily kernel crashed when running ifconfig eth0 up/done test

2015-10-19 Thread Ming Lei

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' test

#!/bin/sh
for i in $(seq 1 $1); do
echo 'reboot test'$i
sleep 5
ifconfig eth0 down
ifconfig eth0 up
done


3 the issue can be reproduced with upstream 4.3-rcX kernel too



ubuntu@am2:~/git/vm-test$ sudo ./if-down-up 1000
reboot test1
reboot test2
reboot test3
reboot test4
[  4] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60840
[  5] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60841
[  6] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60842
[  7] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60843
[  8] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60844
[  9] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60845
[ 10] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60846
[ 11] local 10.228.66.98 port 5001 connected with 10.228.0.2 port 60847
[  123.244188] Unable to handle kernel paging request at virtual address 
dadaeaeb46463b6b
[  123.252083] pgd = ffc3e955e000
[  123.255467] [dadaeaeb46463b6b] *pgd=, *pud=
[  123.262429] Internal error: Oops: 9604 [#1] PREEMPT SMP
[  123.267973] Modules linked in:
[  123.271023] CPU: 2 PID: 2286 Comm: iperf Not tainted 4.2.3+ #16
[  123.276912] Hardware name: APM X-Gene Mustang board (DT)
[  123.282196] task: ffc3e35a4c80 ti: ffc3e3634000 task.ti: 
ffc3e3634000
[  123.289644] PC is at memcpy+0x20/0x180
[  123.293374] LR is at skb_copy_ubufs+0x134/0x278
[  123.297880] pc : [] lr : [] pstate: 
0145
[  123.305236] sp : ffc3e3637660
[  123.308531] x29: ffc3e3637660 x28: ffc000872269 
[  123.313837] x27: ffc000a6f240 x26: ffc3de92 
[  123.319142] x25: ffc3ecbbca70 x24: 6b6b6b6b6b6b6b6b 
[  123.324446] x23: 006b x22: ffbecfb5bc40 
[  123.329750] x21:  x20: ffc3e3634000 
[  123.335054] x19:  x18: 828d80b9 
[  123.340358] x17:  x16: 0014 
[  123.345663] x15: 000b7d80 x14: 0003 
[  123.350966] x13: 8d7f x12: 000b7d80 
[  123.356270] x11: 8298f2ea x10: ffc3de940a30 
[  123.361574] x9 :  x8 : 0001 
[  123.366876] x7 : ffc000880110 x6 : ffc3ed6f1000 
[  123.372180] x5 : 6b6b6b6b x4 : 0005 
[  123.377483] x3 : 6b6b6b6b6b6b6b6b x2 : 6b6b6b66 
[  123.382788] x1 : dadaeaeb46463b6b x0 : ffc3ed6f1000 
[  123.388093] 
[  123.389575] Process iperf (pid: 2286, stack limit = 0xffc3e3634020)
[  123.396155] Stack: (0xffc3e3637660 to 0xffc3e3638000)
[  123.401871] 7660: e36376e0 ffc3 0053c254 ffc0 de92 ffc3 
0020 
[  123.410006] 7680: de8fa300 ffc3     
0198 
[  123.418141] 76a0: 3300  ec814000 ffc3 0198  
 
[  123.426276] 76c0: 828d80b9  0030  6b6b6b6b 6b6b6b6b 
f79a9900 0020
[  123.434411] 76e0: e3637700 ffc3 0053ffa8 ffc0 de92 ffc3 
de92 ffc3
[  123.442545] 7700: e3637740 ffc3 00540010 ffc0 de92 ffc3 
ed3f1518 ffc3
[  123.450680] 7720: f79a9900 ffc0 ed9dc790 ffc3 ec817300 ffc3 
8145 
[  123.458815] 7740: e3637750 ffc3 0049bc88 ffc0 e36377c0 ffc3 
0054fc24 ffc0
[  123.466950] 7760: de92 ffc3 0042  f79a9180 ffc0 
 
[  123.475084] 7780: f79a9210 ffc0 ed3f0e00 ffc3 009ac0e8 ffc0 
 
[  123.483219] 77a0: de923cc0 ffc3 009ac0f8 ffc0 de92 ffc3 
ecbbc80e 0043
[  123.491353] 77c0: e3637860 ffc3 0056cb18 ffc0 e96f5b00 ffc3 
ed3f0e00 ffc3
[  123.499488] 77e0: de92 ffc3 f79a9180 ffc0 e96f5bac ffc3 
0002 
[  123.507623] 7800:     de8fa370 ffc3 
de8fa300 ffc3
[  123.515757] 7820:   00681bd0 ffc0 008cb95f ffc0 
009ac0f8 ffc0
[  123.523892] 7840: 009ac0e8 ffc0 e36378ac ffc3 e96f5b00 ffc3 
f79a9210 ffc0
[  123.532026] 7860: e36378b0 ffc3 00550104 ffc0 de92 ffc3 
e96f5b00 ffc3
[  123.540161] 7880: f79a9180 ffc0 ed3f0e00 ffc3   
e96f5bac ffc3
[  123.548296] 78a0: de92 ffc3  0010 e3637910 ffc3 
00550320 ffc0
[  123.556430] 78c0: de92 ffc3 f6bf ffc0 000e  
 
[  123.564565] 78e0: f6bf00c8 ffc0 0020  0016fb16  
005c3dd0 ffc0
[

[Bug 1495761] Re: stress-ng --numa 1 causes translation fault on itself on ARM64

2015-09-15 Thread Ming Lei

Looks there are other translation fault issue on arm64, and the following fault 
is triggered when I run
a stress-ng built from your tree just before, and kernel is v4.2.

ubuntu@ubuntu:~/stress-ng$ ./stress-ng --all 8 -t 10
[90392.210285] stress-ng[2513]: unhandled level 3 translation fault (11) at 
0x0072c00c, esr 0x9207
[90392.318907] pgd = ffc0ae2ad000
[90392.359708] [0072c00c] *pgd=0040ed199003, *pud=0040ed199003, 
*pmd=0040e9b0a003, *pte=
[90392.483330] 
[90392.501080] CPU: 3 PID: 2513 Comm: stress-ng Not tainted 4.2.0 #63
[90392.575261] Hardware name: HP ProLiant m400 Server Cartridge (DT)
[90392.648396] task: ffceebdc7080 ti: ffc0e2e38000 task.ti: 
ffc0e2e38000
[90392.738226] PC is at 0x407f70
[90392.773807] LR is at 0x407ea0
[90392.809387] pc : [<00407f70>] lr : [<00407ea0>] pstate: 
8000
[90392.898169] sp : 007fd9016c90
[90392.937922] x29: 007fd9016ca0 x28: 0300 
[90393.001762] x27: 038a x26: 806a 
[90393.065507] x25: 3fc24210 x24: 00449780 
[90393.129361] x23: 038a x22: 00466000 
[90393.193312] x21: 0008 x20: 0066b000 
[90393.257163] x19: 00466000 x18:  
[90393.320909] x17: 007f8be3d1c0 x16: 00465898 
[90393.384759] x15: 000ab9fdd88dad13 x14: 007f8bdc6078 
[90393.448509] x13:  x12: 0030 
[90393.512453] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f 
[90393.576200] x9 : fefefefefefeff64 x8 : 7f7f7f7f7f7f7f7f 
[90393.640046] x7 : 61ff6468616c6e79 x6 :  
[90393.703894] x5 : 0001fa71 x4 : 007fd9016e40 
[90393.767744] x3 : 0018 x2 : 0001 
[90393.831594] x1 : 806a x0 : 0072bff8 
[90393.895340] 
Segmentation fault (core dumped)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495761

Title:
  stress-ng --numa 1 causes translation fault on itself on ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1495761/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1469859] Re: HP ProLiant m400: NULL pointer dereference PC is at ctx_sched_in+0xdc/0x30c

2015-09-14 Thread Ming Lei

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 in just seconds. I'm no longer seeing the NULL
> pointer dereference - or any additional information on the console - but
> that could just be that the console is running too slow. The system no
> longer responds to pings - so I don't believe it is just overloaded.

I can't trigger that on mustang/merlin.

And looks the kernel won't crash too when I run one 4.2 upstream kernel.

But on wily, stress-ng often causes itself translation fault, see the report
below:

https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1495761

Thanks,


>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1469859
>
> Title:
>   HP ProLiant m400: NULL pointer dereference PC is at
>   ctx_sched_in+0xdc/0x30c
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   [Impact]
>   A heavily loaded system can lead to a kernel crash.
>
>   [Test Case]
>   while :; do stress-ng --all 64 -t 600 -v; done
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469859/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469859

Title:
  HP ProLiant m400: NULL pointer dereference PC is at
  ctx_sched_in+0xdc/0x30c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1495761] [NEW] stress-ng --numa 1 causes translation fault on itself on ARM64

2015-09-14 Thread Ming Lei

Public bug reported:

ubuntu@ubuntu:~/stress-ng$ stress-ng --numa 1
stress-ng: info:  [3191] defaulting to a 86400 second run per st[ 1722.813407] 
stress-ng-numa[3192]: unhandled level 2 translation fault (11) at 0x, 
esr 0x9206
ressor
stress-ng: info:  [3191] dispatching hogs: 1 numa
[ 1722.992447] pgd = ffc0cbd5e000
[ 1723.094682] [] *pgd=0040d3713003, *pud=0040d3713003, 
*pmd=
[ 1723.194204] 
[ 1723.211951] CPU: 4 PID: 3192 Comm: stress-ng-numa Not tainted 4.2.0 #63
[ 1723.291343] Hardware name: HP ProLiant m400 Server Cartridge (DT)
[ 1723.364476] task: ffcf49447080 ti: ffc0ecc94000 task.ti: 
ffc0ecc94000
[ 1723.454307] PC is at 0x421d7c
[ 1723.489882] LR is at 0x421d7c
[ 1723.525465] pc : [<00421d7c>] lr : [<00421d7c>] pstate: 
6000
[ 1723.614244] sp : 007fc46205c0
[ 1723.653997] x29: 007fc4624a10 x28: 0400 
[ 1723.717936] x27: 007fc46225d0 x26: 1000 
[ 1723.781784] x25:  x24: 007fc46229f0 
[ 1723.845727] x23: 007fc46205c0 x22: 0046c000 
[ 1723.909572] x21: 007fc4623a00 x20: 007f8daf3000 
[ 1723.973415] x19: 007fc46227e0 x18:  
[ 1724.037260] x17: 007f8e196700 x16: 0046b378 
[ 1724.101113] x15: 0020 x14: 007f8e11fa1c 
[ 1724.165058] x13: 0003e800 x12: 0008 
[ 1724.228798] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f 
[ 1724.292641] x9 : 0004 x8 : 007fc46229e0 
[ 1724.356484] x7 :  x6 : 003f 
[ 1724.420331] x5 : 0040 x4 : ffe0 
[ 1724.484173] x3 : 0020 x2 :  
[ 1724.548023] x1 :  x0 : 007fc46227e0 
[ 1724.611870] 
stress-ng: info:  [3191] successful run completed in 1.82s

** Affects: stress-ng (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/1495761

Title:
  stress-ng --numa 1 causes translation fault on itself on ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1495761/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1473818] Re: vivid kernel can't boot on APM xgene2 Soc

2015-08-09 Thread Ming Lei

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473818

Title:
  vivid kernel can't boot on APM xgene2 Soc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473818/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477431] Re: vivid: ethernet can't work on xgene2 when booting from acpi

2015-07-23 Thread Ming Lei

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477431

Title:
  vivid: ethernet can't work on xgene2 when booting from acpi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477431] [NEW] vivid: ethernet can't work on xgene2 when booting from acpi

2015-07-23 Thread Ming Lei

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 compatibility with the old 
and new firmware
0738c54 drivers: net: xgene: Fix the ACPI support for RGMII/SGMII0/XFI 
interface of APM X-Gene

** 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/1477431

Title:
  vivid: ethernet can't work on xgene2 when booting from acpi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1476512] [NEW] wily: arm64: irqbalance works at oneshot mode at default

2015-07-21 Thread Ming Lei

Public bug reported:


From kernel v4.0, CPU cache topo information is added into sysfs for ARM64,  
in which all cores often share one L3 cache 
such as APM xgene, so cache domain count can be one, and irqbalance will work 
at oneshot mode.

With the following upstream patch, irqbalance can work as before.

https://github.com/Irqbalance/irqbalance/commit/4540a34b728780985041d8432e580d8000589c76

** Affects: irqbalance (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1476512

Title:
  wily: arm64: irqbalance works at oneshot mode at default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1476512/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1476512] [NEW] wily: arm64: irqbalance works at oneshot mode at default

2015-07-21 Thread Ming Lei

Public bug reported:


From kernel v4.0, CPU cache topo information is added into sysfs for ARM64,  
in which all cores often share one L3 cache 
such as APM xgene, so cache domain count can be one, and irqbalance will work 
at oneshot mode.

With the following upstream patch, irqbalance can work as before.

https://github.com/Irqbalance/irqbalance/commit/4540a34b728780985041d8432e580d8000589c76

** Affects: irqbalance (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/1476512

Title:
  wily: arm64: irqbalance works at oneshot mode at default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1476512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-20 Thread Ming Lei

** 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/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-16 Thread Ming Lei

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 configuration from DT
c49b8fc of/pci: Add of_pci_dma_configure() to update DMA configuration
6675a60 PCI: Add helper functions pci_get[put]_host_bridge_device()
0c79c81 of: Fix size when dma-range is not used
1f5c69a of: Move of_dma_configure() to device.c to help re-use
ed74862 of: iommu: Add ptr to OF node arg to of_iommu_configure()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-16 Thread Ming Lei

Dann,

I have figured out patches for fixing wily kernel, see following link:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/comments/4

so you can reproduce the issue on a totally clean wily distribution, :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-16 Thread Ming Lei

Dann,

I have figured out patches for fixing wily kernel, see following link:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/comments/4

so you can reproduce the issue on a totally clean wily distribution, :-)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-15 Thread Ming Lei

From upstrem kernel, v4.0 is same with wily(4.0 kernel), but there isn't the 
issue in v4.1 and v4.2 kernel.

And it can't be found by reverse 'git bisect', because some pci change can 
cause no mellanox nic found
in pci bus.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-15 Thread Ming Lei

From upstrem kernel, v4.0 is same with wily(4.0 kernel), but there isn't the 
issue in v4.1 and v4.2 kernel.

And it can't be found by reverse 'git bisect', because some pci change can 
cause no mellanox nic found
in pci bus.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-15 Thread Ming Lei

** Package changed: irqbalance (Ubuntu) = linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-15 Thread Ming Lei

** Package changed: irqbalance (Ubuntu) = linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-14 Thread Ming Lei

 I prepared a wily package w/ the proposed upstream backport for testing:
   lp:~dannf/ubuntu/wily/irqbalance/lp1469214

 Unfortunately, I'm still seeing irqbalance crash even with this
backport:

I guess you still test irqbalance on c33, looks that upgrade from trusty isn't 
good, and
I can see lots of this kind of falut in different processes(sshd, stress-ng, 
systemd...)
just after a fresh boot with irqbalance disabled(see attachment), and sounds 
like a bad upgrade.


If you verify the patch on trusty/utopic/vivid, it does fix the issue according 
to my tests.

** Attachment added: wily.log
   
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+attachment/4429049/+files/wily.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-14 Thread Ming Lei

 I prepared a wily package w/ the proposed upstream backport for testing:
   lp:~dannf/ubuntu/wily/irqbalance/lp1469214

 Unfortunately, I'm still seeing irqbalance crash even with this
backport:

I guess you still test irqbalance on c33, looks that upgrade from trusty isn't 
good, and
I can see lots of this kind of falut in different processes(sshd, stress-ng, 
systemd...)
just after a fresh boot with irqbalance disabled(see attachment), and sounds 
like a bad upgrade.


If you verify the patch on trusty/utopic/vivid, it does fix the issue according 
to my tests.

** Attachment added: wily.log
   
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+attachment/4429049/+files/wily.log

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-13 Thread Ming Lei

On Mon, Jul 13, 2015 at 9:27 AM, Ming Lei 1469...@bugs.launchpad.net wrote:
 Dann,

 Please follow the steps in #12, in which you should trigger the crash in
 4 minutes.

 I've been running that in a loop and I'm currently on iteration #76
 w/o a crash :(

The issue is nothing to do with kernel, and it should be made sure that 
irqbalance
is running first.

I can reproduce the issue on trusty, utopic and vivid easily with the
approach in #12.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-13 Thread Ming Lei

On Mon, Jul 13, 2015 at 9:27 AM, Ming Lei 1469...@bugs.launchpad.net wrote:
 Dann,

 Please follow the steps in #12, in which you should trigger the crash in
 4 minutes.

 I've been running that in a loop and I'm currently on iteration #76
 w/o a crash :(

The issue is nothing to do with kernel, and it should be made sure that 
irqbalance
is running first.

I can reproduce the issue on trusty, utopic and vivid easily with the
approach in #12.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-13 Thread Ming Lei

 BTW, looks wily kernel can't boot to shell prompt on mcdivitt.

That kernel(v4.0) isn't the final kernel for wily, so do we need to pay
attention to that?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-13 Thread Ming Lei

 BTW, looks wily kernel can't boot to shell prompt on mcdivitt.

That kernel(v4.0) isn't the final kernel for wily, so do we need to pay
attention to that?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-13 Thread Ming Lei

Dann,

Please follow the steps in #12, in which you should trigger the crash in
4 minutes.

BTW, looks wily kernel can't boot to shell prompt on mcdivitt.

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-13 Thread Ming Lei

Dann,

Please follow the steps in #12, in which you should trigger the crash in
4 minutes.

BTW, looks wily kernel can't boot to shell prompt on mcdivitt.

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] [NEW] Wily boot failure on HP proliant m400 server

2015-07-13 Thread Ming Lei

Public bug reported:


Looks kernel crashs inside mlx4_en_xmit() of mlx ethernet driver.

** Affects: irqbalance (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/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-13 Thread Ming Lei

** Attachment added: dmesg during boot
   
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+attachment/4428465/+files/hp-ProLiant-m400.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474171] [NEW] Wily boot failure on HP proliant m400 server

2015-07-13 Thread Ming Lei

Public bug reported:


Looks kernel crashs inside mlx4_en_xmit() of mlx ethernet driver.

** Affects: irqbalance (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1474171] Re: Wily boot failure on HP proliant m400 server

2015-07-13 Thread Ming Lei

** Attachment added: dmesg during boot
   
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+attachment/4428465/+files/hp-ProLiant-m400.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1474171/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1473818] [NEW] vivid kernel can't boot on APM xgene2 Soc

2015-07-12 Thread Ming Lei

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) ) #73 SMP PREEMPT Sun Jul 12 23:01:21 EDT 2015 ()
CPU: AArch64 Processor [501f] revision 0
Detected PIPT I-cache on CPU0
Early serial console at MMIO32 0x1060 (options '')
bootconsole [uart0] enabled
Memory limited to 16384MB
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
On node 0 totalpages: 4194304
  DMA zone: 16384 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 1048576 pages, LIFO batch:31
  Normal zone: 49152 pages used for memmap
  Normal zone: 3145728 pages, LIFO batch:31
PERCPU: Embedded 13 pages/cpu @ffc3fff51000 s13312 r8192 d31744 u53248
pcpu-alloc: s13312 r8192 d31744 u53248 alloc=13*4096
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 4128768
Kernel command line: root=/dev/sda1 rw rootfstype=ext4 loglevel=9 
console=ttyS0,115200 earlycon=uart8250,mmio32,0x1060 mem=16G 
console=ttyS0,115200 earlyprintk=uart8250-32bit,0x1060 debug maxcpus=8
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Memory: 16480552K/16777216K available (5330K kernel code, 371K rwdata, 1920K 
rodata, 256K init, 1198K bss, 296664K reserved, 0K cma-reserved)
Virtual kernel memory layout:
vmalloc : 0xff80 - 0xffbdbfff   (   246 GB)
vmemmap : 0xffbdc000 - 0xffbfc000   ( 8 GB maximum)
  0xffbec000 - 0xffbed000   (   256 MB actual)
PCI I/O : 0xffbffa00 - 0xffbffb00   (16 MB)
fixed   : 0xffbffbdfd000 - 0xffbffbdff000   ( 8 KB)
modules : 0xffbffc00 - 0xffc0   (64 MB)
memory  : 0xffc0 - 0xffc4   ( 16384 MB)
  .init : 0xffc000797000 - 0xffc0007d7000   (   256 KB)
  .text : 0xffc8 - 0xffc000796934   (  7259 KB)
  .data : 0xffc0007db000 - 0xffc000837c00   (   371 KB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Preemptible hierarchical RCU implementation.
Additional per-CPU info printed with stalls.
NR_IRQS:64 nr_irqs:64 0
Architected cp15 timer(s) running at 50.00MHz (phys).
sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns
Console: colour dummy device 80x25
Calibrating delay loop (skipped), value calculated using timer frequency.. 
100.00 BogoMIPS (lpj=50)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 5 counters available
EFI services will not be available.

** 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/1473818

Title:
  vivid kernel can't boot on APM xgene2 Soc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473818/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port

2015-07-09 Thread Ming Lei

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/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Link detected: no


** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458042

Title:
  [SRU] xgene-enet: add SGMII based 1GbE support for the second port

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

2015-07-09 Thread Ming Lei

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 with 10.228.0.2 port 5001
[  4] local 10.228.66.98 port 59717 connected with 10.228.0.2 port 5001
[  3] local 10.228.66.98 port 59715 connected with 10.228.0.2 port 5001
[  5] local 10.228.66.98 port 59716 connected with 10.228.0.2 port 5001
[  6] local 10.228.66.98 port 59718 connected with 10.228.0.2 port 5001
[  7] local 10.228.66.98 port 59719 connected with 10.228.0.2 port 5001
[  9] local 10.228.66.98 port 59721 connected with 10.228.0.2 port 5001
[  8] local 10.228.66.98 port 59720 connected with 10.228.0.2 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-120.0 sec  1.71 GBytes   122 Mbits/sec
[  7]  0.0-120.0 sec  1.64 GBytes   117 Mbits/sec
[  4]  0.0-120.0 sec  1.56 GBytes   112 Mbits/sec
[  5]  0.0-120.0 sec  1.54 GBytes   110 Mbits/sec
[ 10]  0.0-120.0 sec  1.70 GBytes   121 Mbits/sec
[  6]  0.0-120.0 sec  1.71 GBytes   123 Mbits/sec
[  9]  0.0-120.0 sec  1.72 GBytes   123 Mbits/sec
[  8]  0.0-120.0 sec  1.58 GBytes   113 Mbits/sec
[SUM]  0.0-120.0 sec  13.2 GBytes   942 Mbits/sec
ubuntu@am2:~$ uname -aa
Linux am2 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 03:00:52 UTC 2015 aarch64 
aarch64 aarch64 GNU/Linux


** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425576

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

2015-07-09 Thread Ming Lei

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 -P 8 -t 120

Client connecting to 10.229.0.101, TCP port 5001
TCP window size: 85.0 KByte (default)

[ 10] local 10.229.65.140 port 48807 connected with 10.229.0.101 port 5001
[  5] local 10.229.65.140 port 48802 connected with 10.229.0.101 port 5001
[  3] local 10.229.65.140 port 48801 connected with 10.229.0.101 port 5001
[  4] local 10.229.65.140 port 48800 connected with 10.229.0.101 port 5001
[  6] local 10.229.65.140 port 48803 connected with 10.229.0.101 port 5001
[  7] local 10.229.65.140 port 48804 connected with 10.229.0.101 port 5001
[  8] local 10.229.65.140 port 48806 connected with 10.229.0.101 port 5001
[  9] local 10.229.65.140 port 48805 connected with 10.229.0.101 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-120.0 sec  3.46 GBytes   247 Mbits/sec
[  5]  0.0-120.0 sec   192 MBytes  13.4 Mbits/sec
[  6]  0.0-120.0 sec  2.94 GBytes   210 Mbits/sec
[  7]  0.0-120.0 sec  2.83 GBytes   203 Mbits/sec
[  8]  0.0-120.0 sec  3.19 GBytes   228 Mbits/sec
[  9]  0.0-120.0 sec   192 MBytes  13.4 Mbits/sec
[ 10]  0.0-120.1 sec   191 MBytes  13.3 Mbits/sec
[  4]  0.0-120.1 sec   191 MBytes  13.3 Mbits/sec
[SUM]  0.0-120.1 sec  13.2 GBytes   942 Mbits/sec


** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425576

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-08 Thread Ming Lei

** Description changed:

- Running stress-ng on a HP ProLiant m400 server can cause unhandled level
- 3 translations faults:
+ 
+ [Impact]
+ irqbalance can be crashed(got signal of segment fault) on trusty, utopic, 
vivid and wily.
+ 
+ [Test Case]
+ stress-ng --seq 0 -t 60 --syslog --metrics --times -v
+ 
+ [Regression Potential]
+ The proposed patch has been merged irqbalance upstream 1.0.7, so there 
shouldn't be potential regression.
+ 
+ 
https://github.com/Irqbalance/irqbalance/commit/a3c812eb6cd627cd3fae45b8345538558b86973c
+ 
+ 
+ [Other Info]
+ 
+ See following about the segmentation fault log.
+ 
+ 
+ 
+ 
+ Running stress-ng on a HP ProLiant m400 server can cause unhandled level 3 
translations faults:
  
  use stress-ng from git://kernel.ubuntu.com/cking/stress-ng
  
  ./stress-ng --seq 0 -t 60 -v
  
  and after some time this trips the following:
  
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922560] 
systemd-timesyn[481]: unhandled level 3 translation fault (7) at 0x7fa8ea6008, 
esr 0x9207
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922561] pgd = 
ffcfb563f000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922563] [7fa8ea6008] 
*pgd=004fb4f28003, *pud=004fb4f28003, *pmd=004fb4f38003, 
*pte=1d151c00
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922566]
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922569] CPU: 6 PID: 481 
Comm: systemd-timesyn Not tainted 3.19.0-21-generic #21-Ubuntu
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922571] Hardware name: HP 
ProLiant m400 Server Cartridge (DT)
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922573] task: 
ffcfb4e3b100 ti: ffcfb4d2c000 task.ti: ffcfb4d2c000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922588] PC is at 0x7fa8d81824
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922589] LR is at 0x7fa8e3b3e4
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922590] pc : 
[007fa8d81824] lr : [007fa8e3b3e4] pstate: 8000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922591] sp : 007ff120d660
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922592] x29: 
007ff120d660 x28: 007fa8f1c000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922594] x27: 
007fa8f32084 x26: 007fa8f32000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922595] x25: 
007fa8f1d788 x24: 007fa8f1d888
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922597] x23: 
0001 x22: 007fa8f1faa0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922599] x21: 
007ff120d7f0 x20: 007ff120d7d0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922600] x19: 
007fa8f31000 x18: 007fa8f1e000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922602] x17: 
007fa8e3b3b8 x16: 007fa8ea6000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922603] x15: 
003b9aca x14: 00219bbdd000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922605] x13: 
aa751223 x12: 
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922607] x11: 
0101010101010101 x10: 7f7f7f7f7f7f7f7f
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922609] x9 : 
37333c43484f5e46 x8 : 007ff120d818
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922610] x7 : 
007ff120d8f0 x6 : 007ff120d828
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922612] x5 : 
ff80ffd0 x4 : 007ff120d8c0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922613] x3 : 
007ff120d7d0 x2 : 007fa8f1faa0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922615] x1 : 
0001 x0 : 0064
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922616]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-08 Thread Ming Lei

** Description changed:

- Running stress-ng on a HP ProLiant m400 server can cause unhandled level
- 3 translations faults:
+ 
+ [Impact]
+ irqbalance can be crashed(got signal of segment fault) on trusty, utopic, 
vivid and wily.
+ 
+ [Test Case]
+ stress-ng --seq 0 -t 60 --syslog --metrics --times -v
+ 
+ [Regression Potential]
+ The proposed patch has been merged irqbalance upstream 1.0.7, so there 
shouldn't be potential regression.
+ 
+ 
https://github.com/Irqbalance/irqbalance/commit/a3c812eb6cd627cd3fae45b8345538558b86973c
+ 
+ 
+ [Other Info]
+ 
+ See following about the segmentation fault log.
+ 
+ 
+ 
+ 
+ Running stress-ng on a HP ProLiant m400 server can cause unhandled level 3 
translations faults:
  
  use stress-ng from git://kernel.ubuntu.com/cking/stress-ng
  
  ./stress-ng --seq 0 -t 60 -v
  
  and after some time this trips the following:
  
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922560] 
systemd-timesyn[481]: unhandled level 3 translation fault (7) at 0x7fa8ea6008, 
esr 0x9207
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922561] pgd = 
ffcfb563f000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922563] [7fa8ea6008] 
*pgd=004fb4f28003, *pud=004fb4f28003, *pmd=004fb4f38003, 
*pte=1d151c00
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922566]
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922569] CPU: 6 PID: 481 
Comm: systemd-timesyn Not tainted 3.19.0-21-generic #21-Ubuntu
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922571] Hardware name: HP 
ProLiant m400 Server Cartridge (DT)
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922573] task: 
ffcfb4e3b100 ti: ffcfb4d2c000 task.ti: ffcfb4d2c000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922588] PC is at 0x7fa8d81824
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922589] LR is at 0x7fa8e3b3e4
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922590] pc : 
[007fa8d81824] lr : [007fa8e3b3e4] pstate: 8000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922591] sp : 007ff120d660
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922592] x29: 
007ff120d660 x28: 007fa8f1c000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922594] x27: 
007fa8f32084 x26: 007fa8f32000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922595] x25: 
007fa8f1d788 x24: 007fa8f1d888
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922597] x23: 
0001 x22: 007fa8f1faa0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922599] x21: 
007ff120d7f0 x20: 007ff120d7d0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922600] x19: 
007fa8f31000 x18: 007fa8f1e000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922602] x17: 
007fa8e3b3b8 x16: 007fa8ea6000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922603] x15: 
003b9aca x14: 00219bbdd000
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922605] x13: 
aa751223 x12: 
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922607] x11: 
0101010101010101 x10: 7f7f7f7f7f7f7f7f
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922609] x9 : 
37333c43484f5e46 x8 : 007ff120d818
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922610] x7 : 
007ff120d8f0 x6 : 007ff120d828
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922612] x5 : 
ff80ffd0 x4 : 007ff120d8c0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922613] x3 : 
007ff120d7d0 x2 : 007fa8f1faa0
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922615] x1 : 
0001 x0 : 0064
  Jun 26 14:01:54 ms10-34-proliant kernel: [150297.922616]

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault

2015-07-07 Thread Ming Lei

On Tue, Jul 7, 2015 at 11:16 AM, Ming Lei ming@canonical.com 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 choose to use its own local glib if there isn't glib2 
 available,
 and the glib2 does exist in my server in which I build irqbalance.


Both of two above reports can be fixed by the following irqbalance commit:

NUMA is not available fix

https://github.com/Irqbalance/irqbalance/commit/a3c812eb6cd627cd3fae45b8345538558b86973c

Looks stress-ng can't only find kernel bug, but also userspace
issue, :-)

Thanks,
Ming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469214

Title:
  HP ProLiant m400 Server crashes with unhandled level 3 translation
  fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1296665] Re: irqbalance crashed with SIGSEGV in __libc_start_main()

2015-07-07 Thread Ming Lei

*** This bug is a duplicate of bug 1469214 ***
https://bugs.launchpad.net/bugs/1469214

** This bug is no longer a duplicate of bug 1183374
   irqbalance crashed with SIGSEGV in place_irq_in_node()
** This bug has been marked a duplicate of bug 1469214
   HP ProLiant m400 Server crashes with unhandled level 3 translation fault

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1296665

Title:
  irqbalance crashed with SIGSEGV in __libc_start_main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1296665/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

1 2 3 4 5 6 7 >

1 - 100 of 692 matches

Mail list logo