date:20180302

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067709/+files/CurrentDmesg.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1752946/+attachment/5067708/+files/CRDA.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067715/+files/ProcInterrupts.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067713/+files/ProcCpuinfoMinimal.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1752946/+attachment/5067711/+files/Lspci.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067717/+files/PulseList.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067712/+files/ProcCpuinfo.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067714/+files/ProcEnviron.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] Re: System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

apport information

** Tags added: apport-collected

** Description changed:

  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It looks
  like it works at first, than the "wait for IO load" in the system
  monitor applet rises to max and the system does no longer respond to
  input, only hard reboot brings it back to life.
  
  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to -36
  the error is back.
  
  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special
  
  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40
  
  Desktop is Mate
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  sunny  1547 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
+ InstallationDate: Installed on 2015-11-19 (834 days ago)
+ InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp2s0no wireless extensions.
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
+  Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
+  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-32-generic N/A
+  linux-backports-modules-4.13.0-32-generic  N/A
+  linux-firmware 1.169.3
+ RfKill:
+  
+ Tags:  artful
+ Uname: Linux 4.13.0-32-generic i686
+ UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/07/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P2.00
+ dmi.board.name: D1800B-ITX
+ 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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.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.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067707/+files/AlsaInfo.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" -

[Kernel-packages] [Bug 1752946] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1752946/+attachment/5067718/+files/UdevDb.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067710/+files/JournalErrors.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067716/+files/ProcModules.txt

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1752946] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1752946/+attachment/5067719/+files/WifiSyslog.txt

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

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1547 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=22925ab1-8a2f-4f13-a372-0a961da45990
  InstallationDate: Installed on 2015-11-19 (834 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 003: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=f377d365-a2b2-4d29-b4c6-60ea74207e8f ro processor.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-23 (130 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: D1800B-ITX
  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.00:bd11/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnD1800B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752946/+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 1749040] Re: KPTI support for arm64 systems

All failures expected.

** Attachment added: "Gigabyte R120 (ACPI mode ThunderX) results"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5067656/+files/r120.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/1749040

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1741081] Re: zfs-import-cache.service fails on startup

2018-03-02 Thread Richard Laager

zfs-load-module.service seems to have a Requires on itself? That has to
be wrong.

Also, zfs-import-cache.service and zfs-import-scan.service need an After
=zfs-load-module.service. They're not getting one automatically because
of DefaultDependencies=no (which seems appropriate here, so leave that
alone). Scott, can you try this? I think it will fix your issue, since
zfs-mount.service already has After=zfs-load-cache.service and After
=zfs-load-scan.service.

The proposed package, with the changes above should fix the issue I'm
reporting.

However, LP #1672749 says, "Since zfsutils-linux/0.6.5.9-4, zfs module
is not automatically loaded on systems that no zpool exists, this avoids
tainting everyone's kernel who has the package installed but is not
using zfs." Is this still an important goal? If so, wasn't that lost
with ubuntu-load-zfs-unconditionally.patch? Or perhaps something is
keeping zfs-import-scan.service from being enabled by default?

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1749040] Re: KPTI support for arm64 systems

crb1s results - all expected failures except disk/disk_stress_ng_dm-1
which is what was running when the panic mentioned in comment #39
occurred.

** Attachment added: "results from thunderx crb1s"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5067655/+files/crb1s.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/1749040

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1748565] Re: [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-03-02 Thread Bulent Besim

My new Ubuntu 18.04 system also having this issue. I am using Wireless
Dual-Band Bluetooth(Intel 8260) PCI-E card from Asus(PCE-AC55BT). No
issues with the wifi, but the bluetooth conrol tools fail to discover
devices:

$ cat /proc/cpuinfo | grep -m1 'model name'
model name  : AMD Ryzen 7 1700 Eight-Core Processor

$ lsb_release -rc
Release:18.04
Codename:   bionic

$ uname -a
Linux soli 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

$ lspci -nnk|grep -i wire
17:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] 
(rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:0010]

$ lsusb 
 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  
  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ hciconfig -a  
 
hci0:   Type: Primary  Bus: USB 
  
BD Address: AC:ED:5C:AE:F0:96  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:1544 acl:0 sco:0 events:118 errors:0
TX bytes:6184 acl:0 sco:0 commands:117 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT  

$ dmesg | egrep 'Blue|Core' 
 
[0.00] ACPI: Core revision 20170831 
  
[0.039987] CPU: Processor Core ID: 0
[0.044000] smpboot: CPU0: AMD Ryzen 7 1700 Eight-Core Processor (family: 
0x17, model: 0x1, stepping: 0x1) 
[3.760967] ip_tables: (C) 2000-2006 Netfilter Core Team 
  
[4.017034] Bluetooth: Core ver 2.22 
  
[4.017050] Bluetooth: HCI device and connection manager initialized
[4.017053] Bluetooth: HCI socket layer initialized
[4.017054] Bluetooth: L2CAP socket layer initialized
[4.017058] Bluetooth: SCO socket layer initialized
[4.067680] Bluetooth: hci0: Firmware revision 0.0 build 176 week 45 2017
[4.563200] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[4.563201] Bluetooth: BNEP filters: protocol multicast
[4.563204] Bluetooth: BNEP socket layer initialized
[6.249296] Bluetooth: RFCOMM TTY layer initialized
[6.249299] Bluetooth: RFCOMM socket layer initialized
[6.249302] Bluetooth: RFCOMM ver 1.11
[   25.321876] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1716.408150] Bluetooth: hci0: last event is not cmd complete (0x0f

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

Title:
  [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1753010] Missing required logs.

2018-03-02 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1753010

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

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to
  post this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753010/+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 1753010] [NEW] after recent updates playing youtube videos in firefox causes sometimes freezing of the system

2018-03-02 Thread Kamil

Public bug reported:

After recent updates that fixed the bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
computer the following different bug has appeared. Playing Youtube music
videos (static picture + music, length 40-70 minutes) in Firefox (as
background for other activities on computer) causes sometimes (rather
often, up to several times per day) freezing of the system. And only
restart through reset button can help.

Initially I though that it is related to different Javascript-related
tasks (manipulating with complex widgets in Chromium, running heavy gulp
tasks through yarn) but it looks they are not the reason (or at least
not the main reason). Because right now I have seen the problem when
keyboard/mouse was not touched at all.

That's why I think this information is rather enough; and I decided to
post this bug.

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

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

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to
  post this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753010/+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 1753010] Re: after recent updates playing youtube videos in firefox causes sometimes freezing of the system

2018-03-02 Thread Kamil

Without running Youtube and js-related tasks it is possible to use the
system all day. But with Youtube and js tasks freezing occurs every 1-3
hrs.

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

Title:
  after recent updates playing youtube videos in firefox causes
  sometimes freezing of the system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After recent updates that fixed the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675 on my
  computer the following different bug has appeared. Playing Youtube
  music videos (static picture + music, length 40-70 minutes) in Firefox
  (as background for other activities on computer) causes sometimes
  (rather often, up to several times per day) freezing of the system.
  And only restart through reset button can help.

  Initially I though that it is related to different Javascript-related
  tasks (manipulating with complex widgets in Chromium, running heavy
  gulp tasks through yarn) but it looks they are not the reason (or at
  least not the main reason). Because right now I have seen the problem
  when keyboard/mouse was not touched at all.

  That's why I think this information is rather enough; and I decided to
  post this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753010/+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 1665211] Re: Upgrade Redpine RS9113 driver to support AP mode

2018-03-02 Thread markus5

It does not seem to be working in 4.4.0-112, either.
I'm losing sleep, too.

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

Title:
  Upgrade Redpine RS9113 driver to support AP mode

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:
  Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel which supports Host AP 
mode available on Dell IoT gateways. This version also fixes connection drop 
issues with multiple AP's/ mobile phone hotspots.
  Release version: 0.9.8.3.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact
  is also restricted to { SDIO_DEVICE(0x041B, 0x9330) } chipsets.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1665211/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-03-02 Thread Leonardo Müller

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

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752772/+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 1662003] Re: /sbin/crda failed with exit code 249

2018-03-02 Thread Jérôme

** Tags removed: 1386
** Tags added: i386

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

Title:
  /sbin/crda failed with exit code 249

Status in crda package in Ubuntu:
  Confirmed

Bug description:
  /var/log/syslog tells :
  ---
  kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
  systemd-udevd:  Process '/sbin/crda' failed with exit code 249.
  kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig 
ASPM ClockPM Segments MSI]
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: crda 3.13-1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  5 20:18:42 2017
  InstallationDate: Installed on 2017-02-01 (3 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: crda
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+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 1752946] Missing required logs.

2018-03-02 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1752946

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

** Tags added: artful

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752946/+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 1716747] Re: linux 4.12 - high system load and mouse delays - pipe A vblank wait timed out

2018-03-02 Thread Jay Vosburgh

Joe,

The issue has returned on my X220 tablet; running 4.13-0.36-generic and
the fully updated 17.10 user space.

Every time it happens the laptop display freezes for about 10 or 15
seconds.  A concurrent ssh session is unaffected.

[94261.464884] pipe A vblank wait timed out
[94261.464948] [ cut here ]
[94261.465044] WARNING: CPU: 2 PID: 16697 at /build/linux-r9581B/linux-4.13.0/dr
ivers/gpu/drm/i915/intel_display.c:12848 intel_atomic_commit_tail+0xfa7/0xfb0 [i
915]
[94261.465046] Modules linked in: ccm rfcomm xt_CHECKSUM iptable_mangle ipt_MASQ
UERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 n
f_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_t
cpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_
filter bnep binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) sp
l(O) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irq
bypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel arc4 a
es_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq_mi
di snd_seq_midi_event snd_hda_codec_hdmi snd_rawmidi iwldvm mac80211 snd_hda_cod
ec_conexant snd_hda_codec_generic uvcvideo videobuf2_vmalloc videobuf2_memops vi
deobuf2_v4l2
[94261.465098]  input_leds thinkpad_acpi snd_seq snd_hda_intel serio_raw wmi_bmo
f videobuf2_core btusb btrtl btbcm iwlwifi videodev btintel joydev bluetooth nvr
am media snd_hda_codec snd_seq_device snd_hda_core ecdh_generic cfg80211 lpc_ich
 snd_hwdep snd_pcm shpchp snd_timer mei_me mei snd soundcore mac_hid nfsd parpor
t_pc ppdev auth_rpcgss nfs_acl lp lockd parport grace sunrpc ip_tables x_tables 
autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect wacom sy
simgblt ptp sdhci_pci fb_sys_fops ahci psmouse usbhid sdhci hid drm libahci pps_
core wmi video
[94261.465153] CPU: 2 PID: 16697 Comm: Xorg Tainted: P   O4.13.0-36-
generic #40-Ubuntu
[94261.465155] Hardware name: LENOVO 42992UU/42992UU, BIOS 8DET69WW (1.39 ) 07/1
8/2013
[94261.465157] task: 955d1d3845c0 task.stack: af29821bc000
[94261.465217] RIP: 0010:intel_atomic_commit_tail+0xfa7/0xfb0 [i915]
[94261.465219] RSP: 0018:af29821bf8a8 EFLAGS: 00010286
[94261.465221] RAX: 001c RBX:  RCX: 
[94261.465223] RDX:  RSI: 0002 RDI: 0246
[94261.465225] RBP: af29821bf960 R08: 001c R09: 6177206b6e616c62
[94261.465226] R10: af29821bf8a8 R11: 74756f2064656d69 R12: 003c6b37
[94261.465228] R13: 955d3fa08000 R14: 955d3fbb9000 R15: 0001
[94261.465231] FS:  7fa6fdfd0500() GS:955d5e28() knlGS:0
000
[94261.465233] CS:  0010 DS:  ES:  CR0: 80050033
[94261.465235] CR2: 55ccba6e9ba8 CR3: 000402762004 CR4: 000606e0

[94261.465237] Call Trace:
[94261.465250]  ? wait_woken+0x80/0x80
[94261.465303]  intel_atomic_commit+0x3d5/0x490 [i915]
[94261.465331]  ? drm_atomic_check_only+0x37e/0x540 [drm]
[94261.465352]  drm_atomic_commit+0x51/0x60 [drm]
[94261.465367]  restore_fbdev_mode+0x15e/0x270 [drm_kms_helper]
[94261.465379]  drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 
[drm_kms_helper]
[94261.465389]  drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
[94261.465447]  intel_fbdev_set_par+0x1a/0x70 [i915]
[94261.465451]  fb_set_var+0x19f/0x440
[94261.465456]  ? __find_get_block+0xb6/0x2b0
[94261.465460]  ? ext4_dirty_inode+0x48/0x70
[94261.465465]  ? __ext4_handle_dirty_metadata+0x87/0x1c0
[94261.465472]  fbcon_blank+0x2b7/0x3a0
[94261.465476]  ? find_get_entry+0x1e/0xd0
[94261.465483]  do_unblank_screen+0xba/0x1b0
[94261.465488]  vt_ioctl+0x4e1/0x11a0
[94261.465493]  ? __slab_free+0x14c/0x2d0
[94261.465497]  ? __slab_free+0x14c/0x2d0
[94261.465502]  tty_ioctl+0xf6/0x8b0
[94261.465507]  ? vga_arb_release+0xd6/0x130
[94261.465511]  ? security_file_free+0x44/0x60
[94261.465515]  ? dput.part.23+0xba/0x1e0
[94261.465521]  do_vfs_ioctl+0xa8/0x630
[94261.465527]  ? entry_SYSCALL_64_after_hwframe+0xe9/0x139
[94261.465530]  ? entry_SYSCALL_64_after_hwframe+0xe2/0x139
[94261.465534]  ? entry_SYSCALL_64_after_hwframe+0xdb/0x139
[94261.465537]  ? entry_SYSCALL_64_after_hwframe+0xd4/0x139
[94261.465541]  ? entry_SYSCALL_64_after_hwframe+0xcd/0x139
[94261.465545]  ? entry_SYSCALL_64_after_hwframe+0xc6/0x139
[94261.465548]  ? entry_SYSCALL_64_after_hwframe+0xbf/0x139
[94261.465552]  ? entry_SYSCALL_64_after_hwframe+0xb8/0x139
[94261.46]  ? entry_SYSCALL_64_after_hwframe+0xb1/0x139
[94261.465560]  SyS_ioctl+0x79/0x90
[94261.465563]  ? entry_SYSCALL_64_after_hwframe+0x72/0x139
[94261.465567]  entry_SYSCALL_64_fastpath+0x24/0xab
[94261.465570] RIP: 0033:0x7fa6fb442ef7
[94261.465572] RSP: 002b:7ffcc51286d8 EFLAGS: 3246 ORIG_RAX: 
0010
[94261.465575] RAX: ffda RBX: 000e RCX: 7fa6fb442ef7
[94261.465576] RDX:

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-03-02 Thread albertoiNET

I used a nvidia propietary driver, but also doesn't work. In this
askubuntu I'm tested multiples things, without success

https://askubuntu.com/questions/1010405/the-brightness-of-laptop-screen-
cannot-be-adjusted-with-either-the-buttons-or-th/1010420#1010420

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

Title:
  The brightness of the screen cannot be adjusted with either the
  buttons or the slider.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness is always at 100% and cannot be adjusted with either the FN
  brightness buttons or the Unity top bar slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  albertoinet   1199 F pulseaudio
   /dev/snd/controlC0:  albertoinet   1199 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 20:49:16 2018
  HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f
  InstallationDate: Installed on 2018-02-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. GT72VR 7RD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1785IMS.30E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1785
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.family: GT
  dmi.product.name: GT72VR 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751887/+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 1752946] Re: System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

2018-03-02 Thread Brian Murray

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

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

Title:
  System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lately one of my boxes reproducably freezes when I copy data from
  internal hard disk to an USB device (USB hard disk or USB key). It
  looks like it works at first, than the "wait for IO load" in the
  system monitor applet rises to max and the system does no longer
  respond to input, only hard reboot brings it back to life.

  When booting the previous kernel 4.13.0-32 all is fine. Do I boot to
  -36 the error is back.

  I append a lshw dump as text file.
  The hardware basically:
   ASRock Board D1800B-ITX
   CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
    4GB RAM
    otherwise nothing special

  System: Ubuntu 17.10
  Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
  Kernel in question: linux-image-4.13.0-36-generic:
    Installiert:   4.13.0-36.40

  Desktop is Mate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752946/+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 1752946] [NEW] System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)

You have been subscribed to a public bug:

Lately one of my boxes reproducably freezes when I copy data from
internal hard disk to an USB device (USB hard disk or USB key). It looks
like it works at first, than the "wait for IO load" in the system
monitor applet rises to max and the system does no longer respond to
input, only hard reboot brings it back to life.

When booting the previous kernel 4.13.0-32 all is fine. Do I boot to -36
the error is back.

I append a lshw dump as text file.
The hardware basically:
 ASRock Board D1800B-ITX
 CPU: Intel(R) Celeron(R) CPU  J1800  @ 2.41GHz
  4GB RAM
  otherwise nothing special

System: Ubuntu 17.10
Kernel (now): Linux Esel 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:18:49 
UTC 2018 i686 i686 i686 GNU/Linux
Kernel in question: linux-image-4.13.0-36-generic:
  Installiert:   4.13.0-36.40

Desktop is Mate

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


** Tags: bot-comment
-- 
System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)
https://bugs.launchpad.net/bugs/1752946
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1742675] Re: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all

2018-03-02 Thread Kamil

I'm author of this bug report.
The bug has been resolved by the recent upgrade.

BUT... during recent days the system freezed rather often and required restart 
to be usable again. It happened randomly in the following circumstances, for 
example:
a) manipulation with complex js widgets by mouse;
b) running heavy job in gulp through yarn;
c) and some other unrelated activities.

Question: is there a way to collect any diagnostics data to post
reasonable bug report for this system behavior that will be enough to
fix this new 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/1742675

Title:
  after upgrade to linux-image-extra-4.13.0-26-generic  the system does
  not start at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to linux-image-extra-4.13.0-26-generic  the system does not 
start at all.
  Only restart through Advanced Options with 
linux-image-extra-4.10.0-42-generic helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jan 11 15:20:26 2018
  InstallationDate: Installed on 2017-06-23 (201 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2017-06-24T18:05:02.372991

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+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 1510125] Re: occasionally loses external monitor

2018-03-02 Thread Roy

This is present for:
- GNOME/Wayland session
- Ubuntu 17.10
- 4.13.0-36-generic
ie. any Ubuntu any kernel

symptom:
tail --follow=name --retry /var/log/syslog
Mar  2 11:36:06 c89 kernel: [649937.206226] thunderbolt :07:00.0: resetting 
error on 0:c.
Mar  2 11:36:06 c89 kernel: [649937.206258] thunderbolt :07:00.0: 0:c: 
hotplug: scanning
Mar  2 11:36:06 c89 kernel: [649937.206261] thunderbolt :07:00.0: 0:c: 
hotplug: no switch found
Mar  2 11:36:07 c89 kernel: [649937.685613] thunderbolt :07:00.0: resetting 
error on 0:c.
Mar  2 11:36:07 c89 kernel: [649937.685645] thunderbolt :07:00.0: 0:c: got 
unplug event for disconnected port, ignoring

Present since:
- always, but was earlier hidden by more severe i915 bugs

Happens when:
- many windows, or when opening many such as when restoring a crashed Chromium 
or LibreOffice session
- 2 external monitors via DisplayPort

Affect hardware:
- Product Name: MacBookPro12,1
lspci -v -s 00:02.0  [21/21]
00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 09)
 (prog-if 00 [VGA controller])  
Subsystem: Apple Inc. Iris Graphics 6100
Flags: bus master, fast devsel, latency 0, IRQ 50   
Memory at c000 (64-bit, non-prefetchable) [size=16M]
Memory at b000 (64-bit, prefetchable) [size=256M]   
I/O ports at 3000 [size=64] 
[virtual] Expansion ROM at 000c [disabled] [size=128K]  
Capabilities:
Kernel driver in use: i915  
Kernel modules: i915

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

Title:
  occasionally loses external monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occasionally the screen will blank and all windows move from the
  external monitor to the laptop monitor.  Relatively immediately
  afterward both screens re-enable, but the windows don't move back to
  the external monitor.

  This usually appears to be triggered by a specific application, eg,
  "ScudCloud" (a slack client that embeds an HTML webkit view), or
  enabling the flash plugin in an existing firefox window.

  dmesg shows:
  [  174.404713] [ cut here ]
  [  174.404736] WARNING: CPU: 0 PID: 1699 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 
i915_gem_track_fb+0x129/0x140 [i915]()
  [  174.404738] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits))
  [  174.404739] Modules linked in:
  [  174.404741]  bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) asix usbnet mii xt_addrtype xt_conntrack ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs 
nls_iso8859_1 applesmc input_polldev uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media btusb btrtl btbcm 
btintel bluetooth snd_usb_audio snd_usbmidi_lib joydev input_leds bcm5974 
snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_cirrus kvm_intel snd_hda_codec_generic kvm snd_seq_midi 
snd_seq_midi_event brcmfmac snd_hda_intel brcmutil snd_hda_codec snd_hda_core 
cfg80211 snd_hwdep snd_rawmidi bdc_pci lpc_ich snd_pcm mei_me snd_seq mei 
snd_seq_device
  [  174.404776]  snd_timer thunderbolt snd sbs soundcore acpi_als kfifo_buf 
shpchp sbshc industrialio apple_gmux mac_hid apple_bl parport_pc ppdev lp 
parport autofs4 jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg 
dm_crypt hid_plantronics hid_microsoft hid_logitech_hidpp hid_generic 
hid_logitech_dj hid_apple usbhid hid crct10dif_pclmul crc32_pclmul i915 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
i2c_algo_bit uas cryptd drm_kms_helper usb_storage drm ahci libahci video
  [  174.404803] CPU: 0 PID: 1699 Comm: gnome-shell Tainted: G   OE   
4.2.0-16-generic #19-Ubuntu
  [  174.404804] Hardware name: Apple Inc. MacBookPro11,4/Mac-06F11FD93F0323C5, 
BIOS MBP114.88Z.0172.B04.1506051511 06/05/2015
  [  174.404806]   5f8a407a 8804613eba28 
817e8c09
  [  174.404808]   8804613eba80 8804613eba68 
8107b3c6
  [  174.404811]  880465a3 0001 88046756e640 
8804658558c0
  [  174.404813] Call Trace:
  [  174.404818]  [] dump_stack+0x45/0x57
  [  174.404823]  [] warn_slowpath_common+0x86/0xc0
  [  174.404825]  [] warn_slowpath_fmt+0x55/0x70
  [  174.404836]  [] i915_gem_track_fb+0x129/0x140 [i915]
  [  174.404852]  []

[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU

As bionic already ships a v4.15 kernel, this should be fixed in bionic.

Can you verify?

Cascardo.

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

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => 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/1747134

Title:
  [bug] [BDX]Ubuntu 16.04.3  with kernel
  "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64"  hang if set "Cores
  Enabled" to 2 for both CPU

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description:
  Customer report a Ubuntu kernel issue related to Intel BDX Core numbers 
setting
  Ubuntu 16.04.3  with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64"  
hang if set "Cores Enabled" to 2 for both CPU.

  We have reproduced this issue on 17.10 release.

  With latest kernel, this issue disappears.

  now we bisect this issue is fixed by commit 947134d9b00f
  (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages
  calculation”) which was merged in v4.15-rc4.

  But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code
  base or Linux upstream mainline kernel v4.13 code base, this issue
  still exists.

  Target Release: 16.04 / 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1747134/+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 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

This bug was fixed in the package kexec-tools - 1:2.0.16-1ubuntu1

---
kexec-tools (1:2.0.16-1ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- Default to not kexecing a kernel on boot in the automatically
  generated conffile
- Don't call db_stop from the postinst.
- Adjust INITCONFFILE to vmlinux if used
- Add maintainer script helper to handle removal of conffile
  /etc/default/grub.d/kexec-tools.cfg has been removed.
  Handle it properly
- Add Breaks: statement toward kdump-tools
   Starting with kdump-tools 1:1.5.9-6, this package takes
   over the addition of crashkernel= parameter which has
   been removed from kexec-tools.
   Make sure that it is upgraded accordingly.
  * New upstream release (LP: #1743529)

kexec-tools (1:2.0.16-1) unstable; urgency=medium

  * New upstream release (Closes: #890818)
  * Updated pointer to kexec-tools home page (Closes: #888565)
  * Updtaed russian translation (Thanks, Lev) (Closes: #883918)
  * Remove obsolete configuration file (Closes: #868100)

kexec-tools (1:2.0.15-1) unstable; urgency=medium

  * New upstream release (Closes: #876318, Closes: #854826)
  * Enable compressed kernel support for ARM64 - Manoj Iyer
(Closes: #854093)
  * Updated Portuguese translation (Closes: #857728)
  * Updated German translation (Closes: #857737)

 -- Thadeu Lima de Souza Cascardo   Fri, 23 Feb
2018 12:11:36 -0300

** Changed in: kexec-tools (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  Triaged
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in kexec-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in kexec-tools source package in Artful:
  New
Status in linux source package in Artful:
  New
Status in kexec-tools source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  
  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash 
kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  root@whip:~# kdump-config status
  current state   : ready to kdump

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048 
  [   85.731745] NUMA 
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv

[Kernel-packages] [Bug 1744638] Re: [Bug] [CNL] mei: LTR holds platform at Pkg C2, cannot enter deeper Pkg C states

Already merged and released as part of v4.15.1.

Can you verify?

Thanks.
Cascardo.

** Tags added: kernel-bug-break-fix

** Description changed:

  Description:
  Platform: CNL-Y8 LPDDR4 PI (merged rail) RVP with BIOS 108
  
  BIOS configuration: 
https://wiki.ith.intel.com/pages/viewpage.action?pageId=865050787
  At least as far back as the 2017-10-25 Intel Next merge, platform will not go 
deeper than Pkg C2 when system is idle. Upon further debug, using the pmc_core 
driver to ignore LTR "6", or bit 6 of LTR_IGN, can allow the system can enter 
Pkg C8.
  
  If I'm not mistaken, according to CSpec bit 6 of LTR_IGN will ignore
  LTR_ME, which is in the MEI driver's domain.
  
  Reproduce by:
  
  Boot to text console with latest Intel Next kernel (2017-10-30 as of writing)
  Run turbostat
  See residency no deeper than Pkg C2
  Expected:
  At idle, system shows nonzero Pkg C8 residency, or deeper.
  
  Actual:
  At idle, system only shows nonzero Pkg C2 residency.
  
  Two work-arounds:
  
  echo 6 > /sys/kernel/debug/pmc_core/ltr_ignore
  Run powertop --auto-tune
  Criteria for closure:
  
  Idle system can enter Pkg C8 (or deeper) without having to explicitly
  "ignore" LTR 6 or otherwise have to manually enable runtime power
  management for MEI device(s).
  
  Commit ids:
  Upstream commit, planned to be merged into 4.16
  
  commit cc365dcf0e56271bedf3de95f88922abe248e951
  Author: Tomas Winkler 
  Date: Tue Jan 2 12:01:41 2018 +0200
  
  mei: me: allow runtime pm for platform with D0i3
  
  Target Kernel: 4.16
  Target Release: 18.04
+ 
+ break-fix: - cc365dcf0e56271bedf3de95f88922abe248e951

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [Bug] [CNL] mei: LTR holds platform at Pkg C2, cannot enter deeper Pkg
  C states

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description:
  Platform: CNL-Y8 LPDDR4 PI (merged rail) RVP with BIOS 108

  BIOS configuration: 
https://wiki.ith.intel.com/pages/viewpage.action?pageId=865050787
  At least as far back as the 2017-10-25 Intel Next merge, platform will not go 
deeper than Pkg C2 when system is idle. Upon further debug, using the pmc_core 
driver to ignore LTR "6", or bit 6 of LTR_IGN, can allow the system can enter 
Pkg C8.

  If I'm not mistaken, according to CSpec bit 6 of LTR_IGN will ignore
  LTR_ME, which is in the MEI driver's domain.

  Reproduce by:

  Boot to text console with latest Intel Next kernel (2017-10-30 as of writing)
  Run turbostat
  See residency no deeper than Pkg C2
  Expected:
  At idle, system shows nonzero Pkg C8 residency, or deeper.

  Actual:
  At idle, system only shows nonzero Pkg C2 residency.

  Two work-arounds:

  echo 6 > /sys/kernel/debug/pmc_core/ltr_ignore
  Run powertop --auto-tune
  Criteria for closure:

  Idle system can enter Pkg C8 (or deeper) without having to explicitly
  "ignore" LTR 6 or otherwise have to manually enable runtime power
  management for MEI device(s).

  Commit ids:
  Upstream commit, planned to be merged into 4.16

  commit cc365dcf0e56271bedf3de95f88922abe248e951
  Author: Tomas Winkler 
  Date: Tue Jan 2 12:01:41 2018 +0200

  mei: me: allow runtime pm for platform with D0i3

  Target Kernel: 4.16
  Target Release: 18.04

  break-fix: - cc365dcf0e56271bedf3de95f88922abe248e951

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1744638/+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 1741081] Re: zfs-import-cache.service fails on startup

2018-03-02 Thread Scott Emmons

OK, I retested with 0.7.5-1ubuntu3 and it's almost there but zfs-
mount.service still runs before the zfs kernel module is loaded:

$ systemctl --failed
  UNIT  LOAD   ACTIVE SUBDESCRIPTION
● zfs-mount.service loaded failed failed Mount ZFS filesystems

$ sudo journalctl -u zfs-mount.service
-- Logs begin at Fri 2018-03-02 19:08:55 UTC, end at Fri 2018-03-02 19:31:42 
UTC. --
Mar 02 19:09:00 ubuntu systemd[1]: Starting Mount ZFS filesystems...
Mar 02 19:09:00 ubuntu zfs[557]: The ZFS modules are not loaded.
Mar 02 19:09:00 ubuntu zfs[557]: Try running '/sbin/modprobe zfs' as root to 
load them.
Mar 02 19:09:00 ubuntu systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
Mar 02 19:09:00 ubuntu systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
Mar 02 19:09:00 ubuntu systemd[1]: Failed to start Mount ZFS filesystems.

But, by the time the system is fully up, something else has loaded the
zfs kernel module along the way:

$ lsmod|grep zfs
zfs  3407872  3

I do see that zfs-load-module.service has "WantedBy=zfs-mount.service",
but maybe zfs-mount.service needs "After=zfs-load-module.service" to
insure the dependency order? Looking at the dependency tree, zfs-
mount.service and zfs-import.target happen in parallel with the start of
zfs-load-module.service resulting in a race condition.

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1742561] Re: [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => 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/1742561

Title:
  [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID
  adds

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description:
  Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds

  c99d7832dcd7423ba352386107118b9bd8b83158 (drm branch commit id)
  (https://patchwork.freedesktop.org/patch/194410/)

  Target Release: 18.04

  Target Kernel: TBD (mainline)

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1742561/+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 1752165] Re: TB16 dock freezes X on hotplug when used with external displays

2018-03-02 Thread Georgi Boiko

Spent this evening attempting to get Bionic to work with no success. The
installer crashes halfway (#1752535) so the only way to test is was to
hotswap nouveau for nvidia while running in a textmode VT from a
LiveUSB. To this end, prime-select is not working on Bionic, showing
"unknown" on "query" and complaining about lack of alternatives on
"prime-select nvidia". Consequently, X won't start after unloading
nouveau and replacing it with nvidia.

Is there any alternative test I could run that does not require a
working Bionic installer?

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

Title:
TB16 dock freezes X on hotplug when used with external displays

Status in Dell Sputnik:
New
Status in linux package in Ubuntu:
Confirmed

Bug description:
Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux
REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released
12/15/2017. If it can be of any help, I can get this tested on an XPS
9560 (GTX 1050) too.

Steps to reproduce:

1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI
cables are used, but I doubt that it matters.
2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME.
3. Select nVidia GPU in PRIME settings, reboot if needed.
4. Either boot with the dock connected or connect it after booting into user
session.
5. Set up monitors if necessary. At this point everything should be working
fine.
6. Disconnect the dock, give it a moment to adjust to the new window layout
etc.
7. Re-connect the dock. Within a few seconds laptop screen should freeze and
external monitors should remain blank, as if not connected.
8. Disconnect the dock. Within a few seconds laptop screen should unfreeze.
There is a small chance that it won't if you repeat this procedure multiple
times.

Errors in dmesg indicate that i915 driver is somehow involved:

[ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF B idle bit
[ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF C idle bit

The kernel logs are flooded with these between steps 7 and 8 above.

This behaviour does not occur when Intel GPU is selected in PRIME
settings or when nouveau is used. However, nouveau performance leaves
a lot to be desired, particularly with 3D acceleration in Windows 10
VMs.

I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make
any difference.

Other reports that may be related:

https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a
-docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes-
hangs-the-whole-machine/ - same error messages

https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189
- "Connecting and disconnecting the TB16 sometimes freeze the laptop."

https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466
- "Hot-plugging the screen does not work."
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gboiko 2491 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c
InstallationDate: Installed on 2017-10-01 (149 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp.
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic
root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0
biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.170
Tags: xenial
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

[Kernel-packages] [Bug 1730829] Re: [Feature]Crystal Ridge:add support for the platform capabilities NFIT sub-table in ACPI 6.2A

All four apply cleanly and build fine for amd64 generic.

Cascardo.

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

Title:
  [Feature]Crystal Ridge:add support for the platform capabilities NFIT
  sub-table in ACPI 6.2A

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Description:

  Enable support for: "5.2.25.9 Platform Capabilities Structure" in ACPI 6.2A.
  This involves NFIT driver changes for the new table, and then detecting if 
the platform has cache flush on fail support. If it does, plumb that through as 
a region property so that we can pick the proper default to pass to the 
dax_write_cache() call in pmem_attach_disk().

  Target Kernel: 4.15
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730829/+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 1752310] Re: What is the zfs support policy wrt. LTS releases?

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  What is the zfs support policy wrt. LTS releases?

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  If we consider the zfs 0.x releases as being major (0.6, 0.7, 0.8), is
  the assumption correct that LTS releases will not receive a new major
  ZFS release ?

  To be as practical as possible: Bionic will be stuck at zfs 0.7.x,
  Xenial at zfs 0.6.x ?

  If my assumption is wrong, when would Xenial see zfs 0.7 ?

  Has a policy been defined ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1752310/+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 1752551] Re: zram smoke test failed on Trusty ppc64le

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  zram smoke test failed on Trusty ppc64le

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The zram smoke has failed with:
    modprobe: FATAL: Module zram not found.

  From its config, there is no zram related entry, not sure if this is intended:
    grep -i zram /boot/config-3.13.0-142-generic

  (returns nothing)

  If this is intended, we can disable this test on ppc64le.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-142-generic 3.13.0-142.191
  ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-142-generic ppc64le
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CurrentDmesg: [  890.069571] init: zram-config post-stop process (9543) 
terminated with status 1
  Date: Thu Mar  1 11:27:11 2018
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro 
console=hvc0
  ProcLoadAvg: 0.00 0.08 0.16 1/1059 10316
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 6459 00:11:43064 0 0
   2: FLOCK  ADVISORY  WRITE 2334 00:11:27831 0 EOF
   3: POSIX  ADVISORY  WRITE 2264 00:11:35027 0 EOF
   4: POSIX  ADVISORY  WRITE 2387 00:11:35925 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 
12:12:31 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-142-generic N/A
   linux-backports-modules-3.13.0-142-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  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/1752551/+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 1752941] Re: zfs - filesystem seems empty after package upgrade

2018-03-02 Thread Jonathan Patterson

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

** Description changed:

- unattended-upgrades upgraded zfs today to 0.6.5.6-0ubuntu19, and since a 
subsequent reboot, the zfs filesystem appears empty. I've verified that there 
was not a directory named after the zfs mount before the mount, and zfs shows 
there is something in the filesystem - see below, but when mounted, no files 
are visible.
- root@mahrez:/var/log/apt# zfs list -t all -o space
- NAME  AVAIL   USED  USEDSNAP  USEDDS  
USEDREFRESERV  USEDCHILD
- mahrez53.5T   332M  201K457K  
0   332M
- root@mahrez:/var/log/apt# df /mahrez
- Filesystem   1K-blocks  Used   Available Use% Mounted on
- mahrez 57443602688   512 57443602176   1% /mahrez
- There are no errors from zfs in the logs, no disk problems, and it has been 
scrubbed with no errors.
- I've been trying to revert to an older zfs version to test if the update is 
definitely the cause, but the packages don't seem to be available. I've booted 
into 3 older kernels to see if that helped, but no.
- The logs from the update are below. After the update, a user reported they 
were getting "operating not permitted" when trying to read their files on the 
fs. I verified this was the case, and rebooted to see if that would help, and 
after that, no files were listed at all. I've got 4 other machines running 
older zfs versions which are fine. I've stopped updates on them.
- Start-Date: 2018-03-02  11:05:42
- Commandline: /usr/bin/unattended-upgrade
- Upgrade: gnome-accessibility-themes:amd64 (3.18.0-2ubuntu1, 3.18.0-2ubuntu2), 
bamfdaemon:amd64 (0.5.3~bzr0+16.04.20160824-0ubuntu1, 
0.5.3~bzr0+16.04.20180209-0ubuntu1), libsnmp-base:amd64 (5.7.3+dfsg-1ubuntu4, 
5.7.3+dfsg-1ubuntu4.1), isc-dhcp-common:amd64 (4.3.3-5ubuntu12.7, 
4.3.3-5ubuntu12.9), zfs-zed:amd64 (0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), 
libdfu1:amd64 (0.7.0-0ubuntu4.3, 0.8.3-0ubuntu2), zfsutils-linux:amd64 
(0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), libbamf3-2:amd64 
(0.5.3~bzr0+16.04.20160824-0ubuntu1, 0.5.3~bzr0+16.04.20180209-0ubuntu1), 
libsnmp30:amd64 (5.7.3+dfsg-1ubuntu4, 5.7.3+dfsg-1ubuntu4.1), 
libzfs2linux:amd64 (0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), libfwupd1:amd64 
(0.7.0-0ubuntu4.3, 0.8.3-0ubuntu2), libzpool2linux:amd64 (0.6.5.6-0ubuntu18, 
0.6.5.6-0ubuntu19), fwupd:amd64 (0.7.0-0ubuntu4.3, 0.8.3-0ubuntu2), 
linux-firmware:amd64 (1.157.16, 1.157.17), libnvpair1linux:amd64 
(0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), libuutil1linux:amd64 
(0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), zfs-doc:amd64 (0.6.5.6-0ubuntu18, 
0.6.5.6-0ubuntu19), isc-dhcp-client:amd64 (4.3.3-5ubuntu12.7, 4.3.3-5ubuntu12.9)
+ qweqweqwe

** Summary changed:

- zfs - filesystem seems empty after package upgrade
+ whycantwedeleteabugwesubmitted

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

Title:
  whycantwedeleteabugwesubmitted

Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  qweqweqwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1752941/+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 1741081] Re: zfs-import-cache.service fails on startup

2018-03-02 Thread Scott Emmons

Great, thanks Colin! We will test this on bionic very soon and will
follow up to confirm.

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1686034] Re: [Feature] Thunderbolt: Integrate thunderbolt user space security level components

** Information type changed from Private to Public

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

Title:
  [Feature] Thunderbolt: Integrate thunderbolt user space security level
  components

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description:
  Support security levels for Thunderbolt. This feature allows users to approve 
devices before being able to use them.

  
  Target Kernel: 4.13

  Target Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1686034/+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 1742563] Re: [Feature] Mehlow:RAID mode PCI ID

** Changed in: linux (Ubuntu Bionic)
   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/1742563

Title:
  [Feature] Mehlow:RAID mode PCI ID

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description:
  RAIP PCI IDs 0xA356
  Dell has requested to upstream this device ID

  Target Release: 18.04

  Target kernel: 4.16

  break-fix: - f919dde0772a894c693a1eeabc77df69d6a9b937

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1742563/+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 1752941] [NEW] zfs - filesystem seems empty after package upgrade

2018-03-02 Thread Jonathan Patterson

Public bug reported:

unattended-upgrades upgraded zfs today to 0.6.5.6-0ubuntu19, and since a 
subsequent reboot, the zfs filesystem appears empty. I've verified that there 
was not a directory named after the zfs mount before the mount, and zfs shows 
there is something in the filesystem - see below, but when mounted, no files 
are visible.
root@mahrez:/var/log/apt# zfs list -t all -o space
NAME  AVAIL   USED  USEDSNAP  USEDDS  
USEDREFRESERV  USEDCHILD
mahrez53.5T   332M  201K457K
  0   332M
root@mahrez:/var/log/apt# df /mahrez
Filesystem   1K-blocks  Used   Available Use% Mounted on
mahrez 57443602688   512 57443602176   1% /mahrez
There are no errors from zfs in the logs, no disk problems, and it has been 
scrubbed with no errors.
I've been trying to revert to an older zfs version to test if the update is 
definitely the cause, but the packages don't seem to be available. I've booted 
into 3 older kernels to see if that helped, but no.
The logs from the update are below. After the update, a user reported they were 
getting "operating not permitted" when trying to read their files on the fs. I 
verified this was the case, and rebooted to see if that would help, and after 
that, no files were listed at all. I've got 4 other machines running older zfs 
versions which are fine. I've stopped updates on them.
Start-Date: 2018-03-02  11:05:42
Commandline: /usr/bin/unattended-upgrade
Upgrade: gnome-accessibility-themes:amd64 (3.18.0-2ubuntu1, 3.18.0-2ubuntu2), 
bamfdaemon:amd64 (0.5.3~bzr0+16.04.20160824-0ubuntu1, 
0.5.3~bzr0+16.04.20180209-0ubuntu1), libsnmp-base:amd64 (5.7.3+dfsg-1ubuntu4, 
5.7.3+dfsg-1ubuntu4.1), isc-dhcp-common:amd64 (4.3.3-5ubuntu12.7, 
4.3.3-5ubuntu12.9), zfs-zed:amd64 (0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), 
libdfu1:amd64 (0.7.0-0ubuntu4.3, 0.8.3-0ubuntu2), zfsutils-linux:amd64 
(0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), libbamf3-2:amd64 
(0.5.3~bzr0+16.04.20160824-0ubuntu1, 0.5.3~bzr0+16.04.20180209-0ubuntu1), 
libsnmp30:amd64 (5.7.3+dfsg-1ubuntu4, 5.7.3+dfsg-1ubuntu4.1), 
libzfs2linux:amd64 (0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), libfwupd1:amd64 
(0.7.0-0ubuntu4.3, 0.8.3-0ubuntu2), libzpool2linux:amd64 (0.6.5.6-0ubuntu18, 
0.6.5.6-0ubuntu19), fwupd:amd64 (0.7.0-0ubuntu4.3, 0.8.3-0ubuntu2), 
linux-firmware:amd64 (1.157.16, 1.157.17), libnvpair1linux:amd64 
(0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), libuutil1linux:amd64 
(0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), zfs-doc:amd64 (0.6.5.6-0ubuntu18, 
0.6.5.6-0ubuntu19), isc-dhcp-client:amd64 (4.3.3-5ubuntu12.7, 4.3.3-5ubuntu12.9)

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

** Summary changed:

- zfs
+ zfs - filesystem seems empty after package upgrade

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

Title:
  zfs - filesystem seems empty after package upgrade

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  unattended-upgrades upgraded zfs today to 0.6.5.6-0ubuntu19, and since a 
subsequent reboot, the zfs filesystem appears empty. I've verified that there 
was not a directory named after the zfs mount before the mount, and zfs shows 
there is something in the filesystem - see below, but when mounted, no files 
are visible.
  root@mahrez:/var/log/apt# zfs list -t all -o space
  NAME  AVAIL   USED  USEDSNAP  USEDDS  
USEDREFRESERV  USEDCHILD
  mahrez53.5T   332M  201K457K  
0   332M
  root@mahrez:/var/log/apt# df /mahrez
  Filesystem   1K-blocks  Used   Available Use% Mounted on
  mahrez 57443602688   512 57443602176   1% /mahrez
  There are no errors from zfs in the logs, no disk problems, and it has been 
scrubbed with no errors.
  I've been trying to revert to an older zfs version to test if the update is 
definitely the cause, but the packages don't seem to be available. I've booted 
into 3 older kernels to see if that helped, but no.
  The logs from the update are below. After the update, a user reported they 
were getting "operating not permitted" when trying to read their files on the 
fs. I verified this was the case, and rebooted to see if that would help, and 
after that, no files were listed at all. I've got 4 other machines running 
older zfs versions which are fine. I've stopped updates on them.
  Start-Date: 2018-03-02  11:05:42
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: gnome-accessibility-themes:amd64 (3.18.0-2ubuntu1, 3.18.0-2ubuntu2), 
bamfdaemon:amd64 (0.5.3~bzr0+16.04.20160824-0ubuntu1, 
0.5.3~bzr0+16.04.20180209-0ubuntu1), libsnmp-base:amd64 (5.7.3+dfsg-1ubuntu4, 
5.7.3+dfsg-1ubuntu4.1), isc-dhcp-common:amd64 (4.3.3-5ubuntu12.7, 
4.3.3-5ubuntu12.9), zfs-zed:amd64 (0.6.5.6-0ubuntu18, 0.6.5.6-0ubuntu19), 
libdfu1:amd64 (0.7.0-0ubuntu4.3,

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

Note: I've put a copy of the Artful fix in the following PPA for test
purposes, it can be installed using:

sudo add-apt-repository ppa:colin-king/zfs-artful-sru-1741081
sudo apt-get update
sudo apt-get dist-upgrade

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1751021] Re: retpoline abi files are empty on i386

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

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

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


** Tags added: verification-needed-trusty

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

Title:
  retpoline abi files are empty on i386

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

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751021/+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 1662003] Re: /sbin/crda failed with exit code 249

2018-03-02 Thread Christian Sirolli

** Tags added: 1386

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

Title:
  /sbin/crda failed with exit code 249

Status in crda package in Ubuntu:
  Confirmed

Bug description:
  /var/log/syslog tells :
  ---
  kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
  systemd-udevd:  Process '/sbin/crda' failed with exit code 249.
  kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig 
ASPM ClockPM Segments MSI]
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: crda 3.13-1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  5 20:18:42 2017
  InstallationDate: Installed on 2017-02-01 (3 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: crda
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+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 1750786] Re: stress-ng enosys stressor triggers a kernel BUG

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

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

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


** Tags added: verification-needed-trusty

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

Title:
  stress-ng enosys stressor triggers a kernel BUG

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

Bug description:
  We are seeing kernel BUGs when running the stress-ng enosys stresser
  on released trusty kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750786/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

probably related to bug #1749261

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1750937/+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 1752912] Re: bionic-proposed block to publish supported kernels in main

2018-03-02 Thread Dimitri John Ledkov

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

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

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

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

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

** Description changed:

  bionic-proposed block to publish supported kernels in main
  
  The following kernels should be available, installable, and in main, in
  bionic.
  
  linux-aws
  linux-azure
  linux-gke
  linux-hwe
  linux-kvm
+ 
+ Once all of these are published, with their metas, and are actually
+ installable, this bug can be closed to trigger migration into the
+ release pocket.

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

Title:
  bionic-proposed block to publish supported kernels in main

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-meta-aws package in Ubuntu:
  New
Status in linux-meta-azure package in Ubuntu:
  New
Status in linux-meta-gke package in Ubuntu:
  New
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-kvm package in Ubuntu:
  New

Bug description:
  bionic-proposed block to publish supported kernels in main

  The following kernels should be available, installable, and in main,
  in bionic.

  linux-aws
  linux-azure
  linux-gke
  linux-hwe
  linux-kvm

  Once all of these are published, with their metas, and are actually
  installable, this bug can be closed to trigger migration into the
  release pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1752912/+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 1742563] Re: [Feature] Mehlow:RAID mode PCI ID

** Information type changed from Private to Public

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

Title:
  [Feature] Mehlow:RAID mode PCI ID

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Description:
  RAIP PCI IDs 0xA356
  Dell has requested to upstream this device ID

  Target Release: 18.04

  Target kernel: 4.16

  break-fix: - f919dde0772a894c693a1eeabc77df69d6a9b937

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1742563/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

switching to "beta" version of gcc (Ubuntu 7.3.0-5ubuntu1~14.04.york0) 7.3.0
and rebuilding the kernel modules in question for 4.4.0-116 seemingly did the 
job.

is this really what you wanted from a good amount of the end users by
publishing those kernel?

** Summary changed:

- 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
+ 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by 
an insufficient compiler!

** Also affects: gcc
   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/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions

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

[Kernel-packages] [Bug 1752912] [NEW] bionic-proposed block to publish supported kernels in main

2018-03-02 Thread Dimitri John Ledkov

Public bug reported:

bionic-proposed block to publish supported kernels in main

The following kernels should be available, installable, and in main, in
bionic.

linux-aws
linux-azure
linux-gke
linux-hwe
linux-kvm

Once all of these are published, with their metas, and are actually
installable, this bug can be closed to trigger migration into the
release pocket.

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed

** Tags added: block-proposed

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

** Description changed:

  bionic-proposed block to publish supported kernels in main
  
  The following kernels should be available, installable, and in main, in
  bionic.
  
  linux-aws
+ linux-azure
  linux-kvm
  linux-gke

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

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

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

** Description changed:

  bionic-proposed block to publish supported kernels in main
  
  The following kernels should be available, installable, and in main, in
  bionic.
  
  linux-aws
  linux-azure
+ linux-gke
+ linux-hwe
  linux-kvm
- linux-gke

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

Title:
  bionic-proposed block to publish supported kernels in main

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-meta-aws package in Ubuntu:
  New
Status in linux-meta-azure package in Ubuntu:
  New
Status in linux-meta-gke package in Ubuntu:
  New
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-kvm package in Ubuntu:
  New

Bug description:
  bionic-proposed block to publish supported kernels in main

  The following kernels should be available, installable, and in main,
  in bionic.

  linux-aws
  linux-azure
  linux-gke
  linux-hwe
  linux-kvm

  Once all of these are published, with their metas, and are actually
  installable, this bug can be closed to trigger migration into the
  release pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1752912/+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 460925] Re: Kernel log message corruption due to incomplete /proc separation

2018-03-02 Thread denis steve

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Kernel log message corruption due to incomplete /proc separation

Status in linux package in Ubuntu:
  Fix Committed
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lxc

  When using LXC (linux containers), /proc/kmsg can be read in guest
  systems in their filtered view of /proc.  This special file should
  never be present in guest systems, and if created within a guest
  system, it should be effectively using /dev/null as it's source.  The
  effect of this bug ranges from simply annoying to potentially a
  security issue in that kernel messages are allowed to be destroyed and
  never fully logged on the host system, which could be used to cover
  evidence of some sort of attack on the system.

  I'm adding the kernel team as well, as this could be an issue inside
  the kernel.  I'm not sure if /proc filtration happens there or in the
  context of the lxc userland utilities.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/460925/+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 1741081] Re: zfs-import-cache.service fails on startup

** Description changed:

+ == SRU Request, Artful ==
+ 
+ Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
+ unconditionally.patch.
+ 
+ == Fix ==
+ 
+ Add a new zfs-load-module.service script that modprobes the ZFS module
+ and remove any hard coded module loading from zfs-import-cache.service &
+ zfs-import-scan.service and make these latter scripts require the new
+ zfs-load-module.service script.  Also remove the now defunct ubuntu-
+ load-zfs-unconditionally.patch as this will no longer be required.
+ 
+ == Testcase ==
+ 
+ On a clean VM, install with the fixed package, zfs should load
+ automatically.
+ 
+ == Regression potential ==
+ 
+ ZFS module may not load if the changes are broken. However, testing
+ proves this not to be the case.
+ 
+ 
+ 
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.
  
  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749
  
  This patch still exists in bionic, so I assume it will be similarly
  broken.
  
  If the goal of the patch is to load the module (and only that), I think
  it should create a third unit instead:
  
  zfs-load-module.service
   ^^ runs modprobe zfs
  
  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service
  
  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.
  
  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a `systemctl
  enable zfs-import-scan.service` to create the Wants symlinks. Looking at
  the zfsutils-linux.postinst, I see the correct boilerplate from
  dh_systemd, so I'm not sure why this wasn't already done. Can anyone
  confirm or deny whether zfs-import-scan.service is enabled out-of-the-
  box on their system?
  
  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or

[Kernel-packages] [Bug 1752695] Re: hisi_sas: Add disk LED support

** Description changed:

  [Impact]
  The disk LED is not supported on HiSilicon D05 systems
  
  [Test Case]
- View LED. (Not sure if this is a "online" LED or an "activity" LED yet)
+ Plug in disk, view LED.
  
  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

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

Title:
  hisi_sas: Add disk LED support

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  The disk LED is not supported on HiSilicon D05 systems

  [Test Case]
  Plug in disk, view LED.

  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752695/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

are you thinking of something like this?

https://launchpad.net/~jonathonf/+archive/ubuntu/gcc-7.3

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

Re: [Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

On Fri, Mar 2, 2018 at 4:48 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> If the bug in #39 is not related to kpti, can you spawn it into a
> separate LP bug and add a reproducer?

If it is shown to not be related to KPTI after I run those further
tests, that is the plan.

  -dann

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

are you sure it has arrived with _some_ gcc version already.

publications indicate its very experimental still and i can not see any
of the typical switches beeing honored by the gcc versions on my
machine. (and i was able to switch them forth and back using "update-
alternatives") needless to say that even after a few attempts a call to
"modinfo" does not at all report the "retpoline" option for the dkms
built nvidia kernel modules (using -384 on top of 4.4.0-116).

https://www.phoronix.com/scan.php?page=news_item=GCC-7-Gets-Retpolines
https://www.phoronix.com/scan.php?page=article=gcc8-mindirect-thunk=1

can you please be more specific with the compiler versions you are
using? please give exact versions. thank you.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

-- 
Mailing list:

[Kernel-packages] [Bug 1751724] Re: [Feature] Crystal Ridge-Restrict DAX to configurations with struct page

** Tags added: kernel

** Information type changed from Proprietary to Public

** Changed in: intel
   Importance: Undecided => Medium

** Changed in: intel
   Status: New => Triaged

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [Feature] Crystal Ridge-Restrict DAX to configurations with struct
  page

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Description:

  Several things break in surprising ways without the
  "memorypageallocation" property. It's better to assume that DAX is
  broken/unavailable in that configuration rather than try to explain
  all the corner cases where operations with a DAX mapping will fail.

  Disabling DAX support altogether if the pages are not allocated, DAX
  is mostly unusable without pages.

  Commit id list:
  24f3478d664b 569d0365f571 b4b5798cea8f

  Target Kernel: 4.16

  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1751724/+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 1741081] Re: zfs-import-cache.service fails on startup

This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu3

---
zfs-linux (0.7.5-1ubuntu3) bionic; urgency=medium

  * Add new module loading systemd service (LP: #1741081)
- loads zfs module unconditionally, and make the
  zfs-import-cache.service and zfs-import-scan.service services
  require this service.

 -- Colin Ian King   Fri, 2 Mar 2018 11:47:12
+

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1645969] Re: [Feature] Jefferson Peak(9560) WiFi/BT support

** Information type changed from Proprietary to Public

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

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

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

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

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: linux-firmware (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: 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/1645969

Title:
  [Feature] Jefferson Peak(9560) WiFi/BT support

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux-firmware source package in Bionic:
  Triaged

Bug description:
  Jefferson Peak (JfP):802.11abgn+acR2 MIMO 2x2
  Supports BT 5.0

  HW: Gemini Lake

  Target Release: 18.04

  Uptream schedule: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645969/+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 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic

2018-03-02 Thread Rod Smith

Sorry it's taken me so long to get back to you; the affected system is
my main work computer, so I can't just go rebooting it constantly, and
I've been busy with other things.

In any event, I'm afraid I haven't had much luck with these newer
kernels. The bottom line is that to get the VirtualBox modules
installed, I need the linux-headers-{version}-generic package, and for
these newer kernels, that package depends on libssl1.1 or greater; but
the 16.04 I'm using ships with libssl1.0, and I'm unwilling to upgrade
that package and risk far greater (and worse) problems or a return to
the old "dependency hell" issues of the 1990s.

If I get the chance, I may try installing bionic on a removable drive
and try to reproduce the problem in that way.

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

Title:
  System hang with Virtualbox & kernel 4.13.0-32-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Some (maybe all) kernels in the 4.13.0 series are hanging with
  Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a
  Virtualbox VM, the VM's window appears, clears to black, and then the
  mouse freezes. I do NOT see any BIOS/EFI information or boot loader in
  the VM; the hang occurs before those messages appear. (I've tried this
  with the VM set for both BIOS and EFI booting with no difference.) The
  host computer also stops responding to pings or anything else; the
  only solution seems to be to do a cold reset. I've tested this on a
  different computer running the same kernel and the latest Ubuntu 18.04
  alpha and had no problems there. Here's some data from the affected
  computer:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ cat /proc/version_signature 
  Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13

  $ dpkg -s virtualbox | grep Version
  Version: 5.0.40-dfsg-0ubuntu1.16.04.2

  This problem does NOT occur with earlier kernels, such as those in the 4.4.0 
series.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   2661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2014-05-02 (1382 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro 
root=/dev/mapper/hostname-trusty_crypt  quiet splash  
initrd=\initrd.img-4.13.0-32-generic
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago)
  UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare 
sbuild sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AFZ.015.161206.KS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP740U5M-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 740U5M
  dmi.product.version: P02AFZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+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 1751714] Re: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)

** Information type changed from Proprietary to Public

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

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

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

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: 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/1751714

Title:
  [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver
  needed)

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Description:
  a commit id missed in LP#1685729. [CNL] - New device IDs for CNL

  v4.16
  cb5fda413e1d

  @Canonical, please take it into 18.04.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1751714/+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 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-02 Thread Joseph Salisbury

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+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 1750568] Re: qeth: check not more than 16 SBALEs on the completion queue

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

Title:
  qeth: check not more than 16 SBALEs on the completion queue

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  af_iucv socket programs with HiperSockets as transport make use of the qdio 
completion queue.
  Running such an af_iucv socket program may result in a crash which can be 
seen 
  in bug comment #1.  This issue is fixed by mainline commit 903e48531e8b.

  Commit 903e48531e8b is in mailine as of 4.8-rc8, so it is only needed
  in Xenial.

  == Fix ==
  903e48531e8b ("qeth: check not more than 16 SBALEs on the completion queue")

  == Regression Potential ==
  Low. Limited to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750568/+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 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

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

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

Title:
[regression] Colour banding and artefacts appear system-wide on an
Asus Zenbook UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Fix Committed

Bug description:
=== SRU Justification ===
[Impact]
Color dithering not working correctly because the graphics driver
assumes the panel support 8bpc, but the panel only supports 6bpc.

[Test]
User reports the issue start appearing from v4.8-rc2.
The issue is fixed with the patch.

[Fix]
Add a quirk to tell DRM that this panel only supports 6bpc.

[Regression Potential]
Low. This fix matches a very specific panel.

=== Original Bug Report ===
- Ubuntu 18.04 (with updates as of 14 Feb 2018).
- Laptop: Asus Zenbook UX303
- CPU: Intel i5 4210U
- Graphics: Intel HD 4400

Problem description: Colour artefacts and banding in all apps.
Graphics, photos and videos display as though the colour range is
improperly configured.

See this photo of a 1080p video taken with a camera (poor quality, but
illustrates the issue): https://ubuntucommunity.s3-us-

east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

Look at the sky’s light colours. They display with smooth gradients on
Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
video with a smaller range of white colours. This is the most apparent
with either very dark or very light colours. Even on window titlebars
the banding is visible (displayed as lines with different shades of
grey/black).

Compared with a PrtSc shot of the same image:
https://i.imgur.com/VkOSCaQ.png

The artefacts are not present on PrtSc shots that are taken on Ubuntu
18.04 but viewed on a different system (16.04 and Windows).

Installing a previous kernel version fixes the issue completely. I
used UKUU Update Utility to install kernel 4.4 (the same that I use in
Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
18.04 everything displayed smoothly. So this indicates that the system
might be using a sub-optimal colour depth with the newer kernel?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified:
boot/vmlinuz-4.13.0-32-generic]
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ystein 1344 F pulseaudio
/dev/snd/controlC1: ystein 1344 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 11:25:43 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
InstallationDate: Installed on 2018-02-12 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:07dc Intel Corp.
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-generic N/A
linux-backports-modules-4.13.0-32-generic N/A
linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LA
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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX303LA
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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

** Also affects: zfs-linux (Ubuntu Bionic)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

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

** Changed in: zfs-linux (Ubuntu Artful)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Artful)
   Status: New => In Progress

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Artful:
  In Progress
Status in zfs-linux source package in Bionic:
  In Progress

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

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

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

Status in cloud-images:
  New
Status in edk2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in edk2 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based 
guests will fail to boot.

  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.

  [Regression Risk]
  I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.

  Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
  only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
  the Cavium ThunderX CRB - and I've regression tested on those systems.

  Patch 6 only adds new macro definitions.

  Patch 7 is restricted to devicetree code, except for a change to
  earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is
  passed on the cmdline (vs. earlycon=something), this function used to
  return 0 - but now it will return -ENODEV on non-devicetree systems,
  which is a subtle API change. However, according to kernel-
  parameters.txt (and the code itself), 'earlycon' by itself is only
  valid on devicetree systems. Just to be sure, I booted an x86 system
  up w/ 'earlycon' with and without this series, and observed no
  difference.

  Patch 8 adds the SPCR table parser, but no caller to it yet. It also
  modifies the same earlycon code as Patch 7 - here it avoids earlycon
  init in the case that the devicetree-specific 'earlycon' was passed.
  As mentioned in my analysis Patch 7, this codepath is only supported
  for devicetree systems, and has been regression tested on x86.

  Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will
  only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not
  to build this for other archs - but I checked the logs, and there's no
  spcr.o built on other archs. (Not that that should be a problem - they
  would just grow a bit of unused code).

  Patch 10 only touches arm64-specific code, adding the call to
  parse_spcr(), so risk is limited to arm64.

  Patch 11 adds a new match method to the ARM-specific pl011 console
  driver, so regression risk to other architectures is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1744754/+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 1752772] CurrentDmesg.txt

2018-03-02 Thread Leonardo Müller

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1752772/+attachment/5067030/+files/CurrentDmesg.txt

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1752772/+subscriptions

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

[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working

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

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Callers vmalloc_32() expect the page is not located in highmem.
  All users of vmalloc_32() have this issue, module saa7146 is one of
  them.

  [Test]
  saa7146 crashes at probing. The issue is fixed with the patch.

  [Fix]
  Add GFP_DMA32 to GFP_VMALLOC32 flag for 32bits systems.
  The patch is in stable trees, so only Artful needs this patch.

  [Regression Potential]
  Low. It's a crucial fix for 32bits systems.

  === Original Bug Report ===
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card 
Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. There is 
a kernel bug message while booting and no /dev/dvb device is created. Tried 
also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/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:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jan 10 00:42:24 2018
  HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456
  InstallationDate: Installed on 2016-02-13 (696 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 
(20151021)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force 
video=LVDS-1:d vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago)
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: AD2700-ITX
  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.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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/1742316/+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 1752695] Re: hisi_sas: Add disk LED support

** Changed in: linux (Ubuntu Artful)
   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/1752695

Title:
  hisi_sas: Add disk LED support

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  The disk LED is not supported on HiSilicon D05 systems

  [Test Case]
  View LED. (Not sure if this is a "online" LED or an "activity" LED yet)

  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752695/+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 1743856] Re: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode)

** Changed in: linux (Ubuntu Artful)
   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/1743856

Title:
  EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM
  sysfs entries with KNL SNC2/SNC4 mode)

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  The sb_edac needs this patch to enable EDAC to know of the existence of
  some DIMMs attached to channels while figuring out the size of the DIMMs
  and the cluster mode is SNC2 or SNC4.

  All the thread connected with this issue is described here
  https://www.spinics.net/lists/linux-edac/msg08170.html.

  Commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 is in mailine as of
  v4.15-rc1.

  == Fix ==
  commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36
  Author: Luis Felipe Sandoval Castro 
  Date:   Thu Sep 28 08:54:42 2017 -0500

  EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4
  mode

  == Regression Potential ==
  Low. Limited to EDAC checking dimm capacity.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Please backport the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=24281a2f4ca569d44e44e4cbc500cf08e7bb4c36
 to solve the sb_edac driver issue on Ubuntu 17.10.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1743856/+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 1750813] Re: qeth: fix L3 next-hop im xmit qeth hdr

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

Title:
  qeth: fix L3 next-hop im xmit qeth hdr

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  The current code accesses rtable->rt_gateway without checking that rtable
  is a valid address. The accidental access to a lowcore area results in a
  random next-hop address in the qeth_hdr.  rtable (or more precisely,
  skb_dst(skb)) can be NULL in rare cases (for instance together with AF_PACKET 
sockets).

  The solution is to add the missing NULL-ptr checks, which is done by
  commit ec2c6726322f.

  Commit ec2c6726322f is in mainline as of v4.13-rc5, so this fix is
  only needed in Xenial.

  == Fix ==
  ec2c6726322f ("s390/qeth: fix L3 next-hop in xmit qeth hdr")

  == Regression Potential ==
  Low.  Limited to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750813/+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 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics