[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it

[Ike Panhc]

** Changed in: kunpeng920/ubuntu-19.10
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-19.10
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  scsi: hisi_sas: Check sas_port before using it

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04 series:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-19.04 series:
  Triaged
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Triaged
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Potential NULL-pointer dereference.

  [Test Case]
  No known test case, but the issue is clear from code reading.

  [Fix]
  8c39673d5474b scsi: hisi_sas: Check sas_port before using it

  [Regression Risk]
  Patch restricted to hisi_sas driver.

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

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

[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it

[Ike Panhc]

** Changed in: kunpeng920/ubuntu-19.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04-hwe
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  scsi: hisi_sas: Check sas_port before using it

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04 series:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-19.04 series:
  Triaged
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Triaged
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Potential NULL-pointer dereference.

  [Test Case]
  No known test case, but the issue is clear from code reading.

  [Fix]
  8c39673d5474b scsi: hisi_sas: Check sas_port before using it

  [Regression Risk]
  Patch restricted to hisi_sas driver.

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

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

[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices

[Oded Arbel]

Tries booting with the chain disconnected from the dock, and as expected
- the system boots correctly with the dock attached and built-in USB
devices present, after which plugging the USB cable in works well.

The problem seems to only be when external USB devices are connected to
the dock.

Here's how the dock's USB controller tree looks after everything is
plugged in:

8<
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
ID 0424:2807 Standard Microsystems Corp. Hub
|__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/5p, 480M
ID 0424:2734 Standard Microsystems Corp. 
|__ Port 4: Dev 7, If 2, Class=Audio, Driver=snd-usb-audio, 480M
ID 03f0:a707 HP, Inc 
|__ Port 4: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M
ID 03f0:a707 HP, Inc 
|__ Port 4: Dev 7, If 3, Class=Audio, Driver=snd-usb-audio, 480M
ID 03f0:a707 HP, Inc 
|__ Port 4: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M
ID 03f0:a707 HP, Inc 
|__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
ID 05e3:0608 Genesys Logic, Inc. Hub
|__ Port 4: Dev 8, If 1, Class=Human Interface Device, 
Driver=usbhid, 1.5M
ID 04d9:2013 Holtek Semiconductor, Inc. Keyboard [Das 
Keyboard]
|__ Port 4: Dev 8, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
ID 04d9:2013 Holtek Semiconductor, Inc. Keyboard [Das 
Keyboard]
|__ Port 5: Dev 10, If 0, Class=Human Interface Device, 
Driver=usbhid, 480M
ID 0424:274c Standard Microsystems Corp. 
|__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/5p, 480M
ID 0424:2734 Standard Microsystems Corp. 
|__ Port 4: Dev 9, If 2, Class=Human Interface Device, 
Driver=usbhid, 12M
ID 046d:c52b Logitech, Inc. Unifying Receiver
|__ Port 4: Dev 9, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
ID 046d:c52b Logitech, Inc. Unifying Receiver
|__ Port 4: Dev 9, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
ID 046d:c52b Logitech, Inc. Unifying Receiver
|__ Port 5: Dev 11, If 0, Class=Human Interface Device, 
Driver=usbhid, 480M
ID 0424:274c Standard Microsystems Corp. 
|__ Port 5: Dev 3, If 0, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
|__ Port 5: Dev 3, If 1, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
|__ Port 5: Dev 3, If 2, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
|__ Port 5: Dev 3, If 3, Class=Audio, Driver=snd-usb-audio, 480M
ID 0bda:4014 Realtek Semiconductor Corp. 
8<

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

Title:
  Thunderbolt dock fails to connect USB devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell
  Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB
  bus connects very slowly (15~20 seconds) and sometimes does not
  connect at all and a failure is reported in dmesg:

  [  117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [  117.850643] xhci_hcd :0e:00.0: Host halt failed, -110
  [  117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [  117.850679] xhci_hcd :0e:00.0: HC died; cleaning up
  [  117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure 
endpoint command

  The slow connection seems to be a feature of the current updated
  firmware - the computer was not used for ~6 months due to a battery
  issue that was fixed, and after fixing the battery a new firmware was
  installed using the MS-Windows Dell software update utility. Both on
  Linux and MS-Windows the process of connecting the Thunderbolt dock
  completes after a much longer time than it used to in the beginning of
  the year.

  On the face of it it seems that the longer init process now hits
  timeouts in the xhci_hcd driver and depending on the exact timing
  often causes the xhci_hcd to give up and drop the USB Thunderbolt bus.
  This happens about 50% of the time, when connecting the Dock when the
  system is running, and a bit less when the system is booted or resumed
  from sleep when the dock is already connected.

  fwupdmgr report:

  -8<-
  Precision M5520 Thunderbolt Controller
DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386

[Kernel-packages] [Bug 1855867] Re: touchpad not working in ubuntu

[Po-Hsu Lin]

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

I will mark this one as a dup for bug 1854798, please feel free to revert the 
status if you think this is incorrect.
Thanks

** This bug has been marked a duplicate of bug 1854798
   Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

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

Title:
  touchpad not working in ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad is not working in ubuntu however in windows it is working
  perfectly

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1601 F pulseaudio
   /dev/snd/controlC0:  user   1601 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 10 16:24:45 2019
  HibernationDevice: RESUME=UUID=ed85b920-aef1-4a08-af75-a25fc080540a
  InstallationDate: Installed on 2016-09-30 (1165 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=aba4af37-5e2e-4cad-b64b-a11a3b78621a ro i8042.reset quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-21 (414 days ago)
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0G1TDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

[Oded Arbel]

Just had the "unknown event type 15" error happen again, with the
lp1766076 kernel and current firmware:

---8<---
Dec 25 11:19:34 vesho kernel: xhci_hcd :0e:00.0: ERROR unknown event type 15
Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: xHCI host not responding 
to stop endpoint command.
Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: xHCI host controller not 
responding, assume dead
Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: HC died; cleaning up
Dec 25 11:19:39 vesho kernel: usb 4-1.3.1: Failed to suspend device, error -22
Dec 25 11:19:39 vesho kernel: usb 3-1: USB disconnect, device number 2
Dec 25 11:19:39 vesho kernel: usb 3-1.3: USB disconnect, device number 4
Dec 25 11:19:39 vesho kernel: usb 3-1.3.1: USB disconnect, device number 5
Dec 25 11:19:39 vesho kernel: usb 3-1.3.1.4: USB disconnect, device number 9
Dec 25 11:19:39 vesho kernel: usb 4-1: USB disconnect, device number 2
Dec 25 11:19:39 vesho kernel: usb 4-1.2: USB disconnect, device number 3
Dec 25 11:19:39 vesho kernel: usb 3-1.3.1.5: USB disconnect, device number 11
Dec 25 11:19:39 vesho kernel: usb 3-1.3.2: USB disconnect, device number 6
Dec 25 11:19:39 vesho kernel: usb 3-1.3.2.4: USB disconnect, device number 8
Dec 25 11:19:39 vesho kernel: usb 4-1.3: USB disconnect, device number 4
Dec 25 11:19:39 vesho kernel: usb 4-1.3.1: USB disconnect, device number 5
Dec 25 11:19:39 vesho kernel: usb 3-1.3.4: USB disconnect, device number 7
Dec 25 11:19:39 vesho kernel: usb 3-1.3.5: USB disconnect, device number 10
Dec 25 11:19:39 vesho kernel: usb 3-1.5: USB disconnect, device number 3
---8<---

Firmware versions:
[Dell] Precision 5520 System Firmware: 0.1.16.0
[Dell] Precision M5520 Thunderbolt Controller: 26.01
[Dell] Dell TB16 Thunderbolt Cable: 0.0.3.18
[Dell] Dell TB16 Port Controller 1: 0.1.2.17
[Dell] Dell TB16 Port Controller 2: 0.1.2.50
[Synaptics] Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock: 3.10.002
[Dell] Dell Thunderbolt Dock: 16.00
[Dell] Dell Thunderbolt Cable: 16.00
[Dell] Dell TB16: 0.0.0.0

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

Title:
  USB over thunderbolt turns off every once in a while

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

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd 000

[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station

[kraba]

tested but it's still stucking the usb hub. After the undock I need to
run the reset of the USB hub to have it working.

Undock:

[   84.219765] usb 2-1: USB disconnect, device number 2
[   84.225638] [drm] DM_MST: stopping TM on aconnector: da0f527b [id: 
78]
[   84.225876] [drm] DM_MST: Disabling connector: 63ebb1ca [id: 83] 
[master: da0f527b]
[   84.227747] [drm] DM_MST: Disabling connector: 4a641ca6 [id: 88] 
[master: da0f527b]
[   84.228238] [drm] DM_MST: Disabling connector: c365f2c1 [id: 93] 
[master: da0f527b]
[   84.255498] usb 3-4: USB disconnect, device number 2
[   84.255516] usb 3-4.2: USB disconnect, device number 3
[   84.255528] usb 3-4.2.2: USB disconnect, device number 4
[   84.285331] r8169 :03:00.0 enp3s0f0: Link is Down
[   84.380070] usb 2-4: USB disconnect, device number 3
[   84.380088] usb 2-4.2: USB disconnect, device number 4
[   84.380101] usb 2-4.2.4: USB disconnect, device number 6
[   84.590759] usb 2-4.3: USB disconnect, device number 5
[   94.852024] xhci_hcd :05:00.3: Abort failed to stop command ring: -110
[   94.863836] xhci_hcd :05:00.3: xHCI host controller not responding, 
assume dead
[   94.863859] xhci_hcd :05:00.3: HC died; cleaning up
[   94.863951] xhci_hcd :05:00.3: Timeout while waiting for configure 
endpoint command
[   94.865041] usb 2-4.5: USB disconnect, device number 7


Dock:

[  147.920108] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow 
control rx/tx
[  148.973615] [drm] DM_MST: starting TM on aconnector: da0f527b [id: 
78]
[  149.070161] [drm] DM_MST: added connector: 1e859739 [id: 101] 
[master: da0f527b]
[  149.070321] [drm] DM_MST: added connector: 761fd001 [id: 106] 
[master: da0f527b]
[  149.070414] [drm] DM_MST: added connector: f8739422 [id: 117] 
[master: da0f527b]

unbind/bind manually/via script:

[  197.186295] xhci_hcd :05:00.3: remove, state 1
[  197.186302] usb usb3: USB disconnect, device number 1
[  197.186786] xhci_hcd :05:00.3: USB bus 3 deregistered
[  197.186850] xhci_hcd :05:00.3: remove, state 1
[  197.186854] usb usb2: USB disconnect, device number 1
[  197.187771] xhci_hcd :05:00.3: USB bus 2 deregistered
[  197.188174] xhci_hcd :05:00.4: remove, state 4
[  197.188181] usb usb5: USB disconnect, device number 1
[  197.188540] xhci_hcd :05:00.4: USB bus 5 deregistered
[  197.188560] xhci_hcd :05:00.4: remove, state 1
[  197.188567] usb usb4: USB disconnect, device number 1
[  197.188569] usb 4-1: USB disconnect, device number 2
[  197.189511] usb 4-2: USB disconnect, device number 3
[  197.189517] usb 4-2.1: USB disconnect, device number 4
[  197.262799] usb 4-2.4: USB disconnect, device number 5
[  197.312146] xhci_hcd :05:00.4: Host halt failed, -110
[  197.312149] xhci_hcd :05:00.4: Host controller not halted, aborting 
reset.
[  197.312483] xhci_hcd :05:00.4: USB bus 4 deregistered
[  198.315237] xhci_hcd :05:00.3: xHCI Host Controller
[  198.315247] xhci_hcd :05:00.3: new USB bus registered, assigned bus 
number 2
[  198.315424] xhci_hcd :05:00.3: hcc params 0x0270ffe5 hci version 0x110 
quirks 0x00084410
[  198.316177] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.05
[  198.316181] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[  198.316184] usb usb2: Product: xHCI Host Controller
[  198.316187] usb usb2: Manufacturer: Linux 5.5.0-050500rc3-generic xhci-hcd
[  198.316189] usb usb2: SerialNumber: :05:00.3
[  198.316472] hub 2-0:1.0: USB hub found
[  198.316514] hub 2-0:1.0: 4 ports detected
[  198.317303] xhci_hcd :05:00.3: xHCI Host Controller
[  198.317310] xhci_hcd :05:00.3: new USB bus registered, assigned bus 
number 3
[  198.317315] xhci_hcd :05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[  198.317372] usb usb3: We don't know the algorithms for LPM for this host, 
disabling LPM.
[  198.317432] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, 
bcdDevice= 5.05
[  198.317435] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[  198.317436] usb usb3: Product: xHCI Host Controller
[  198.317438] usb usb3: Manufacturer: Linux 5.5.0-050500rc3-generic xhci-hcd
[  198.317440] usb usb3: SerialNumber: :05:00.3
[  198.317632] hub 3-0:1.0: USB hub found
[  198.317651] hub 3-0:1.0: 4 ports detected
[  198.318427] xhci_hcd :05:00.4: xHCI Host Controller
[  198.318435] xhci_hcd :05:00.4: new USB bus registered, assigned bus 
number 4
[  198.318644] xhci_hcd :05:00.4: hcc params 0x0260ffe5 hci version 0x110 
quirks 0x00084410
[  198.319507] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.05
[  198.319510] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[  198.319512] usb usb4: Product: xHCI Host Controller
[  198.319514] usb usb4: Manufacturer: Linux 5.5.0

[Kernel-packages] [Bug 1845620] Re: stime01 from ubuntu_ltp_syscalls failed on D Power9

[Po-Hsu Lin]

I have the patch tested on Power9 node "baltar" with Disco kernel (5.0.0-37).
It's still failing with this stime01 test.

 startup='Wed Dec 25 10:25:31 2019'
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:45: INFO: Testing libc stime()
 stime01.c:46: INFO: pt.tv_sec: 1577269561
 stime01.c:47: PASS: system time was set to 1577269561
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:48: INFO: Testing SYS_stime syscall
 stime01.c:51: FAIL: system time not set to 1577269591 (got: 1577269531)
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 stime_var.h:51: INFO: Testing SYS_settimeofday syscall
 stime01.c:46: INFO: pt.tv_sec: 1577269561
 stime01.c:47: PASS: system time was set to 1577269561

 Summary:
 passed   2
 failed   1
 skipped  0
 warnings 0

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

Title:
  stime01 from ubuntu_ltp_syscalls failed on D Power9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Invalid

Bug description:
  This failure can only be found on Disco Power9, passed on other arches.
  Probably a glitch that similar to the hwclock test failure (bug 1802233)

   tag=stime01 stime=1568943645 dur=-22 exit=exited stat=1 core=no cu=0 cs=0
   startup='Fri Sep 20 01:40:45 2019'
   tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
   stime_var.h:45: INFO: Testing libc stime()
   stime01.c:46: INFO: pt.tv_sec: 1568943675
   stime01.c:47: PASS: system time was set to 1568943675
   tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
   stime_var.h:48: INFO: Testing SYS_stime syscall
   stime01.c:51: FAIL: system time not set to 1568943705 (got: 1568943660)
   tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
   stime_var.h:51: INFO: Testing SYS_settimeofday syscall
   stime01.c:46: INFO: pt.tv_sec: 1568943690
   stime01.c:47: PASS: system time was set to 1568943690

   Summary:
   passed 2
   failed 1
   skipped 0
   warnings 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845620/+subscriptions

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

[Kernel-packages] [Bug 1857536] [NEW] Touch pad is not working - Lenovo G50

[kadivarnishant]

Public bug reported:

Laptop : Lenovo G50
I ran below command to check that touchpad package is available or not, and 
couldn't find the synaptic touchpad package.
Command : cat /proc/bus/input/devices

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kadinish   1720 F pulseaudio
 /dev/snd/controlC1:  kadinish   1720 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 25 16:02:24 2019
InstallationDate: Installed on 2019-12-10 (15 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20351
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=6a5066c3-fbca-4e9c-be14-2af9e25b497b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-24-generic N/A
 linux-backports-modules-5.3.0-24-generic  N/A
 linux-firmware1.183.3
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-12-25 (0 days ago)
dmi.bios.date: 04/02/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN25WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A2
dmi.board.vendor: LENOVO
dmi.board.version: 31900059STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20351
dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
dmi.product.version: Lenovo G50-70
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug eoan

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

Title:
  Touch pad is not working - Lenovo G50

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop : Lenovo G50
  I ran below command to check that touchpad package is available or not, and 
couldn't find the synaptic touchpad package.
  Command : cat /proc/bus/input/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kadinish   1720 F pulseaudio
   /dev/snd/controlC1:  kadinish   1720 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 16:02:24 2019
  InstallationDate: Installed on 2019-12-10 (15 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20351
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=6a5066c3-fbca-4e9c-be14-2af9e25b497b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-12-25 (0 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20351
  dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1857536] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Touch pad is not working - Lenovo G50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop : Lenovo G50
  I ran below command to check that touchpad package is available or not, and 
couldn't find the synaptic touchpad package.
  Command : cat /proc/bus/input/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kadinish   1720 F pulseaudio
   /dev/snd/controlC1:  kadinish   1720 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 16:02:24 2019
  InstallationDate: Installed on 2019-12-10 (15 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20351
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=6a5066c3-fbca-4e9c-be14-2af9e25b497b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-12-25 (0 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20351
  dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1857227] Re: PulseAudio sound disappears on hdmi via stereo output

[Rocinante]

This problem has been known for 5 years and has not yet been resolved
https://github.com/raspberrypi/linux/issues/688

** Bug watch added: github.com/raspberrypi/linux/issues #688
   https://github.com/raspberrypi/linux/issues/688

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

Title:
  PulseAudio sound disappears on hdmi via stereo output

Status in linux-raspi2 package in Ubuntu:
  In Progress

Bug description:
  Оn my Raspberry Pi 4 4GB version the sound constantly disappears when
  I connect the computer to my Samsung plasma TV using the hdmi output.
  This works great with an analog 3.5 jack and hdmi-vga adapter, but I
  can’t set up stable sound with a "clean" hdmi connection. I tried with
  different hdmi cables that work great with a desktop PC and other
  equipment and it seems like a software problem. Used operating system
  Ubuntu server 19.10.1 aarch64. I try removed pulseaudio and the sound
  works fine through alsa on hdmi

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

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

[Kernel-packages] [Bug 1857541] [NEW] [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support

[AaronMa]

Public bug reported:

SRU justification:

[Impact]
The current kernel didn't support multitouch for LG I2C touchscreen.

[Fix]
Add LG I2C id to hid-multitouch to support it.

[Test]
Verified on hardware with a positive result.

[Regression Potential]
Low.
Add new I2C id with positive verification.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AaronMa (mapengyu)
 Status: Incomplete

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
  support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU justification:

  [Impact]
  The current kernel didn't support multitouch for LG I2C touchscreen.

  [Fix]
  Add LG I2C id to hid-multitouch to support it.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new I2C id with positive verification.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1857541

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

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

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

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

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
  support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU justification:

  [Impact]
  The current kernel didn't support multitouch for LG I2C touchscreen.

  [Fix]
  Add LG I2C id to hid-multitouch to support it.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new I2C id with positive verification.

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

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

[Kernel-packages] [Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support

[AaronMa]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
  support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU justification:

  [Impact]
  The current kernel didn't support multitouch for LG I2C touchscreen.

  [Fix]
  Add LG I2C id to hid-multitouch to support it.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new I2C id with positive verification.

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

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

[Kernel-packages] [Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support

[AaronMa]

** Tags added: oem-priority originate-from-1852693 sutton

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
  support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU justification:

  [Impact]
  The current kernel didn't support multitouch for LG I2C touchscreen.

  [Fix]
  Add LG I2C id to hid-multitouch to support it.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new I2C id with positive verification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1857541/+subscriptions

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

[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50

[Rolando Gorgs]

Thank you, Martin, for providing this simple but clever and VERY
effective workaround! I can confirm that it works.

I'd like to add, that you have to execute this script with 'bash fix_sound.sh'.
'sh fix_sound.sh' doesn't work because debian and ubuntu use dash as 
non-interactive shell and dash cannot handle that kind of assertion: <<<. Took 
me a while to realize what the problem was. ^^

Anyway. I'd like to see a real fix here. But in the meantime I can live
with that script.

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

Title:
  No HDMI-audio after kernel 4.15.-0.50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. 
In pavucontrol HDMI-audio shows unplugged. And also internal audio shows 
unplugged, but it still works. I'm on linux mint 18.3.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jouni  1859 F pulseaudio
   /dev/snd/controlC1:  jouni  1859 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36
  InstallationDate: Installed on 2017-01-28 (883 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

[Frank Blah]

Hello,
I suffer from the same issue, I also have HP Zbook 15 G6 with Ubuntu 19.10. I 
installed the latest kernel v5.5-rc3 through ukuu utility. Now, I do not have 
any sound (nor mic, nor speakers). 
Here is the output from dmesg:
```
[0.00] Linux version 5.5.0-050500rc3-generic (kernel@kathleen) (gcc 
version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)) #201912230230 SMP Mon Dec 23 
02:33:07 UTC 2019
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500rc3-generic 
root=UUID=68ba5bbe-cf0c-4d88-8325-9a95b3cceb05 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0005bfff] usable
[0.00] BIOS-e820: [mem 0x0005c000-0x0005cfff] reserved
[0.00] BIOS-e820: [mem 0x0005d000-0x0009] usable
[0.00] BIOS-e820: [mem 0x000a-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x76789fff] usable
[0.00] BIOS-e820: [mem 0x7678a000-0x76c89fff] type 20
[0.00] BIOS-e820: [mem 0x76c8a000-0x77a6dfff] reserved
[0.00] BIOS-e820: [mem 0x77a6e000-0x77c6dfff] ACPI NVS
[0.00] BIOS-e820: [mem 0x77c6e000-0x77d0efff] ACPI data
[0.00] BIOS-e820: [mem 0x77d0f000-0x77d0] usable
[0.00] BIOS-e820: [mem 0x77d1-0x7e7f] reserved
[0.00] BIOS-e820: [mem 0xfe01-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00047d7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.60 by HP
[0.00] efi:  ACPI=0x77d0e000  ACPI 2.0=0x77d0e014  ESRT=0x76f54b98  
TPMFinalLog=0x77bf6000  SMBIOS=0x76f53000  MEMATTR=0x72e93018  MPS=0x771d 
[0.00] SMBIOS 3.1 present.
[0.00] DMI: HP HP ZBook 15 G6/860F, BIOS R92 Ver. 01.03.04 11/06/2019
[0.00] tsc: Detected 2600.000 MHz processor
[0.001922] tsc: Detected 2599.992 MHz TSC
[0.001922] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.001924] e820: remove [mem 0x000a-0x000f] usable
[0.001929] last_pfn = 0x47d800 max_arch_pfn = 0x4
[0.001932] MTRR default type: write-back
[0.001933] MTRR fixed ranges enabled:
[0.001934]   0-9 write-back
[0.001935]   A-B uncachable
[0.001936]   C-F write-protect
[0.001936] MTRR variable ranges enabled:
[0.001938]   0 base 008000 mask 7F8000 uncachable
[0.001939]   1 base 007C00 mask 7FFC00 uncachable
[0.001940]   2 base 20 mask 60 uncachable
[0.001941]   3 base 10 mask 70 uncachable
[0.001941]   4 base 08 mask 78 uncachable
[0.001942]   5 base 40 mask 40 uncachable
[0.001943]   6 disabled
[0.001943]   7 disabled
[0.001944]   8 disabled
[0.001944]   9 disabled
[0.002421] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.002603] last_pfn = 0x77d10 max_arch_pfn = 0x4
[0.010888] esrt: Reserving ESRT space from 0x76f54b98 to 
0x76f54bf8.
[0.010899] check: Scanning 1 areas for low memory corruption
[0.010903] Using GB pages for direct mapping
[0.010905] BRK [0x3c3a01000, 0x3c3a01fff] PGTABLE
[0.010907] BRK [0x3c3a02000, 0x3c3a02fff] PGTABLE
[0.010908] BRK [0x3c3a03000, 0x3c3a03fff] PGTABLE
[0.010938] BRK [0x3c3a04000, 0x3c3a04fff] PGTABLE
[0.010940] BRK [0x3c3a05000, 0x3c3a05fff] PGTABLE
[0.011032] BRK [0x3c3a06000, 0x3c3a06fff] PGTABLE
[0.011056] BRK [0x3c3a07000, 0x3c3a07fff] PGTABLE
[0.011085] BRK [0x3c3a08000, 0x3c3a08fff] PGTABLE
[0.011129] Secure boot could not be determined
[0.011130] RAMDISK: [mem 0x2ef89000-0x337bbfff]
[0.011145] ACPI: Early table checksum verification disabled
[0.011148]

[Kernel-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

[Eric Desrochers]

Ok so in fact the inconsistency is due to "parted" that will try to
probe devices iff the given block device return informations from
stat(), regardless if the block device is available or not.

Seems like the only trigger/criteria is the stat() return. Since the
loop device stat doesn't clear/reset once umounted/detacted, then parted
assume it can go ahead and probe it assuming it is a legit device.


# libparted/arch/linux.c

618 static int
619 _device_stat (PedDevice* dev, struct stat * dev_stat)
620 {
621 PED_ASSERT (dev != NULL);
622 PED_ASSERT (!dev->external_mode);
623 
624 while (1) {
625 if (!stat (dev->path, dev_stat)) {
626 return 1;
627 } else {
628 if (ped_exception_throw (
629 PED_EXCEPTION_ERROR,
630 PED_EXCEPTION_RETRY_CANCEL,
631 _("Could not stat device %s - %s."),
632 dev->path,
633 strerror (errno))
634 != PED_EXCEPTION_RETRY)
635 return 0;
636 }
637 }
638 }


Example:

# parted -s $(losetup -f) unit s print
Warning: Error fsyncing/closing /dev/loop18: Input/output error

# stat $(losetup -f)
  File: /dev/loop18
  Size: 0   Blocks: 0  IO Block: 4096   block special file
Device: 6h/6d   Inode: 509 Links: 1 Device type: 7,12
Access: (0660/brw-rw)  Uid: (0/root)   Gid: (6/disk)
Access: 2019-12-25 13:05:15.543108777 -0500
Modify: 2019-12-25 13:05:15.543108777 -0500
Change: 2019-12-25 13:05:15.543108777 -0500
 Birth: -

# parted -s /dev/loop19 unit s print
Error: Could not stat device /dev/loop19 - No such file or directory.

# stat /dev/loop19
stat: cannot stat '/dev/loop19': No such file or directory


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

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing w

[Kernel-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

[Eric Desrochers]

so 2 things come to my mind right now

Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?

and/or

Does parted need to smarter and not only based is detection only on
stat() ?

Let's circle back on Jan 2020.

** Also affects: parted (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/1856871

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Incomplete
Status in parted package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

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

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

[Kernel-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

[Eric Desrochers]

so 2 things come to my mind right now

Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?

and/or

Does parted need to be smarter and not only based is detection on stat()
to assume if its a legit device or not to be probed ?

Let's circle back on Jan 2020.

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

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Incomplete
Status in parted package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

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

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

[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

[Ivan]

Hi all,

can someone tell me how to fix this issue, its getting annoying. Is it
going to be new update on this, im not sure about using the ppa. Is
there any other safety way to be patched ?

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

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

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0

[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash

[Bug Watch Updater]

** Changed in: dmidecode (Debian)
   Status: New => Fix Released

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

Title:
  dmidecode causing system crash

Status in dmidecode package in Ubuntu:
  Confirmed
Status in dmidecode package in Debian:
  Fix Released

Bug description:
  Please let me know what other information I can provide. Some basic
  info I've captured below.

  root@jetson-0423318029481:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic
  root@jetson-0423318029481:~# uname -a
  Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21 
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
  root@jetson-0423318029481:~# apt-cache madison dmidecode
   dmidecode |  3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main 
arm64 Packages
  root@jetson-0423318029481:~# dmidecode -V
  3.1
  root@jetson-0423318029481:~# strace dmidecode
  execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
  brk(NULL)   = 0x559651a000
  faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
  faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
  mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
  close(3)= 0
  faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0 
\10\2\0\0\0\0\0"..., 832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f8050a000
  mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f80369000
  mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
  mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
  mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
  close(3)= 0
  mprotect(0x7f804b8000, 16384, PROT_READ) = 0
  mprotect(0x55932d9000, 12288, PROT_READ) = 0
  mprotect(0x7f8050e000, 4096, PROT_READ) = 0
  munmap(0x7f804c2000, 130516)= 0
  fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
  brk(NULL)   = 0x559651a000
  brk(0x559653b000)   = 0x559653b000
  write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
  )   = 16
  openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) = 
-1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such 
file or directory)
  openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or 
directory)
  write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry 
point.
  ) = 35
  openat(AT_FDCWD, "/dev/mem", O_RDONLY)  = 3
  fstat(3, 

  # System hangs and reboots here.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dmidecode 3.1-1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 25 12:15:53 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  InstallationDate: Installed on 2019-02-28 (24 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dmidecode
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

[Chris Guiver]

@ivanak

Bug reports aren't for support, for support options please refer to
https://discourse.ubuntu.com/t/finding-help/709

For using proposed (comment #13 and others) see
https://help.ubuntu.com/community/Repositories/Ubuntu and
https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

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

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (r

[Kernel-packages] [Bug 1856534] Re: Touchpad not working after update

[Chris Guiver]

Bug reports aren't for support, for support options please refer to
https://discourse.ubuntu.com/t/finding-help/709

I believe kernel linux-image-4.15.0-73-generic (currently in proposed)
will move to 'main' on January 5, 2020.

For enabling proposed (suggested in comment #13 and others in the bug
report 1854798 I believe this is a duplicate of, which will let you use
it now) see https://help.ubuntu.com/community/Repositories/Ubuntu and
https://wiki.ubuntu.com/Testing/EnableProposed

If it solves your issue (best if done before it's live for everyone Jan
5 probably) PLEASE report back here that here it works.

If it doesn't work, then it may be you have a unique situation that may
need attention its not getting due likely duplicate. Please report that
here too.

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

Title:
  Touchpad not working after update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update shown up and process, it request for reboot, than the
  touchpad stoped working. I can use external mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivan   2936 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 09:59:54 2019
  HibernationDevice: RESUME=UUID=46c57e98-ae21-43ec-b4cf-833f890ce21c
  InstallationDate: Installed on 2019-01-16 (333 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 15-3568
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=32182752-4df3-4480-817d-e2c0863ac8d0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 09V8CF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn09V8CF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

[Lewi S. Kristianto]

Hi Ivanak,

while awaiting new kernel, browsing and testing with kernel 5.x, is working in 
dell xps 9333, 
here is reference how to enable
https://wiki.ubuntu.com/Kernel/LTSEnablementStack

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

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

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
09

[Kernel-packages] [Bug 1849913] Re: urget resume from s2idle deep error

[Launchpad Bug Tracker]

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

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

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

Title:
  urget resume from s2idle deep error

Status in linux package in Ubuntu:
  Expired

Bug description:
  My laptop is 'Dell xps13 9370 2 in 1 ' , I can perfectly install the ubuntu 
19.10 version.
  The default setting of '/sys/power/mem_sleep' is [s2idle] not deep. In the 
[s2idle] mode it take
  very long time (about 5 mins ) to resume from sleep and sometimes i have a 
black screen when resume
  from it.

  After changing the /sys/power/mem_sleep to [deep] mode which is said to save 
more energy, I got
  a total black screen problem.

  Please help and fix this bug.

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

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

[Kernel-packages] [Bug 1842173] Re: ubuntu 18.04.3 install /dev/sda1 could not boot up

[Launchpad Bug Tracker]

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

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

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

Title:
  ubuntu 18.04.3 install /dev/sda1 could not boot up

Status in linux package in Ubuntu:
  Expired

Bug description:
  My PC use ASrock H110M-HVD mother(version P7.60).
  CPU is intel i3-7100, and Geforece 1050i.
  Geforce only use CUDA sysytem, not to use VGA. VGA use onboard chip.
  I use CSM to use mbr.

  This PC /dev/sda disk has four partitions for primary partition to use mbr.
  I install ubuntu-18.04.3 Japanese edition to /dev/sda to use mount point /.
  boot loader install /dev/sda1 named pbr.

  My PC mbr use mbm039 that is multi-boot-loader for mbr.
  boot from /dev/sda1, but could not start.
  purple screen dots that are change red to white for ever.

  I boot from /dev/sda4, that is installed ubuntu-18.04.2.
  and get syslog in /dev/sda1. upload syslog.
  

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

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

[Kernel-packages] [Bug 1857235] Re: touchpad not working

[Po-Hsu Lin]

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

Hello Pratik,
please try this tool: https://github.com/Cypresslin/alt_my_grub.git

git clone https://github.com/Cypresslin/alt_my_grub.git
cd alt_my_grub
./alt_my_grub

And select the kernel that you want to boot with.

After the newer kernel has been released in the future, you can upgrade
your system and run this script with "./alt_my_grub -r" again to restore
your current setting.

Thanks

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  my touchpad is not working in ubuntu 18.04; however it works fine when
  I run the diagnostics from the boot menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pratik 1509 F pulseaudio
   /dev/snd/controlC1:  pratik 1509 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 22 20:44:41 2019
  HibernationDevice: RESUME=UUID=cc034e3f-9499-474e-a0d8-089de59d3153
  InstallationDate: Installed on 2016-12-11 (1106 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=706edc44-7e3d-4c83-82c4-d7ad2140392a ro i8042.reset quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.14
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (570 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0G1TDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1857418] Re: KDE Panel disappears after screen lock

[amasterov]

This error was reproduced under kernel v5.5-rc3

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

Title:
  KDE Panel disappears after screen lock

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I use ubuntu 18.04. 
  Kernel Ubuntu 4.15.0-73.82+lp1854798+2-generic 4.15.18 (problem exists on 
previous kernels too)
  KDE from the repo
  Screen is extended to external monitor
  laptop Lenovo Carbon 6x
  Monitor attached with HDMI 
  Monitor model: Acer H236HL

  When the screen is locked by timeout, after unlocking by entering
  password, KDE panel disappears on external monitor. I can not add a
  panel to it, e.g. I add it to screen but the panel does not appear.
  After reboot panel is in place. If I have added panels to screen they
  are also exist.

  It is interesting that this problem exists with only my monitor. Other 
monitors attached to my laptop work OK. The problem also does not exist if I 
turn my monitor off before screen lock.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 2726 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f52c7f84-717f-47b3-82c8-99ef8ff44b4d
  InstallationDate: Installed on 2018-09-17 (462 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KH006JRT
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-73-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-73.82+lp1854798+2-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-73-generic N/A
   linux-backports-modules-4.15.0-73-generic  N/A
   linux-firmware 1.173.12
  Tags:  bionic
  Uname: Linux 4.15.0-73-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006JRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KH006JRT:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006JRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KH006JRT
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1853995

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

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

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

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

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

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

Title:
  [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04 series:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  "[Steps to Reproduce]
  mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error

  [Actual Results]
  Io error when the first time of mkfs.ext4

  [  745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8 
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  776.034612] sas: trying to find task 0x9656953a
  [  776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
  [  776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  776.049635] sas: trying to find task 0x975f5cdf
  [  776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  776.062900] sas: ata5: end_device-4:0: cmd error handler
  [  776.062914] sas: ata5: end_device-4:0: dev error handler
  [  776.062918] sas: ata6: end_device-4:1: dev error handler
  [  776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action 
0x6 frozen
  [  776.062924] sas: ata7: end_device-4:2: dev error handler
  [  776.062926] sas: ata8: end_device-4:3: dev error handler
  [  776.070548] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq 
dma 512 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.090638] ata5.00: status: { DRDY }
  [  776.094290] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq 
dma 512 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.114399] ata5.00: status: { DRDY }
  [  776.118051] ata5: hard resetting link
  [  776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
  [  776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
  [  776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
  [  776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
  [  776.451784] ata5.00: configured for UDMA/133
  [  776.456043] ata5.00: device reported invalid CHS sector 0
  [  776.461423] ata5.00: device reported invalid CHS sector 0
  [  776.466807] ata5: EH complete
  [  776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
  [  776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15 
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  806.746604] sas: trying to find task 0x975f5cdf
  [  806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  806.761582] sas: trying to find task 0x9656953a
  [  806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
  [  806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  806.774852] sas: ata5: end_device-4:0: cmd error handler
  

[Kernel-packages] [Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands

[Ike Panhc]

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04 series:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  "[Steps to Reproduce]
  mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error

  [Actual Results]
  Io error when the first time of mkfs.ext4

  [  745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8 
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  776.034612] sas: trying to find task 0x9656953a
  [  776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
  [  776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  776.049635] sas: trying to find task 0x975f5cdf
  [  776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  776.062900] sas: ata5: end_device-4:0: cmd error handler
  [  776.062914] sas: ata5: end_device-4:0: dev error handler
  [  776.062918] sas: ata6: end_device-4:1: dev error handler
  [  776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action 
0x6 frozen
  [  776.062924] sas: ata7: end_device-4:2: dev error handler
  [  776.062926] sas: ata8: end_device-4:3: dev error handler
  [  776.070548] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq 
dma 512 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.090638] ata5.00: status: { DRDY }
  [  776.094290] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq 
dma 512 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.114399] ata5.00: status: { DRDY }
  [  776.118051] ata5: hard resetting link
  [  776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
  [  776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
  [  776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
  [  776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
  [  776.451784] ata5.00: configured for UDMA/133
  [  776.456043] ata5.00: device reported invalid CHS sector 0
  [  776.461423] ata5.00: device reported invalid CHS sector 0
  [  776.466807] ata5: EH complete
  [  776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
  [  776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15 
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  806.746604] sas: trying to find task 0x975f5cdf
  [  806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  806.761582] sas: trying to find task 0x9656953a
  [  806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
  [  806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  806

[Kernel-packages] [Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

[Ike Panhc]

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

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

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Bug Description]
  sas kasan test will produce this out bounds in sas module

  [Steps to Reproduce]
  1) enbale this kasn
  2)
  3)

  [Actual Results]
  30293.504016] sas: ata464: end_device-2:2:6: dev error handler
  [30293.504041] sas: ata465: end_device-2:2:7: dev error handler
  [30293.504059] sas: ata466: end_device-2:2:8: dev error handler
  [30293.538746] 
==
  [30293.550672] BUG: KASAN: slab-out-of-bounds in 
hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.558642] Read of size 8 at addr b72e47233540 by task 
kworker/u193:3/79165
  [30293.566004] 
  [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB  O 
 5.1.0-rc1-g7a3fab8-dirty #1
  [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 
CS V3.B010.01 06/21/2019
  [30293.586037] Workqueue: events_unbound async_run_entry_fn
  [30293.591331] Call trace:
  [30293.593770]  dump_backtrace+0x0/0x1f8
  [30293.597419]  show_stack+0x14/0x20
  [30293.600726]  dump_stack+0xc4/0xfc
  [30293.604032]  print_address_description+0x60/0x258
  [30293.608716]  kasan_report+0x164/0x1b8
  [30293.612366]  __asan_load8+0x84/0xa8
  [30293.615842]  hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.620961]  hisi_sas_I_T_nexus_reset+0xc4/0x170
  [30293.625562]  sas_ata_hard_reset+0x88/0x178
  [30293.629646]  ata_do_reset.constprop.6+0x80/0x90
  [30293.634160]  ata_eh_reset+0x71c/0x10e8
  [30293.637897]  ata_eh_recover+0x3d0/0x1a80
  [30293.641804]  ata_do_eh+0x50/0xd0
  [30293.645020]  ata_std_error_handler+0x78/0xa8
  [30293.649273]  ata_scsi_port_error_handler+0x288/0x930
  [30293.654216]  async_sas_ata_eh+0x68/0x90
  [30293.658040]  async_run_entry_fn+0x7c/0x1c0
  [30293.662121]  process_one_work+0x3c0/0x878
  [30293.666115]  worker_thread+0x70/0x670
  [30293.669762]  kthread+0x1b0/0x1b8
  [30293.672978]  ret_from_fork+0x10/0x18
  [30293.676541] 
  [30293.678027] Allocated by task 16690:
  [30293.681593]  __kasan_kmalloc.isra.0+0xd4/0x188
  [30293.686018]  kasan_kmalloc+0xc/0x18
  [30293.689496]  __kmalloc_node_track_caller+0x5c/0x98
  [30293.694270]  devm_kmalloc+0x44/0xb8
  [30293.697746]  hisi_sas_v3_probe+0x2ec/0x698
  [30293.701828]  local_pci_probe+0x74/0xf0
  [30293.705562]  work_for_cpu_fn+0x2c/0x48
  [30293.709300]  process_one_work+0x3c0/0x878
  [30293.713294]  worker_thread+0x400/0x670
  [30293.717027]  kthread+0x1b0/0x1b8
  [30293.720241]  ret_from_fork+0x10/0x18
  [30293.723801] 
  [30293.725287] Freed by task 16227:
  [30293.728503]  __kasan_slab_free+0x108/0x210
  [30293.732583]  kasan_slab_free+0x10/0x18
  [30293.736318]  kfree+0x74/0x150
  [30293.739276]  devres_free+0x34/0x48
  [30293.742665]  devres_release+0x38/0x60
  [30293.746313]  devm_pinctrl_put+0x34/0x58
  [30293.750136]  pinctrl_bind_pins+0x164/0x248
  [30293.754214]  really_probe+0xc0/0x3b0
  [30293.75]  driver_probe_device+0x70/0x138
  [30293.761944]  __device_attach_driver+0xc0/0xe0
  [30293.766285]  bus_for_each_drv+0xcc/0x150
  [30293.770194]  __device_attach+0x154/0x1c0
  [30293.774101]  device_initial_probe+0x10/0x18
  [30293.778270]  bus_probe_device+0xec/0x100
  [30293.782178]  device_ad

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

[Ubuntu Kernel Bot]

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

apport-collect 1853992

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

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

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

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

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

Title:
  [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Bug Description]
  sas kasan test will produce this out bounds in sas module

  [Steps to Reproduce]
  1) enbale this kasn
  2)
  3)

  [Actual Results]
  30293.504016] sas: ata464: end_device-2:2:6: dev error handler
  [30293.504041] sas: ata465: end_device-2:2:7: dev error handler
  [30293.504059] sas: ata466: end_device-2:2:8: dev error handler
  [30293.538746] 
==
  [30293.550672] BUG: KASAN: slab-out-of-bounds in 
hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.558642] Read of size 8 at addr b72e47233540 by task 
kworker/u193:3/79165
  [30293.566004] 
  [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB  O 
 5.1.0-rc1-g7a3fab8-dirty #1
  [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 
CS V3.B010.01 06/21/2019
  [30293.586037] Workqueue: events_unbound async_run_entry_fn
  [30293.591331] Call trace:
  [30293.593770]  dump_backtrace+0x0/0x1f8
  [30293.597419]  show_stack+0x14/0x20
  [30293.600726]  dump_stack+0xc4/0xfc
  [30293.604032]  print_address_description+0x60/0x258
  [30293.608716]  kasan_report+0x164/0x1b8
  [30293.612366]  __asan_load8+0x84/0xa8
  [30293.615842]  hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.620961]  hisi_sas_I_T_nexus_reset+0xc4/0x170
  [30293.625562]  sas_ata_hard_reset+0x88/0x178
  [30293.629646]  ata_do_reset.constprop.6+0x80/0x90
  [30293.634160]  ata_eh_reset+0x71c/0x10e8
  [30293.637897]  ata_eh_recover+0x3d0/0x1a80
  [30293.641804]  ata_do_eh+0x50/0xd0
  [30293.645020]  ata_std_error_handler+0x78/0xa8
  [30293.649273]  ata_scsi_port_error_handler+0x288/0x930
  [30293.654216]  async_sas_ata_eh+0x68/0x90
  [30293.658040]  async_run_entry_fn+0x7c/0x1c0
  [30293.662121]  process_one_work+0x3c0/0x878
  [30293.666115]  worker_thread+0x70/0x670
  [30293.669762]  kthread+0x1b0/0x1b8
  [30293.672978]  ret_from_fork+0x10/0x18
  [30293.676541] 
  [30293.678027] Allocated by task 16690:
  [30293.681593]  __kasan_kmalloc.isra.0+0xd4/0x188
  [30293.686018]  kasan_kmalloc+0xc/0x18
  [30293.689496]  __kmalloc_node_track_caller+0x5c/0x98
  [30293.694270]  devm_kmalloc+0x44/0xb8
  [30293.697746]  hisi_sas_v3_probe+0x2ec/0x698
  [30293.701828]  local_pci_probe+0x74/0xf0
  [30293.705562]  work_for_cpu_fn+0x2c/0x48
  [30293.709300]  process_one_work+0x3c0/0x878
  [30293.713294]  worker_thread+0x400/0x670
  [30293.717027]  kthread+0x1b0/0x1b8
  [30293.720241]  ret_from_fork+0x10/0x18
  [30293.723801] 
  [30293.725287] Freed by task 16227:
  [30293.728503]  __kasan_slab_free+0x108/0x210
  [30293.732583]  kasan_slab_free+0x10/0x18
  [30293.736318]  kfree+0x74/0x150
  [30293.739276]  devres_free+0x34/0x48
  [30293.742665]  devres_release+0x38/0x60
  [30293.746313]  devm_pinctrl_put+0x34/0x58
  [30293.750136]  pinctrl_bind_pins+0x164/0x248
  [30293.754214]  really_probe+0xc0/0x3b0
  [30293.75]  driver_probe_device+0x70/0x138
  [30293.761944]  __device_attach_driver+0xc0/0xe0
  [30293.766285]  bus_for_each_drv+0xcc/0x150
  [30293.770194]  __device_attach+0x154/0x1c0
  [30293.774101]  device_initial_probe+0x10/0x18
  [30293.778270]  bus_probe_device+0xec/0x100
  [30293.782178]  device_add+0x5f8/0x9b8
  [30293.785658]  scsi_sysfs_add_sdev+0xa4/0x310
  [30293.789825]  scsi_probe_and_add_lun+0xe60/0x1240
  [30293.794425]  __scsi_scan_target+0x1ac/0x780
  [30293.798591]  scsi_scan_target+0x134/0x140
  [30293.802586]  sas_rphy_add+0x1fc/0x2c8
  [30293.806234]  sas_probe

[Kernel-packages] [Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands

[Ike Panhc]

Patch has been sent for review

https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Fix Released

** Changed in: kunpeng920/ubuntu-19.10
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-19.10
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-19.04
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-19.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-18.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920
   Status: Triaged => In Progress

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

Title:
  [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  I/O error on blank Samsung SSD

  [Test Case]
  mkfs.ext4 on SSDs generates no I/O error

  [Fix]
  435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands

  [Regression Risk]
  Patch restricted to hisi_sas driver.

  
  "[Steps to Reproduce]
  mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error

  [Actual Results]
  Io error when the first time of mkfs.ext4

  [  745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8 
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  776.034612] sas: trying to find task 0x9656953a
  [  776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
  [  776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  776.049635] sas: trying to find task 0x975f5cdf
  [  776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  776.062900] sas: ata5: end_device-4:0: cmd error handler
  [  776.062914] sas: ata5: end_device-4:0: dev error handler
  [  776.062918] sas: ata6: end_device-4:1: dev error handler
  [  776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action 
0x6 frozen
  [  776.062924] sas: ata7: end_device-4:2: dev error handler
  [  776.062926] sas: ata8: end_device-4:3: dev error handler
  [  776.070548] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq 
dma 512 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.090638] ata5.00: status: { DRDY }
  [  776.094290] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq 
dma 512 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.114399] ata5.00: status: { DRDY }
  [  776.118051] ata5: hard resetting link
  [  776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
  [  776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
  [  776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
  [  776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
  [  776.451784] ata5.00: configured for UDMA/133
  [  776.456043] ata5.00: device reported invalid CHS sector 0
  [  776.461423] ata5.00: device reported invalid CHS sector 0
  [  776.466807] ata5: EH complete
  [  776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
  [  776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15 
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  806.740789] sas: Enter sas_scs

[Kernel-packages] [Bug 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  False positive test result in run_afpackettests from net in
  ubuntu_kernel_selftest

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  == Justification ==
  The run_afpackettests will be marked as passed regardless the return
  value of those sub-tests in the script:
  
  running psock_tpacket test
  
  [FAIL]
  selftests: run_afpackettests [PASS]

  Fix this by changing the return value for each tests.

  == Fix ==
  * 8c03557 (selftests/net: correct the return value for run_afpackettests)

  This patch has alreay landed on newer releases and D with stable
  updates.
  For X and B this can be backported with the same logic.

  == Test ==
  Tested on a Xenial KVM with this patch applied on these two trees, when
  the test failed the return value will be 1 instead of 0 as expected.

  == Regression Potential ==
  * Low, it's just reflecting the real test return value. We may see this
  test failing on some kernels but it's good as it's reporting a real bug.

  
  == Original Bug Report ==
  The run_afpackettests will be marked as passed regardless the return
  value of those sub-tests in the script:
  
  running psock_tpacket test
  
  [FAIL]
  selftests: run_afpackettests [PASS]

  Fix this by changing the return value for each tests.

  Patch sent to upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825778/+subscriptions

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

[Kernel-packages] [Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

[Ike Panhc]

Patch has been sent for review

https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Fix Released

** Changed in: kunpeng920/ubuntu-18.04
   Status: New => In Progress

** Changed in: kunpeng920/ubuntu-18.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-19.04
   Status: New => In Progress

** Changed in: kunpeng920/ubuntu-19.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-19.10
   Status: New => In Progress

** Changed in: kunpeng920/ubuntu-19.10
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920
   Status: New => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Fix Committed => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: ubuntu-18.04.5 => None

** Changed in: kunpeng920/ubuntu-18.04-hwe
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Potential NULL-pointer dereference.

  [Test Case]
  No known test case, but the issue is clear from code reading.

  [Fix]
  445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

  [Regression Risk]
  Patch restricted to hisi_sas driver.


  [Bug Description]
  sas kasan test will produce this out bounds in sas module

  [Steps to Reproduce]
  1) enbale this kasn
  2)
  3)

  [Actual Results]
  30293.504016] sas: ata464: end_device-2:2:6: dev error handler
  [30293.504041] sas: ata465: end_device-2:2:7: dev error handler
  [30293.504059] sas: ata466: end_device-2:2:8: dev error handler
  [30293.538746] 
==
  [30293.550672] BUG: KASAN: slab-out-of-bounds in 
hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.558642] Read of size 8 at addr b72e47233540 by task 
kworker/u193:3/79165
  [30293.566004]
  [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB  O 
 5.1.0-rc1-g7a3fab8-dirty #1
  [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 
CS V3.B010.01 06/21/2019
  [30293.586037] Workqueue: events_unbound async_run_entry_fn
  [30293.591331] Call trace:
  [30293.593770]  dump_backtrace+0x0/0x1f8
  [30293.597419]  show_stack+0x14/0x20
  [30293.600726]  dump_stack+0xc4/0xfc
  [30293.604032]  print_address_description+0x60/0x258
  [30293.608716]  kasan_report+0x164/0x1b8
  [30293.612366]  __asan_load8+0x84/0xa8
  [30293.615842]  hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.620961]  hisi_sas_I_T_nexus_reset+0xc4/0x170
  [30293.625562]  sas_ata_hard_reset+0x88/0x178
  [30293.629646]  ata_do_reset.constprop.6+0x80/0x90
  [30293.634160]  ata_eh_reset+0x71c/0x10e8
  [30293.637897]  ata_eh_recover+0x3d0/0x1a80
  [30293.641804]  ata_do_eh+0x50/0xd0
  [30293.645020]  ata_std_error_handler+0x78/0xa8
  [30293.649273]  ata_scsi_port_error_handler+0x288/0x930
  [30293.654216]  async_sas_ata_eh+0x68/0x90
  [30293.658040]  async_run_entry_fn+0x7c/0x1c0
  [30293.662121]  process_one_work+0x3c0/0x878
  [30293.666115]  worker_thread+0x70/0x670
  [30293.669762]  kthread+0x1b0/0x1b8
  [30293.672978]  ret_from_fork+0x10/0x18
  [30293.676541]
  [30293.678027] Allocated by task 16690:
  [30293.681593]  __kasan_kmalloc.isra.0+0xd4/0x188
  [30293.686018]  kasan_kmalloc+0xc/0x18
  [30293.689496]  __kmalloc_node_track_caller+0x5c/0x98
  [30293.694270]  devm_kmalloc+0x44/0xb8
  [30293.697746]  hisi_sas_v3_probe+0x2ec/0x698
  [30293.701828]  local_pci_probe+0x74/0xf0
  [30293.705562]  work_for_cpu_fn+0x2c/0x48
  [30293.709300]  process_one_work+0x3c0/0x878
  [30293.713294]  worker_thread+0x400/0x670
  [30293.717027]  kthread+0x1b0/0x1b8
  [30293.720241]  ret_from_fork+0x10/0x18
  [30293.723801]
  [30293.725287] Freed by task 16227:
  [30293.728503]  __kasan_slab_free+0x108/0x210
  [30293.732583]  kasan_slab_free+0x10/0x18
  [30293.736318]  kfree+0x74/0x150
  [30293.739276]  devres_free+0x34/0x48
  [30293.742665]  devres_release+0x38/0x60
  [30293.746313]  devm_pinctrl_put+0x34/0x58
  [30293.750136

[Kernel-packages] [Bug 1857307] Re: Wireless wouldn't turn on.

[You-Sheng Yang]

Hi, didn't find something directly related from above WMI events. Could
you try following to kernel parameters sets separately:

1. "module_blacklist=wmi": this will disable wmi completely

2. "wmi.debug_event=1 wmi.debug_dump_wdg=1": this will enable wmi debug
info.

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

Title:
  Wireless wouldn't turn on.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I used Ubuntu on this machine starting with 16.04 LTS. The network PCI
  never worked but USB D-Link card did work... up to recently and then
  it stopped. I installed 18.04 LTS -- it read Airplane Mode On and
  nothing could be done. rfkill gave me phy0 soft block no, hard block
  yes. But f8+Fn only caused a pop-up message that Airplane Mod On or
  Off but not in the status bar -- there it was always on with an
  instruction to use hardware switch and setting wireless never worked.
  I installed KDE over Ubuntu 19 now and Airplane Mode can be turned On
  and Off but WiFi never turns on.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anatoly1081 F pulseaudio
   /dev/snd/pcmC0D0p:   anatoly1081 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Sun Dec 22 20:58:33 2019
  InstallationDate: Installed on 2019-12-20 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 
6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E 
SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20LQS0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=5f3b3bd7-d68f-47e0-99e0-7d5c8befd27a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0TET37W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LQS0
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K13476 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0TET37W(1.11):bd03/01/2018:svnLENOVO:pn20LQS0:pvrThinkPad11e5thGen:rvnLENOVO:rn20LQS0:rvrSDK0K13476WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 11e 5th Gen
  dmi.product.name: 20LQS0
  dmi.product.sku: LENOVO_MT_20LQ_BU_Think_FM_ThinkPad 11e 5th Gen
  dmi.product.version: ThinkPad 11e 5th Gen
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it

[Ike Panhc]

Patch has been sent for review

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

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

** Changed in: kunpeng920/ubuntu-19.04
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-18.04
   Status: Triaged => In Progress

** Changed in: kunpeng920
   Status: Triaged => In Progress

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

Title:
  scsi: hisi_sas: Check sas_port before using it

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Potential NULL-pointer dereference.

  [Test Case]
  No known test case, but the issue is clear from code reading.

  [Fix]
  8c39673d5474b scsi: hisi_sas: Check sas_port before using it

  [Regression Risk]
  Patch restricted to hisi_sas driver.

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

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

[Kernel-packages] [Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset

[Ike Panhc]

https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html

** Description changed:

+ [Impact]
+ Some SAS devices is gone when recovering
+ 
+ [Test Case]
+ No known test case, stress test on SAS deivce.
+ 
+ [Fix]
+ e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host 
reset
+ 
+ [Regression Risk]
+ Patch restricted to hisi_sas driver.
+ 
+ 
  "[Steps to Reproduce]
  1. Close all the PHYS;
- 2. Inject error; 
- 3. Open one PHY; 
+ 2. Inject error;
+ 3. Open one PHY;
  
  [Actual Results]
  Some disk will be lost
  
  [Expected Results]
  No disk will be lost
  
  [Reproducibility]
  occasionally
  
  [Additional information]
  Hardware: D06 CS
  Firmware: NA+I59
  Kernel: NA
  
  [Resolution]
  When init device for SAS disks, it will send TMF IO to clear disks. At that
  time TMF IO is broken by some operations such as injecting controller reset
  from HW RAs event, the TMF IO will be timeout, and at last device will be
  gone. Print is as followed:
  
  hisi_sas_v3_hw :74:02.0: dev[240:1] found
  ...
  hisi_sas_v3_hw :74:02.0: controller resetting...
  hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11
  hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11
  hisi_sas_v3_hw :74:02.0: controller reset complete
  hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done
  hisi_sas_v3_hw :74:02.0: dev[240:1] is gone
  sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d,
  error:5
  
  To improve the reliability, retry TMF IO max of 3 times for SAS disks which
  is the same as softreset does."
  
  scsi: hisi_sas: Fix the conflict between device gone and host reset

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

Title:
  [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and
  host reset

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Some SAS devices is gone when recovering

  [Test Case]
  No known test case, stress test on SAS deivce.

  [Fix]
  e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host 
reset

  [Regression Risk]
  Patch restricted to hisi_sas driver.

  
  "[Steps to Reproduce]
  1. Close all the PHYS;
  2. Inject error;
  3. Open one PHY;

  [Actual Results]
  Some disk will be lost

  [Expected Results]
  No disk will be lost

  [Reproducibility]
  occasionally

  [Additional information]
  Hardware: D06 CS
  Firmware: NA+I59
  Kernel: NA

  [Resolution]
  When init device for SAS disks, it will send TMF IO to clear disks. At that
  time TMF IO is broken by some operations such as injecting controller reset
  from HW RAs event, the TMF IO will be timeout, and at last device will be
  gone. Print is as followed:

  hisi_sas_v3_hw :74:02.0: dev[240:1] found
  ...
  hisi_sas_v3_hw :74:02.0: controller resetting...
  hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11
  hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11
  hisi_sas_v3_hw :74:02.0: controller reset complete
  hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done
  hisi_sas_v3_hw :74:02.0: dev[240:1] is gone
  sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d,
  error:5

  To improve the reliability, retry TMF IO max of 3 times for SAS disks which
  is the same as softreset does."

  scsi: hisi_sas: Fix the conflict between device gone and host reset

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

-- 
Mailing list: https://launch

[Kernel-packages] [Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset

[Ike Panhc]

Patch has been sent for review

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-19.10
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-19.10
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-19.04
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-19.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04
   Status: Triaged => In Progress

** Changed in: kunpeng920/ubuntu-18.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920
   Status: Triaged => In Progress

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

Title:
  [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and
  host reset

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Some SAS devices is gone when recovering

  [Test Case]
  No known test case, stress test on SAS deivce.

  [Fix]
  e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host 
reset

  [Regression Risk]
  Patch restricted to hisi_sas driver.

  
  "[Steps to Reproduce]
  1. Close all the PHYS;
  2. Inject error;
  3. Open one PHY;

  [Actual Results]
  Some disk will be lost

  [Expected Results]
  No disk will be lost

  [Reproducibility]
  occasionally

  [Additional information]
  Hardware: D06 CS
  Firmware: NA+I59
  Kernel: NA

  [Resolution]
  When init device for SAS disks, it will send TMF IO to clear disks. At that
  time TMF IO is broken by some operations such as injecting controller reset
  from HW RAs event, the TMF IO will be timeout, and at last device will be
  gone. Print is as followed:

  hisi_sas_v3_hw :74:02.0: dev[240:1] found
  ...
  hisi_sas_v3_hw :74:02.0: controller resetting...
  hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11
  hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11
  hisi_sas_v3_hw :74:02.0: controller reset complete
  hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done
  hisi_sas_v3_hw :74:02.0: dev[240:1] is gone
  sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d,
  error:5

  To improve the reliability, retry TMF IO max of 3 times for SAS disks which
  is the same as softreset does."

  scsi: hisi_sas: Fix the conflict between device gone and host reset

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

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

[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it

[Ike Panhc]

https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.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/1855952

Title:
  scsi: hisi_sas: Check sas_port before using it

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Potential NULL-pointer dereference.

  [Test Case]
  No known test case, but the issue is clear from code reading.

  [Fix]
  8c39673d5474b scsi: hisi_sas: Check sas_port before using it

  [Regression Risk]
  Patch restricted to hisi_sas driver.

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

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

[Kernel-packages] [Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands

[Ike Panhc]

** Description changed:

+ [Impact]
+ I/O error on blank Samsung SSD
+ 
+ [Test Case]
+ mkfs.ext4 on SSDs generates no I/O error
+ 
+ [Fix]
+ 435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands
+ 
+ [Regression Risk]
+ Patch restricted to hisi_sas driver.
+ 
+ 
  "[Steps to Reproduce]
  mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error
  
  [Actual Results]
  Io error when the first time of mkfs.ext4
  
  [  745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8 
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  776.034612] sas: trying to find task 0x9656953a
  [  776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
  [  776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  776.049635] sas: trying to find task 0x975f5cdf
  [  776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  776.062900] sas: ata5: end_device-4:0: cmd error handler
  [  776.062914] sas: ata5: end_device-4:0: dev error handler
  [  776.062918] sas: ata6: end_device-4:1: dev error handler
  [  776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action 
0x6 frozen
  [  776.062924] sas: ata7: end_device-4:2: dev error handler
  [  776.062926] sas: ata8: end_device-4:3: dev error handler
  [  776.070548] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq 
dma 512 out
-  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.090638] ata5.00: status: { DRDY }
  [  776.094290] ata5.00: failed command: SEND FPDMA QUEUED
  [  776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq 
dma 512 out
-  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  776.114399] ata5.00: status: { DRDY }
  [  776.118051] ata5: hard resetting link
  [  776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
  [  776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
  [  776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
  [  776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
  [  776.451784] ata5.00: configured for UDMA/133
  [  776.456043] ata5.00: device reported invalid CHS sector 0
  [  776.461423] ata5.00: device reported invalid CHS sector 0
  [  776.466807] ata5: EH complete
  [  776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
  [  776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15 
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error 
info: 0x0 0x0 0x1 0x0
  [  806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
  [  806.746604] sas: trying to find task 0x975f5cdf
  [  806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
  [  806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
  [  806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
  [  806.761582] sas: trying to find task 0x9656953a
  [  806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
  [  806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
  [  806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
  [  806.774852] sas: ata5: end_device-4:0: cmd error handler
  [  806.774864] sas: ata5: end_device-4:0: dev error handler
  [  806.774868] sas: ata6: end_device-4:1: dev error handler
  [  806.774870] ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 
frozen
  [  806.774873] ata5.00: failed command: SEND FPDMA QUEUED
  [  806.774875] sas: ata7: end_device-4:2: dev error handler
  [  806.774878] sas: ata8: end_device-4:3: dev error handler
  [  806.787013] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 0 ncq dma 
512 out
-  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  806.801900] ata5.00: status: { DRDY }
  [  806.805554] ata5.00: failed command: SEND FPDMA QUEUED
  [  806.810674] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 1 ncq dma 
512 out
-  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  [  806.825582] ata5.00: status: { DRDY }
  [  806.829237] ata5: hard resetting link
  [  806.834445] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
  [  806.840856] hisi_sas_v3_hw :74

[Kernel-packages] [Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

[Ike Panhc]

** Description changed:

+ [Impact]
+ Potential NULL-pointer dereference.
+ 
+ [Test Case]
+ No known test case, but the issue is clear from code reading.
+ 
+ [Fix]
+ 445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
+ 
+ [Regression Risk]
+ Patch restricted to hisi_sas driver.
+ 
+ 
  [Bug Description]
  sas kasan test will produce this out bounds in sas module
  
  [Steps to Reproduce]
  1) enbale this kasn
  2)
  3)
  
  [Actual Results]
  30293.504016] sas: ata464: end_device-2:2:6: dev error handler
  [30293.504041] sas: ata465: end_device-2:2:7: dev error handler
  [30293.504059] sas: ata466: end_device-2:2:8: dev error handler
  [30293.538746] 
==
  [30293.550672] BUG: KASAN: slab-out-of-bounds in 
hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.558642] Read of size 8 at addr b72e47233540 by task 
kworker/u193:3/79165
- [30293.566004] 
+ [30293.566004]
  [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB  O 
 5.1.0-rc1-g7a3fab8-dirty #1
  [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 
CS V3.B010.01 06/21/2019
  [30293.586037] Workqueue: events_unbound async_run_entry_fn
  [30293.591331] Call trace:
  [30293.593770]  dump_backtrace+0x0/0x1f8
  [30293.597419]  show_stack+0x14/0x20
  [30293.600726]  dump_stack+0xc4/0xfc
  [30293.604032]  print_address_description+0x60/0x258
  [30293.608716]  kasan_report+0x164/0x1b8
  [30293.612366]  __asan_load8+0x84/0xa8
  [30293.615842]  hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.620961]  hisi_sas_I_T_nexus_reset+0xc4/0x170
  [30293.625562]  sas_ata_hard_reset+0x88/0x178
  [30293.629646]  ata_do_reset.constprop.6+0x80/0x90
  [30293.634160]  ata_eh_reset+0x71c/0x10e8
  [30293.637897]  ata_eh_recover+0x3d0/0x1a80
  [30293.641804]  ata_do_eh+0x50/0xd0
  [30293.645020]  ata_std_error_handler+0x78/0xa8
  [30293.649273]  ata_scsi_port_error_handler+0x288/0x930
  [30293.654216]  async_sas_ata_eh+0x68/0x90
  [30293.658040]  async_run_entry_fn+0x7c/0x1c0
  [30293.662121]  process_one_work+0x3c0/0x878
  [30293.666115]  worker_thread+0x70/0x670
  [30293.669762]  kthread+0x1b0/0x1b8
  [30293.672978]  ret_from_fork+0x10/0x18
- [30293.676541] 
+ [30293.676541]
  [30293.678027] Allocated by task 16690:
  [30293.681593]  __kasan_kmalloc.isra.0+0xd4/0x188
  [30293.686018]  kasan_kmalloc+0xc/0x18
  [30293.689496]  __kmalloc_node_track_caller+0x5c/0x98
  [30293.694270]  devm_kmalloc+0x44/0xb8
  [30293.697746]  hisi_sas_v3_probe+0x2ec/0x698
  [30293.701828]  local_pci_probe+0x74/0xf0
  [30293.705562]  work_for_cpu_fn+0x2c/0x48
  [30293.709300]  process_one_work+0x3c0/0x878
  [30293.713294]  worker_thread+0x400/0x670
  [30293.717027]  kthread+0x1b0/0x1b8
  [30293.720241]  ret_from_fork+0x10/0x18
- [30293.723801] 
+ [30293.723801]
  [30293.725287] Freed by task 16227:
  [30293.728503]  __kasan_slab_free+0x108/0x210
  [30293.732583]  kasan_slab_free+0x10/0x18
  [30293.736318]  kfree+0x74/0x150
  [30293.739276]  devres_free+0x34/0x48
  [30293.742665]  devres_release+0x38/0x60
  [30293.746313]  devm_pinctrl_put+0x34/0x58
  [30293.750136]  pinctrl_bind_pins+0x164/0x248
  [30293.754214]  really_probe+0xc0/0x3b0
  [30293.75]  driver_probe_device+0x70/0x138
  [30293.761944]  __device_attach_driver+0xc0/0xe0
  [30293.766285]  bus_for_each_drv+0xcc/0x150
  [30293.770194]  __device_attach+0x154/0x1c0
  [30293.774101]  device_initial_probe+0x10/0x18
  [30293.778270]  bus_probe_device+0xec/0x100
  [30293.782178]  device_add+0x5f8/0x9b8
  [30293.785658]  scsi_sysfs_add_sdev+0xa4/0x310
  [30293.789825]  scsi_probe_and_add_lun+0xe60/0x1240
  [30293.794425]  __scsi_scan_target+0x1ac/0x780
  [30293.798591]  scsi_scan_target+0x134/0x140
  [30293.802586]  sas_rphy_add+0x1fc/0x2c8
  [30293.806234]  sas_probe_devices+0x10c/0x1e8
  [30293.810313]  sas_discover_domain+0x754/0x998
  [30293.814567]  process_one_work+0x3c0/0x878
  [30293.818560]  worker_thread+0x70/0x670
  [30293.822207]  kthread+0x1b0/0x1b8
  [30293.825423]  ret_from_fork+0x10/0x18
- [30293.828983] 
+ [30293.828983]
  [30293.830473] The buggy address belongs to the object at b72e47233480
  [30293.830473]  which belongs to the cache kmalloc-256 of size 256
  [30293.842934] The buggy address is located 192 bytes inside of
  [30293.842934]  256-byte region [b72e47233480, b72e47233580)
  [30293.854617] The buggy address belongs to the page:
  [30293.859388] page:7edcb91c8cc0 count:1 mapcount:0 
mapping:972e5f000200 index:0x0
  [30293.867360] flags: 0xdfffe200(slab)
  [30293.871533] raw: dfffe200 7edcb915ca48 7edcb93fdc08 
972e5f000200
  
  [Expected Results]
  
  [Reproducibility]
  
  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):
  
  [Resolution]
  
  scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

-- 
You received this bug notification because you are a member of Kernel
P