[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

2018-01-12 Thread Dawei wang
My kernel version is linux-image-4.13.0-26-generic, reboot to old kernel
linux-headers-4.10.0-42-generic works.

-- 
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/1742721

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  I've updated the machine to the linux-hwe kernels, and experienced an
  almost instant crash when booting.  Nothing is shown on the VGA
  output, so no stack traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine

  So, it seems, the problem is fixed either in patches between 4.13.14
  and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
  kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742721/+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 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

2018-01-12 Thread Dawei wang
I got similar issue, the kernel encountered NULL dereference to null
error.

-- 
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/1742721

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  I've updated the machine to the linux-hwe kernels, and experienced an
  almost instant crash when booting.  Nothing is shown on the VGA
  output, so no stack traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine

  So, it seems, the problem is fixed either in patches between 4.13.14
  and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
  kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742721/+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 1679768] Re: Docker build hangs on XFS with kernel 4.10

2017-07-28 Thread Dawei wang
Got the same issue, when using rpm/yum in docker container with aufs and
xfs.

Switched docker to overlay2 and it worked.

-- 
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/1679768

Title:
  Docker build hangs on XFS with kernel 4.10

Status in docker.io package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have my docker partition on XFS, and recently upgraded to Zesty Beta.
  Most of my `docker build.` processes hangs with a similar message in syslog:

  ```
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171267] INFO: task 
kworker/1:3:5589 blocked for more than 120 seconds.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171275]   Tainted: P  
 O4.10.0-15-generic #17-Ubuntu
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171278] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171282] kworker/1:3 D0  
5589  2 0x
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171310] Workqueue: aufsd wkq_func 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171313] Call Trace:
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171323]  __schedule+0x233/0x6f0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171415]  ? 
kmem_zone_alloc+0x81/0x120 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171419]  schedule+0x36/0x80
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171423]  
rwsem_down_read_failed+0xfa/0x150
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171491]  ? 
xfs_file_buffered_aio_read+0x3d/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171496]  
call_rwsem_down_read_failed+0x18/0x30
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171500]  down_read+0x20/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171567]  xfs_ilock+0xf5/0x110 
[xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171628]  
xfs_file_buffered_aio_read+0x3d/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171686]  
xfs_file_read_iter+0x68/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171692]  new_sync_read+0xd2/0x120
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171695]  __vfs_read+0x26/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171697]  vfs_read+0x96/0x130
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171715]  vfsub_read_u+0x14/0x30 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171729]  vfsub_read_k+0x2c/0x40 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171743]  au_copy_file+0x10c/0x370 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171756]  
au_cp_regular+0x11a/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171767]  ? 
au_cp_regular+0x1ef/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171777]  ? 
au_cp_regular+0x188/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171788]  cpup_entry+0x538/0x5f0 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171802]  ? 
vfsub_lookup_one_len+0x31/0x70 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171814]  
au_cpup_single.constprop.18+0x145/0x6a0 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171820]  ? dput+0x40/0x270
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171831]  au_cpup_simple+0x4d/0x80 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171842]  
au_call_cpup_simple+0x28/0x40 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171855]  wkq_func+0x14/0x80 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171861]  
process_one_work+0x1fc/0x4b0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171864]  worker_thread+0x4b/0x500
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171870]  kthread+0x101/0x140
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171873]  ? 
process_one_work+0x4b0/0x4b0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171878]  ? 
kthread_create_on_node+0x60/0x60
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171883]  ? 
SyS_exit_group+0x14/0x20
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171887]  ret_from_fork+0x2c/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171895] INFO: task useradd:5758 
blocked for more than 120 seconds.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171899]   Tainted: P  
 O4.10.0-15-generic #17-Ubuntu
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1679768/+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