[Kernel-packages] [Bug 1811255] Re: perf archive missing

[Trent Lloyd]

*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281

** This bug has been marked a duplicate of bug 1823281
   perf-archive is not shipped in the linux-tools package

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

Title:
  perf archive missing

Status in linux package in Ubuntu:
  Expired

Bug description:
  Running perf in 16.04 returns:
  ``
   usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]

   The most commonly used perf commands are:
 annotateRead perf.data (created by perf record) and display 
annotated code
 archive Create archive with object files with build-ids found in 
perf.data file
  ...

  ```

  ```
  perf version 4.15.18
  ```

  However `perf archive` returns:

  ```
  perf: 'archive' is not a perf-command. See 'perf --help'.
  ```

  It appears that the archive script is somehow missing from the
  package.

  Similar reports can be seen here:

   * 
https://stackoverflow.com/questions/42150355/how-do-i-use-a-newer-perf-tool-front-end-with-a-record-from-an-older-perf-versio
   * https://www.spinics.net/lists/linux-perf-users/msg01294.html


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  linux-tools-4.15.0-43-generic:
Installed: 4.15.0-43.46~16.04.1
Candidate: 4.15.0-43.46~16.04.1
Version table:
   *** 4.15.0-43.46~16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811255/+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 2034099] Re: Bridge MTU not applied at first boot, only after netplan apply/networkctl reload

[Trent Lloyd]

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

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

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

Title:
  Bridge MTU not applied at first boot, only after netplan
  apply/networkctl reload

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If you set a Bridge's MTU to a specific value using netplan/networkd
  which is different to the MTU of the interface you add, it does not
  appear to be applied correctly during boot.

  However the MTU switches to the correct value when you re-apply the
  configuration with "netplan apply" (or "systemctl restart systemd-
  networkd"; "networkctl reload")

  
  Additionally:
  - It does apply correctly when you create the bridge for the first time 
(after boot), I did not debug why.
  - When deploying the same configuration with Juju & MAAS it works after first 
boot (likely because juju modifies the netplan config and runs netplan apply) 
but still fails on reboot.

  == Cause ==

  Linux bridges, by default, "auto-tune" the bridge MTU to MIN(mtu) of
  all member ports. This is updated each time an interface is added or
  removed (except with vlan aware mode, which uses MAX(mtu) instead).

  If the user changes the MTU of the bridge explicitly, it disables this
  behaviour since 804b854d374e ("net: bridge: disable bridge MTU auto
  tuning if it was set manually") which landed in v4.17.

  This is the expected behaviour, unfortunately that code has a bug in
  that it only works if the bridge MTU is changed after it was created.
  If the bridge MTU is set during bridge creation by passing IFLA_MTU
  (as systemd-networkd and network-manager do), it does not disable
  auto-tuning. Subsequently when the interface is added to the bridge,
  the MTU is auto-tuned to match.

  So while systemd-networkd is setting this MTU initially, it is almost
  immediately changed by the auto-tuning when the member port is added.
  If you reload, it notices the MTU doesn't match and changes it again.
  This change then triggers the relevant code to disable auto-tuning -
  so it won't change again after that.

  To verify this, you can examine the state of BROPT_MTU_SET_BY_USER
  with this drgn
  script:
https://gist.github.com/lathiat/7a3cace35bd28413822c362f76ad2f1a

  You can also capture the MTU being set at creation with this bpftrace
  script:
https://gist.github.com/lathiat/1624723ceef8d17239ae450f03c8eb3b

  It can also be helpful to set the following in a drop-in override using 
"systemctl edit systemd-networkd":
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  == Use Case ==

  The specific use case that found this bug was wanting to have a VLAN
  with MTU 9000 and the default untagged VLAN interface with MTU 1500.
  For a VLAN sub-interface (e.g. eth0.42) to have MTU 9000 the parent
  interface (eth0) must also have MTU 9000. Even if that's not what you
  actually wanted.

  One way to work around this is to create eth0 and eth0.42 with MTU
  9000 but then create br0 with MTU 1500 containing eth0. Because we are
  intentionally setting the MTU of br0 to a value other than the member
  interfaces the bug is triggered.

  
  However this also happens in other cases and this bug has often not been 
noticed because either

  (a) If the same MTU is desired on the bridge and member ports, setting
  the MTU of the member ports to match result in auto-tuning still
  happening but to the desired value.

  (b) When member ports are created by other tools (e.g. virtualisation
  software such as LXD) they often (but not always) clone the MTU of the
  bridge to the interface before adding it, specifically to avoid this
  behaviour. However not all software clones the bridge MTU before
  adding an interface (so the bridge MTU will get reduced to 1500 when a
  higher value is desired).

  (c) ifupdown specifically sets MTU after creation (using ip link X set
  mtu N), so does not experience this bug, unlike networkd/Network
  Manager which set MTU during creation with IFLA_MTU.

  
  == Test Case ==

  # Notes:
  # - This requires a multi-core VM to reproduce reliably. Single core VMs 
frequently fail to reproduce it. 
  # - Requires a spare interface separate to the primary interface, in the 
exampel we use eth2.
  # - You can take the netplan generated configs from /run/systemd/network and 
use them directly in /etc/systemd/network and apply with "networkctl reload". 
You get the same results.

  # 1. Create simple netplan configuration

  # Ensure that no eth2 configuration exists in the other files, if so, remove 
that.
  grep eth2 /etc/netplan/ -Ri

  cat >> /etc/netplan/60-br0.yaml 

[Kernel-packages] [Bug 2034099] Re: Bridge MTU not applied at first boot, only after netplan apply/networkctl reload

[Trent Lloyd]

Submitted upstream for review:
https://lore.kernel.org/all/20230927075713.1253681-1-trent.ll...@canonical.com/T/#u

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

Title:
  Bridge MTU not applied at first boot, only after netplan
  apply/networkctl reload

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If you set a Bridge's MTU to a specific value using netplan/networkd
  which is different to the MTU of the interface you add, it does not
  appear to be applied correctly during boot.

  However the MTU switches to the correct value when you re-apply the
  configuration with "netplan apply" (or "systemctl restart systemd-
  networkd"; "networkctl reload")

  
  Additionally:
  - It does apply correctly when you create the bridge for the first time 
(after boot), I did not debug why.
  - When deploying the same configuration with Juju & MAAS it works after first 
boot (likely because juju modifies the netplan config and runs netplan apply) 
but still fails on reboot.

  == Cause ==

  Linux bridges, by default, "auto-tune" the bridge MTU to MIN(mtu) of
  all member ports. This is updated each time an interface is added or
  removed (except with vlan aware mode, which uses MAX(mtu) instead).

  If the user changes the MTU of the bridge explicitly, it disables this
  behaviour since 804b854d374e ("net: bridge: disable bridge MTU auto
  tuning if it was set manually") which landed in v4.17.

  This is the expected behaviour, unfortunately that code has a bug in
  that it only works if the bridge MTU is changed after it was created.
  If the bridge MTU is set during bridge creation by passing IFLA_MTU
  (as systemd-networkd and network-manager do), it does not disable
  auto-tuning. Subsequently when the interface is added to the bridge,
  the MTU is auto-tuned to match.

  So while systemd-networkd is setting this MTU initially, it is almost
  immediately changed by the auto-tuning when the member port is added.
  If you reload, it notices the MTU doesn't match and changes it again.
  This change then triggers the relevant code to disable auto-tuning -
  so it won't change again after that.

  To verify this, you can examine the state of BROPT_MTU_SET_BY_USER
  with this drgn
  script:
https://gist.github.com/lathiat/7a3cace35bd28413822c362f76ad2f1a

  You can also capture the MTU being set at creation with this bpftrace
  script:
https://gist.github.com/lathiat/1624723ceef8d17239ae450f03c8eb3b

  It can also be helpful to set the following in a drop-in override using 
"systemctl edit systemd-networkd":
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  == Use Case ==

  The specific use case that found this bug was wanting to have a VLAN
  with MTU 9000 and the default untagged VLAN interface with MTU 1500.
  For a VLAN sub-interface (e.g. eth0.42) to have MTU 9000 the parent
  interface (eth0) must also have MTU 9000. Even if that's not what you
  actually wanted.

  One way to work around this is to create eth0 and eth0.42 with MTU
  9000 but then create br0 with MTU 1500 containing eth0. Because we are
  intentionally setting the MTU of br0 to a value other than the member
  interfaces the bug is triggered.

  
  However this also happens in other cases and this bug has often not been 
noticed because either

  (a) If the same MTU is desired on the bridge and member ports, setting
  the MTU of the member ports to match result in auto-tuning still
  happening but to the desired value.

  (b) When member ports are created by other tools (e.g. virtualisation
  software such as LXD) they often (but not always) clone the MTU of the
  bridge to the interface before adding it, specifically to avoid this
  behaviour. However not all software clones the bridge MTU before
  adding an interface (so the bridge MTU will get reduced to 1500 when a
  higher value is desired).

  (c) ifupdown specifically sets MTU after creation (using ip link X set
  mtu N), so does not experience this bug, unlike networkd/Network
  Manager which set MTU during creation with IFLA_MTU.

  
  == Test Case ==

  # Notes:
  # - This requires a multi-core VM to reproduce reliably. Single core VMs 
frequently fail to reproduce it. 
  # - Requires a spare interface separate to the primary interface, in the 
exampel we use eth2.
  # - You can take the netplan generated configs from /run/systemd/network and 
use them directly in /etc/systemd/network and apply with "networkctl reload". 
You get the same results.

  # 1. Create simple netplan configuration

  # Ensure that no eth2 configuration exists in the other files, if so, remove 
that.
  grep eth2 /etc/netplan/ -Ri

  cat >> /etc/netplan/60-br0.yaml 

[Kernel-packages] [Bug 2034099] [NEW] Bridge MTU not applied at first boot, only after netplan apply/networkctl reload

[Trent Lloyd]

Public bug reported:

If you set a Bridge's MTU to a specific value using netplan/networkd
which is different to the MTU of the interface you add, it does not
appear to be applied correctly during boot.

However the MTU switches to the correct value when you re-apply the
configuration with "netplan apply" (or "systemctl restart systemd-
networkd"; "networkctl reload")


Additionally:
- It does apply correctly when you create the bridge for the first time (after 
boot), I did not debug why.
- When deploying the same configuration with Juju & MAAS it works after first 
boot (likely because juju modifies the netplan config and runs netplan apply) 
but still fails on reboot.

== Cause ==

Linux bridges, by default, "auto-tune" the bridge MTU to MIN(mtu) of all
member ports. This is updated each time an interface is added or removed
(except with vlan aware mode, which uses MAX(mtu) instead).

If the user changes the MTU of the bridge explicitly, it disables this
behaviour since 804b854d374e ("net: bridge: disable bridge MTU auto
tuning if it was set manually") which landed in v4.17.

This is the expected behaviour, unfortunately that code has a bug in
that it only works if the bridge MTU is changed after it was created. If
the bridge MTU is set during bridge creation by passing IFLA_MTU (as
systemd-networkd and network-manager do), it does not disable auto-
tuning. Subsequently when the interface is added to the bridge, the MTU
is auto-tuned to match.

So while systemd-networkd is setting this MTU initially, it is almost
immediately changed by the auto-tuning when the member port is added. If
you reload, it notices the MTU doesn't match and changes it again. This
change then triggers the relevant code to disable auto-tuning - so it
won't change again after that.

To verify this, you can examine the state of BROPT_MTU_SET_BY_USER with
this drgn
script:
https://gist.github.com/lathiat/7a3cace35bd28413822c362f76ad2f1a

You can also capture the MTU being set at creation with this bpftrace
script:
https://gist.github.com/lathiat/1624723ceef8d17239ae450f03c8eb3b

It can also be helpful to set the following in a drop-in override using 
"systemctl edit systemd-networkd":
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

== Use Case ==

The specific use case that found this bug was wanting to have a VLAN
with MTU 9000 and the default untagged VLAN interface with MTU 1500. For
a VLAN sub-interface (e.g. eth0.42) to have MTU 9000 the parent
interface (eth0) must also have MTU 9000. Even if that's not what you
actually wanted.

One way to work around this is to create eth0 and eth0.42 with MTU 9000
but then create br0 with MTU 1500 containing eth0. Because we are
intentionally setting the MTU of br0 to a value other than the member
interfaces the bug is triggered.


However this also happens in other cases and this bug has often not been 
noticed because either

(a) If the same MTU is desired on the bridge and member ports, setting
the MTU of the member ports to match result in auto-tuning still
happening but to the desired value.

(b) When member ports are created by other tools (e.g. virtualisation
software such as LXD) they often (but not always) clone the MTU of the
bridge to the interface before adding it, specifically to avoid this
behaviour. However not all software clones the bridge MTU before adding
an interface (so the bridge MTU will get reduced to 1500 when a higher
value is desired).

(c) ifupdown specifically sets MTU after creation (using ip link X set
mtu N), so does not experience this bug, unlike networkd/Network Manager
which set MTU during creation with IFLA_MTU.


== Test Case ==

# Notes:
# - This requires a multi-core VM to reproduce reliably. Single core VMs 
frequently fail to reproduce it. 
# - Requires a spare interface separate to the primary interface, in the 
exampel we use eth2.
# - You can take the netplan generated configs from /run/systemd/network and 
use them directly in /etc/systemd/network and apply with "networkctl reload". 
You get the same results.

# 1. Create simple netplan configuration

# Ensure that no eth2 configuration exists in the other files, if so, remove 
that.
grep eth2 /etc/netplan/ -Ri

cat >> /etc/netplan/60-br0.yaml < Confirmed

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Trent Lloyd (lathiat)

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

Title:
  Bridge MTU not applied at first boot, only after netplan
  apply/networkctl reload

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If you set a Bridge's MTU to a specific value using netplan/networkd
  which is different to the MTU of the interface you add, it does not
  appear to be applied correctly during boot.

  However the MTU switches to the correct value when you re-app

[Kernel-packages] [Bug 74069] Re: razer USB mouse isn't recognized after system startup

[Trent Steel]

I have a Razor Viper Ultimate (Model No: rc30-030501) and can confirm I
am having this same issue. On startup the mouse doesn't move the cursor
even though the lights are on, then when I unplug and plug in it works.
It is a wireless mouse but I am using it plugged in on the laptop I am
on. A "normal" USB mouse always works.

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

Title:
  razer USB mouse isn't recognized after system startup

Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.17 package in Ubuntu:
  Invalid

Bug description:
  I got my Razer Copperhead (USB), but there is still a problem with it.
  When I restart my Ubuntu 6.10 PC my Mouse isn't recognized.
  To got the Mouse workin' I must put it Out and In...

  sorry 4 my bad English


  
  Note: the original reporter indicated the bug was in package 'linux-image'; 
however, that package was not published in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/74069/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[trent--]

With 5.19.9000-37-generic, the audio is back on my RX580 DisplayPort
too.

No audio problem with 60Hz refresh rate, but my screen resolution is
2560*1440. The audio speedup issue should be a separate bug report,
anyway.

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  In Progress

Bug description:
  CLARIFICATION: Just to avoid any confusion for those coming to this
  bug report; the "Jammy: invalid" status above does *not* mean that
  this bug doesn't affect jammy -- it does, and the kernel team is aware
  of this. All it reflects is that the fix has to go into the kinetic
  kernel package which will then flow into the kernel-hwe package
  implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[trent--]

Hello, I tried all the kernels in this post and I experience the same
behaviour as Dave :

5.19.0-31 OK
5.19.0-32 OK
5.19.0-35 bad

5.19.9000-34 (tk)  bad
5.19.9001-34 (tk1) bad
5.19.9002-34 (tk2) bad
5.15.9003-68 (tk3) OK

tk_generic_202303131019 = latest vanilla OK
tk_genRevertfdcc4c22b7ab_202303131037OK
tk_20230313113 (5.19.0-35 rev fdcc4c22b) bad

I am experiencing this problem with DisplayPort audio output on a RX580.
I am attaching the output of "sudo lspci -nl" as spci-sf.out


** Attachment added: "lspci-sf.out"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5654248/+files/lspci-sf.out

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  In Progress

Bug description:
  CLARIFICATION: Just to avoid any confusion for those coming to this
  bug report; the "Jammy: invalid" status above does *not* mean that
  this bug doesn't affect jammy -- it does, and the kernel team is aware
  of this. All it reflects is that the fix has to go into the kinetic
  kernel package which will then flow into the kernel-hwe package
  implicitly.

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

[Trent Lloyd]

A bunch of fixes for this card have gone in. I'd make sure you are using
the 5.15 HWE kernel on focal if anyone has issues with this card.

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

Title:
  Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi!

  We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.

  The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" 
network cards.
  When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) 
the network card is working without issues.

  When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) 
the system will only boot when the NIC has not been configured using netplan.
  After configuring (and therefore enabling) the NIC in netplan, the system 
will hang at "Wait for network to be configured".

  After waiting for some time other error messages also are being shown:
  "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 
5.15.0-46-generic"
  Same for task systemd-network and systemd-udevd.

  The NIC is using "ice" kernel driver:
  root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet
  [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - 
version 0.8.1-k

  I suspect there have been changes performed in that particular driver
  between 5.4 and 5.15 release.

  If additional information is required I am happy to provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990156/+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 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Trent Lloyd]

** Description changed:

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
  no traffic flow and produce error messages in both the host and guest
  during network configuration.
  
  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy
  
  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5
  
  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
  
  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES
  
  It was found in these cases that the VM is able to successfully transmit
  packets but never receives any and the RX packet drop counters for the
  VF in "ip link" on the host increase equal to the RX packet count.
  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included in
  the test kernel v5.15.0-41 and did not resolve the issue.
  
  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest
  
  It appears that this ice/iavf driver is quite immature as many
  significant SR-IOV related fixes have landed in each of the recent
  kernel releases and we may need to consider pro-actively backporting
  more fixes.
  
  [ Impact ]
  
  Intel E810 (host: ice) SR-IOV VFs (guest: iavf) fail when a port VLAN is
- assigned by the host and the guest changes the MTU >1500. The guest iavf 
driver
- logs the following error and traffic flow stops: 
+ assigned by the host and the guest changes the MTU >1500. The guest iavf
+ driver logs the following error and traffic flow stops:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
  
- There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be used
- without this patch.
- 
+ There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
+ used without this patch.
  
  [ Fix ]
  
  During queue configuration, VF's max packet size was set to
  IAVF_MAX_RXBUFFER but on ice max frame size was smaller by VLAN_HLEN
  due to making some space for port VLAN as VF is not aware whether it's
  in a port VLAN. This mismatch in sizes caused ice to reject queue
  configuration with ERR_PARAM error. Proper max_mtu is sent from ice PF
  to VF with GET_VF_RESOURCES msg but VF does not look at this.
  
  In iavf change max_frame from IAVF_MAX_RXBUFFER to max_mtu
  received from pf with GET_VF_RESOURCES msg to make vf's
  max_frame_size dependent from pf. Add check if received max_mtu is
  not in eligible range then set it to IAVF_MAX_RXBUFFER.
- 
  
  [ Test Plan ]
  
  1. Create a focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan
  
  Openstack works, as does creating a VM directly with uvtool/libvirt.
  
  The syntax inside  for the port VLAN is 
  
  2. Set an IP on the interface, set it’s link up and verify operation
  
  sudo ip a a 192.168.1.7/24 dev enp7s0
  sudo ip link set up dev enp7s0
  ping 192.168.1.1
  
  3. Set the MTU to 9000
  
  sudo ip link set mtu 9000 dev enp7s0
  
  4. Test if the interface still works and whether the error was observed:
  iavf :07:00.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
  
- 
  [ Where problems could occur ]
  
  The iavf driver is unified for multiple host drivers including ice and
  i40e.
  
- A companion patch for i40e was also submitted as it did not set the max_mtu
- although the ice driver already did. We should test the fixed iavf driver
- against both i40e (Intel E7xx) and ice (Intel E8xx) cards with and without 
that
- patch.
+ A companion patch for i40e was also submitted as it did not set the
+ max_mtu although the ice driver already did. We should test the fixed iavf
+ driver against both i40e (Intel E7xx) and ice (Intel E8xx) cards with and
+ without that patch on the host kernel.
  
  
https://lore.kernel.org/netdev/20220919223428.572091-4-anthony.l.ngu...@intel.com/
- 
  
  [ Other Info ]
  
  Patch was developed by intel, has been accepted into v6.0-rc7 and already
  released into upstream stable v5.4.215, v5.15.71 and v5.19.12.
  
- Early SRU is requested as the functionality is required now and there is no
- workaround.
+ Early SRU is requested as the functionality is required now and there is
+ no workaround.

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

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

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and 

[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Trent Lloyd]

** Description changed:

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
  no traffic flow and produce error messages in both the host and guest
  during network configuration.
  
  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy
  
  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5
  
  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
  
  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES
  
  It was found in these cases that the VM is able to successfully transmit
  packets but never receives any and the RX packet drop counters for the
  VF in "ip link" on the host increase equal to the RX packet count.
  
+ There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
+ claiming to resolve this error in some cases. It is already included in
+ the test kernel v5.15.0-41 and did not resolve the issue.
  
- There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 
+ The following conditions are required to trigger the bug:
+ - A port VLAN must be assigned by the host
+ - The MTU must be set >1500 by the guest
  
- These Virtual Machines do work with the Mainline v5.19 build on the host
- and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related
- commits that are not currently backported to v5.15 or any upstream
- stable kernel:
+ It appears that this ice/iavf driver is quite immature as many
+ significant SR-IOV related fixes have landed in each of the recent
+ kernel releases and we may need to consider pro-actively backporting
+ more fixes.
  
- 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
- be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]
+ [ Impact ]
  
- Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
- efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]
+ Intel E810 (host: ice) SR-IOV VFs (guest: iavf) fail when a port VLAN is
+ assigned by the host and the guest changes the MTU >1500. The guest iavf 
driver
+ logs the following error and traffic flow stops: 
+ iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
+ 
+ There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be used
+ without this patch.
  
  
- It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.
+ [ Fix ]
+ 
+ During queue configuration, VF's max packet size was set to
+ IAVF_MAX_RXBUFFER but on ice max frame size was smaller by VLAN_HLEN
+ due to making some space for port VLAN as VF is not aware whether it's
+ in a port VLAN. This mismatch in sizes caused ice to reject queue
+ configuration with ERR_PARAM error. Proper max_mtu is sent from ice PF
+ to VF with GET_VF_RESOURCES msg but VF does not look at this.
+ 
+ In iavf change max_frame from IAVF_MAX_RXBUFFER to max_mtu
+ received from pf with GET_VF_RESOURCES msg to make vf's
+ max_frame_size dependent from pf. Add check if received max_mtu is
+ not in eligible range then set it to IAVF_MAX_RXBUFFER.
+ 
+ 
+ [ Test Plan ]
+ 
+ 1. Create a focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
+ vlan
+ 
+ Openstack works, as does creating a VM directly with uvtool/libvirt.
+ 
+ The syntax inside  for the port VLAN is 
+ 
+ 2. Set an IP on the interface, set it’s link up and verify operation
+ 
+ sudo ip a a 192.168.1.7/24 dev enp7s0
+ sudo ip link set up dev enp7s0
+ ping 192.168.1.1
+ 
+ 3. Set the MTU to 9000
+ 
+ sudo ip link set mtu 9000 dev enp7s0
+ 
+ 4. Test if the interface still works and whether the error was observed:
+ iavf :07:00.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
+ 
+ 
+ [ Where problems could occur ]
+ 
+ The iavf driver is unified for multiple host drivers including ice and
+ i40e.
+ 
+ A companion patch for i40e was also submitted as it did not set the max_mtu
+ although the ice driver already did. We should test the fixed iavf driver
+ against both i40e (Intel E7xx) and ice (Intel E8xx) cards with and without 
that
+ patch.
+ 
+ 
https://lore.kernel.org/netdev/20220919223428.572091-4-anthony.l.ngu...@intel.com/
+ 
+ 
+ [ Other Info ]
+ 
+ Patch was developed by intel, has been accepted into v6.0-rc7 and already
+ released into upstream stable v5.4.215, v5.15.71 and v5.19.12.
+ 
+ Early SRU is requested as the functionality is required now and there is no
+ workaround.

[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Trent Lloyd]

For users of i40e, seems this depends on the following host patch where the 
max_mtu from the host PF that is now used was not set on i40e (but was for ice).
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

It's also queued for stable. We may want to pull this at the same time.

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

  These Virtual Machines do work with the Mainline v5.19 build on the
  host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES
  related commits that are not currently backported to v5.15 or any
  upstream stable kernel:

  6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
  be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

  Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
  efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]

  
  It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Trent Lloyd]

The patch has now made it upstream into the v6.0-rc7 release:
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

It has also been pushed to the stable-queue for the upstream 5.4 and 5.15 
kernels:
https://www.spinics.net/lists/stable-commits/msg266383.html
https://www.spinics.net/lists/stable-commits/msg266285.html

A test kernel for Focal 5.4 and 5.15 was also built and tested. It does
resolve the issue as expected.

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

  These Virtual Machines do work with the Mainline v5.19 build on the
  host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES
  related commits that are not currently backported to v5.15 or any
  upstream stable kernel:

  6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
  be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

  Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
  efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]

  
  It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

[Trent Lloyd]

It would be great if you can do the following:
(1) Upload a copy of /etc/netplan

(2) Find out where it's stuck. Preferably generate and attach a kernel
crashdump (https://ubuntu.com/server/docs/kernel-crash-dump) or perhaps
the hung_task_panic=1 kernel option will cause it to print out where
it's stuck if you can capture the full console history?

(3) Test the v5.19.5 Mainline build to see if that works as there have
been a lot of ice driver fixes after 5.15 and would be good to know if
this one is already fixed or not

Details: https://wiki.ubuntu.com/Kernel/MainlineBuilds
Download: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/

Download and install these two files should suffice:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/linux-image-unsigned-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/linux-modules-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb

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

Title:
  Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.

  The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" 
network cards.
  When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) 
the network card is working without issues.

  When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) 
the system will only boot when the NIC has not been configured using netplan.
  After configuring (and therefore enabling) the NIC in netplan, the system 
will hang at "Wait for network to be configured".

  After waiting for some time other error messages also are being shown:
  "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 
5.15.0-46-generic"
  Same for task systemd-network and systemd-udevd.

  The NIC is using "ice" kernel driver:
  root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet
  [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - 
version 0.8.1-k

  I suspect there have been changes performed in that particular driver
  between 5.4 and 5.15 release.

  If additional information is required I am happy to provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990156/+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 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Trent Lloyd]

Updaet: We found that this bug was only triggering when you try to
change the MTU to anything other than 1500. With MTU=1500 the VMs work
fine even with the current 5.15 kernel.

With MTU=1550 or MTU=9000 it fails even with the upstream 5.19 kernel
and these patches. So seems we need to report and work with Intel on
this to develop a new patch. Though probably we still need to backport
these and maybe other ice patches to 5.15

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

  These Virtual Machines do work with the Mainline v5.19 build on the
  host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES
  related commits that are not currently backported to v5.15 or any
  upstream stable kernel:

  6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
  be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

  Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
  efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]

  
  It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1983656] [NEW] SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Trent Lloyd]

Public bug reported:

Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
no traffic flow and produce error messages in both the host and guest
during network configuration.

Environment: Ubuntu OpenStack Focal-Ussuri with OVN
Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

Host Error Messages:
ice :98:00.1: VF 7 failed opcode 6, retval: -5

Guest Error Messages:
iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

In the context of these errors "6" refers to the value of
VIRTCHNL_OP_CONFIG_VSI_QUEUES

It was found in these cases that the VM is able to successfully transmit
packets but never receives any and the RX packet drop counters for the
VF in "ip link" on the host increase equal to the RX packet count.


There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

These Virtual Machines do work with the Mainline v5.19 build on the host
and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related
commits that are not currently backported to v5.15 or any upstream
stable kernel:

6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]


It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Trent Lloyd (lathiat)
 Status: Confirmed


** Tags: sts

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Trent Lloyd (lathiat)

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

** Tags added: sts

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

  These Virtual Machines do work with the Mainline v5.19 build on the
  host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES
  related commits that are not currently backported to v5.15 or any
  upstream stable kernel:

  6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
  be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

  Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
  efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]

  
  It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

[Trent Lloyd]

With regards to the patch here:
https://lists.linuxfoundation.org/pipermail/iommu/2021-October/060115.html

It is mentioned this issue can occur if you are passing through a PCI
device to a virtual machine guest. This patch seems like it never made
it into the kernel. So I am curious if you are using any virtual
machines on this host, and if any of them are mapping PCI devices from
the host in.

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

Title:
  DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 22.04 with kernel 5.15.0.27.30 on an HPE ProLiant
  DL20 Gen9 server. The server has an HPE Smart HBA H240 SATA
  controller.

  Since Ubuntu 22.04, the kernel runs into trouble after a few hours of
  uptime. The problem starts with a few instances of a message such as
  this:

  Apr 26 12:03:37  kernel: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 
already set (to 7bf32003 not 24c563801)
  Apr 26 12:03:37  kernel: [ cut here ]
  Apr 26 12:03:37  kernel: WARNING: CPU: 1 PID: 10171 at 
drivers/iommu/intel/iommu.c:2391 __domain_mapping.cold+0x94/0xcb
  Apr 26 12:03:37  kernel: Modules linked in: tls rpcsec_gss_krb5 
binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT 
nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limi>
  Apr 26 12:03:37  kernel:  drm_kms_helper aesni_intel syscopyarea 
sysfillrect sysimgblt fb_sys_fops xhci_pci cec crypto_simd i2c_i801 rc_core 
cryptd drm xhci_pci_renesas ahci i2c_smbus tg3 hpsa>
  Apr 26 12:03:37  kernel: CPU: 1 PID: 10171 Comm: kworker/u4:0 Not 
tainted 5.15.0-27-generic #28-Ubuntu
  Apr 26 12:03:37  kernel: Hardware name: HP ProLiant DL20 
Gen9/ProLiant DL20 Gen9, BIOS U22 04/01/2021
  Apr 26 12:03:37  kernel: Workqueue: writeback wb_workfn 
(flush-253:2)
  Apr 26 12:03:37  kernel: RIP: 0010:__domain_mapping.cold+0x94/0xcb
  Apr 26 12:03:37  kernel: Code: 27 9d 4c 89 4d b8 4c 89 45 c0 e8 03 
c5 fa ff 8b 05 e7 e6 40 01 4c 8b 45 c0 4c 8b 4d b8 85 c0 74 09 83 e8 01 89 05 
d2 e6 40 01 <0f> 0b e9 7e b2 b1 ff 89 ca 48 83 >
  Apr 26 12:03:37  kernel: RSP: 0018:c077826b2fa0 EFLAGS: 00010202
  Apr 26 12:03:37  kernel: RAX: 0004 RBX: 
9f0042062990 RCX: 
  Apr 26 12:03:37  kernel: RDX:  RSI: 
9f02b3d20980 RDI: 9f02b3d20980
  Apr 26 12:03:37  kernel: RBP: c077826b2ff0 R08: 
00024c563801 R09: 0024c563
  Apr 26 12:03:37  kernel: R10:  R11: 
c01550e0 R12: 000f
  Apr 26 12:03:37  kernel: R13: 0007bf32 R14: 
9f00412f5800 R15: 9f0042062938
  Apr 26 12:03:37  kernel: FS:  () 
GS:9f02b3d0() knlGS:
  Apr 26 12:03:37  kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 26 12:03:37  kernel: CR2: 1530f676a01c CR3: 
00029c210001 CR4: 002706e0
  Apr 26 12:03:37  kernel: Call Trace:
  Apr 26 12:03:37  kernel:  
  Apr 26 12:03:37  kernel:  intel_iommu_map_pages+0xdc/0x120
  Apr 26 12:03:37  kernel:  ? 
__alloc_and_insert_iova_range+0x203/0x240
  Apr 26 12:03:37  kernel:  __iommu_map+0xda/0x270
  Apr 26 12:03:37  kernel:  __iommu_map_sg+0x8e/0x120
  Apr 26 12:03:37  kernel:  iommu_map_sg_atomic+0x14/0x20
  Apr 26 12:03:37  kernel:  iommu_dma_map_sg+0x345/0x4d0
  Apr 26 12:03:37  kernel:  __dma_map_sg_attrs+0x68/0x70
  Apr 26 12:03:37  kernel:  dma_map_sg_attrs+0xe/0x20
  Apr 26 12:03:37  kernel:  scsi_dma_map+0x39/0x50
  Apr 26 12:03:37  kernel:  
hpsa_scsi_ioaccel2_queue_command.constprop.0+0x11e/0x570 [hpsa]
  Apr 26 12:03:37  kernel:  ? __blk_rq_map_sg+0x36/0x160
  Apr 26 12:03:37  kernel:  hpsa_scsi_ioaccel_queue_command+0x82/0xd0 
[hpsa]
  Apr 26 12:03:37  kernel:  hpsa_ioaccel_submit+0x174/0x190 [hpsa]
  Apr 26 12:03:37  kernel:  hpsa_scsi_queue_command+0x19c/0x240 [hpsa]
  Apr 26 12:03:37  kernel:  ? recalibrate_cpu_khz+0x10/0x10
  Apr 26 12:03:37  kernel:  scsi_dispatch_cmd+0x93/0x1f0
  Apr 26 12:03:37  kernel:  scsi_queue_rq+0x2d1/0x690
  Apr 26 12:03:37  kernel:  blk_mq_dispatch_rq_list+0x126/0x600
  Apr 26 12:03:37  kernel:  ? __sbitmap_queue_get+0x1/0x10
  Apr 26 12:03:37  kernel:  __blk_mq_do_dispatch_sched+0xba/0x2d0
  Apr 26 12:03:37  kernel:  
__blk_mq_sched_dispatch_requests+0x104/0x150
  Apr 26 12:03:37  kernel:  blk_mq_sched_dispatch_requests+0x35/0x60
  Apr 26 12:03:37  kernel:  __blk_mq_run_hw_queue+0x34/0xb0
  Apr 26 12:03:37  kernel:  __blk_mq_delay_run_hw_queue+0x162/0x170
  Apr 26 12:03:37  kernel:  blk_mq_run_hw_queue+0x83/0x120
  Apr 26 12:03:37  kernel:  blk_mq_sched_insert_requests+0x69/0xf0
  Apr 26 12:03:37  kernel:  blk_mq_flush_plug_list+0x103/0x1c0
  Apr 26 12:03:37  kernel:  blk_flush_plug_list+0xdd/0x100
  Apr 26 12:03:37  kernel:  blk_mq_submit_bio+0x2bd/0x600
  Apr 26 12:03:37  kernel:  __submit_bio+0x1ea/0x220
  Apr 26 

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Re-installing from scratch should resolve the issue. I suspect in most
cases if you install with the 21.10 installer (even though it has the
old kernel) as long as you install updates during the install this issue
probably won't hit you. It mostly seems to occur after a reboot and it's
loading data back from disk again.

As per some of the other comments you'll have a bit of a hard time
copying data off the old broken install.. you need to work through which
files/folders are corrupt and reboot and then exclude those from the
next rsync.


You could use the 22.04 daily build, it will eventually upgrade into the final 
release. However not usually recommended as there may be bugs or other problems 
in those daily images and/or it's not uncommon for the development release to 
sometimes break during the development cycle. Most of the time it doesn't and 
it usually works most of the time, but it's much more likely than using 21.10.

I'd try a re-install with 21.10 as I described. Obviously you'll need to
backup all of your data from the existing install first.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-raspi source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Confirmed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   

[Kernel-packages] [Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()

[Trent Lloyd]

This looks like a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476

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

Title:
  PANIC at zfs_znode.c:339:zfs_znode_sa_init()

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing a non-deterministic panic in the ZFS code. Last boot, this
  occurred in systemd-udevd, resulting in a failed boot. The boot before
  that, firefox hit the same thing, and this boot it looks like it's hit
  an Evolution component.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  4988 F pulseaudio
   /dev/snd/controlC1:  chris  4988 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 11 11:49:47 2021
  InstallationDate: Installed on 2021-05-13 (28 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware 1.198
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

In a related way say you wanted to recover a system from a boot disk,
and copy all the data off to another disk. If you use a sequential file
copy like from tar/cp in verbose mode and watch it, eventaully it will
hang on the file triggering the issue (watch dmesg/kern.log). Once that
happens, move that file into a directory like /broken which you exclude
from tar/cp, reboot to get back into a working state, then start the
copy again. Basically what I did incrementally to find all the broken
files. Fortunately for me they were mostly inside chrome or electron app
dirs.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

So to be clear this patch revert fixes the issue being caused new, but,
if the issue already happened on your filesystem it will continue to
occur because the exception is reporting corruption on disk. I don't
currently have a good fix for this other than to move the affected files
to a directory you don't use (but it's sometimes tricky to figure out
which files are the cause).

For dkms status you could try check ls -la /proc/$(pidof dkms)/fd to see
what file it opened, or strace it, to try figure out what file it's up
to when it hangs. then move that file or directory out of the way and
then replace them.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Have created a 100% reliable reproducer test case and also determined
the Ubuntu-specific patch 4701-enable-ARC-FILL-LOCKED-flag.patch to fix
Bug #1900889 is likely the cause.

[Test Case]

The important parts are:
- Use encryption
- rsync the zfs git tree
- Use parallel I/O from silversearcher-ag to access it after a reboot. A simple 
"find ." or "find . -exec cat {} > /dev/null \;" does not reproduce the issue.

Reproduction done using a libvirt VM installed from the Ubuntu Impish
daily livecd using a normal ext4 root but with a second 4GB /dev/vdb
disk for zfs later

= Preparation
apt install silversearcher-ag git zfs-dkms zfsutils-linux
echo -n testkey2 > /root/testkey
git clone https://github.com/openzfs/zfs /root/zfs

= Test Execution
zpool create test /dev/vdb
zfs create test/test -o encryption=on -o keyformat=passphrase -o 
keylocation=file:///root/testkey
rsync -va --progress -HAX /root/zfs/ /test/test/zfs/

# If you access the data now it works fine.
reboot

zfs load-key test/test
zfs mount -a
cd /test/test/zfs/
ag DISKS= 

= Test Result
ag hangs, "sudo dmesg" shows an exception

[Analysis]
I rebuilt the zfs-linux 2.0.6-1ubuntu1 package from ppa:colin-king/zfs-impish 
without the Ubuntu-specific patch ubuntu/4701-enable-ARC-FILL-LOCKED-flag.patch 
which fixed Bug #1900889. With this patch disabled the issue does not 
reproduce. Re-enabling the patch it reproduces reliably every time again.

Seems this bug was never sent upstream. No code changes upstream setting the 
flag ARC_FILL_IN_PLACE appear to have been added since that I can see however 
interestingly the code for this ARC_FILL_IN_PLACE handling was added to fix a 
similar sounding issue "Raw receive fix and encrypted objset security fix" 
 in 
https://github.com/openzfs/zfs/commit/69830602de2d836013a91bd42cc8d36bbebb3aae 
. This first shipped in zfs 0.8.0 and the original bug was filed against 0.8.3.

I also have found the same issue as the original Launchpad bug reported 
upstream without any fixes and a lot of discussion (and quite a few duplicates 
linking back to 11679):
https://github.com/openzfs/zfs/issues/11679
https://github.com/openzfs/zfs/issues/12014

Without fully understanding the ZFS code in relation to this flag, the
code at
https://github.com/openzfs/zfs/blob/ce2bdcedf549b2d83ae9df23a3fa0188b33327b7/module/zfs/arc.c#L2026
talks about how this flag is to do with decrypting blocks in the ARC and
doing so 'inplace'. It makes some sense thus that I need encryption to
reproduce it and it works best after a reboot (thus flushing the ARC)
and why I can still read the data in the test case before doing a reboot
when it then fails.

This patch was added in 0.8.4-1ubuntu15 and I first experienced the
issue somewhere between 0.8.4-1ubuntu11 and 0.8.4-1ubuntu16.

So it all adds up and I suggest that this patch should be reverted.

** Bug watch added: github.com/openzfs/zfs/issues #11679
   https://github.com/openzfs/zfs/issues/11679

** Bug watch added: github.com/openzfs/zfs/issues #12014
   https://github.com/openzfs/zfs/issues/12014

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

While trying to setup a reproducer that would excercise chrome or wine
or something I stumbled across the following reproducer that worked
twice in a row in a libvirt VM on my machine today.

The general gist is to
(1) Create a zfs filesystem with "-o encryption=aes-256-gcm -o compression=zstd 
-o atime=off -o keyformat=passphrase"
(2) rsync a copy of the openzfs git tree into it
(3) Reboot
(4) Use silversearcher-ag to search the directory for "DISKS="

Precise steps:
mkdir src
cd src
git clone https://github.com/openzfs/zfs
sudo apt install zfsutils-linux zfs-initramfs
sudo zpool create tank /dev/vdb
sudo zfs create tank/lathiat2 -o encryption=aes-256-gcm -o compression=zstd  -o 
atime=off  -o keyformat=passphrase
rsync -va --progress -HAX /etc/skel /tank/lathiat2/; chown -R lathiat:lathiat 
/tank/lathiat2; rsync -va --progress /home/lathiat/src/ /tank/lathiat2/src/; 
chown -R lathiat:lathiat /tank/lathiat2/src/
# reboot
sudo zfs load-key tank/lathiat2
sudo zfs mount -a
cd /tank/lathiat2/src/zfs/
ag DISKS=

Hit on the exact same crash:
[   61.377929] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, 
SA_HDL_SHARED, >z_sa_hdl)) failed
[   61.377930] PANIC at zfs_znode.c:339:zfs_znode_sa_init()

Now will test this out on the beta 2.0.6 package and also see if the
standard zfs test suite will trigger it or not as a matter of somewhat
curiosity.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? 

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

34 more user reports on the upstream bug of people hitting it on Ubuntu 5.13.0:
https://github.com/openzfs/zfs/issues/10971

I think this needs some priority. It doesn't seem like it's hitting
upstream, for some reason only really hitting on Ubuntu.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

@Colin To be clear this is the same bug I originally hit and opened the
launchpad for, it just doesn't quite match with what most people saw in
the upstream bugs. But it seemed to get fixed anyway for a while, and
has regressed again somehow.

Same exception as from the original description and others reporting:
2021 May 16 21:19:09 laptop VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, 
zp, SA_HDL_SHARED, >z_sa_hdl)) failed

The upstream bug mostly reported slightly different errors though
similar symptoms (files get stuck and can't be accessed).

I also tried to use 'zdb' to check if incorrect file modes were saved,
unfortunately it seems zdb does not work for encrypted datasets, it only
dumps the unencrypted block info and doesn't dump info about filemodes
etc from the encrypted part. So I can't check that.

I've reverted back to 5.11.0-25 for now and it's stable again.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

I traced the call failure. I found the failing code is in
sa.c:1291#sa_build_index()

if (BSWAP_32(sa_hdr_phys->sa_magic) != SA_MAGIC) {

This code prints debug info to /proc/spl/kstat/zfs/dbgmsg, which for me is:
1629791353   sa.c:1293:sa_build_index(): Buffer Header: cb872954 != 
SA_MAGIC:2f505a object=0x45175e

So in this case seems the data is somehow corrupted, since this is
supposed to be a magic value that is always correct and doesn't change.
Not entirely clear how this actually played into the original bug. So it
may be that this is really a different bug. Hrm.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

This has re-appeared for me today after upgrading to 5.13.0-14 on
Impish. Same call stack, and same chrome-based applications (Mattermost
was hit first) affected.

Not currently running DKMS, so:

Today:
5.13.0-14-lowlat Tue Aug 24 10:59   still running (zfs module is 2.0.3-8ubuntu6)

Yesterday:
5.11.0-25-lowlat Mon Aug 23 12:52 - 08:05  (19:13) (zfs module is 
2.0.2-1ubuntu5)

I am a bit confused because the patched line "newmode = zp->z_mode;"
still seems present in the package.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Try the zfs_recover step from Colin's comment above. And then look for
invalid files and try to move them out of the way.

I'm not aware of encrypted pools being specifically implicated (no such
mention in the bug and it doesn't seem like it), having said that, I am
using encryption on the dataset where I was hitting this.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Are you confident that the issue is a new issue? Unfortunately as best I
can tell, the corruption can occur and then will still appear on a fixed
system if it's reading corruption created in the past that unfortunately
scrub doesn't seem to detect.

I've still had no re-occurance here after a few weeks on hirsute with
2.0.2-1ubuntu5 (which includes the
https://github.com/openzfs/zfs/issues/11474 fix) - but from a fresh
install.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

I got another couple of days out of it without issue - so I think it's
likely fixed.

It seems like this issue looks very similar to the following upstream bug, same 
behaviour but a different error, and so I wonder if it was ultimately the same 
bug. Looks like this patch from 2.0.3 was pulled into the package?
https://github.com/openzfs/zfs/issues/11621
https://github.com/openzfs/zfs/issues/11474
https://github.com/openzfs/zfs/pull/11576

Further testing has been hampered as zsys deleted all of my home
datasets entirely (including all snapshots) - tracked in
https://github.com/ubuntu/zsys/issues/196 - using a non-zfs boot until I
finish recovering that - but still seems likely fixed as I was hitting
it most days before.


** Bug watch added: github.com/openzfs/zfs/issues #11621
   https://github.com/openzfs/zfs/issues/11621

** Bug watch added: github.com/openzfs/zfs/issues #11474
   https://github.com/openzfs/zfs/issues/11474

** Bug watch added: github.com/ubuntu/zsys/issues #196
   https://github.com/ubuntu/zsys/issues/196

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

It's worth noting that, as best I can understand, the patches won't fix
an already broken filesystem. You have to remove all of the affected
files, and it's difficult to know exactly what files are affected. I try
to guess based on which show a ??? mark in "ls -la". But sometimes the
"ls" hangs, etc.

I've been running zfs-dkms 2.0.2-1ubuntu2 for 24 hours now and so far so
good.. won't call it conclusive but hoping this has solved it. Though I
am thoroughly confused as to what patch solved it, nothing *seems*
relevant. Which is frustrating.

Will try to update in a few days as to whether it definitely hasn't hit,
most of the time I hit it in a day but wasn't strictly 100%.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

I can confirm 100% this bug is still happening with 2.0.1 from hirsute-
proposed, even with a brand new install, on a different disk (SATA SSD
instead of NVMe Intel Optane 900p SSD), using 2.0.1 inside the installer
and from first boot. I can reproduce it reliably within about 2 hours
just using the desktop with google chrome (after restoring my google
chrome sync, so common set of data and extensions), it always seems to
trigger first on an access from Google Chrome for some reason - that
part is very reliable - but other files can get corrupt or lose access
including git trees and the like.

So I am at a loss to explain the cause given no one outside of Ubuntu
seems to be hitting this. It also, for whatever reason, seems to always
cause my tampermonkey and lastpass extension files to show as corrupt -
but not other extensions - very reliably happens every time.

The only notable change from default is I am using encryption=on with
passphrase for /home/user. I have not tested with encryption off.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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

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

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Using 2.0.1 from hirsute-proposed it seems like I'm still hitting this.
Move and replace .config/google-chrome and seems after using it for a
day, shutdown, boot up, same issue again.

Going to see if I can somehow try to reproduce this on a different disk
or in a VM with xfstests or something.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.

When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kernel built version and it was working OK.
linux-image-5.8.0-36-generic is now released on Hirsute with
0.8.4-1ubuntu16 and so now the out of the box kernel is also broken and
I am regularly having problems with this.

linux-image-5.8.0-29-generic: working
linux-image-5.8.0-36-generic: broken

`
lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo 
/lib/modules/5.8.0-29-generic/kernel/zfs/zfs.ko|grep version
version: 0.8.4-1ubuntu11

lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo 
/lib/modules/5.8.0-36-generic/kernel/zfs/zfs.ko|grep version
version: 0.8.4-1ubuntu16
`

I don't have a good quick/easy reproducer but just using my desktop for
a day or two seems I am likely to hit the issue after a while.

I tried to install the upstream zfs-dkms package for 2.0 to see if I can
bisect the issue on upstream versions but it breaks my boot for some
weird systemd reason I cannot quite figure out as yet.

Looking at the Ubuntu changelog I'd say the fix for
https://bugs.launchpad.net/bugs/1899826 that landed in 0.8.4-1ubuntu13
to backport the 5.9 and 5.10 compataibility patches is a prime suspect
but could also be any other version. I'm going to try and 'bisect'
0.8.4-1ubuntu11 through 0.8.4-1ubuntu16 to figure out which version
actually hit it.

Since the default kernel is now hitting this, there have been 2 more
user reports of the same things in the upstream bug in the past few days
since that kernel landed and I am regularly getting inaccessible files
not just from chrome but even a linux git tree among other things I am
going to raise the priority on this bug to Critical as you lose access
to files so has data loss potential. I have not yet determined if you
can somehow get the data back, so far it's only affected files I can
replace such as cache/git files. It seems like snapshots might be OK
(which would make sense).

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

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 

[Kernel-packages] [Bug 1899826] Re: backport upstream fixes for 5.9 Linux support

[Trent Lloyd]

This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.

When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kernel built version and it was working OK.
linux-image-5.8.0-36-generic is now released on Hirsute with
0.8.4-1ubuntu16 and so now the out of the box kernel is also broken, and
I am regularly having problems with this.

linux-image-5.8.0-29-generic: working
linux-image-5.8.0-36-generic: broken

`
lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo 
/lib/modules/5.8.0-29-generic/kernel/zfs/zfs.ko|grep version
version: 0.8.4-1ubuntu11

lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo 
/lib/modules/5.8.0-36-generic/kernel/zfs/zfs.ko|grep version
version: 0.8.4-1ubuntu16
`

I don't have a good quick/easy reproducer but just using my desktop for
a day or two seems I am likely to hit the issue after a while.

I tried to install the upstream zfs-dkms package for 2.0 to see if I can
bisect the issue on upstream versions but it breaks my boot for some
reason I cannot quite figure out.

Looking at the Ubuntu changelog I'd say the fix for
https://bugs.launchpad.net/bugs/1899826 that landed in 0.8.4-1ubuntu13
to backport the 5.9 and 5.10 compataibility patches is a prime suspect
but could also be any other version. I'm going to try and 'bisect'
0.8.4-1ubuntu11 through 0.8.4-1ubuntu16 to figure out which version
actually hit it.

Since the default kernel is now hitting this, there have been 2 more
user reports of the same things in the upstream bug in the past few days
since that kernel landed, and I am regularly getting inaccessible files
not just from chrome but even a linux git tree among other things I am
going to raise the priority on this bug to Critical as you lose access
to files so has data loss potential. I have not yet determined if you
can somehow get the data back, so far it's only affected files I can
replace such as cache/git files. It seems like snapshots might be OK
(which would make sense).

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

Title:
  backport upstream fixes for 5.9 Linux support

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Groovy:
  Confirmed
Status in zfs-linux source package in Hirsute:
  Fix Released

Bug description:
  == SRU Request Groovy ==

  Upstream zfs supports 5.9. it would be useful to backport these for
  users who want newer kernels.

  == The Fix ==

  Although 6 fixes are required, 2 add changes that get removed by a
  later change, so one can backport this with just the following 4
  changes:

  1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add 
linux/blkdev.h include")
  3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat: 
NR_SLAB_RECLAIMABLE")
  d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn 
replaced with submit_bio")
  4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to 
5.9")

  == Regression potential ==

  The first patch just includes blkdev.h to workaround a build warning,
  so the results in no functional change to the working code.

  The second patch removes legacy arc page free estimation by droping
  the accounting for inactive anonymous pages and reclaimable pages on
  the slab. This change removes a very minor component of the free
  memory calculation and speeds up arc free stats calculations. There is
  a potential that this small change in free page calculation may impact
  systems where memory is more constrained, but the change is so small I
  believe this really is insignificant.

  The third patch is a build time detection of the kernel block
  allocation queue due to API changes, so should not change behaviour
  for current 5.8 kernels, only change behaviour for newer kernels with
  the newer kernel API.  Hence for the released 5.8 groovy kernel the
  code will not be changed, so the regression potential for 5.8 is zero.

  The final patch changes the META build data to allow the driver to
  build on newer kernels, so the risk on this change is effectively
  zero.

  == Testing ==

  Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount 
options)

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

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

[Kernel-packages] [Bug 1899826] Re: backport upstream fixes for 5.9 Linux support

[Trent Lloyd]

Accidentally posted the above comment in the wrong bug, sorry, was meant
for https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -
where I suspect this bug as having caused a regression.

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

Title:
  backport upstream fixes for 5.9 Linux support

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Groovy:
  Confirmed
Status in zfs-linux source package in Hirsute:
  Fix Released

Bug description:
  == SRU Request Groovy ==

  Upstream zfs supports 5.9. it would be useful to backport these for
  users who want newer kernels.

  == The Fix ==

  Although 6 fixes are required, 2 add changes that get removed by a
  later change, so one can backport this with just the following 4
  changes:

  1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add 
linux/blkdev.h include")
  3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat: 
NR_SLAB_RECLAIMABLE")
  d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn 
replaced with submit_bio")
  4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to 
5.9")

  == Regression potential ==

  The first patch just includes blkdev.h to workaround a build warning,
  so the results in no functional change to the working code.

  The second patch removes legacy arc page free estimation by droping
  the accounting for inactive anonymous pages and reclaimable pages on
  the slab. This change removes a very minor component of the free
  memory calculation and speeds up arc free stats calculations. There is
  a potential that this small change in free page calculation may impact
  systems where memory is more constrained, but the change is so small I
  believe this really is insignificant.

  The third patch is a build time detection of the kernel block
  allocation queue due to API changes, so should not change behaviour
  for current 5.8 kernels, only change behaviour for newer kernels with
  the newer kernel API.  Hence for the released 5.8 groovy kernel the
  code will not be changed, so the regression potential for 5.8 is zero.

  The final patch changes the META build data to allow the driver to
  build on newer kernels, so the risk on this change is effectively
  zero.

  == Testing ==

  Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount 
options)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Another user report here:
https://github.com/openzfs/zfs/issues/10971

Curiously I found a 2016(??) report of similar here:
https://bbs.archlinux.org/viewtopic.php?id=217204

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

I hit this problem again today, but now without zfs-dkms. After
upgrading my kernel from initrd.img-5.8.0-29-generic to 5.8.0-36-generic
my Google Chrome Cache directory is broken again, had to rename it and
then reboot to get out of the problem.

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

** Bug watch added: github.com/openzfs/zfs/issues #10971
   https://github.com/openzfs/zfs/issues/10971

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+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 1907262] Re: raid10: discard leads to corrupted file system

[Trent Lloyd]

I can reproduce this on a Google Cloud n1-standard-16 using 2x Local
NVMe disks. Then partition nvme0n1 and nvne0n2 with only an 8GB
partition, then format directly with ext4 (skip LVM).

In this setup each 'check' takes <1 min so speeds up testing
considerably. Example details - seems pre-emptible instance cost for
this is $0.292/hour / $7/day.

gcloud compute instances create raid10-test --project=juju2-157804 \
--zone=us-west1-b \
--machine-type=n1-standard-16 \
--subnet=default \
--network-tier=STANDARD \
--no-restart-on-failure \
--maintenance-policy=TERMINATE \
--preemptible \
--boot-disk-size=32GB \
--boot-disk-type=pd-ssd \
--image=ubuntu-1804-bionic-v20201116 --image-project=ubuntu-os-cloud \
--local-ssd=interface=NVME  --local-ssd=interface=NVME

# apt install linux-image-virtual
# apt-get remove linux-image-gcp linux-image-5.4.0-1029-gcp 
linux-image-unsigned-5.4.0-1029-gcp   --purge
# reboot

sgdisk -n 0:0:+8G /dev/nvme0n1
sgdisk -n 0:0:+8G /dev/nvme0n2
mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2
mkfs.ext4 /dev/md0
mount /dev/md0 /mnt
dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M; sync; rm /mnt/data.raw
echo check >/sys/block/md0/md/sync_action; watch 'grep . /proc/mdstat 
/sys/block/md0/md/mismatch_cnt' # no mismatch
fstrim -v /mnt
echo check >/sys/block/md0/md/sync_action; watch 'grep . /proc/mdstat 
/sys/block/md0/md/mismatch_cnt' # mismatch=256

I ran blktrace /dev/md0 /dev/nvme0n1 /dev/nvme0n2 and will upload the
results I didn't have time to try and understand the results as yet.

Some thoughts
 - It was asserted that the first disk 'appears' fine
 - So I wondered can we reliably repair by asking mdadm to do a 'repair' or 
'resync'
 - It seems that reads are at least sometimes balanced (maybe by PID) to 
different disks since this post.. 
https://www.spinics.net/lists/raid/msg62762.html - unclear if the same 
selection impacts writes (not that it would help performance)
 - So it's unclear we can reliably say only a 'passive mirror' is being 
corrupted, it's possible application reads may or may not be corrupted. More 
testing/understanding of the code required.
 - This area of RAID10 and RAID1 seems quite under-documented, "man md" doesn't 
talk much about how or which disk is used to repair the other if there is a 
mismatch (unlike RAID5 where the parity gives us some assurances as to which 
data is wrong).
 - We should try writes from different PIDs, with known different data, and 
compare the data on both disks with the known data to see if we can knowingly 
get the wrong data on both disks or only one. And try that with 4 disks instead 
of 2.

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

Title:
  raid10: discard leads to corrupted file system

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  Seems to be closely related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578

  After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126
  the fstrim command triggered by fstrim.timer causes a severe number of
  mismatches between two RAID10 component devices.

  This bug affects several machines in our company with different HW
  configurations (All using ECC RAM). Both, NVMe and SATA SSDs are
  affected.

  How to reproduce:
   - Create a RAID10 LVM and filesystem on two SSDs
  mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 
/dev/nvme1n1p2
  pvcreate -ff -y /dev/md0
  vgcreate -f -y VolGroup /dev/md0
  lvcreate -n root-L 100G -ay -y VolGroup
  mkfs.ext4 /dev/VolGroup/root
  mount /dev/VolGroup/root /mnt
   - Write some data, sync and delete it
  dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M
  sync
  rm /mnt/data.raw
   - Check the RAID device
  echo check >/sys/block/md0/md/sync_action
   - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0):
  cat /sys/block/md0/md/mismatch_cnt
   - Trigger the bug
  fstrim /mnt
   - Re-Check the RAID device
  echo check >/sys/block/md0/md/sync_action
   - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in 
the range of N*1):
  cat /sys/block/md0/md/mismatch_cnt

  After investigating this issue on several machines it *seems* that the
  first drive does the trim correctly while the second one goes wild. At
  least the number and severity of errors found by a  USB stick live
  session fsck.ext4 suggests this.

  To perform the single drive evaluation the RAID10 was started using a single 
drive at once:
mdadm --assemble /dev/md127 /dev/nvme0n1p2
mdadm --run /dev/md127
fsck.ext4 -n 

[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system

[Trent Lloyd]

** Attachment added: "blktrace-lp1907262.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+attachment/5442212/+files/blktrace-lp1907262.tar.gz

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

Title:
  raid10: discard leads to corrupted file system

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  Seems to be closely related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578

  After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126
  the fstrim command triggered by fstrim.timer causes a severe number of
  mismatches between two RAID10 component devices.

  This bug affects several machines in our company with different HW
  configurations (All using ECC RAM). Both, NVMe and SATA SSDs are
  affected.

  How to reproduce:
   - Create a RAID10 LVM and filesystem on two SSDs
  mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 
/dev/nvme1n1p2
  pvcreate -ff -y /dev/md0
  vgcreate -f -y VolGroup /dev/md0
  lvcreate -n root-L 100G -ay -y VolGroup
  mkfs.ext4 /dev/VolGroup/root
  mount /dev/VolGroup/root /mnt
   - Write some data, sync and delete it
  dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M
  sync
  rm /mnt/data.raw
   - Check the RAID device
  echo check >/sys/block/md0/md/sync_action
   - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0):
  cat /sys/block/md0/md/mismatch_cnt
   - Trigger the bug
  fstrim /mnt
   - Re-Check the RAID device
  echo check >/sys/block/md0/md/sync_action
   - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in 
the range of N*1):
  cat /sys/block/md0/md/mismatch_cnt

  After investigating this issue on several machines it *seems* that the
  first drive does the trim correctly while the second one goes wild. At
  least the number and severity of errors found by a  USB stick live
  session fsck.ext4 suggests this.

  To perform the single drive evaluation the RAID10 was started using a single 
drive at once:
mdadm --assemble /dev/md127 /dev/nvme0n1p2
mdadm --run /dev/md127
fsck.ext4 -n -f /dev/VolGroup/root

vgchange -a n /dev/VolGroup
mdadm --stop /dev/md127

mdadm --assemble /dev/md127 /dev/nvme1n1p2
mdadm --run /dev/md127
fsck.ext4 -n -f /dev/VolGroup/root

  When starting these fscks without -n, on the first device it seems the
  directory structure is OK while on the second device there is only the
  lost+found folder left.

  Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53
  before) seems to have a quite similar issue.

  Unfortunately the risk/regression assessment in the aforementioned bug
  is not complete: the workaround only mitigates the issues during FS
  creation. This bug on the other hand is triggered by a weekly service
  (fstrim) causing severe file system corruption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Should mention that Chrome itself always showed "waiting for cache" part
of backing up the story around the cache files.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+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 1906476] [NEW] PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Trent Lloyd]

Public bug reported:

Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
panic in the kernel log which was also hanging Disk I/O for all
Chrome/Electron Apps.

I have narrowed down a few important notes:
- It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

- It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
on the same kernel and also on 5.8.18-acso (a custom kernel).

- For whatever reason multiple Chrome/Electron apps were affected,
specifically Discord, Chrome and Mattermost. In all cases they seem (but
I was unable to strace the processes so it was a bit hard ot confirm
100% but by deduction from /proc/PID/fd and the hanging ls) they seem
hung trying to open files in their 'Cache' directory, e.g.  ~/.cache
/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the
issue was going on I could not list that directory either "ls" would
just hang.

- Once I removed zfs-dkms only to revert to the kernel built-in version
it immediately worked without changing anything, removing files, etc.

- It happened over multiple reboots and kernels every time, all my
Chrome apps weren't working but for whatever reason nothing else seemed
affected.

- It would log a series of spl_panic dumps into kern.log that look like this:
Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

I could only find one other google reference to this issue, with 2 other users 
reporting the same error but on 20.04 here:
https://github.com/openzfs/zfs/issues/10971

- I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it
was working on 0.8.4-1ubuntu15 but broken after upgrade to
0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
that.

There were a few originating call stacks but the first one I hit was

Call Trace:
 dump_stack+0x74/0x95
 spl_dumpstack+0x29/0x2b [spl]
 spl_panic+0xd4/0xfc [spl]
 ? sa_cache_constructor+0x27/0x50 [zfs]
 ? _cond_resched+0x19/0x40
 ? mutex_lock+0x12/0x40
 ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
 zfs_znode_sa_init+0xe0/0xf0 [zfs]
 zfs_znode_alloc+0x101/0x700 [zfs]
 ? arc_buf_fill+0x270/0xd30 [zfs]
 ? __cv_init+0x42/0x60 [spl]
 ? dnode_cons+0x28f/0x2a0 [zfs]
 ? _cond_resched+0x19/0x40
 ? _cond_resched+0x19/0x40
 ? mutex_lock+0x12/0x40
 ? aggsum_add+0x153/0x170 [zfs]
 ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
 ? arc_space_consume+0x54/0xe0 [zfs]
 ? dbuf_read+0x4a0/0xb50 [zfs]
 ? _cond_resched+0x19/0x40
 ? mutex_lock+0x12/0x40
 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
 ? _cond_resched+0x19/0x40
 ? mutex_lock+0x12/0x40
 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
 zfs_zget+0x1c3/0x270 [zfs]
 ? dmu_buf_rele+0x3a/0x40 [zfs]
 zfs_dirent_lock+0x349/0x680 [zfs]
 zfs_dirlook+0x90/0x2a0 [zfs]
 ? zfs_zaccess+0x10c/0x480 [zfs]
 zfs_lookup+0x202/0x3b0 [zfs]
 zpl_lookup+0xca/0x1e0 [zfs]
 path_openat+0x6a2/0xfe0
 do_filp_open+0x9b/0x110
 ? __check_object_size+0xdb/0x1b0
 ? __alloc_fd+0x46/0x170
 do_sys_openat2+0x217/0x2d0
 ? do_sys_openat2+0x217/0x2d0
 do_sys_open+0x59/0x80
 __x64_sys_openat+0x20/0x30

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

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series 

[Kernel-packages] [Bug 1891269] Re: perf is not built with python script support

[Trent Lloyd]

Logs are not required for this issue

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

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

Title:
  perf is not built with python script support

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The "perf" tool supports python scripting to process events, this
  support is currently not enabled.

  $ sudo perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.

  The expected behaviour is that the script creates a template python
  file for you to modify to process the events.

  From what I can see enabling this requires a few items
  - We need to Build-Depend on python3-dev
  - We would ship the perf-script-python binary
  - There are various python modules (under tools/perf/scripts/python) needed 
for these to work
  - There are also a number of upstream scripts (e.g. 'net_dropmonitor') we 
could ship, normally you can see those by running 'perf script -l' but we get 
"open(/usr/libexec/perf-core/scripts) failed. Check "PERF_EXEC_PATH" env to set 
scripts dir.". Expected output can be seen by running 
"PERF_EXEC_PATH=LINUX_SOURCE_PATH/tools/perf ./perf script -l"


  While not important to me personally, it also doesn't have support for
  perl that could be fixed in a similar way, in case we want to fix that
  at the same time. It doesn't have as many pre-existing scripts though
  and seems less likely to be as useful compared to the Python version.

  $ sudo perf script -g perl
  Perl scripting not supported.  Install libperl and rebuild perf to enable it.
  For example:
# apt-get install libperl-dev (ubuntu)
# yum install 'perl(ExtUtils::Embed)' (Fedora)
etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891269/+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 1891269] [NEW] perf is not built with python script support

[Trent Lloyd]

Public bug reported:

The "perf" tool supports python scripting to process events, this
support is currently not enabled.

$ sudo perf script -g python
Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
For example:
  # apt-get install python-dev (ubuntu)
  # yum install python-devel (Fedora)
  etc.

The expected behaviour is that the script creates a template python file
for you to modify to process the events.

>From what I can see enabling this requires a few items
- We need to Build-Depend on python3-dev
- We would ship the perf-script-python binary
- There are various python modules (under tools/perf/scripts/python) needed for 
these to work
- There are also a number of upstream scripts (e.g. 'net_dropmonitor') we could 
ship, normally you can see those by running 'perf script -l' but we get 
"open(/usr/libexec/perf-core/scripts) failed. Check "PERF_EXEC_PATH" env to set 
scripts dir.". Expected output can be seen by running 
"PERF_EXEC_PATH=LINUX_SOURCE_PATH/tools/perf ./perf script -l"


While not important to me personally, it also doesn't have support for
perl that could be fixed in a similar way, in case we want to fix that
at the same time. It doesn't have as many pre-existing scripts though
and seems less likely to be as useful compared to the Python version.

$ sudo perf script -g perl
Perl scripting not supported.  Install libperl and rebuild perf to enable it.
For example:
  # apt-get install libperl-dev (ubuntu)
  # yum install 'perl(ExtUtils::Embed)' (Fedora)
  etc.

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


** Tags: seg

** Tags added: seg

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

Title:
  perf is not built with python script support

Status in linux package in Ubuntu:
  New

Bug description:
  The "perf" tool supports python scripting to process events, this
  support is currently not enabled.

  $ sudo perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.

  The expected behaviour is that the script creates a template python
  file for you to modify to process the events.

  From what I can see enabling this requires a few items
  - We need to Build-Depend on python3-dev
  - We would ship the perf-script-python binary
  - There are various python modules (under tools/perf/scripts/python) needed 
for these to work
  - There are also a number of upstream scripts (e.g. 'net_dropmonitor') we 
could ship, normally you can see those by running 'perf script -l' but we get 
"open(/usr/libexec/perf-core/scripts) failed. Check "PERF_EXEC_PATH" env to set 
scripts dir.". Expected output can be seen by running 
"PERF_EXEC_PATH=LINUX_SOURCE_PATH/tools/perf ./perf script -l"


  While not important to me personally, it also doesn't have support for
  perl that could be fixed in a similar way, in case we want to fix that
  at the same time. It doesn't have as many pre-existing scripts though
  and seems less likely to be as useful compared to the Python version.

  $ sudo perf script -g perl
  Perl scripting not supported.  Install libperl and rebuild perf to enable it.
  For example:
# apt-get install libperl-dev (ubuntu)
# yum install 'perl(ExtUtils::Embed)' (Fedora)
etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891269/+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 1750479] Re: 'perf record' does not work

[Trent Lloyd]

*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281

** This bug has been marked a duplicate of bug 1823281
   perf-archive is not shipped in the linux-tools package

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

Title:
  'perf record' does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ perf archive
  perf: 'archive' is not a perf-command. See 'perf --help'.

  $ perf --help

   usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]

   The most commonly used perf commands are:
 annotateRead perf.data (created by perf record) and display 
annotated code
 archive Create archive with object files with build-ids found in 
perf.data file <-
 bench   General framework for benchmark suites
 buildid-cache   Manage build-id cache.
 buildid-listList the buildids in a perf.data file
 c2c Shared Data C2C/HITM Analyzer.
 config  Get and set variables in a configuration file.
 dataData file related processing
 diffRead perf.data files and display the differential profile
 evlist  List the event names in a perf.data file
 ftrace  simple wrapper for kernel's ftrace functionality
 inject  Filter to augment the events stream with additional 
information
 kallsymsSearches running kernel for symbols
 kmemTool to trace/measure kernel memory properties
 kvm Tool to trace/measure kvm guest os
 listList all symbolic event types
 lockAnalyze lock events
 mem Profile memory accesses
 record  Run a command and record its profile into perf.data
 report  Read perf.data (created by perf record) and display the 
profile
 sched   Tool to trace/measure scheduler properties (latencies)
 script  Read perf.data (created by perf record) and display trace 
output
 statRun a command and gather performance counter statistics
 testRuns sanity tests.
 timechart   Tool to visualize total system behavior during a workload
 top System profiling tool.
 probe   Define new dynamic tracepoints
 trace   strace inspired tool

   See 'perf help COMMAND' for more information on a specific command.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-tools-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sbarcomb   2227 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 20:53:27 2018
  HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc
  InstallationDate: Installed on 2017-10-19 (123 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: Alienware Aurora-R4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A11
  dmi.board.name: 07JNH0
  dmi.board.vendor: Alienware
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
  dmi.product.family: 0
  dmi.product.name: Aurora-R4
  dmi.product.version: 00
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750479/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures

[Trent Lloyd]

I have been running into this (curtin 18.1-17-gae48e86f-
0ubuntu1~16.04.1)

I think this commit basically agrees with my thoughts but I just wanted
to share them explicitly in case they are interesting

 (1) If you *unregister* the cache device from the backing device, it
first has to purge all the dirty data back to the backing device. This
may obviously take a while.

 (2) When doing that, I managed to deadlock bcache at least once on
xenial-hwe 4.15 where it was trying to reclaim memory from XFS, which I
assume was trying to write to the bcache.. traceback:
https://pastebin.canonical.com/117528/ - you can't get out of that
without a reboot

 (3) However generally I had good luck simplying "stop"ing the cache
devices (it seems perhaps that is what this bug is designed to do,
switch to stop, instead of unregister?). Specifically though I was
stopping the backing devices, and then later the cache device. It seems
like the current commit is the other way around?

** Tags added: sts

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

Title:
  Tight timeout for bcache removal causes spurious failures

Status in curtin:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've had a number of deployment faults where curtin would report
  Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
  deployment of 30+ nodes. Upon retrying the node would usually deploy
  fine. Experimentally I've set the timeout ridiculously high, and it
  seems I'm getting no faults with this. I'm wondering if the timeout
  for removal is set too tight, or might need to be made configurable.

  --- curtin/util.py~ 2018-05-18 18:40:48.0 +
  +++ curtin/util.py  2018-10-05 09:40:06.807390367 +
  @@ -263,7 +263,7 @@
   return _subp(*args, **kwargs)
   
   
  -def wait_for_removal(path, retries=[1, 3, 5, 7]):
  +def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
   if not path:
   raise ValueError('wait_for_removal: missing path parameter')

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1823281] Re: perf-archive is not shipped in the linux-tools package

[Trent Lloyd]

** Tags added: sts

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

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

Title:
  perf-archive is not shipped in the linux-tools package

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The perf-archive tool is not shipped in the linux-tools package. This
  causes the command 'perf archive' to fail despite there being a
  manpage for it.

  This tool is used to help ship debug info to analyse perf data
  remotely.

  This is a shell script in the kernel tree (tools/perf/perf-archive.sh)
  that gets copied to the file tools/perf/perf-archive at build time.
  When executing 'perf archive' it executes this tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823281/+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 1823281] [NEW] perf-archive is not shipped in the linux-tools package

[Trent Lloyd]

Public bug reported:

The perf-archive tool is not shipped in the linux-tools package. This
causes the command 'perf archive' to fail despite there being a manpage
for it.

This tool is used to help ship debug info to analyse perf data remotely.

This is a shell script in the kernel tree (tools/perf/perf-archive.sh)
that gets copied to the file tools/perf/perf-archive at build time. When
executing 'perf archive' it executes this tool.

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

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

Title:
  perf-archive is not shipped in the linux-tools package

Status in linux package in Ubuntu:
  New

Bug description:
  The perf-archive tool is not shipped in the linux-tools package. This
  causes the command 'perf archive' to fail despite there being a
  manpage for it.

  This tool is used to help ship debug info to analyse perf data
  remotely.

  This is a shell script in the kernel tree (tools/perf/perf-archive.sh)
  that gets copied to the file tools/perf/perf-archive at build time.
  When executing 'perf archive' it executes this tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823281/+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 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

[Trent]

linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64 - no 
good
linux-image-4.13.1-041301-generic_4.13.1-041301.201709100232_amd64   - no 
good
linux-image-4.13.0-041300rc1-generic_4.13.0-041300rc1.201707151931_amd64 - no 
good
linux-image-4.12.14-041214-generic_4.12.14-041214.201709200843_amd64 - good
linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64 - good

the issue appears to have begun with the jump from 4.12.x to 4.13.x

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

[Trent]

i can try.

someone above found the issue was in a 4.13 kernel, i can move forward
from 4.9.x and hopefully we can find where something changed.

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

[Trent]

mainline linux-
image-4.9.162-0409162-generic_4.9.162-0409162.201903051732_amd64.deb is
working fine.

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

[Trent]

I also have this issue after upgrading to 18.04.2 LTS with a host with
an Adaptec 5805 and linux-image-4.15.0-46-generic.

Machine hangs on boots and starts returning
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (0,2,223,0):
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (0,2,224,0):
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (0,2,225,0):
etc

First I upgraded the FW on the controller to 19204 (from 19176) no
improvement

Rolled back to linux-image-4.15.0-45-generic no change.

I tried mainline kernels
linux-image-unsigned-5.0.0-05-generic_5.0.0-05.201903032031_amd64.deb
and
linux-image-unsigned-4.20.14-042014-generic_4.20.14-042014.201903051334_amd64.deb
and issue persisted

But if i roll back to 4.4.0-142-generic no problems.

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

I'll try again someday.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797031/+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 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

I've posted it to the linux-input list a few times but was ignored, so I
tried here.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797031/+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 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

The bug still exists in 4.19rc7.

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797031/+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 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

Forget to answer, this bug has existed on every kernel I've tried, which
is limited to Ubuntu 18.04.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797031/+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 1797031] [NEW] Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

Public bug reported:

I have a Dell 5379 with a touchscreen that always reports 1% battery
with the stylus. This pops up a low battery notification the first time
I use the stylus after booting. The attached patch tells the kernel to
ignore the battery on this particular device, since it appears to not
report information correctly anyway.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  trent  1734 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  9 22:42:47 2018
HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
InstallationDate: Installed on 2018-05-10 (153 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 8087:0025 Intel Corp. 
 Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5379
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-36-generic N/A
 linux-backports-modules-4.15.0-36-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.0
dmi.board.name: 05G60G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5379
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

** Patch added: "Ignore battery on a particular bad behaving touchscreen"
   https://bugs.launchpad.net/bugs/1797031/+attachment/5199355/+files/elan.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/1797031

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:p

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Trent Nelson]

The upstream commit to fix this issues is this one:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/advertising.c?id=1873096352f518d3247f8efb3c2e0aa8804e50ac

I've applied it to Ubuntu's bluez 5.48 and confirmed that it works, as
expected.

Please backport!

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Trent Lloyd]

You can potentially use numactl to launch the process and set a policy
of interleaving allocations between NUMA nodes to avoid these 1 sided
allocations.  Tends to happen with servers that make big allocations
from a single thread during startup, as commonly seen on mysqld servers
and the innodb_buffer_pool for example.

numactl --interleave all /path/to/server/process --argument-1 #etc

Reference:
https://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-architecture/

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  Confirmed
Status in linux-raspi2 source package in Xenial:
  Fix Committed

Bug description:
  After a fix for LP#1647400, a bug that caused freezes under some
  workloads, some users noticed regular OOMs. Those regular OOMs were
  reported under this bug, and fixed after some releases.

  Some of the affected kernels are documented below. In order to check
  your particular kernel, read its changelog and lookup for 1655842 and
  1647400. If it has the fix for 1647400, but not the fix for 1655842,
  then it's affected.

  It's still possible that you notice regressions compared to kernels
  that didn't have the fixes for any of the bugs. However, reverting all
  fixes would cause the freeze bug to come back. So, it's not a possible
  solution moving forward.

  If you see any regressions, in the form of OOMs, mainly, please report
  a new bug. Different workloads may require different solutions, and
  it's possible that further fixes are needed, be them upstream or not.
  The best way to get such fixes applied is reporting that under a new
  bug, one that can be verified, so being able to reproduce the bug
  makes it possible to verify the fixes really fix the identified bug.

  Kernels affected:

  linux  4.4.0-58, 4.4.0-59, 4.4.0-60, 4.4.0-61, 4.4.0-62.
  linux-raspi2  4.4.0-1039 to 4.4.0-1042 and 4.4.0-1044 to 4.4.0-1071

  
  Particular kernels NOT affected by THIS bug:

  linux-aws

  To reiterate, if you find an OOM with an affected kernel, please upgrade.
  If you find an OOM with a non-affected kernel, please report a new bug. We 
want to investigate it and fix it.

  
  ===
  I recently replaced some Xenial servers, and started experiencing "Out of 
memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  

[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Trent Nelson]

Confirmed with 4.10.0-38-generic from zesty-proposed.

Will this be hitting the 4.11.0 branch as well?  I'm actually using the
generic-hwe-16.04-edge package on xenial.

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

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

Title:
  Stranded with ENODEV after mdadm --readonly

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

Bug description:
  == SRU Justification ==
  The bug reporter was trying to turn on the RAID journal.  One of the steps
  is to set the device readonly.  This did not work as planned, or indeed at
  all. After the first --readonly, all requests for the device report
  "No such device or address" until a reboot, though /proc/mdstat says the
  device is still there.

  This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
  which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but
  upstream 4.10 is EOL, so that is the reason for the SRU request.

  == Fix ==
  commit 065e519e71b2c1f41936cce75b46b5ab34adb588
  Author: NeilBrown <ne...@suse.com>
  Date:   Thu Apr 6 11:16:33 2017 +0800

  md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  == Regression Potential ==
  This commit was also cc'd to stable and accepted, so additional upstream 
review
  was performed.

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



  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:

  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1581594] Re: constantly shows wrong temperature (99°C )

[Trent Nelson]

Sorry, I missed Robie's comment yesterday.  Upstream seems
inactive/dead.  Nothing from Lennart on
https://bugs.freedesktop.org/buglist.cgi?product=libatasmart since 2011.
No commits to http://git.0pointer.net/libatasmart.git since 2012.  I
didn't see any indication the development had been picked up anywhere
else.

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress
Status in libatasmart source package in Trusty:
  New
Status in libatasmart source package in Xenial:
  New
Status in libatasmart source package in Yakkety:
  New

Bug description:
  Hello, here's my system info

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

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+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 1581594] Re: constantly shows wrong temperature (99°C )

[Trent Nelson]

I've added support for SSD Life Left via the quirks infrastructure.  The
two devices I have access to, that abuse attribute 231, store the value
differently, so I had to use separate quirks.

The attached patch adds support for Kingston A400 and V300 series SSDs.
Side-effect, correct temperature reporting!

Let me know if the diff needs any tweaks to make it more, Ubuntu-y.


** Patch added: "Quirk for attr 231 SSD Life Left"
   
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1581594/+attachment/4974299/+files/231-ssd-life-left-quirk.diff

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress
Status in libatasmart source package in Trusty:
  New
Status in libatasmart source package in Xenial:
  New
Status in libatasmart source package in Yakkety:
  New

Bug description:
  Hello, here's my system info

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

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

This is resolved now.

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Trent Nelson]

Will this be making its way to a release build?

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

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

Same problem with the new 4.11.0-12 upload, i'm assuming since binutils
is still in -proposed it wasn't built against?

 linux-tools-4.11.0-12 : Depends: binutils (< 2.29) but 2.29-2ubuntu1 is
to be installed

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Trent Nelson]

Confirmed working!

Thanks for the quick response!

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

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

New binutils upload today of 2.29, which conflicts with linux-tools as
it turns out it Depends binutils (>= 2.28), binutils (<< 2.29)

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Trent Nelson]

For reference, https://www.spinics.net/lists/raid/msg57989.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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] CurrentDmesg.txt

[Trent Nelson]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1706243/+attachment/4921157/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] Lspci.txt

[Trent Nelson]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1706243/+attachment/4921159/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] ProcInterrupts.txt

[Trent Nelson]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1706243/+attachment/4921161/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] JournalErrors.txt

[Trent Nelson]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1706243/+attachment/4921158/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] CRDA.txt

[Trent Nelson]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1706243/+attachment/4921156/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] WifiSyslog.txt

[Trent Nelson]

apport information

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

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

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

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] ProcModules.txt

[Trent Nelson]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1706243/+attachment/4921162/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Trent Nelson]

apport information

** Tags added: apport-collected xenial

** Description changed:

  Please backport upstream fix.
  
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
- stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
+  /dev/snd/controlC0:  trent 10668 F pulseaudio
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
+ InstallationDate: Installed on 2014-12-23 (944 days ago)
+ InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
+ IwConfig:
+  p11p1 no wireless extensions.
+  
+  lono wireless extensions.
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
+  Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-26-generic N/A
+  linux-backports-modules-4.10.0-26-generic  N/A
+  linux-firmware 1.157.11
+ RfKill:
+  
+ Tags:  xenial xenial
+ Uname: Linux 4.10.0-26-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
+ UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
+ _MarkForUpload: False
+ dmi.bios.date: 06/16/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 0808
+ dmi.board.asset.tag: Default string
+ dmi.board.name: PRIME B250M-A
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
+ 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/1706243/+attachment/4921155/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restrict

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

[Trent Nelson]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1706243/+attachment/4921164/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] ProcCpuinfoMinimal.txt

[Trent Nelson]

apport information

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

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

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] PulseList.txt

[Trent Nelson]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1706243/+attachment/4921163/+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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1706243/+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 1706243] [NEW] Stranded with ENODEV after mdadm --readonly

[Trent Nelson]

Public bug reported:

Please backport upstream fix.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588

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

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

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  New

Bug description:
  Please backport upstream fix.

  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706243/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

I rebuilt both binutils and linux-4.11.0-11 locally to see if anything
changed.

binutils still has the same libbfd-2.28.90-system.20170718.so soname in
the package

however perf in linux-tools is now linked against the new soname.  So a
rebuild may solve it however I am not entirely sure if this soname
change made sense or not.  I'm not familiar enough with how it works..
Building the current Debian version (2.28-6) renders
libbfd-2.28-system.so

lathiat@ubuntu:/src/z$ ldd ./usr/lib/linux-tools-4.11.0-11/perf|grep bfd
libbfd-2.28.90-system.20170718.so => 
/usr/lib/x86_64-linux-gnu/libbfd-2.28.90-system.20170718.so (0x7fd09cbbf000)

lathiat@ubuntu:~$ ldd /usr/lib/linux-tools-4.11.0-11/perf |grep bfd
libbfd-2.28-system.so => not found

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

** Changed in: binutils (Ubuntu)
   Importance: Undecided => High

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

Doing a quick google, it seems third party binaries can get linked
against this shared library as well possibly.  Ran apport-collect for
the extra logs; and both today's binutils and kernel upgrade haven't
fixed it.

Thinking we might need to propose for affecting binutils?

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

** Changed in: binutils (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] IwConfig.txt

[Trent Lloyd]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909534/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] PulseList.txt

[Trent Lloyd]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909543/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] ProcEnviron.txt

[Trent Lloyd]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909540/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] CurrentDmesg.txt

[Trent Lloyd]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909533/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] WifiSyslog.txt

[Trent Lloyd]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909546/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] Lspci.txt

[Trent Lloyd]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1702056/+attachment/4909536/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] ProcCpuinfoMinimal.txt

[Trent Lloyd]

apport information

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

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] UdevDb.txt

[Trent Lloyd]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1702056/+attachment/4909545/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] CRDA.txt

[Trent Lloyd]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1702056/+attachment/4909532/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] ProcInterrupts.txt

[Trent Lloyd]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909541/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] JournalErrors.txt

[Trent Lloyd]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909535/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] ProcModules.txt

[Trent Lloyd]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909542/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] RfKill.txt

[Trent Lloyd]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1702056/+attachment/4909544/+files/RfKill.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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] ProcCpuinfo.txt

[Trent Lloyd]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909538/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] Lsusb.txt

[Trent Lloyd]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1702056/+attachment/4909537/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lathiat4190 F pulseaudio
   /dev/snd/controlC3:  lathiat4190 F pulseaudio
   /dev/snd/controlC0:  lathiat4190 F pulseaudio
   /dev/snd/controlC2:  lathiat4190 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
  ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-9-generic N/A
   linux-backports-modules-4.11.0-9-generic  N/A
   linux-firmware1.167
  Tags:  artful
  Uname: Linux 4.11.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming G1 WIFI-BK
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-Gaming G1 WIFI-BK
  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/binutils/+bug/1702056/+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 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

apport information

** Tags added: apport-collected

** Description changed:

  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed
  
  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory
  
  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.
  
  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so
  
  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so
  
  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so
  
  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.
+ --- 
+ ApportVersion: 2.20.5-0ubuntu5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  lathiat4190 F pulseaudio
+  /dev/snd/controlC3:  lathiat4190 F pulseaudio
+  /dev/snd/controlC0:  lathiat4190 F pulseaudio
+  /dev/snd/controlC2:  lathiat4190 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ EcryptfsInUse: Yes
+ MachineType: Gigabyte Technology Co., Ltd. Z97X-Gaming G1 WIFI-BK
+ NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
+ Package: linux (not installed)
+ ProcFB:
+  0 radeondrmfb
+  1 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.11.0-9-generic 
root=ZFS=hostname/root ro
+ ProcVersionSignature: Ubuntu 4.11.0-9.14-generic 4.11.7
+ RelatedPackageVersions:
+  linux-restricted-modules-4.11.0-9-generic N/A
+  linux-backports-modules-4.11.0-9-generic  N/A
+  linux-firmware1.167
+ Tags:  artful
+ Uname: Linux 4.11.0-9-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip libvirt lxd plugdev sudo wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 04/21/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F7
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: Z97X-Gaming G1 WIFI-BK
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-GamingG1WIFI-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-GamingG1WIFI-BK:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.name: Z97X-Gaming G1 WIFI-BK
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1702056/+attachment/4909531/+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/1702056

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in binutils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with 

[Kernel-packages] [Bug 1702056] Re: perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open share

[Trent Lloyd]

lathiat@ubuntu:~$ apt-cache policy binutils
binutils:
  Installed: 2.28.51.20170627-1ubuntu1
  Candidate: 2.28.51.20170627-1ubuntu1
  Version table:
 *** 2.28.51.20170627-1ubuntu1 500
500 http://mirror.tcc.wa.edu.au/ubuntu artful-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 2.28-6ubuntu1 500
500 http://mirror.tcc.wa.edu.au/ubuntu artful/main amd64 Packages

lathiat@ubuntu:~$ apt-cache policy linux-tools-4.11.0-9-generic
linux-tools-4.11.0-9-generic:
  Installed: 4.11.0-9.14
  Candidate: 4.11.0-9.14
  Version table:
 *** 4.11.0-9.14 100
100 /var/lib/dpkg/status

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702056/+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 1702056] [NEW] perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open sha

[Trent Lloyd]

Public bug reported:

I am unable to launch perf on 4.11.0-9-generic (artful) running on
artful-proposed

/usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
libraries: libbfd-2.28-system.so: cannot open shared object file: No
such file or directory

It seems this library is provided by binutils, however the symlink
doesn't exist like it does on my xenial system for comparison.

lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

On xenial:
root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
/usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
/usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so


Not clear to me where the bug lies here, so starting with the 'perf' binary by 
way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.

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


** Tags: artful

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

Title:
  perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
  tools/4.11.0-9-generic/perf: error while loading shared libraries:
  libbfd-2.28-system.so: cannot open shared object file: No such file or
  directory

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am unable to launch perf on 4.11.0-9-generic (artful) running on
  artful-proposed

  /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
  libraries: libbfd-2.28-system.so: cannot open shared object file: No
  such file or directory

  It seems this library is provided by binutils, however the symlink
  doesn't exist like it does on my xenial system for comparison.

  lathiat@ubuntu:~$ dpkg -L binutils|grep bfd|grep so
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  lathiat@ubuntu:~$ ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.28.51-powerpc.20170627.so  
/usr/lib/x86_64-linux-gnu/libbfd-2.28.51-system.20170627.so

  On xenial:
  root@hyper:~# ls /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.26.1-system.so  
/usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd-2.26-system.so
/usr/lib/x86_64-linux-gnu/libbfd.so

  
  Not clear to me where the bug lies here, so starting with the 'perf' binary 
by way of the kernel package.  But may be an issue with something else.  I did 
notice quickly running 'ldd' in /usr/bin that it seems other files are linking 
against the above so directly.

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