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 1916468

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 Focal)
       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/1916468

Title:
  powerpc/eeh-basic.sh in kselftest make P8 node stopped working

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  Issue found on node entei with Focal kernel.

  When trying to run this test, it will try to break 4 devices on Focal,
  and one of them is using the AHCI driver:

  $ sudo ./eeh-basic.sh 
  0000:00:00.0, Skipped: bridge
  0001:00:00.0, Skipped: bridge
  0020:00:00.0, Skipped: bridge
  0021:00:00.0, Skipped: bridge
  0021:01:00.0, Skipped: bridge
  0021:02:01.0, Skipped: bridge
  0021:02:08.0, Skipped: bridge
  0021:02:09.0, Skipped: bridge
  0021:02:0a.0, Skipped: bridge
  0021:02:0b.0, Skipped: bridge
  0021:02:0c.0, Skipped: bridge
  0021:0d:00.0, Added
  0021:0e:00.0, Added
  0021:0f:00.0, Skipped: bridge
  0021:10:00.0, Added
  0022:00:00.0, Skipped: bridge
  0022:01:00.0, Added
  Found 4 breakable devices...
  Breaking 0021:0d:00.0...
  0021:0d:00.0, waited 0/60
  0021:0d:00.0, waited 1/60
  0021:0d:00.0, waited 2/60
  0021:0d:00.0, waited 3/60
  0021:0d:00.0, waited 4/60
  0021:0d:00.0, waited 5/60
  0021:0d:00.0, waited 6/60
  0021:0d:00.0, waited 7/60
  0021:0d:00.0, waited 8/60
  0021:0d:00.0, Recovered after 9 seconds
  Breaking 0021:0e:00.0...
  0021:0e:00.0, waited 0/60
  0021:0e:00.0, waited 1/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 2/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 3/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  ....
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 59/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 60/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, Failed to recover!
  Breaking 0021:10:00.0...
  Skipping 0021:10:00.0, Initial PE state is not ok
  Breaking 0022:01:00.0...
  Skipping 0022:01:00.0, Initial PE state is not ok
  3 devices failed to recover (4 tested)
  ./eeh-basic.sh: 81: lspci: Input/output error
  ./eeh-basic.sh: 81: diff: Input/output error
  ./eeh-basic.sh: 82: rm: Input/output error
  ./eeh-basic.sh: 84: test: 3: unexpected operator

  With the driver failed to recovery, the system will start acting up.
  $ ls
  ls: command not found

  And drop into read-only state, dmesg can be found in the attachment.

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

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

Reply via email to