[Kernel-packages] [Bug 1304045] Re: rpciod: page alloc error no

[joh...@servergy.com]

Servergy went out of business in 2015 after SEC stock fraud scandal.
This bug is no longer relevant.

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

Title:
  rpciod: page alloc error no

Status in linux-ppc package in Ubuntu:
  New

Bug description:
  (saucy)root@jade-rev4:/home2/usbkey# [21841.439960] kworker/4:1: page 
allocation failure: order:0, mode:0x204000
  [21841.446658] CPU: 4 PID: 77 Comm: kworker/4:1 Tainted: GF
3.11.0-5-powerpc-e500mc #8-Ubuntu
  [21841.455917] Workqueue: rpciod rpc_async_schedule [sunrpc]
  [21841.461307] Call Trace:
  [21841.463749] [ea427bb0] [c00080fc] show_stack+0xfc/0x1c0 (unreliable)
  [21841.470100] [ea427c00] [c080ae6c] dump_stack+0x78/0xa0
  [21841.475233] [ea427c10] [c01651cc] warn_alloc_failed+0xfc/0x160
  [21841.481059] [ea427c70] [c01686c8] __alloc_pages_nodemask+0x678/0x880
  [21841.487407] [ea427d50] [c01af2b0] new_slab+0x290/0x2a0
  [21841.492538] [ea427d70] [c01b1070] __slab_alloc.constprop.64+0x3f0/0x500
  [21841.499143] [ea427df0] [c01b135c] __kmalloc+0x1dc/0x230
  [21841.504371] [ea427e10] [fa514cd8] rpc_malloc+0x48/0xa0 [sunrpc]
  [21841.510290] [ea427e20] [fa50b278] call_allocate+0xe8/0x160 [sunrpc]
  [21841.516556] [ea427e30] [fa5156c4] __rpc_execute+0x94/0x3b0 [sunrpc]
  [21841.522823] [ea427e80] [fa515a0c] rpc_async_schedule+0x2c/0x50 [sunrpc]
  [21841.529431] [ea427e90] [c007f8e0] process_one_work+0x150/0x3f0
  [21841.535255] [ea427ec0] [c00802b4] worker_thread+0x134/0x3e0
  [21841.540821] [ea427ef0] [c0088084] kthread+0xb4/0xc0
  [21841.545692] [ea427f40] [c001073c] ret_from_kernel_thread+0x5c/0x64
  [21841.551861] Mem-Info:
  [21841.554123] DMA per-cpu:
  [21841.556646] CPU0: hi:   90, btch:  15 usd:  78
  [21841.561426] CPU1: hi:   90, btch:  15 usd:   2
  [21841.566205] CPU2: hi:   90, btch:  15 usd:  79
  [21841.570985] CPU3: hi:   90, btch:  15 usd:  67
  [21841.575764] CPU4: hi:   90, btch:  15 usd:  14
  [21841.580543] CPU5: hi:   90, btch:  15 usd:   0
  [21841.585323] CPU6: hi:   90, btch:  15 usd:  55
  [21841.590102] CPU7: hi:   90, btch:  15 usd:  75
  [21841.594881] HighMem per-cpu:
  [21841.597751] CPU0: hi:  186, btch:  31 usd:   0
  [21841.602530] CPU1: hi:  186, btch:  31 usd: 180
  [21841.607309] CPU2: hi:  186, btch:  31 usd:   0
  [21841.612089] CPU3: hi:  186, btch:  31 usd:   0
  [21841.616868] CPU4: hi:  186, btch:  31 usd:   0
  [21841.621648] CPU5: hi:  186, btch:  31 usd:   0
  [21841.626427] CPU6: hi:  186, btch:  31 usd:   0
  [21841.631206] CPU7: hi:  186, btch:  31 usd: 169
  [21841.635991] active_anon:20771 inactive_anon:21077 isolated_anon:0
  [21841.635991]  active_file:452533 inactive_file:476704 isolated_file:6
  [21841.635991]  unevictable:0 dirty:0 writeback:0 unstable:0
  [21841.635991]  free:7239714 slab_reclaimable:38857 slab_unreclaimable:9994
  [21841.635991]  mapped:16084 shmem:336 pagetables:1476 bounce:0
  [21841.635991]  free_cma:0
  [21841.668561] DMA free:27984kB min:2252kB low:2812kB high:3376kB 
active_anon:0kB inactive_anon:0kB active_file:33552kB inactive_file:33484kB 
unevictable:0kB isolated(anon):0kB isolated(file):24kB present:786432kB 
managed:317684kB mlocked:0kB dirty:0kB writeback:0kB mapped:8kB shmem:0kB 
slab_reclaimable:155428kB slab_unreclaimable:36288kB kernel_stack:2384kB 
pagetables:5904kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB 
pages_scanned:0 all_unreclaimable? no
  [21841.709623] lowmem_reserve[]: 0 0 32000 32000
  [21841.713988] HighMem free:28934512kB min:512kB low:58676kB high:116840kB 
active_anon:83084kB inactive_anon:84308kB active_file:1776580kB 
inactive_file:1873332kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:32768000kB managed:32768000kB mlocked:0kB dirty:0kB writeback:0kB 
mapped:64328kB shmem:1344kB slab_reclaimable:0kB slab_unreclaimable:0kB 
kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [21841.756438] lowmem_reserve[]: 0 0 0 0
  [21841.760099] DMA: 1338*4kB (UEM) 448*8kB (UEM) 213*16kB (UEM) 160*32kB 
(UEM) 61*64kB (UEM) 14*128kB (UEM) 9*256kB (UEM) 0*512kB 0*1024kB 0*2048kB 
1*4096kB (R) = 29560kB
  [21841.775088] HighMem: 515*4kB (UM) 1221*8kB (UM) 95*16kB (UM) 61*32kB (UM) 
43*64kB (UM) 18*128kB (UM) 12*256kB (UM) 7*512kB (M) 5*1024kB (M) 5*2048kB (UM) 
7054*4096kB (UMR) = 28935556kB
  [21841.791561] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=4096kB
  [21841.799986] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=16384kB
  [21841.808499] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=65536kB
  [21841.817011] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=262144kB
  [21841.825610] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 

[Kernel-packages] [Bug 1276290] Re: Oops in rpc_remove_client_dir (NFS mount)

[joh...@servergy.com]

Servergy went out of business in 2015 after SEC stock fraud scandal.
This bug is no longer relevant.

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

Title:
  Oops in  rpc_remove_client_dir (NFS mount)

Status in linux-ppc package in Ubuntu:
  New

Bug description:

  Multiple Oops  in NFS unmount  during shutdown (saucy rel )

  3.11.0-5-powerpc-e500mc #8-Ubuntu


  (saucy)root@(none):/work/svy/tools#  * Stopping MD monitoring service mdadm 
--monitor[ 
OK ]
   * Asking all remaining processes to terminate...[ OK 
]
   * All processes ended within 1 seconds...   [ OK 
]
  [65426.692405] Oops: Exception in kernel mode, sig: 11 [#1]
  [65426.697721] SMP NR_CPUS=8 P4080 DS
  [65426.701122] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) 
ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) 
libcrc32c(F) reiserfs(F) nls_iso8859_1(F) nls_cp437(F) vfat(F) fat(F) 
dm_multipath(F) scsi_dh(F) usb_storage(F) ext2(F) rpcsec_gss_krb5(F) nfsv4(F) 
nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) 
ofpart(F) redboot(F) cmdlinepart(F) cfi_cmdset_0002(F) cfi_probe(F) cfi_util(F) 
gen_probe(F) physmap_of(F) map_funcs(F) chipreg(F) mtd(F) lm90(F) at24(F) 
caam(F) i2c_mpc(F) mpc85xx_edac(F) edac_core(F) uio_pdrv_genirq(F) uio(F) 
ata_generic(F) ahci(F) libahci(F) pata_jmicron(F) fsl_pq_mdio(F)
  [65426.759065] CPU: 6 PID: 19006 Comm: umount.nfs Tainted: GF
3.11.0-5-powerpc-e500mc #8-Ubuntu
  [65426.768461] task: ea0f3900 ti: ea05c000 task.ti: ea05c000
  [65426.773858] NIP: f99a0f50 LR: f998250c CTR: c07f85c0
  [65426.778820] REGS: ea05dda0 TRAP: 0700   Tainted: GF 
(3.11.0-5-powerpc-e500mc)
  [65426.786998] MSR: 00029002   CR: 24000422  XER: 2000
  [65426.793107]
  GPR00: f9982d20 ea05de50 ea0f3900 e7e66ee0 00029002 0001  
  GPR08: eadc2504   0001 c07f85c0 1002e3ac 1001 8000
  GPR16: 100112e4 1000f3c4 1000f3e0 1000f594 1000f59c 1000f440 c0b4fb6c 1001
  GPR24: 1001  c0089180 ea05de84 f99ab064 ea2bf500 c0b41380 ea54ef00
  [65426.822949] NIP [f99a0f50] rpc_remove_client_dir+0x0/0x30 [sunrpc]
  [65426.829143] LR [f998250c] __rpc_clnt_remove_pipedir+0x5c/0x80 [sunrpc]
  [65426.835668] Call Trace:
  [65426.838128] [ea05de50] [f999f9f0] rpc_get_sb_net+0x70/0xa0 [sunrpc] 
(unreliable)
  [65426.845542] [ea05de60] [f9982d20] rpc_free_client+0x50/0xa0 [sunrpc]
  [65426.851910] [ea05de70] [f9982c58] rpc_shutdown_client+0x68/0xe0 [sunrpc]
  [65426.858647] [ea05dec0] [f9a3fd04] nfs_free_server+0x124/0x190 [nfs]
  [65426.864920] [ea05dee0] [c01c5f34] deactivate_locked_super+0x74/0xa0
  [65426.871193] [ea05def0] [c01e9184] SyS_umount+0x94/0x3d0
  [65426.876422] [ea05df40] [c0010604] ret_from_syscall+0x0/0x3c
  [65426.882002] --- Exception: c01 at 0xfec55dc
  [65426.882002] LR = 0xff88d54
  [65426.889225] Instruction dump:
  [65426.892191] 1b50 aa32 0706 0120 aa36 0706 1af8 
aa3a
  [65426.899964] 0706 1aa0 aa46 0704 <0058> aa4a 
0704 1b74
  [65426.907949] udlfb: /dev/fb0 FB_BLANK mode 1 --> 0
  [65426.912666] udlfb: set_par mode 1024x768
  [65426.927196] ---[ end trace b25b3039b99e0391 ]---
  [65426.931816]
  umount.nfs: /work: not mounted
  [65426.960296] init: idmapd main process (2394) killed by TERM signal
  [65426.983998] init: systemd-logind main process (544) killed by TERM signal

  Oops #2

  [65426.994070] Oops: Exception in kernel mode, sig: 11 [#2]
  [65426.999386] SMP NR_CPUS=8 P4080 DS
  [65427.002787] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) 
ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) 
libcrc32c(F) reiserfs(F) nls_iso8859_1(F) nls_cp437(F) vfat(F) fat(F) 
dm_multipath(F) scsi_dh(F) usb_storage(F) ext2(F) rpcsec_gss_krb5(F) nfsv4(F) 
nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) 
ofpart(F) redboot(F) cmdlinepart(F) cfi_cmdset_0002(F) cfi_probe(F) cfi_util(F) 
gen_probe(F) physmap_of(F) map_funcs(F) chipreg(F) mtd(F) lm90(F) at24(F) 
caam(F) i2c_mpc(F) mpc85xx_edac(F) edac_core(F) uio_pdrv_genirq(F) uio(F) 
ata_generic(F) ahci(F) libahci(F) pata_jmicron(F) fsl_pq_mdio(F)
  [65427.060734] CPU: 7 PID: 19014 Comm: umount Tainted: GF D  
3.11.0-5-powerpc-e500mc #8-Ubuntu
  [65427.069783] task: e5d55580 ti: ea2f task.ti: ea2f
  [65427.075180] NIP: f99a0270 LR: c01c5f34 CTR: f99a0270
  [65427.080142] REGS: ea2f1e30 TRAP: 0700   Tainted: GF D   
(3.11.0-5-powerpc-e500mc)
  [65427.088320] MSR: 00029002   CR: 24004424  XER: 
  [65427.094430]
  GPR00: c01c5f24 ea2f1ee0 e5d55580 ea1e7800 c1d404e0 ea027a80 c01e7b78 0001
  GPR08:  f99a0270  

[Kernel-packages] [Bug 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks

[joh...@servergy.com]

Servergy went out of business in 2015 after SEC stock fraud scandal.
This bug is no longer relevant.

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1279403] Re: udlfd video driver hangs " BUG: scheduling while atomic " iscsi booted initrd : (trusty)

[joh...@servergy.com]

Servergy closed in 2015 after SEC stock fraud scandal. This bug is no
longer relevant.

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

Title:
  udlfd video driver hangs " BUG: scheduling while atomic "   iscsi
  booted initrd : (trusty)

Status in linux package in Ubuntu:
  Triaged
Status in linux-ppc package in Ubuntu:
  Triaged

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   -> This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 &
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 -> System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 &
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

-> System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 &
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

  < hung >

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279403/+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 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275

[joh...@servergy.com]

This fix needs applied to a ISO image ; Where can I find that image at ?

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

Title:
  book3e bootloader recommendation should point to grub-ieee1275

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  The original idea of a grub-kexec never happened. These platforms need at
  least grub-ieee1275 to generate grub.cfg, so recommended that instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+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 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275

[joh...@servergy.com]

Hi,
 This change needs applied to a ISO image for installation; Where can
I locate that image ?

Regards,
 John.

--

o Energy-efficiency is #1 reason data centers look to expand.  --
Digital Realty Trust
o Green Data Centers spending to increase 300% worldwide by 2016.  --
Pike Research
o Data Centers have become as vital to the functioning of society as
power stations.  -- The Economist


On Thu, May 29, 2014 at 7:55 AM, Luis Henriques
luis.henriq...@canonical.com wrote:
 This bug is awaiting verification that the kernel in -proposed solves
 the problem. Please test the kernel and update this bug with the
 results. If the problem is solved, change the tag 'verification-needed-
 trusty' to 'verification-done-trusty'.

 If verification is not done by 5 working days from today, this fix will
 be dropped from the source code, and this bug will be closed.

 See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
 to enable and use -proposed. Thank you!


 ** Tags added: verification-needed-trusty

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1317925).
 https://bugs.launchpad.net/bugs/1318629

 Title:
   book3e bootloader recommendation should point to grub-ieee1275

 Status in “linux” package in Ubuntu:
   Fix Released
 Status in “linux” source package in Trusty:
   Fix Committed
 Status in “linux” source package in Utopic:
   Fix Released

 Bug description:
   The original idea of a grub-kexec never happened. These platforms need at
   least grub-ieee1275 to generate grub.cfg, so recommended that instead.

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

Title:
  book3e bootloader recommendation should point to grub-ieee1275

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  The original idea of a grub-kexec never happened. These platforms need at
  least grub-ieee1275 to generate grub.cfg, so recommended that instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+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 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275

[joh...@servergy.com]

The ISO  procedure for https://wiki.ubuntu.com/Testing/QATracker is
based on Intel x86 using virtbox. It does not address ppc test cases.

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

Title:
  book3e bootloader recommendation should point to grub-ieee1275

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  The original idea of a grub-kexec never happened. These platforms need at
  least grub-ieee1275 to generate grub.cfg, so recommended that instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+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 1279403] Re: udlfd video driver hangs BUG: scheduling while atomic iscsi booted initrd : (trusty)

[joh...@servergy.com]

** Summary changed:

- udlfd video driver hangs in iscsi booted initrd : (trusty)
+ udlfd video driver hangs  BUG: scheduling while atomiciscsi booted 
initrd : (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/1279403

Title:
  udlfd video driver hangs  BUG: scheduling while atomiciscsi
  booted initrd : (trusty)

Status in “linux” package in Ubuntu:
  Triaged
Status in “linux-ppc” package in Ubuntu:
  Triaged

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279403/+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 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)

[joh...@servergy.com]

i back ported a fix from Alexander Holler:

The console functions are using spinlocks while calling fb-driver ops
but udlfb waits for a semaphore in many ops. This results in the BUG
scheduling while atomic. One of those call flows is e.g.

vt_console_print() (spinlock printing_lock)
(...)
dlfb_ops_imageblit()
dlfb_handle_damage()
dlfb_get_urb()
down_timeout(semaphore)
BUG: scheduling while atomic
(...)
vt_console_print() (release spinlock printing_lock)

Fix this through a workqueue for dlfb_handle_damage().

Cc: stable at vger.kernel.org
Signed-off-by: Alexander Holler holler at ahsoftware.de


And it cured the hang.

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

Title:
  udlfd video driver hangs in iscsi booted initrd : (trusty)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+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 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)

[joh...@servergy.com]

** Patch added: Patch for system hang
   
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+attachment/4121466/+files/video.patch

** Summary changed:

- tg3 driver hangs in iscsi booted initrd : (trusty)
+ udlfd video driver hangs in iscsi booted initrd : (trusty)

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

Title:
  udlfd video driver hangs in iscsi booted initrd : (trusty)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+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 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)

[joh...@servergy.com]

Seems the video driver calling timeout in the wrong context  is the root cause:

[   45.638269] Call Trace:
4[   45.638273] [e69a38a0] [c00080bc] show_stack+0xfc/0x1c0 (unreliable)
4[   45.638277] [e69a38f0] [c07fd050] dump_stack+0x78/0xa0
4[   45.638285] [e69a3900] [c008eb50] dequeue_task_idle+0x40/0x60
4[   45.638288] [e69a3910] [c07ebc7c] __schedule+0x4dc/0x780
4[   45.638292] [e69a3a20] [c07eaf64] schedule_timeout+0x144/0x260
4[   45.638295] [e69a3a80] [c07ee368] __down_timeout+0x78/0xc0
4[   45.638299] [e69a3ab0] [c00a1834] down_timeout+0x74/0x80
4[   45.638303] [e69a3ad0] [c0439f0c] dlfb_get_urb+0x2c/0xc0
4[   45.638306] [e69a3af0] [c043b5e4] dlfb_handle_damage.isra.3+0xa4/0x1f0
4[   45.638309] [e69a3b30] [c0419934] soft_cursor+0x1b4/0x2a0
4[   45.638313] [e69a3b60] [c041935c] bit_cursor+0x52c/0x550
4[   45.638316] [e69a3bf0] [c0415400] fbcon_cursor+0x130/0x1b0
4[   45.638319] [e69a3c20] [c046f098] vt_console_print+0x248/0x4a0
4[   45.638322] [e69a3c70] [c00a6ab0] 
call_console_drivers.constprop.18+0xf0/0x170
4[   45.638325] [e69a3c90] [c00a73a4] console_unlock+0x474/0x4a0
4[   45.638329] [e69a3cc0] [c00a76c4] vprintk_emit+0x2f4/0x500
4[   45.638332] [e69a3d10] [c0499018] dev_vprintk_emit+0x58/0x70
4[   45.638336] [e69a3db0] [c0499084] dev_printk_emit+0x54/0x70
4[   45.638339] [e69a3de0] [c06db0a4] netdev_info+0x74/0x90
4[   45.638346] [e69a3e20] [f1c6ead8] tg3_link_report+0xb8/0x170 [tg3]
4[   45.638351] [e69a3e30] [f1c6f888] tg3_test_and_report_link_chg+0x58/0xa0 
[tg3]
4[   45.638358] [e69a3e40] [f1c79ef4] tg3_setup_phy+0xf74/0x2450 [tg3]
4[   45.638364] [e69a3ee0] [f1c7f6b8] tg3_poll+0x398/0x430 [tg3]
4[   45.638367] [e69a3f30] [c06d9954] net_rx_action+0x144/0x250
4[   45.638370] [e69a3f80] [c0055758] __do_softirq+0x118/0x2b0
4[   45.638374] [e69a3fe0] [c0055d04] irq_exit+0xb4/0xf0
4[   45.638377] [e69a3ff0] [c000e8d0] call_do_irq+0x24/0x3c
4[   45.638380] [c0b75e90] [c00054c8] do_IRQ+0x98/0x110
4[   45.638383] [c0b75eb0] [c0010bfc] ret_from_except+0x0/0x18
4[   45.638388] --- Exception: 501 at arch_cpu_idle+0x30/0x80
4[   45.638388] LR = arch_cpu_idle+0x30/0x80
4[   45.638392] [c0b75f70] [c00b5bd8] rcu_idle_enter+0xb8/0x100 (unreliable)
4[   45.638395] [c0b75f80] [c00a93a0] cpu_startup_entry+0x160/0x260
4[   45.638398] [c0b75fc0] [c0a887ec] start_kernel+0x33c/0x350
4[   45.638401] [c0b75ff0] [c3fc] skpinv+0x2e8/0x324
1[   45.638412] Unable to handle kernel paging request for instruction fetch
1[   45.638413] Faulting instruction address: 0x
[dumpcommon]kdb   -bt

Stack traceback for pid 74
0xe62b8000   742  11   R  0xe62b8340 *kworker/1:1
Call Trace:
[e63978e0] [c00080bc] show_stack+0xfc/0x1c0 (unreliable)
[e6397930] [c00fcb28] kdb_show_stack+0x88/0xb0
[e6397950] [c00fcc04] kdb_bt1.isra.0+0xb4/0x140
[e6397980] [c00fd010] kdb_bt+0x380/0x450
[e6397a10] [c00f9c50] kdb_parse+0x270/0x720
[e6397a60] [c00fa1d4] kdb_exec_defcmd+0xd4/0x140
[e6397a80] [c00f9c50] kdb_parse+0x270/0x720
[e6397ad0] [c00fa7b8] kdb_main_loop+0x348/0x7c0
[e6397b30] [c00fdee8] kdb_stub+0x248/0x4c0
[e6397b70] [c00f2a10] kgdb_cpu_enter+0x3c0/0x6a0
[e6397bd0] [c00f30a0] kgdb_handle_exception+0x1c0/0x220
[e6397c20] [c0011a04] kgdb_debugger+0x94/0xb0
[e6397c30] [c000bd3c] die+0x2ec/0x310
[e6397c60] [c0010a68] handle_page_fault+0x7c/0x80
--- Exception: 400 at   (null)
LR = ttwu_activate+0x28/0x70
[e6397d30] [c0088e70] ttwu_do_activate+0x50/0x70
[e6397d50] [c0088ff4] sched_ttwu_pending+0x84/0xb0
[e6397d70] [c0089f10] scheduler_ipi+0x60/0x190
[e6397d90] [c00126d0] smp_ipi_demux+0xa0/0xf0
[e6397db0] [c0010250] doorbell_exception+0x70/0xa0
[e6397dd0] [c0010bb0] ret_from_except_full+0x0/0x4c
--- Exception: 2070 at linkwatch_event+0x0/0x50
LR = process_one_work+0x14c/0x3e0
[e6397e90] [c006fef8] process_one_work+0x128/0x3e0 (unreliable)

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

Title:
  tg3 driver hangs in iscsi booted initrd : (trusty)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 

[Kernel-packages] [Bug 1322270] [NEW] Enabling lock checking in ppc-e500mc produces bug checks

[joh...@servergy.com]

Public bug reported:

Building a 3.13.24. kernel with lock checking enabled produces Oops ;

See console log for example

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
Uname: Linux 3.13.0-24-powerpc-e500mc ppc
ApportVersion: 2.14.1-0ubuntu3
Architecture: powerpc
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Thu May 22 11:54:41 2014
Lsusb:
 Bus 002 Device 002: ID 17e9:047b DisplayLink 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 udlfb
ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
WifiSyslog:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: apport-bug powerpc 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/1322270

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Building a 3.13.24. kernel with lock checking enabled produces Oops ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks

[joh...@servergy.com]

[   11.158704] usb usb2: Product: Freescale On-Chip EHCI Host Controller
[   11.158704] usb usb2: Product: Freescale On-Chip EHCI Host Controller
[   11.171577] usb usb2: Manufacturer: Linux 3.13.9+ ehci_hcd
[   11.171577] usb usb2: Manufacturer: Linux 3.13.9+ ehci_hcd
[   11.182539] usb usb2: SerialNumber: fsl-ehci.1
[   11.182539] usb usb2: SerialNumber: fsl-ehci.1
[   11.191762] hub 2-0:1.0: in hub_probe 
[   11.191762] hub 2-0:1.0: in hub_probe 
[   11.199264] hub 2-0:1.0: USB hub found
[   11.199264] hub 2-0:1.0: USB hub found
[   11.206778] hub 2-0:1.0: 1 port detected
[   11.206778] hub 2-0:1.0: 1 port detected
[   11.215272] mousedev: PS/2 mouse device common for all mice
[   11.215272] mousedev: PS/2 mouse device common for all mice
[   11.227120] device-mapper: uevent: version 1.0.3
[   11.227120] device-mapper: uevent: version 1.0.3
[   11.236595] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: 
dm-de...@redhat.com
[   11.236595] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: 
dm-de...@redhat.com
[   11.253536] ledtrig-cpu: registered to indicate activity on CPUs
[   11.253536] ledtrig-cpu: registered to indicate activity on CPUs
[   11.265788] BUG: key deadbeef not in .data!
[   11.265788] BUG: key deadbeef not in .data!
[   11.274148] DEBUG_LOCKS_WARN_ON(1)[   11.274148] DEBUG_LOCKS_WARN_ON(1)
Entering kdb (current=0xe60a8000, pid 1) 
Entering kdb (current=0xe60a8000, pid 1) on processor 1 on processor 1 Oops: 
(null)
Oops: (null)
due to oops @ 0xc00a650c
due to oops @ 0xc00a650c
dCPU: 1 PID: 1 Comm: swapper/1 Not tainted 3.13.9+ #4
dCPU: 1 PID: 1 Comm: swapper/1 Not tainted 3.13.9+ #4
dtask: e60a8000 ti: e609e000 task.ti: e609e000
dtask: e60a8000 ti: e609e000 task.ti: e609e000
NIP: c00a650c LR: c00a650c CTR: c04281e0
NIP: c00a650c LR: c00a650c CTR: c04281e0
REGS: e609fc40 TRAP: 0700   Not tainted  (3.13.9+)
REGS: e609fc40 TRAP: 0700   Not tainted  (3.13.9+)
MSR: 00029002 MSR: 00029002 CECE,EE,EE,ME,ME  CR: 22ad2e82  XER: 
  CR: 22ad2e82  XER: 

GPR00: 
GPR00: c00a650c c00a650c e609fcf0 e609fcf0 e60a8000 e60a8000 0016 0016 
0001 0001 c00af694 c00af694   0001 0001 
GPR08: 
GPR08:         
22ad2e84 22ad2e84   c0002cc0 c0002cc0   
GPR16: 
GPR16:       0100 0100 
c06b1cf0 c06b1cf0 c09fc134 c09fc134 c0bd45b4 c0bd45b4 c08a6564 c08a6564 
GPR24: 
GPR24: e6293400 e6293400 c08a6554 c08a6554   e1c77aa0 e1c77aa0 
  c0bd c0bd e1c77af8 e1c77af8 deadbeef deadbeef 

NIP [c00a650c] lockdep_init_map+0x31c/0x4a0
NIP [c00a650c] lockdep_init_map+0x31c/0x4a0
LR [c00a650c] lockdep_init_map+0x31c/0x4a0
LR [c00a650c] lockdep_init_map+0x31c/0x4a0
Call Trace:
Call Trace:
[e609fcf0] [c00a650c] lockdep_init_map+0x31c/0x4a0[e609fcf0] [c00a650c] 
lockdep_init_map+0x31c/0x4a0 (unreliable) (unreliable)

[e609fd30] [c0245500] sysfs_add_file_mode_ns+0x70/0x110[e609fd30]
[c0245500] sysfs_add_file_mode_ns+0x70/0x110

[e609fd60] [c02489c0] internal_create_group+0x110/0x2f0[e609fd60]
[c02489c0] internal_create_group+0x110/0x2f0

[e609fda0] [c06b20e4] of_fsl_bman_probe+0x2b4/0x340[e609fda0] [c06b20e4]
of_fsl_bman_probe+0x2b4/0x340

[e609fde0] [c04bb0b4] platform_drv_probe+0x34/0x80[e609fde0] [c04bb0b4]
platform_drv_probe+0x34/0x80

[e609fdf0] [c04b8c8c] driver_probe_device+0xbc/0x3d0[e609fdf0]
[c04b8c8c] driver_probe_device+0xbc/0x3d0

[e609fe10] [c04b90fc] __driver_attach+0xdc/0xe0[e609fe10] [c04b90fc]
__driver_attach+0xdc/0xe0

more more [e609fe30] [c04b647c] bus_for_each_dev+0x7c/0xd0[e609fe30]
[c04b647c] bus_for_each_dev+0x7c/0xd0

more more 
Only 'q' or 'Q' are processed at more prompt, input ignored

Only 'q' or 'Q' are processed at more prompt, input ignored
[e609fe60] [c04b7f88] bus_add_driver+0x198/0x290[e609fe60] [c04b7f88] 
bus_add_driver+0x198/0x290

[e609fe80] [c04b96f4] driver_register+0x94/0x150[e609fe80] [c04b96f4]
driver_register+0x94/0x150

[e609fe90] [c0002528] do_one_initcall+0x128/0x1f0[e609fe90] [c0002528]
do_one_initcall+0x128/0x1f0

[e609ff00] [c0acc9cc] kernel_init_freeable+0x1c4/0x260[e609ff00]
[c0acc9cc] kernel_init_freeable+0x1c4/0x260

[e609ff30] [c0002ce0] kernel_init+0x20/0x140[e609ff30] [c0002ce0]
kernel_init+0x20/0x140

[e609ff40] [c00106d0] ret_from_kernel_thread+0x5c/0x64[e609ff40]
[c00106d0] ret_from_kernel_thread+0x5c/0x64

Instruction dump:Instruction dump:

48313515 48313515 2f83 2f83 41defd8c 41defd8c 3d20c0bd 3d20c0bd
812944a0 812944a0 2f89 2f89 40fefd7c 40fefd7c 3c60c09e 3c60c09e

3c80c0a5 3c80c0a5 38849a44 38849a44 3863b8c4 3863b8c4 48785395 48785395
0fe0 0fe0 4bfffd60 4bfffd60 93de 93de 7fc3f378
7fc3f378


[1]kdb [1]kdb tt


** Attachment added: entire console log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+attachment/4117723/+files/console-1322270.txt

** 

[Kernel-packages] [Bug 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks

[joh...@servergy.com]

apport information

** Tags added: apport-collected

** Description changed:

  Building a 3.13.0.24. kernel with lock checking enabled produces Oops ;
  
  See console log for example
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3
+ Architecture: powerpc
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CurrentDesktop: XFCE
+ CurrentDmesg:
+  Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
+  dmesg: write failed: Broken pipe
+ DistroRelease: Ubuntu 14.04
+ Lsusb:
+  Bus 002 Device 002: ID 17e9:047b DisplayLink 
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 udlfb
+ ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
+ ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
+ RfKill:
+  
+ Tags:  trusty
+ Uname: Linux 3.13.0-24-powerpc-e500mc ppc
+ UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
+ UserGroups: wireshark
+ WifiSyslog:
+  
+ _MarkForUpload: True

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117724/+files/AlsaInfo.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission 

[Kernel-packages] [Bug 1322270] UdevLog.txt

[joh...@servergy.com]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117734/+files/UdevLog.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] ProcCpuinfo.txt

[joh...@servergy.com]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117729/+files/ProcCpuinfo.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] IwConfig.txt

[joh...@servergy.com]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117727/+files/IwConfig.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] ProcModules.txt

[joh...@servergy.com]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117731/+files/ProcModules.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] PulseList.txt

[joh...@servergy.com]

apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117732/+files/PulseList.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] Lspci.txt

[joh...@servergy.com]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1322270/+attachment/4117728/+files/Lspci.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] HookError_source_linux.txt

[joh...@servergy.com]

apport information

** Attachment added: HookError_source_linux.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117726/+files/HookError_source_linux.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] UdevDb.txt

[joh...@servergy.com]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1322270/+attachment/4117733/+files/UdevDb.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] CRDA.txt

[joh...@servergy.com]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1322270/+attachment/4117725/+files/CRDA.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] ProcInterrupts.txt

[joh...@servergy.com]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1322270/+attachment/4117730/+files/ProcInterrupts.txt

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

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks

[joh...@servergy.com]

set CONFIG_DEBUG_LOCK_ALLOC =y   in .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/1322270

Title:
  Enabling lock checking in ppc-e500mc produces bug checks

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Building a 3.13.0.24. kernel with lock checking enabled produces Oops
  ;

  See console log for example

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu May 22 11:54:41 2014
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  WifiSyslog:
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  Lsusb:
   Bus 002 Device 002: ID 17e9:047b DisplayLink 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 udlfb
  ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc 
root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 
nomdmonddf nomdmonisw  sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 
fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022
  ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-24-powerpc-e500mc ppc
  UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago)
  UserGroups: wireshark
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+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 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)

[joh...@servergy.com]

I enabled kgdboc=ttyS0,115200 and caught this :


[   71.145241] input: Barcode Reader  as 
/devices/ffe00.soc/ffe21.usb/fsl-ehci.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input1
[   71.145493] hid-generic 0003:13BA:0018.0002: input,hidraw1: USB HID v1.10 
Mouse [Barcode Reader ] on usb-fsl-ehci.0-1.3/input1
[   71.206233] md: raid6 personality registered for level 6
[   71.206235] md: raid5 personality registered for level 5
[   71.206236] md: raid4 personality registered for level 4
[   71.260531] md: raid10 personality registered for level 10
[   71.664609] udlfb: DisplayLink USB device /dev/fb0 attached. 1440x900 
resolution. Using 5064K framebuffer memory
[   71.934176] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[   72.083988] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[   73.549288] tg3 :01:00.0 eth2: Link is up at 100 Mbps, full duplex

Entering kdb (current=0xe62b8000, pid 74) on processor 1 Oops: (null)
due to oops @ 0x0
dCPU: 1 PID: 74 Comm: kworker/1:1 Tainted: GW3.13.9+ #3
dWorkqueue: events linkwatch_event
dtask: e62b8000 ti: e6396000 task.ti: e6396000
NIP:  LR: c00885ac CTR: 
REGS: e6397ca0 TRAP: 0400   Tainted: GW (3.13.9+)
MSR: 00021002 CE,ME  CR: 22ad2e28  XER: 

GPR00: c00885ac e6397d50 e62b8000 d1826900 c0b0b340 0005 448130bc 0011 
GPR08:   0011 204c2f00   c0078250 e62c7920 
GPR16:        d1826680 
GPR24: c0b6 10d2 c0b06900 c0b06900 c0b80e18 e6396000 d1826900 c0b0b340 
NIP []   (null)
LR [c00885ac] ttwu_do_activate.constprop.70+0x4c/0x90
Call Trace:
[e6397d50] [c00885ac] ttwu_do_activate.constprop.70+0x4c/0x90 (unreliable)
[e6397d60] [c0089d80] scheduler_ipi+0xb0/0x1e0
[e6397d90] [c00126d0] smp_ipi_demux+0xa0/0xf0
[e6397db0] [c0010250] doorbell_exception+0x70/0xa0
[e6397dd0] [c0010bb0] ret_from_except_full+0x0/0x4c
--- Exception: 2070 at linkwatch_event+0x0/0x50
LR = process_one_work+0x14c/0x3e0
[e6397e90] [c006fef8] process_one_work+0x128/0x3e0 (unreliable)
[e6397ec0] [c00708d4] worker_thread+0x134/0x3e0
[e6397ef0] [c0078324] kthread+0xd4/0xf0
[e6397f40] [c001068c] ret_from_kernel_thread+0x5c/0x64

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

Title:
  tg3 driver hangs in iscsi booted initrd : (trusty)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 

[Kernel-packages] [Bug 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275

[joh...@servergy.com]

Hi;

How and when will this be implemented ?

Will  future 3.13.0-24-powerpc-e500mc installs configure grub.cfg ?

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

Title:
  book3e bootloader recommendation should point to grub-ieee1275

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Committed

Bug description:
  The original idea of a grub-kexec never happened. These platforms need at
  least grub-ieee1275 to generate grub.cfg, so recommended that instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+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 1279403] Re: tg3 driver hangs in iscsi booted initrd : (saucy)

[joh...@servergy.com]

retested with Trusty kernel 3-13-0-24  by doing a direct install to a
iSCSI target;


 Stiil hangs ;

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

Title:
  tg3 driver hangs in iscsi booted initrd : (saucy)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+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 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)

[joh...@servergy.com]

** Summary changed:

- tg3 driver hangs in iscsi booted initrd : (saucy) 
+ tg3 driver hangs in iscsi booted initrd : (trusty)

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

Title:
  tg3 driver hangs in iscsi booted initrd : (trusty)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+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 1313888] Re: ppc : Trusty ISO install fails booted from CD

[joh...@servergy.com]

It appears the root cause is the CD is not being detected in Linux -
/dev/sr0 - that is attached to a USB ,  is missing when the Install
process starts.

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

Title:
  ppc : Trusty ISO install fails booted from CD

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  The ppc 14.04 CD boots ok and the install process starts ;
  but it eventually fails during setup phase complaining it's can't find the 
CD; 

  Saucy ppc ISO boots and installs a p4080 cts-1000 base system ok , but 
requires 
  additional post install steps ( adding grub and installing e500mc kernel deb 
package) ;

  
  Description:Ubuntu 14.04 LTS
  Release:14.04

  
  (saucy)root@jade-jpd://media/cdrom# more README.diskdefines
  #define DISKNAME  Ubuntu-Server 14.04 LTS Trusty Tahr - Release powerpc
  #define TYPE  binary
  #define TYPEbinary  1
  #define ARCH  powerpc
  #define ARCHpowerpc  1
  #define DISKNUM  1
  #define DISKNUM1  1
  #define TOTALNUM  0
  #define TOTALNUM0  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1313888/+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 1304045] [NEW] rpciod: page alloc error no

[joh...@servergy.com]

Public bug reported:

(saucy)root@jade-rev4:/home2/usbkey# [21841.439960] kworker/4:1: page 
allocation failure: order:0, mode:0x204000
[21841.446658] CPU: 4 PID: 77 Comm: kworker/4:1 Tainted: GF
3.11.0-5-powerpc-e500mc #8-Ubuntu
[21841.455917] Workqueue: rpciod rpc_async_schedule [sunrpc]
[21841.461307] Call Trace:
[21841.463749] [ea427bb0] [c00080fc] show_stack+0xfc/0x1c0 (unreliable)
[21841.470100] [ea427c00] [c080ae6c] dump_stack+0x78/0xa0
[21841.475233] [ea427c10] [c01651cc] warn_alloc_failed+0xfc/0x160
[21841.481059] [ea427c70] [c01686c8] __alloc_pages_nodemask+0x678/0x880
[21841.487407] [ea427d50] [c01af2b0] new_slab+0x290/0x2a0
[21841.492538] [ea427d70] [c01b1070] __slab_alloc.constprop.64+0x3f0/0x500
[21841.499143] [ea427df0] [c01b135c] __kmalloc+0x1dc/0x230
[21841.504371] [ea427e10] [fa514cd8] rpc_malloc+0x48/0xa0 [sunrpc]
[21841.510290] [ea427e20] [fa50b278] call_allocate+0xe8/0x160 [sunrpc]
[21841.516556] [ea427e30] [fa5156c4] __rpc_execute+0x94/0x3b0 [sunrpc]
[21841.522823] [ea427e80] [fa515a0c] rpc_async_schedule+0x2c/0x50 [sunrpc]
[21841.529431] [ea427e90] [c007f8e0] process_one_work+0x150/0x3f0
[21841.535255] [ea427ec0] [c00802b4] worker_thread+0x134/0x3e0
[21841.540821] [ea427ef0] [c0088084] kthread+0xb4/0xc0
[21841.545692] [ea427f40] [c001073c] ret_from_kernel_thread+0x5c/0x64
[21841.551861] Mem-Info:
[21841.554123] DMA per-cpu:
[21841.556646] CPU0: hi:   90, btch:  15 usd:  78
[21841.561426] CPU1: hi:   90, btch:  15 usd:   2
[21841.566205] CPU2: hi:   90, btch:  15 usd:  79
[21841.570985] CPU3: hi:   90, btch:  15 usd:  67
[21841.575764] CPU4: hi:   90, btch:  15 usd:  14
[21841.580543] CPU5: hi:   90, btch:  15 usd:   0
[21841.585323] CPU6: hi:   90, btch:  15 usd:  55
[21841.590102] CPU7: hi:   90, btch:  15 usd:  75
[21841.594881] HighMem per-cpu:
[21841.597751] CPU0: hi:  186, btch:  31 usd:   0
[21841.602530] CPU1: hi:  186, btch:  31 usd: 180
[21841.607309] CPU2: hi:  186, btch:  31 usd:   0
[21841.612089] CPU3: hi:  186, btch:  31 usd:   0
[21841.616868] CPU4: hi:  186, btch:  31 usd:   0
[21841.621648] CPU5: hi:  186, btch:  31 usd:   0
[21841.626427] CPU6: hi:  186, btch:  31 usd:   0
[21841.631206] CPU7: hi:  186, btch:  31 usd: 169
[21841.635991] active_anon:20771 inactive_anon:21077 isolated_anon:0
[21841.635991]  active_file:452533 inactive_file:476704 isolated_file:6
[21841.635991]  unevictable:0 dirty:0 writeback:0 unstable:0
[21841.635991]  free:7239714 slab_reclaimable:38857 slab_unreclaimable:9994
[21841.635991]  mapped:16084 shmem:336 pagetables:1476 bounce:0
[21841.635991]  free_cma:0
[21841.668561] DMA free:27984kB min:2252kB low:2812kB high:3376kB 
active_anon:0kB inactive_anon:0kB active_file:33552kB inactive_file:33484kB 
unevictable:0kB isolated(anon):0kB isolated(file):24kB present:786432kB 
managed:317684kB mlocked:0kB dirty:0kB writeback:0kB mapped:8kB shmem:0kB 
slab_reclaimable:155428kB slab_unreclaimable:36288kB kernel_stack:2384kB 
pagetables:5904kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB 
pages_scanned:0 all_unreclaimable? no
[21841.709623] lowmem_reserve[]: 0 0 32000 32000
[21841.713988] HighMem free:28934512kB min:512kB low:58676kB high:116840kB 
active_anon:83084kB inactive_anon:84308kB active_file:1776580kB 
inactive_file:1873332kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:32768000kB managed:32768000kB mlocked:0kB dirty:0kB writeback:0kB 
mapped:64328kB shmem:1344kB slab_reclaimable:0kB slab_unreclaimable:0kB 
kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
[21841.756438] lowmem_reserve[]: 0 0 0 0
[21841.760099] DMA: 1338*4kB (UEM) 448*8kB (UEM) 213*16kB (UEM) 160*32kB (UEM) 
61*64kB (UEM) 14*128kB (UEM) 9*256kB (UEM) 0*512kB 0*1024kB 0*2048kB 1*4096kB 
(R) = 29560kB
[21841.775088] HighMem: 515*4kB (UM) 1221*8kB (UM) 95*16kB (UM) 61*32kB (UM) 
43*64kB (UM) 18*128kB (UM) 12*256kB (UM) 7*512kB (M) 5*1024kB (M) 5*2048kB (UM) 
7054*4096kB (UMR) = 28935556kB
[21841.791561] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=4096kB
[21841.799986] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=16384kB
[21841.808499] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=65536kB
[21841.817011] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=262144kB
[21841.825610] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=1048576kB
[21841.834295] 929384 total pagecache pages
[21841.838207] 0 pages in swap cache
[21841.841510] Swap cache stats: add 0, delete 0, find 0/0
[21841.846722] Free swap  = 33553404kB
[21841.850199] Total swap = 33553404kB
[21841.853677] __slab_alloc: 144 callbacks suppressed
[21841.858456] SLUB: Unable to allocate memory on node -1 (gfp=0x0)
[21841.864452]   cache: kmalloc-4096, object size: 4096, buffer size: 4096, 
default order: 3, 

[Kernel-packages] [Bug 1297452] [NEW] dirty root FS should be forced clean if they are dirty

[joh...@servergy.com]

Public bug reported:


It is poor practice  not to force clean a dirty root FS (ext4 type) on boot if 
the system has gone down hard; The root FS comes up mounted read only and one 
has to manually reboot to recovery  mode and force fsck through a command line. 

For Server class machines the user invention increases down time.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION=Ubuntu 13.10
NAME=Ubuntu
VERSION=13.10, Saucy Salamander
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=Ubuntu 13.10
VERSION_ID=13.10
HOME_URL=http://www.ubuntu.com/;
SUPPORT_URL=http://help.ubuntu.com/;
BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/;
# uname -a
Linux -jpd 3.11.0-6-powerpc-e500mc #9-Ubuntu SMP Fri Feb 28 04:08:05 UTC 2014 
ppc ppc ppc GNU/Linux

** Affects: linux-ppc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  dirty root FS should be forced clean if they are dirty

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  
  It is poor practice  not to force clean a dirty root FS (ext4 type) on boot 
if the system has gone down hard; The root FS comes up mounted read only and 
one has to manually reboot to recovery  mode and force fsck through a command 
line. 

  For Server class machines the user invention increases down time.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=13.10
  DISTRIB_CODENAME=saucy
  DISTRIB_DESCRIPTION=Ubuntu 13.10
  NAME=Ubuntu
  VERSION=13.10, Saucy Salamander
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME=Ubuntu 13.10
  VERSION_ID=13.10
  HOME_URL=http://www.ubuntu.com/;
  SUPPORT_URL=http://help.ubuntu.com/;
  BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/;
  # uname -a
  Linux -jpd 3.11.0-6-powerpc-e500mc #9-Ubuntu SMP Fri Feb 28 04:08:05 UTC 2014 
ppc ppc ppc GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1297452/+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 1282201] Re: SysRQ over serial console redirects to syslog

[joh...@servergy.com]

I know it's not a bug per say .


On Sat, Mar 8, 2014 at 8:21 AM, Ben Collins benmcollin...@gmail.com wrote:

 John,

 This isn't a bug. You are normally booted in Linux with the quiet flag
 passed to the kernel command line. You won't see output like this unless
 you either boot without that flag, or run a command such as dmesg
 --console-on or twiddle some bits in /proc/sys/kernel/printk.

 This is normal behavior.

 ** Changed in: linux-ppc (Ubuntu)
Status: New = Invalid

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1282201

 Title:
   SysRQ over serial console redirects to syslog

 Status in linux-ppc package in Ubuntu:
   Invalid

 Bug description:

   VERSION=13.10, Saucy Salamander
   ID=ubuntu
   ID_LIKE=debian
   PRETTY_NAME=Ubuntu 13.10
   VERSION_ID=13.10

   vmlinux-3.11.0-5-powerpc-e500mc


   When SysRQ is enabled through  /proc :


 echo 1  /proc/sys/kernel/sysrq


   All responses from SysRQ  sequences are redirected to /var/log/syslog ,
 not the serial console.

   For instance:

SySRQ ( break )  l

   Is suppose to report CPU stack traces .  The summary is sent to
 v/var/log/syslog , not the serial port, which
   defeats the entire purpose of SysRQ feature which is intended for
 diagnostics of server issues.

   The logging behavior can redirected to the console by using :

dmesg --console-on

   This should be the default behavior for ppc ; It is also how x86 has
   worked in the past.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1282201/+subscriptions



--

*Regards,*
* John.*

*--*

*o* Energy-efficiency is #1 reason data centers look to expand.  -- Digital
Realty Trust
*o* Green Data Centers spending to increase 300% worldwide by 2016.  --
Pike Research
*o *Data Centers have become as vital to the functioni
ng of society as power stations.  -- The Economist

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

Title:
  SysRQ over serial console redirects to syslog

Status in “linux-ppc” package in Ubuntu:
  Invalid

Bug description:
  
  VERSION=13.10, Saucy Salamander
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME=Ubuntu 13.10
  VERSION_ID=13.10

  vmlinux-3.11.0-5-powerpc-e500mc

  
  When SysRQ is enabled through  /proc :


echo 1  /proc/sys/kernel/sysrq

   
  All responses from SysRQ  sequences are redirected to /var/log/syslog , not 
the serial console. 

  For instance:

   SySRQ ( break )  l

  Is suppose to report CPU stack traces .  The summary is sent to 
v/var/log/syslog , not the serial port, which 
  defeats the entire purpose of SysRQ feature which is intended for diagnostics 
of server issues.

  The logging behavior can redirected to the console by using :

   dmesg --console-on

  This should be the default behavior for ppc ; It is also how x86 has
  worked in the past.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1282201/+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 1282201] [NEW] SysRQ over serial console redirects to syslog

[joh...@servergy.com]

Public bug reported:


VERSION=13.10, Saucy Salamander
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=Ubuntu 13.10
VERSION_ID=13.10

vmlinux-3.11.0-5-powerpc-e500mc


When SysRQ is enabled through  /proc :

  
  echo 1  /proc/sys/kernel/sysrq

 
All responses from SysRQ  sequences are redirected to /var/log/syslog , not the 
serial console. 

For instance:

 SySRQ ( break )  l

Is suppose to report CPU stack traces .  The summary is sent to 
v/var/log/syslog , not the serial port, which 
defeats the entire purpose of SysRQ feature which is intended for diagnostics 
of server issues.

The logging behavior can redirected to the console by using :

 dmesg --console-on

This should be the default behavior for ppc ; It is also how x86 has
worked in the past.

** Affects: linux-ppc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  SysRQ over serial console redirects to syslog

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  
  VERSION=13.10, Saucy Salamander
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME=Ubuntu 13.10
  VERSION_ID=13.10

  vmlinux-3.11.0-5-powerpc-e500mc

  
  When SysRQ is enabled through  /proc :


echo 1  /proc/sys/kernel/sysrq

   
  All responses from SysRQ  sequences are redirected to /var/log/syslog , not 
the serial console. 

  For instance:

   SySRQ ( break )  l

  Is suppose to report CPU stack traces .  The summary is sent to 
v/var/log/syslog , not the serial port, which 
  defeats the entire purpose of SysRQ feature which is intended for diagnostics 
of server issues.

  The logging behavior can redirected to the console by using :

   dmesg --console-on

  This should be the default behavior for ppc ; It is also how x86 has
  worked in the past.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1282201/+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 1279403] [NEW] tg3 driver hangs in iscsi booted initrd : (saucy)

[joh...@servergy.com]

Public bug reported:

Testing saucy iscsi target  booted  on e500mc  default initrd hangs when
tg3 driver started.

saucy was installed to an iSCSI target using the interactive setup from:
  
   
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
   
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

Linux version 3.11.0-5-powerpc-e500mc 
initrd.img-3.11.0-5-powerpc-e500mc

Booted from flash USB to simulate a pxe boot.

svy-boot# 
svy-boot# mount /dev/sda1 /mnt
svy-boot# cd /mnt/iscsi2
svy-boot# ./go.sh
 /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 


with break enabled I can enter cli in the initramfs 

 - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

(initramfs) ipconfig -t 10 -c dhcp -d eth1 
(initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
IP-Config: no response after 10 secs - giving up

   - System is alive ( I have a prompt )  - The above SHOULD HAVE
WORKED since it is an  active port.

This is embedded fsl eth1 - (10Gbe) - No cable

(initramfs) ipconfig -t 10 -c dhcp -d eth0 
(initramfs)
(initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
IP-Config: no response after 10 secs - giving up

  - System is alive ( I have a prompt)

tg3 stand up card in pci-e slot:

(initramfs) ipconfig -t 10 -c dhcp -d eth4 
(initramfs)
(initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
(initramfs)
(initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, full 
duplex

 hung 


iSCSI  target information:

Server: CentOS 6.4 .x64 .

#passwd setup 
#
# tgtadm --lld iscsi --op new --mode account --user ronnie --password password
# tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
#
# dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


tgtadm --lld iscsi --op delete  --mode target --tid 1

tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0


tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
tgtadm --lld iscsi --op show --mode target

** Affects: linux-ppc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  tg3 driver hangs in iscsi booted initrd : (saucy)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is 

[Kernel-packages] [Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (saucy)

[joh...@servergy.com]

Originally reportedas defect  1276298.

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

Title:
  tg3 driver hangs in iscsi booted initrd : (saucy)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:
  Testing saucy iscsi target  booted  on e500mc  default initrd hangs
  when tg3 driver started.

  saucy was installed to an iSCSI target using the interactive setup from:

 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux
 
http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz

  Linux version 3.11.0-5-powerpc-e500mc 
  initrd.img-3.11.0-5-powerpc-e500mc

  Booted from flash USB to simulate a pxe boot.

  svy-boot# 
  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi2
  svy-boot# ./go.sh
   /sbin/kexec --command='root=/dev/ram ro 
UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 
console=tty0 console=ttyS0,115200 dhcp 
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e 
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' 
--initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l 
/mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc 

  
  with break enabled I can enter cli in the initramfs 

   - This is embedded  fsl  eth1  ( 1Gbe ) with  a cable :

  (initramfs) ipconfig -t 10 -c dhcp -d eth1 
  (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

 - System is alive ( I have a prompt )  - The above SHOULD HAVE
  WORKED since it is an  active port.

  This is embedded fsl eth1 - (10Gbe) - No cable

  (initramfs) ipconfig -t 10 -c dhcp -d eth0 
  (initramfs)
  (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP
  IP-Config: no response after 10 secs - giving up

- System is alive ( I have a prompt)

  tg3 stand up card in pci-e slot:

  (initramfs) ipconfig -t 10 -c dhcp -d eth4 
  (initramfs)
  (initramfs) [  218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
  (initramfs)
  (initramfs) [  221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, 
full duplex

   hung 

  
  iSCSI  target information:

  Server: CentOS 6.4 .x64 .

  #passwd setup 
  #
  # tgtadm --lld iscsi --op new --mode account --user ronnie --password password
  # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
  #
  # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


  
  tgtadm --lld iscsi --op delete  --mode target --tid 1

  tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
  tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0

  
  tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
  tgtadm --lld iscsi --op show --mode target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+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 1276290] Re: Oops in rpc_remove_client_dir (NFS mount)

[joh...@servergy.com]

NFS Server:


Linux ab763 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  Oops in  rpc_remove_client_dir (NFS mount)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:

  Multiple Oops  in NFS unmount  during shutdown (saucy rel )

  3.11.0-5-powerpc-e500mc #8-Ubuntu


  (saucy)root@(none):/work/svy/tools#  * Stopping MD monitoring service mdadm 
--monitor[ 
OK ]
   * Asking all remaining processes to terminate...[ OK 
]
   * All processes ended within 1 seconds...   [ OK 
]
  [65426.692405] Oops: Exception in kernel mode, sig: 11 [#1]
  [65426.697721] SMP NR_CPUS=8 P4080 DS
  [65426.701122] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) 
ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) 
libcrc32c(F) reiserfs(F) nls_iso8859_1(F) nls_cp437(F) vfat(F) fat(F) 
dm_multipath(F) scsi_dh(F) usb_storage(F) ext2(F) rpcsec_gss_krb5(F) nfsv4(F) 
nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) 
ofpart(F) redboot(F) cmdlinepart(F) cfi_cmdset_0002(F) cfi_probe(F) cfi_util(F) 
gen_probe(F) physmap_of(F) map_funcs(F) chipreg(F) mtd(F) lm90(F) at24(F) 
caam(F) i2c_mpc(F) mpc85xx_edac(F) edac_core(F) uio_pdrv_genirq(F) uio(F) 
ata_generic(F) ahci(F) libahci(F) pata_jmicron(F) fsl_pq_mdio(F)
  [65426.759065] CPU: 6 PID: 19006 Comm: umount.nfs Tainted: GF
3.11.0-5-powerpc-e500mc #8-Ubuntu
  [65426.768461] task: ea0f3900 ti: ea05c000 task.ti: ea05c000
  [65426.773858] NIP: f99a0f50 LR: f998250c CTR: c07f85c0
  [65426.778820] REGS: ea05dda0 TRAP: 0700   Tainted: GF 
(3.11.0-5-powerpc-e500mc)
  [65426.786998] MSR: 00029002 CE,EE,ME  CR: 24000422  XER: 2000
  [65426.793107]
  GPR00: f9982d20 ea05de50 ea0f3900 e7e66ee0 00029002 0001  
  GPR08: eadc2504   0001 c07f85c0 1002e3ac 1001 8000
  GPR16: 100112e4 1000f3c4 1000f3e0 1000f594 1000f59c 1000f440 c0b4fb6c 1001
  GPR24: 1001  c0089180 ea05de84 f99ab064 ea2bf500 c0b41380 ea54ef00
  [65426.822949] NIP [f99a0f50] rpc_remove_client_dir+0x0/0x30 [sunrpc]
  [65426.829143] LR [f998250c] __rpc_clnt_remove_pipedir+0x5c/0x80 [sunrpc]
  [65426.835668] Call Trace:
  [65426.838128] [ea05de50] [f999f9f0] rpc_get_sb_net+0x70/0xa0 [sunrpc] 
(unreliable)
  [65426.845542] [ea05de60] [f9982d20] rpc_free_client+0x50/0xa0 [sunrpc]
  [65426.851910] [ea05de70] [f9982c58] rpc_shutdown_client+0x68/0xe0 [sunrpc]
  [65426.858647] [ea05dec0] [f9a3fd04] nfs_free_server+0x124/0x190 [nfs]
  [65426.864920] [ea05dee0] [c01c5f34] deactivate_locked_super+0x74/0xa0
  [65426.871193] [ea05def0] [c01e9184] SyS_umount+0x94/0x3d0
  [65426.876422] [ea05df40] [c0010604] ret_from_syscall+0x0/0x3c
  [65426.882002] --- Exception: c01 at 0xfec55dc
  [65426.882002] LR = 0xff88d54
  [65426.889225] Instruction dump:
  [65426.892191] 1b50 aa32 0706 0120 aa36 0706 1af8 
aa3a
  [65426.899964] 0706 1aa0 aa46 0704 0058 aa4a 
0704 1b74
  [65426.907949] udlfb: /dev/fb0 FB_BLANK mode 1 -- 0
  [65426.912666] udlfb: set_par mode 1024x768
  [65426.927196] ---[ end trace b25b3039b99e0391 ]---
  [65426.931816]
  umount.nfs: /work: not mounted
  [65426.960296] init: idmapd main process (2394) killed by TERM signal
  [65426.983998] init: systemd-logind main process (544) killed by TERM signal

  Oops #2

  [65426.994070] Oops: Exception in kernel mode, sig: 11 [#2]
  [65426.999386] SMP NR_CPUS=8 P4080 DS
  [65427.002787] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) 
ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) 
libcrc32c(F) reiserfs(F) nls_iso8859_1(F) nls_cp437(F) vfat(F) fat(F) 
dm_multipath(F) scsi_dh(F) usb_storage(F) ext2(F) rpcsec_gss_krb5(F) nfsv4(F) 
nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) 
ofpart(F) redboot(F) cmdlinepart(F) cfi_cmdset_0002(F) cfi_probe(F) cfi_util(F) 
gen_probe(F) physmap_of(F) map_funcs(F) chipreg(F) mtd(F) lm90(F) at24(F) 
caam(F) i2c_mpc(F) mpc85xx_edac(F) edac_core(F) uio_pdrv_genirq(F) uio(F) 
ata_generic(F) ahci(F) libahci(F) pata_jmicron(F) fsl_pq_mdio(F)
  [65427.060734] CPU: 7 PID: 19014 Comm: umount Tainted: GF D  
3.11.0-5-powerpc-e500mc #8-Ubuntu
  [65427.069783] task: e5d55580 ti: ea2f task.ti: ea2f
  [65427.075180] NIP: f99a0270 LR: c01c5f34 CTR: f99a0270
  [65427.080142] REGS: ea2f1e30 TRAP: 0700   Tainted: GF D   
(3.11.0-5-powerpc-e500mc)
  [65427.088320] MSR: 00029002 CE,EE,ME  CR: 24004424  XER: 
  [65427.094430]
  GPR00: c01c5f24 ea2f1ee0 e5d55580 ea1e7800 c1d404e0 ea027a80 c01e7b78 0001
  GPR08:  f99a0270 

[Kernel-packages] [Bug 1276290] [NEW] Oops in rpc_remove_client_dir (NFS mount)

[joh...@servergy.com]

Public bug reported:


Multiple Oops  in NFS unmount  during shutdown (saucy rel )

3.11.0-5-powerpc-e500mc #8-Ubuntu


(saucy)root@(none):/work/svy/tools#  * Stopping MD monitoring service mdadm 
--monitor[ 
OK ]
 * Asking all remaining processes to terminate...[ OK ]
 * All processes ended within 1 seconds...   [ OK ]
[65426.692405] Oops: Exception in kernel mode, sig: 11 [#1]
[65426.697721] SMP NR_CPUS=8 P4080 DS
[65426.701122] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) 
ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) 
libcrc32c(F) reiserfs(F) nls_iso8859_1(F) nls_cp437(F) vfat(F) fat(F) 
dm_multipath(F) scsi_dh(F) usb_storage(F) ext2(F) rpcsec_gss_krb5(F) nfsv4(F) 
nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) 
ofpart(F) redboot(F) cmdlinepart(F) cfi_cmdset_0002(F) cfi_probe(F) cfi_util(F) 
gen_probe(F) physmap_of(F) map_funcs(F) chipreg(F) mtd(F) lm90(F) at24(F) 
caam(F) i2c_mpc(F) mpc85xx_edac(F) edac_core(F) uio_pdrv_genirq(F) uio(F) 
ata_generic(F) ahci(F) libahci(F) pata_jmicron(F) fsl_pq_mdio(F)
[65426.759065] CPU: 6 PID: 19006 Comm: umount.nfs Tainted: GF
3.11.0-5-powerpc-e500mc #8-Ubuntu
[65426.768461] task: ea0f3900 ti: ea05c000 task.ti: ea05c000
[65426.773858] NIP: f99a0f50 LR: f998250c CTR: c07f85c0
[65426.778820] REGS: ea05dda0 TRAP: 0700   Tainted: GF 
(3.11.0-5-powerpc-e500mc)
[65426.786998] MSR: 00029002 CE,EE,ME  CR: 24000422  XER: 2000
[65426.793107]
GPR00: f9982d20 ea05de50 ea0f3900 e7e66ee0 00029002 0001  
GPR08: eadc2504   0001 c07f85c0 1002e3ac 1001 8000
GPR16: 100112e4 1000f3c4 1000f3e0 1000f594 1000f59c 1000f440 c0b4fb6c 1001
GPR24: 1001  c0089180 ea05de84 f99ab064 ea2bf500 c0b41380 ea54ef00
[65426.822949] NIP [f99a0f50] rpc_remove_client_dir+0x0/0x30 [sunrpc]
[65426.829143] LR [f998250c] __rpc_clnt_remove_pipedir+0x5c/0x80 [sunrpc]
[65426.835668] Call Trace:
[65426.838128] [ea05de50] [f999f9f0] rpc_get_sb_net+0x70/0xa0 [sunrpc] 
(unreliable)
[65426.845542] [ea05de60] [f9982d20] rpc_free_client+0x50/0xa0 [sunrpc]
[65426.851910] [ea05de70] [f9982c58] rpc_shutdown_client+0x68/0xe0 [sunrpc]
[65426.858647] [ea05dec0] [f9a3fd04] nfs_free_server+0x124/0x190 [nfs]
[65426.864920] [ea05dee0] [c01c5f34] deactivate_locked_super+0x74/0xa0
[65426.871193] [ea05def0] [c01e9184] SyS_umount+0x94/0x3d0
[65426.876422] [ea05df40] [c0010604] ret_from_syscall+0x0/0x3c
[65426.882002] --- Exception: c01 at 0xfec55dc
[65426.882002] LR = 0xff88d54
[65426.889225] Instruction dump:
[65426.892191] 1b50 aa32 0706 0120 aa36 0706 1af8 
aa3a
[65426.899964] 0706 1aa0 aa46 0704 0058 aa4a 0704 
1b74
[65426.907949] udlfb: /dev/fb0 FB_BLANK mode 1 -- 0
[65426.912666] udlfb: set_par mode 1024x768
[65426.927196] ---[ end trace b25b3039b99e0391 ]---
[65426.931816]
umount.nfs: /work: not mounted
[65426.960296] init: idmapd main process (2394) killed by TERM signal
[65426.983998] init: systemd-logind main process (544) killed by TERM signal

Oops #2

[65426.994070] Oops: Exception in kernel mode, sig: 11 [#2]
[65426.999386] SMP NR_CPUS=8 P4080 DS
[65427.002787] Modules linked in: btrfs(F) raid6_pq(F) zlib_deflate(F) xor(F) 
ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) 
libcrc32c(F) reiserfs(F) nls_iso8859_1(F) nls_cp437(F) vfat(F) fat(F) 
dm_multipath(F) scsi_dh(F) usb_storage(F) ext2(F) rpcsec_gss_krb5(F) nfsv4(F) 
nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) 
ofpart(F) redboot(F) cmdlinepart(F) cfi_cmdset_0002(F) cfi_probe(F) cfi_util(F) 
gen_probe(F) physmap_of(F) map_funcs(F) chipreg(F) mtd(F) lm90(F) at24(F) 
caam(F) i2c_mpc(F) mpc85xx_edac(F) edac_core(F) uio_pdrv_genirq(F) uio(F) 
ata_generic(F) ahci(F) libahci(F) pata_jmicron(F) fsl_pq_mdio(F)
[65427.060734] CPU: 7 PID: 19014 Comm: umount Tainted: GF D  
3.11.0-5-powerpc-e500mc #8-Ubuntu
[65427.069783] task: e5d55580 ti: ea2f task.ti: ea2f
[65427.075180] NIP: f99a0270 LR: c01c5f34 CTR: f99a0270
[65427.080142] REGS: ea2f1e30 TRAP: 0700   Tainted: GF D   
(3.11.0-5-powerpc-e500mc)
[65427.088320] MSR: 00029002 CE,EE,ME  CR: 24004424  XER: 
[65427.094430]
GPR00: c01c5f24 ea2f1ee0 e5d55580 ea1e7800 c1d404e0 ea027a80 c01e7b78 0001
GPR08:  f99a0270  000d 003fe0f9 100192e0 1001 8000
GPR16: 100112e4 1000f3c4 1000f3e0 1000f594 1000f59c ea027aa0 c0b4fb6c ea2f1ef8
GPR24:  ea027a80  ea027a80 ea027aa0 ea027abc f99aba78 ea1e7800
[65427.124275] NIP [f99a0270] rpc_kill_sb+0x0/0x110 [sunrpc]
[65427.129677] LR [c01c5f34] deactivate_locked_super+0x74/0xa0
[65427.135246] Call Trace:
[65427.137689] [ea2f1ee0] [c01c5f24] deactivate_locked_super+0x64/0xa0 
(unreliable)
[65427.145094] [ea2f1ef0] [c01e9184] 

[Kernel-packages] [Bug 1276298] [NEW] iscsi booted system hangs on 3.8.0.19 ramdisk .(ppc - e500mc)

[joh...@servergy.com]

Public bug reported:


I was experimenting with an iscsi boot device   as root device , and 
one of the preliminary steps is getting a network connection established via
the default initrd.

 It appears that starting the network from init hangs the
system.

I installed Ubuntu directly to an iSCSI target via the Ubuntu install , copied
the default vmlinux+initrd to a USB, then attempted to setup the boot
environment via USB where we launch vmlinux and initrd via kexec:

svy-boot# mount /dev/sda1 /mnt
svy-boot# cd /mnt/iscsi
svy-boot# ls
abi-3.8.0-19-powerpc-e500mc 
bootargsinitrd.img-3.8.0-19-powerpc-e500mc
bootiscsi.shkernel
config-3.8.0-19-powerpc-e500mc  vmlinux-3.8.0-19-powerpc-e500mc
go.sh
   
svy-boot# ./go.sh


/sbin/kexec --command='root=/dev/ram ro
UUID=3967a9b2-91f5-4dce-98ae-874fcb2d5a7d ro break debug console=tty0
console=ttyS0,115200 interface=eth3
192.168.1.110:192.168.1.140:192.168.1.1:255.255.0.0:jade-iscsi0:eth3:none
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 '
--initrd=/mnt/iscsi/initrd.img-3.8.0-19-powerpc-e500mc -l
/mnt/iscsi/vmlinux-3.8.0-19-powerpc-e500mc 


I started the system so it would break if a error occured:


[0.00] Using P4080 DS machine description
[0.00] Memory CAM mapping: 256/256/256 Mb, residual: 3328Mb
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.8.0-19-powerpc-e500mc (buildd@ross) (gcc version
4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #25-Ubuntu SMP Mon Dec 23 12:18:15 UTC
2013 (Ubuntu 3.8.0-19.25-powerpc-e500mc 3.8.13.13)


The system would likely find the iSCSI device but it hangs when the iscsi stack
is started :

(initramfs) sh +x ./iscissi
[ 1750.717666] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[ 1750.730184] Loading iSCSI transport class v2.0-870.
[ 1750.739849] iscsi: registered transport (tcp)
iscsistart: Logging into iqn.2001-04.com.jade:storage.disk0
192.168.1.140:3260,1
iscsistart: version 2.0-873
[ 1753.621329] tg3 :01:00.0 eth3: Link is up at 1000 Mbps, full duplex


- The iSCSI target target was created ona CentOS server ,


#startiscsi.sh 
#
# tgtadm --lld iscsi --op new --mode account --user ronnie --password password
# tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
#
# dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10


tgtadm --lld iscsi --op delete  --mode target --tid 1

tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.jade:storage.disk0
tgtadm  --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b  
`pwd`/iscsi.disk0


tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
tgtadm --lld iscsi --op show --mode target

** Affects: linux-ppc (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  iscsi booted system hangs on 3.8.0.19 ramdisk .(ppc - e500mc)

Status in “linux-ppc” package in Ubuntu:
  New

Bug description:

  I was experimenting with an iscsi boot device   as root device , and 
  one of the preliminary steps is getting a network connection established via
  the default initrd.

   It appears that starting the network from init hangs the
  system.

  I installed Ubuntu directly to an iSCSI target via the Ubuntu install , copied
  the default vmlinux+initrd to a USB, then attempted to setup the boot
  environment via USB where we launch vmlinux and initrd via kexec:

  svy-boot# mount /dev/sda1 /mnt
  svy-boot# cd /mnt/iscsi
  svy-boot# ls
  abi-3.8.0-19-powerpc-e500mc 
  bootargsinitrd.img-3.8.0-19-powerpc-e500mc
  bootiscsi.shkernel
  config-3.8.0-19-powerpc-e500mc  vmlinux-3.8.0-19-powerpc-e500mc
  go.sh
 
  svy-boot# ./go.sh

  
  /sbin/kexec --command='root=/dev/ram ro
  UUID=3967a9b2-91f5-4dce-98ae-874fcb2d5a7d ro break debug console=tty0
  console=ttyS0,115200 interface=eth3
  192.168.1.110:192.168.1.140:192.168.1.1:255.255.0.0:jade-iscsi0:eth3:none
  ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e
  ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0
  ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 '
  --initrd=/mnt/iscsi/initrd.img-3.8.0-19-powerpc-e500mc -l
  /mnt/iscsi/vmlinux-3.8.0-19-powerpc-e500mc 


  
  I started the system so it would break if a error occured:

  
  [0.00] Using P4080 DS machine description
  [0.00] Memory CAM mapping: 256/256/256 Mb, residual: 3328Mb
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [