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

[Ming Lei]

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

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

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  CONFIG_ARM64_ERRATUM_845719 should have been enabled in Yakkety, but
  it isn't actually.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1647793

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CONFIG_ARM64_ERRATUM_845719 should have been enabled in Yakkety, but
  it isn't actually.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1647793

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  CONFIG_ARM64_ERRATUM_845719 should be enabled in Yakkety, but it isn't.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

On Thu, Nov 3, 2016 at 5:42 AM, Kamal Mostafa  wrote:
> Ming Lei comment #2 says you're the author of this patch to the hio
> driver:
>
> +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
> +   blk_queue_split(q, &bio, q->bio_split);
> +#endif
> +
>
> 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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&

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

[Ming Lei]

On Tue, May 17, 2016 at 12:12 PM, Ming Lei  wrote:
> On Mon, May 16, 2016 at 5:25 PM, Ming Lei  wrote:
>> On Fri, May 13, 2016 at 7:22 AM, dann frazier
>>  wrote:
>>> I used ftrace to do some duration measuring of the timer function
>>> fb_flashcursor(). I 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(&base->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: 801f667d9800 x22: 804ec4c0
>>&

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

[Ming Lei]

On Mon, May 16, 2016 at 5:25 PM, Ming Lei  wrote:
> On Fri, May 13, 2016 at 7:22 AM, dann frazier
>  wrote:
>> I used ftrace to do some duration measuring of the timer function
>> fb_flashcursor(). I noticed several places where this timer takes around
>> 98 ms to 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(&base->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 : 
>>   [ 84.922837] x5 :

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

[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(&base->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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux 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) thunde

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux 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] x

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

[Ming Lei]

On Tue, May 3, 2016 at 10:35 AM, dann frazier
 wrote:
> On Fri, Apr 29, 2016 at 2:06 AM, Ming Lei <1574...@bugs.launchpad.net> wrote:
>> It can be triggered 100% by running 'tcpdump -I ethX'.
>
> Thanks Ming. I let that run for a few hours, but was unable to
> 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux 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] x

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

[Ming Lei]

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

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

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 
> 
>   [   93.309274] 

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

[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 
Date:   Wed Dec 2 07:28:37 2015 -0700

UBUNTU: SAUCE: AUFS

Signed-off-by: Tim Gardner 

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

Thanks,

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 000

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

[Ming Lei]

Upstream 4.6-rc6 hasn't this problem

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

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 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 

  [   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] Intern

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

[Ming Lei]

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

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

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer 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 

  [   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=

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1575506

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

Status in linux package in Ubuntu:
  Incomplete

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 

  [   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=
 

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

[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 

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553934

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

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553934

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

Status in linux package in Ubuntu:
  New

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548207

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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 c

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548207

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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]

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

[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 0

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

[Ming Lei]

On Mon, Feb 22, 2016 at 4:37 PM, Ming Lei  wrote:
> Looks it is enough to just revert
> 'e96e20134729121689a0089537c6ed(module: clean up RO/NX handling)'
> for fixing the issue.
>
> But the interesting thing is that there isn't the problem in upstream kernel
> 4.5-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  
> 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 
>> 0

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

[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:  cb88537fdc8ba602 fff

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548207

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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:  

[Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Confirmed
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/gcc-linaro/+bug/1533009/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

Status in gcc-5 package in Ubuntu:
  Confirmed
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

[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 Kernel
Packages, which is 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

[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 Kernel
Packages, which is 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:
  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/gcc-5/+bug/1533009/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

[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  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  [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
>>
>

Re: [Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

[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 Kernel
Packages, which is 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507653

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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 

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

[Ming Lei]

On Tue, Oct 27, 2015 at 11:03 PM, Fathi Boudra  wrote:
> Ming Lei,
>
> yes, on Mustang. We're using U-Boot.

OK, we found the issue is triggered during booting, and finally
APM's fix on firmware can make the issue disappeared, but
it isn't released yet.

>
> --
> 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 Kernel
Packages, which is 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509221

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [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 ]---

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [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 ]---

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  [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 ]---

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509221

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [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 ]---

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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
[  123.572699]

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469859

Title:
  HP ProLiant m400: NULL pointer dereference PC is at
  ctx_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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

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

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1477431

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

Status in linux package in Ubuntu:
  Invalid

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1477431

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

Status in linux package in Ubuntu:
  New

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

Title:
  Wily boot failure on HP proliant m400 server

Status in linux package in Ubuntu:
  Confirmed

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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1474171

Title:
  Wily boot failure on HP proliant m400 server

Status in linux package in Ubuntu:
  Incomplete

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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

Title:
  Wily boot failure on HP proliant m400 server

Status in linux package in Ubuntu:
  Incomplete

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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1473818

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

Status in linux package in Ubuntu:
  New

Bug description:
  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/167772

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1425576

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  System panics every few hours under constant network load

  [Test Case]
  On the X-Gene system, start an iperf server:
$ iperf -s
  Connect to it from another system (1Gbps is sufficient)
$ iperf -t 10 -c 

  On failure, you'll get a panic within several hours.

  [Regression Risk]
  The proposed patch only touches the impacted driver. It is adding a memory 
barrier - albeit a lightweight one - so there is the risk of a performance 
degradation. Indeed, when measured using a 60s iperf run, I do see a 
performance drop, but by < 0.5%.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1425576

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  System panics every few hours under constant network load

  [Test Case]
  On the X-Gene system, start an iperf server:
$ iperf -s
  Connect to it from another system (1Gbps is sufficient)
$ iperf -t 10 -c 

  On failure, you'll get a panic within several hours.

  [Regression Risk]
  The proposed patch only touches the impacted driver. It is adding a memory 
barrier - albeit a lightweight one - so there is the risk of a performance 
degradation. Indeed, when measured using a 60s iperf run, I do see a 
performance drop, but by < 0.5%.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1458042

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

** Changed in: irqbalance (Ubuntu Vivid)
   Status: In Progress => Confirmed

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

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

Status in irqbalance package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in irqbalance source package in Trusty:
  New
Status in linux source package in Trusty:
  Invalid
Status in irqbalance source package in Utopic:
  New
Status in linux source package in Utopic:
  Invalid
Status in irqbalance source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Invalid
Status in irqbalance source package in Wily:
  New
Status in linux source package in Wily:
  Invalid

Bug description:
  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]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

On Tue, Jul 7, 2015 at 11:16 AM, Ming Lei  wrote:
> Looks there are two kinds of translation fault from irqbalance:
>
> 1) happend in place_irq_in_node() which can reproduce in vivid package
>
> 2) the 2nd one happened in glib2, which  is built by myself, because
> irqbalance can 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469214

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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.

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

On Tue, Jul 7, 2015 at 2:37 AM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> captured irqbalance segfaulting:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00408f8c in place_irq_in_node (info=0x2c3d0050, data=0x0) at 
> placement.c:145
> 145 if (irq_numa_node(info)->number != -1) {
> (gdb) where
> #0  0x00408f8c in place_irq_in_node (info=0x2c3d0050, data=0x0) at 
> placement.c:145
> #1  0x00405154 in for_each_irq (list=0x2c3df660, cb=0x408f4c 
> , data=0x0)
> at classify.c:508
> #2  0x0040923c in calculate_placement () at placement.c:196
> #3  0x00407800 in main (argc=2, argv=0x7fcd014928) at irqbalance.c:372
>
> (gdb) print info
> $1 = (struct irq_info *) 0x2c3d0050

Suppose info is one address in heap, then it is valid, and the segfault
should be caused by invalid info->numa_node.

Thanks

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1469214
>
> Title:
>   HP ProLiant m400 Server crashes with unhandled level 3 translation
>   fault
>
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   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]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469214/+subscriptions

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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

  ./str

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

[Ming Lei]

On Mon, Jul 6, 2015 at 9:28 PM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> I re-ran this today with the following script as a non-root user:
>
> #!/bin/bash
> tests="affinity aio bigheap brk bsearch cache chdir chmod clock context cpu 
> crypt dentry dir dup epoll eventfd fstat fallocate fault fifo flock fork 
> futex get getrandom hdd hsearch inotify io itimer kcmp kill lease link lockf 
> longjmp lsearch malloc matrix memcpy memfd mincore mlock mmap mmapmany mremap 
> msg mq nice null open pipe poll procfs pthread qsort readahead rename rlimit 
> seek sem sem-sysv sendfile shm-sysv sigfd sigfpe sigq sigsegv sock splice 
> stack str switch symlink sysinfo sysfs tee timer timerfd tsearch udp 
> udp-flood urandom utime vecmath vfork vm vm-rw vm-splice wcs wait yield xattr 
> zero zombie"
>
> for t in $tests
> do
> echo $t
> echo $t | sudo tee /dev/kmsg
> ./stress-ng --$t 0 -v -t 60
> done
>
> and hit this issue:
>
> [14098.848615] urandom
> [14111.696335] irqbalance[828]: unhandled level 2 translation fault (11) at 
> 0x4f64, esr 0x9206
> [14111.696341] pgd = ffcfef71b000
> [14111.737149] [4f64] *pgd=004fef1f3003, *pud=004fef1f3003, 
> *pmd=
>

As I suggested, it should be helpful to provide /proc/$(pidof
irqbalance)/maps, otherwise we can't know where both the faulted
and PC address are.

Finally I have figured out one simple way to reproduce the issue:

1) apply the attached debug patch to stress-ng

2) run the following script:

sudo cat /proc/$(pidof irqbalance)/maps
/home/ubuntu/git/stress-ng/stress-ng --sequential 0 --seq-start 80
--seq-end 84 -t 60 --syslog --metrics --times -v

And the above command just runs the following 4 stresses in 4 minutes:

stress-ng: info:  [1067] dispatching hogs: 8 tsearch, 8 udp, 8 udp-flood,
8  urandom

3) the above may trigger the following faults from irqbalance with
~3/4 probability, and the faulted address is in heap, and PC points to
code of libglib-2.0.so, so looks like a use-after-free in irqbalance or
libglib? And no information shows it is related with kernel, also
the four stresses are quite simple and shouldn't cause trouble to
kernel.


# irqbalance memory maps
0040-0040a000 r-xp  08:02 10496929
  /usr/sbin/irqbalance
00419000-0041a000 r-xp 9000 08:02 10496929
  /usr/sbin/irqbalance
0041a000-0041b000 rwxp a000 08:02 10496929
  /usr/sbin/irqbalance
16294000-162b5000 rwxp  00:00 0  [heap]
162b5000-162ce000 rwxp  00:00 0  [heap]
7f8fbf9000-7f8fbfb000 rwxp  00:00 0
7f8fbfb000-7f8fc11000 r-xp  08:02 4722034
  /lib/aarch64-linux-gnu/libpthread-2.21.so
7f8fc11000-7f8fc2 ---p 00016000 08:02 4722034
  /lib/aarch64-linux-gnu/libpthread-2.21.so
7f8fc2-7f8fc21000 r-xp 00015000 08:02 4722034
  /lib/aarch64-linux-gnu/libpthread-2.21.so
7f8fc21000-7f8fc22000 rwxp 00016000 08:02 4722034
  /lib/aarch64-linux-gnu/libpthread-2.21.so
7f8fc22000-7f8fc26000 rwxp  00:00 0
7f8fc26000-7f8fc7f000 r-xp  08:02 4718668
  /lib/aarch64-linux-gnu/libpcre.so.3.13.1
7f8fc7f000-7f8fc8f000 ---p 00059000 08:02 4718668
  /lib/aarch64-linux-gnu/libpcre.so.3.13.1
7f8fc8f000-7f8fc9 r-xp 00059000 08:02 4718668
  /lib/aarch64-linux-gnu/libpcre.so.3.13.1
7f8fc9-7f8fc91000 rwxp 0005a000 08:02 4718668
  /lib/aarch64-linux-gnu/libpcre.so.3.13.1
7f8fc91000-7f8fdc1000 r-xp  08:02 4722027
  /lib/aarch64-linux-gnu/libc-2.21.so
7f8fdc1000-7f8fdd ---p 0013 08:02 4722027
  /lib/aarch64-linux-gnu/libc-2.21.so
7f8fdd-7f8fdd4000 r-xp 0012f000 08:02 4722027
  /lib/aarch64-linux-gnu/libc-2.21.so
7f8fdd4000-7f8fdd6000 rwxp 00133000 08:02 4722027
  /lib/aarch64-linux-gnu/libc-2.21.so
7f8fdd6000-7f8fdda000 rwxp  00:00 0
7f8fdda000-7f8fde3000 r-xp  08:02 10885206
  /usr/lib/aarch64-linux-gnu/libnuma.so.1.0.0
7f8fde3000-7f8fdf2000 ---p 9000 08:02 10885206
  /usr/lib/aarch64-linux-gnu/libnuma.so.1.0.0
7f8fdf2000-7f8fdf3000 r-xp 8000 08:02 10885206
  /usr/lib/aarch64-linux-gnu/libnuma.so.1.0.0
7f8fdf3000-7f8fdf4000 rwxp 9000 08:02 10885206
  /usr/lib/aarch64-linux-gnu/libnuma.so.1.0.0
7f8fdf4000-7f8fdf8000 rwxp  00:00 0
7f8fdf8000-7f8fe89000 r-xp  08:02 4722041
  /lib/aarch64-linux-gnu/libm-2.21.so
7f8fe89000-7f8fe98000 ---p 00091000 08:02 4722041
  /lib/aarch64-linux-gnu/libm-2.21.so
7f8fe98000-7f8fe99000 r-xp 0009 08:02 4722041
  /lib/aarch64-linux-gnu/libm-2.21.so
7f8fe99000-7f8fe9a000 rwxp 00091000 08:02 4722041
  /lib/aarch64-linux-gnu/libm-2.21.so
7f8fe9a000-7f8ff8c000 r-xp  08:02 4718610
  /lib/aarch64-linux-gnu/libglib-2.0.so.0.4400.1
7f8ff8c000-7f8ff9c000 ---p 000f2000 08:02 4718610
  /lib/aarch64-linux-gnu/libglib-2.0.so.0.4400.1
7f8ff9c000-7f8ff9d000 r-xp 000f2000 08:02 4718610
  /lib/aarch64-linux-gnu/libglib-2.0.so.0.4400.1
7f8ff9d000-7f8ff9e000 rwxp 000f3000 08:02 4718610
  /lib/aarch64-linux-gnu/libglib-2.0.

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

[Ming Lei]

Hi Colin,

On Sat, Jul 4, 2015 at 12:43 AM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> I was able to hit the following translation fault running sudo ./stress-
> ng --seq 0 -t 60 --syslog --metrics --times -v

I suggest to not run stress-ng as root, otherwise it can be less
serious because:

  - root user can do bad things easily, and it is quite easy to kill any
of process
  - in reality most of loads are run as non-root

If some system processes(irqbalance, systemd-*) are only killed
becasue stress-ng is running as root, it can be a low priority issue.
Otherwise we need pay close attention to the issue.

And I always run 'stress-ng' as ubuntu user without sudo, that may
be the reason why it is difficult for me to reproduce that.

Even with the two new approaches, it is still not easy for me to
reproduce that. I only see one time of translation fault by your
first approach(./stress-ng --seq 0 ...)  in 6 hours, and can't trigger
that with your 2nd approach(by bash script).

Folllows the log[1] I triggered, and I think it is very likely a userspace
issue. From irqbalanc-dbgsym package, we can easily find 'PC is at
0x406078' is one address in text section, and it should be inside
function of 'place_irq_in_node' because the exec file isn't built as
relocation. One thing I still can't understand is that why the fault
address is '0x0040' in the context.


[1]
[ 3616.92] Bits 55-60 of /proc/PID/pagemap entries are about to
stop being page-shift some time soon. See the
linux/Documentation/vm/pagemap.txt for details.
[ 3616.93] Bits 55-60 of /proc/PID/pagemap entries are about to
stop being page-shift some time soon. See the
linux/Documentation/vm/pagemap.txt for details.
[ 5316.367265] irqbalance[1457]: unhandled level 2 translation fault
(11) at 0x0040, esr 0x9206
[ 5316.476937] pgd = ffcfb5478000
[ 5316.520692] [0040] *pgd=004fb4a3c003,
*pud=004fb4a3c003, *pmd=
[ 5316.620270]
[ 5316.638140] CPU: 7 PID: 1457 Comm: irqbalance Not tain-21-generic #21-Ubuntu
[ 5316.733212] Hardware name: HP ProLiant m400 Server Cartridge (DT)
[ 5316.806382] task: ffcfb55e6e40 ti: ffcfa72b task.ti:
ffcfa72b
[ 5316.896258] PC is at 0x406078
[ 5316.931865] LR is at 0x404100
[ 5316.967457] pc : [<00406078>] lr : [<00404100>]
pstate: 2000
[ 5317.056268] sp : 007fc07ff2d0
[ 5317.096038] x29: 007fc07ff2d0 x28: 004095a0
[ 5317.160023] x27: 00409548 x26: 0041a000
[ 5317.223897] x25: 00405000 x24: 0041acf8
[ 5317.287868] x23: 0041a000 x22: 0041a000
[ 5317.351841] x21: 2e0d6050 x20: 0041a000
[ 5317.415744] x19: 2e0e9020 x18: 
[ 5317.479620] x17: 007fb5ac287c x16: 0041a188
[ 5317.543490] x15: 003bdd2370f74a1c x14: 2030203020302030
[ 5317.607373] x13: 2030203020302030 x12: 2030203020302030
[ 5317.671263] x11: 2030203020302030 x10: 2030203020302030
[ 5317.735137] x9 : 00a0 x8 : 0001
[ 5317.799113] x7 : 0033 x6 : 2e0d6e08
[ 5317.862983] x5 : 0040 x4 : 
[ 5317.926867] x3 : 2e0d7008 x2 : 
[ 5317.990840] x1 : 002c x0 : 0003
[ 5318.054713]

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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 

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

[Ming Lei]

Hi Colin,

That looks one progress, but still takes time to reproduce that,
and I will use your new approach to reproduce that.

When you are doing that, could you dump the file of /proc/$(pidof
irqbalance)/maps so that we can see where the faulted address are
in the process's vm space?

thanks,


On Sat, Jul 4, 2015 at 4:10 AM, Colin Ian King
<1469...@bugs.launchpad.net> wrote:
> Running the following:
>
> #!/bin/bash
> tests="affinity aio bigheap brk bsearch cache chdir chmod clock context cpu 
> crypt dentry dir dup epoll eventfd fstat fallocate fault fifo flock fork 
> futex get getrandom hdd hsearch inotify io itimer kcmp kill lease link lockf 
> longjmp lsearch malloc matrix memcpy memfd mincore mlock mmap mmapmany mremap 
> msg mq nice null open pipe poll procfs pthread qsort readahead rename rlimit 
> seek sem sem-sysv sendfile shm-sysv sigfd sigfpe sigq sigsegv sock splice 
> stack str switch symlink sysinfo sysfs tee timer timerfd tsearch udp 
> udp-flood urandom utime vecmath vfork vm vm-rw vm-splice wcs wait yield xattr 
> zero zombie"
>
> for t in $tests
> do
> echo $t
> echo $t > /dev/kmsg
> ./stress-ng --$t 0 -v -t 60
> done
>
> eventually tripped the translation fault in irqbalance.  I ran this
> after a clean reboot.
>
> [ 4901.799846] timerfd
> [ 4961.807050] tsearch
> [ 5021.884456] udp
> [ 5081.895058] udp-flood
> [ 5141.674365] irqbalance[827]: unhandled level 2 translation fault (11) at 
> 0x002d6da4, esr 0x9206
> [ 5141.674376] pgd = ffcfb51a
> [ 5141.715215] [002d6da4] *pgd=004fb677e003, *pud=004fb677e003, 
> *pmd=
>
> [ 5141.816183] CPU: 0 PID: 827 Comm: irqbalance Not tainted 3.19.0-21-generic 
> #21-Ubuntu
> [ 5141.816185] Hardware name: HP ProLiant m400 Server Cartridge (DT)
> [ 5141.816188] task: ffcfac088000 ti: ffcfab71 task.ti: 
> ffcfab71
> [ 5141.816206] PC is at 0x7f88287834
> [ 5141.816208] LR is at 0x7f882877f4
> [ 5141.816210] pc : [<007f88287834>] lr : [<007f882877f4>] pstate: 
> 8000
> [ 5141.816212] sp : 007ff2e46b30
> [ 5141.816214] x29: 007ff2e46b30 x28: 004095a0
> [ 5141.816217] x27: 00409548 x26: 0041a000
> [ 5141.816220] x25: 0001 x24: 0010
> [ 5141.816222] x23: 2d6c98a0 x22: 2d6c9880
> [ 5141.816225] x21: 0018 x20: 007f88323000
> [ 5141.816228] x19: 0002 x18: 
> [ 5141.816230] x17: 007f87f8d8ec x16: 007f883222e0
> [ 5141.816233] x15: 0020 x14: 0001
> [ 5141.816235] x13:  x12: 
> [ 5141.816237] x11: 007ff2e446a0 x10: 0010
> [ 5141.816240] x9 : 00a0 x8 : 0007
> [ 5141.816242] x7 : 0033 x6 : 2d6c9c80
> [ 5141.816245] x5 : 0001 x4 : 007f87fa62a0
> [ 5141.816247] x3 : 2d6c9880 x2 : 0001
> [ 5141.816250] x1 : 03fa x0 : 002d6d9c
>
> [ 5141.907792] urandom
> [ 5201.928712] utime
> [ 5261.934534] vecmath
> [ 5321.940302] vfork
> [ 5381.947904] vm
> [ 5441.991784] vm-rw
> [ 5502.017614] vm-splice
> [ 5562.023334] wcs
> [ 5622.037054] wait
> [ 5682.043302] yield
> [ 5742.056595] xattr
> [ 5802.075772] zero
> [ 5862.087396] zombie
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1469214
>
> Title:
>   HP ProLiant m400 Server crashes with unhandled level 3 translation
>   fault
>
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   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>]

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

[Ming Lei]

This one looks a problem of systemd-timesyncd, from pmap log[1],
both the PC and faulted address aren't valid,  which drop in heap area,
but the faulted address(0x7fa8ea6008) shouldn't have been allocated
and is far away from the start address(0x7f9eb27000) of hear area.


[1] pmap log

ubuntu@ms10-37-mcdivittB0:~$ ps -ax | grep systemd-timesyncd
  412 ?Ssl0:00 /lib/systemd/systemd-timesyncd
18058 pts/2S+ 0:00 grep --color=auto systemd-timesyncd
ubuntu@ms10-37-mcdivittB0:~$ sudo pmap 412 | tail -n 10
007f8273108K r-x-- systemd-timesyncd
007f8274e000 16K rw---   [ anon ]
007f82757000  8K rw---   [ anon ]
007f82759000  4K r   [ anon ]
007f8275a000  4K r-x--   [ anon ]
007f8275b000  4K r systemd-timesyncd
007f8275c000  4K rw--- systemd-timesyncd
007f9eb27000132K rw---   [ anon ]
007fd5e13000132K rw---   [ stack ]
 total77176K
ubuntu@ms10-37-mcdivittB0:~$ sudo pmap 412
412:   /lib/systemd/systemd-timesyncd
007f7c00132K rw---   [ anon ]
007f7c021000  65404K -   [ anon ]
007f81c29000 16K r-x-- libnss_dns-2.21.so
007f81c2d000 64K - libnss_dns-2.21.so
007f81c3d000  4K r libnss_dns-2.21.so
007f81c3e000  4K rw--- libnss_dns-2.21.so
007f81c3f000  4K -   [ anon ]
007f81c4   8188K rw---   [ anon ]
007f8243f000 40K r-x-- libnss_files-2.21.so
007f82449000 60K - libnss_files-2.21.so
007f82458000  4K r libnss_files-2.21.so
007f82459000  4K rw--- libnss_files-2.21.so
007f8245a000 36K r-x-- libnss_nis-2.21.so
007f82463000 60K - libnss_nis-2.21.so
007f82472000  4K r libnss_nis-2.21.so
007f82473000  4K rw--- libnss_nis-2.21.so
007f82474000 72K r-x-- libnsl-2.21.so
007f82486000 60K - libnsl-2.21.so
007f82495000  4K r libnsl-2.21.so
007f82496000  4K rw--- libnsl-2.21.so
007f82497000  8K rw---   [ anon ]
007f82499000 24K r-x-- libnss_compat-2.21.so
007f8249f000 64K - libnss_compat-2.21.so
007f824af000  4K r libnss_compat-2.21.so
007f824b  4K rw--- libnss_compat-2.21.so
007f824b1000580K r-x-- libm-2.21.so
007f82542000 60K - libm-2.21.so
007f82551000  4K r libm-2.21.so
007f82552000  4K rw--- libm-2.21.so
007f82553000 16K r-x-- libcap.so.2.24
007f82557000 60K - libcap.so.2.24
007f82566000  4K r libcap.so.2.24
007f82567000  4K rw--- libcap.so.2.24
007f82568000 68K r-x-- libresolv-2.21.so
007f82579000 64K - libresolv-2.21.so
007f82589000  4K r libresolv-2.21.so
007f8258a000  4K rw--- libresolv-2.21.so
007f8258b000  8K rw---   [ anon ]
007f8258d000   1216K r-x-- libc-2.21.so
007f826bd000 60K - libc-2.21.so
007f826cc000 16K r libc-2.21.so
007f826d  8K rw--- libc-2.21.so
007f826d2000 16K rw---   [ anon ]
007f826d6000 88K r-x-- libpthread-2.21.so
007f826ec000 60K - libpthread-2.21.so
007f826fb000  4K r libpthread-2.21.so
007f826fc000  4K rw--- libpthread-2.21.so
007f826fd000 16K rw---   [ anon ]
007f82701000112K r-x-- ld-2.21.so
007f8272d000  4K r ld-2.21.so
007f8272e000  8K rw--- ld-2.21.so
007f8273108K r-x-- systemd-timesyncd
007f8274e000 16K rw---   [ anon ]
007f82757000  8K rw---   [ anon ]
007f82759000  4K r   [ anon ]
007f8275a000  4K r-x--   [ anon ]
007f8275b000  4K r systemd-timesyncd
007f8275c000  4K rw--- systemd-timesyncd
007f9eb27000132K rw---   [ anon ]
007fd5e13000132K rw---   [ stack ]
 total77176K

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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-gene

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

The night before yesterday, I have run stress-ng for one night, looks it isn't 
crashed on
mcdivitt.

Yesterday, I found my system is upgraded from trysty to vivid directly and the 
'systemd'
package isn't installed, then 'systemd-timesyn' can't be found, so I install 
the package
and make sure systemd-timesyncd is installed because the process was reported 
two times
in Colin's reports.

Then last night, I enable the the server by 'sudo timedatectl set-ntp true' 
before running
the test, but still not crash, see the logs attached.

** Attachment added: "mcdivitt-log-not-duplicatd.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469218/+attachment/4423691/+files/mcdivitt-log-not-duplicatd.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

Some static code analysis:

1), looks not possbile in scsi  request submit path
- preempt is disabled for arm64 vivid
- the timer is always added just before submitting to hardware
- once it can't be submitted to hardware, the timer is disabled

2), another possibility is in ata's completion path
- block request is always completed in 
softirq(scsi_done()->blk_complete_request())
- the softirq may be run from another CPU, which is triggered by IPI
- but one atomic complete flag is used to monitor the request completion status
(blk_mark_rq_complete()), so looks the timeout can't be caused by softirq delay 
schedule.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

Wrt. disk read failure in Colin's report, looks the sectors themselves invoved 
in timeout are good, becasue the following
test runs well in ms10-34 now:

sudo dd if=/dev/sda skip=9741420 iflag=direct of=/dev/null bs=512
count=1K

1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.0767411 s, 6.8 MB/s

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

Title:
  HP ProLiant m400: NULL pointer dereference PC is at
  ctx_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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

Given 'stress-ng --all 64' is  quite heavy and system-wide stress, and 
thousands of tasks are created for
running lots of stress concurrently which may touch most areas of kernel,  the 
triggered issue is quite difficult
to reproduce, so please add the detailed log information for further 
invesitigating in the following report,
otherwise it isn't helpful for the invesitigation.

Thanks,

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

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

Status in linux package in Ubuntu:
  Triaged

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

BTW, about the sata read timeout issue, I have run fio to verify sata disk 
read/randread/write/randwrite, and looks
it works fine

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

For #5's log, the fault happened in the following code snippet of
kernel/sched/cputime.c:

for_each_thread(tsk, t) {
ffcd3dc0:   f9445760ldr x0, [x27,#2216]
ffcd3dc4:   f8410c03ldr x3, [x0,#16]!
ffcd3dc8:   f90037a3str x3, [x29,#104]
ffcd3dcc:   f94037b4ldr x20, [x29,#104]
ffcd3dd0:   eb00029fcmp x20, x0
ffcd3dd4:   d10ee294sub x20, x20, #0x3b8
ffcd3dd8:   5481b.neffcd3de8 

ffcd3ddc:   1415b   ffcd3e30 

ffcd3de0:   f9400261ldr x1, [x19]
ffcd3de4:   f9400662ldr x2, [x19,#8]
cputime_t *utime, cputime_t *stime)
{
if (utime)
*utime = t->utime;
if (stime)
*stime = t->stime;
ffcd3de8:   f941f684ldr x4, [x20,#1000]  #fault 
instruction

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

But another kernel oops is just found on one mustang with vivid:

Call trace:
Unable to handle kernel NULL pointer dereference at virtual address 0018
pgd = ffc105652000
[0018] *pgd=00432d9dc003Unable to handle kernel NULL pointer 
dereference at virtual address 0030
pgd = ffc1b8d49000
[0030] *pgd=0041b8d4a003, *pud=0041b8d4a003, *pmd=
Internal error: Oops: 9606 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 15416 Comm: stress-ng-sysin Tainted: GW  3.19.8-ckt1+ 
#40
Hardware name: APM X-Gene Mustang board (DT)
task: ffc233cf0ac0 ti: ffc132094000 task.ti: ffc132094000
PC is at thread_group_cputime+0x90/0x154
LR is at thread_group_cputime+0x30/0x154
pc : [] lr : [] pstate: 0145
sp : ffc132097d90
x29: ffc132097d90 x28: ffc132094000 
x27: ffc233cf0ac0 x26: ffc02cc24154 
x25:  x24:  
x23:  x22: ffc02cc23fc0 
x21:  x20: fc48 
x19: ffc132097e38 x18:  
x17: 007fa836cff0 x16: ffcbb030 
x15: 002416761800 x14: 007fa82d3624 
x13: 6f6d2c6b32393237 x12:  
x11: 0006 x10: 0101010101010101 
x9 : fefeff7ea7306a2f x8 : 0099 
x7 : 746e756f6d203631 x6 : 007fc0aa71c3 
x5 :  x4 :  
x3 :  x2 :  
x1 :  x0 : ffc02cc23fd0 

Process stress-ng-sysin (pid: 15416, stack limit = 0xffc132094058)
Stack: (0xffc132097d90 to 0xffc132098000)
7d80: 32097e00 ffc1 000d0ed0 ffc0
7da0: 32097e80 ffc1 33cf0ac0 ffc2   a836cffc 007f
7dc0: 6000  0015  011a  0099 
7de0: 007f2000 ffc0 001e7742     
7e00: 32097e50 ffc1 000bafd8 ffc0 32097eb0 ffc1 0044cf58 
7e20:   32097e88 ffc1 c080 007f  
7e40:     32097e90 ffc1 000bb04c ffc0
7e60: c0aaab20 007f 0044cf58    000617db 
7e80: 001e7746  001e7742  c080 007f 00086470 ffc0
7ea0:   1026     
7ec0:     c0aaab20 007f c0aaabb0 007f
7ee0: c0aaab20 007f      
7f00: c0aa71c3 007f 6d203631 746e756f 0099  a7306a2f fefeff7e
7f20: 01010101 01010101 0006    32393237 6f6d2c6b
7f40: a82d3624 007f 1800 00241676 0044c5e8  a836cff0 007f
7f60:   c0aaaca0 007f 0044cf58  c0aaaca0 007f
7f80:   0044c000  a82b3370 007f 0010 
7fa0:   c0aab168 007f 0044c000  c080 007f
7fc0: 0042068c  c080 007f a836cffc 007f 6000 
7fe0: c0aaab20 007f 0099  49494949 49494949 49494949 49494949
Call trace:
[] thread_group_cputime+0x90/0x154
[] thread_group_cputime_adjusted+0x1c/0x44
[] do_sys_times+0x28/0x84
[] SyS_times+0x18/0x78
Code: 5481 1415 f9400261 f9400662 (f941f684) 
---[ end trace d68092dda907ca24 ]---
Kernel panic - not syncing: Fatal exception
CPU7: stopping
CPU: 7 PID: 18484 Comm: stress-ng-kill Tainted: G  D W  3.19.8-ckt1+ #40
Hardware name: APM X-Gene Mustang board (DT)
Call trace:
[] dump_backtrace+0x0/0x12c
[] show_stack+0x10/0x1c
[] dump_stack+0x88/0xd8
[] handle_IPI+0x184/0x194
[] gic_handle_irq+0x74/0x7c
Exception stack(0xffc32c0dbeb0 to 0xffc32c0dbfd0)
bea0:   4834 
bec0:   a8301cc8 007f   000a 
bee0:   0008  0008  03e8 
bf00: c0aaae88 007f   0081   
bf20: 01010101 01010101 0006     
bf40: a82d22e4 007f 8800 00080051 0044c180  a8301cc0 007f
bf60:   a8292c58 007f 4834  0044c000 
bf80:   0044c000  0044c000  00430ad8 
bfa0: 0005  c0aab168 007f 001b  c0aaaf20 007f
bfc0: 004180c8  c0aaaf20 007f
CPU6: stopping
CPU: 6 PID: 18493 Comm: stress-ng-minco Tainted: G  D W  3.19.8-ckt1+ 
#40
Hardware name: APM X-Gene Mustang board (DT)
Call trace:
[] dump_backtrace+0x0/0x12c
[] show_stack+0x10/0x1c
[] dump_stack+0x88/0xd8
[] handle_IPI+0x184/0x194
[] gic_handle_irq+0x74/0x7c
Exception stack(0xffc3bffdfeb0 to 0xffc3bffdffd0)
fea0:   000c 
fec0:   a83954e8 007f fff4  1000 0

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

BTW, it can't be reproduced on mustang when running vivid too.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469218] Re: HP ProLiant m400 Server sda timeout causes file system hang

[Ming Lei]

I can't reproduce it after running half a day on ms10-36, and OOM is
often triggered .

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469218

Title:
  HP ProLiant m400 Server sda timeout causes file system hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  While running stress-ng on a ProLiant m400 Server I managed to cause
  the disk controller to timeout which causes a file system hang. I am
  wondering if the timeout was causes because I completely overloaded
  the system causing it to be slow on ata handling times.

  I ran:

  stress-ng --all 64 -t 600 -v

  and the machine slowly clogged up with stress processes, and finally
  hit the hang.  Had to reboot the system.

  Attached is a kernel log.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

Oops, the test result in #4 is for LP1469218 instead of this one.

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

I can't reproduce it after running half a day on ms10-36, and OOM is often 
triggered .

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  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]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1469937] Re: HP ProLiant m400 Server: kernel boot failed because of failed sata probe

[Ming Lei]

Turns out the firmware on this server is a bit old(U-Boot 2013.04 (Oct 01 2014 
- 15:18:17)), and the problem
doesn't exit on another server which firmware is U-Boot 2013.04 (Mar 26 2015 - 
11:31:01).

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469937

Title:
  HP ProLiant m400 Server: kernel boot failed because of failed sata
  probe

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  1, upgrade to vivid from trysty

  2, boot the server, then the following log in [1] can be observed


  
  [1] kernel booting log
  Starting kernel ...

  L3C: 8MB
  [0.00] Booting Linux on physical CPU 0x0
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-21-generic (buildd@beebe) (gcc version 
4.9.2 (Ubuntu/Linaro 4.9.2-10ubuntu13) ) #21-Ubuntu SMP Sun Jun 14 18:34:06 UTC 
2015 (Ubuntu 3.19.0-21.21-generic 3.19.8)
  [0.00] CPU: AArch64 Processor [500f] revision 0
  [0.00] Detected PIPT I-cache on CPU0
  [0.00] efi: Getting EFI parameters from FDT:
  [0.00] efi: UEFI not found.
  [0.00] PERCPU: Embedded 14 pages/cpu @ffc7fff49000 s19968 r8192 
d29184 u57344
  [0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 8257536
  [0.00] Kernel command line: console=ttyS0,9600n8r ro
  [0.00] log_buf_len individual max cpu contribution: 4096 bytes
  [0.00] log_buf_len total cpu_extra contributions: 28672 bytes
  [0.00] log_buf_len min size: 16384 bytes
  [0.00] log_buf_len: 65536 bytes
  [0.00] early log buf free: 14868(90%)
  [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
  [0.00] Dentry cache hash table entries: 4194304 (order: 13, 33554432 
bytes)
  [0.00] Inode-cache hash table entries: 2097152 (order: 12, 16777216 
bytes)
  [0.00] Memory: 32942004K/33554432K available (7287K kernel code, 812K 
rwdata, 3180K rodata, 604K init, 743K bss, 612428K reserved, 0K cma-reserved)
  [0.00] Virtual kernel memory layout:
  [0.00] vmalloc : 0xff80 - 0xffbdbfff   (   
246 GB)
  [0.00] vmemmap : 0xffbdc000 - 0xffbfc000   ( 
8 GB maximum)
  [0.00]   0xffbec000 - 0xffbee000   (   
512 MB actual)
  [0.00] PCI I/O : 0xffbffa00 - 0xffbffb00   (
16 MB)
  [0.00] fixed   : 0xffbffbdfd000 - 0xffbffbdff000   ( 
8 KB)
  [0.00] modules : 0xffbffc00 - 0xffc0   (
64 MB)
  [0.00] memory  : 0xffc0 - 0xffc8   ( 
32768 MB)
  [0.00]   .init : 0xffc000abb000 - 0xffc000b52000   (   
604 KB)
  [0.00]   .text : 0xffc8 - 0xffc000abaf04   ( 
10476 KB)
  [0.00]   .data : 0xffc000b57000 - 0xffc000c22200   (   
813 KB)
  [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
  [0.00] Hierarchical RCU implementation.
  [0.00]RCU dyntick-idle grace-period acceleration is enabled.
  [0.00] NR_IRQS:64 nr_irqs:64 0
  [0.00] Architected cp15 timer(s) running at 50.00MHz (phys).
  [0.02] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 
2748779069440ns
  [0.69] Console: colour dummy device 80x25
  [0.82] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 100.00 BogoMIPS (lpj=50)
  [0.87] pid_max: default: 32768 minimum: 301
  [0.000114] Security Framework initialized
  [0.000149] AppArmor: AppArmor initialized
  [0.000151] Yama: becoming mindful.
  [0.000218] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
  [0.000223] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 
bytes)
  [0.000602] Initializing cgroup subsys memory
  [0.000613] Initializing cgroup subsys devices
  [0.000617] Initializing cgroup subsys freezer
  [0.000621] Initializing cgroup subsys net_cls
  [0.000624] Initializing cgroup subsys blkio
  [0.000628] Initializing cgroup subsys perf_event
  [0.000631] Initializing cgroup subsys net_prio
  [0.000635] Initializing cgroup subsys hugetlb
  [0.000653] ftrace: allocating 26186 entries in 103 pages
  [0.011825] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 5 
counters available
  [0.011839] EFI services will not be available.
  [0.012826] CPU1: Booted secondary processor
  [0.012830] Detected PIPT I-cache on CPU1
  [0.012986] CPU2: Booted secondary processor
  [0.012989] Detected PIPT I-cache on CPU2
  [0.013131]

[Kernel-packages] [Bug 1469937] [NEW] HP ProLiant m400 Server: kernel boot failed because of failed sata probe

[Ming Lei]

Public bug reported:


1, upgrade to vivid from trysty

2, boot the server, then the following log in [1] can be observed


[1] kernel booting log
Starting kernel ...

L3C: 8MB
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.19.0-21-generic (buildd@beebe) (gcc version 
4.9.2 (Ubuntu/Linaro 4.9.2-10ubuntu13) ) #21-Ubuntu SMP Sun Jun 14 18:34:06 UTC 
2015 (Ubuntu 3.19.0-21.21-generic 3.19.8)
[0.00] CPU: AArch64 Processor [500f] revision 0
[0.00] Detected PIPT I-cache on CPU0
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] PERCPU: Embedded 14 pages/cpu @ffc7fff49000 s19968 r8192 
d29184 u57344
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 8257536
[0.00] Kernel command line: console=ttyS0,9600n8r ro
[0.00] log_buf_len individual max cpu contribution: 4096 bytes
[0.00] log_buf_len total cpu_extra contributions: 28672 bytes
[0.00] log_buf_len min size: 16384 bytes
[0.00] log_buf_len: 65536 bytes
[0.00] early log buf free: 14868(90%)
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] Dentry cache hash table entries: 4194304 (order: 13, 33554432 
bytes)
[0.00] Inode-cache hash table entries: 2097152 (order: 12, 16777216 
bytes)
[0.00] Memory: 32942004K/33554432K available (7287K kernel code, 812K 
rwdata, 3180K rodata, 604K init, 743K bss, 612428K reserved, 0K cma-reserved)
[0.00] Virtual kernel memory layout:
[0.00] vmalloc : 0xff80 - 0xffbdbfff   (   246 
GB)
[0.00] vmemmap : 0xffbdc000 - 0xffbfc000   ( 8 
GB maximum)
[0.00]   0xffbec000 - 0xffbee000   (   512 
MB actual)
[0.00] PCI I/O : 0xffbffa00 - 0xffbffb00   (16 
MB)
[0.00] fixed   : 0xffbffbdfd000 - 0xffbffbdff000   ( 8 
KB)
[0.00] modules : 0xffbffc00 - 0xffc0   (64 
MB)
[0.00] memory  : 0xffc0 - 0xffc8   ( 32768 
MB)
[0.00]   .init : 0xffc000abb000 - 0xffc000b52000   (   604 
KB)
[0.00]   .text : 0xffc8 - 0xffc000abaf04   ( 10476 
KB)
[0.00]   .data : 0xffc000b57000 - 0xffc000c22200   (   813 
KB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[0.00] Hierarchical RCU implementation.
[0.00]  RCU dyntick-idle grace-period acceleration is enabled.
[0.00] NR_IRQS:64 nr_irqs:64 0
[0.00] Architected cp15 timer(s) running at 50.00MHz (phys).
[0.02] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 
2748779069440ns
[0.69] Console: colour dummy device 80x25
[0.82] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 100.00 BogoMIPS (lpj=50)
[0.87] pid_max: default: 32768 minimum: 301
[0.000114] Security Framework initialized
[0.000149] AppArmor: AppArmor initialized
[0.000151] Yama: becoming mindful.
[0.000218] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
[0.000223] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 
bytes)
[0.000602] Initializing cgroup subsys memory
[0.000613] Initializing cgroup subsys devices
[0.000617] Initializing cgroup subsys freezer
[0.000621] Initializing cgroup subsys net_cls
[0.000624] Initializing cgroup subsys blkio
[0.000628] Initializing cgroup subsys perf_event
[0.000631] Initializing cgroup subsys net_prio
[0.000635] Initializing cgroup subsys hugetlb
[0.000653] ftrace: allocating 26186 entries in 103 pages
[0.011825] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 5 
counters available
[0.011839] EFI services will not be available.
[0.012826] CPU1: Booted secondary processor
[0.012830] Detected PIPT I-cache on CPU1
[0.012986] CPU2: Booted secondary processor
[0.012989] Detected PIPT I-cache on CPU2
[0.013131] CPU3: Booted secondary processor
[0.013133] Detected PIPT I-cache on CPU3
[0.013266] CPU4: Booted secondary processor
[0.013269] Detected PIPT I-cache on CPU4
[0.013410] CPU5: Booted secondary processor
[0.013412] Detected PIPT I-cache on CPU5
[0.013545] CPU6: Booted secondary processor
[0.013548] Detected PIPT I-cache on CPU6
[0.013687] CPU7: Booted secondary processor
[0.013689] Detected PIPT I-cache on CPU7
[0.013718] Brought up 8 CPUs
[0.013730] SMP: Total of 8 processors activated.
[0.014041] devtmpfs: initialized
[0.014210] evm: security.selinux
[0.014213] evm: security.SMACK64
[0.014215] evm: security.SMACK64EXEC
[0.014217] ev

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

[Ming Lei]

ubuntu@am6:~$ uname -a
Linux am6 3.16.0-43-generic #58-Ubuntu SMP Fri Jun 19 11:04:11 UTC 2015 aarch64 
aarch64 aarch64 GNU/Linux
ubuntu@am6:~$ sudo ethtool eth2
Settings for eth2:
Supported ports: [ MII ]
Supported link modes:   1000baseT/Full 
Supported pause frame use: No
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: yes

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

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

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

Verification on utopic:

ubuntu@am6:~$ sudo crash vmlinux
[sudo] password for ubuntu: 

crash 7.0.8
Copyright (C) 2002-2014  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu"...

  KERNEL: vmlinux
DUMPFILE: /dev/mem
CPUS: 8
DATE: Wed Dec 31 19:00:00 1969
  UPTIME: 00:01:48
LOAD AVERAGE: 0.26, 0.13, 0.05
   TASKS: 135
NODENAME: am6
 RELEASE: 3.19.8-ckt1+
 VERSION: #39 SMP PREEMPT Thu Jun 25 04:41:15 EDT 2015
 MACHINE: aarch64  (unknown Mhz)
  MEMORY: 16 GB
 PID: 1955
 COMMAND: "crash"
TASK: ffc3ed08cb40  [THREAD_INFO: ffc0fee2c000]
 CPU: 3
   STATE: TASK_RUNNING (ACTIVE)

crash> bt -e
PID: 1955   TASK: ffc3ed08cb40  CPU: 6   COMMAND: "crash"
USER-MODE EXCEPTION FRAME AT: ffc0fee2fed0
 PC: 007fb1432218   LR: 0047ddb0   SP: 007fedca7c50
X29: 007fedca7c50  X28: fff9  X27: 00854700
X26: 007fb1375710  X25: ffc0fee2f000  X24: 00a225f0
X23: 0004  X22: 1000  X21: 0097
X20: 0040fee2f000  X19: 009a7180  X18: 007fedca8300
X17: 007fb1432200  X16:   X15: 007fb14ac590
X14:   X13:   X12: 0028
X11: 0005  X10: 161a28e8   X9: 0004
 X8: 003f   X7: 009bf180   X6: 009a4f70
 X5: 0040   X4: 0044   X3: ffc0fee2f000
 X2: 1000   X1: 00a225f0   X0: 0004
ORIG_X0: 0004  SYSCALLNO: 3f  PSTATE: 6000
crash> quit
ubuntu@am6:~$ dpkg -l crash
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  crash  7.0.8-1ubunt arm64kernel debugging utility, allowin
ubuntu@am6:~$ 


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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed
Status in crash source package in Utopic:
  Fix Committed
Status in crash source package in Vivid:
  Fix Committed
Status in crash source package in Wily:
  Fix Released

Bug description:
  [Impact]

  crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
  debugging a new kernel like 4.1-rc+

  [Test Case]

  sudo crash ~/vmlinux
  crash will exit with failure log of 'crash: invalid/unknown page size: 
  6144', see detailed steps in [1].

  [Regression Potential]

  The proposed patch has been merged upstream, so there shouldn't be
  potential regression.

  Also These changes are to code that only gets compiled on arm64, so
  there's no risk to other architectures.

  [Other Info]

  After running crash from trusty, the failure log in [1] can be
  observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

verification on vivid:
ubuntu@ubuntu:~/test$ sudo dpkg -l crash
sudo: unable to resolve host ubuntu
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  crash  7.0.8-1ubunt arm64kernel debugging utility, allowin
ubuntu@ubuntu:~/test$ ls
Image  linux1.tar.xz  loopubuntu   vm-test
linux  linux.tar.xz   System.map  vmlinux
ubuntu@ubuntu:~/test$ sudo crash vmlinux
sudo: unable to resolve host ubuntu

crash 7.0.8
Copyright (C) 2002-2014  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu"...

  KERNEL: vmlinux
DUMPFILE: /dev/mem
CPUS: 8
DATE: Thu Jan  1 00:00:00 1970
  UPTIME: 00:01:50
LOAD AVERAGE: 0.30, 0.10, 0.04
   TASKS: 142
NODENAME: ubuntu
 RELEASE: 3.19.8-ckt1+
 VERSION: #39 SMP PREEMPT Thu Jun 25 04:41:15 EDT 2015
 MACHINE: aarch64  (unknown Mhz)
  MEMORY: 16 GB
 PID: 2017
 COMMAND: "crash"
TASK: ffc3ccae5600  [THREAD_INFO: ffc0fd1a8000]
 CPU: 0
   STATE: TASK_RUNNING (ACTIVE)

crash> bt -e
PID: 2017   TASK: ffc3ccae5600  CPU: 2   COMMAND: "crash"
USER-MODE EXCEPTION FRAME AT: ffc0fd1abed0
 PC: 007fa3a2ca78   LR: 0047daa0   SP: 007fcb803950
X29: 007fcb803950  X28: 0096e000  X27: 007f1000
X26: 007f75a8  X25: ffc0fd1ab000  X24: 00a205f0
X23: 0004  X22: 1000  X21: 0096e000
X20: 0040fd1ab000  X19: 009a5180  X18: 
X17: 007fa3a2ca90  X16:   X15: 
X14:   X13:   X12: 0028
X11: 0101010101010101  X10: 7f7f7f7f7f7f7fff   X9: 0004
 X8: 003f   X7:    X6: 007fa3c18710
 X5: 0047d970   X4: 0040fd1ab000   X3: ffc0fd1ab000
 X2: 1000   X1: 00a205f0   X0: 0004
ORIG_X0: 0004  SYSCALLNO: 3f  PSTATE: 
crash>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed
Status in crash source package in Utopic:
  Fix Committed
Status in crash source package in Vivid:
  Fix Committed
Status in crash source package in Wily:
  Fix Released

Bug description:
  [Impact]

  crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
  debugging a new kernel like 4.1-rc+

  [Test Case]

  sudo crash ~/vmlinux
  crash will exit with failure log of 'crash: invalid/unknown page size: 
  6144', see detailed steps in [1].

  [Regression Potential]

  The proposed patch has been merged upstream, so there shouldn't be
  potential regression.

  Also These changes are to code that only gets compiled on arm64, so
  there's no risk to other architectures.

  [Other Info]

  After running crash from trusty, the failure log in [1] can be
  observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free 

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

Verification on trusty:

ubuntu@am2:~$ sudo crash vmlinux
[sudo] password for ubuntu: 

crash 7.0.3
Copyright (C) 2002-2013  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu"...

  KERNEL: vmlinux
DUMPFILE: /dev/mem
CPUS: 8
DATE: Thu Jun 25 21:58:34 2015
  UPTIME: 00:03:29
LOAD AVERAGE: 0.08, 0.03, 0.01
   TASKS: 130
NODENAME: am2
 RELEASE: 3.13.11-ckt21+
 VERSION: #35 SMP PREEMPT Thu Jun 18 03:19:42 EDT 2015
 MACHINE: aarch64  (unknown Mhz)
  MEMORY: 16 GB
 PID: 1766
 COMMAND: "crash"
TASK: ffc3e79be180  [THREAD_INFO: ffc3e3c44000]
 CPU: 3
   STATE: TASK_RUNNING (ACTIVE)

crash> bt -e
PID: 1766   TASK: ffc3e79be180  CPU: 5   COMMAND: "crash"
USER-MODE EXCEPTION FRAME AT: ffc3e3c47ed0
 PC: 007fa68812cc   LR: 0047ad2c   SP: 007fd2a4c400
X29: 007fd2a4c400  X28: 0094b000  X27: 1000
X26: 007fa67c4710  X25: ffc3e3c47000  X24: 00982080
X23: 009fd488  X22: 0004  X21: 1000
X20: 0094b000  X19: 0043e3c47000  X18: 007fd2a4ca60
X17: 007fa68812b0  X16:   X15: 007fa690b590
X14:   X13:   X12: 0028
X11: 0005  X10: 28521830   X9: 0004
 X8: 003f   X7: 0099a030   X6: 003f
 X5: 0047ac18   X4: 0099f9e8   X3: ffc3e3c47000
 X2: 1000   X1: 009fd488   X0: 0004
ORIG_X0: 0004  SYSCALLNO: 3f  PSTATE: 6000
crash> 
crash> quit
ubuntu@am2:~$ sudo dpkg -l crash
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  crash  7.0.3-3ubunt arm64kernel debugging utility, allowin

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed
Status in crash source package in Utopic:
  Fix Committed
Status in crash source package in Vivid:
  Fix Committed
Status in crash source package in Wily:
  Fix Released

Bug description:
  [Impact]

  crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
  debugging a new kernel like 4.1-rc+

  [Test Case]

  sudo crash ~/vmlinux
  crash will exit with failure log of 'crash: invalid/unknown page size: 
  6144', see detailed steps in [1].

  [Regression Potential]

  The proposed patch has been merged upstream, so there shouldn't be
  potential regression.

  Also These changes are to code that only gets compiled on arm64, so
  there's no risk to other architectures.

  [Other Info]

  After running crash from trusty, the failure log in [1] can be
  observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help cop

[Kernel-packages] [Bug 1466686] Re: crash: arm64: don't support some BT commands

[Ming Lei]

ubuntu@am2:~$ sudo crash vmlinux
[sudo] password for ubuntu: 

crash 7.0.3
Copyright (C) 2002-2013  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu"...

  KERNEL: vmlinux
DUMPFILE: /dev/mem
CPUS: 8
DATE: Thu Jun 25 21:58:34 2015
  UPTIME: 00:03:29
LOAD AVERAGE: 0.08, 0.03, 0.01
   TASKS: 130
NODENAME: am2
 RELEASE: 3.13.11-ckt21+
 VERSION: #35 SMP PREEMPT Thu Jun 18 03:19:42 EDT 2015
 MACHINE: aarch64  (unknown Mhz)
  MEMORY: 16 GB
 PID: 1766
 COMMAND: "crash"
TASK: ffc3e79be180  [THREAD_INFO: ffc3e3c44000]
 CPU: 3
   STATE: TASK_RUNNING (ACTIVE)

crash> bt -e
PID: 1766   TASK: ffc3e79be180  CPU: 5   COMMAND: "crash"
USER-MODE EXCEPTION FRAME AT: ffc3e3c47ed0
 PC: 007fa68812cc   LR: 0047ad2c   SP: 007fd2a4c400
X29: 007fd2a4c400  X28: 0094b000  X27: 1000
X26: 007fa67c4710  X25: ffc3e3c47000  X24: 00982080
X23: 009fd488  X22: 0004  X21: 1000
X20: 0094b000  X19: 0043e3c47000  X18: 007fd2a4ca60
X17: 007fa68812b0  X16:   X15: 007fa690b590
X14:   X13:   X12: 0028
X11: 0005  X10: 28521830   X9: 0004
 X8: 003f   X7: 0099a030   X6: 003f
 X5: 0047ac18   X4: 0099f9e8   X3: ffc3e3c47000
 X2: 1000   X1: 009fd488   X0: 0004
ORIG_X0: 0004  SYSCALLNO: 3f  PSTATE: 6000
crash> 
crash> quit
ubuntu@am2:~$ sudo dpkg -l crash
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  crash  7.0.3-3ubunt arm64kernel debugging utility, allowin
ubuntu@am2:~$ 


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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1466686

Title:
  crash: arm64: don't support some BT commands

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed

Bug description:
  On trusty, some BT commands are missed for ARM64.

  [Impact]
  some BT commands aren't usable, such as bt -e, bt -l, ...

  [Test Case]
  - start crash
  - run bt -e

  crash> bt -e
  PID: 2113   TASK: ffc3e3446180  CPU: 5   COMMAND: "crash"
  bt: arm64_eframe_search: function not implemented

  
  [Regression Potential]
  These changes are to code that only gets compiled on arm64, so
  there's no risk to other architectures. Also the proposed change is
  merged to upstream alread.

  The patches in below link can make them workable:

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=3d11253387a609283054c8b0d76b0d33704b6e27

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=2c43ddb93e0591e14c92c5d7469ed2c6029df5a5

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=f384eaa863b82009caaf136bc88c3e6f5c0ceb66

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=653aa6bc8b5108bf6a6f737275fe4a1b94ba4703

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Ming Lei (tom-leiming)

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1466686] [NEW] crash: arm64: don't support some BT commands

[Ming Lei]

Public bug reported:

On trusty, some BT commands are missed for ARM64.

[Impact]
some BT commands aren't usable, such as bt -e, bt -l, ...

[Test Case]
- start crash
- run bt -e

crash> bt -e
PID: 2113   TASK: ffc3e3446180  CPU: 5   COMMAND: "crash"
bt: arm64_eframe_search: function not implemented


[Regression Potential]
These changes are to code that only gets compiled on arm64, so
there's no risk to other architectures. Also the proposed change is
merged to upstream alread.

The patches in below link can make them workable:

http://kernel.ubuntu.com/git/ming/crash-
trusty.git/commit/?id=3d11253387a609283054c8b0d76b0d33704b6e27

http://kernel.ubuntu.com/git/ming/crash-
trusty.git/commit/?id=2c43ddb93e0591e14c92c5d7469ed2c6029df5a5

http://kernel.ubuntu.com/git/ming/crash-
trusty.git/commit/?id=f384eaa863b82009caaf136bc88c3e6f5c0ceb66

http://kernel.ubuntu.com/git/ming/crash-
trusty.git/commit/?id=653aa6bc8b5108bf6a6f737275fe4a1b94ba4703

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1466686

Title:
  crash: arm64: don't support some BT commands

Status in crash package in Ubuntu:
  New

Bug description:
  On trusty, some BT commands are missed for ARM64.

  [Impact]
  some BT commands aren't usable, such as bt -e, bt -l, ...

  [Test Case]
  - start crash
  - run bt -e

  crash> bt -e
  PID: 2113   TASK: ffc3e3446180  CPU: 5   COMMAND: "crash"
  bt: arm64_eframe_search: function not implemented

  
  [Regression Potential]
  These changes are to code that only gets compiled on arm64, so
  there's no risk to other architectures. Also the proposed change is
  merged to upstream alread.

  The patches in below link can make them workable:

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=3d11253387a609283054c8b0d76b0d33704b6e27

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=2c43ddb93e0591e14c92c5d7469ed2c6029df5a5

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=f384eaa863b82009caaf136bc88c3e6f5c0ceb66

  http://kernel.ubuntu.com/git/ming/crash-
  trusty.git/commit/?id=653aa6bc8b5108bf6a6f737275fe4a1b94ba4703

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

** Description changed:

+ [Impact]
  
- [Impact] 
- 
- crash can't be used on ubuntu trusty, utopic and vivid
+ crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
+ debugging a new kernel like 4.1-rc+
  
  [Test Case]
  
  sudo crash ~/vmlinux
+ crash will exit with failure log of 'crash: invalid/unknown page size: 
+ 6144', see detailed steps in [1].
  
  [Regression Potential]
  
  The proposed patch has been merged upstream, so there shouldn't be
- potential regression
+ potential regression.
+ 
+ Also These changes are to code that only gets compiled on arm64, so
+ there's no risk to other architectures.
  
  [Other Info]
-  
- 
  
  After running crash from trusty, the failure log in [1] can be observed.
  
  Then I built crash from wily directly, the similar failure[2] can be
  observed too.
  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux
  
  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  crash: invalid/unknown page size: 6144
  
  [2]
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
  [sudo] password for ubuntu:
  
  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  crash: invalid/unsupported page size: 6144

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  New
Status in crash source package in Utopic:
  New
Status in crash source package in Vivid:
  New
Status in crash source package in Wily:
  Fix Released

Bug description:
  [Impact]

  crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
  debugging a new kernel like 4.1-rc+

  [Test Case]

  sudo crash ~/vmlinux
  crash will exit with failure log of 'crash: invalid/unknown page size: 
  6144', see detailed steps in [1].

  [Regression Potential]

  The proposed patch has been merged upstream, so there shouldn't be
  potential regression.

  Also These changes are to code that only gets compiled on arm64, so
  there's no risk to other architectures.

  [Other Info]

  After running crash from trusty, the failure log in [1] can be
  observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  crash: invalid/unknown page size: 6144

  [2]
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
  [sudo] password for ubuntu:

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright 

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

[Ming Lei]

And the patches in below links can fix the above crashs(#14, #15)

http://kernel.ubuntu.com/git/ming/ubuntu-trusty.git/commit/?h=apm-enet-
fix&id=a19b2c0bdd12e59a482717664312b18407284ee5

http://kernel.ubuntu.com/git/ming/ubuntu-utopic.git/commit/?h=arm64-net-
backport&id=d46456e3ed9153e743f2add6e01d06c56eb2ceb7

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  In Progress

Bug description:
  [Impact]
  System panics every few hours under constant network load

  [Test Case]
  On the X-Gene system, start an iperf server:
$ iperf -s
  Connect to it from another system (1Gbps is sufficient)
$ iperf -t 10 -c 

  On failure, you'll get a panic within several hours.

  [Regression Risk]
  The proposed patch only touches the impacted driver. It is adding a memory 
barrier - albeit a lightweight one - so there is the risk of a performance 
degradation. Indeed, when measured using a 60s iperf run, I do see a 
performance drop, but by < 0.5%.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

** Attachment added: "crash log in utopic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416914/+files/dmesg-utopic.log

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  In Progress

Bug description:
  [Impact]
  System panics every few hours under constant network load

  [Test Case]
  On the X-Gene system, start an iperf server:
$ iperf -s
  Connect to it from another system (1Gbps is sufficient)
$ iperf -t 10 -c 

  On failure, you'll get a panic within several hours.

  [Regression Risk]
  The proposed patch only touches the impacted driver. It is adding a memory 
barrier - albeit a lightweight one - so there is the risk of a performance 
degradation. Indeed, when measured using a 60s iperf run, I do see a 
performance drop, but by < 0.5%.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

Finally I figured out one approach to reproduce it quickly, see the
attachment log.


** Attachment added: "crash log in trusty"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416913/+files/dmesg-trusty.log

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  In Progress

Bug description:
  [Impact]
  System panics every few hours under constant network load

  [Test Case]
  On the X-Gene system, start an iperf server:
$ iperf -s
  Connect to it from another system (1Gbps is sufficient)
$ iperf -t 10 -c 

  On failure, you'll get a panic within several hours.

  [Regression Risk]
  The proposed patch only touches the impacted driver. It is adding a memory 
barrier - albeit a lightweight one - so there is the risk of a performance 
degradation. Indeed, when measured using a 60s iperf run, I do see a 
performance drop, but by < 0.5%.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

>From the original report, the issue happened since 3.17, so close it on trysty 
>because we can't reproduce it
on trusty too.

  I've seen this with mainline since somewhere in v3.17 and on several
 hardware boards stress testing KVM by running workloads in VMs.

** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => Invalid

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [] lr : [] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20: 0

[Kernel-packages] [Bug 1460942] Re: crash: incompatible arguments: vmlinux is not SMP -- live system is SMP

[Ming Lei]

** Description changed:

+ 
+ [Impact] 
+ 
+ crash can't be used on ubuntu trusty, utopic and vivid
+ 
+ [Test Case]
+ 
+ sudo crash ~/vmlinux
+ 
+ [Regression Potential]
+ 
+ The proposed patch has been merged upstream, so there shouldn't be
+ potential regression
+ 
+ [Other Info]
+  
+ 
  
  When I build crash from wily, the failure in [1] can be
  triggered if the kernel is 4.0+.
  
- 
  [1] failure log
- ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
+ ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
  
  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
-  
+ 
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...
  
  WARNING: kernels compiled by different gcc versions:
-   /home/ubuntu/vmlinux: (unknown)
-   live system kernel: 4.8.2
+   /home/ubuntu/vmlinux: (unknown)
+   live system kernel: 4.8.2
  
  WARNING: kernel version inconsistency between vmlinux and live memory
  
- crash: incompatible arguments: 
-/home/ubuntu/vmlinux is not SMP -- live system is SMP
+ crash: incompatible arguments:
+    /home/ubuntu/vmlinux is not SMP -- live system is SMP
  
  Usage:
  
-   crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
-   crash [OPTION]... [NAMELIST](live system form)
+   crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
+   crash [OPTION]... [NAMELIST](live system form)
  
  Enter "crash -h" for details.
  ubuntu@am2:~/git/crash-wily$

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460942

Title:
  crash: incompatible arguments:   vmlinux is not SMP -- live system is
  SMP

Status in crash package in Ubuntu:
  New

Bug description:
  
  [Impact] 

  crash can't be used on ubuntu trusty, utopic and vivid

  [Test Case]

  sudo crash ~/vmlinux

  [Regression Potential]

  The proposed patch has been merged upstream, so there shouldn't be
  potential regression

  [Other Info]
   


  When I build crash from wily, the failure in [1] can be
  triggered if the kernel is 4.0+.

  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...

  WARNING: kernels compiled by different gcc versions:
    /home/ubuntu/vmlinux: (unknown)
    live system kernel: 4.8.2

  WARNING: kernel version inconsistency between vmlinux and live memory

  crash: incompatible arguments:
     /home/ubuntu/vmlinux is not SMP -- live system is SMP

  Usage:

    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
    crash [OPTION]... [NAMELIST](live system form)

  Enter "crash -h" for details.
  ubuntu@am2:~/git/crash-wily$

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

-- 
Mailing list: https

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

** Description changed:

+ 
+ [Impact] 
+ 
+ crash can't be used on ubuntu trusty, utopic and vivid
+ 
+ [Test Case]
+ 
+ sudo crash ~/vmlinux
+ 
+ [Regression Potential]
+ 
+ The proposed patch has been merged upstream, so there shouldn't be
+ potential regression
+ 
+ [Other Info]
+  
+ 
  
  After running crash from trusty, the failure log in [1] can be observed.
  
  Then I built crash from wily directly, the similar failure[2] can be
  observed too.
  
- 
  [1] failure log
- ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 
+ ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux
  
  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
-  
  
  crash: invalid/unknown page size: 6144
  
- [2] 
- ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
- [sudo] password for ubuntu: 
+ [2]
+ ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
+ [sudo] password for ubuntu:
  
  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
-  
  
  crash: invalid/unsupported page size: 6144

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  New

Bug description:
  
  [Impact] 

  crash can't be used on ubuntu trusty, utopic and vivid

  [Test Case]

  sudo crash ~/vmlinux

  [Regression Potential]

  The proposed patch has been merged upstream, so there shouldn't be
  potential regression

  [Other Info]
   


  After running crash from trusty, the failure log in [1] can be
  observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  crash: invalid/unknown page size: 6144

  [2]
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
  [sudo] password for ubuntu:

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  crash: invalid/unsupported page size: 6144

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
U

[Kernel-packages] [Bug 1452293] Re: kernel crash when compiling linux-4.1-rc2 with make -j20

[Ming Lei]

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

** This bug has been marked a duplicate of bug 1440536
   Oops __d_lookup+0x88/0x194

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1452293

Title:
  kernel crash when compiling linux-4.1-rc2 with make -j20

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel crash whilst building new kernel:

  Steps to reproduce:

  wget https://www.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc2.tar.xz
  tar xf linux-4.1-rc2.tar.xz
  cd linux-4.1-rc2/
  make mrproper
  make olddefconfig
  make -j20

  I noticed that the output from the build had stopped then noticed the
  following messages (via dmesg):

  [   15.285274] random: nonblocking pool is initialized
  [   15.633718] xgene-enet 1702.ethernet eth0: Link is Up - 1Gbps/Full - 
flow control off
  [ 2541.173142] Unable to handle kernel paging request at virtual address 
1018
  [ 2541.181062] pgd = ffc3ec61d000
  [ 2541.184449] [1018] *pgd=, *pud=
  [ 2541.191476] Internal error: Oops: 9605 [#1] SMP
  [ 2541.196331] Modules linked in: rtc_xgene xgene_rng uio_pdrv_genirq uio 
autofs4 realtek ahci_xgene libahci_platform xgene_enet libahci aes_neon_blk 
ablk_
  helper cryptd
  [ 2541.211214] CPU: 2 PID: 17206 Comm: sh Not tainted 3.19.0-15-generic 
#15-Ubuntu
  [ 2541.218488] Hardware name: APM X-Gene Mustang board (DT)
  [ 2541.223775] task: ffc3ec2d3d40 ti: ffc0fec1c000 task.ti: 
ffc0fec1c000
  [ 2541.231236] PC is at __d_lookup+0x88/0x194
  [ 2541.235324] LR is at d_lookup+0x3c/0x64
  [ 2541.239148] pc : [] lr : [] pstate: 
0145
  [ 2541.246509] sp : ffc0fec1fb40
  [ 2541.249807] x29: ffc0fec1fb40 x28: 00020241 
  [ 2541.255114] x27: 1b2865a6 x26: ffc0fec1fe88 
  [ 2541.260421] x25:  x24: ffc0ff01d02d 
  [ 2541.265728] x23: 000b x22: ffc0fec1fda0 
  [ 2541.271045] x21: ffc3b80ebd80 x20: 0ff8 
  [ 2541.276353] x19: 1000 x18:  
  [ 2541.281659] x17: 002000118748 x16: ffc00020f430 
  [ 2541.286967] x15: 0008 x14: 636e692f8134366d 
  [ 2541.292275] x13: 72612f8168637261 x12: 492d812069706175 
  [ 2541.297594] x11:  x10: fefefefefefefeff 
  [ 2541.302904] x9 :  x8 : ffc3e9ed2f40 
  [ 2541.308221] x7 :  x6 : 003f 
  [ 2541.313532] x5 : ffc0ff01d000 x4 : 0015 
  [ 2541.318848] x3 : ffc000b64f60 x2 : 9e370001 
  [ 2541.324155] x1 : ffc3eec0 x0 : 001e7194 
  [ 2541.330959] Process sh (pid: 17206, stack limit = 0xffc0fec1c058)
  [ 2541.337367] Stack: (0xffc0fec1fb40 to 0xffc0fec2)
  [ 2541.343088] fb40: fec1fba0 ffc0 0022a268 ffc0 dd6e  
00b5a000 ffc0
  [ 2541.351235] fb60: fec1fda0 ffc0 b80ebd80 ffc3 0301  
b80ebd80 ffc3
  [ 2541.359378] fb80: 0001  fec1fe88 ffc0 fec1fd90 ffc0 
00020241 
  [ 2541.367516] fba0: fec1fbd0 ffc0 0021b0e0 ffc0 fec1fd40 ffc0 
b80ebd80 ffc3
  [ 2541.375654] fbc0: fec1fda0 ffc0 fec1fca7 ffc0 fec1fc10 ffc0 
0021d790 ffc0
  [ 2541.383792] fbe0: fec1fd40 ffc0 b8113458 ffc3 b80ebd80 ffc3 
ff01d000 ffc0
  [ 2541.391930] fc00: fec1fd3c ffc0 fec1fd90 ffc0 fec1fcb0 ffc0 
002204c8 ffc0
  [ 2541.400066] fc20: fe52d000 ffc0 fec1fd90 ffc0 fec1fe88 ffc0 
ff01d000 ffc0
  [ 2541.408204] fc40: 0041  ff9c  011a  
0038 
  [ 2541.416343] fc60: 00b6e000 ffc0   fec1fcb0 ffc0 
002204a4 ffc0
  [ 2541.424481] fc80: 0001  ff01d000 ffc0 fe52d000 ffc0 
0022 

  (the rest is attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  1  1970 seq
   crw-rw 1 root audio 116, 33 Jan  1  1970 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed May  6 14:08:16 2015
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=

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

[Ming Lei]

>From dann's reports:

1) system1
Code: 1412 f9400273 b4000213 d1002274 (b9402280)

2) system2
Code: 1412 f9400273 b4000213 d1002274 (b9402280)

And the upstem report in #15,
Code: 1403 f9400273 b4000213 d1002274 (b9402282)

The code snippet should be the following in __d_lookup(): fs/dcache.c

ffc0001aae68:   1403b   ffc0001aae74 
<__d_lookup+0x84>
 *
 * See Documentation/filesystems/path-lookup.txt for more details.
 */
rcu_read_lock();

hlist_bl_for_each_entry_rcu(dentry, node, b, d_hash) {
ffc0001aae6c:   f9400273ldr x19, [x19]
ffc0001aae70:   b40001f3cbz x19, ffc0001aaeac 
<__d_lookup+0xbc>

if (dentry->d_name.hash != hash)
ffc0001aae74:   d1002274sub x20, x19, #0x8
ffc0001aae78:   b9402282ldr w2, [x20,#32] 
#faulted instruction


Then the problem should be caused by bad pointer of dcache.

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

Title:
  Oops __d_lookup+0x88/0x194

Status in The Linux Kernel:
  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

BTW, looks it isn't related with specific filesystem, and from the recent 
triger, it happened when
walking path inside proc filesystem:

[24993.562923] Call trace:
[24993.565357] [] __d_lookup+0x88/0x194
[24993.570467] [] d_lookup+0x38/0x64
[24993.575319] [] d_hash_and_lookup+0x54/0x6c
[24993.580948] [] proc_flush_task+0xa8/0x1a8
[24993.586491] [] release_task+0x5c/0x46c
[24993.591774] [] wait_task_zombie+0x140/0x67c
[24993.597489] [] wait_consider_task+0x388/0x670
[24993.603377] [] do_wait+0xe8/0x234
[24993.608229] [] SyS_wait4+0x7c/0xe8


Also from the link in #15, looks it is still triggered on arm64 from the 
register information
in the log.

So it might be one arm64 dependent issue.

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

Title:
  Oops __d_lookup+0x88/0x194

Status in The Linux Kernel:
  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ming Lei]

Looks there was similar report from upstream:

http://marc.info/?l=linux-fsdevel&m=142865378923064&w=2

but still don't have resolution or further report.


Also I tried to use fbench to create lots of files, list dirs concurently for 
reproducing
the issue, but can't reproduce it yet.

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

Title:
  Oops __d_lookup+0x88/0x194

Status in The Linux Kernel:
  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1455372] Re: Trusty arm64 VM doesn't support 'reboot' and 'powerdown'

[Ming Lei]

** Attachment added: "dmesg log of 'poweroff'"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4411589/+files/dmesg.log

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1455372

Title:
  Trusty arm64 VM doesn't support 'reboot' and 'powerdown'

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Trusty arm64/arm kernel can't support reboot and powerdown function.

  If user runs 'reboot', then finally the VM hangs in the last step
  instead of going another booting, and similar problem exists during
  powerdown.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460942] Re: crash: incompatible arguments: vmlinux is not SMP -- live system is SMP

[Ming Lei]

The problem can be fixed by applying the following commit:

commit db07dbf5a7e19806b1629bd4125e6643978c6f9f
Author: Dave Anderson 
Date:   Thu Feb 19 16:16:33 2015 -0500

Prepare for the future increment of Linux 3.x to 4.x.
(ander...@redhat.com)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460942

Title:
  crash: incompatible arguments:   vmlinux is not SMP -- live system is
  SMP

Status in crash package in Ubuntu:
  New

Bug description:
  
  When I build crash from wily, the failure in [1] can be
  triggered if the kernel is 4.0+.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...

  WARNING: kernels compiled by different gcc versions:
/home/ubuntu/vmlinux: (unknown)
live system kernel: 4.8.2

  WARNING: kernel version inconsistency between vmlinux and live memory

  crash: incompatible arguments: 
 /home/ubuntu/vmlinux is not SMP -- live system is SMP

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
crash [OPTION]... [NAMELIST](live system form)

  Enter "crash -h" for details.
  ubuntu@am2:~/git/crash-wily$

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460942] [NEW] crash: incompatible arguments: vmlinux is not SMP -- live system is SMP

[Ming Lei]

Public bug reported:


When I build crash from wily, the failure in [1] can be
triggered if the kernel is 4.0+.


[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 

crash 7.0.8
Copyright (C) 2002-2014  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu"...

WARNING: kernels compiled by different gcc versions:
  /home/ubuntu/vmlinux: (unknown)
  live system kernel: 4.8.2

WARNING: kernel version inconsistency between vmlinux and live memory

crash: incompatible arguments: 
   /home/ubuntu/vmlinux is not SMP -- live system is SMP

Usage:

  crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
  crash [OPTION]... [NAMELIST]  (live system form)

Enter "crash -h" for details.
ubuntu@am2:~/git/crash-wily$

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460942

Title:
  crash: incompatible arguments:   vmlinux is not SMP -- live system is
  SMP

Status in crash package in Ubuntu:
  New

Bug description:
  
  When I build crash from wily, the failure in [1] can be
  triggered if the kernel is 4.0+.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...

  WARNING: kernels compiled by different gcc versions:
/home/ubuntu/vmlinux: (unknown)
live system kernel: 4.8.2

  WARNING: kernel version inconsistency between vmlinux and live memory

  crash: incompatible arguments: 
 /home/ubuntu/vmlinux is not SMP -- live system is SMP

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
crash [OPTION]... [NAMELIST](live system form)

  Enter "crash -h" for details.
  ubuntu@am2:~/git/crash-wily$

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460941] [NEW] arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

Public bug reported:


After running crash from trusty, the failure log in [1] can be observed.

Then I built crash from wily directly, the similar failure[2] can be
observed too.


[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 

crash 7.0.3
Copyright (C) 2002-2013  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 

crash: invalid/unknown page size: 6144

[2] 
ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
[sudo] password for ubuntu: 

crash 7.0.8
Copyright (C) 2002-2014  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 

crash: invalid/unsupported page size: 6144

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  New

Bug description:
  
  After running crash from trusty, the failure log in [1] can be observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   

  crash: invalid/unknown page size: 6144

  [2] 
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
  [sudo] password for ubuntu: 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   

  crash: invalid/unsupported page size: 6144

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460941] Re: arm64: crash: invalid/unsupported page size: 6144

[Ming Lei]

The issue can be fixed by the following upstream commit:

commit 7623eee9046015b65a1f63f6bf07ab7805c36eb4
Author: Dave Anderson 
Date:   Tue May 19 10:20:04 2015 -0400

Fix for the ARM64 page size determination on Linux 4.1 and later
kernels.  Without the patch, the crash session fails during
initialization with the message "crash: invalid/unsupported page
size: 98304" on kernels with 64K pages.  On kernels with 4K pages,
the message is "crash: invalid/unsupported page size: 6144".  In
addition, the "-p " command line override option
had no effect on ARM64; that has been fixed as well.
(ander...@redhat.com)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1460941

Title:
  arm64: crash: invalid/unsupported page size: 6144

Status in crash package in Ubuntu:
  New

Bug description:
  
  After running crash from trusty, the failure log in [1] can be observed.

  Then I built crash from wily directly, the similar failure[2] can be
  observed too.

  
  [1] failure log
  ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux 

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   

  crash: invalid/unknown page size: 6144

  [2] 
  ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux 
  [sudo] password for ubuntu: 

  crash 7.0.8
  Copyright (C) 2002-2014  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   

  crash: invalid/unsupported page size: 6144

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1438585] Re: no console when starting VM from cloud image

[Ming Lei]

** Tags removed: verification-needed-trusty

** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1438585

Title:
  no console when starting VM from cloud image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  In current arm64 utopic cloud image, the 'console=' parameter has been
  removed from grub config, and always resort to 'stdout' DT property
  which is setup from QEMU.

  Unfortunately parsing 'stdout' DT property is just merged to 3.19
  kernel, so there is no console usable any more for arm64 utopic VM
  when booting via uefi/grub.

  SRU Justification:
  Impact: No console if arm64 Utopic based VM is booted from the cloud image.
  Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are 
cherry picked from 3.19 to Utopic, and the other one is backported by just 
dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can 
be booted with console.
  Testcase: Boot one arm64 Utopic VM via uefi/grub.

  5ba2ee8 of: support passing console options with stdout-path
  5c64126 of: add optional options parameter to of_find_node_by_path()
  7507839 of: Add bindings for chosen node, stdout-path
  54e15d7 of: correct of_console_check()'s return value
  4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path
  a699dfd of: Create of_console_check() for selecting a console specified in 
/chosen

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1438585] Re: no console when starting VM from cloud image

[Ming Lei]

[tom@vm-test]$vim arm64-qemu
[tom@vm-test]$./arm64-qemu
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.13.11-ckt20+ (tom@tom-T450) (gcc version 4.8.2 
20140110 (prerelease) [ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision 
205847] (Ubuntu/Linaro 4.8.2-13ubuntu1) ) #181 SMP PREEMPT Mon Jun 1 17:48:14 
CST 2015 ()
[0.00] CPU: AArch64 Processor [411fd070] revision 0
[0.00] Memory limited to 1024MB
[0.00] efi: Getting parameters from FDT:
[0.00] efi: Can't find System Table in device tree!
[0.00] On node 0 totalpages: 262144
[0.00]   DMA32 zone: 3584 pages used for memmap
[0.00]   DMA32 zone: 0 pages reserved
[0.00]   DMA32 zone: 262144 pages, LIFO batch:31
[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] PERCPU: Embedded 10 pages/cpu @ffc03ffda000 s10880 r8192 
d21888 u40960
[0.00] pcpu-alloc: s10880 r8192 d21888 u40960 alloc=10*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 258560
[0.00] Kernel command line: mem=1024M rootfstype=ext4 root=/dev/vda rw 
loglevel=9 no_console_suspend ip=dhcp
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[0.00] software IO TLB [mem 0x7b00-0x7f00] (64MB) mapped at 
[ffc03b00-ffc03eff]
[0.00] Memory: 938804K/1048576K available (3508K kernel code, 249K 
rwdata, 1324K rodata, 194K init, 1180K bss, 109772K reserved)
[0.00] Virtual kernel memory layout:
[0.00] vmalloc : 0xff80 - 0xffbb   (245759 
MB)
[0.00] vmemmap : 0xffbc00e0 - 0xffbc01c0   (14 
MB)
[0.00] modules : 0xffbffc00 - 0xffc0   (64 
MB)
[0.00] memory  : 0xffc0 - 0xffc04000   (  1024 
MB)
[0.00]   .init : 0xffc00053a000 - 0xffc00056aa80   (   195 
kB)
[0.00]   .text : 0xffc8 - 0xffc000539154   (  4837 
kB)
[0.00]   .data : 0xffc00056b000 - 0xffc0005a94e0   (   250 
kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[0.00] NR_IRQS:64 nr_irqs:64 0
[0.00] Architected cp15 timer(s) running at 62.50MHz (virt).
[0.00] sched_clock: 56 bits at 62MHz, resolution 16ns, wraps every 
219902322ns
[0.00] Console: colour dummy device 80x25
[0.00] console [tty0] enabled
[0.004477] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 125.00 BogoMIPS (lpj=625000)


** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1438585

Title:
  no console when starting VM from cloud image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  In current arm64 utopic cloud image, the 'console=' parameter has been
  removed from grub config, and always resort to 'stdout' DT property
  which is setup from QEMU.

  Unfortunately parsing 'stdout' DT property is just merged to 3.19
  kernel, so there is no console usable any more for arm64 utopic VM
  when booting via uefi/grub.

  SRU Justification:
  Impact: No console if arm64 Utopic based VM is booted from the cloud image.
  Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are 
cherry picked from 3.19 to Utopic, and the other one is backported by just 
dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can 
be booted with console.
  Testcase: Boot one arm64 Utopic VM via uefi/grub.

  5ba2ee8 of: support passing console options with stdout-path
  5c64126 of: add optional options parameter to of_find_node_by_path()
  7507839 of: Add bindings for chosen node, stdout-path
  54e15d7 of: correct of_console_check()'s return value
  4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path
  a699dfd of: Create of_console_check() for selecting a console specified in 
/chosen

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Un

[Kernel-packages] [Bug 1455372] Re: Trausty arm64 VM doesn't support 'reboot' and 'powerdown'

[Ming Lei]

[1]  kvm psci v0.2 patchset
http://comments.gmane.org/gmane.linux.ubuntu.devel.kernel.general/56676


** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current 
arm64 VM with the kvm psci v0.2 patchset"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4400724/+files/dmesg-after-applying-patches.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1455372

Title:
  Trausty arm64 VM doesn't support 'reboot' and 'powerdown'

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trusty arm64/arm kernel can't support reboot and powerdown function.

  If user runs 'reboot', then finally the VM hangs in the last step
  instead of going another booting, and similar problem exists during
  powerdown.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1455372] Re: Trausty arm64 VM doesn't support 'reboot' and 'powerdown'

[Ming Lei]

** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current 
arm64 VM"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4400723/+files/dmesg-before-applying-patches.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1455372

Title:
  Trausty arm64 VM doesn't support 'reboot' and 'powerdown'

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trusty arm64/arm kernel can't support reboot and powerdown function.

  If user runs 'reboot', then finally the VM hangs in the last step
  instead of going another booting, and similar problem exists during
  powerdown.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1455372] Re: Trausty arm64 VM doesn't support 'reboot' and 'powerdown'

[Ming Lei]

** Tags added: kernel-fixed-upstream

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1455372

Title:
  Trausty arm64 VM doesn't support 'reboot' and 'powerdown'

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trusty arm64/arm kernel can't support reboot and powerdown function.

  If user runs 'reboot', then finally the VM hangs in the last step
  instead of going another booting, and similar problem exists during
  powerdown.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp