[Kernel-packages] [Bug 1612305] onibi (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-20_04-46-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1593874] Re: warning stack trace while playing with apparmor namespaces

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  warning stack trace while playing with apparmor namespaces

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm not sure what exactly I was doing when this happened, but
  something fairly basic (creating containers, adding/removing
  profiles). Let me know if you need more than the trace and I can try
  and figure out how to reproduce.

  Jun 17 20:20:06 dev kernel: [13314.032676] [ cut here 
]
  Jun 17 20:20:06 dev kernel: [13314.032689] WARNING: CPU: 3 PID: 8964 at 
/build/linux-oXTOqc/linux-4.4.0/security/apparmor/label.c:82 
__aa_proxy_redirect+0xff/0x130()
  Jun 17 20:20:06 dev kernel: [13314.032692] AppArmor WARN __aa_proxy_redirect: 
((!!queued_write_can_lock(&(&(&(&((orig)->vec[0])))[(((orig)->size)) - 
1])->ns))->labels)->lock)->raw_lock))): 
  Jun 17 20:20:06 dev kernel: [13314.032693] Modules linked in: binfmt_misc 
veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables isofs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ppdev kvm_intel kvm joydev 
serio_raw irqbypass parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse floppy
  Jun 17 20:20:06 dev kernel: [13314.032751] CPU: 3 PID: 8964 Comm: lxd 
Tainted: P        W  O    4.4.0-24-generic #43-Ubuntu
  Jun 17 20:20:06 dev kernel: [13314.032753] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
  Jun 17 20:20:06 dev kernel: [13314.032756]  0286 dc104ca4 
880044db3d18 813eab23
  Jun 17 20:20:06 dev kernel: [13314.032760]  880044db3d60 81cec7f0 
880044db3d50 810810d2
  Jun 17 20:20:06 dev kernel: [13314.032763]  880047f04360 88007a08d360 
88004a551b00 88004a551b38
  Jun 17 20:20:06 dev kernel: [13314.032766] Call Trace:
  Jun 17 20:20:06 dev kernel: [13314.032773]  [] 
dump_stack+0x63/0x90
  Jun 17 20:20:06 dev kernel: [13314.032777]  [] 
warn_slowpath_common+0x82/0xc0
  Jun 17 20:20:06 dev kernel: [13314.032780]  [] 
warn_slowpath_fmt+0x5c/0x80
  Jun 17 20:20:06 dev kernel: [13314.032784]  [] ? 
__list_remove_profile+0x62/0xe0
  Jun 17 20:20:06 dev kernel: [13314.032788]  [] 
__aa_proxy_redirect+0xff/0x130
  Jun 17 20:20:06 dev kernel: [13314.032792]  [] 
destroy_ns+0x86/0xa0
  Jun 17 20:20:06 dev kernel: [13314.032794]  [] 
__aa_remove_ns+0x2f/0x60
  Jun 17 20:20:06 dev kernel: [13314.032798]  [] 
aa_remove_profiles+0x193/0x270
  Jun 17 20:20:06 dev kernel: [13314.032800]  [] ? 
__aa_kvmalloc+0x41/0x60
  Jun 17 20:20:06 dev kernel: [13314.032803]  [] 
profile_remove+0x9e/0x1f0
  Jun 17 20:20:06 dev kernel: [13314.032808]  [] 
__vfs_write+0x18/0x40
  Jun 17 20:20:06 dev kernel: [13314.032811]  [] 
vfs_write+0xa9/0x1a0
  Jun 17 20:20:06 dev kernel: [13314.032814]  [] ? 
do_sys_open+0x1bf/0x2a0
  Jun 17 20:20:06 dev kernel: [13314.032818]  [] 
SyS_write+0x55/0xc0
  Jun 17 20:20:06 dev kernel: [13314.032823]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Jun 17 20:20:06 dev kernel: [13314.032826] ---[ end trace 2eb06377c45f3d4c 
]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593874/+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 1550304] Re: After sleep or hibernate my laptop doesn't wake up

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  After sleep or hibernate my laptop doesn't wake up

Status in linux package in Ubuntu:
  Expired

Bug description:
  When my laptop sleep or hibernate after doe'nt wake up.
  light of laptop turn on but monitor was turn off

  Ubuntu 15.10
  Laoptop Hp probook 450 G3

  graphic : Radeon R7 340M
  cpu : intel  skylake 7i 6500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550304/+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 1554077] Re: brcmf_add_if: ERROR: netdev:wlp2s0 already exists

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  brcmf_add_if: ERROR: netdev:wlp2s0 already exists

Status in linux package in Ubuntu:
  Expired

Bug description:
  At boot time, on  Wifi interface set up, at boot time, an error is raised. 
  The graphical boot switches to textual boot to display this error.
  Despite this error the Wifi connection mostly works.

  [   47.250309] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  [   47.289947] brcmf_add_if: ERROR: netdev:wlp2s0 already exists
  [   47.289950] brcmf_add_if: ignore IF event
  [   48.485330] brcmf_add_if: ERROR: netdev:wlp2s0 already exists
  [   48.485333] brcmf_add_if: ignore IF event

  Ubuntu Wily 15.10, Kernel 4.2.0-30-generic,
  Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC 
(rev 01)
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gquintana   1413 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=2e069a2b-037f-4058-89b1-6e221da4046d
  InstallationDate: Installed on 2016-01-31 (35 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:6410 Broadcom Corp.
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=3ecb2c05-ad6c-4d9d-9356-48c6991f0226 ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0X2P13
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0X2P13:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554077/+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 1577440] Re: Suspension doesn't work after closing lid

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Suspension doesn't work after closing lid

Status in linux package in Ubuntu:
  Expired

Bug description:
  In my HP 650 suspension works good when i use power button and choose this 
action. It doesn't work when i close lid. In settings i set suspension as a 
action for this event, but id does not work. Screen goes black, but it is not 
even locked to secure my laptop. After opening lid screen starts to work, but 
no password is needed. 
  I'm using 16.04 LTS Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577440/+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 1592585] Re: radeon.ko not loads automatically after updates

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  radeon.ko not loads automatically after updates

Status in linux package in Ubuntu:
  Expired

Bug description:
  I think after updating libudev1 to latest version from repos:
   - on boot system cannot load radeon.ko module
   - some other things not loaded (cpu governors for example, only performance 
is present)
   - a tried deifferent kernel versions (4.4.0-24, 4.6.0, 4.6.2) and problems 
hasn't gone
   - I take this problem only with new installed 4.6.2 kernel, but after 
updating initrd image problem present on all kernels

  I'm Linux developer and you can ask me for some additional info which
  can help to solve this problem. I think this problem is only software
  related.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libudev1 229-4ubuntu6
  Uname: Linux 4.6.2-040602-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 15 01:01:48 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-05-07 (38 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  edgar  2313 F pulseaudio
   /dev/snd/controlC0:  edgar  2313 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a2084e77-daf0-465f-b09a-9694a03a3b26
  InstallationDate: Installed on 2016-05-07 (43 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555YI
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=6947b781-942c-4c6e-810a-997d674d4b3b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592585/+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 1500183] Re: 15.10 beta does not resume from hibernate

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  15.10 beta does not resume from hibernate

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  I've installed 15.10 beta1 on a new PC with an SSD, and used the
  following scheme (I've used that plenty of times with 14.04):

  /dev/sda1:  unencrypted ext4 , mounted as /boot
  /dev/sda2: luks-encrypted swap
  /dev/sda3: luks-encrypted btrfs mounte as /root

  
  Sending the machine into hibernating with pm-hibernate works, but it ignores 
the hibernated state when powering ab, it just does a fresh boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500183/+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 1559805] Re: suspend not working with latest xenial and kernel 4.4.0

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  suspend not working with latest xenial and kernel 4.4.0

Status in linux package in Ubuntu:
  Expired

Bug description:
  suspend stops but never finishes and needs a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar 20 22:45:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-04 (168 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-03-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559805/+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 1571786] Re: Broadcom 43602 requires module to be reloaded to work

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

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

Title:
  Broadcom 43602 requires module to be reloaded to work

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

Bug description:
  Running 16.04, and a recent update (last week?) introduced the
  following issue.

  I have a Broadcom wireless card:

  02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac
  Wireless LAN SoC (rev 01)

  Upon startup the network will connect fine.  Then after about a minute
  it will drop out.  Possibly related to the following in dmesg:

  [  163.870916] brcmfmac :02:00.0: Direct firmware load for
  brcm/brcmfmac43602-pcie.txt failed with error -2

  If I rmmod and re-insert  brcmfmac it works until the next reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571786/+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 1567781] Re: unable to handle kernel NULL pointer dereference at 00000134

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  unable to handle kernel NULL pointer dereference at 0134

Status in linux package in Ubuntu:
  Expired

Bug description:
  Problem is found in dmesg output:
  [   11.660671] BUG: unable to handle kernel NULL pointer dereference at 
0134
  [   11.660688] IP: [] mutex_lock+0x12/0x30
  [   11.660706] *pdpt = 33ee5001 *pde = 
  [   11.660714] Oops: 0002 [#1] SMP
  [   11.660723] Modules linked in: nfsd auth_rpcgss nfs_acl lockd parport_pc 
grace ppdev lp sunrpc parport autofs4 hid_generic hid_cherry pata_acpi usbhid 
hid psmouse gma500_gfx i2c_algo_bit r8169 drm_kms_helper drm sdhci_pci pata_sch 
sdhci mii video
  [   11.660772] CPU: 1 PID: 242 Comm: plymouthd Not tainted 4.2.0-35-generic 
#40-Ubuntu
  [   11.660779] Hardware name: CompuLab CM-iAM/SBC-FITPC2i/CM-iAM/SBC-FITPC2i, 
BIOS NAPA0001.86C..D.1009141059 09/14/2010
  [   11.660785] task: f5cf08c0 ti: f2364000 task.ti: f2364000
  [   11.660792] EIP: 0060:[] EFLAGS: 00010286 CPU: 1
  [   11.660798] EIP is at mutex_lock+0x12/0x30
  [   11.660804] EAX: 0134 EBX: 0134 ECX:  EDX: 8000
  [   11.660810] ESI:  EDI:  EBP: f2365ea8 ESP: f2365ea4
  [   11.660815]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   11.660820] CR0: 80050033 CR2: 0134 CR3: 31a1d540 CR4: 06f0
  [   11.660824] Stack:
  [   11.660828]  f19f93a0 f2365ec0 f8586171 f326dea0 f1ad7000  
f1a0a400 f2365ec8
  [   11.660842]  f858621f f2365edc f845ff47 f1a0a400 f1a0a400 f1a0a400 
f2365eec f84b6019
  [   11.660856]  f2365f04 c11b2de4 f2365f04 f856a78a f74d59d0  
 f1a0a400
  [   11.660869] Call Trace:
  [   11.660935]  [] __drm_modeset_lock_all+0x91/0x130 [drm]
  [   11.660986]  [] drm_modeset_lock_all+0xf/0x30 [drm]
  [   11.661018]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x17/0x50 [drm_kms_helper]
  [   11.661048]  [] psb_driver_lastclose+0x19/0x50 [gma500_gfx]
  [   11.661060]  [] ? kfree+0x134/0x140
  [   11.661110]  [] drm_lastclose+0x2a/0x140 [drm]
  [   11.661159]  [] drm_release+0x29f/0x490 [drm]
  [   11.661170]  [] __fput+0xcf/0x210
  [   11.661179]  [] fput+0xd/0x10
  [   11.661189]  [] task_work_run+0x7f/0xa0
  [   11.661200]  [] do_notify_resume+0x75/0x80
  [   11.661209]  [] work_notifysig+0x16/0x1b
  [   11.661215] Code: 00 00 c3 8d b6 00 00 00 00 31 c0 5d c3 8d b6 00 00 00 00 
8d bf 00 00 00 00 55 89 e5 53 3e 8d 74 26 00 89 c3 e8 60 ef ff ff 89 d8  ff 
08 79 05 e8 74 07 00 00 64 a1 c8 c0 bf c1 89 43 10 5b 5d
  [   11.661311] EIP: [] mutex_lock+0x12/0x30 SS:ESP 0068:f2365ea4
  [   11.661323] CR2: 0134
  [   11.661332] ---[ end trace 3bb80835d39a3e44 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Apr  8 08:21:26 2016
  HibernationDevice: RESUME=UUID=fda9b258-61a9-4bc5-974e-738538cee628
  InstallationDate: Installed on 2013-07-09 (1003 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  MachineType: CompuLab CM-iAM/SBC-FITPC2i
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=41b7698f-f3fa-4940-8e13-9378c5021e90 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-12-23 (106 days ago)
  dmi.bios.date: 09/14/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: NAPA0001.86C..D.1009141059
  dmi.board.name: CM-iAM/SBC-FITPC2i
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: OEM
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrNAPA0001.86C..D.1009141059:bd09/14/2010:svnCompuLab:pnCM-iAM/SBC-FITPC2i:pvrNotApplicable:rvnIntelCorporation:rnCM-iAM/SBC-FITPC2i:rvr1.x:cvnOEM:ct1:cvrN/A:
  dmi.product.name: CM-iAM/SBC-FITPC2i
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CompuLab

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1579918] Re: Smart Card Reader BCM 5880 with kernel 4.2

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Smart Card Reader BCM 5880 with kernel 4.2

Status in linux package in Ubuntu:
  Expired

Bug description:
  Native to Ubuntu 14.04 and 16.04 (kernel 4.2.0) on Dell Precision 7510
  with Broadcom 5880 (internal card reader). Card reads successfully
  from SCRx31 USB reader (external). Card also works on kernel 3.13.0
  (Dell Latitude E6430, 14.04) with same Broadcom 5880 reader.

  snippet from syslog:

  May 1 19:06:41 m-Precision pcscd: eventhandler.c:313:EHStatusHandlerThread() 
Error communicating to: Broadcom Corp 5880 [Contacted SmartCard] 
(0123456789ABCD) 00 00
  May 1 19:06:46 m-Precision kernel: [15276.197331] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.426405] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.442649] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.465888] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision pcscd: commands.c:1456:CCID_Receive() Can't read 
all data (54 out of 92 expected)
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:214:t1_transceive() 
fatal: transmit/receive failed
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:47 m-Precision pcscd: ccid_usb.c:790:ReadUSB() read failed (1/2): 
-8 Resource temporarily unavailable
  May 1 19:06:47 m-Precision pcscd: ifdwrapper.c:348:IFDStatusICC() Card not 
transacted: 612
  May 1 19:06:47 m-Precision pcscd: eventhandler.c:313:EHStatusHandlerThread() 
Error communicating to: Broadcom Corp 5880 [Contacted SmartCard] 
(0123456789ABCD) 00 00
  May 1 19:06:52 m-Precision kernel: [15281.960976] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?

  The above cycles on syslog roughly every second until card is removed.

  pcsc_scan shows card as alternating between successfully read to card
  reader not available, also on the roughly 1 sec interval.

  ---
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grumpy 2207 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28b8 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic.efi.signed 
root=UUID=62ed5a52-92de-456c-8a4b-433666572702 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42~14.04.1-generic 4.2.8-ckt8
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-36-generic N/A
   linux-backports-modules-4.2.0-36-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1571786] Re: Broadcom 43602 requires module to be reloaded to work

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Broadcom 43602 requires module to be reloaded to work

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

Bug description:
  Running 16.04, and a recent update (last week?) introduced the
  following issue.

  I have a Broadcom wireless card:

  02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac
  Wireless LAN SoC (rev 01)

  Upon startup the network will connect fine.  Then after about a minute
  it will drop out.  Possibly related to the following in dmesg:

  [  163.870916] brcmfmac :02:00.0: Direct firmware load for
  brcm/brcmfmac43602-pcie.txt failed with error -2

  If I rmmod and re-insert  brcmfmac it works until the next reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571786/+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 1612305] onibi (i386) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-20_02-40-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1612305] onza (amd64) - tests ran: 26, failed: 0

[Brad Figg]

tests ran:  26, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onza__4.4.0-36.55__2016-08-19_23-44-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1612305] onibi (amd64) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-20_00-36-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1612305] onibi (i386) - tests ran: 10, failed: 1

[Brad Figg]

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_23-57-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1504909] Re: blk_update_request: I/O error when accessing a disk that is spun down

[antst]

Actually, my fault. Nobody reverted commit which broke it, but commit
which solved it back in 2012 is present in current ubuntu kernel. Hm.

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

Title:
  blk_update_request: I/O error when accessing a disk that is spun down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 6 3TB SATA disks that are attached via a IBM M1015 in IT mode
  and the mpt2sas driver. The filesystem is zfsonlinux.

  I can't name the exact 3.19 kernel version when this error began, but
  it was not the inital 3.19 Vivid LTS Kernel because after initally
  upgrading to 3.19 everything still worked.

  After a recent update I have the following problem:

  When disks are spun down and then accessed an error occurs which corrupts 
data.
  When the disks are finally spun up everything works as expected, also 
preventing them from spinning down works as a workaround.

  Could this be a NCQ bug?

  Drives are 5x Seagate ST3000DM001 and 1x HGST HDN724030ALE640.

  [59526.359997] sd 0:0:1:0: [sdc] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59526.360003] sd 0:0:1:0: [sdc] CDB:
  [59526.360006] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59526.360022] blk_update_request: I/O error, dev sdc, sector 824769880
  [59544.111090] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.111097] sd 0:0:0:0: [sdb] CDB:
  [59544.00] Read(16): 88 00 00 00 00 00 31 28 fd 50 00 00 00 08 00 00
  [59544.15] blk_update_request: I/O error, dev sdb, sector 824769872
  [59544.114465] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.114468] sd 0:0:4:0: [sdf] CDB:
  [59544.114469] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59544.114483] blk_update_request: I/O error, dev sdf, sector 824769880
  [59552.117436] sd 0:0:3:0: [sde] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59552.117443] sd 0:0:3:0: [sde] CDB:
  [59552.117446] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59552.117462] blk_update_request: I/O error, dev sde, sector 824769968
  [59572.951158] sd 0:0:2:0: [sdd] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.951167] sd 0:0:2:0: [sdd] CDB:
  [59572.951170] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.951192] blk_update_request: I/O error, dev sdd, sector 824769968
  [59572.955679] sd 0:0:5:0: [sdg] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.955695] sd 0:0:5:0: [sdg] CDB:
  [59572.955701] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.955720] blk_update_request: I/O error, dev sdg, sector 824769968
  [70357.782677] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70357.782686] sd 0:0:4:0: [sdf] CDB:
  [70357.782690] Read(16): 88 00 00 00 00 00 85 c1 c9 08 00 00 00 08 00 00
  [70357.782712] blk_update_request: I/O error, dev sdf, sector 2244069640
  [70368.087947] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70368.087953] sd 0:0:0:0: [sdb] CDB:
  [70368.087955] Read(16): 88 00 00 00 00 00 85 c1 c9 00 00 00 00 08 00 00
  [70368.087969] blk_update_request: I/O error, dev sdb, sector 2244069632

  lsb_release -rd:
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Kernel Version: 3.19.0-30-generic
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Okt  8 18:46 seq
   crw-rw 1 root audio 116, 33 Okt  8 18:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/eternity--vg-swap_1
  InstallationDate: Installed on 2014-09-25 (380 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   lono wireless extensions.
   
   em1   no wireless extensions.
  MachineType: Dell Inc. PowerEdge T20
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic 
root=/dev/mapper/hostname--vg-root ro console=tty0 console=ttyS4,115200 
intel_pstate=enable cgroup_enable=memory swapaccount=1 intel_iommu=on 
enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=16M mtrr_chunk_size=64M 
i915.enable_rc6=0 nmi_watchdog=0
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1504909] Re: blk_update_request: I/O error when accessing a disk that is spun down

[antst]

Felix,

it is indeed the same bug, as rollback of commit (which was proposed in
that mail thread from 2012) is never happened. I just checked kernel
sources.

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

Title:
  blk_update_request: I/O error when accessing a disk that is spun down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 6 3TB SATA disks that are attached via a IBM M1015 in IT mode
  and the mpt2sas driver. The filesystem is zfsonlinux.

  I can't name the exact 3.19 kernel version when this error began, but
  it was not the inital 3.19 Vivid LTS Kernel because after initally
  upgrading to 3.19 everything still worked.

  After a recent update I have the following problem:

  When disks are spun down and then accessed an error occurs which corrupts 
data.
  When the disks are finally spun up everything works as expected, also 
preventing them from spinning down works as a workaround.

  Could this be a NCQ bug?

  Drives are 5x Seagate ST3000DM001 and 1x HGST HDN724030ALE640.

  [59526.359997] sd 0:0:1:0: [sdc] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59526.360003] sd 0:0:1:0: [sdc] CDB:
  [59526.360006] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59526.360022] blk_update_request: I/O error, dev sdc, sector 824769880
  [59544.111090] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.111097] sd 0:0:0:0: [sdb] CDB:
  [59544.00] Read(16): 88 00 00 00 00 00 31 28 fd 50 00 00 00 08 00 00
  [59544.15] blk_update_request: I/O error, dev sdb, sector 824769872
  [59544.114465] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.114468] sd 0:0:4:0: [sdf] CDB:
  [59544.114469] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59544.114483] blk_update_request: I/O error, dev sdf, sector 824769880
  [59552.117436] sd 0:0:3:0: [sde] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59552.117443] sd 0:0:3:0: [sde] CDB:
  [59552.117446] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59552.117462] blk_update_request: I/O error, dev sde, sector 824769968
  [59572.951158] sd 0:0:2:0: [sdd] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.951167] sd 0:0:2:0: [sdd] CDB:
  [59572.951170] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.951192] blk_update_request: I/O error, dev sdd, sector 824769968
  [59572.955679] sd 0:0:5:0: [sdg] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.955695] sd 0:0:5:0: [sdg] CDB:
  [59572.955701] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.955720] blk_update_request: I/O error, dev sdg, sector 824769968
  [70357.782677] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70357.782686] sd 0:0:4:0: [sdf] CDB:
  [70357.782690] Read(16): 88 00 00 00 00 00 85 c1 c9 08 00 00 00 08 00 00
  [70357.782712] blk_update_request: I/O error, dev sdf, sector 2244069640
  [70368.087947] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70368.087953] sd 0:0:0:0: [sdb] CDB:
  [70368.087955] Read(16): 88 00 00 00 00 00 85 c1 c9 00 00 00 00 08 00 00
  [70368.087969] blk_update_request: I/O error, dev sdb, sector 2244069632

  lsb_release -rd:
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Kernel Version: 3.19.0-30-generic
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Okt  8 18:46 seq
   crw-rw 1 root audio 116, 33 Okt  8 18:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/eternity--vg-swap_1
  InstallationDate: Installed on 2014-09-25 (380 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   lono wireless extensions.
   
   em1   no wireless extensions.
  MachineType: Dell Inc. PowerEdge T20
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic 
root=/dev/mapper/hostname--vg-root ro console=tty0 console=ttyS4,115200 
intel_pstate=enable cgroup_enable=memory swapaccount=1 intel_iommu=on 
enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=16M mtrr_chunk_size=64M 
i915.enable_rc6=0 nmi_watchdog=0
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1612305] onibi (amd64) - tests ran: 23, failed: 0

[Brad Figg]

tests ran:  23, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_23-12-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1612305] onza (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onza__4.4.0-36.55__2016-08-19_22-34-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1614362] Re: SD Card not mounted

[Sebastian Nohn]

Same wroblem with 4.4.0-34-generic #53~14.04.1-Ubuntu

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

Title:
  SD Card not mounted

Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  Since a few days, my SD Card doesn't get mounted anymore on my Ubuntu
  14.04 LTS machine. It works fine on my 12.04 LTS machine and can also
  be mounted on any Windows machine.

  Syslog output:

  Aug 18 06:42:29 bnasws02 kernel: [65330.017144] usb 1-8: new high-speed USB 
device number 13 using xhci_hcd
  Aug 18 06:42:30 bnasws02 kernel: [65330.148016] usb 1-8: New USB device 
found, idVendor=058f, idProduct=6366
  Aug 18 06:42:30 bnasws02 kernel: [65330.148021] usb 1-8: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Aug 18 06:42:30 bnasws02 kernel: [65330.148023] usb 1-8: Product: Flash Card 
Reader/Writer
  Aug 18 06:42:30 bnasws02 kernel: [65330.148025] usb 1-8: Manufacturer: Generic
  Aug 18 06:42:30 bnasws02 kernel: [65330.148027] usb 1-8: SerialNumber: 
058F63666485
  Aug 18 06:42:30 bnasws02 kernel: [65330.148589] usb-storage 1-8:1.0: USB Mass 
Storage device detected
  Aug 18 06:42:30 bnasws02 kernel: [65330.148695] scsi6 : usb-storage 1-8:1.0
  Aug 18 06:42:30 bnasws02 mtp-probe: checking bus 1, device 13: 
"/sys/devices/pci:00/:00:14.0/usb1/1-8"
  Aug 18 06:42:30 bnasws02 mtp-probe: bus: 1, device: 13 was not an MTP device
  Aug 18 06:42:31 bnasws02 kernel: [65331.147150] scsi 6:0:0:0: Direct-Access   
  Multiple Card  Reader 1.00 PQ: 0 ANSI: 4
  Aug 18 06:42:31 bnasws02 kernel: [65331.147528] sd 6:0:0:0: Attached scsi 
generic sg1 type 0
  Aug 18 06:42:40 bnasws02 kernel: [65340.789407] sd 6:0:0:0: [sdb] Attached 
SCSI removable disk

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-77-generic 3.16.0-77.99~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 18 06:40:25 2016
  InstallationDate: Installed on 2015-08-06 (377 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1614362/+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 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION

[Brian Daniels]

I've had the same issues after applying patches for 14.10.  Had to use
recovery to boot and decided to upgrade to fix.  This did not help as
16.04 has same issue with "Host adapter" errors on Dell PowerEdge 2800
and CERC controller.  OS will not boot.

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

Title:
  Dell CERC Adapter hangs temporarily until reset.  REGRESSION

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 
seconds until reset.
  The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 
7419].  The Dell Poweredge 1800 has newest BIOS (A07).
  All hardware has been tested thoroughly OK except possibly the APIC component 
(Serverset Northbridge?).
  The 14.04LTS with all updates (or not) works fine with a perfectly consistent 
throughput of 77MB/s (slowest HD=66MB/s), RAID5.
  15.10 has the hangs of 10-60 seconds, AND with newest updates as of 
26-FEB-2016.
  I have changed PCI interrupts around and moved card slots to minimize sharing 
and removed cards - repeatedly.
  All hard drives and cables have been thoroughly tested, but the drives are 
mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s.
  The drives not only work perfectly in 14.04LTS, but all Windows versions and 
DOS/BIOS-INT 19 as well (0x13).
  I have tried all combinations of card RAID options Read ahead, Write cache, 
and other BIOS options.
  Relevant dmesg lines (these were consecutive):
  [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0)
  [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ?
  [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0)
  [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.365
  CurrentDesktop: Unity
  Date: Thu Mar  3 05:08:57 2016
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation PowerEdge 1800
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi 
file=u15.10-64/preseed/username.seed boot=casper netboot=nfs 
nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz 
ipv6.disable=1 net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2006
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A07
  dmi.board.name: 0P8611
  dmi.board.vendor: Dell Computer Corporation
  dmi.board.version: A04
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr:
  dmi.product.name: PowerEdge 1800
  dmi.sys.vendor: Dell Computer Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+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 1612305] onibi (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_21-37-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1608236] Re: Regression: S-video output does not work

[Jarno Suni]

Also problem with this system http://askubuntu.com/q/814358/21005

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

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1612305] onza (amd64) - tests ran: 30, failed: 0

[Brad Figg]

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onza__4.4.0-36.55__2016-08-19_21-20-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1608236] Re: Regression: S-video output does not work

[Jarno Suni]

I installed linux-image-4.4.0-36-generic (4.4.0-36.55) and xserver-xorg-
video-intel (2:2.99.917+git20160325-1ubuntu1.1) from Proposed.

It did not resolve this bug.

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

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Stunts]

Thank you Konrad!
Eagerly waiting for OTA13.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1612305] onibi (amd64) - tests ran: 30, failed: 0

[Brad Figg]

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_20-07-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1612305] onza (i386) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onza__4.4.0-36.55__2016-08-19_19-56-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[Stefan Mikulaj]

Here it is, all I found.
OTA-12, STABLE, MEIZU-PD.EN

** Attachment added: "Meizu Pro5 Bluetooth logs,"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4724139/+files/Logs.zip

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

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1612305] onibi (i386) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_18-46-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1612305] onza (amd64) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onza__4.4.0-36.55__2016-08-19_18-34-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1483343] Re: NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

[Fabio C. Barrionuevo]

@Joseph, i see similar error messages in your syslog.

Dell replace the motherboard of my notebook (Latitude 3450), and
consequently processor Core i7--5500U @ 2.4GHz, Nvidia GeForce 830M 2GB
are replaced.

After this fact, none of problems appeared again.

then, by inference, I think the problems occurred due to failure in the
manufacturing process,

if you still want me to perform any test, please explain me step by step
how to run it.

Sorry the noise.

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

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  In Progress

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 1717.146899] [c00c7551b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146904] [c00c7551b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146909] [c00c7551b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146913] [c00c7551b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146922] --- interrupt: 901 at _raw_write_lock+0x68/0xc0
  [ 1717.146922] LR = torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146927] [c00c7551bca0] [c00c7551bcd0] 0xc00c7551bcd0 
(unreliable)
  [ 1717.146934] [c00c7551bcd0] [dd4810b8] 
torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146939] [c00c7551bcf0] [dd480578] 
lock_torture_writer+0x98/0x210 [locktorture]
  [ 1717.146944] [c00c7551bd80] [c00da4d4] kthread+0x114/0x140
  [ 1717.146948] [c00c7551be30] [c000956c] 
ret_from_kernel_thread+0x5c/0x70
  [ 1717.146951] Task dump for CPU 10:
  [ 1717.146953] lock_torture_wr R  running task

[Kernel-packages] [Bug 1579542] Re: My computer reboots instead of shutdown

[luvr]

To make the shutdown work, I created a systemd service that will run
whenever the halt.target or the shutdown.target is to be reached. Since
I need to unbind the EHCI drivers, I named the service, naturally,
'unbind-ehci-drivers'.

First, I created the '/usr/local/sbin/unbind-ehci-drivers' script, which
the service must execute:

--
#!/bin/sh

DRIVER_DIRECTORY='/sys/bus/pci/drivers/ehci-pci'

cd "${DRIVER_DIRECTORY}"
find -mindepth 1 -maxdepth 1 -name '*:*:*.*' -type l -printf '%f\0' | xargs -I 
'{}' --null echo '{}' > unbind
--

Next, the '/etc/systemd/system/unbind-ehci-drivers.service' systemd
service file:

--
[Unit]
Description=Unbind EHCI drivers upon system shutdown
DefaultDependencies=no
Before=shutdown.target halt.target

[Service]
Type=oneshot
ExecStart=/usr/local/sbin/unbind-ehci-drivers

[Install]
WantedBy=halt.target shutdown.target
--

With these files in place, the following command will enable the
service:

root@localhost# systemctl enable unbind-ehci-drivers

Optionally, verify if the service is now enabled:

root@localhost# systemctl is-enabled unbind-ehci-drivers

Two other commands that will show more details about the service:

root@localhost# systemctl --all list-units unbind-ehci-drivers.service
root@localhost# systemctl list-unit-files unbind-ehci-drivers.service

Shutdown works now.
Ref.: 
'http://askubuntu.com/questions/416299/execute-command-before-shutdown-reboot', 
entry "How to Do it with Systemd (it's easier)".

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

Title:
  My computer reboots instead of shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Really basic operation - I go to drop-down system menu and choose
  "Shut down...". My computer goes poweroff but after two, maybe three
  seconds it starts booting process automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  corsseir   1818 F pulseaudio
   /dev/snd/pcmC0D0p:   corsseir   1818 F...m pulseaudio
   /dev/snd/controlC0:  corsseir   1818 F pulseaudio
   /dev/snd/controlC1:  corsseir   1818 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  8 18:41:01 2016
  InstallationDate: Installed on 2016-04-21 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=ddb69d9b-bdbe-46a8-9071-81c3762158c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+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 1615082] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1615082

Title:
  kernel NULL pointer dereference on apparmor profile update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used aa-logprof to find more things out to be added to my custom
  apache2 apparmor file. Since PHP created tons of files in /tmp in the
  form of /tmp/php* I've decided to add this:

  /tmp/php* rw,

  I'm not sure if it caused the problem, but after this
  /etc/init.d/apparmor reload froze and there was the following in the
  output of dmesg command:

  
  [13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" 
pid=23590 comm="apparmor_parser"
  [13838.920067] [ cut here ]
  [13838.920079] WARNING: CPU: 0 PID: 23590 at 
/build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
  [13838.920083] AppArmor WARN profile_cmp: ((!b)): 
  [13838.920085] Modules linked in:
  [13838.920088]  binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas 
irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb 
ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm 
drm_kms_helper
  [13838.920166]  syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops 
usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core 
pata_acpi fjes
  [13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 
4.4.0-34-generic #53-Ubuntu
  [13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
  [13838.920195]  0086 88f44738 880128bffc00 
813f11b3
  [13838.920199]  880128bffc48 81cf08e8 880128bffc38 
81081102
  [13838.920204]  8800c8d7d400  000a 

  [13838.920208] Call Trace:
  [13838.920218]  [] dump_stack+0x63/0x90
  [13838.920224]  [] warn_slowpath_common+0x82/0xc0
  [13838.920228]  [] warn_slowpath_fmt+0x5c/0x80
  [13838.920232]  [] ? u32_swap+0x10/0x10
  [13838.920236]  [] profile_cmp+0xed/0x180
  [13838.920239]  [] aa_vec_unique+0x163/0x240
  [13838.920244]  [] __aa_labelset_update_subtree+0x687/0x820
  [13838.920249]  [] ? kzfree+0x2d/0x40
  [13838.920254]  [] aa_replace_profiles+0x59b/0xb70
  [13838.920259]  [] ? __kmalloc+0x22e/0x250
  [13838.920263]  [] policy_update+0x9f/0x1f0
  [13838.920267]  [] profile_replace+0x13/0x20
  [13838.920272]  [] __vfs_write+0x18/0x40
  [13838.920275]  [] vfs_write+0xa9/0x1a0
  [13838.920279]  [] ? do_sys_open+0x1bf/0x2a0
  [13838.920282]  [] SyS_write+0x55/0xc0
  [13838.920288]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [13838.920291] ---[ end trace a19473a0fd8d9556 ]---
  [13838.920305] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [13838.920475] IP: [] profile_cmp+0x2f/0x180
  [13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 
  [13838.920684] Oops:  [#1] SMP 
  [13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp 
nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log 
nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp 
ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev 
input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit
  [13838.922791]  ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm 
megaraid_sas bnx2 pps_core pata_acpi fjes
  [13838.923223] CPU: 0 PID: 23590 Comm: apparmor_parser Tainted: GW
   4.4.0-34-generic #53-Ubuntu
  [13838.923369] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 

[Kernel-packages] [Bug 1615082] Re: kernel NULL pointer dereference on apparmor profile update

[LGB [Gábor Lénárt]]

I've also attached some files, with full dmesg output, uname -a, lspci,
version info, and the apparmor profile for apache2.

** Attachment added: "Logs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615082/+attachment/4724162/+files/bug-info.tgz

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

Title:
  kernel NULL pointer dereference on apparmor profile update

Status in linux package in Ubuntu:
  New

Bug description:
  I've used aa-logprof to find more things out to be added to my custom
  apache2 apparmor file. Since PHP created tons of files in /tmp in the
  form of /tmp/php* I've decided to add this:

  /tmp/php* rw,

  I'm not sure if it caused the problem, but after this
  /etc/init.d/apparmor reload froze and there was the following in the
  output of dmesg command:

  
  [13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" 
pid=23590 comm="apparmor_parser"
  [13838.920067] [ cut here ]
  [13838.920079] WARNING: CPU: 0 PID: 23590 at 
/build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
  [13838.920083] AppArmor WARN profile_cmp: ((!b)): 
  [13838.920085] Modules linked in:
  [13838.920088]  binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas 
irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb 
ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm 
drm_kms_helper
  [13838.920166]  syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops 
usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core 
pata_acpi fjes
  [13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 
4.4.0-34-generic #53-Ubuntu
  [13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
  [13838.920195]  0086 88f44738 880128bffc00 
813f11b3
  [13838.920199]  880128bffc48 81cf08e8 880128bffc38 
81081102
  [13838.920204]  8800c8d7d400  000a 

  [13838.920208] Call Trace:
  [13838.920218]  [] dump_stack+0x63/0x90
  [13838.920224]  [] warn_slowpath_common+0x82/0xc0
  [13838.920228]  [] warn_slowpath_fmt+0x5c/0x80
  [13838.920232]  [] ? u32_swap+0x10/0x10
  [13838.920236]  [] profile_cmp+0xed/0x180
  [13838.920239]  [] aa_vec_unique+0x163/0x240
  [13838.920244]  [] __aa_labelset_update_subtree+0x687/0x820
  [13838.920249]  [] ? kzfree+0x2d/0x40
  [13838.920254]  [] aa_replace_profiles+0x59b/0xb70
  [13838.920259]  [] ? __kmalloc+0x22e/0x250
  [13838.920263]  [] policy_update+0x9f/0x1f0
  [13838.920267]  [] profile_replace+0x13/0x20
  [13838.920272]  [] __vfs_write+0x18/0x40
  [13838.920275]  [] vfs_write+0xa9/0x1a0
  [13838.920279]  [] ? do_sys_open+0x1bf/0x2a0
  [13838.920282]  [] SyS_write+0x55/0xc0
  [13838.920288]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [13838.920291] ---[ end trace a19473a0fd8d9556 ]---
  [13838.920305] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [13838.920475] IP: [] profile_cmp+0x2f/0x180
  [13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 
  [13838.920684] Oops:  [#1] SMP 
  [13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp 
nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log 
nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp 
ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev 
input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit
  [13838.922791]  ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm 
megaraid_sas bnx2 pps_core pata_acpi fjes
  [13838.923223] CPU: 0 

[Kernel-packages] [Bug 1615082] [NEW] kernel NULL pointer dereference on apparmor profile update

[LGB [Gábor Lénárt]]

Public bug reported:

I've used aa-logprof to find more things out to be added to my custom
apache2 apparmor file. Since PHP created tons of files in /tmp in the
form of /tmp/php* I've decided to add this:

/tmp/php* rw,

I'm not sure if it caused the problem, but after this
/etc/init.d/apparmor reload froze and there was the following in the
output of dmesg command:


[13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" 
pid=23590 comm="apparmor_parser"
[13838.920067] [ cut here ]
[13838.920079] WARNING: CPU: 0 PID: 23590 at 
/build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
[13838.920083] AppArmor WARN profile_cmp: ((!b)): 
[13838.920085] Modules linked in:
[13838.920088]  binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas 
irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb 
ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm 
drm_kms_helper
[13838.920166]  syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops 
usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core 
pata_acpi fjes
[13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 
4.4.0-34-generic #53-Ubuntu
[13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
[13838.920195]  0086 88f44738 880128bffc00 
813f11b3
[13838.920199]  880128bffc48 81cf08e8 880128bffc38 
81081102
[13838.920204]  8800c8d7d400  000a 

[13838.920208] Call Trace:
[13838.920218]  [] dump_stack+0x63/0x90
[13838.920224]  [] warn_slowpath_common+0x82/0xc0
[13838.920228]  [] warn_slowpath_fmt+0x5c/0x80
[13838.920232]  [] ? u32_swap+0x10/0x10
[13838.920236]  [] profile_cmp+0xed/0x180
[13838.920239]  [] aa_vec_unique+0x163/0x240
[13838.920244]  [] __aa_labelset_update_subtree+0x687/0x820
[13838.920249]  [] ? kzfree+0x2d/0x40
[13838.920254]  [] aa_replace_profiles+0x59b/0xb70
[13838.920259]  [] ? __kmalloc+0x22e/0x250
[13838.920263]  [] policy_update+0x9f/0x1f0
[13838.920267]  [] profile_replace+0x13/0x20
[13838.920272]  [] __vfs_write+0x18/0x40
[13838.920275]  [] vfs_write+0xa9/0x1a0
[13838.920279]  [] ? do_sys_open+0x1bf/0x2a0
[13838.920282]  [] SyS_write+0x55/0xc0
[13838.920288]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[13838.920291] ---[ end trace a19473a0fd8d9556 ]---
[13838.920305] BUG: unable to handle kernel NULL pointer dereference at 
0038
[13838.920475] IP: [] profile_cmp+0x2f/0x180
[13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 
[13838.920684] Oops:  [#1] SMP 
[13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp nf_conntrack_irc 
ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter 
ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp 
xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm 
dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds 
i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit
[13838.922791]  ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm 
megaraid_sas bnx2 pps_core pata_acpi fjes
[13838.923223] CPU: 0 PID: 23590 Comm: apparmor_parser Tainted: GW  
 4.4.0-34-generic #53-Ubuntu
[13838.923369] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
[13838.923485] task: 880035b86400 ti: 880128bfc000 task.ti: 
880128bfc000
[13838.923599] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
[13838.923734] RSP: 0018:880128bffcb0  EFLAGS: 00010086
[13838.923816] RAX:  RBX: 8800c8d7d400 RCX: 0006
[13838.923916] RDX:  RSI:  RDI: 0009
[13838.924017] RBP: 880128bffcc0 R08: 000a R09: 0562

[Kernel-packages] [Bug 1612305] onibi (amd64) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_17-24-00/results-index.html

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

Title:
  linux: 4.4.0-36.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-36.55 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1587714] Re: MacBookPro11, 4 fails to poweroff or suspend

[Kamal Mostafa]

https://lists.ubuntu.com/archives/kernel-team/2016-August/079594.html

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

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

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

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

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

Title:
  MacBookPro11,4 fails to poweroff or suspend

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  Since the release of the 2015 MacBookPro11,4 (15" retina), it has been
  unable to suspend or poweroff on linux.  Recently,
  https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a
  patch that works to fix these issues.  The patch is in comment #172,
  and is also attached to this bugreport, and reported to work very well
  by users of other distributions.  In addition, I can confirm that
  building the latest xenial 4.4.0-22-generic kernel with this patch
  applied fixes the issue.  Can this be added to the official xenial
  kernel?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1587714/+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 1587714] Re: MacBookPro11, 4 fails to poweroff or suspend

[Kamal Mostafa]

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Triaged

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  MacBookPro11,4 fails to poweroff or suspend

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Yakkety:
  Triaged

Bug description:
  Since the release of the 2015 MacBookPro11,4 (15" retina), it has been
  unable to suspend or poweroff on linux.  Recently,
  https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a
  patch that works to fix these issues.  The patch is in comment #172,
  and is also attached to this bugreport, and reported to work very well
  by users of other distributions.  In addition, I can confirm that
  building the latest xenial 4.4.0-22-generic kernel with this patch
  applied fixes the issue.  Can this be added to the official xenial
  kernel?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1587714/+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 1613787] Re: xfrm: ipsec crash when updating spd thresholds

[Kamal Mostafa]

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  xfrm: ipsec crash when updating spd thresholds

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Fixed upstream by this commit (only in IPsec tree for now):

  
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb
  http://patchwork.ozlabs.org/patch/654026/

  To update the thresholds: 'ip xfrm policy set hthresh4 24 32'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613787/+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 1614791] Re: stress-ng freezes system

[Kenneth]

apport-collect 1614791 cannot run because it is unable to identify the
application

** Changed in: stress-ng (Ubuntu)
   Status: New => Incomplete

** Changed in: stress-ng (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/1614791

Title:
  stress-ng freezes system

Status in linux package in Ubuntu:
  Incomplete
Status in stress-ng package in Ubuntu:
  Confirmed

Bug description:
  While running "stress-ng --aggressive --verify --timeout 2860 --log-
  file stress-ng-brk.log -v --brk 0", the system would freeze within an
  hour of running the test.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: stress-ng 0.05.23-1ubuntu2
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  Date: Fri Aug 19 01:04:30 2016
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcLoadAvg: 0.00 0.00 0.00 1/1200 10125
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 7809 00:14:652 0 EOF
   2: FLOCK  ADVISORY  WRITE 7797 00:14:646 0 EOF
   3: POSIX  ADVISORY  WRITE 7799 00:14:656 0 EOF
   4: POSIX  ADVISORY  WRITE 8810 00:14:670 0 EOF
   5: POSIX  ADVISORY  WRITE 4914 00:14:419 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-34-generic (buildd@bos01-ppc64el-022) (gcc 
version 5.3.1 20160413 (User Name/IBM 5.3.1-14ubuntu2.1) ) #53-User Name SMP 
Wed Jul 27 16:04:07 UTC 2016
  SourcePackage: stress-ng
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614791/+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 1612718] onza (i386) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_15-28-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[Stefan Mikulaj]

I will compress the logs as they are many and will post them when have
access to a PC later today

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

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[Stefan Mikulaj]

** Attachment added: "Logs"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4724017/+files/application-legacy-ubuntu-system-settings-.log.1.gz

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

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

[Stefan Mikulaj]

I managed to find the logs.

** Attachment added: "Logs"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4724015/+files/application-legacy-ubuntu-system-settings-.log

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

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1579542] Re: My computer reboots instead of shutdown

[luvr]

Running Ubuntu 16.04.
Just tested with v4.8-rc2 mainline build, and the problem remains.

In my case, there are no devices in /sys/bus/pci/drivers/xhci_hcd, so there's 
nothing to unbind there.
Instead, unbinding the ehci-pci devices made the shutdown work:

echo ':00:12.2
:00:13.2' > /sys/bus/pci/drivers/ehci-pci/unbind

I'll try and create a system halt script to do this automatically upon
each shutdown/ halt.

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

Title:
  My computer reboots instead of shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Really basic operation - I go to drop-down system menu and choose
  "Shut down...". My computer goes poweroff but after two, maybe three
  seconds it starts booting process automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  corsseir   1818 F pulseaudio
   /dev/snd/pcmC0D0p:   corsseir   1818 F...m pulseaudio
   /dev/snd/controlC0:  corsseir   1818 F pulseaudio
   /dev/snd/controlC1:  corsseir   1818 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  8 18:41:01 2016
  InstallationDate: Installed on 2016-04-21 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=ddb69d9b-bdbe-46a8-9071-81c3762158c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+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 1609913] Re: linux: 4.6.0-10.12 -proposed tracker

[Steve Langasek]

removed block-proposed tag from this bug, because 4.6.0-10.12 is not in
-proposed right now.

** Tags removed: block-proposed

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1609913/+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 1612718] onibi (i386) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_14-22-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1612718] onza (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_14-07-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1604344] Re: changelog: add CVEs as first class citizens

[Brad Figg]

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

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

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

Title:
  changelog: add CVEs as first class citizens

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  We no longer use bugs routinely for CVEs so pull the CVE number up as
  a bug number rather than letting the fixes all fall into misc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604344/+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 1587714] Re: MacBookPro11, 4 fails to poweroff or suspend

[Joe Barnett]

Updated patch with a Singed-off-by line has been posted to
https://patchwork.kernel.org/patch/9289777/

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

Title:
  MacBookPro11,4 fails to poweroff or suspend

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Since the release of the 2015 MacBookPro11,4 (15" retina), it has been
  unable to suspend or poweroff on linux.  Recently,
  https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a
  patch that works to fix these issues.  The patch is in comment #172,
  and is also attached to this bugreport, and reported to work very well
  by users of other distributions.  In addition, I can confirm that
  building the latest xenial 4.4.0-22-generic kernel with this patch
  applied fixes the issue.  Can this be added to the official xenial
  kernel?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1587714/+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 1614987] [NEW] cannot connect BT speaker to laptop running unity8

[Victor gonzalez]

Public bug reported:

Laptop running unity8::

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Codename:   yakkety

HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

BT speaker: Avrha Strauss P/N:11BQALT01

Steps to reproduce:

1º On your laptop running unity8, go to System settings>Bluetooth and turn it on
2º Turn on your BT speaker as well(on this model just press the BT button a few 
seconds for being discoverable)
3º After a few seconds BT speaker should be found by the laptop, but it doesn't

Current result: Laptop can discover and pair with Utouch and android
devices, but is not seeing the BT speaker

Expected result: Laptop should discover and be able to pair BT speakers

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

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

Title:
  cannot connect BT speaker to laptop running unity8

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop running unity8::

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  BT speaker: Avrha Strauss P/N:11BQALT01

  Steps to reproduce:

  1º On your laptop running unity8, go to System settings>Bluetooth and turn it 
on
  2º Turn on your BT speaker as well(on this model just press the BT button a 
few seconds for being discoverable)
  3º After a few seconds BT speaker should be found by the laptop, but it 
doesn't

  Current result: Laptop can discover and pair with Utouch and android
  devices, but is not seeing the BT speaker

  Expected result: Laptop should discover and be able to pair BT
  speakers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1614987/+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 1612718] onibi (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_13-17-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1612718] onza (i386) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_12-17-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04

[Anthony Buckley]

OK, I've tested a few of the mainlines (binary chop) and as far as I can
tell the last kernel that worked OK was 4.3.6-040306-generic
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3.6-wily/). So it
looks to me as if its since the start of the 4.4... series.

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

Title:
  Network scanner not detected by xsane after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hopefully I'm reporting this in the correct area/group. Sorry if not.
  After upgrading to 16.04, my scanner is no longer detected by xsane (and 
other scan apps.) The model is 'Epson WF-3520' multi-function and is connected 
wirelessly to the network.
  The problem occurs on all my computers: A Dell 64 bit desktop, An Asus 64 bit 
laptop, A Medion 32 bit laptop.
  I've upgraded to the latest software released by the manufacturer on 2 
computers, but it makes no difference.
  Printing works OK and also the scanner is detected if I connect using a USB 
cable (a second printer is installed though).
  The problem only occurs using the 'linux-image-4.4.0...' series of kernels. 
If I boot with any of the previous kernels available, 'linux-image-4.2.0...' or 
'linux-image-3.19.0...' everything works OK.
  I am able to ping the scanner.
  I've tried a number of suggested fixes from searching around various forums, 
although many of these relate to 'back-end' scanners connected to a host for 
network access which is not applicable as mine is connected directly to the 
network. In any case none have worked.
  I have tried the following:
  . Removing all manufacturer software and /usr/sane.d/epkowa.conf
  . Comment out all entries in the /usr/sane.d/dll (Back-end related)
  . Comment out all entries in the /usr/sane.d/dll.conf.conf except 'net' and 
adding 'epkowa' (Back-end related)
  . Disable the firewall (ufw)
  . Specifically adding a port to use (1865) (ie. net 192.1... 1865
  . Linking the libraries in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane

  Other than that I'm at a loss and sticking with older kernels.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   4520 F pulseaudio
   /dev/snd/controlC1:  tony   4520 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug 14 16:37:16 2016
  HibernationDevice: RESUME=UUID=762f657a-d174-4173-b09d-52d580c09a91
  InstallationDate: Installed on 2013-10-01 (1047 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK Computer Inc. N71Jq
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=dea23950-d6b3-498c-abba-a94513b58579 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (14 days ago)
  dmi.bios.date: 12/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N71Jq.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N71Jq
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN71Jq.204:bd12/24/2009:svnASUSTeKComputerInc.:pnN71Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN71Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N71Jq
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+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 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus

[Fred Zelastian]

Tried to install Ubuntu Gnome 16.04.1 with NVIDIA Driver 367.xx using
the GDM display manager yesterday and resulted in black screen at login.

Did the same today with the newly released NVIDIA Driver 370.23 (beta, I
think) and everything is actually working fine - no black screens, but
the login seemed kinda funky. Although there don't appear to be any
technical issues so far, I'm not entirely sure if that NVIDIA Driver
build is stable. Not sure if it's just affecting me either, but thought
I'd throw that comment in there.

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers on a laptop with Optimus

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1559576/+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 1612718] onibi (i386) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_11-36-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1614953] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1614953

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+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 1614953] [NEW] hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Andrew McDermott]

Public bug reported:

Since I started using IPv6 I noticed the following kernel error:

Thu Aug 18 15:05:01 2016] : hw csum failure
[Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P   
OE   4.4.0-34-generic #53-Ubuntu
[Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
[Thu Aug 18 15:05:01 2016]  0286 c05989f2 8807573dfcd0 
813f11b3
[Thu Aug 18 15:05:01 2016]   0008 8807573dfce8 
8171f6e8
[Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 8171639b 
fe091360
[Thu Aug 18 15:05:01 2016] Call Trace:
[Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
[Thu Aug 18 15:05:01 2016]  [] netdev_rx_csum_fault+0x38/0x40
[Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
[Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
[Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
[Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
[Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
[Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
[Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
[Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

It repeats periodically:

$ dmesg -T | grep 'hw csum failure' | wc -l
201

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug 19 13:47:54 2016
HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
InstallationDate: Installed on 2016-04-24 (116 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic  N/A
 linux-firmware1.157.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum 

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Andrew McDermott]

I mentioned that it repeats - here's the uptime to get a feeling of the
frequency:

$ uptime
 13:51:59 up 1 day,  4:17,  2 users,  load average: 0.40, 0.67, 0.71

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+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 1614887] Re: Lage samba file transfers block btrfs to hung task

[S. W.]

i also confirmed this bug with the latest v4.7.1 mainline build from the
ubuntu ppa

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

Title:
  Lage samba file transfers block btrfs to hung task

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  this bug occurs when user transfer big files ~1gb to the samba server
  on xenial/wily

  on wily this problem was NOT showing with samba 4.2 (i guess) until
  samba was also upgraded to 4.3.

  the samba runs on a KVM VM

  samba version: 4.3.9+dfsg-0ubuntu0.16.04.

  
  [   30.171211] zram: Added device: zram0
  [   30.356301] zram0: detected capacity change from 0 to 1518252032
  [   30.668855] Adding 1482664k swap on /dev/zram0.  Priority:5 extents:1 
across:1482664k SSFS
  [   35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or 
missing monitors config: c9e3, 0
  [   45.008364] Non-volatile memory driver v1.3
  [65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds.
  [65636.820128]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820131] btrfs-cleaner   D 88005ae93ce8 0   631  2 
0x
  [65636.820137]  88005ae93ce8 8800bbb86400 8801b0dc3e80 
8801b0dc2580
  [65636.820139]  88005ae94000 8801851971f0 880185197000 
8801851971f0
  [65636.820141]  0001 88005ae93d00 81829ec5 
8801b7fc4000
  [65636.820143] Call Trace:
  [65636.820182]  [] schedule+0x35/0x80
  [65636.820360]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820395]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820409]  [] start_transaction+0x2c5/0x4b0 [btrfs]
  [65636.820434]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
  [65636.820452]  [] btrfs_drop_snapshot+0x7f/0x830 [btrfs]
  [65636.820454]  [] ? __schedule+0x3b6/0xa30
  [65636.820467]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
  [65636.820480]  [] cleaner_kthread+0xcf/0x220 [btrfs]
  [65636.820493]  [] ? check_leaf+0x360/0x360 [btrfs]
  [65636.820497]  [] kthread+0xd8/0xf0
  [65636.820499]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820505]  [] ret_from_fork+0x3f/0x70
  [65636.820507]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds.
  [65636.820551]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820559] kworker/u4:1D 880008433c48 0  7760  2 
0x
  [65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820581]  880008433c48 0040 8800b9d98c80 
8801b51a9900
  [65636.820582]  880008434000 8801851941f0 880185194000 
8801851941f0
  [65636.820584]  0001 880008433c60 81829ec5 
8801b7fc4000
  [65636.820586] Call Trace:
  [65636.820588]  [] schedule+0x35/0x80
  [65636.820602]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820604]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820620]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820650]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
  [65636.820667]  [] btrfs_finish_ordered_io+0x435/0x650 
[btrfs]
  [65636.820692]  [] finish_ordered_fn+0x15/0x20 [btrfs]
  [65636.820718]  [] btrfs_scrubparity_helper+0xca/0x2f0 
[btrfs]
  [65636.820723]  [] ? try_to_wake_up+0x47/0x3b0
  [65636.820741]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
  [65636.820753]  [] process_one_work+0x165/0x480
  [65636.820755]  [] worker_thread+0x4b/0x4c0
  [65636.820757]  [] ? process_one_work+0x480/0x480
  [65636.820758]  [] kthread+0xd8/0xf0
  [65636.820760]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820761]  [] ret_from_fork+0x3f/0x70
  [65636.820763]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820770] INFO: task kworker/u4:2:7814 blocked for more than 120 seconds.
  [65636.820771]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820772] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820773] kworker/u4:2D 880102027c48 0  7814  2 
0x
  [65636.820848] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820850]  880102027c48 0040 8801b51ae400 
8801b51a8c80
  [65636.820852]  880102028000 8801851941f0 880185194000 
8801851941f0
  [65636.820853]  0001 880102027c60 81829ec5 
8801b7fc4000
  [65636.820855] Call Trace:
  [65636.820857]  [] schedule+0x35/0x80
  [65636.820877]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820879]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820893]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820908]  [] 

[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Stefan Bader]

The required change will be in the 4.4.0-36 (includes the 4.4.0-35
updates) which is currently in -proposed and waiting for verification
and regression testing to finish. If there are no problems found this is
supposed to get released by Aug-29th.

https://launchpad.net/ubuntu/+source/linux/4.4.0-36.55

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  divide error:  [#1] SMP in task_numa_migrate - handle_mm_fault

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1
  the host system has crashed (load > 200) 3 times in the last 3 days.

  Always with this stack trace:

  Apr  9 19:01:09 cnode9.0 kernel: [197071.195577] divide error:  [#1] SMP 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net 
vhost macvtap macvlan arc4 md4 nls_utf8 ci
  fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag
   dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_fil
  ter ip6_tables iptable_mangle xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables dum
  my bridge stp llc ipmi_ssif ipmi_devintf intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm dcdbas irqbypass crct10dif_p
  clmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd joydev input_leds nf_nat_ftp sb_edac nf_conntrack_ftp e
  dac_core cdc_ether nf_nat_pptp usbnet nf_conntrack_pptp mii nf_nat_proto_gre 
lpc_ich nf_nat_sip ioatdma nf_nat nf_conntrack_sip nfsd ipmi_si 
  8250_fintek nf_conntrack_proto_gre ipmi_msghandler acpi_pad wmi shpchp 
nf_conntrack acpi_power_meter mac_hid auth_rpcgss nfs_acl bonding nfs 
  lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs hid_generic usbhid 
hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_
  xor async_tx xor ixgbe raid6_pq libcrc32c igb vxlan raid1 i2c_algo_bit 
ip6_udp_tunnel dca udp_tunnel ahci raid0 ptp libahci megaraid_sas mult
  ipath pps_core mdio linear fjes
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197014] CPU: 13 PID: 3147726 Comm: 
ceph-osd Not tainted 4.4.0-15-generic #31~14
  .04.1-Ubuntu
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197085] Hardware name: Dell Inc. 
PowerEdge R720/0XH7F2, BIOS 2.5.2 01/28/2015
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197154] task: 88252be1ee00 ti: 
8824fc0d4000 task.ti: 8824fc0d4000
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197221] RIP: 
0010:[]  [] task_numa_find_cpu+0x238/0x700
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197300] RSP: :8824fc0d7ba8  
EFLAGS: 00010257
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197340] RAX:  RBX: 
8824fc0d7c48 RCX: 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197406] RDX:  RSI: 
88479f18 RDI: 884782a47600
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197473] RBP: 8824fc0d7c10 R08: 
000102eea157 R09: 01a8
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197540] R10: 0002404b R11: 
023f R12: 88238093
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197606] R13: 0008 R14: 
008c R15: 0124
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197673] FS:  7f19aab5b700() 
GS:88479f18() knlGS:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197741] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197782] CR2: 25469600 CR3: 
0023846bc000 CR4: 000426e0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197848] Stack:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197880]  817425fb 
8829af3e9e00 00f6 88252be1ee00
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197965]  008d 
0225 00016d40 008d
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198047]  88252be1ee00 
01ad 8824fc0d7c48 00e1
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198132] Call Trace:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198172]  [] ? 
tcp_schedule_loss_probe+0x12b/0x1b0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198219]  [] 
task_numa_migrate+0x4a0/0x930
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198264]  [] ? 
release_sock+0x117/0x160
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198306]  [] 
numa_migrate_preferred+0x79/0x80
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198350]  [] 
task_numa_fault+0x91d/0xcc0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198395]  [] ? 
mpol_misplaced+0x14e/0x190
  

[Kernel-packages] [Bug 1562618] Re: whole OS freezes seemingly randomly

[Vincent Gerris]

Hi,

Since I read of the vt bug being fixed, I tried another 4.4 kernel.
I also upgraded my SSD to the latest firmware.
I have:
ubuntu@ubuntu-Lenovo-Yoga-2-11:~$ uname -a
Linux ubuntu-Lenovo-Yoga-2-11 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 
16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I still get a freeze when I play bluetooth audio and do a file transfer.
I think I will try the same on Windows and see what happens.

I am considering dual boot to fix these issues if anyone can push this.
The laptop is practicallly useless now and I actually need it.

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

Title:
  whole OS freezes seemingly randomly

Status in linux package in Ubuntu:
  Expired

Bug description:
  I had some random freezes of the whole operating system.
  No caps lock response or terminal switching, nothng.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent1714 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 27 23:46:02 2016
  HibernationDevice: RESUME=UUID=8180a7b6-a1c0-494a-9f65-99a7b54f6deb
  InstallationDate: Installed on 2015-11-01 (147 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20332
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=44fb018f-3dbd-4eb6-ab9a-6668de8d13d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (2 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562618/+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 1612718] onza (amd64) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_10-30-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1608820] Re: Cannot use BT speaker - sink is suspended

[Jean-Baptiste Lallement]

After some experiments on a up to date yakkety, I cannot make audio BT work 
after a resume from suspend. The following procedure works around the problem:
1. With a BT speaker already paired, power off the BT speaker
2. Reboot the laptop
3. Go to the BT indicator, and with the BT speaker still off, select the menu 
item for the speaker, and enable the connection
4. Turn on the BT speaker <- BT connection will establish automatically. At 
this point the ouput goes to the speaker but you cannot control the volume
5. Go to sound settings and select the speaker in the list of output devices.

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

Title:
  Cannot use BT speaker - sink is suspended

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After a fresh boot or resuming from suspend it is possible to connect to a BT 
speaker but not possible to play anything.
  Furthermore, if I play a video from youtube, the stream plays fine if the 
output is the internal speaker, but as soon as I select the BT speaker the 
stream hangs. It resumes immediately if I switch back to the internal speaker.

  When I play something over the BT speaker the following lines are logged in 
the journal:
  pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not 
connected, selecting off profile
  bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready
  rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users.
  rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) 
owned by '1000' RT at priority 5.
  rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users.
  pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed 
for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not 
Authorized)
  kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: 
zeitgeist-datahub.vala:212: Error during inserting events: 
GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: 
interpretation, manifestation and actor are required
  wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 
14:0c:76:71:a1:f4 [GTK=CCMP]
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  2 09:09:18 2016
  InstallationDate: Installed on 2013-09-03 (1063 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: C4:85:08:A7:45:76  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING
    RX bytes:3492 acl:70 sco:0 events:137 errors:0
    TX bytes:4838 acl:64 sco:0 commands:57 errors:0
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820/+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 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Philipp Noack]

Had the same divide error and a hanging server myself. Ubuntu 16.04.1
LTS with "linux-image-4.4.0-31-generic". Now running "linux-
image-4.4.0-34-generic".

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

Title:
  divide error:  [#1] SMP in task_numa_migrate - handle_mm_fault

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

Bug description:
  While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1
  the host system has crashed (load > 200) 3 times in the last 3 days.

  Always with this stack trace:

  Apr  9 19:01:09 cnode9.0 kernel: [197071.195577] divide error:  [#1] SMP 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net 
vhost macvtap macvlan arc4 md4 nls_utf8 ci
  fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag
   dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_fil
  ter ip6_tables iptable_mangle xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables dum
  my bridge stp llc ipmi_ssif ipmi_devintf intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm dcdbas irqbypass crct10dif_p
  clmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd joydev input_leds nf_nat_ftp sb_edac nf_conntrack_ftp e
  dac_core cdc_ether nf_nat_pptp usbnet nf_conntrack_pptp mii nf_nat_proto_gre 
lpc_ich nf_nat_sip ioatdma nf_nat nf_conntrack_sip nfsd ipmi_si 
  8250_fintek nf_conntrack_proto_gre ipmi_msghandler acpi_pad wmi shpchp 
nf_conntrack acpi_power_meter mac_hid auth_rpcgss nfs_acl bonding nfs 
  lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs hid_generic usbhid 
hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_
  xor async_tx xor ixgbe raid6_pq libcrc32c igb vxlan raid1 i2c_algo_bit 
ip6_udp_tunnel dca udp_tunnel ahci raid0 ptp libahci megaraid_sas mult
  ipath pps_core mdio linear fjes
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197014] CPU: 13 PID: 3147726 Comm: 
ceph-osd Not tainted 4.4.0-15-generic #31~14
  .04.1-Ubuntu
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197085] Hardware name: Dell Inc. 
PowerEdge R720/0XH7F2, BIOS 2.5.2 01/28/2015
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197154] task: 88252be1ee00 ti: 
8824fc0d4000 task.ti: 8824fc0d4000
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197221] RIP: 
0010:[]  [] task_numa_find_cpu+0x238/0x700
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197300] RSP: :8824fc0d7ba8  
EFLAGS: 00010257
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197340] RAX:  RBX: 
8824fc0d7c48 RCX: 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197406] RDX:  RSI: 
88479f18 RDI: 884782a47600
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197473] RBP: 8824fc0d7c10 R08: 
000102eea157 R09: 01a8
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197540] R10: 0002404b R11: 
023f R12: 88238093
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197606] R13: 0008 R14: 
008c R15: 0124
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197673] FS:  7f19aab5b700() 
GS:88479f18() knlGS:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197741] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197782] CR2: 25469600 CR3: 
0023846bc000 CR4: 000426e0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197848] Stack:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197880]  817425fb 
8829af3e9e00 00f6 88252be1ee00
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197965]  008d 
0225 00016d40 008d
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198047]  88252be1ee00 
01ad 8824fc0d7c48 00e1
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198132] Call Trace:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198172]  [] ? 
tcp_schedule_loss_probe+0x12b/0x1b0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198219]  [] 
task_numa_migrate+0x4a0/0x930
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198264]  [] ? 
release_sock+0x117/0x160
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198306]  [] 
numa_migrate_preferred+0x79/0x80
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198350]  [] 
task_numa_fault+0x91d/0xcc0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198395]  [] ? 
mpol_misplaced+0x14e/0x190
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198439]  [] 
handle_pte_fault+0x5a8/0x14c0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198485]  [] ? 
futex_wake+0x81/0x150
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198526]  [] ? 

[Kernel-packages] [Bug 1608820] Re: Cannot use BT speaker - sink is suspended

[Will Cooke]

Added to Trello: https://trello.com/c/N0adjFrK/12-bug-1608820-cannot-
use-bt-speaker-sink-is-suspended

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Luke Yelavich (themuso)

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

Title:
  Cannot use BT speaker - sink is suspended

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After a fresh boot or resuming from suspend it is possible to connect to a BT 
speaker but not possible to play anything.
  Furthermore, if I play a video from youtube, the stream plays fine if the 
output is the internal speaker, but as soon as I select the BT speaker the 
stream hangs. It resumes immediately if I switch back to the internal speaker.

  When I play something over the BT speaker the following lines are logged in 
the journal:
  pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not 
connected, selecting off profile
  bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready
  rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users.
  rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) 
owned by '1000' RT at priority 5.
  rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users.
  pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed 
for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not 
Authorized)
  kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: 
zeitgeist-datahub.vala:212: Error during inserting events: 
GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: 
interpretation, manifestation and actor are required
  wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 
14:0c:76:71:a1:f4 [GTK=CCMP]
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  2 09:09:18 2016
  InstallationDate: Installed on 2013-09-03 (1063 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: C4:85:08:A7:45:76  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING
    RX bytes:3492 acl:70 sco:0 events:137 errors:0
    TX bytes:4838 acl:64 sco:0 commands:57 errors:0
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820/+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 1612718] onibi (amd64) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_09-53-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1521173] Re: AER: Corrected error received: id=00e0

[JujuLand]

Humm ... typo : booting on a live DvD, obviously :)

A+

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1521173] Re: AER: Corrected error received: id=00e0

[JujuLand]

Hi, I had a look to the link you give, and saw there is a way to boot
using pci=noaer parameter.

It's a good way while no other solution has been found, but does this
method is usable when booting on a live hd to install on an HD

Thanks
A+

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1614887] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1614887

Title:
  Lage samba file transfers block btrfs to hung task

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  this bug occurs when user transfer big files ~1gb to the samba server
  on xenial/wily

  on wily this problem was NOT showing with samba 4.2 (i guess) until
  samba was also upgraded to 4.3.

  the samba runs on a KVM VM

  samba version: 4.3.9+dfsg-0ubuntu0.16.04.

  
  [   30.171211] zram: Added device: zram0
  [   30.356301] zram0: detected capacity change from 0 to 1518252032
  [   30.668855] Adding 1482664k swap on /dev/zram0.  Priority:5 extents:1 
across:1482664k SSFS
  [   35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or 
missing monitors config: c9e3, 0
  [   45.008364] Non-volatile memory driver v1.3
  [65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds.
  [65636.820128]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820131] btrfs-cleaner   D 88005ae93ce8 0   631  2 
0x
  [65636.820137]  88005ae93ce8 8800bbb86400 8801b0dc3e80 
8801b0dc2580
  [65636.820139]  88005ae94000 8801851971f0 880185197000 
8801851971f0
  [65636.820141]  0001 88005ae93d00 81829ec5 
8801b7fc4000
  [65636.820143] Call Trace:
  [65636.820182]  [] schedule+0x35/0x80
  [65636.820360]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820395]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820409]  [] start_transaction+0x2c5/0x4b0 [btrfs]
  [65636.820434]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
  [65636.820452]  [] btrfs_drop_snapshot+0x7f/0x830 [btrfs]
  [65636.820454]  [] ? __schedule+0x3b6/0xa30
  [65636.820467]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
  [65636.820480]  [] cleaner_kthread+0xcf/0x220 [btrfs]
  [65636.820493]  [] ? check_leaf+0x360/0x360 [btrfs]
  [65636.820497]  [] kthread+0xd8/0xf0
  [65636.820499]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820505]  [] ret_from_fork+0x3f/0x70
  [65636.820507]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds.
  [65636.820551]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820559] kworker/u4:1D 880008433c48 0  7760  2 
0x
  [65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820581]  880008433c48 0040 8800b9d98c80 
8801b51a9900
  [65636.820582]  880008434000 8801851941f0 880185194000 
8801851941f0
  [65636.820584]  0001 880008433c60 81829ec5 
8801b7fc4000
  [65636.820586] Call Trace:
  [65636.820588]  [] schedule+0x35/0x80
  [65636.820602]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820604]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820620]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820650]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
  [65636.820667]  [] btrfs_finish_ordered_io+0x435/0x650 
[btrfs]
  [65636.820692]  [] finish_ordered_fn+0x15/0x20 [btrfs]
  [65636.820718]  [] btrfs_scrubparity_helper+0xca/0x2f0 
[btrfs]
  [65636.820723]  [] ? try_to_wake_up+0x47/0x3b0
  [65636.820741]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
  [65636.820753]  [] process_one_work+0x165/0x480
  [65636.820755]  [] worker_thread+0x4b/0x4c0
  [65636.820757]  [] ? process_one_work+0x480/0x480
  [65636.820758]  [] kthread+0xd8/0xf0
  [65636.820760]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820761]  [] ret_from_fork+0x3f/0x70
  [65636.820763]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820770] INFO: task kworker/u4:2:7814 blocked for more than 120 seconds.
  [65636.820771]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820772] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820773] kworker/u4:2D 880102027c48 0  7814  2 
0x
  [65636.820848] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820850]  880102027c48 0040 8801b51ae400 
8801b51a8c80
  [65636.820852]  880102028000 8801851941f0 880185194000 
8801851941f0
  [65636.820853]  0001 880102027c60 81829ec5 
8801b7fc4000
  [65636.820855] Call Trace:
  [65636.820857]  [] schedule+0x35/0x80
  [65636.820877]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820879]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820893]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820908]  [] 

[Kernel-packages] [Bug 1614859] Re: zfsutils-linux fails to configure "directory not empty"

[Richard Laager]

I've marked it as Invalid, as there's nothing to be done at this point.
But, there may still be some bug here. After all, how did this happen in
the first place? That may have been user error, or it may not have. But,
at this point, it likely doesn't matter. If we see more, similar
reports, or if something is reproducible, then we can go from there.

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

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

Title:
  zfsutils-linux fails to configure "directory not empty"

Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12

  
  After apt-get upgrade, zfsutils-linux fails to configure. 

  # systemctl status zfs-mount.service 
  Aug 19 09:39:56 MediaServer systemd[1]: Starting Mount ZFS filesystems...
  Aug 19 09:39:56 MediaServer zfs[27456]: cannot mount '/storage/media': 
directory is not empty
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 19 09:39:56 MediaServer systemd[1]: Failed to start Mount ZFS filesystems.
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Unit entered 
failed state.
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.

  Unmounting zpool entirely shows the folder is indeed empty.

  Running apt-get -f upgrade with the pool entirely unmounted returns
  the same result. (The zpool is successfully mounted though, including
  the supposed failed directory.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 09:11:44 2016
  InstallationDate: Installed on 2013-11-08 (1014 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to xenial on 2016-08-16 (3 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']
  mtime.conffile..etc.default.zfs: 2016-04-28T16:29:55.338840

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614859/+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 1612718] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_09-22-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1614859] Re: zfsutils-linux fails to configure "directory not empty"

[benzo8]

And now I feel foolish. Yup, this worked. Thank your for your time. This
bug can be marked "Not a bug, just an idiot"!

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

Title:
  zfsutils-linux fails to configure "directory not empty"

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12

  
  After apt-get upgrade, zfsutils-linux fails to configure. 

  # systemctl status zfs-mount.service 
  Aug 19 09:39:56 MediaServer systemd[1]: Starting Mount ZFS filesystems...
  Aug 19 09:39:56 MediaServer zfs[27456]: cannot mount '/storage/media': 
directory is not empty
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 19 09:39:56 MediaServer systemd[1]: Failed to start Mount ZFS filesystems.
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Unit entered 
failed state.
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.

  Unmounting zpool entirely shows the folder is indeed empty.

  Running apt-get -f upgrade with the pool entirely unmounted returns
  the same result. (The zpool is successfully mounted though, including
  the supposed failed directory.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 09:11:44 2016
  InstallationDate: Installed on 2013-11-08 (1014 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to xenial on 2016-08-16 (3 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']
  mtime.conffile..etc.default.zfs: 2016-04-28T16:29:55.338840

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614859/+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 1614887] [NEW] Lage samba file transfers block btrfs to hung task

[S. W.]

Public bug reported:

this bug occurs when user transfer big files ~1gb to the samba server on
xenial/wily

on wily this problem was NOT showing with samba 4.2 (i guess) until
samba was also upgraded to 4.3.

the samba runs on a KVM VM

samba version: 4.3.9+dfsg-0ubuntu0.16.04.


[   30.171211] zram: Added device: zram0
[   30.356301] zram0: detected capacity change from 0 to 1518252032
[   30.668855] Adding 1482664k swap on /dev/zram0.  Priority:5 extents:1 
across:1482664k SSFS
[   35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or 
missing monitors config: c9e3, 0
[   45.008364] Non-volatile memory driver v1.3
[65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds.
[65636.820128]   Not tainted 4.4.0-36-generic #55-Ubuntu
[65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[65636.820131] btrfs-cleaner   D 88005ae93ce8 0   631  2 0x
[65636.820137]  88005ae93ce8 8800bbb86400 8801b0dc3e80 
8801b0dc2580
[65636.820139]  88005ae94000 8801851971f0 880185197000 
8801851971f0
[65636.820141]  0001 88005ae93d00 81829ec5 
8801b7fc4000
[65636.820143] Call Trace:
[65636.820182]  [] schedule+0x35/0x80
[65636.820360]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
[65636.820395]  [] ? wake_atomic_t_function+0x60/0x60
[65636.820409]  [] start_transaction+0x2c5/0x4b0 [btrfs]
[65636.820434]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
[65636.820452]  [] btrfs_drop_snapshot+0x7f/0x830 [btrfs]
[65636.820454]  [] ? __schedule+0x3b6/0xa30
[65636.820467]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
[65636.820480]  [] cleaner_kthread+0xcf/0x220 [btrfs]
[65636.820493]  [] ? check_leaf+0x360/0x360 [btrfs]
[65636.820497]  [] kthread+0xd8/0xf0
[65636.820499]  [] ? kthread_create_on_node+0x1e0/0x1e0
[65636.820505]  [] ret_from_fork+0x3f/0x70
[65636.820507]  [] ? kthread_create_on_node+0x1e0/0x1e0
[65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds.
[65636.820551]   Not tainted 4.4.0-36-generic #55-Ubuntu
[65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[65636.820559] kworker/u4:1D 880008433c48 0  7760  2 0x
[65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
[65636.820581]  880008433c48 0040 8800b9d98c80 
8801b51a9900
[65636.820582]  880008434000 8801851941f0 880185194000 
8801851941f0
[65636.820584]  0001 880008433c60 81829ec5 
8801b7fc4000
[65636.820586] Call Trace:
[65636.820588]  [] schedule+0x35/0x80
[65636.820602]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
[65636.820604]  [] ? wake_atomic_t_function+0x60/0x60
[65636.820620]  [] start_transaction+0x275/0x4b0 [btrfs]
[65636.820650]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
[65636.820667]  [] btrfs_finish_ordered_io+0x435/0x650 [btrfs]
[65636.820692]  [] finish_ordered_fn+0x15/0x20 [btrfs]
[65636.820718]  [] btrfs_scrubparity_helper+0xca/0x2f0 [btrfs]
[65636.820723]  [] ? try_to_wake_up+0x47/0x3b0
[65636.820741]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
[65636.820753]  [] process_one_work+0x165/0x480
[65636.820755]  [] worker_thread+0x4b/0x4c0
[65636.820757]  [] ? process_one_work+0x480/0x480
[65636.820758]  [] kthread+0xd8/0xf0
[65636.820760]  [] ? kthread_create_on_node+0x1e0/0x1e0
[65636.820761]  [] ret_from_fork+0x3f/0x70
[65636.820763]  [] ? kthread_create_on_node+0x1e0/0x1e0
[65636.820770] INFO: task kworker/u4:2:7814 blocked for more than 120 seconds.
[65636.820771]   Not tainted 4.4.0-36-generic #55-Ubuntu
[65636.820772] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[65636.820773] kworker/u4:2D 880102027c48 0  7814  2 0x
[65636.820848] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
[65636.820850]  880102027c48 0040 8801b51ae400 
8801b51a8c80
[65636.820852]  880102028000 8801851941f0 880185194000 
8801851941f0
[65636.820853]  0001 880102027c60 81829ec5 
8801b7fc4000
[65636.820855] Call Trace:
[65636.820857]  [] schedule+0x35/0x80
[65636.820877]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
[65636.820879]  [] ? wake_atomic_t_function+0x60/0x60
[65636.820893]  [] start_transaction+0x275/0x4b0 [btrfs]
[65636.820908]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
[65636.820922]  [] btrfs_finish_ordered_io+0x435/0x650 [btrfs]
[65636.820934]  [] ? bio_free+0x4e/0x60
[65636.820936]  [] ? bio_put+0x23/0x30
[65636.820950]  [] finish_ordered_fn+0x15/0x20 [btrfs]
[65636.820964]  [] btrfs_scrubparity_helper+0xca/0x2f0 [btrfs]
[65636.820966]  [] ? try_to_wake_up+0x47/0x3b0
[65636.820999]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
[65636.821002]  [] process_one_work+0x165/0x480
[65636.821003]  [] worker_thread+0x4b/0x4c0
[65636.821005]  [] ? 

[Kernel-packages] [Bug 1614859] Re: zfsutils-linux fails to configure "directory not empty"

[Richard Laager]

It's not mounted correctly, though. Note that, in the mount output,
there is no "storage/media on /storage/media".

Do this:
sudo zfs umount storage/media/anime
sudo zfs umount storage/media/comedy
sudo zfs umount storage/media/comics
sudo zfs umount storage/media/documentaries
sudo zfs umount storage/media/ebooks
sudo zfs umount storage/media/movies
sudo zfs umount storage/media/mp3
sudo zfs umount storage/media/musicfilms
sudo zfs umount storage/media/spoken-word

This will leave storage mounted at /storage. Then, `ls /storage/media`
and you'll see it is NOT empty, but has (hopefully empty) directories
for those mountpoints. Delete them:

sudo rmdir /storage/media/anime
sudo rmdir /storage/media/comedy
sudo rmdir /storage/media/comics
sudo rmdir /storage/media/documentaries
sudo rmdir /storage/media/ebooks
sudo rmdir /storage/media/movies
sudo rmdir /storage/media/mp3
sudo rmdir /storage/media/musicfilms
sudo rmdir /storage/media/spoken-word

At that point, /storage/media should be empty. Now, mount storage/media:
sudo zfs mount storage/media

Assuming that all works, mount the remainder of the filesystems again:
sudo zfs mount -a

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

Title:
  zfsutils-linux fails to configure "directory not empty"

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12

  
  After apt-get upgrade, zfsutils-linux fails to configure. 

  # systemctl status zfs-mount.service 
  Aug 19 09:39:56 MediaServer systemd[1]: Starting Mount ZFS filesystems...
  Aug 19 09:39:56 MediaServer zfs[27456]: cannot mount '/storage/media': 
directory is not empty
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 19 09:39:56 MediaServer systemd[1]: Failed to start Mount ZFS filesystems.
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Unit entered 
failed state.
  Aug 19 09:39:56 MediaServer systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.

  Unmounting zpool entirely shows the folder is indeed empty.

  Running apt-get -f upgrade with the pool entirely unmounted returns
  the same result. (The zpool is successfully mounted though, including
  the supposed failed directory.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 09:11:44 2016
  InstallationDate: Installed on 2013-11-08 (1014 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to xenial on 2016-08-16 (3 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']
  mtime.conffile..etc.default.zfs: 2016-04-28T16:29:55.338840

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614859/+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 1612718] onibi (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_08-52-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1612718] onza (amd64) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_08-52-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1612564] dwalin (amd64) - tests ran: 65, failed: 1

[Brad Figg]

tests ran:  65, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/dwalin__3.19.0-68.76~14.04.1__2016-08-19_08-13-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-68.76~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612564/+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 1614791] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1614791

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  stress-ng freezes system

Status in linux package in Ubuntu:
  Incomplete
Status in stress-ng package in Ubuntu:
  New

Bug description:
  While running "stress-ng --aggressive --verify --timeout 2860 --log-
  file stress-ng-brk.log -v --brk 0", the system would freeze within an
  hour of running the test.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: stress-ng 0.05.23-1ubuntu2
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  Date: Fri Aug 19 01:04:30 2016
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcLoadAvg: 0.00 0.00 0.00 1/1200 10125
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 7809 00:14:652 0 EOF
   2: FLOCK  ADVISORY  WRITE 7797 00:14:646 0 EOF
   3: POSIX  ADVISORY  WRITE 7799 00:14:656 0 EOF
   4: POSIX  ADVISORY  WRITE 8810 00:14:670 0 EOF
   5: POSIX  ADVISORY  WRITE 4914 00:14:419 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-34-generic (buildd@bos01-ppc64el-022) (gcc 
version 5.3.1 20160413 (User Name/IBM 5.3.1-14ubuntu2.1) ) #53-User Name SMP 
Wed Jul 27 16:04:07 UTC 2016
  SourcePackage: stress-ng
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614791/+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 1599379] Re: Baytrail-I got black screen with HDMI output

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Baytrail-I got black screen with HDMI output

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  Although the commit fff7660 fixes the issue, it still misses to probe
  HDMI port in some circumstance, therefore there's another commit
  (already merged):

  commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
  Author: Ville Syrjälä 
  CommitDate: Fri Jun 10 10:40:54 2016 +0300

  drm/i915: Check VBT for port presence in addition to the strap on
  VLV/CHV

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599379/+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 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Huang YangWen]

Thank you very much! Currently the system works normally with the raid
devices loaded.

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bblab  6762 

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[Konrad Zapałowicz]

For you to know a fix for in-car Bluetooth that addresses the pairing
problems when pairing is initiated by the car will be released in OTA13

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Stefan Bader]

About your question about maximum RAID size: I cannot answer that. There
possibly are different limits on what dmraid can construct via device-
mapper (those are likely higher than 4TB). But then there might be
limits that the meta-data which the BIOS uses impose. And I have no clue
there.

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Stefan Bader]

** Attachment added: 
"libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723896/+files/libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Stefan Bader]

Those packages are compiled against 14.04 user-space and should need no
update for libdevmapper.

** Attachment added: "dmraid_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723895/+files/dmraid_1.0.0.rc16-4.2ubuntu4~14.04.1_amd64.deb

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk 

[Kernel-packages] [Bug 1614513] Re: System freezes when undocking laptop

[Luke Murray]

Upgrading to 4.8.0-rc2 kernel fixes this problem.

** Tags added: kernel-fixed-upstream

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

Title:
  System freezes when undocking laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Lenovo Thinkpad X260 docking with a Lenovo 40A20090UK docking
  station. I have two monitors plugged into the back of the dock via its
  two separate displayport connectors. Booting the machine whilst docked
  causes the machine to freeze when it is undocked. Same for booting
  undocked, then docking.

  May relate to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604313

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luke   5384 F...m pulseaudio
   /dev/snd/controlC0:  luke   5384 F pulseaudio
  CurrentDesktop: i3
  Date: Thu Aug 18 13:33:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06d00448-ea78-46fb-8a32-6ec62b16a454
  InstallationDate: Installed on 2016-06-06 (73 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20F6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=6658071a-159f-4980-b5f8-a0b728bb8dc9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET48W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6CTO1WW
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614513/+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 1612718] onibi (amd64) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_08-23-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1612718] onza (i386) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onza__3.13.0-95.142~precise1__2016-08-19_07-51-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1614791] Re: stress-ng freezes system

[Colin Ian King]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  stress-ng freezes system

Status in linux package in Ubuntu:
  New
Status in stress-ng package in Ubuntu:
  New

Bug description:
  While running "stress-ng --aggressive --verify --timeout 2860 --log-
  file stress-ng-brk.log -v --brk 0", the system would freeze within an
  hour of running the test.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: stress-ng 0.05.23-1ubuntu2
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  Date: Fri Aug 19 01:04:30 2016
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcLoadAvg: 0.00 0.00 0.00 1/1200 10125
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 7809 00:14:652 0 EOF
   2: FLOCK  ADVISORY  WRITE 7797 00:14:646 0 EOF
   3: POSIX  ADVISORY  WRITE 7799 00:14:656 0 EOF
   4: POSIX  ADVISORY  WRITE 8810 00:14:670 0 EOF
   5: POSIX  ADVISORY  WRITE 4914 00:14:419 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-34-generic (buildd@bos01-ppc64el-022) (gcc 
version 5.3.1 20160413 (User Name/IBM 5.3.1-14ubuntu2.1) ) #53-User Name SMP 
Wed Jul 27 16:04:07 UTC 2016
  SourcePackage: stress-ng
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614791/+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 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Stefan Bader]

Oh, sorry, wait a second. I think I made a mistake and compiled the
package against 16.04 user-space.

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bblab 

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Huang YangWen]

It says my libdevmapper (2:1.02.77) is too old, it needs (2:1.02.97)
instead. So I should install the patch after I switched the kernel?

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS 

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bblab  6762 F pulseaudio
   /dev/snd/controlC0:  bblab  6762 F 

[Kernel-packages] [Bug 1614859] Re: zfsutils-linux fails to configure "directory not empty"

[benzo8]

Sure. As far as I can tell, everything *does* mount correctly. It's
almost as if is trying to be mounted twice, and the second one fails
because the first one succeeded.

% sudo zfs list
NAME
  USED  AVAIL  REFER  MOUNTPOINT
storage 
 28.5T  3.03T   202K  /storage
storage/backups 
 1.06T  3.03T  1.06T  /storage/backups
storage/containers  
 12.3G  3.03T   128K  /storage/containers
storage/containers/loganalyzer  
 5.69G  3.03T  1.97G  /var/lib/lxd/containers/loganalyzer.zfs
storage/containers/nzbhydra 
 6.59G  3.03T   986M  /var/lib/lxd/containers/nzbhydra.zfs
storage/deleted 
 2.30G  3.03T   128K  /storage/deleted
storage/deleted/images  
 2.30G  3.03T   128K  /storage/deleted/images
storage/deleted/images/5b1b191d59c79c3415d57e9578259dcdfc148f5141447c61ae9942d68e0532a0
   856M  3.03T   856M  none
storage/deleted/images/77bd6b7dd911233cc95213e6325fa68edbbfce73e55ea77eb66310b59382479b
   748M  3.03T   748M  none
storage/deleted/images/f4c4c60a6b752a381288ae72a1689a9da00f8e03b732c8d1b8a8fcd1a8890800
   750M  3.03T   746M  none
storage/images  
 1.59G  3.03T   128K  /storage/images
storage/images/295d53ae6db4b3b0df9565377cb48c62845ab3bee5a241a8effe50ccdfd8bf17 
  767M  3.03T   767M  
/var/lib/lxd/images/295d53ae6db4b3b0df9565377cb48c62845ab3bee5a241a8effe50ccdfd8bf17.zfs
storage/images/9b9de680184bc9951a4f6f771e40fc98284db21c94bd5384fe31f2434dfa9049 
  857M  3.03T   857M  
/var/lib/lxd/images/9b9de680184bc9951a4f6f771e40fc98284db21c94bd5384fe31f2434dfa9049.zfs
storage/media   
 11.5T  3.03T   256K  /storage/media
storage/media/anime 
  153G  3.03T   147G  /storage/media/anime
storage/media/comedy
 4.59G  3.03T  4.59G  /storage/media/comedy
storage/media/comics
 33.9G  3.03T  33.3G  /storage/media/comics
storage/media/documentaries 
 87.6G  3.03T  87.6G  /storage/media/documentaries
storage/media/ebooks
  491G  3.03T   464G  /storage/media/ebooks
storage/media/movies
 9.60T  3.03T  9.52T  /storage/media/movies
storage/media/mp3   
 1.09T  3.03T  1.04T  /storage/media/mp3
storage/media/musicfilms
  101G  3.03T   101G  /storage/media/musicfilms
storage/media/spoken-word   
 3.75G  3.03T  3.75G  /storage/media/spoken-word
storage/photos  
 34.8G  3.03T  34.8G  /storage/photos
storage/temp
  376G  3.03T   199G  /storage/temp
storage/tv  
 15.3T  3.03T  13.4T  /storage/tv
storage/varlibplex  
  192G  3.03T   192G  /var/lib/plexmediaserver

% sudo mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=4068704k,nr_inodes=1017176,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=817252k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on 

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Huang YangWen]

I'm only using Linux on this PC. But the migration process seems to
tired. Maybe I'll just stick to the dmraid if there's not major
problems.

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID 

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Huang YangWen]

So now I'll just have to install these two packages and switch to a
newer kernel to see if the fix works? Another question is that does
dmraid have maximum size limit of the raid devices (something like raid
1 up to 4TB)?

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 

[Kernel-packages] [Bug 1612718] onibi (i386) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142~precise1/onibi__3.13.0-95.142~precise1__2016-08-19_07-37-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-95.142~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612715
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612718/+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 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Stefan Bader]

** Attachment added: "libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4_amd64.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723890/+files/libdmraid1.0.0.rc16_1.0.0.rc16-4.2ubuntu4_amd64.deb

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition
  table


  The fakeRaid with Marvell chipset on my motherboard shows the
  following information with fdisk in Ubuntu 14.04.4.

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001: 
2000.3 GB, 2000315047936 bytes
  255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x3b9fee89

   Device Boot  
Start End  Blocks   Id  System
  /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1   
 2048  3906865151  1953431552   83  Linux

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1: 
2000.3 GB, 2000313909248 bytes
  255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ddf1_4b1b92914b1b92914b044b040001p1 
doesn't contain a valid partition table
  ---
  ApportVersion: 

[Kernel-packages] [Bug 1611277] Re: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

[Stefan Bader]

Sorry, I was distracted by other things. So I will be attaching a
proposed update to dmraid and some pre-built package to test. I just
cannot promise that change will be accepted.

About converting to mdadm: That would be an option that might be more
future proof but only if you do not want to use the RAIDed disks in
parallel with Windows. The drivers that come with the motherboard rely
on the BIOS signatures and I am not aware (I never had need, so I never
searched) of any generic RAID driver for Windows that would recognize
the DDF signatures that mdadm creates.

If you only will be using Linux it is a different story. Then moving to
mdadm (you can then use even the normal superblock format, no strict
need for DDF) would have the additional benefit of being able to replace
the motherboard or move the disks to a different computer and have the
RAID still working. But of course its a tedious task: you need some
place to backup all data, also better make sure the backup has no bits
corrupted (maybe rare but happened), erase the RAID signatures (if
possible, from the BIOS), either plug the disks to a different
controller or switch the current one into SATA/AHCI mode, set up the
mdamd RAID and finally copy the backup back (and possibly again check
for consistency). A lot of work...

** Patch added: "Proposed update for dmraid"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723888/+files/disable-removable-test.debdiff

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

Title:
  Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid

Status in dmraid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in dmraid source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created
  from Ubuntu 14.04. I've tried three ways but none of them work.

  1. Update 14.04.4 to 16.04.1
  2. Fresh install 16.04.1
  3. Update kernel to linux-images-4.4.0-34-generic only

  The result is that the mapper was seperated into /dev/sdb and /dev/sdc
  and cannot be rebuild with dmraid (said no raid disk) or mdadm (said
  no superblock).

  Something interesting is that when I reinstall Ubuntu 14.04.2 with my
  old CD, during the installation Ubuntu is able to recognize
  /dev/mapper/ But when I do a fresh install in Ubuntu 16.04 with
  the CD, I get /dev/sdb and /dev/sdc

  The motherboard I'm using is Gigabyte X79-UP4

  The fakeRaid with Marvell chipset on my motherboard shows the following 
information with fdisk in Ubuntu 16.04.1.
  /dev/sda is where the system is installed. It is a normal hard drive.
  /dev/sdb and /dev/sdc are using raid 1.

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x000b7321

 Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  499711  248832   83  Linux
  /dev/sda2  501758  1953523711   9765109775  Extended
  Partition 2 does not start on physical sector boundary.
  /dev/sda5  501760  1953523711   976510976   8e  Linux LVM

  Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdb doesn't contain a valid partition table

  Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
  255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/sdc doesn't contain a valid partition table

  Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes
  255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition
  table

  Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes
  255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disk identifier: 0x

  Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid