[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2019-07-24 Thread Brad Figg 
** Tags added: cscc

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:  c000f53cbc00 0001  
  GPR28: c000f53cbde0 00bf 0003

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2016-12-08 Thread Thadeu Lima de Souza Cascardo 
** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2016-10-06 Thread bugproxy 
** Tags removed: targetmilestone-inin14044
** Tags added: targetmilestone-inin---

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:  c000f53cbc00 0001

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2016-05-12 Thread Mathew Hodson 
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:  c000f53cbc00 0001

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2015-11-03 Thread bugproxy 
** Tags removed: targetmilestone-inin14043
** Tags added: targetmilestone-inin14044

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:  c000f53cbc00 0001

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2015-10-26 Thread bugproxy 
--- Comment From cdead...@us.ibm.com 2015-10-26 18:25 EDT---
 State: Assigned by: nguyenp on 26 October 2015 13:14:50 

Per sametime with Gabriel this morning,he's working and building a
workaround for to the problem.

I'm lowering the severity of the defect since it's not a blocker.

** Tags removed: severity-critical
** Tags added: severity-high

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12:

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2015-10-05 Thread Adam Conrad 
In the failure case, does the system literally have no serial ports left
(ie: is userspace incorrectly sending syscalls wildly into the ether
without checking), or is it that you're shuffling port assignments by
adding/removing ports, and we're now trying to configure a *different*
driver that doesn't take kindly to the old config?

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2015-09-03 Thread Leann Ogasawara 
** Changed in: linux (Ubuntu)
   Status: New => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d

[Kernel-packages] [Bug 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile

2015-09-02 Thread Luciano Chavez 
** Package changed: ubuntu => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  New

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24: