[Kernel-packages] [Bug 1447909] Re: external mic not detected on machines with alc256 codec
This is before plug the headset Pin 0x12 (Internal Mic, ATAPI): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker, ATAPI): present = No Pin 0x18 (Pink Mic, Rear side): present = No Pin 0x19 (Not connected): present = No Pin 0x1a (Internal Mic): present = No Pin 0x1b (Not connected): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No This is after Pin 0x12 (Internal Mic, ATAPI): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker, ATAPI): present = No Pin 0x18 (Pink Mic, Rear side): present = No Pin 0x19 (Not connected): present = No Pin 0x1a (Internal Mic): present = No Pin 0x1b (Not connected): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No -- 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/1447909 Title: external mic not detected on machines with alc256 codec Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This bug is used for tracking, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1447909/+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 1629512] JournalErrors.txt
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752165/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752170/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752162/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752169/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752174/+files/WifiSyslog.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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752167/+files/Lsusb.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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752166/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752172/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752163/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752168/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752171/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752173/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752164/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: boby 2509 F pulseaudio
/dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
/dev/snd/controlC0: boby 2509 F pulseaudio
/dev/snd/controlC1: boby 2509 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
InstallationDate: Installed on 2016-05-31 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
RelatedPackageVersions:
linux-restricted-modules-4.4.0-38-generic N/A
linux-backports-modules-4.4.0-38-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SABERTOOTH X58
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] Re: HDD failed command: SET FEATURES error
apport information
** Tags added: apport-collected xenial
** Description changed:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
+ ---
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC2: boby 2509 F pulseaudio
+ /dev/snd/pcmC0D0p: boby 2509 F...m pulseaudio
+ /dev/snd/controlC0: boby 2509 F pulseaudio
+ /dev/snd/controlC1: boby 2509 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=6c36e74e-a467-4b4c-a6b0-edd20249754f
+ InstallationDate: Installed on 2016-05-31 (122 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB:
+
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=01f82bf5-45f1-4509-bdb3-44a51665830f ro quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
+ RelatedPackageVersions:
+ linux-restricted-modules-4.4.0-38-generic N/A
+ linux-backports-modules-4.4.0-38-generic N/A
+ linux-firmware1.157.3
+ RfKill:
+ 0: phy0: Wireless LAN
+ Soft blocked: no
+ Hard blocked: no
+ Tags: xenial
+ Uname: Linux 4.4.0-38-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/21/2010
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 0802
+ dmi.board.asset.tag: To Be Filled By O.E.M.
+ dmi.board.name: SABERTOOTH X58
+ dmi.board.vendor: ASUSTeK Computer INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd12/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752161/+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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
---
ApportVersion: 2.20.1-
[Kernel-packages] [Bug 1629512] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1629512
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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
Incomplete
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same
time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] Re: HDD failed command: SET FEATURES error
version.log attached.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+attachment/4752160/+files/version.log
--
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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
New
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same
time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1629512] [NEW] HDD failed command: SET FEATURES error
Public bug reported:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/1629512/+attachment/4752159/+files/lspci-vnvn.log
--
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/1629512
Title:
HDD failed command: SET FEATURES error
Status in linux package in Ubuntu:
New
Bug description:
When my computer boots, i get a screen with following errors
[9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.470880] ata6.00: irq_stat 0x4001
[9.470893] ata6.00: failed command: SET FEATURES
[9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
[9.470908] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.470942] ata6.00: status: { DRDY ERR }
[9.470954] ata6.00: error: { ABRT }
[9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[9.506944] ata5.00: irq_stat 0x4001
[9.506974] ata5.00: failed command: SET FEATURES
[9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
[9.507008] res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1
(device error)
[9.507083] ata5.00: status: { DRDY ERR }
[9.507110] ata5.00: error: { ABRT }
I stays there for like a minute before continue booting.
It started after i upgrade to Ubuntu 16.04, i had no such errors with
both HDD on Ubuntu 14.04
The HDDs are western digital WDC WD20EZRX-00D. Both purchased same
time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+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 1589776] Re: Radeon R7 not work in ubuntu xenial
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589776 Title: Radeon R7 not work in ubuntu xenial Status in linux package in Ubuntu: Expired Bug description: lspci: VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360] (rev ff) kernel:4.4.12-040412-generic #201606011712 ubuntu xenial. [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 1 test failed (scratch(0xC040)=0xCAFEDEAD) [ 18.514980] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 2 test failed (scratch(0xC040)=0xCAFEDEAD) [ 18.719097] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 3 test failed (scratch(0xC040)=0xCAFEDEAD) [ 18.923323] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 4 test failed (scratch(0xC040)=0xCAFEDEAD) [ 19.127705] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 5 test failed (scratch(0xC040)=0xCAFEDEAD) [ 19.331781] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 6 test failed (scratch(0xC040)=0xCAFEDEAD) [ 19.535642] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 7 test failed (scratch(0xC040)=0xCAFEDEAD) [ 19.739668] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 8 test failed (scratch(0xC040)=0xCAFEDEAD) [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 0 (-2). [ 26.229070] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed (-2). [ 26.229823] amdgpu :05:00.0: couldn't schedule ib [ 26.230498] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 26.231173] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! amdgpu :05:00.0: couldn't schedule ib [ 27.260411] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 27.260425] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 27.260428] amdgpu :05:00.0: couldn't schedule ib [ 27.260438] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 27.260447] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 27.260572] amdgpu :05:00.0: couldn't schedule ib [ 27.260583] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 27.260592] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.550867] amdgpu :05:00.0: couldn't schedule ib [ 28.550891] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.550908] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.550912] amdgpu :05:00.0: couldn't schedule ib [ 28.550926] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.550939] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.550942] amdgpu :05:00.0: couldn't schedule ib [ 28.550954] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.550967] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.550969] amdgpu :05:00.0: couldn't schedule ib [ 28.550980] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.550992] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.550995] amdgpu :05:00.0: couldn't schedule ib [ 28.551006] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.551018] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.551021] amdgpu :05:00.0: couldn't schedule ib [ 28.551032] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.551044] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.551046] amdgpu :05:00.0: couldn't schedule ib [ 28.551057] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.551069] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.551072] amdgpu :05:00.0: couldn't schedule ib [ 28.551083] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.551095] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.551122] amdgpu :05:00.0: couldn't schedule ib [ 28.551136] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.551148] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.713622] amdgpu :05:00.0: couldn't schedule ib [ 28.713646] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 28.713663] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 28.713667] amdgpu :05:00.0: couldn't schedule ib [ 28.713681] [drm:amdgpu_sched_r
[Kernel-packages] [Bug 1598935] Re: Ubuntu 16.04 won't properly boot due to radeon module issue
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598935 Title: Ubuntu 16.04 won't properly boot due to radeon module issue Status in linux package in Ubuntu: Expired Bug description: When I boot an Ubuntu 16.04 live DVD on a Gateway system with an AMD A6-5400K APU, with an integrated Radeon HD 7540D graphics adapter, I get a black screen with no video image. If I look at "dmesg" output, I see these messages: ubuntu@ubuntu:~$ dmesg | grep "UMS" [4.827258] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 39.561534] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 76.905778] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! We currently run Ubuntu 14.04.2 on the system with no issue, including using the "radeon" video driver. WORKAROUND: Boot using kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu 2057 F pulseaudio /dev/snd/controlC0: ubuntu 2057 F pulseaudio /dev/snd/controlC1: ubuntu 2057 F pulseaudio CasperVersion: 1.376 Date: Mon Jul 4 20:08:04 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway DX4380G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash nomodeset --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A1 dmi.board.name: DX4380G dmi.board.vendor: Gateway dmi.board.version: 1.02 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr: dmi.product.name: DX4380G dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598935/+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 1608191] Re: zfs-dkms 0.6.5.6-0ubuntu12: zfs kernel module failed to build
[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Expired -- 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/1608191 Title: zfs-dkms 0.6.5.6-0ubuntu12: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Expired Bug description: generate a error message on my board. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic i686 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-34-generic (i686) dimanche 31 juillet 2016, 10:23:29 (UTC+0200) make: *** Pas de cible spécifiée et aucun makefile n'a été trouvé. Arrêt. DKMSKernelVersion: 4.4.0-34-generic Date: Sun Jul 31 10:24:06 2016 InstallationDate: Installed on 2014-10-08 (661 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageVersion: 0.6.5.6-0ubuntu12 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu12: zfs kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-04-23 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1608191/+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 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18
I have been running for a few days with MTU=automatic (1500) on Ubuntu 16.04 with kernel 4.4.0-38-generic with no overrun errors. I didn't try with any kernels between 4.4.0-21 and 4.4.0-38, so I don't know at which update it would have begun to work, but it appears to be fixed. -- 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/1458208 Title: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18 Status in linux package in Ubuntu: Triaged Bug description: Partial lshw output: *-network description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Qualcomm Atheros physical id: 0 bus info: pci@:04:00.0 logical name: eth0 version: 08 serial: 70:54:d2:97:05:11 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=alx duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:30 memory:f710-f713 ioport:d000(size=128) Partial ifconfig output: eth0 Link encap:Ethernet HWaddr 70:54:d2:97:05:11 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1276 errors:609 dropped:0 overruns:609 frame:0 TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:230131 (230.1 KB) TX bytes:142978 (142.9 KB) Interrupt:17 The ethernet adapter stopped working on upgrade from linux 3.19.0-16-generic to 3.19.0-18-generic. Upon inital system start, I can successfully ping a remote server, but once I try any TCP connection, even ping fails. If I fallback to 3.19.0-16, everything is working OK. WORKAROUND: In Network manager, set the ethernet connection's MTU value from automatic to 8192. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mark 2611 F pulseaudio /dev/snd/controlC1: mark 2611 F pulseaudio /dev/snd/controlC0: mark 2611 F pulseaudio CurrentDesktop: Unity Date: Sat May 23 10:21:44 2015 HibernationDevice: RESUME=UUID=b4733b71-2c28-4a85-8450-6f330135cfe4 InstallationDate: Installed on 2013-04-24 (758 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Hewlett-Packard h8-1360t ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=578349d7-ca6f-4750-b977-7674ad95c763 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-20 (3 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: AMI dmi.bios.version: 7.15 dmi.board.name: 2AD5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.asset.tag: 2MD3140FD9 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.15:bd07/02/2012:svnHewlett-Packard:pnh8-1360t:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: h8-1360t dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/+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 1627574] modoc (ppc64el) - tests ran: 83, failed: 31
tests ran: 83, failed: 31; http://kernel.ubuntu.com/testing/4.8.0-18.20/modoc__4.8.0-18.20__2016-09-30_17-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627574 Title: linux: 4.8.0-18.20 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-18.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC kernel-phase:Packaging -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1627574/+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 1629509] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629509 Title: Cannot mount overlay with upperdir on overlay Status in linux package in Ubuntu: Confirmed Bug description: I have a docker setup using overlay as its storage driver. I mount an overlay in the container. Both the lower, upper and work directories are themselves on an overlay filesystem. This mount started to fail after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error message "overlayfs: filesystem on '/mnt/overlay/upper' not supported as upperdir". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaw 2257 F pulseaudio /dev/snd/controlC1: shaw 2257 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 30 20:06:03 2016 HibernationDevice: RESUME=UUID=f23b927f-5173-43fe-9269-8c7714fb0927 InstallationDate: Installed on 2016-07-23 (69 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=306f5ab9-de0e-4920-be20-3f4081e13c7e ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+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 1629509] [NEW] Cannot mount overlay with upperdir on overlay
Public bug reported: I have a docker setup using overlay as its storage driver. I mount an overlay in the container. Both the lower, upper and work directories are themselves on an overlay filesystem. This mount started to fail after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error message "overlayfs: filesystem on '/mnt/overlay/upper' not supported as upperdir". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaw 2257 F pulseaudio /dev/snd/controlC1: shaw 2257 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 30 20:06:03 2016 HibernationDevice: RESUME=UUID=f23b927f-5173-43fe-9269-8c7714fb0927 InstallationDate: Installed on 2016-07-23 (69 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=306f5ab9-de0e-4920-be20-3f4081e13c7e ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629509 Title: Cannot mount overlay with upperdir on overlay Status in linux package in Ubuntu: New Bug description: I have a docker setup using overlay as its storage driver. I mount an overlay in the container. Both the lower, upper and work directories are themselves on an overlay filesystem. This mount started to fail after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error message "overlayfs: filesystem on '/mnt/overlay/upper' not supported as upperdir". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaw 2257 F pulseaudio /dev/snd/controlC1: shaw 2257 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 30 20:06:03 2016 HibernationDevice: RESUME=UUID=f23b927f-5173-43fe-9269-8c7714fb0927 InstallationDate: Installed on 2016-07-23 (69 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=306f5ab9-de0e-4920-be20-3f4081e13c7e ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+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 1627574] dwalin (amd64) - tests ran: 19, failed: 0
tests ran: 19, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-18.20/dwalin__4.8.0-18.20__2016-10-01_00-09-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627574 Title: linux: 4.8.0-18.20 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-18.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC kernel-phase:Packaging -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1627574/+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 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628553] Re: Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop
For the record, this is also posted upstream: https://github.com/zfsonlinux/zfs/issues/5173 ** Bug watch added: Github Issue Tracker for ZFS #5173 https://github.com/zfsonlinux/zfs/issues/5173 -- 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/1628553 Title: Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop Status in zfs-linux package in Ubuntu: New Bug description: Fresh install of Ubuntu 16.04.1, installed all updates / upgrades for system before installing zfsutils-linux. The install processes all the way to Reached target Swap then has a PANIC error and loops endlessly. There is a zpool there already (was) with 3TB of data on it. This only happened after the system upgrade, so I reinstalled the boot drive / OS to see if it was just a issue with that, clearly it's an issue with the zfsutils-linux package for 16.04.1 Package version installed zfsutils-linux 0.6.5.6-0ubuntu12 Screenshot attached as I can't actually do anything once the boot gets to this stage: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628553/+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 1611078] Re: Support snaps inside of lxd containers
John has gotten all of the AppArmor kernel changes merged into the Yakkety kernel and my apparmor userspace upload is making its way through the autopkgtests. ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Committed ** Changed in: apparmor (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => Tyler Hicks (tyhicks) -- 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/1611078 Title: Support snaps inside of lxd containers Status in lxd: Unknown Status in Snappy: Fix Committed Status in apparmor package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in lxd package in Ubuntu: Fix Committed Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1611078/+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 1629480] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629480 Title: Internal Hard Drives Detected as Removable and External USB Drive as Non-Removable Status in linux package in Ubuntu: Confirmed Bug description: I excepted the 'dmraid' to detect my internal SATA Hard Drive as a non-removable device However, instead it reads it as removable and I am 95% sure it is a kernel problem due to it showing ones (removable) instead of zeros (non-removable) in /sys/class/block//removable. The only hard drive that has the correct listing is the one Ubuntu is installed on. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy linux-image-4.8.0-17-generic linux-image-4.8.0-17-generic: Installed: 4.8.0-17.19 Candidate: 4.8.0-17.19 Version table: *** 4.8.0-17.19 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status $ sudo dmraid -ay -vvv WARN: locking /var/lock/dmraid/.lock NOTICE: skipping removable device /dev/sdd NOTICE: skipping removable device /dev/sdb NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: pdc discovering NOTICE: /dev/sdc: sil discovering NOTICE: /dev/sdc: via discovering no raid disks WARN: unlocking /var/lock/dmraid/.lock $ sudo cat /sys/class/block//removable 0 $ sudo cat /sys/class/block//removable 1 $ sudo blkid /dev/sdb: TYPE="ddf_raid_member" /dev/sdd: TYPE="ddf_raid_member" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-generic 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Sep 30 17:32:35 2016 InstallationDate: Installed on 2016-07-04 (88 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp3s0f0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B75M-D3P ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=b1aa3e68-61ee-4e3e-be43-f5be5f8cef43 ro nomodeset RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-09-30 (0 days ago) dmi.bios.date: 07/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7s dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7s:bd07/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnB75M-D3P:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B75M-D3P dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629480/+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 1629482] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629482 Title: 4.4.0-38-generic reboots periodically Status in linux package in Ubuntu: Confirmed Bug description: When upgrading a server to 4.4.0-38-generic, it started to reboot every ~45 minutes without any visible reasons. Logs look fine. Just reboots. My other computer (a desktop) works fine with the same setup. Another difference: the server hosts ZFS raid. Unfortunately (fortunately) I had this problem ~2 years ago. That time after much debugging it turned out to be a kernel problem. So I loaded a previous kernel (4.4.0-36-generic), and it is rock solid again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic. AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Sep 30 17:35:35 2016 HibernationDevice: RESUME=/dev/mapper/croc--vg-swap_1 InstallationDate: Installed on 2013-11-05 (1060 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic root=/dev/mapper/hostname--vg-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-24 (159 days ago) dmi.bios.date: 05/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0216.2007.0502.1916 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP35DP dmi.board.vendor: Intel Corporation dmi.board.version: AAD81073-206 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0216.2007.0502.1916:bd05/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-206:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629482/+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 1629482] [NEW] 4.4.0-38-generic reboots periodically
Public bug reported: When upgrading a server to 4.4.0-38-generic, it started to reboot every ~45 minutes without any visible reasons. Logs look fine. Just reboots. My other computer (a desktop) works fine with the same setup. Another difference: the server hosts ZFS raid. Unfortunately (fortunately) I had this problem ~2 years ago. That time after much debugging it turned out to be a kernel problem. So I loaded a previous kernel (4.4.0-36-generic), and it is rock solid again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic. AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Sep 30 17:35:35 2016 HibernationDevice: RESUME=/dev/mapper/croc--vg-swap_1 InstallationDate: Installed on 2013-11-05 (1060 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic root=/dev/mapper/hostname--vg-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-24 (159 days ago) dmi.bios.date: 05/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0216.2007.0502.1916 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP35DP dmi.board.vendor: Intel Corporation dmi.board.version: AAD81073-206 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0216.2007.0502.1916:bd05/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-206:cvn:ct2:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629482 Title: 4.4.0-38-generic reboots periodically Status in linux package in Ubuntu: New Bug description: When upgrading a server to 4.4.0-38-generic, it started to reboot every ~45 minutes without any visible reasons. Logs look fine. Just reboots. My other computer (a desktop) works fine with the same setup. Another difference: the server hosts ZFS raid. Unfortunately (fortunately) I had this problem ~2 years ago. That time after much debugging it turned out to be a kernel problem. So I loaded a previous kernel (4.4.0-36-generic), and it is rock solid again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic. AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Sep 30 17:35:35 2016 HibernationDevice: RESUME=/dev/mapper/croc--vg-swap_1 InstallationDate: Installed on 2013-11-05 (1060 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: TERM=xterm-256color PATH=(custom, no use
[Kernel-packages] [Bug 1626604] dwalin (i386) - tests ran: 65, failed: 26
tests ran: 65, failed: 26; http://kernel.ubuntu.com/testing/3.13.0-97.144/dwalin__3.13.0-97.144__2016-09-30_18-28-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626604 Title: linux: 3.13.0-97.144 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-97.144 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1626604/+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 1629480] [NEW] Internal Hard Drives Detected as Removable and External USB Drive as Non-Removable
Public bug reported: I excepted the 'dmraid' to detect my internal SATA Hard Drive as a non- removable device However, instead it reads it as removable and I am 95% sure it is a kernel problem due to it showing ones (removable) instead of zeros (non-removable) in /sys/class/block//removable. The only hard drive that has the correct listing is the one Ubuntu is installed on. $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 $ apt-cache policy linux-image-4.8.0-17-generic linux-image-4.8.0-17-generic: Installed: 4.8.0-17.19 Candidate: 4.8.0-17.19 Version table: *** 4.8.0-17.19 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status $ sudo dmraid -ay -vvv WARN: locking /var/lock/dmraid/.lock NOTICE: skipping removable device /dev/sdd NOTICE: skipping removable device /dev/sdb NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: pdc discovering NOTICE: /dev/sdc: sil discovering NOTICE: /dev/sdc: via discovering no raid disks WARN: unlocking /var/lock/dmraid/.lock $ sudo cat /sys/class/block//removable 0 $ sudo cat /sys/class/block//removable 1 $ sudo blkid /dev/sdb: TYPE="ddf_raid_member" /dev/sdd: TYPE="ddf_raid_member" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-generic 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Sep 30 17:32:35 2016 InstallationDate: Installed on 2016-07-04 (88 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp3s0f0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B75M-D3P ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=b1aa3e68-61ee-4e3e-be43-f5be5f8cef43 ro nomodeset RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-09-30 (0 days ago) dmi.bios.date: 07/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7s dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7s:bd07/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnB75M-D3P:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B75M-D3P dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-bug linux yakkety -- 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/1629480 Title: Internal Hard Drives Detected as Removable and External USB Drive as Non-Removable Status in linux package in Ubuntu: New Bug description: I excepted the 'dmraid' to detect my internal SATA Hard Drive as a non-removable device However, instead it reads it as removable and I am 95% sure it is a kernel problem due to it showing ones (removable) instead of zeros (non-removable) in /sys/class/block//removable. The only hard drive that has the correct listing is the one Ubuntu is installed on. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy linux-image-4.8.0-17-generic linux-image-4.8.0-17-generic: Installed: 4.8.0-17.19 Candidate: 4.8.0-17.19 Version table: *** 4.8.0-17.19 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status $ sudo dmraid -ay -
[Kernel-packages] [Bug 1624569] Re: thunder: chip errata w/ multiple CQEs for a TSO packet
I don't have a reliable way to reproduce this crash, but I have not seen any regressions in my testing. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1624569 Title: thunder: chip errata w/ multiple CQEs for a TSO packet Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] With small segment sizes, it is possible for the driver to free an SKB before transmitting it, potentially resulting in a crash. [Test Case] The test case for this is to use a small MTU (200) and mount an NFS exported directory. Create several (~4) 1M files w/ dd, then copy them locally. However, I have not been able to trigger the crash myself. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624569/+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 1623627] Re: thunder: faulty TSO padding
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1623627 Title: thunder: faulty TSO padding Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] Certain packet sizes will trigger spurious TCP retransmissions on Cavium Thunder-X systems when TSO is enabled (the default). This can result in excess traffic and additional latency. [Test Case] Connect 2 systems to a 10G switch: - 1 ThunderX node (the client) - 1 "other" node - doesn't have to be ThunderX (the server) On the server, run the "receiver" command from the attached tcptest tarball: $ ./receiver Also on the server, run tcpdump to capture the traffic: $ sudo tcpdump -i -w tcpdump.out On the client, run the "sender" command from the tcptest tarball, with a 1461 packet size: $ ./sender 1461 1461 Kill the tcpdump process, and open it in wireshark. On failure, you'll see several "[TCP Spurious Retransmission]" packets - on success you should see none. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623627/+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 1629469] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1629469 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/1629469 Title: wifi wi-fi wireless connection drops down randomly Status in linux package in Ubuntu: Incomplete Bug description: wifi wi-fi wireless connection drops down flowing to kern.log: Sep 26 19:27:13 freelsd-luck kernel: [28423.068865] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:13 freelsd-luck kernel: [28423.182073] ath: phy0: Chip reset failed Sep 26 19:27:13 freelsd-luck kernel: [28423.182085] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:13 freelsd-luck kernel: [28423.258006] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:13 freelsd-luck kernel: [28423.371691] ath: phy0: Chip reset failed Sep 26 19:27:13 freelsd-luck kernel: [28423.371702] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:14 freelsd-luck kernel: [28423.447861] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:14 freelsd-luck kernel: [28423.560914] ath: phy0: Chip reset failed Sep 26 19:27:14 freelsd-luck kernel: [28423.560926] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:14 freelsd-luck kernel: [28423.636926] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Would be easier to have a opportunity to reset connection through logging out from DE. I do appreciate any clarifications! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ibus 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 30 23:27:14 2016 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2016-08-30 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629469/+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 1629469] Re: wifi wi-fi wireless connection drops down randomly
Should be a kernel issue, re-assigning. ** Package changed: ibus (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/1629469 Title: wifi wi-fi wireless connection drops down randomly Status in linux package in Ubuntu: New Bug description: wifi wi-fi wireless connection drops down flowing to kern.log: Sep 26 19:27:13 freelsd-luck kernel: [28423.068865] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:13 freelsd-luck kernel: [28423.182073] ath: phy0: Chip reset failed Sep 26 19:27:13 freelsd-luck kernel: [28423.182085] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:13 freelsd-luck kernel: [28423.258006] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:13 freelsd-luck kernel: [28423.371691] ath: phy0: Chip reset failed Sep 26 19:27:13 freelsd-luck kernel: [28423.371702] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:14 freelsd-luck kernel: [28423.447861] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:14 freelsd-luck kernel: [28423.560914] ath: phy0: Chip reset failed Sep 26 19:27:14 freelsd-luck kernel: [28423.560926] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:14 freelsd-luck kernel: [28423.636926] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Would be easier to have a opportunity to reset connection through logging out from DE. I do appreciate any clarifications! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ibus 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 30 23:27:14 2016 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2016-08-30 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629469/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image
This bug was fixed in the package zfs-linux - 0.6.5.8-0ubuntu3 --- zfs-linux (0.6.5.8-0ubuntu3) yakkety; urgency=medium [ Eric Desrochers ] * Fix zfs services to fail on first boot due to zfs services starting up before /etc/mtab has a chance to be symlinked to /proc/mounts. (LP: #1607920) (upstream commit 792517389fad5c495a2738b61c2e9c65dedaaa9a) -- Eric Desrochers Thu, 29 Sep 2016 16:13:38 +0200 ** Changed in: zfs-linux (Ubuntu) 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/1607920 Title: zfs services fail on firstboot if zfs-utils is integrated into the deployment image Status in sysvinit package in Ubuntu: Won't Fix Status in zfs-linux package in Ubuntu: Fix Released Status in sysvinit source package in Xenial: Won't Fix Status in zfs-linux source package in Xenial: In Progress Bug description: [Impact] * zfs services fail on firstboot if zfs-utils is integrated into the deployment image. * Output from systemd - sudo systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● zfs-import-scan.service loaded failed failed Import ZFS pools by device scanning ● zfs-mount.service loaded failed failed Mount ZFS filesystems * This is particularly frustrating for users who use automated monitoring as it means virtual machines must always be restarted before showing as clean. * This failure is due to zfs services starting up before /etc/mtab has a chance to be symlinked to /proc/mounts. [Test Case] 1. Grab a stock xenial image, and unpack it and add zfs-utils to it. Repack it. 2. Boot machine 3. Check systemctl --failed. [Regression Potential] * none expected, patch has been intensively tested by the upsteam zfs test script suite. * This is a upstream commit merge in 0.7.0. * A ubuntu package has been tested (including the upstream commit) by a user of the community facing this bug, and confirmed it addresses the problem (see comment #7). [Other Info] * The "reading" is redirected to /proc/self/mounts. The writing to /etc/mtab. Some distros still need that. The current hope is to replace the writing (and maybe reading) with libmount, in a second phase. * Upstream commit : https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680 * Debian bug : https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=839071 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1629469] [NEW] wifi wi-fi wireless connection drops down randomly
You have been subscribed to a public bug: wifi wi-fi wireless connection drops down flowing to kern.log: Sep 26 19:27:13 freelsd-luck kernel: [28423.068865] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:13 freelsd-luck kernel: [28423.182073] ath: phy0: Chip reset failed Sep 26 19:27:13 freelsd-luck kernel: [28423.182085] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:13 freelsd-luck kernel: [28423.258006] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:13 freelsd-luck kernel: [28423.371691] ath: phy0: Chip reset failed Sep 26 19:27:13 freelsd-luck kernel: [28423.371702] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:14 freelsd-luck kernel: [28423.447861] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Sep 26 19:27:14 freelsd-luck kernel: [28423.560914] ath: phy0: Chip reset failed Sep 26 19:27:14 freelsd-luck kernel: [28423.560926] ath: phy0: Unable to reset channel, reset status -22 Sep 26 19:27:14 freelsd-luck kernel: [28423.636926] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x AR_DIAG_SW=0x DMADBG_7=0x Would be easier to have a opportunity to reset connection through logging out from DE. I do appreciate any clarifications! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ibus 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 30 23:27:14 2016 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2016-08-30 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- wifi wi-fi wireless connection drops down randomly https://bugs.launchpad.net/bugs/1629469 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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4
@rlaager @kirkland @happyaron The SRU are usally for "High-impact bugs"... but the current SRU for Xenial might possibly fit in section : 2. When 2.2. Other safe cases For Long Term Support releases we sometimes want to introduce new features. They must not change the behaviour on existing installations (e. g. entirely new packages are usually fine). If existing software needs to be modified to make use of the new feature, it must be demonstrated that these changes are unintrusive, have a minimal regression potential, and have been tested properly. To avoid regressions on upgrade, any such feature must then also be added to any newer supported Ubuntu release. Once a new feature/package has been introduced, subsequent changes to it are subject to the usual requirements of SRUs to avoid regressions. [1] - https://wiki.ubuntu.com/StableReleaseUpdates Eric -- 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/1628279 Title: python utilities script suffix (.py) should be removed as per Policy 10.4 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: [Impact] The zfs utilities scripts shipped with debian and ubuntu such as : * arc_summary.py : Provides a summary of the statistics * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) * dbufstat.py : Print out statistics for all cached dmu buffers should be renamed according to Policy 10.4 : https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts "When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it." Ideally, this should be fixed and upstreamed to Debian (or to zfslinux upstream) as well. [Test Case] * Install zfsutils-linux * List files $ dpkg -L zfsutils-linux | egrep "arc|dbufstat" /usr/sbin/arc_summary.py /usr/sbin/arcstat.py /usr/sbin/dbufstat.py [Regression Potential] * none expected, this is a trivial change that simply rename the scripts to remove the extension (.py) with a simple 'mv' before the dh_install invocation in order to get this expected result : $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf" /usr/sbin/arc_summary /usr/sbin/arcstat /usr/sbin/dbufstat [Other Info] * Upstream (ZoL) is reluctant to change it at upstream code level. https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2 * This has been flag by Adam Conrad https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19 * Debian policy https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1626436] Re: [4.8 regression] boot has become very slow
I marked the "affects me too" button at the top, but just wanted to add that we're seeing slow boots on EC2 also. With the latest yakkety AMI on ec2 (ami-1bc5820c, us-east-1, m4.large) first and subsequent boots are are much slower than expected. Top 5 in the blame: $ systemd-analyze blame 2min 6.384s cloud-init.service 14.945s cloud-init-local.service 5.595s keyboard-setup.service 4.079s dev-xvda1.device 2.587s cloud-config.service -- 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: Triaged Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Meizu MX4, OTA-13 Seat Altea car, model 2009 No success to connect. At first the phone shows connected, but no feedback is shown on the car side. Then, after a while the phone says it is disconnected. Pretty much the same (mis-) behaviour in every OTA since the very beginning when I bought the MX4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4
Once this is in Yakkety, I think we should SRU it to Xenial. The sooner we change this, the less likelihood we have people relying on the old names (with .py) of these utilities. @kirkland, it'd be really nice to address this before ZFS lands in the default Server Seed for 16.04. -- 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/1628279 Title: python utilities script suffix (.py) should be removed as per Policy 10.4 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: [Impact] The zfs utilities scripts shipped with debian and ubuntu such as : * arc_summary.py : Provides a summary of the statistics * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) * dbufstat.py : Print out statistics for all cached dmu buffers should be renamed according to Policy 10.4 : https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts "When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it." Ideally, this should be fixed and upstreamed to Debian (or to zfslinux upstream) as well. [Test Case] * Install zfsutils-linux * List files $ dpkg -L zfsutils-linux | egrep "arc|dbufstat" /usr/sbin/arc_summary.py /usr/sbin/arcstat.py /usr/sbin/dbufstat.py [Regression Potential] * none expected, this is a trivial change that simply rename the scripts to remove the extension (.py) with a simple 'mv' before the dh_install invocation in order to get this expected result : $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf" /usr/sbin/arc_summary /usr/sbin/arcstat /usr/sbin/dbufstat [Other Info] * Upstream (ZoL) is reluctant to change it at upstream code level. https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2 * This has been flag by Adam Conrad https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19 * Debian policy https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4
Thanks Aron. -- 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/1628279 Title: python utilities script suffix (.py) should be removed as per Policy 10.4 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: [Impact] The zfs utilities scripts shipped with debian and ubuntu such as : * arc_summary.py : Provides a summary of the statistics * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) * dbufstat.py : Print out statistics for all cached dmu buffers should be renamed according to Policy 10.4 : https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts "When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it." Ideally, this should be fixed and upstreamed to Debian (or to zfslinux upstream) as well. [Test Case] * Install zfsutils-linux * List files $ dpkg -L zfsutils-linux | egrep "arc|dbufstat" /usr/sbin/arc_summary.py /usr/sbin/arcstat.py /usr/sbin/dbufstat.py [Regression Potential] * none expected, this is a trivial change that simply rename the scripts to remove the extension (.py) with a simple 'mv' before the dh_install invocation in order to get this expected result : $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf" /usr/sbin/arc_summary /usr/sbin/arcstat /usr/sbin/dbufstat [Other Info] * Upstream (ZoL) is reluctant to change it at upstream code level. https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2 * This has been flag by Adam Conrad https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19 * Debian policy https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4
Uploaded, needs approval from queue because of freeze. ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1628279 Title: python utilities script suffix (.py) should be removed as per Policy 10.4 Status in zfs-linux package in Ubuntu: Fix Committed Bug description: [Impact] The zfs utilities scripts shipped with debian and ubuntu such as : * arc_summary.py : Provides a summary of the statistics * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) * dbufstat.py : Print out statistics for all cached dmu buffers should be renamed according to Policy 10.4 : https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts "When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it." Ideally, this should be fixed and upstreamed to Debian (or to zfslinux upstream) as well. [Test Case] * Install zfsutils-linux * List files $ dpkg -L zfsutils-linux | egrep "arc|dbufstat" /usr/sbin/arc_summary.py /usr/sbin/arcstat.py /usr/sbin/dbufstat.py [Regression Potential] * none expected, this is a trivial change that simply rename the scripts to remove the extension (.py) with a simple 'mv' before the dh_install invocation in order to get this expected result : $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf" /usr/sbin/arc_summary /usr/sbin/arcstat /usr/sbin/dbufstat [Other Info] * Upstream (ZoL) is reluctant to change it at upstream code level. https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2 * This has been flag by Adam Conrad https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19 * Debian policy https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)
Functional and performance testing are also complete on the Azure side with the same results. Thanks! -- 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/1616677 Title: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: Please rebase the Hyper-V drivers and tools in lts-xenial (and yakkity) to the final v4.7.2 stable upstream kernel. The following files comprise Hyper-V support in the upstream kernel: arch/x86/kernel/cpu/mshyperv.c arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h include/linux/hyperv.h drivers/hv/channel.c drivers/hv/channel_mgmt.c drivers/hv/connection.c drivers/hv/hv_balloon.c drivers/hv/hv.c drivers/hv/hv_fcopy.c drivers/hv/hv_kvp.c drivers/hv/hv_snapshot.c drivers/hv/hv_util.c drivers/hv/hv_utils_transport.c drivers/hv/hv_utils_transport.h drivers/hv/hyperv_vmbus.h drivers/hv/ring_buffer.c drivers/hv/vmbus_drv.c tools/hv/hv_fcopy_daemon.c tools/hv/hv_get_dhcp_info.sh tools/hv/hv_get_dns_info.sh tools/hv/hv_kvp_daemon.c tools/hv/hv_set_ifconfig.sh tools/hv/hv_vss_daemon.c tools/hv/lsvmbus drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/hyperv_net.h drivers/net/hyperv/netvsc.c drivers/net/hyperv/netvsc_drv.c drivers/net/hyperv/rndis_filter.c drivers/scsi/storvsc_drv.c drivers/hid/hid-hyperv.c drivers/pci/host/pci-hyperv.c drivers/video/fbdev/hyperv_fb.c While I know a number of post-4.6 commits are already included, I am including all of the commits from 4.6 to 4.7.2 for reference: channel_mgmt.c : commit cd95aad5579371ac332507fc946008217fc37e6c : Drivers: hv: vmbus: handle various crash scenarios connection.c : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: hv: vmbus: Export the vmbus_set_event() API hv_balloon.c : commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d : Drivers: hv: balloon: don't crash when memory is added in non-sorted order hv_balloon.c : commit d19a55d6ed5bf0ffe553df2d8bf91d054ddf2d76 : Drivers: hv: balloon: reset host_specified_ha_region hv_kvp.c : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: kvp: fix IP Failover hyperv_fb.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : drivers:hv: Use new vmbus_mmio_free() from client drivers. hyperv.h : commit 97fb77dc87582300fa3c141b63699f853576cab1 : drivers:hv: Make a function to free mmio regions through vmbus hyperv.h : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer hyperv.h : commit ab028db41ca9174caab7f9e3fc0a2e7f4a418410 : Drivers: hv: vmbus: Implement APIs to support "in place" consumption of vmbus packets hyperv_net.h : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : hv_netvsc: Eliminate status from struct hv_netvsc_packet hyperv_net.h : commit 3d541ac5a92af708d0085925d136f875f3a58d57 : hv_netvsc: untangle the pointer mess hyperv_net.h : commit c85e4924452ae8225c8829f3fa8a2f7baa34bc5c : hv_netvsc: Fix book keeping of skb during batching process hyperv_vmbus.h : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: kvp: fix IP Failover hyperv_vmbus.h : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: hv: vmbus: Export the vmbus_set_event() API hyperv_vmbus.h : commit cd95aad5579371ac332507fc946008217fc37e6c : Drivers: hv: vmbus: handle various crash scenarios lsvmbus : commit 552beb4930ef3889d42a049eb9ba3533b4cbe0f6 : tools: hv: lsvmbus: add pci pass-through UUID netvsc_drv.c : commit 15cfd40771e18a4e9b788c64c9db2606f958b93d : hv_netvsc: Fix the list processing for network change event netvsc_drv.c : commit 1bdcec8a5f05445752a0639edd603ac09ae6c553 : hv_netvsc: use start_remove flag to protect netvsc_link_change() netvsc_drv.c : commit 84bf9cefb162b197da20a0f4388929f4b5ba5db4 : hv_netvsc: Implement support for VF drivers on Hyper-V pci-hyperv.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : drivers:hv: Use new vmbus_mmio_free() from client drivers. pci-hyperv.c : commit bdd74440d9e887b1fa648eefa17421def5f5243c : PCI: hv: Add explicit barriers to config space access pci-hyperv.c : commit deb22e5c84c884a129d801cf3bfde7411536998d : PCI: hv: Report resources release after stopping the bus ring_buffer.c : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer rndis_filter.c : commit 0a1275ca5128b84c149960969ed351ae00eb : hv_netvsc: get rid of struct net_device pointer in struct netvsc_device rndis_filter.c : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 :
[Kernel-packages] [Bug 1628204] kernel01 (s390x.zVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-30_18-07-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_18-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] kernel01 (s390x.zVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-30_17-56-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 1, failed: 1
tests ran: 1, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_18-02-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_17-50-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] kernel01 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-30_17-53-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] kernel01 (s390x.zVM) - tests ran: 83, failed: 0
tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-30_17-23-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_17-47-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 83, failed: 1
tests ran: 83, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_17-23-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1620636] Re: Fails to pair with Bose QC35 headphones
** Description changed: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ + + With Linux kernel 4.8.0 and bluez 4.52: + --- + http://pastebin.ubuntu.com/23256457/ ** Description changed: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- - http://pastebin.ubuntu.com/23256457/ + + bluetoothctl: http://pastebin.ubuntu.com/23256457/ + btmon: http://pastebin.ubuntu.com/23256471/ ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: bluez (Ubuntu) Status: New => In Progress ** Changed in: canonical-devices-system-image Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 136, failed: 27
tests ran: 136, failed: 27; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_17-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] kernel01 (s390x.zVM) - tests ran: 136, failed: 27
tests ran: 136, failed: 27; http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-30_16-54-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1628204] s2lp6g001 (s390x.zKVM) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-30_16-43-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1425333] Re: Precise kernel lockup with Intel Corporation 82579LM network interfaces
** Tags removed: verification-failed-precise -- 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/1425333 Title: Precise kernel lockup with Intel Corporation 82579LM network interfaces Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: Fix Committed Bug description: SRU Justification: Impact: e1000e driver can lockup in machine HP Z210. Fix: All the patches were taken from upstream. Testcase: To use an HP Z210 machine and wait certain conditions. Original Description: It was brought to my attention the following lockup (and error message): Feb 1 21:17:54 hostname kernel: [10461681.674619] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out """ Feb 1 21:17:54 hostname kernel: [10461681.674613] WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270() Feb 1 21:17:54 hostname kernel: [10461681.674616] Hardware name: HP Z210 Workstation Feb 1 21:17:54 hostname kernel: [10461681.674619] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Feb 1 21:17:54 hostname kernel: [10461681.674622] Modules linked in: nvidia(P) btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext2 openafs(P) bnep rfcomm bluetooth autofs4 parport_pc ppdev nfsd nfs binfmt_misc lockd fscache auth_rpcgss nfs_acl sunrpc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq joydev hp_wmi snd_timer snd_seq_device snd mei(C) psmouse soundcore sparse_keymap serio_raw mac_hid wmi snd_page_alloc lp parport dm_multipath ses enclosure hid_logitech_dj usb_storage usbhid hid e1000e [last unloaded: nvidia] Feb 1 21:17:54 hostname kernel: [10461681.674683] Pid: 0, comm: swapper/0 Tainted: P C O 3.2.0-69-generic #103-Ubuntu Feb 1 21:17:54 hostname kernel: [10461681.674684] Call Trace: Feb 1 21:17:54 hostname kernel: [10461681.674685] [] warn_slowpath_common+0x7f/0xc0 Feb 1 21:17:54 hostname kernel: [10461681.674692] [] ? __enqueue_entity+0x74/0x80 Feb 1 21:17:54 hostname kernel: [10461681.674694] [] warn_slowpath_fmt+0x46/0x50 Feb 1 21:17:54 hostname kernel: [10461681.674696] [] ? x86_pmu_enable+0x1f2/0x270 Feb 1 21:17:54 hostname kernel: [10461681.674699] [] dev_watchdog+0x25a/0x270 Feb 1 21:17:54 hostname kernel: [10461681.674701] [] ? perf_rotate_context+0x110/0x220 Feb 1 21:17:54 hostname kernel: [10461681.674703] [] ? qdisc_reset+0x50/0x50 Feb 1 21:17:54 hostname kernel: [10461681.674705] [] ? qdisc_reset+0x50/0x50 Feb 1 21:17:54 hostname kernel: [10461681.674708] [] call_timer_fn+0x46/0x160 Feb 1 21:17:54 hostname kernel: [10461681.674710] [] ? qdisc_reset+0x50/0x50 Feb 1 21:17:54 hostname kernel: [10461681.674712] [] run_timer_softirq+0x132/0x2a0 Feb 1 21:17:54 hostname kernel: [10461681.674715] [] ? ktime_get+0x65/0xe0 Feb 1 21:17:54 hostname kernel: [10461681.674717] [] __do_softirq+0xa8/0x210 Feb 1 21:17:54 hostname kernel: [10461681.674719] [] ? tick_program_event+0x24/0x30 Feb 1 21:17:54 hostname kernel: [10461681.674723] [] call_softirq+0x1c/0x30 Feb 1 21:17:54 hostname kernel: [10461681.674725] [] do_softirq+0x65/0xa0 Feb 1 21:17:54 hostname kernel: [10461681.674727] [] irq_exit+0x8e/0xb0 Feb 1 21:17:54 hostname kernel: [10461681.674729] [] smp_apic_timer_interrupt+0x6e/0x99 Feb 1 21:17:54 hostname kernel: [10461681.674731] [] apic_timer_interrupt+0x6e/0x80 Feb 1 21:17:54 hostname kernel: [10461681.674732] [] ? __switch_to_xtra+0x171/0x180 Feb 1 21:17:54 hostname kernel: [10461681.674737] [] ? intel_idle+0xed/0x150 Feb 1 21:17:54 hostname kernel: [10461681.674739] [] ? intel_idle+0xcf/0x150 Feb 1 21:17:54 hostname kernel: [10461681.674742] [] cpuidle_idle_call+0xc1/0x290 Feb 1 21:17:54 hostname kernel: [10461681.674744] [] cpu_idle+0xca/0x120 Feb 1 21:17:54 hostname kernel: [10461681.674746] [] rest_init+0x72/0x74 Feb 1 21:17:54 hostname kernel: [10461681.674750] [] start_kernel+0x3b5/0x3c2 Feb 1 21:17:54 hostname kernel: [10461681.674752] [] x86_64_start_reservations+0x132/0x136 Feb 1 21:17:54 hostname kernel: [10461681.674754] [] ? early_idt_handlers+0x140/0x140 Feb 1 21:17:54 hostname kernel: [10461681.674756] [] x86_64_start_kernel+0xcd/0xdc Feb 1 21:17:54 hostname kernel: [10461681.674757] ---[ end trace a84a3dbc98d19bff ]--- Feb 1 21:17:54 hostname kernel: [10461681.674762] e1000e :00:19.0: eth0: Reset adapter Feb 1 21:17:58 hostname kernel: [10461685.529232] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx """ This happens with the e1000e module on HP z210 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/
[Kernel-packages] [Bug 1622763] Re: Sennheiser Officerunner - cannot get freq at ep 0x83
Hi David, When you have a chance, can you verify this bug is fixed? See comment #23. Thanks in advance! ** Changed in: linux (Ubuntu Yakkety) 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/1622763 Title: Sennheiser Officerunner - cannot get freq at ep 0x83 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: This USB headset doesn't seem to support sample rate polling, similar to this issue: https://bugzilla.kernel.org/show_bug.cgi?id=95961 == The problem == Every time something goes to interact with the device (playing a sound file, opening the sound panel, opening web audio/video), a 10 second pause is encountered, where dmesg prints out two messages: usb 2-1.2: 2:1: cannot get freq at ep 0x83 usb 2-1.2: 2:1: cannot get freq at ep 0x83 Once the sound is playing, everything is fine. These sample rate polls don't seem to keep happening. After waiting for maybe 30 seconds after sound is playing, future interactions will again trigger the pause. This 10 second pause can introduce other subtle problems. For instance, google hangouts will sometimes timeout waiting for the sound device to respond, and the browser tab will crash or not fully load as a result. The sound panel often also will not display the device in the list of choices, and you will have to close it out. Sometimes restart pulse audio to get it to recognize the headset again. == The solution == It is simple, add this USB ID to the sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function. case USB_ID(0x1395, 0x740a): /* Sennheiser Officerunner */ version signature: Ubuntu 4.4.0-36.55-generic 4.4.16 # lsusb |grep Senn Bus 002 Device 004: ID 1395:740a Sennheiser Communications # zcat /var/log/kern.log.2.gz | grep 'cannot get' | tail -4 Sep 2 11:26:56 helo kernel: [908040.937098] usb 2-1.2: 2:1: cannot get freq at ep 0x4 Sep 2 11:27:01 helo kernel: [908045.941168] usb 2-1.2: 2:1: cannot get freq at ep 0x4 Sep 2 12:18:44 helo kernel: [911149.006318] usb 2-1.2: 3:1: cannot get freq at ep 0x83 Sep 2 12:18:49 helo kernel: [911154.010268] usb 2-1.2: 3:1: cannot get freq at ep 0x83 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dpb 12893 F pulseaudio /dev/snd/controlC2: dpb 12893 F pulseaudio /dev/snd/controlC1: dpb 12893 F pulseaudio /dev/snd/controlC0: dpb 12893 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a9a39ff3-c97d-471e-a0b3-518b4db8685c InstallationDate: Installed on 2015-03-18 (544 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) MachineType: Hewlett-Packard HP Z620 Workstation NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/vgroot-lvroot ro console=tty0 console=ttyS4,115200 nosplash nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-02-16 (210 days ago) UserGroups: adm cdrom dip docker libvirtd lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.88 dmi.board.asset.tag: 2UA41528ZC dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: 2UA41528ZC dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/+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 1625932] Re: Backlight does not change when adjust it higher than 50% after S3
Hello, When you have a chance, can you verify this bug is fixed? See comment #2. Thanks in advance! -- 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/1625932 Title: Backlight does not change when adjust it higher than 50% after S3 Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Backlight does not change when adjust it higher than 50% after S3 Steps: 1. Install ubuntu 16.04 and boot into OS 2. suspend system 3. resume system from S3 4. Try to adjust brightness level Expected results: Backlight should be changed when adjust it Actual results: Backlight does not change when adjust it higher than 50% after S3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1625932/+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 1628204] kernel01 (s390x.zVM) - tests ran: 19, failed: 11
tests ran: 19, failed: 11; http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-30_16-43-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620317 Title: ISST-LTE:pNV: system ben is hung during ST (nvme) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: On when we are running I/O intensive tasks and CPU addition/removal, the block may hang stalling the entire machine. The backtrace below is one of the symptoms: [12747.49] ---[ end trace b4d8d720952460b5 ]--- [12747.126885] Trying to free IRQ 357 from IRQ context! [12747.146930] [ cut here ] [12747.166674] WARNING: at /build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438 [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW OEL 4.4.0-21-generic #37-Ubuntu [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: c00f1fb6c000 [12747.404848] NIP: c0131888 LR: c0131884 CTR: 300303f0 [12747.808333] REGS: c00f1fb6e550 TRAP: 0700 Tainted: GW OEL (4.4.0-21-generic) [12747.867658] MSR: 900100029033 CR: 2802 XER: 2000 [12747.884783] CFAR: c0aea8f4 SOFTE: 1 GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da GPR08: 0007 c0f8b27c 000f2948 90011003 GPR12: 2200 c7b6f800 c00f2a40a938 0100 GPR16: c00f1148 3a98 GPR20: d9521008 d95146a0 f000 GPR24: c4a19ef0 0003 007d GPR28: 0165 c00eefeb1800 c00eef830600 0165 [12748.243270] NIP [c0131888] __free_irq+0x238/0x370 [12748.254089] LR [c0131884] __free_irq+0x234/0x370 [12748.269738] Call Trace: [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 (unreliable) [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0 [12748.304594] [c00f1fb6e890] [d9514528] nvme_suspend_queue+0xc8/0x150 [nvme] [12748.333825] [c00f1fb6e8c0] [d951681c] nvme_dev_disable+0x3fc/0x400 [nvme] [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 [nvme] [12748.357136] [c00f1fb6ea60] [c0548a34] blk_mq_rq_timed_out+0x64/0x110 [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170 [12748.399292] [c00f1fb6eb40] [c054d4e8] blk_mq_queue_tag_busy_iter+0x78/0x110 [12748.402665] [c00f1fb6eb90] [c0547358] blk_mq_rq_timer+0x48/0x140 [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0 [12748.468126] [c00f1fb6ec60] [c014a5fc] run_timer_softirq+0x31c/0x3f0 [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0 [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100 [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0 [12748.516377] [c00f1fb6ee70] [c0002714] decrementer_common+0x114/0x180 [12748.547282] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90 [12748.547282] LR = arch_local_irq_restore+0x74/0x90 [12748.574141] [c00f1fb6f160] [0001] 0x1 (unreliable) [12748.592405] [c00f1fb6f180] [c0aedc3c] dump_stack+0xd0/0xf0 [12748.596461] [c00f1fb6f1c0] [c01006fc] dequeue_task_idle+0x5c/0x90 [12748.611532] [c00f1fb6f230] [c00f6080] deactivate_task+0xc0/0x130 [12748.627685] [c00f1fb6f270] [c0adcb10] __schedule+0x440/0x990 [12748.654416] [c00f1fb6f300] [c0add0a8] schedule+0x48/0xc0 [12748.670558] [c00f1fb6f330] [c0ae1474] schedule_timeout+0x274/0x350 [12748.673485] [c00f1fb6f420] [c0ade23c] wait_for_common+0xec/0x240 [12748.69
[Kernel-packages] [Bug 1624569] Re: thunder: chip errata w/ multiple CQEs for a TSO packet
** Changed in: linux (Ubuntu) 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/1624569 Title: thunder: chip errata w/ multiple CQEs for a TSO packet Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] With small segment sizes, it is possible for the driver to free an SKB before transmitting it, potentially resulting in a crash. [Test Case] The test case for this is to use a small MTU (200) and mount an NFS exported directory. Create several (~4) 1M files w/ dd, then copy them locally. However, I have not been able to trigger the crash myself. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624569/+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 1623627] Re: thunder: faulty TSO padding
** Changed in: linux (Ubuntu) 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/1623627 Title: thunder: faulty TSO padding Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] Certain packet sizes will trigger spurious TCP retransmissions on Cavium Thunder-X systems when TSO is enabled (the default). This can result in excess traffic and additional latency. [Test Case] Connect 2 systems to a 10G switch: - 1 ThunderX node (the client) - 1 "other" node - doesn't have to be ThunderX (the server) On the server, run the "receiver" command from the attached tcptest tarball: $ ./receiver Also on the server, run tcpdump to capture the traffic: $ sudo tcpdump -i -w tcpdump.out On the client, run the "sender" command from the tcptest tarball, with a 1461 packet size: $ ./sender 1461 1461 Kill the tcpdump process, and open it in wireshark. On failure, you'll see several "[TCP Spurious Retransmission]" packets - on success you should see none. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623627/+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 1625932] Re: Backlight does not change when adjust it higher than 50% after S3
** Changed in: linux (Ubuntu) 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/1625932 Title: Backlight does not change when adjust it higher than 50% after S3 Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Backlight does not change when adjust it higher than 50% after S3 Steps: 1. Install ubuntu 16.04 and boot into OS 2. suspend system 3. resume system from S3 4. Try to adjust brightness level Expected results: Backlight should be changed when adjust it Actual results: Backlight does not change when adjust it higher than 50% after S3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1625932/+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 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux package in Debian: Fix Released Bug description: SRU Justification: Impact: Users of VMs running 3.13/3.16 and ext4 can experience data corruption in the guest. Fix: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424 Testcase: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22 -- I noticed that one of my VM had this "dmesg -T" output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 [Thu Feb 19 06:25:09 2015] Oops: [#1] SMP [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G W 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 task.ti: 880003a1 [Thu Feb 19 06:25:09 2015] RIP: 0010:[] [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58 EFLAGS: 00010292 [Thu Feb 19 06:25:09 2015] RAX: RBX: RCX: 00
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Confirmed Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Tags removed: verification-needed-vivid -- 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/1490895 Title: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: This is a long-standing bug for some Haswell, Broadwell and most Skylake machines. When the HDA audio controller is in D3, a hotplug event (i e, HDMI or DisplayPort being plugged in) fails to wake up the audio side so it never registers that something has happened. By having the i915 driver call directly into the hda driver, the HDA driver is always notified that an HDMI hotplug event has happened. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1490895/+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 1541330] Re: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid)
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: Fix Released Status in linux-lts-vivid package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+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 1540731] Re: SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session" on kernel 4.4 (bu
** Tags removed: verification-needed-trusty verification-needed-vivid
** Tags added: verification-done-trusty verification-done-vivid
--
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/1540731
Title:
SocketMessenger::update_session_creds() fails to get client PID,
causing "[ FAILED ]
PromptSessionClientAPI.client_pid_is_associated_with_session" on
kernel 4.4 (but kernel 4.3 works)
Status in GLibC:
New
Status in Mir:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Vivid:
Fix Released
Bug description:
Since updating to the 4.4.0-2 kernel recvmsg() fails SCM_CREDENTIALS
request with EOPNOTSUPP.
This manifests as a test failure in Mir:
[ RUN ] PromptSessionClientAPI.client_pid_is_associated_with_session
unknown file: Failure
Test case:
#include
#include
#include
#include
#include
#include
#include
int main()
{
enum { server, client, size };
int socket_fd[size];
int const opt = 1;
assert(socketpair(AF_LOCAL, SOCK_STREAM, 0, socket_fd) == 0);
char const msg[] = "A random message";
send(socket_fd[client], msg, sizeof msg, MSG_DONTWAIT | MSG_NOSIGNAL);
assert(setsockopt(socket_fd[server], SOL_SOCKET, SO_PASSCRED,
&opt, sizeof(opt)) != -1);
union {
struct cmsghdr cmh;
char control[CMSG_SPACE(sizeof(ucred))];
} control_un;
control_un.cmh.cmsg_len = CMSG_LEN(sizeof(ucred));
control_un.cmh.cmsg_level = SOL_SOCKET;
control_un.cmh.cmsg_type = SCM_CREDENTIALS;
msghdr msgh;
msgh.msg_name = NULL;
msgh.msg_namelen = 0;
msgh.msg_iov = NULL;
msgh.msg_iovlen = 0;
msgh.msg_control = control_un.control;
msgh.msg_controllen = sizeof(control_un.control);
errno = 0;
if (recvmsg(socket_fd[server], &msgh, MSG_PEEK) == -1)
{
printf("Error: %s\n", strerror(errno));
exit(EXIT_FAILURE);
}
else
{
printf("Success!\n");
exit(EXIT_SUCCESS);
}
}
===
Kernel-Description: recvmsg() fails SCM_CREDENTIALS request with EOPNOTSUPP.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1540731/+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 1518855] Re: Backport better suspend/resume function for pinctrl-cherryview
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- 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/1518855 Title: Backport better suspend/resume function for pinctrl-cherryview Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: [Impact] On some platforms the touchpad relies on pinctrl devices to provide GPIO interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and will lose the config after suspend/resume, then touchpad can't be used. [Fix] There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview: commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e Refs: [HEAD] Author: Mika Westerberg Date: Thu Dec 4 12:32:50 2014 +0200 pinctrl: cherryview: Save and restore pin configs over system sle which can be clean cherry-picked [Test] 3.19.0-33 -> failed 4.2-> passed 4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test 3.19.0-33 + patched module -> passed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1518855/+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 1529077] Re: USB device resets since kernel version 3.13.0-73-generic #116-Ubuntu
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1529077 Title: USB device resets since kernel version 3.13.0-73-generic #116-Ubuntu Status in linux package in Ubuntu: Triaged Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux-lts-utopic source package in Vivid: Invalid Bug description: I am using Ubuntu 14.04 with Gnome desktop. When running "goobox" (a cd-player application) the application hangs for about 30 seconds before being initialized. During this one core of the cpu is running at 100% utilization. The following lines appear then in the syslog: Dec 24 13:14:27 computer4 kernel: [ 1386.238349] usb 3-1: reset high-speed USB device number 2 using xhci_hcd Dec 24 13:14:27 computer4 kernel: [ 1386.293951] xhci_hcd :03:00.0: xHCI xhci_drop_endpoint called with disabled ep 880036272600 Dec 24 13:14:27 computer4 kernel: [ 1386.293955] xhci_hcd :03:00.0: xHCI xhci_drop_endpoint called with disabled ep 880036272640 The CD drive is a external USB one connected to a USB 3.0 port: Bus 003 Device 002: ID 0e8d:1806 MediaTek Inc. Samsung SE-208AB Slim Portable DVD Writer This behaviour appeared with the kernel version 3.13.0-73-generic #116-Ubuntu. Running "goobox" on the same system with kernel 3.13.0-71 does not exhibit this behaviour. Using the newest available kernel 3.13.0-74 the problem persists. Kernel, goobox and the other software are installed from official Ubuntu packages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-73-generic 3.13.0-73.116 ProcVersionSignature: Ubuntu 3.13.0-73.116-generic 3.13.11-ckt30 Uname: Linux 3.13.0-73-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: markus 2224 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 24 13:08:36 2015 HibernationDevice: RESUME=UUID=e711920c-5aab-410e-b993-bb341ddfa987 InstallationDate: Installed on 2014-12-13 (376 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B06211 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-73-generic root=UUID=a501b8b5-7f50-4131-ad2e-cc401009acbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-73-generic N/A linux-backports-modules-3.13.0-73-generic N/A linux-firmware 1.127.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: EB062IMS V1.4 dmi.board.name: MS-B0621 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 100 dmi.chassis.type: 13 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrEB062IMSV1.4:bd08/25/2014:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B06211:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-B0621:rvr100:cvnMICRO-STARINTERNATIONALCO.,LTD:ct13:cvr: dmi.product.name: MS-B06211 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529077/+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 1454687] Re: add NX 842 hw compression patches
** Changed in: initramfs-tools (Ubuntu Vivid) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- 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/1454687 Title: add NX 842 hw compression patches Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in initramfs-tools source package in Vivid: Fix Released Status in linux source package in Vivid: Fix Released Bug description: [Impact] Users of PowerPC processors with an NX coprocessor will not be able to use features like memory compression without this set of patches. [Test Case] Run kernel on a PowerPC processor with an NX coprocessor implementing 842 memory compression. [Fix] Commits: b130e7c04f1130f241eddf72098a6e08d41d08fe edc424f8cd84bbae530d8a9f86caf1923606fb24 2da572c959dd5815aef153cf62010b16a498a0d3 2062c5b6da758ca2bb64b698d7f9c5c45a06fcf9 fdd05e4b9ae22603ed09beb4e179ae7746555a81 7011a122383e36dab594406720fa1d089e0be8f9 959e6659b6f74ec1fa4d391a3b88d63dc0189f36 99182a42b7ef3d5e4180992ce01befd9e87526d2 b8e04187c90107c58d1ccbeb68a0ba4c5bfd4167 ed70b479c2c0b6e1319f0cb2de19f1051be219a4 f7ead7b47a758bbee6fdc66f95f27fdb866e5e9d ca7fc7e962fa067ba31f76a6e5828537394f6481 9358eac06b8fcf9fcaf566ec825fc05e2b1acd10 3e648cbeb31be5cb84b9ec19822e2b85417f07c4 3154de71258a32040214fda174e67b975b0810ef 32be6d3e362b896c81aae7c635d44e5a91406ce2 2c6f6eabc0bfcea0a62370038da713e3873cff31 c47d63020c03659e584673f78f24f2e5de3e6b9b Plus the following configuration changes: +CONFIG_842_COMPRESS=m +CONFIG_842_DECOMPRESS=m +CONFIG_CRYPTO_DEV_NX_COMPRESS_CRYPTO=m +CONFIG_CRYPTO_DEV_NX_COMPRESS_POWERNV=m +CONFIG_CRYPTO_DEV_NX_COMPRESS_PSERIES=m In addition some modules need to be loaded by initramfs which requires changes to the initramfs-tools package. The modules are: nx-compress nx-compress-crypto nx-compress-platform nx-compress-pseries nx-compress-powernv 842-decompress -- Please add/include the patches for PowerPC NX coprocessor 842 memory compression. They're currently in Herbert Xu's upstream tree, and presumably he will send them up to Linus at the 4.2 merge window. You can find the commits at git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git ed70b47 crypto: nx - add hardware 842 crypto comp alg b8e04187 crypto: nx - simplify pSeries nx842 driver 99182a42 crypto: nx - add PowerNV platform NX-842 driver 959e665 crypto: nx - add nx842 constraints 7011a12 crypto: nx - add NX-842 platform frontend driver fdd05e4 crypto: nx - rename nx-842.c to nx-842-pseries.c 2062c5b crypto: 842 - change 842 alg to use software 2da572c lib: add software 842 compression/decompression edc424f powerpc: Add ICSWX instruction b130e7c powerpc: export of_get_ibm_chip_id function I'll update this when they are added to Linus' tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1454687/+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 1598197] Re: deadlock on balloon deflation
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1598197
Title:
deadlock on balloon deflation
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Trusty:
Fix Released
Bug description:
Latest Ubuntu trusty with kernel 3.13.0-91-generic run in a KVM
virtual machine with virtio_balloon hangs when the previously inflated
balloon is deflated.
The problem is in the recently committed backport:
commit 838478a8496ef9677256f53710144abe2ea49625
Author: Konstantin Khlebnikov
AuthorDate: Mon May 16 14:43:10 2016 +0800
Commit: Kamal Mostafa
CommitDate: Fri Jun 10 07:15:37 2016 -0700
mm/balloon_compaction: redesign ballooned pages management
BugLink: http://bugs.launchpad.net/bugs/1572562
Sasha Levin reported KASAN splash inside isolate_migratepages_range().
Problem is in the function __is_movable_balloon_page() which tests
AS_BALLOON_MAP in page->mapping->flags. This function has no protection
against anonymous pages. As result it tried to check address space flags
inside struct anon_vma.
Further investigation shows more problems in current implementation:
* Special branch in __unmap_and_move() never works:
balloon_page_movable() checks page flags and page_count. In
__unmap_and_move() page is locked, reference counter is elevated, thus
balloon_page_movable() always fails. As a result execution goes to the
normal migration path. virtballoon_migratepage() returns
MIGRATEPAGE_BALLOON_SUCCESS instead of MIGRATEPAGE_SUCCESS,
move_to_new_page() thinks this is an error code and assigns
newpage->mapping to NULL. Newly migrated page lose connectivity with
balloon an all ability for further migration.
* lru_lock erroneously required in isolate_migratepages_range() for
isolation ballooned page. This function releases lru_lock periodically,
this makes migration mostly impossible for some pages.
* balloon_page_dequeue have a tight race with balloon_page_isolate:
balloon_page_isolate could be executed in parallel with dequeue between
picking page from list and locking page_lock. Race is rare because they
use trylock_page() for locking.
This patch fixes all of them.
Instead of fake mapping with special flag this patch uses special state of
page->_mapcount: PAGE_BALLOON_MAPCOUNT_VALUE = -256. Buddy allocator uses
PAGE_BUDDY_MAPCOUNT_VALUE = -128 for similar purpose. Storing mark
directly in struct page makes everything safer and easier.
PagePrivate is used to mark pages present in page list (i.e. not
isolated, like PageLRU for normal pages). It replaces special rules for
reference counter and makes balloon migration similar to migration of
normal pages. This flag is protected by page_lock together with link to
the balloon device.
Signed-off-by: Konstantin Khlebnikov
Reported-by: Sasha Levin
Link: http://lkml.kernel.org/p/53e6ceaa.9020...@oracle.com
Cc: Rafael Aquini
Cc: Andrey Ryabinin
Cc: [3.8+]
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
(backported from commit d6d86c0a7f8ddc5b38cf089222cb1d9540762dc2)
Signed-off-by: Gavin Guo
Conflicts:
mm/balloon_compaction.c
mm/migrate.c
Acked-by: Stefan Bader
Signed-off-by: Kamal Mostafa
It was applied after another backport:
commit 47618e32c2a729554bf56b8ee7b541b63aadad97
Author: Minchan Kim
AuthorDate: Mon Dec 28 08:35:13 2015 +0900
Commit: Luis Henriques
CommitDate: Mon Feb 22 19:31:53 2016 +
virtio_balloon: fix race between migration and ballooning
BugLink: http://bugs.launchpad.net/bugs/1542497
commit 21ea9fb69e7c4b1b1559c3e410943d3ff248ffcb upstream.
In balloon_page_dequeue, pages_lock should cover the loop
(ie, list_for_each_entry_safe). Otherwise, the cursor page could
be isolated by compaction and then list_del by isolation could
poison the page->lru.{prev,next} so the loop finally could
access wrong address like this. This patch fixes the bug.
general protection fault: [#1] SMP
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 2 PID: 82 Comm: vballoon Not tainted 4.4.0-rc5-mm1-access_bit+ #1906
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs
01/01/2011
task: 8800a7ff ti: 8800a7fec000 task.ti: 8800a7fec000
RIP: 0010:[] []
balloon_page_dequeue+0x54/0x130
RSP: 0018:880
[Kernel-packages] [Bug 1628238] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
Patch in "linux-kernel-bugs #111291" ** Bug watch added: Linux Kernel Bug Tracker #111291 http://bugzilla.kernel.org/show_bug.cgi?id=111291 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=111291 Importance: Unknown Status: Unknown -- 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/1628238 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: [5.525445] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [5.525452] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [5.525456] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7 Uname: Linux 4.8.0-17-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2084 F...m pulseaudio /dev/snd/controlC0: caravena 2084 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 27 15:21:42 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (429 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-lowlatency N/A linux-backports-modules-4.8.0-17-lowlatency N/A linux-firmware 1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1628238/+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 1629386] [NEW] Xenial update to v4.4.23 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.4.23 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.4.23 stable release shall be applied: include/linux/kernel.h: change abs() macro so it uses consistent return type Fix build warning in kernel/cpuset.c reiserfs: fix "new_insert_key may be used uninitialized ..." ipv4: panic in leaf_walk_rcu due to stale node pointer ipv6: release dst in ping_v6_sendmsg tcp: cwnd does not increase in TCP YeAH tcp: properly scale window in tcp_v[46]_reqsk_send_ack() crypto: arm64/aes-ctr - fix NULL dereference in tail processing crypto: arm/aes-ctr - fix NULL dereference in tail processing crypto: skcipher - Fix blkcipher walk OOM crash crypto: echainiv - Replace chaining with multiplication ocfs2/dlm: fix race between convert and migration ocfs2: fix start offset to ocfs2_zero_range_for_truncate() kbuild: Do not run modules_install and install in paralel Makefile: revert "Makefile: Document ability to make file.lst and file.S" partially tools: Support relative directory path for 'O=' kbuild: forbid kernel directory to contain spaces and colons Kbuild: disable 'maybe-uninitialized' warning for CONFIG_PROFILE_ALL_BRANCHES gcov: disable -Wmaybe-uninitialized warning Disable "maybe-uninitialized" warning globally Disable "frame-address" warning Makefile: Mute warning for __builtin_return_address(>0) for tracing only net: caif: fix misleading indentation Add braces to avoid "ambiguous ‘else’" compiler warnings am437x-vfpe: fix typo in vpfe_get_app_input_index ath9k: fix misleading indentation iwlegacy: avoid warning about missing braces Staging: iio: adc: fix indent on break statement nouveau: fix nv40_perfctr_next() cleanup regression bonding: Fix bonding crash Revert "af_unix: Fix splice-bind deadlock" af_unix: split 'u->readlock' into two: 'iolock' and 'bindlock' vti: flush x-netns xfrm cache when vti interface is removed net/irda: handle iriap_register_lsap() allocation failure tipc: fix NULL pointer dereference in shutdown() net/mlx5: Added missing check of msg length in verifying its signature net: dsa: bcm_sf2: Fix race condition while unmasking interrupts Revert "phy: IRQ cannot be shared" net: smc91x: fix SMC accesses bridge: re-introduce 'fix parsing of MLDv2 reports' autofs races autofs: use dentry flags to block walks during expire xfs: prevent dropping ioend completions during buftarg wait fsnotify: add a way to stop queueing events on group shutdown fanotify: fix list corruption in fanotify_get_response() fix fault_in_multipages_...() on architectures with no-op access_ok() mtd: maps: sa1100-flash: potential NULL dereference mtd: pmcmsp-flash: Allocating too much in init_msp_flash() power: reset: hisi-reboot: Unmap region obtained by of_iomap fix memory leaks in tracing_buffers_splice_read() tracing: Move mutex to protect against resetting of seq data mm: delete unnecessary and unsafe init_tlb_ubc() can: flexcan: fix resume function nl80211: validate number of probe response CSA counters btrfs: ensure that file descriptor used with subvol ioctls is a dir i2c-eg20t: fix race between i2c init and interrupt enable i2c: qup: skip qup_i2c_suspend if the device is already runtime suspended MIPS: Fix pre-r6 emulation FPU initialisation MIPS: SMP: Fix possibility of deadlock when bringing CPUs online MIPS: vDSO: Fix Malta EVA mapping to vDSO page structs MIPS: Remove compact branch policy Kconfig entries MIPS: Avoid a BUG warning during prctl(PR_SET_FP_MODE, ...) MIPS: Add a missing ".set pop" in an early commit MIPS: paravirt: Fix undefined reference to smp_bootstrap PM / hibernate: Restore processor state before using per-CPU variables PM / hibernate: Fix rtree_next_node() to avoid walking off list ends power_supply: tps65217-charger: fix missing platform_set_drvdata() power: supply: max17042_battery: fix model download bug. qxl: check for kmap failures hostfs: Freeing an ERR_PTR in hostfs_fill_sb_common() Linux 4.4.23 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fi
[Kernel-packages] [Bug 1529077] Re: USB device resets since kernel version 3.13.0-73-generic #116-Ubuntu
** Tags removed: verification-needed-precise verification-needed-utopic ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1529077 Title: USB device resets since kernel version 3.13.0-73-generic #116-Ubuntu Status in linux package in Ubuntu: Triaged Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux-lts-utopic source package in Vivid: Invalid Bug description: I am using Ubuntu 14.04 with Gnome desktop. When running "goobox" (a cd-player application) the application hangs for about 30 seconds before being initialized. During this one core of the cpu is running at 100% utilization. The following lines appear then in the syslog: Dec 24 13:14:27 computer4 kernel: [ 1386.238349] usb 3-1: reset high-speed USB device number 2 using xhci_hcd Dec 24 13:14:27 computer4 kernel: [ 1386.293951] xhci_hcd :03:00.0: xHCI xhci_drop_endpoint called with disabled ep 880036272600 Dec 24 13:14:27 computer4 kernel: [ 1386.293955] xhci_hcd :03:00.0: xHCI xhci_drop_endpoint called with disabled ep 880036272640 The CD drive is a external USB one connected to a USB 3.0 port: Bus 003 Device 002: ID 0e8d:1806 MediaTek Inc. Samsung SE-208AB Slim Portable DVD Writer This behaviour appeared with the kernel version 3.13.0-73-generic #116-Ubuntu. Running "goobox" on the same system with kernel 3.13.0-71 does not exhibit this behaviour. Using the newest available kernel 3.13.0-74 the problem persists. Kernel, goobox and the other software are installed from official Ubuntu packages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-73-generic 3.13.0-73.116 ProcVersionSignature: Ubuntu 3.13.0-73.116-generic 3.13.11-ckt30 Uname: Linux 3.13.0-73-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: markus 2224 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 24 13:08:36 2015 HibernationDevice: RESUME=UUID=e711920c-5aab-410e-b993-bb341ddfa987 InstallationDate: Installed on 2014-12-13 (376 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B06211 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-73-generic root=UUID=a501b8b5-7f50-4131-ad2e-cc401009acbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-73-generic N/A linux-backports-modules-3.13.0-73-generic N/A linux-firmware 1.127.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: EB062IMS V1.4 dmi.board.name: MS-B0621 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 100 dmi.chassis.type: 13 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrEB062IMSV1.4:bd08/25/2014:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B06211:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-B0621:rvr100:cvnMICRO-STARINTERNATIONALCO.,LTD:ct13:cvr: dmi.product.name: MS-B06211 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529077/+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 1613295] Re: AES-XTS poor performance in Ubuntu 16.04
** 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/1613295 Title: AES-XTS poor performance in Ubuntu 16.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: == Comment: #0 - Paulo Flabiano Smorigo - 2016-07-21 09:57:49 == ---Problem Description--- Pre-sales customer observed slow performance of XTS using our system, multiple times slower then Haswell. We work to support it on VMX and managed to increase the performance by 20 times. ---uname output--- N/A ---Additional Hardware Info--- N/A Machine Type = P8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- N/A Contact Information = Paulo Flabiano Smorigo Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Paulo Flabiano Smorigo : -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #1 - Paulo Flabiano Smorigo - 2016-07-21 10:02:19 == The necessary patches: http://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=11c6e16ee13ab68b8ff04c17ab41611a4fcc5c81 http://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=c07f5d3da643329f38ff7c2ef2252723453dd9c4 http://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=16dee78005be9908197c707393a3b6a61a14b4fb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613295/+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 994931] Re: Altering use_tempaddr drops all IPv6 addresses
** Tags removed: verification-needed-precise ** Tags added: verification-done-precise -- 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/994931 Title: Altering use_tempaddr drops all IPv6 addresses Status in Linux: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Invalid Bug description: $ uname -a Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 UTC 2012 i686 i686 i386 GNU/Linux $ sysctl net.ipv6.conf.eth2.use_tempaddr net.ipv6.conf.eth2.use_tempaddr = 2 # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04) # Add a static IPv6 address: $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2 # Verify that it has been set up, and that a temporary address and a SLAAC address also exist: $ ip -6 addr list dev eth2 4: eth2: mtu 1500 qlen 1000 inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary dynamic valid_lft 86393sec preferred_lft 14393sec inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic valid_lft 86393sec preferred_lft 14393sec inet6 2001:470:9321:f003::1122/64 scope global valid_lft forever preferred_lft forever inet6 fe80::6c97:24ff:fe3f:263b/64 scope link valid_lft forever preferred_lft forever # Disable RFC 4941 temporary addresses: $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0 net.ipv6.conf.eth2.use_tempaddr = 0 $ ip -6 addr list dev eth2 4: eth2: mtu 1500 qlen 1000 inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative valid_lft forever preferred_lft forever I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed, including statically-configured and non-temporary SLAAC-configured addresses. (The link-local address reappears quickly but the 'tentative' flag indicates that it has been newly re-added. The SLAAC address reappears after a slightly longer interval as the kernel continues to undergo SLAAC, but the static address is gone forever unless manually reinstated.) The same happens if use_tempaddr is changed from 0 back to 2. The expected outcome is that only temporary addresses are affected by a change to use_tempaddr. --- AcpiTables: AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 May 5 03:53 seq crw-rw---T 1 root audio 116, 33 May 5 03:53 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: DistroRelease: Ubuntu 12.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro console=hvc0 ProcModules: lp 17455 0 - Live 0x parport 40930 1 lp, Live 0x xenfs 17877 1 - Live 0x ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: Error: [Errno 2] No such file or directory Tags: precise Uname: Linux 3.2.0-24-generic-pae i686 UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/994931/+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 1627730] Re: Xenial update to v4.4.22 stable release
** Changed in: linux (Ubuntu Xenial)
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/1627730
Title:
Xenial update to v4.4.22 stable release
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The v4.4.22 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches from the v4.4.22 stable release shall be
applied:
ext4: use __GFP_NOFAIL in ext4_free_blocks()
fscrypto: add authorization check for setting encryption policy
clocksource/drivers/sun4i: Clear interrupts after stopping timer in probe
function
MIPS: KVM: Check for pfn noslot case
fscrypto: require write access to mount to set encryption policy
lightnvm: put bio before return
powerpc/tm: do not use r13 for tabort_syscall
powerpc/mm: Don't alias user region to other regions below PAGE_OFFSET
kernfs: don't depend on d_find_any_alias() when generating notifications
pNFS: The client must not do I/O to the DS if it's lease has expired
NFSv4.x: Fix a refcount leak in nfs_callback_up_net
nfsd: Close race between nfsd4_release_lockowner and nfsd4_lock
pNFS: Ensure LAYOUTGET and LAYOUTRETURN are properly serialised
NFSv4.1: Fix the CREATE_SESSION slot number accounting
kexec: fix double-free when failing to relocate the purgatory
mm: introduce get_task_exe_file
audit: fix exe_file access in audit_exe_compare
dm flakey: fix reads to be issued if drop_writes configured
IB/uverbs: Fix race between uverbs_close and remove_one
ARC: mm: fix build breakage with STRICT_MM_TYPECHECKS
x86/paravirt: Do not trace _paravirt_ident_*() functions
x86/AMD: Apply erratum 665 on machines without a BIOS fix
kvm-arm: Unmap shadow pagetables properly
iio: accel: kxsd9: Fix raw read return
iio: proximity: as3935: set up buffer timestamps for non-zero values
iio: adc: rockchip_saradc: reset saradc controller before programming it
iio: adc: ti_am335x_adc: Protect FIFO1 from concurrent access
iio: adc: ti_am335x_adc: Increase timeout value waiting for ADC sample
iio: ad799x: Fix buffered capture for ad7991/ad7995/ad7999
iio: adc: at91: unbreak channel adc channel 3
iio: accel: bmc150: reset chip at init time
iio: fix pressure data output unit in hid-sensor-attributes
iio: accel: kxsd9: Fix scaling bug
iio:core: fix IIO_VAL_FRACTIONAL sign handling
iio: ensure ret is initialized to zero before entering do loop
serial: 8250_mid: fix divide error bug if baud rate is 0
serial: 8250: added acces i/o products quad and octal serial cards
USB: serial: simple: add support for another Infineon flashloader
usb: renesas_usbhs: fix clearing the {BRDY,BEMP}STS condition
usb: chipidea: udc: fix NULL ptr dereference in isr_setup_status_phase
ARM: dts: STiH410: Handle interconnect clock required by EHCI/OHCI (USB)
USB: change bInterval default to 10 ms
net: thunderx: Fix OOPs with ethtool --register-dump
cpuset: make sure new tasks conform to the current config of the cpuset
ARM: AM43XX: hwmod: Fix RSTST register offset for pruss
ARM: imx6: add missing BM_CLPCR_BYP_MMDC_CH0_LPM_HS setting for imx6ul
ARM: imx6: add missing BM_CLPCR_BYPASS_PMIC_READY setting for imx6sx
ARM: kirkwood: ib62x0: fix size of u-boot environment partition
ARM: OMAP3: hwmod data: Add sysc information for DSI
ARM: dts: imx6qdl: Fix SPDIF regression
ARM: dts: overo: fix gpmc nand cs0 range
ARM: dts: overo: fix gpmc nand on boards with ethernet
ARM: dts: STiH407-family: Provide interconnect clock for consumption in ST
SDHCI
bus: arm-ccn: Fix PMU handling of MN
bus: arm-ccn: Do not attempt to configure XPs for cycle counter
bus: arm-ccn: Fix XP watchpoint settings bitmask
dm log writes: fix check of kthread_run() return value
dm log writes: move IO accounting earlier to fix error path
dm crypt: fix error with too large bios
pinctrl: pistachio: fix mfio pll_lock pinmux
pinctrl: sunxi: fix uart1 CTS/RTS pins at PG on A23/A33
arm64: spinlocks: implement smp_mb__before_spinlock() as smp_mb()
crypto: cryptd - initialize child shash_desc on import
Btrfs: remove root_log_ctx from ctx list before btrfs_sync_log returns
fuse: direct-io: don't dirty ITER_BVEC pages
xhci: fix null pointer dereference in stop command timeout function
md-cluster: make md-cluster also can work when compiled into
[Kernel-packages] [Bug 1571020] Re: CVE-2016-3961
** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1571020 Title: CVE-2016-3961 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta sou
[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
@Chris - please give the kernel below a try, I think it will fix your issue. Let me know your results. Thanks! http://people.canonical.com/~sforshee/lp1629204/ ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+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 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)
** Tags removed: verification-failed-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620317 Title: ISST-LTE:pNV: system ben is hung during ST (nvme) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: On when we are running I/O intensive tasks and CPU addition/removal, the block may hang stalling the entire machine. The backtrace below is one of the symptoms: [12747.49] ---[ end trace b4d8d720952460b5 ]--- [12747.126885] Trying to free IRQ 357 from IRQ context! [12747.146930] [ cut here ] [12747.166674] WARNING: at /build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438 [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW OEL 4.4.0-21-generic #37-Ubuntu [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: c00f1fb6c000 [12747.404848] NIP: c0131888 LR: c0131884 CTR: 300303f0 [12747.808333] REGS: c00f1fb6e550 TRAP: 0700 Tainted: GW OEL (4.4.0-21-generic) [12747.867658] MSR: 900100029033 CR: 2802 XER: 2000 [12747.884783] CFAR: c0aea8f4 SOFTE: 1 GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da GPR08: 0007 c0f8b27c 000f2948 90011003 GPR12: 2200 c7b6f800 c00f2a40a938 0100 GPR16: c00f1148 3a98 GPR20: d9521008 d95146a0 f000 GPR24: c4a19ef0 0003 007d GPR28: 0165 c00eefeb1800 c00eef830600 0165 [12748.243270] NIP [c0131888] __free_irq+0x238/0x370 [12748.254089] LR [c0131884] __free_irq+0x234/0x370 [12748.269738] Call Trace: [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 (unreliable) [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0 [12748.304594] [c00f1fb6e890] [d9514528] nvme_suspend_queue+0xc8/0x150 [nvme] [12748.333825] [c00f1fb6e8c0] [d951681c] nvme_dev_disable+0x3fc/0x400 [nvme] [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 [nvme] [12748.357136] [c00f1fb6ea60] [c0548a34] blk_mq_rq_timed_out+0x64/0x110 [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170 [12748.399292] [c00f1fb6eb40] [c054d4e8] blk_mq_queue_tag_busy_iter+0x78/0x110 [12748.402665] [c00f1fb6eb90] [c0547358] blk_mq_rq_timer+0x48/0x140 [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0 [12748.468126] [c00f1fb6ec60] [c014a5fc] run_timer_softirq+0x31c/0x3f0 [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0 [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100 [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0 [12748.516377] [c00f1fb6ee70] [c0002714] decrementer_common+0x114/0x180 [12748.547282] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90 [12748.547282] LR = arch_local_irq_restore+0x74/0x90 [12748.574141] [c00f1fb6f160] [0001] 0x1 (unreliable) [12748.592405] [c00f1fb6f180] [c0aedc3c] dump_stack+0xd0/0xf0 [12748.596461] [c00f1fb6f1c0] [c01006fc] dequeue_task_idle+0x5c/0x90 [12748.611532] [c00f1fb6f230] [c00f6080] deactivate_task+0xc0/0x130 [12748.627685] [c00f1fb6f270] [c0adcb10] __schedule+0x440/0x990 [12748.654416] [c00f1fb6f300] [c0add0a8] schedule+0x48/0xc0 [12748.670558] [c00f1fb6f330] [c0ae1474] schedule_timeout+0x274/0x350 [12748.673485] [c00f1fb6f420] [c0ade23c] wait_for_common+0xec/0x240 [12748.
[Kernel-packages] [Bug 1627670] Re: 4.4.0-40.60 fails to boot
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) 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/1627670 Title: 4.4.0-40.60 fails to boot Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: I've just tried both -39 and -40 in xenial-proposed, and both fail to boot on my laptop (dropping to busybox - see the attached screenshot). This is a regression over -38, which works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chr1s 2537 F pulseaudio /dev/snd/controlC1: chr1s 2537 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 26 10:42:45 2016 HibernationDevice: RESUME=UUID=934c1be9-b0ee-4b9d-9508-7bfb0af474c9 InstallationDate: Installed on 2016-03-09 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. Precision 7510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=aa26703d-fe98-42ad-927a-31369b873d93 ro noprompt persistent quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.05.04 dmi.board.name: 0692Y5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.05.04:bd05/27/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0692Y5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627670/+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 1625177] Re: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial
** Description changed: + SRU: + + Problem: during installation, before configuring the network interfaces, + netconf puts down all the network links and cpsw gets suspended - later + on the PM code kicks and tries to access the same hardware generating an + oops + + Fix: apply the patches present in: + + git://git.launchpad.net/~p-pisati/ubuntu/+source/linux + x-master_lp1625177 + + and recompile. + + How to reproduce: try to install an image using the above patched kernel + + + trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ ** Description changed: SRU: Problem: during installation, before configuring the network interfaces, netconf puts down all the network links and cpsw gets suspended - later on the PM code kicks and tries to access the same hardware generating an oops Fix: apply the patches present in: git://git.launchpad.net/~p-pisati/ubuntu/+source/linux x-master_lp1625177 and recompile. - How to reproduce: try to install an image using the above patched kernel + How to reproduce: try to install an ubuntu-core image using the above + patched kernel trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ ** Description changed: SRU: Problem: during installation, before configuring the network interfaces, netconf puts down all the network links and cpsw gets suspended - later - on the PM code kicks and tries to access the same hardware generating an - oops + on the PM code kicks and tries to access the suspended hardware + generating an oops Fix: apply the patches present in: git://git.launchpad.net/~p-pisati/ubuntu/+source/linux x-master_lp1625177 and recompile. How to reproduce: try to install an ubuntu-core image using the above patched kernel trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ -- 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/1625177 Title: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial Status in linux package in Ubuntu: Confirmed Bug description: SRU: Problem: during installation, before configuring the network interfaces, netconf puts down all the network links and cpsw gets suspended - later on the PM code kicks and tries to access the suspended hardware generating an oops Fix: apply the patches present in: git://git.launchpad.net/~p-pisati/ubuntu/+source/linux x-master_lp1625177 and recompile. How to reproduce: try to install an ubuntu-core image using the above patched kernel trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625177/+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 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 EDT--- Debian kernel package with genwqe-bad-page.patch applied. ** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/bugs/1559194/+attachment/4751793/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pac
[Kernel-packages] [Bug 1525390] Re: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A
The save messages on my old desktops: $ dmesg | grep -i error [2.508824] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=9 end=3362197174) time 9 us, min 1017, max 1023, scanline start 1027, end 1023 $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) $ uname -a Linux q35 4.8.0-994-generic #20160939 SMP Fri Sep 30 04:11:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux xserver-xorg-video-intel: 2.99.917+git20160325-1ubuntu1.1 -- 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/1525390 Title: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A Status in linux package in Ubuntu: Confirmed Bug description: Dell 3552 Inspiron laptop, bought with Ubuntu 14.04LTS upgraded, to 15.10. Every few minutes the following appears in the syslog: [ 6355.488381] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=1171 end=1172) Does not seem to be related to any specific user activity, though I note the Chrome 47 displays many graphical artifacts in images. Additionally, the below stack trace often appears: [ 1365.284232] perf interrupt took too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [ 1599.998487] [ cut here ] [ 1599.998536] WARNING: CPU: 0 PID: 2333 at /build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11102 intel_check_page_flip+0xfc/0x110 [i915]() [ 1599.998539] Kicking stuck page flip: queued at 94224, now 94229 [ 1599.998541] Modules linked in: ctr ccm ip6table_filter ip6_tables iptable_filter ip_tables x_tables pci_stub vboxpci(OE) vboxnetadp(OE) rfcomm vboxnetflt(OE) vboxdrv(OE) msr bnep binfmt_misc rtsx_usb_ms memstick snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic btusb uvcvideo dell_wmi btrtl snd_hda_intel sparse_keymap btbcm videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec videobuf2_core bluetooth v4l2_common snd_hda_core snd_hwdep arc4 videodev media snd_pcm dell_laptop dcdbas nls_iso8859_1 rtl8723be snd_seq_midi snd_seq_midi_event intel_rapl snd_rawmidi dell_smm_hwmon btcoexist rtl8723_common intel_powerclamp rtl_pci coretemp rtlwifi kvm_intel mac80211 kvm punit_atom_debug cfg80211 snd_seq input_leds joydev serio_raw snd_seq_device snd_timer lpc_ich snd mei_txe mei [ 1599.998609] shpchp soundcore iosf_mbi i2c_designware_platform mac_hid i2c_designware_core dell_rbtn synaptics_i2c parport_pc ppdev lp parport autofs4 jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_usb_sdmmc rtsx_usb crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i915 cryptd psmouse i2c_algo_bit drm_kms_helper drm ahci libahci wmi sdhci_acpi video sdhci pinctrl_cherryview [ 1599.998649] CPU: 0 PID: 2333 Comm: Chrome_IOThread Tainted: G OE 4.2.0-19-generic #23-Ubuntu [ 1599.998651] Hardware name: Dell Inc. Inspiron 15-3552/0CP33T, BIOS 3.0.3 08/26/2015 [ 1599.998654] 24a8568b 88017fc03ce8 817e93f9 [ 1599.998659] 88017fc03d40 88017fc03d28 8107b3d6 [ 1599.998663] 88017fc03d58 880035904800 8800e000 8800359049a8 [ 1599.998668] Call Trace: [ 1599.998670][] dump_stack+0x45/0x57 [ 1599.998684] [] warn_slowpath_common+0x86/0xc0 [ 1599.998687] [] warn_slowpath_fmt+0x55/0x70 [ 1599.998714] [] intel_check_page_flip+0xfc/0x110 [i915] [ 1599.998736] [] valleyview_pipestat_irq_handler+0x1f6/0x200 [i915] [ 1599.998759] [] cherryview_irq_handler+0x63/0x110 [i915] [ 1599.998765] [] handle_irq_event_percpu+0x74/0x180 [ 1599.998768] [] handle_irq_event+0x49/0x70 [ 1599.998772] [] handle_edge_irq+0x81/0x150 [ 1599.998777] [] handle_irq+0x25/0x40 [ 1599.998781] [] do_IRQ+0x4f/0xe0 [ 1599.998785] [] common_interrupt+0x6b/0x6b [ 1599.998786] [ 1599.998789] ---[ end trace c4f14dcdc80fdcfe ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Dec 11 21:17:25 2015 DistUpgraded: 2015-10-29 20:07:04,539 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.10, 4.2.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b1] (rev
[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 EDT--- Debian kernel package with genwqe-bad-page.patch applied. ** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/bugs/1559194/+attachment/4751777/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pac
[Kernel-packages] [Bug 1628968] Re: powerpc 4.8.0-17 fails to boot on PowerMac G5
We've been carrying a revert (Revert "powerpc: Simplify module TOC handling") since 4.6 because of FTBS. It is a possible candidate for this symbol resolution issue. Please try a test kernel from http://people.canonical.com/~rtg/powerpc-lp1628968/ which has dropped this revert. -- 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/1628968 Title: powerpc 4.8.0-17 fails to boot on PowerMac G5 Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: Not much else to say. The system fails to complete booting, it gets stuck somewhere before network comes up; with errors in syslog about missing symbols for some modules (see http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21: Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release (err 0) Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol cache_dir_open (err 0) Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 16.405448] shpchp: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 16.684111] ata_generic: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 16.826081] rack_meter: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 16.953962] i2c_algo_bit: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 16.977975] pps_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.010110] uio: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.022857] soundcore: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.034422] firewire_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.049942] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.070474] uio: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.085972] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.102451] windfarm_core: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.118814] uio: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.813073] hid: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 17.820183] hid: Unknown symbol mcount (err 0) Sep 28 12:49:55 fujin kernel: [ 19.022406] bluetooth: Unknown symbol mcount (err 0) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: powerpc AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883 InstallationDate: Installed on 2016-09-28 (1 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc (20160420.1) IwConfig: lono wireless extensions. enP1p5s4f1 no wireless extensions. enP1p5s4f0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 003: ID 05ac:8207 Apple, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet splash verbose Pro
[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
Hello IBM - is this patch going upstream ? It is not currently in a consumable form, i.e., no provenance. ** Changed in: linux (Ubuntu Xenial) Assignee: Andy Whitcroft (apw) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Yakkety) Assignee: Andy Whitcroft (apw) => Tim Gardner (timg-tpi) -- 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/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubs
[Kernel-packages] [Bug 1628187] Re: vNIC driver missing in 4.8 kernel package
Watch for Ubuntu-4.8.0-19.21 which should get promoted to proposed by Monday. -- 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/1628187 Title: vNIC driver missing in 4.8 kernel package Status in linux package in Ubuntu: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Ping Tian Han - 2016-09-22 01:20:10 == ---Problem Description--- There is on "ibmvnic" in 4.8.0-14-generic package: root@roselp2:~# uname -a Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@roselp2:~# modprobe ibmvnic modprobe: FATAL: Module ibmvnic not found in directory /lib/modules/4.8.0-14-generic root@roselp2:~# so the vNIC device which works well under 4.4 kernel doens't work now. == Comment: #6 - Kevin W. Rudd - 2016-09-27 11:49:32 == From Bug 146781, this is still an issue with 4.8.0-17: --- Have installed lpar using virtual Ether adapter and after installation am not able to find vnic adapters root@miglp2:~# modprobe ibmvnic modprobe: FATAL: Module ibmvnic not found in directory /lib/modules/4.8.0-17-generic root@miglp2:~# root@miglp2:~# ifconfig -a ibmveth2: flags=4163 mtu 1500 inet 10.33.15.21 netmask 255.255.0.0 broadcast 10.33.255.255 inet6 fe80::140f:bbff:fe6b:9502 prefixlen 64 scopeid 0x20 inet6 2002:903:15f:1130:140f:bbff:fe6b:9502 prefixlen 64 scopeid 0x0 inet6 2002:926:3e2:1130:140f:bbff:fe6b:9502 prefixlen 64 scopeid 0x0 ether 16:0f:bb:6b:95:02 txqueuelen 1000 (Ethernet) RX packets 437923 bytes 29797431 (29.7 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 153 bytes 13014 (13.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Local Loopback) RX packets 326 bytes 24184 (24.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 326 bytes 24184 (24.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628187/+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 1359689] Re: cryptsetup password prompt not shown
Workarounds using a text boot works, but is quite ugly. If having multiple encrypted disks each needs to be separately unlocked (plymouth feeds the first password to the following ones). Also the password prompts either not visible or aligned to a very far right which makes it hard to notice when to strart typing your passwords. -- 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/1359689 Title: cryptsetup password prompt not shown Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Triaged Status in plymouth package in Debian: Fix Released Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
@ppisati - if you have a classic deb based filesystem that is Xenial based, add the ppa:ci-train-ppa-service/stable-phone-overlay (update/upgrade), then you can simply apt-get install unity8-desktop-session-mir. Once that is installed, you can toggle between unity8 & unity7 by clicking the ubuntu-logo icon just in the top-right corner of the password entry box on the greeter/lock-screen to your session. here's a doc for any other questions. https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc -- 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/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4
** Description changed: + [Impact] + The zfs utilities scripts shipped with debian and ubuntu such as : * arc_summary.py : Provides a summary of the statistics - https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary + * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) + * dbufstat.py : Print out statistics for all cached dmu buffers - * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) - https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat - - * dbufstat.py : Print out statistics for all cached dmu buffers - https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat should be renamed according to Policy 10.4 : [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts] "When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it." Ideally, this should be fixed and upstreamed to Debian (or to zfslinux upstream) as well. + + [Test Case] + + * Install zfsutils-linux and list file using dpkg -L zfsutils-linux | + egrep "arc|dbufstat" + +/usr/sbin/arc_summary.py +/usr/sbin/arcstat.py +/usr/sbin/dbufstat.py + + [Regression Potential] + + * none expected, this is a trivial change that simply rename the + scripts to remove the extension (.py) with a simple 'mv' before the + dh_install invocation. + + To get this expected result : + + $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf" + /usr/sbin/arc_summary + /usr/sbin/arcstat + /usr/sbin/dbufstat + + [Other Info] + + * Upstream (ZoL) is reluctant to change it at upstream code level. + + * This has been flag by Adam Conrad : + https://bugs.launchpad.net/ubuntu/+source/zfs- + linux/+bug/1574342/comments/19 + + * Debian policy : https://www.debian.org/doc/debian-policy/ch- + files.html#s-scripts ** Description changed: [Impact] The zfs utilities scripts shipped with debian and ubuntu such as : - * arc_summary.py : Provides a summary of the statistics - * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) - * dbufstat.py : Print out statistics for all cached dmu buffers - + * arc_summary.py : Provides a summary of the statistics + * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) + * dbufstat.py : Print out statistics for all cached dmu buffers should be renamed according to Policy 10.4 : [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts] "When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it." Ideally, this should be fixed and upstreamed to Debian (or to zfslinux upstream) as well. [Test Case] - * Install zfsutils-linux and list file using dpkg -L zfsutils-linux | - egrep "arc|dbufstat" + * Install zfsutils-linux + * List files -/usr/sbin/arc_summary.py -/usr/sbin/arcstat.py -/usr/sbin/dbufstat.py + $ dpkg -L zfsutils-linux | egrep "arc|dbufstat" + /usr/sbin/arc_summary.py + /usr/sbin/arcstat.py + /usr/sbin/dbufstat.py + [Regression Potential] - * none expected, this is a trivial change that simply rename the + * none expected, this is a trivial change that simply rename the scripts to remove the extension (.py) with a simple 'mv' before the dh_install invocation. To get this expected result : $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf" - /usr/sbin/arc_summary - /usr/sbin/arcstat - /usr/sbin/dbufstat + /usr/sbin/arc_summary + /usr/sbin/arcstat + /usr/sbin/dbufstat [Other Info] - - * Upstream (ZoL) is reluctant to change it at upstream code level. - * This has been flag by Adam Conrad : - https://bugs.launchpad.net/ubuntu/+source/zfs- - linux/+bug/1574342/comments/19 + * Upstream (ZoL) is reluctant to change it at upstream code level. +https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2 - * Debian policy : https://www.debian.org/doc/debian-policy/ch- - files.html#s-scripts + * This has been flag by Adam Conrad + https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19 + + * Debian policy + https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts ** Description changed: [Impact] The zfs utilities scripts shipped with debian and ubuntu such as : * arc_summary.py : Provides a summary of the statistics * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1) * dbufstat.py : Print out statistics for all cached dmu buffers should be renamed according to Policy 10.4 : - - [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts] + https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts "When scripts are installed into a directory in the s
[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
Thanks Chris. I see what the problem is, so I'll look into a fix. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+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 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
Ok, i was able to reproduce this on a classic image by installing the snap core / unity-session 8 snaps and running it under snap-confine - now, how can i recreate the unity-session8 binary locally? I want a vanilla linux elf executable that i can run on a vanilla ubuntu classic image to start digging into it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+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 1585668] Re: Random file corruption when writing large files to hba mounted volume
Rainier, I'm also seeing this issue. Have you ever resolved it? Thanks, Chris -- 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/1585668 Title: Random file corruption when writing large files to hba mounted volume Status in linux package in Ubuntu: Expired Bug description: We have an Ubuntu 16.04 LTS server with a 3Par volume via QLogic HBA. When mounted, writing large files to it repeatedly produces the following errors: [435753.554230] sd 5:0:0:1: [sde] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [435753.554232] sd 5:0:0:1: [sde] tag#10 Sense Key : Illegal Request [current] [435753.554233] sd 5:0:0:1: [sde] tag#10 Add. Sense: Invalid field in cdb [435753.554235] sd 5:0:0:1: [sde] tag#10 CDB: Write same(16) 93 08 00 00 00 00 04 7f ff f7 00 7f ff ff 00 00 [435753.554236] blk_update_request: critical target error, dev sde, sector 75497463 We see similar errors with XFS and EXT4. ZFS seems to work fine though. Here's how to recreate: // create a large file $ sudo dd if=/dev/urandom of=/random_file.bin bs=1048576 count=800 // 3Par volume is /dev/sde $ sudo mkfs.xfs /dev/sde // mount to /test $ sudo mount /dev/sde /test // watch syslog $ tail -f /var/log/syslog & $ sudo cp /random_file.bin /test WORKAROUND: sudo sh -c 'echo 16384 > /sys/block/sde/queue/max_sectors_kb' We made this permanent by adding a udev rule: $ cat /etc/udev/rules.d/61-block-max-sectors.rules ACTION=="add|change", KERNEL=="sd[a-z]", SUBSYSTEM=="block", DRIVERS=="qla2xxx", RUN+="/bin/sh -c '/bin/echo 16384 > /sys/block/%k/queue/max_sectors_kb'" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 24 12:30 seq crw-rw 1 root audio 116, 33 May 24 12:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed May 25 10:18:33 2016 HibernationDevice: RESUME=UUID=8e53840e-3198-4383-ac8b-0a811ed2d0b0 InstallationDate: Installed on 2016-05-19 (5 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=459ae48a-619a-4e7e-8001-bbdf1968a944 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585668/+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
