[Bug 1967493] Re: pl2303 serial adapter not recognized

2022-06-06 Thread Po-Hsu Lin
Hello,
thanks for the bug report, 
I have built some test kernels with this patch:
https://people.canonical.com/~phlin/kernel/lp-1967493-pl2303/

Can you give them a try? Thank you.

The kernel version for F-5.13 should be:
5.13.0-47-generic #52~20.04.1+lp1967493

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967493

Title:
  pl2303 serial adapter not recognized

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967493] Re: pl2303 serial adapter not recognized

2022-06-06 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967493

Title:
  pl2303 serial adapter not recognized

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967493] Re: pl2303 serial adapter not recognized

2022-06-06 Thread Po-Hsu Lin
** Package changed: linux-signed-hwe-5.13 (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967493

Title:
  pl2303 serial adapter not recognized

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought

2022-06-01 Thread Po-Hsu Lin
Found on node vought with F-OEM 5.14.0-1040.44

** Tags added: 5.14 focal oem sru-20220509

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959215

Title:
  unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to
  handle page fault for address: 1cc8" on Impish with node
  vought

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1959215/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969624] Re: kernel NULL pointer dereference while removing floppy module

2022-05-30 Thread Po-Hsu Lin
This issue does not exist in mainline 5.16-rc1 [1] but exist in 5.15

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.16-rc1/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969624

Title:
  kernel NULL pointer dereference while removing floppy module

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-30 Thread Po-Hsu Lin
** Description changed:

  [Impact]
  test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
  will fail on 5.13 kernel with:
  
    # selftests: net: test_vxlan_under_vrf.sh
    # Checking HV connectivity [ OK ]
    # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
    not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  Note that this test is not failing on F-oem-5.14 but it's better to
  have corresponding patches applied to reduce the maintenance cost
  in the future.
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
- Only I-5.13 and F-oem-5.14 need these patches.
+ Only F-5.4, I-5.13 and F-oem-5.14 need these patches.
  
  First patch (e7e4785f):
-   - Can be cherry-picked to Impish 5.13
+   - Can be cherry-picked to F-5.4 / Impish 5.13
    - Can be cherry-picked to F-oem-5.14.
  Second patch (b50d3b46):
-   - Can be cherry-picked to Impish 5.13 (-C2 is required while
+   - Can be cherry-picked to F-5.4 / Impish 5.13 (-C2 is required while
  applying it due to our SAUCE patches)
    - F-oem-5.14 has already got this one applied.
  
  The reason why we need the second patch is that after the first one
  got applied, we will see another failure, which we made it an expected
  failure (XFAIL) with SAUCE patches:
    Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
  
  [Test]
  With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
  5.13 and F-oem-5.14 without any issue:
    Checking HV connectivity [ OK ]
    Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
    Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. But if these fixes are incorrect we will see
  failures in our regression-testing report. The worst scenario is
  getting false-negative results.
  
  v2: Update cover-letter content and target in patch title to make it
  easier to read.
  
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-30 Thread Po-Hsu Lin
https://lists.ubuntu.com/archives/kernel-team/2022-May/130739.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-30 Thread Po-Hsu Lin
** Description changed:

  [Impact]
- test_vxlan_under_vrf.sh should not be failing anymore (unless it's a
- kernel config related issue) with patches submitted for fixing this 
- test in bug 1871015.
+ test_vxlan_under_vrf.sh should not be failing anymore with patches
+ submitted to fix it in bug 1871015 (unless it's a kernel config
+ related issue).
  
- We should remove the SAUCE patches that mark "vxlan_under_vrf" test
- failure as expected failure to catch regressions in the future.
+ With the regression-testing result hinting system available, we should
+ remove the SAUCE patches that mark "vxlan_under_vrf" test failure as
+ an expected failure to catch regressions in the future. This could
+ reduce maintenance cost as well.
  
  [Fix]
  Revert the following patches:
  * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default 
VRF an expected failure
  * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail
  
  [Test]
- Tested with F/I/J/F-oem-5.14/J-oem-5.17.
+ Patched test script tested with F/I/J/F-oem-5.14/J-oem-5.17. I have
+ also modify the test case to fail it deliberately to verify this
+ change, it works as expected.
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. We may see failures reported from this test in
  our SRU regression-testing report in the future, but it means we're
  doing the right thing.

** Description changed:

  [Impact]
  test_vxlan_under_vrf.sh should not be failing anymore with patches
  submitted to fix it in bug 1871015 (unless it's a kernel config
  related issue).
  
  With the regression-testing result hinting system available, we should
- remove the SAUCE patches that mark "vxlan_under_vrf" test failure as
+ remove the SAUCE patches that mark "underlay in a VRF" test failure as
  an expected failure to catch regressions in the future. This could
  reduce maintenance cost as well.
  
  [Fix]
  Revert the following patches:
  * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default 
VRF an expected failure
  * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail
  
  [Test]
  Patched test script tested with F/I/J/F-oem-5.14/J-oem-5.17. I have
  also modify the test case to fail it deliberately to verify this
  change, it works as expected.
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. We may see failures reported from this test in
  our SRU regression-testing report in the future, but it means we're
  doing the right thing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-27 Thread Po-Hsu Lin
** Description changed:

  [Impact]
- test_vxlan_under_vrf.sh should not be failing anymore (except if it's a 
config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 
1871015
+ test_vxlan_under_vrf.sh should not be failing anymore (unless it's a
+ kernel config related issue) with patches submitted for fixing this 
+ test in bug 1871015.
  
- We should remove the SAUCE patches that mark "vxlan_under_vrf" failure
- as expected failure to catch regressions in the future.
+ We should remove the SAUCE patches that mark "vxlan_under_vrf" test
+ failure as expected failure to catch regressions in the future.
  
  [Fix]
  Revert the following patches:
  * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default 
VRF an expected failure
  * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail
  
  [Test]
- 
+ Tested with F/I/J/F-oem-5.14/J-oem-5.17.
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. We may see failures reported from this test in
  our SRU regression-testing report in the future, but it means we're
  doing the right thing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-26 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
     Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-26 Thread Po-Hsu Lin
** Also affects: linux-oem-5.17 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.14 (Ubuntu Impish)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-5.17 (Ubuntu Focal)
   Status: New => Invalid

** Changed in: linux-oem-5.17 (Ubuntu Impish)
   Status: New => Invalid

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

** Tags added: focal impish jammy kinetic oem ubuntu-kernel-selftests

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
Just realized that Focal need this patch as well.

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-25 Thread Po-Hsu Lin
** Summary changed:

- Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of 
ubuntu_kernel_selftests
+ Remove SAUCE patches from test_vxlan_under_vrf.sh in net of 
ubuntu_kernel_selftests

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] Re: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-25 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.14 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.14 (Ubuntu Impish)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
V2 https://lists.ubuntu.com/archives/kernel-team/2022-May/130594.html

** Description changed:

  [Impact]
  test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
  will fail on 5.13 kernel with:
  
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but
  it's better to have corresponding patches applied to reduce the
  maintenance cost in the future.
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
  First patch (e7e4785f):
- Can be cherry-picked to Impish 5.13
- Can be cherry-picked to F-oem-5.14.
  Second patch (b50d3b46):
- Can be cherry-picked to Impish 5.13 (-C2 is required while
  applying it due to our SAUCE patches)
- F-oem-5.14 has already got this one applied.
-   - Can be cherry-picked to J-oem-5.17
  
  The reason why we need the second patch is that after the first one
  got applied, we will see another failure, which we made it an expected
  failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
  
  [Test]
  With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
- 5.13, F-oem-5.14 and J-oem-5.17 without any issue:
+ 5.13 and F-oem-5.14 without any issue:
Checking HV connectivity [ OK ]
Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. But if these fixes are incorrect we will see
  failures in our regression-testing report. The worst scenario is
  getting false-negative results.
  
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

** Description changed:

  [Impact]
  test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
  will fail on 5.13 kernel with:
  
-   # selftests: net: test_vxlan_under_vrf.sh
-   # Checking HV connectivity [ OK ]
-   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
-   not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
+   # selftests: net: test_vxlan_under_vrf.sh
+   # Checking HV connectivity [ OK ]
+   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
+   not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
- Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but
- it's better to have corresponding patches applied to reduce the
- maintenance cost in the future.
+ Note that this test is not failing on F-oem-5.14 but it's better to
+ have corresponding patches applied to reduce the maintenance cost
+ in the future.
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
  First patch (e7e4785f):
-   - Can be cherry-picked to Impish 5.13
-   - Can be cherry-picked to F-oem-5.14.
+   - Can be cherry-picked to Impish 5.13
+   - Can be cherry-picked to F-oem-5.14.
  Second patch (b50d3b46):
-   - Can be cherry-picked to Impish 5.13 (-C2 is required while
- applying it due to our SAUCE patches)
-   - F-oem-5.14 has already got this one applied.
+   - Can be cherry-picked to Impish 5.13 (-C2 is required while
+ applying it due to our SAUCE patches)
+   - F-oem-5.14 has already got this one applied.
  
  The reason why we need the second patch is that after the first one
  got applied, we will see another failure, which we made it an expected
  failure (XFAIL) with SAUCE patches:
-   Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
+   Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
  
  [Test]
  With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
  5.13 and F-oem-5.14 without any issue:
-   Checking HV connectivity [ OK ]
-   Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
-   Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
+   Checking HV connectivity [ OK ]
+   Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
+   Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. But if these fixes are incorrect we will see
  failures in our regression-testing report. The worst scenario is
  

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Description changed:

  [Impact]
  test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
  will fail on 5.13 kernel with:
  
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
+ Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but
+ it's better to have corresponding patches applied to reduce the
+ maintenance cost in the future.
+ 
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
- The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and
- F-oem-5.14.
+ First patch (e7e4785f):
+   - Can be cherry-picked to Impish 5.13
+   - Can be cherry-picked to F-oem-5.14.
+ Second patch (b50d3b46):
+   - Can be cherry-picked to Impish 5.13 (-C2 is required while
+ applying it due to our SAUCE patches)
+   - F-oem-5.14 has already got this one applied.
+   - Can be cherry-picked to J-oem-5.17
  
- Note that this test is not failing on F-oem-5.14, but it's better to
- have it applied to reduce the maintenance cost.
- 
- After the first patch was applied, we will need the second patch on
- Impish 5.13 to solve the another failure, which we made it an expected
+ The reason why we need the second patch is that after the first one
+ got applied, we will see another failure, which we made it an expected
  failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
  
- The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but
- must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has
- already got this one applied.
- 
  [Test]
  With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
- 5.13 and F-oem-5.14 without any issue:
+ 5.13, F-oem-5.14 and J-oem-5.17 without any issue:
Checking HV connectivity [ OK ]
Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. But if these fixes are incorrect we will see
  failures in our regression-testing report. The worst scenario is
  getting false-negative results.
  
- 
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975691] [NEW] Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

2022-05-25 Thread Po-Hsu Lin
Public bug reported:

[Impact]
test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config 
related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015

We should remove the SAUCE patches that mark "vxlan_under_vrf" failure
as expected failure to catch regressions in the future.

[Fix]
Revert the following patches:
* UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default 
VRF an expected failure
* UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail

[Test]


[Where problems could occur]
Change limit to test cases, should not have any real impact to any
kernel functions. We may see failures reported from this test in
our SRU regression-testing report in the future, but it means we're
doing the right thing.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress

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

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691

Title:
  Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
https://lists.ubuntu.com/archives/kernel-team/2022-May/130587.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Description changed:

  [Impact]
- The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests 
will fail on 5.13 kernel with:
+ test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
+ will fail on 5.13 kernel with:
  
-  # selftests: net: test_vxlan_under_vrf.sh
-  # Checking HV connectivity[ OK ]
-  # Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]
-  not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
+   # selftests: net: test_vxlan_under_vrf.sh
+   # Checking HV connectivity [ OK ]
+   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
+   not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
  The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and
  F-oem-5.14.
  
  Note that this test is not failing on F-oem-5.14, but it's better to
  have it applied to reduce the maintenance cost.
  
- After the first patch was applied, we will need the second patch on Impish 
5.13 to solve the another failure, which we made it an expected failure (XFAIL) 
with SAUCE patches:
- Check VM connectivity through VXLAN (underlay in a VRF)   [XFAIL]
+ After the first patch was applied, we will need the second patch on
+ Impish 5.13 to solve the another failure, which we made it an expected
+ failure (XFAIL) with SAUCE patches:
+   Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
  
- The second patch (b50d3b46) can be cherry-picked with must be applied
- with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one
- applied.
+ The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but
+ must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has
+ already got this one applied.
  
  [Test]
- Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test 
can pass without any issue:
- Checking HV connectivity   [ OK ]
- Check VM connectivity through VXLAN (underlay in the default VRF)  [ OK ]
- Check VM connectivity through VXLAN (underlay in a VRF)[ OK ]
+ With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
+ 5.13 and F-oem-5.14 without any issue:
+   Checking HV connectivity [ OK ]
+   Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
+   Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
  
  [Where problems could occur]
- Change limit to test cases, should not have any real impact to kernel 
functions. But if these fixes are incorrect we will see failures in our 
regression-testing report. The worst scenario is getting false-negative results.
+ Change limit to test cases, should not have any real impact to any
+ kernel functions. But if these fixes are incorrect we will see
+ failures in our regression-testing report. The worst scenario is
+ getting false-negative results.
+ 
  
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Description changed:

  [Impact]
  The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests 
will fail on 5.13 kernel with:
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity[ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]
   not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
- The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
+ The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and
+ F-oem-5.14.
  
  Note that this test is not failing on F-oem-5.14, but it's better to
  have it applied to reduce the maintenance cost.
  
  After the first patch was applied, we will need the second patch on Impish 
5.13 to solve the another failure, which we made it an expected failure (XFAIL) 
with SAUCE patches:
  Check VM connectivity through VXLAN (underlay in a VRF)   [XFAIL]
  
- F-oem-5.14 has already got this one applied.
+ The second patch (b50d3b46) can be cherry-picked with must be applied
+ with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one
+ applied.
  
  [Test]
  Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test 
can pass without any issue:
  Checking HV connectivity   [ OK ]
  Check VM connectivity through VXLAN (underlay in the default VRF)  [ OK ]
  Check VM connectivity through VXLAN (underlay in a VRF)[ OK ]
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to kernel 
functions. But if these fixes are incorrect we will see failures in our 
regression-testing report. The worst scenario is getting false-negative results.
  
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Description changed:

  [Impact]
  The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests 
will fail on 5.13 kernel with:
  
-  Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
-  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
-  make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
-  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
-INSTALL ./usr/include
-  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
-  TAP version 13
-  1..1
-  # selftests: net: test_vxlan_under_vrf.sh
-  # Checking HV connectivity[ OK ]
-  # Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]
-  not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 
+  Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
+  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
+  make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
+  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
+    INSTALL ./usr/include
+  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
+  TAP version 13
+  1..1
+  # selftests: net: test_vxlan_under_vrf.sh
+  # Checking HV connectivity[ OK ]
+  # Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]
+  not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
- * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case 
+ * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
  The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
  
  Note that this test is not failing on F-oem-5.14, but it's better to
  have it applied to reduce the maintenance cost.
  
  After the first patch was applied, we will need the second patch to solve the 
another failure on Impish 5.13, which we made it an expected failure (XFAIL) 
with SAUCE patches:
  Check VM connectivity through VXLAN (underlay in a VRF)   [XFAIL]
  
  [Test]
  Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test 
can pass without any issue:
- 
+ Checking HV connectivity   [ OK ]
+ Check VM connectivity through VXLAN (underlay in the default VRF)  [ OK ]
+ Check VM connectivity through VXLAN (underlay in a VRF)[ OK ]
  
  [Where problems could occur]
+ Change limit to test cases, should not have any real impact to kernel 
functions. But if these fixes are incorrect we will see failures in our 
regression-testing report. The worst scenario is getting false-negative results.
  
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

** Description changed:

  [Impact]
  The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests 
will fail on 5.13 kernel with:
  
-  Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
-  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
-  make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
-  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
-    INSTALL ./usr/include
-  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
-  TAP version 13
-  1..1
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity[ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]
   not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
  
  The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
  
  Note that this test is not failing on F-oem-5.14, but it's better to
  have it applied to reduce the maintenance cost.
  
  After the first patch was applied, we will need the second patch to solve the 
another failure on Impish 5.13, which we made it an expected failure (XFAIL) 
with SAUCE patches:
  Check VM connectivity through VXLAN (underlay in a VRF)   [XFAIL]
  
  [Test]
  Patch tested on Impish 5.13 and 

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Description changed:

  [Impact]
+ The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests 
will fail on 5.13 kernel with:
  
+  Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
+  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
+  make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
+  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
+INSTALL ./usr/include
+  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
+  TAP version 13
+  1..1
+  # selftests: net: test_vxlan_under_vrf.sh
+  # Checking HV connectivity[ OK ]
+  # Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]
+  not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 
  
  [Fix]
+ * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
+ * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case 
  
+ The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
+ 
+ Note that this test is not failing on F-oem-5.14, but it's better to
+ have it applied to reduce the maintenance cost.
+ 
+ After the first patch was applied, we will need the second patch to solve the 
another failure on Impish 5.13, which we made it an expected failure (XFAIL) 
with SAUCE patches:
+ Check VM connectivity through VXLAN (underlay in a VRF)   [XFAIL]
  
  [Test]
+ Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test 
can pass without any issue:
  
  
  [Where problems could occur]
  
  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Summary changed:

- test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H 
(Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
+ test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM 
connectivity through VXLAN (underlay in the default VRF) [FAIL])

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Description changed:

+ [Impact]
+ 
+ 
+ [Fix]
+ 
+ 
+ [Test]
+ 
+ 
+ [Where problems could occur]
+ 
+ [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1
  
-  # selftests: net: test_vxlan_under_vrf.sh
-  # Checking HV connectivity [ OK ]
-  # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
-  not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
- 
+  # selftests: net: test_vxlan_under_vrf.sh
+  # Checking HV connectivity [ OK ]
+  # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
+  not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
  
  The failure is different from bug 1837348

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with H (Check VM connectivity through VXLAN (underlay in the default
  VRF) [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.14 (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Invalid => In Progress

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-oem-5.14 (Ubuntu Impish)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Kinetic)
   Status: New => Invalid

** Tags added: 13 5.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with H (Check VM connectivity through VXLAN (underlay in the default
  VRF) [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-25 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Incomplete

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

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

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Fix Released

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with H (Check VM connectivity through VXLAN (underlay in the default
  VRF) [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

2022-05-24 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with H (Check VM connectivity through VXLAN (underlay in the default
  VRF) [FAIL])

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972791] Re: If i want my P.C. OK, i must to start with the 5.11.0-40-generic Kernel Release . Not another.

2022-05-22 Thread Po-Hsu Lin
Good to hear that :D
enjoy it!

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972791

Title:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

2022-05-20 Thread Po-Hsu Lin
This has been applied in Jammy via stable update process:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959376

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

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957753

Title:
  net/mlx5e: EPERM on vlan 0 programming

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947836] Re: nvidia-340 cannot be installed on F-Intel-5.13

2022-05-18 Thread Po-Hsu Lin
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947836

Title:
  nvidia-340 cannot be installed on F-Intel-5.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1947836/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940080] Re: ubuntu-kernel-selftests.ftrace hangs on riscv64

2022-05-16 Thread Po-Hsu Lin
** Summary changed:

- ubuntu-kernel-selftests.ftrace fails on riscv64
+ ubuntu-kernel-selftests.ftrace hangs on riscv64

** Tags added: sru-20220509

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940080

Title:
  ubuntu-kernel-selftests.ftrace hangs on riscv64

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966417] Re: memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F)

2022-05-15 Thread Po-Hsu Lin
Found with J-OEM 5.17.0-1004.4 with node wildcat


** Tags added: 5.17 oem sru-20220418

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966417

Title:
  memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events
  in F)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973378] Re: kernel BUG in pci_assign_unassigned_bus_resources

2022-05-15 Thread Po-Hsu Lin
Hi,
the kernel you're using, 5.4.0-64.72, is relatively old.

Can you give the latest Focal kernel 5.4.0-111.125 a try to see if this issue 
still exist?
Thanks


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973378

Title:
  kernel BUG in pci_assign_unassigned_bus_resources

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy)

2022-05-15 Thread Po-Hsu Lin
** Tags removed: azures
** Tags added: azure

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949532

Title:
  ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already
  mounted or mount point busy)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973261] Re: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

2022-05-13 Thread Po-Hsu Lin
This issue can be reproduced with 5.18.0-051800rc6-generic as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973261

Title:
  f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973261] Re: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

2022-05-13 Thread Po-Hsu Lin
** Package changed: linux-signed-oem-5.17 (Ubuntu) => linux-oem-5.17
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973261

Title:
  f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973261] [NEW] f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

2022-05-13 Thread Po-Hsu Lin
Public bug reported:

Issue found on Jammy OEM 5.17.0-1004.4

Test output:
  Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  
  fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  
  Btrfs: skip submitting barrier for missing device
  
  I got an error on v3.13:
   BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure 
(errors while submitting device barriers.)
  
  how to reproduce:
> mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
> wipefs -a /dev/sdf2
> mount -o degraded /dev/sdf1 /mnt
> btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt
  
  The reason of the error is that barrier_all_devices() failed to submit
  barrier to the missing device.  However it is clear that we cannot do
  anything on missing device, and also it is not necessary to care chunks
  on the missing device.
  
  This patch stops sending/waiting barrier if device is missing.
  
  btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  
  FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

dmesg output:

[  390.757211] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
[  390.773367] loop6: detected capacity change from 0 to 2097152
[  390.801666] loop7: detected capacity change from 0 to 2097152
[  392.126867] BTRFS: device fsid 3c464492-2cf2-4feb-a6fd-26f90d644196 devid 1 
transid 6 /dev/loop6 scanned by systemd-udevd (1407)
[  392.196398] BTRFS: device fsid 3c464492-2cf2-4feb-a6fd-26f90d644196 devid 2 
transid 6 /dev/loop7 scanned by mkfs.btrfs (1409)
[  392.548599] BTRFS info (device loop6): flagging fs with big metadata feature
[  392.548610] BTRFS info (device loop6): allowing degraded mounts
[  392.548614] BTRFS info (device loop6): using free space tree
[  392.548617] BTRFS info (device loop6): has skinny extents
[  392.549304] BTRFS warning (device loop6): devid 2 uuid 
918c3e31-5c12-491e-aac0-a007eda45078 is missing
[  392.549434] BTRFS warning (device loop6): devid 2 uuid 
918c3e31-5c12-491e-aac0-a007eda45078 is missing
[  392.550341] BTRFS info (device loop6): checking UUID tree
[  392.562271] BTRFS info (device loop6): balance: force reducing metadata 
redundancy
[  392.622941] BTRFS info (device loop6): balance: start -f -dconvert=single 
-mconvert=single -sconvert=single
[  392.623003] BTRFS info (device loop6): relocating block group 362545152 
flags system
[  392.742941] BTRFS info (device loop6): relocating block group 245104640 
flags metadata
[  393.004397] BTRFS info (device loop6): relocating block group 137756672 
flags data|raid1
[  393.298466] BTRFS info (device loop6): relocating block group 30408704 flags 
metadata|raid1
[  393.591373] BTRFS info (device loop6): found 7 extents, stage: move data 
extents
[  393.959629] BTRFS info (device loop6): relocating block group 22020096 flags 
system|raid1
[  394.210882] BTRFS info (device loop6): 1 enospc errors during balance
[  394.210893] BTRFS info (device loop6): balance: ended with status: -28
[  394.437519] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0


This is not a regression as this failure can be found with 5.17.0-1002.2 / 
5.17.0-1003.3 as well.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1004-oem 5.17.0-1004.4
ProcVersionSignature: User Name 5.17.0-1004.4-oem 5.17.3
Uname: Linux 5.17.0-1004-oem x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri May 13 05:52:35 2022
SourcePackage: linux-signed-oem-5.17
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux-signed-oem-5.17 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 5.17 amd64 apport-bug jammy oem package-from-proposed 
ubuntu-btrfs-kernel-fixes uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: 5.17 oem ubuntu-btrfs-kernel-fixes

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973261

Title:
  f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel"

2022-05-12 Thread Po-Hsu Lin
This would fail on another ARM64 node howzit-kernel as well with Jammy
5.15.0-27-generic

But without the messages from mpt3sas_cm0

dmesg output:
[ 2945.964263] LTP: starting read_all_sys (read_all -d /sys -q -r 3)
[ 2947.922462] WARNING! power/level is deprecated; use power/control instead
[ 2949.808190] bdi 7:6: the stable_pages_required attribute has been removed. 
Use the stable_writes queue attribute instead.
[ 2949.931340] No UUID available providing old NGUID
[ 2949.937332] No UUID available providing old NGUID
[ 2949.937814] No UUID available providing old NGUID
[ 2950.630986] Unable to handle kernel paging request at virtual address 
80007cf003bf
[ 2950.631121] Unable to handle kernel paging request at virtual address 
80007cf003bf
[ 2950.631160] Unable to handle kernel paging request at virtual address 
80007cf003bf
[ 2950.631168] Mem abort info:
[ 2950.631172]   ESR = 0x9621
[ 2950.631175]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 2950.631180]   SET = 0, FnV = 0
[ 2950.631183]   EA = 0, S1PTW = 0
[ 2950.631186]   FSC = 0x21: alignment fault
[ 2950.631190] Data abort info:
[ 2950.631193]   ISV = 0, ISS = 0x0021
[ 2950.631196]   CM = 0, WnR = 0
[ 2950.631199] swapper pgtable: 4k pages, 48-bit VAs, pgdp=400a02db7000
[ 2950.631204] [80007cf003bf] pgd=181b3003, p4d=181b3003, 
pud=18000c3dc003, pmd=18007a118003, pte=006888230f0f
[ 2950.631228] Internal error: Oops: 9621 [#1] SMP
[ 2950.631236] Modules linked in: arm_spe_pmu efi_pstore nls_iso8859_1 
input_leds joydev acpi_ipmi ipmi_ssif arm_cmn xgene_hwmon arm_dmc620_pmu 
arm_dsu_pmu cppc_cpufreq acpi_tad sch_fq_codel dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables 
autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear hid_generic usbhid cdc_ether hid usbnet mlx5_ib 
ib_uverbs ib_core uas usb_storage ast drm_vram_helper drm_ttm_helper ttm 
i2c_algo_bit drm_kms_helper crct10dif_ce ghash_ce syscopyarea sha2_ce 
sysfillrect sysimgblt sha256_arm64 fb_sys_fops mlx5_core sha1_ce cec rc_core 
nvme mlxfw drm xhci_pci psample nvme_core xhci_pci_renesas tls aes_neon_bs 
aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 2950.631420] CPU: 5 PID: 46308 Comm: read_all Not tainted 5.15.0-27-generic 
#28-Ubuntu
[ 2950.631426] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26
[ 2950.631430] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2950.631437] pc : __memcpy+0x168/0x260
[ 2950.631456] lr : memory_read_from_buffer+0x58/0x80
[ 2950.631470] sp : 8000776ebb60
[ 2950.631473] x29: 8000776ebb60 x28: 07fff4eb x27: 
[ 2950.631485] x26:  x25:  x24: 07ff8ac2ae20
[ 2950.631495] x23: 8000776ebc60 x22: 03ff x21: 8000776ebbc8
[ 2950.631506] x20: 03ff x19: 03ff x18: 
[ 2950.631516] x17:  x16:  x15: 
[ 2950.631526] x14:  x13:  x12: 
[ 2950.631536] x11:  x10:  x9 : 
[ 2950.631546] x8 :  x7 :  x6 : 
[ 2950.631556] x5 : 07fff26a6bff x4 : 80007cf003ff x3 : 07fff26a6b80
[ 2950.631566] x2 : ffef x1 : 80007cf003c0 x0 : 07fff26a6800
[ 2950.631576] Call trace:
[ 2950.631579]  __memcpy+0x168/0x260
[ 2950.631585]  acpi_data_show+0x5c/0x90
[ 2950.631596]  sysfs_kf_bin_read+0x78/0xa0
[ 2950.631607]  kernfs_file_read_iter+0x9c/0x1a4
[ 2950.631613]  kernfs_fop_read_iter+0x34/0x50
[ 2950.631619]  new_sync_read+0xf0/0x184
[ 2950.631629]  vfs_read+0x158/0x1f0
[ 2950.631635]  ksys_read+0x74/0x100
[ 2950.631640]  __arm64_sys_read+0x28/0x34
[ 2950.631645]  invoke_syscall+0x78/0x100
[ 2950.631657]  el0_svc_common.constprop.0+0x54/0x184
[ 2950.631664]  do_el0_svc+0x34/0x9c
[ 2950.631670]  el0_svc+0x48/0x1b0
[ 2950.631681]  el0t_64_sync_handler+0xa4/0x130
[ 2950.631686]  el0t_64_sync+0x1a4/0x1a8
[ 2950.631697] Code: a984346c a9c4342c f1010042 54fffee8 (a97c3c8e) 
[ 2950.631703] ---[ end trace 36f3d711c3548ceb ]---
[ 2950.638926] Mem abort info:
[ 2950.646846] Mem abort info:
[ 2950.646852]   ESR = 0x9621
[ 2950.646855]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 2950.646860]   SET = 0, FnV = 0
[ 2950.646861]   EA = 0, S1PTW = 0
[ 2950.646866]   FSC = 0x21: alignment fault
[ 2950.654786]   ESR = 0x9621
[ 2950.654792]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 2950.654797]   SET = 0, FnV = 0
[ 2950.654800]   EA = 0, S1PTW = 0
[ 2950.657589] Data abort info:
[ 2950.657593]   ISV = 0, ISS = 0x0021
[ 2950.657596]   CM = 0, WnR = 0
[ 2950.657599] swapper pgtable: 4k pages, 48-bit VAs, 

[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel"

2022-05-12 Thread Po-Hsu Lin
** Summary changed:

- kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 
ARM64 "helo-kernel"
+ kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 
ARM64 "helo-kernel"

** Description changed:

  Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy
  5.15.0-27-generic with ARM64 node helo-kernel only.
  
  It looks like this is hardware-specific.
  
  The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and
  test will timeout.
+ 
+ Steps to reproduce this:
+ git clone -b sru git://git.launchpad.net/~canonical-kernel-team/+git/ltp
+ cd ltp
+ make autotools
+ ./configure
+ make
+ make install
+ echo "read_all_sys read_all -d /sys -q -r 3" > /tmp/fs
+ sudo /opt/ltp/runltp -f /tmp/fs
  
  Test log:
  <<>>
  tag=read_all_sys stime=1652343855
  cmdline="read_all -d /sys -q -r 3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1500: TINFO: Killed the leftover descendant processes
  tst_test.c:1506: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1508: TBROK: Test killed! (timeout?)
  
  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1800 termination_type=exited termination_id=2 corefile=no
  cutime=39 cstime=140
  <<>>
  
  dmesg output:
  [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3)
  [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 
0; assume missing optional EEPROM
  [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
  [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
  [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
  [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
  [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
  [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for 
warpdrive
  [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for 
warpdrive
  [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
  [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for 
warpdrive
  [ 1617.641990] mpt3sas :8d:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 1617.973894] WARNING! power/level is deprecated; use power/control instead
  [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. 
Use the stable_writes queue attribute instead.
  [ 1627.430319] Unable to handle kernel paging request at virtual address 
800033b503bf
  [ 1627.438256] Mem abort info:
  [ 1627.441086]   ESR = 0x9621
  [ 1627.444133]   EC = 0x25: DABT (current EL), IL = 32 bits
  [ 1627.449469]   SET = 0, FnV = 0
  [ 1627.452515]   EA = 0, S1PTW = 0
  [ 1627.455676]   FSC = 0x21: alignment fault
  [ 1627.459701] Data abort info:
  [ 1627.462597]   ISV = 0, ISS = 0x0021
  [ 1627.466449]   CM = 0, WnR = 0
  [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000
  [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, 
pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f
  [ 1627.488712] Internal error: Oops: 9621 [#1] SMP
  [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds 
acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables 
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid 
usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit 
drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce 
fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm 
scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx 
aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher
  [ 1627.500861] Unable to handle kernel paging request at virtual address 
800033b503bf
  [ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic 
#8~22.04.2-Ubuntu
  [ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 
0ACKL030 06/04/2020
  [ 1627.562626] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [ 1627.570544] Mem abort info:
  [ 1627.571497] Unable to handle kernel paging request at virtual address 
800033b503bf
  [ 1627.571505] Mem abort info:
  [ 1627.571508]   ESR = 0x9621
  [ 1627.571511]   EC = 0x25: DABT (current EL), IL = 32 bits
  [ 1627.571516]   SET = 

[Bug 1973153] Re: kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel"

2022-05-12 Thread Po-Hsu Lin
** Summary changed:

- kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.17 ARM64
+ kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 
ARM64 "helo-kernel"

** Description changed:

- Issue found on 5.17.0-8-generic #8~22.04.2-Ubuntu with ARM64 node helo-
- kernel
+ Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy
+ 5.15.0-27-generic with ARM64 node helo-kernel only.
+ 
+ It looks like this is hardware-specific.
  
  The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and
  test will timeout.
  
  Test log:
  <<>>
  tag=read_all_sys stime=1652343855
  cmdline="read_all -d /sys -q -r 3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1500: TINFO: Killed the leftover descendant processes
  tst_test.c:1506: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1508: TBROK: Test killed! (timeout?)
  
  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1800 termination_type=exited termination_id=2 corefile=no
  cutime=39 cstime=140
  <<>>
- 
  
  dmesg output:
  [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3)
  [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 
0; assume missing optional EEPROM
  [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
  [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
  [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
  [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
  [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
  [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for 
warpdrive
  [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for 
warpdrive
  [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
  [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for 
warpdrive
  [ 1617.641990] mpt3sas :8d:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 1617.973894] WARNING! power/level is deprecated; use power/control instead
  [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. 
Use the stable_writes queue attribute instead.
  [ 1627.430319] Unable to handle kernel paging request at virtual address 
800033b503bf
  [ 1627.438256] Mem abort info:
  [ 1627.441086]   ESR = 0x9621
  [ 1627.444133]   EC = 0x25: DABT (current EL), IL = 32 bits
  [ 1627.449469]   SET = 0, FnV = 0
  [ 1627.452515]   EA = 0, S1PTW = 0
  [ 1627.455676]   FSC = 0x21: alignment fault
  [ 1627.459701] Data abort info:
  [ 1627.462597]   ISV = 0, ISS = 0x0021
  [ 1627.466449]   CM = 0, WnR = 0
  [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000
  [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, 
pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f
  [ 1627.488712] Internal error: Oops: 9621 [#1] SMP
  [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds 
acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables 
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid 
usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit 
drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce 
fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm 
scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx 
aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher
  [ 1627.500861] Unable to handle kernel paging request at virtual address 
800033b503bf
  [ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic 
#8~22.04.2-Ubuntu
  [ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 
0ACKL030 06/04/2020
  [ 1627.562626] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [ 1627.570544] Mem abort info:
  [ 1627.571497] Unable to handle kernel paging request at virtual address 
800033b503bf
  [ 1627.571505] Mem abort info:
  [ 1627.571508]   ESR = 0x9621
  [ 1627.571511]   EC = 0x25: DABT (current EL), IL = 32 bits
  [ 1627.571516]   SET = 0, FnV = 0
  [ 1627.571519]   EA = 0, S1PTW = 0
  [ 1627.571521]   FSC = 0x21: alignment fault
  [ 1627.571524] Data abort info:
  [ 1627.571526]   ISV = 0, ISS = 0x0021
  [ 1627.571529]   CM = 

[Bug 1973153] [NEW] kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.17 ARM64

2022-05-12 Thread Po-Hsu Lin
Public bug reported:

Issue found on 5.17.0-8-generic #8~22.04.2-Ubuntu with ARM64 node helo-
kernel

The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and
test will timeout.

Test log:
<<>>
tag=read_all_sys stime=1652343855
cmdline="read_all -d /sys -q -r 3"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s
Test timeouted, sending SIGKILL!
tst_test.c:1500: TINFO: Killed the leftover descendant processes
tst_test.c:1506: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
tst_test.c:1508: TBROK: Test killed! (timeout?)

Summary:
passed   0
failed   0
broken   1
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=1800 termination_type=exited termination_id=2 corefile=no
cutime=39 cstime=140
<<>>


dmesg output:
[ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3)
[ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 0; 
assume missing optional EEPROM
[ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
[ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
[ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is 
not registered
[ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
[ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
[ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive
[ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive
[ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not 
registered
[ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive
[ 1617.641990] mpt3sas :8d:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
[ 1617.973894] WARNING! power/level is deprecated; use power/control instead
[ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. 
Use the stable_writes queue attribute instead.
[ 1627.430319] Unable to handle kernel paging request at virtual address 
800033b503bf
[ 1627.438256] Mem abort info:
[ 1627.441086]   ESR = 0x9621
[ 1627.444133]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 1627.449469]   SET = 0, FnV = 0
[ 1627.452515]   EA = 0, S1PTW = 0
[ 1627.455676]   FSC = 0x21: alignment fault
[ 1627.459701] Data abort info:
[ 1627.462597]   ISV = 0, ISS = 0x0021
[ 1627.466449]   CM = 0, WnR = 0
[ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000
[ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, 
pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f
[ 1627.488712] Internal error: Oops: 9621 [#1] SMP
[ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds 
acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables 
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid 
usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit 
drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce 
fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm 
scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx 
aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher
[ 1627.500861] Unable to handle kernel paging request at virtual address 
800033b503bf
[ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic 
#8~22.04.2-Ubuntu
[ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 
06/04/2020
[ 1627.562626] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 1627.570544] Mem abort info:
[ 1627.571497] Unable to handle kernel paging request at virtual address 
800033b503bf
[ 1627.571505] Mem abort info:
[ 1627.571508]   ESR = 0x9621
[ 1627.571511]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 1627.571516]   SET = 0, FnV = 0
[ 1627.571519]   EA = 0, S1PTW = 0
[ 1627.571521]   FSC = 0x21: alignment fault
[ 1627.571524] Data abort info:
[ 1627.571526]   ISV = 0, ISS = 0x0021
[ 1627.571529]   CM = 0, WnR = 0
[ 1627.571531] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000
[ 1627.571536] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, 
pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f
[ 1627.578871] pc : __memcpy+0x168/0x240
[ 1627.578882] lr : memory_read_from_buffer+0x58/0x80
[ 1627.578892] sp : 800032ddba40
[ 1627.578894] x29: 800032ddba40 x28: 00083e53b0c0 x27: 
[ 1627.586903]   ESR = 0x9621
[ 1627.593843] x26:  

[Bug 1972894] Re: Touchpad does not work

2022-05-11 Thread Po-Hsu Lin
** Summary changed:

- After replacing the original HDD in my Acer Aspire ES1-311-C4Q6 with an ADATA 
240GB SSD I installed Ubuntu 20.04.1 from a Linux Format magazine DVD. The 
installation appeared to complete correctly. However, on rebooting the laptop 
there was no response to the Touchpad.  Using "less /proc/bus/devices" results 
in a list that shows no touchpad or mouse detected.
+ Touchpad does not work

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972894

Title:
  Touchpad does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1972894/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972791] Re: If i want my P.C. OK, i must to start with the 5.11.0-40-generic Kernel Release . Not another.

2022-05-11 Thread Po-Hsu Lin
Hi,

a couple things that worth a try:
* Check if there is any additional driver available, hit the windows key on 
your keyboard and search for "additional drivers"
* Or, install the OEM kernel on your Focal release, it will bring 5.14 kernel 
to you computer
sudo apt install linux-oem-20.04
* Or, try the latest LTS release 22.04 Jammy
* If your computer is still not working with possible solutions above, I would 
say give it a try with older releases, you can install Focal 20.04.1 (with 5.4 
kernel) or Bionic 18.04.1 (with 4.15 kernel) they are all supported.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972791

Title:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD

2022-05-11 Thread Po-Hsu Lin
** Description changed:

- Issue found on B-ibm-gt-4.15.0-1116.127 
+ [Impact]
+ rdpru test in ubuntu_kvm_unit_tests is to check if the RDPRU instruction can 
be intercepted by the Hypervisor.
+ 
+ RDPRU is one of the new instruction set extensions of AMD "Zen 2" CPUs
+ that is for reading a processor register that is typically limited to
+ privilege level zero. RDPRU allows for reading select registers at any
+ privilege level. With Linux 5.5, the RDPRU presence will be advertised
+ by the CPU features.
+ 
+ Without this patchset, the rdpru test will fail on our AMD Zen 2 system
+ "riccioli"
+ 
+ [Fix]
+ * 9d40b85b x86/cpufeatures: Add feature bit RDPRU on AMD
+ * 0cb8410b kvm: svm: Intercept RDPRU
+ 
+ We have these patches in newer releases already, only Bionic 4.15
+ require this fix. And they can be cherry-picked without any conflict.
+ 
+ [Test]
+ With the patched kernel, this rdpru test will pass on the target AMD Zen 2 
system.
+ 
+ And the rdpru flag will be available in cpuinfo:
+ flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf 
pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core 
perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate 
ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm 
rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves 
cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr 
rdpru arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid 
decodeassists pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes 
vpclmulqdq rdpid overflow_recov succor smca
+ bugs : sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
+ 
+ $ sudo ./rdpru
+ BUILD_HEAD=16647354
+ timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.syc17ecDpN -smp 1 -cpu max # -initrd /tmp/tmp.poLG53JqrJ
+ enabling apic
+ PASS: RDPRU raises #UD
+ SUMMARY: 1 tests
+ PASS rdpru (1 tests)
+ 
+ [Where problems could occur]
+ This patchset will add a new feature bit RDPRU, the impact should be small as 
it's still up to user-space for making use of it. 
+ 
+ [Original Bug Report]
+ Issue found on B-ibm-gt-4.15.0-1116.127
  This can be reproduced with B-4.15.0-175 as well.
  
  This failure is only visible on this node.
  
   Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/rdpru'
   BUILD_HEAD=16647354
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.qGIR5tvTw1 -smp 1 -cpu max # -initrd /tmp/tmp.8JuYRCFRUi
   enabling apic
   FAIL: RDPRU raises #UD
   SUMMARY: 1 tests, 1 unexpected failures
   FAIL rdpru (1 tests, 1 unexpected failures)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968681

Title:
  rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with
  FAIL: RDPRU raises #UD

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972791] Re: If i want my P.C. OK, i must to start with the 5.11.0-40-generic Kernel Release . Not another.

2022-05-11 Thread Po-Hsu Lin
Hi,

it's not recommended to stay with an old kernel, especially 5.11 kernel
has already reaches its end-of-life in Jan. 2022

Please give 5.13 hwe kernel a try, a `sudo apt dist-upgrade` should
bring that to you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972791

Title:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967493] Re: pl2303 serial adapter not recognized

2022-05-06 Thread Po-Hsu Lin
Hi,
thanks for testing this out,
from the attachment it looks like your pl2303 does not work with the new device 
detection algorithm in 5.13 kernel:

https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/tree/drivers/usb/serial/pl2303.c#n421
Which can only handle devices with bcdUSB 1.10 and 2.00

However yours is 1.01:
Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.01
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x067b Prolific Technology, Inc.
  idProduct  0x2303 PL2303 Serial Port
  bcdDevice3.00

I would suggest you to give the latest mainline kernel [1] a try to see
if this issue exist with the latest kernel, you will find instructions
here [2].

If the issue still exist, please report this issue to linux-
u...@vger.kernel.org, indicating the kernel version and attach the lsusb
-v output for this device.

Thanks!

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18-rc5/
[2] 
https://wiki.ubuntu.com/Kernel/MainlineBuilds#How_do_I_install_an_upstream_kernel.3F

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967493

Title:
  pl2303 serial adapter not recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1967493/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb

2022-05-06 Thread Po-Hsu Lin
Closing as per comment #6
You can try to install the nvidia driver then the KDE on ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825638

Title:
  Lenovo Legion Y530-15ICH  does not start with live usb

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970896] Re: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal

2022-05-04 Thread Po-Hsu Lin
OK!
Thanks for the info, we will discuss how to deal with this first (maybe just 
bump the disk size)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970896

Title:
  uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all
  disk free space on Jammy AWS baremetal

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971635] Re: Bluettooth não conecta - notebook Dell

2022-05-04 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1969853 ***
https://bugs.launchpad.net/bugs/1969853

This might be a duplicate of bug 1969853, please feel free to unmark it
if it's a different issue.

** This bug has been marked a duplicate of bug 1969853
   No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971635

Title:
  Bluettooth não conecta - notebook Dell

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550704] Re: Type Cover (3) touchpad not working on Surface Pro 3

2022-05-04 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550704

Title:
  Type Cover (3) touchpad not working on Surface Pro 3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb

2022-05-04 Thread Po-Hsu Lin
Closing as per comment #6

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825638

Title:
  Lenovo Legion Y530-15ICH  does not start with live usb

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

2022-05-04 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939052

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970896] Re: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal

2022-05-03 Thread Po-Hsu Lin
Hi Robie,
thanks for the reply,

It make sense to require twice of the image size as per the verification
requirement, however it looks like in this case it's using more than two
times of it.

The image is just around 600M, so it should be just 600M in /tmp and
600M more in libvirt after it's been verified. 3.0G free space should be
enough, but it's not.

Maybe I am missing some pieces here?
Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970896

Title:
  uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all
  disk free space on Jammy AWS baremetal

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971215] Re: hwclock failed on 5.13 Oracle ARM64 bare-metal BM.Standard.A1.160

2022-05-02 Thread Po-Hsu Lin
I grabbed an ARM64 bare-metal system in our pool and run the hwclock
test on it. It can pass with the generic Bionic HWE kernel
5.4.0-109-generic #123~18.04.1-Ubuntu without any problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971215

Title:
  hwclock failed on 5.13 Oracle ARM64 bare-metal BM.Standard.A1.160

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971215] [NEW] hwclock failed on 5.13 Oracle ARM64 bare-metal BM.Standard.A1.160

2022-05-02 Thread Po-Hsu Lin
Public bug reported:

Issue found on:
  * 5.4.0-1071.77~18.04.1 
  * 5.4.0-1071.77

Passed on:
  * 5.13.0-1028.33~20.04.1 
  * 5.13.0-1028.33
  * 5.15.0-1004.6

Not failing with 4.15.0-1093.102 / 4.15.0-1093.102~16.04.1 as this
instance was not tested there

Test failed with:
hwclock: Cannot access the Hardware Clock via any known method.

This is a new node added in this cycle, so this is not a regression.
Looks like a kernel support issue to me.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: 5.4 bionic focal hwclock oracle sru-20220418

** Summary changed:

- hwclock failed on Oracle ARM64 bare-metal BM.Standard.A1.160
+ hwclock failed on 5.13 Oracle ARM64 bare-metal BM.Standard.A1.160

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971215

Title:
  hwclock failed on 5.13 Oracle ARM64 bare-metal BM.Standard.A1.160

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought

2022-04-29 Thread Po-Hsu Lin
Tested with stress-ng V0.13.12

5.17.1-051701-generic - Not OK
5.17.3-051703-generic - Not OK
5.17.5-051705-generic - Not OK
5.18.0-051800rc1-generic - OK

[   51.103647] BUG: unable to handle page fault for address: 1cc8
[   51.103724] #PF: supervisor read access in kernel mode
[   51.103768] #PF: error_code(0x) - not-present page
[   51.103810] PGD 0 P4D 0 
[   51.103838] Oops:  [#1] PREEMPT SMP NOPTI
[   51.103876] CPU: 26 PID: 3277 Comm: stress-ng Not tainted 
5.17.5-051705-generic #202204271406
[   51.103943] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
[   51.104020] RIP: 0010:__next_zones_zonelist+0x6/0x50
[   51.104074] Code: 39 d0 0f 4e d0 3d ff 03 00 00 7f 0e 48 63 d2 5d 48 8b 04 
d5 a0 ed e4 85 c3 cc 31 c0 5d c3 cc 0f 1f 44 00 00 0f 1f 44 00 00 55 <8b> 4f 08 
48 89 f8 48 89 e5 48 85 d2 75 10 eb 1e 48 63 49 50 48 0f
[   51.104210] RSP: 0018:a28424897aa8 EFLAGS: 00010286
[   51.104254] RAX:  RBX:  RCX: 
[   51.104309] RDX: 95c7e17b2e00 RSI: 0002 RDI: 1cc0
[   51.104365] RBP: a28424897b10 R08:  R09: 
[   51.104419] R10: 0002 R11: fffc R12: 00052cc0
[   51.104474] R13: 0002 R14: 0001 R15: 00152cc0
[   51.104528] FS:  7faa2a8b7b80() GS:95f38ca8() 
knlGS:
[   51.104591] CS:  0010 DS:  ES:  CR0: 80050033
[   51.104637] CR2: 1cc8 CR3: 00bd74a92004 CR4: 007706e0
[   51.104692] DR0:  DR1:  DR2: 
[   51.104747] DR3:  DR6: fffe0ff0 DR7: 0400
[   51.104802] PKRU: 5554
[   51.104827] Call Trace:
[   51.104851]  
[   51.104874]  ? __alloc_pages+0x305/0x340
[   51.104918]  kmalloc_large_node+0x45/0xa0
[   51.104958]  ? krc_this_cpu_lock+0x36/0x40
[   51.104998]  __kmalloc_node+0x2f9/0x3e0
[   51.105036]  kvmalloc_node+0x4f/0x90
[   51.105072]  expand_one_shrinker_info+0x82/0x180
[   51.105116]  prealloc_shrinker+0x174/0x1d0
[   51.105154]  alloc_super+0x2b3/0x340
[   51.105188]  ? fput+0x20/0x20
[   51.105220]  sget_fc+0x6f/0x2e0
[   51.105249]  ? kill_litter_super+0x50/0x50
[   51.105289]  ? mqueue_get_tree+0x20/0x20
[   51.105329]  get_tree_keyed+0x34/0xd0
[   51.105362]  mqueue_get_tree+0x1c/0x20
[   51.105396]  vfs_get_tree+0x27/0xc0
[   51.105431]  fc_mount+0x13/0x50
[   51.105463]  mq_init_ns+0x10a/0x1b0
[   51.105498]  copy_ipcs+0x131/0x230
[   51.105531]  create_new_namespaces+0xa6/0x2e0
[   51.105575]  unshare_nsproxy_namespaces+0x5a/0xb0
[   51.105620]  ksys_unshare+0x1a0/0x380
[   51.106980]  ? switch_task_namespaces+0x40/0x70
[   51.108315]  __x64_sys_unshare+0x12/0x20
[   51.109648]  do_syscall_64+0x59/0xc0
[   51.111359]  ? exit_to_user_mode_prepare+0x37/0xb0
[   51.112920]  ? syscall_exit_to_user_mode+0x27/0x50
[   51.114260]  ? __x64_sys_unshare+0x12/0x20
[   51.115594]  ? do_syscall_64+0x69/0xc0
[   51.116919]  ? exit_to_user_mode_prepare+0x37/0xb0
[   51.118226]  ? syscall_exit_to_user_mode+0x27/0x50
[   51.119490]  ? __x64_sys_close+0x11/0x50
[   51.120708]  ? do_syscall_64+0x69/0xc0
[   51.121876]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   51.122937] RIP: 0033:0x7faa2a9ecfcb
[   51.123680] Code: 73 01 c3 48 8b 0d 65 1e 0f 00 f7 d8 64 89 01 48 83 c8 ff 
c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 01 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 35 1e 0f 00 f7 d8 64 89 01 48
[   51.125272] RSP: 002b:7fffa228d818 EFLAGS: 0246 ORIG_RAX: 
0110
[   51.126105] RAX: ffda RBX: 7fffa228d9c0 RCX: 7faa2a9ecfcb
[   51.126940] RDX: 55ea47f8e022 RSI: 0800 RDI: 0800
[   51.127783] RBP: 7fffa228d870 R08: 55ea47f6690e R09: 7faa2a8b7b80
[   51.128617] R10:  R11: 0246 R12: 55ea47f8e022
[   51.129444] R13: 7fffa228d9c0 R14: 0ca2 R15: 55ea47f7d4e6
[   51.130262]  
[   51.131070] Modules linked in: kmem device_dax intel_rapl_msr 
intel_rapl_common isst_if_common nd_pmem dax_pmem nd_btt skx_edac ipmi_ssif 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nls_iso8859_1 
irdma rapl ice intel_cstate ib_uverbs efi_pstore ib_core joydev input_leds 
mei_me ioatdma mei intel_pch_thermal dca acpi_ipmi ipmi_si nfit mac_hid 
sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc ipmi_devintf scsi_dh_alua 
ipmi_msghandler msr ip_tables x_tables autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul cec 
ghash_clmulni_intel rc_core aesni_intel crypto_simd i40e cryptd ahci 

[Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought

2022-04-29 Thread Po-Hsu Lin
Test passed on 5.18.0-051800rc1-generic with both stress-ng V0.14.0 / V0.13.12
$ sudo ./stress-ng -v -t 5 --unshare 4 --unshare-ops 3000 --ignite-cpu --syslog 
--verbose --verify --oomable
stress-ng: debug: [27013] stress-ng 0.13.12 gf59bcb2fe1e2
stress-ng: debug: [27013] system: Linux vought 5.18.0-051800rc1-generic 
#202204032230 SMP PREEMPT_DYNAMIC Sun Apr 3 22:35:34 UTC 2022 x86_64
stress-ng: debug: [27013] RAM total: 351.5G, RAM free: 346.8G, swap free: 8.0G
stress-ng: debug: [27013] 96 processors online, 96 processors configured
stress-ng: info:  [27013] setting to a 5 second run per stressor
stress-ng: info:  [27013] dispatching hogs: 4 unshare
stress-ng: debug: [27013] cache allocate: shared cache buffer size: 36608K
stress-ng: debug: [27013] starting stressors
stress-ng: debug: [27013] 4 stressors started
stress-ng: debug: [27014] stress-ng-unshare: started [27014] (instance 0)
stress-ng: debug: [27015] stress-ng-unshare: started [27015] (instance 1)
stress-ng: debug: [27016] stress-ng-unshare: started [27016] (instance 2)
stress-ng: debug: [27017] stress-ng-unshare: started [27017] (instance 3)
stress-ng: debug: [27015] stress-ng-unshare: exited [27015] (instance 1)
stress-ng: debug: [27014] stress-ng-unshare: exited [27014] (instance 0)
stress-ng: debug: [27013] process [27014] terminated
stress-ng: debug: [27013] process [27015] terminated
stress-ng: debug: [27016] stress-ng-unshare: exited [27016] (instance 2)
stress-ng: debug: [27017] stress-ng-unshare: exited [27017] (instance 3)
stress-ng: debug: [27013] process [27016] terminated
stress-ng: debug: [27013] process [27017] terminated
stress-ng: info:  [27013] successful run completed in 5.10s
stress-ng: debug: [27013] metrics-check: all stressor metrics validated and sane

Now we have something to bisect with.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959215

Title:
  unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to
  handle page fault for address: 1cc8" on Impish with node
  vought

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1959215/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970896] Re: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal

2022-04-29 Thread Po-Hsu Lin
When you run this `uvt-simplestreams-libvirt sync` command, I noticed there 
will be two files created in /tmp:
-rw---  1 root root 575M Apr 29 09:23 tmpf17tglw6
-rw---  1 root root 1.4G Apr 29 09:23 tmpi4lq8p24
After that, it will start writing image file in 
/var/lib/uvtool/libvirt/images/, the file size reaches about 1.1G then disk 
space runs out
root@a1.metal:/var/lib/uvtool/libvirt/images# ls -alh
total 1.1G
-rw--- 1 root root 1.1G Apr 29 09:14 
'x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MjIuMDQ6YXJtNjQgMjAyMjA0MjM='

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970896

Title:
  uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all
  disk free space on Jammy AWS baremetal

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970896] Re: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal

2022-04-29 Thread Po-Hsu Lin
** Also affects: uvtool (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: sru-20220418 ubuntu-kvm-smoke

** Tags removed: ubuntu-kvm-smoke
** Tags added: 5.15 aws jammy ubuntu-kvm-smoke-test

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970896

Title:
  uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all
  disk free space on Jammy AWS baremetal

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests

2022-04-28 Thread Po-Hsu Lin
ADT test started correctly on Jammy.

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968016

Title:
  Use kernel-testing repo from launchpad for ADT tests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966066] Re: audio from external sound card is distorted

2022-04-28 Thread Po-Hsu Lin
Hi Stefan,

It's expected to see this kernel in -updates on 09-May

Kernel Versions
=
impish:
linux:   5.13.0-41.46
focal:
linux-hwe-5.13:  5.13.0-41.46~20.04.1

https://lists.ubuntu.com/archives/kernel-team/2022-April/129717.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966066

Title:
  audio from external sound card is distorted

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support

2022-04-26 Thread Po-Hsu Lin
Hi,
Yes it will be shipped with Focal HWE 5.13 kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966499

Title:
  Recent 5.13 kernel has broken KVM support

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970049] Re: Tick tick sound when USB Play on Xenyx302USB (PCM2902) enabled

2022-04-26 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1966066 ***
https://bugs.launchpad.net/bugs/1966066

Thanks for checking!

** This bug has been marked a duplicate of bug 1966066
   audio from external sound card is distorted

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970049

Title:
  Tick tick sound when USB Play on  Xenyx302USB (PCM2902) enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1970049/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970004] Re: tex shinobi is not being recognize by the kernel

2022-04-24 Thread Po-Hsu Lin
Marked as Incomplete as per comment in #7

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970004

Title:
  tex shinobi is not being recognize by the kernel

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970049] Re: Tick tick sound when USB Play on Xenyx302USB (PCM2902) enabled

2022-04-24 Thread Po-Hsu Lin
Hi,
this sounds like a duplicated issue of 
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066

Can you give the 5.13.0-41-generic proposed kernel a try?

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


** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970049

Title:
  Tick tick sound when USB Play on  Xenyx302USB (PCM2902) enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1970049/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )

2022-04-22 Thread Po-Hsu Lin
OK I misread Stefan's comment,

checking the report again, it's using the consistent version
(1:4.0.12-0ubuntu1~20.04.1)) for both lxc and test cases (source) on
that s390x zVM.

Please find attachment for the full test log.

I will switch the bug status back to New.

** Attachment added: "test-110.log"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1969905/+attachment/5582419/+files/test-110.log

** Changed in: lxc (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969905

Title:
  lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc
  1:4.0.12-0ubuntu1~20.04.1 )

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )

2022-04-22 Thread Po-Hsu Lin
Tried this on a Focal AMD64 instance, and it passed with
1:4.0.12-0ubuntu1~20.04.1

Stefan is right, the tool was not updated on that s390x SUT.

Sorry for the noise, this is a manually provisioned system and this
-proposed stuff must be something leftover from the past.

** Changed in: lxc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969905

Title:
  lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc
  1:4.0.12-0ubuntu1~20.04.1 )

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )

2022-04-22 Thread Po-Hsu Lin
Hi Christian,
we just found that it's because we have universe -proposed enabled on that node 
only. (Which should be disabled for our SRU test)
On other instances they're still using the old test case from 
1:4.0.6-0ubuntu1~20.04.1.

I can give it a try on AMD64 instance.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969905

Title:
  lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc
  1:4.0.12-0ubuntu1~20.04.1 )

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )

2022-04-22 Thread Po-Hsu Lin
** Tags added: 5.4 focal s390x sru-20220321 ubuntu-lxc

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969905

Title:
  lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc
  1:4.0.12-0ubuntu1~20.04.1 )

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD

2022-04-21 Thread Po-Hsu Lin
This hardware is an AMD system, codename Rome, Second generation Epyc

Fix:
https://github.com/torvalds/linux/commit/9d40b85bb46a99bc95dad3a07787da93b0a018e9
https://github.com/torvalds/linux/commit/0cb8410b90e78948984f35f2c4d50c2c0b7ee675

With patched kernel, the rdpru flag will be available in cpuinfo:
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe 
popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm 
sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core 
perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate 
ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm 
rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves 
cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr 
rdpru arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid 
decodeassists pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes 
vpclmulqdq rdpid overflow_recov succor smca
bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass

$ sudo ./rdpru 
BUILD_HEAD=16647354
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.syc17ecDpN -smp 1 -cpu max # -initrd /tmp/tmp.poLG53JqrJ
enabling apic
PASS: RDPRU raises #UD
SUMMARY: 1 tests
PASS rdpru (1 tests)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968681

Title:
  rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with
  FAIL: RDPRU raises #UD

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD

2022-04-21 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968681

Title:
  rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with
  FAIL: RDPRU raises #UD

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests

2022-04-21 Thread Po-Hsu Lin
ADT started correctly on Bionic as well.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968016

Title:
  Use kernel-testing repo from launchpad for ADT tests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))

2022-04-20 Thread Po-Hsu Lin
Bionic 4.15.0-177.186 with node exotic-skunk.amd64

 Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test'
 BUILD_HEAD=16647354
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.3qPxgV32ap -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd 
/tmp/tmp.cCbvsNzbhI
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 1007000
 cr4 = 20
 filter = vmx_ldtr_test, test = test_vmx_feature_control
 filter = vmx_ldtr_test, test = test_vmxon
 filter = vmx_ldtr_test, test = test_vmptrld
 filter = vmx_ldtr_test, test = test_vmclear
 filter = vmx_ldtr_test, test = test_vmptrst
 filter = vmx_ldtr_test, test = test_vmwrite_vmread
 filter = vmx_ldtr_test, test = test_vmcs_high
 filter = vmx_ldtr_test, test = test_vmcs_lifecycle
 filter = vmx_ldtr_test, test = test_vmx_caps
 filter = vmx_ldtr_test, test = test_vmread_flags_touch
 filter = vmx_ldtr_test, test = test_vmwrite_flags_touch
 filter = vmx_ldtr_test, test = null
 filter = vmx_ldtr_test, test = vmenter
 filter = vmx_ldtr_test, test = preemption timer
 filter = vmx_ldtr_test, test = control field PAT
 filter = vmx_ldtr_test, test = control field EFER
 filter = vmx_ldtr_test, test = CR shadowing
 filter = vmx_ldtr_test, test = I/O bitmap
 filter = vmx_ldtr_test, test = instruction intercept
 filter = vmx_ldtr_test, test = EPT A/D disabled
 filter = vmx_ldtr_test, test = EPT A/D enabled
 filter = vmx_ldtr_test, test = PML
 filter = vmx_ldtr_test, test = interrupt
 filter = vmx_ldtr_test, test = nmi_hlt
 filter = vmx_ldtr_test, test = debug controls
 filter = vmx_ldtr_test, test = MSR switch
 filter = vmx_ldtr_test, test = vmmcall
 filter = vmx_ldtr_test, test = disable RDTSCP
 filter = vmx_ldtr_test, test = int3
 filter = vmx_ldtr_test, test = into
 filter = vmx_ldtr_test, test = exit_monitor_from_l2_test
 filter = vmx_ldtr_test, test = invalid_msr
 filter = vmx_ldtr_test, test = v2_null_test
 filter = vmx_ldtr_test, test = v2_multiple_entries_test
 filter = vmx_ldtr_test, test = fixture_test_case1
 filter = vmx_ldtr_test, test = fixture_test_case2
 filter = vmx_ldtr_test, test = invvpid_test
 filter = vmx_ldtr_test, test = vmx_controls_test
 filter = vmx_ldtr_test, test = vmx_host_state_area_test
 filter = vmx_ldtr_test, test = vmx_guest_state_area_test
 filter = vmx_ldtr_test, test = vmentry_movss_shadow_test
 filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test
 filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test
 filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test
 filter = vmx_ldtr_test, test = apic_reg_virt_test
 filter = vmx_ldtr_test, test = virt_x2apic_mode_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test
 filter = vmx_ldtr_test, test = vmx_init_signal_test
 filter = vmx_ldtr_test, test = vmx_sipi_signal_test
 filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test
 filter = vmx_ldtr_test, test = vmx_ldtr_test
 
 Test suite: vmx_ldtr_test
 PASS: Expected 18 for L2 LDTR selector (got 18)
 PASS: Expected 0 for L1 LDTR selector (got 0)
 filter = vmx_ldtr_test, test = vmx_cr_load_test
 filter = vmx_ldtr_test, test = vmx_cr4_osxsave_test
 filter = vmx_ldtr_test, test = vmx_nm_test
 filter = vmx_ldtr_test, test = vmx_db_test
 filter = vmx_ldtr_test, test = vmx_nmi_window_test
 filter = vmx_ldtr_test, test = vmx_intr_window_test
 filter = vmx_ldtr_test, test = vmx_pending_event_test
 filter = vmx_ldtr_test, test = vmx_pending_event_hlt_test
 filter = vmx_ldtr_test, test = vmx_store_tsc_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_zero_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_tf_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_expiry_test
 filter = vmx_ldtr_test, test = ept_access_test_not_present
 filter = vmx_ldtr_test, test = ept_access_test_read_only
 filter = vmx_ldtr_test, test = ept_access_test_write_only
 filter = vmx_ldtr_test, test = ept_access_test_read_write
 filter = vmx_ldtr_test, test = ept_access_test_execute_only
 filter = vmx_ldtr_test, test = ept_access_test_read_execute
 filter = vmx_ldtr_test, test = ept_access_test_write_execute
 filter = vmx_ldtr_test, test = ept_access_test_read_write_execute
 filter = vmx_ldtr_test, test = ept_access_test_reserved_bits
 filter = vmx_ldtr_test, test = ept_access_test_ignored_bits
 filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_disabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_enabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_disabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_enabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_write
 filter = vmx_ldtr_test, test = 

[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support

2022-04-19 Thread Po-Hsu Lin
Thanks for testing this!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966499

Title:
  Recent 5.13 kernel has broken KVM support

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)

2022-04-19 Thread Po-Hsu Lin
Mark unsupported series as Won't fix.

** Changed in: linux (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938964

Title:
  icmp_redirect from selftests fails on F/kvm (unary operator expected)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968902] Re: ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels

2022-04-19 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968902

Title:
  ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966143] Re: Periodic glitch in LogiTech H390 headphone audio

2022-04-19 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1966066 ***
https://bugs.launchpad.net/bugs/1966066

Mark it as dup for bug 1966066, please feel free to unmark it if you
think this is incorrect.

** This bug has been marked a duplicate of bug 1966066
   audio from external sound card is distorted

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966143

Title:
  Periodic glitch in LogiTech H390 headphone audio

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests

2022-04-19 Thread Po-Hsu Lin
ADT test started correctly.

** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968016

Title:
  Use kernel-testing repo from launchpad for ADT tests

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))

2022-04-19 Thread Po-Hsu Lin
Focal 5.4.0-110.124 with node spitfire:

 Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test'
 BUILD_HEAD=16647354
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.8hYc1dgvp4 -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd 
/tmp/tmp.VW7zzXkBfL
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 1007000
 cr4 = 20
 filter = vmx_ldtr_test, test = test_vmx_feature_control
 filter = vmx_ldtr_test, test = test_vmxon
 filter = vmx_ldtr_test, test = test_vmptrld
 filter = vmx_ldtr_test, test = test_vmclear
 filter = vmx_ldtr_test, test = test_vmptrst
 filter = vmx_ldtr_test, test = test_vmwrite_vmread
 filter = vmx_ldtr_test, test = test_vmcs_high
 filter = vmx_ldtr_test, test = test_vmcs_lifecycle
 filter = vmx_ldtr_test, test = test_vmx_caps
 filter = vmx_ldtr_test, test = test_vmread_flags_touch
 filter = vmx_ldtr_test, test = test_vmwrite_flags_touch
 filter = vmx_ldtr_test, test = null
 filter = vmx_ldtr_test, test = vmenter
 filter = vmx_ldtr_test, test = preemption timer
 filter = vmx_ldtr_test, test = control field PAT
 filter = vmx_ldtr_test, test = control field EFER
 filter = vmx_ldtr_test, test = CR shadowing
 filter = vmx_ldtr_test, test = I/O bitmap
 filter = vmx_ldtr_test, test = instruction intercept
 filter = vmx_ldtr_test, test = EPT A/D disabled
 filter = vmx_ldtr_test, test = EPT A/D enabled
 filter = vmx_ldtr_test, test = PML
 filter = vmx_ldtr_test, test = interrupt
 filter = vmx_ldtr_test, test = nmi_hlt
 filter = vmx_ldtr_test, test = debug controls
 filter = vmx_ldtr_test, test = MSR switch
 filter = vmx_ldtr_test, test = vmmcall
 filter = vmx_ldtr_test, test = disable RDTSCP
 filter = vmx_ldtr_test, test = int3
 filter = vmx_ldtr_test, test = into
 filter = vmx_ldtr_test, test = exit_monitor_from_l2_test
 filter = vmx_ldtr_test, test = invalid_msr
 filter = vmx_ldtr_test, test = v2_null_test
 filter = vmx_ldtr_test, test = v2_multiple_entries_test
 filter = vmx_ldtr_test, test = fixture_test_case1
 filter = vmx_ldtr_test, test = fixture_test_case2
 filter = vmx_ldtr_test, test = invvpid_test
 filter = vmx_ldtr_test, test = vmx_controls_test
 filter = vmx_ldtr_test, test = vmx_host_state_area_test
 filter = vmx_ldtr_test, test = vmx_guest_state_area_test
 filter = vmx_ldtr_test, test = vmentry_movss_shadow_test
 filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test
 filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test
 filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test
 filter = vmx_ldtr_test, test = apic_reg_virt_test
 filter = vmx_ldtr_test, test = virt_x2apic_mode_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test
 filter = vmx_ldtr_test, test = vmx_init_signal_test
 filter = vmx_ldtr_test, test = vmx_sipi_signal_test
 filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test
 filter = vmx_ldtr_test, test = vmx_ldtr_test
 
 Test suite: vmx_ldtr_test
 PASS: Expected 18 for L2 LDTR selector (got 18)
 PASS: Expected 0 for L1 LDTR selector (got 0)
 filter = vmx_ldtr_test, test = vmx_cr_load_test
 filter = vmx_ldtr_test, test = vmx_cr4_osxsave_test
 filter = vmx_ldtr_test, test = vmx_nm_test
 filter = vmx_ldtr_test, test = vmx_db_test
 filter = vmx_ldtr_test, test = vmx_nmi_window_test
 filter = vmx_ldtr_test, test = vmx_intr_window_test
 filter = vmx_ldtr_test, test = vmx_pending_event_test
 filter = vmx_ldtr_test, test = vmx_pending_event_hlt_test
 filter = vmx_ldtr_test, test = vmx_store_tsc_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_zero_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_tf_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_expiry_test
 filter = vmx_ldtr_test, test = ept_access_test_not_present
 filter = vmx_ldtr_test, test = ept_access_test_read_only
 filter = vmx_ldtr_test, test = ept_access_test_write_only
 filter = vmx_ldtr_test, test = ept_access_test_read_write
 filter = vmx_ldtr_test, test = ept_access_test_execute_only
 filter = vmx_ldtr_test, test = ept_access_test_read_execute
 filter = vmx_ldtr_test, test = ept_access_test_write_execute
 filter = vmx_ldtr_test, test = ept_access_test_read_write_execute
 filter = vmx_ldtr_test, test = ept_access_test_reserved_bits
 filter = vmx_ldtr_test, test = ept_access_test_ignored_bits
 filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_disabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_enabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_disabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_enabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_write
 filter = vmx_ldtr_test, test = 

[Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))

2022-04-19 Thread Po-Hsu Lin
Impish 5.13 with node vought:
 Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test'
 BUILD_HEAD=16647354
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.WvqHvN1Mpk -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd 
/tmp/tmp.gTntUdwZWg
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 1007000
 cr4 = 20
 filter = vmx_ldtr_test, test = test_vmx_feature_control
 filter = vmx_ldtr_test, test = test_vmxon
 filter = vmx_ldtr_test, test = test_vmptrld
 filter = vmx_ldtr_test, test = test_vmclear
 filter = vmx_ldtr_test, test = test_vmptrst
 filter = vmx_ldtr_test, test = test_vmwrite_vmread
 filter = vmx_ldtr_test, test = test_vmcs_high
 filter = vmx_ldtr_test, test = test_vmcs_lifecycle
 filter = vmx_ldtr_test, test = test_vmx_caps
 filter = vmx_ldtr_test, test = test_vmread_flags_touch
 filter = vmx_ldtr_test, test = test_vmwrite_flags_touch
 filter = vmx_ldtr_test, test = null
 filter = vmx_ldtr_test, test = vmenter
 filter = vmx_ldtr_test, test = preemption timer
 filter = vmx_ldtr_test, test = control field PAT
 filter = vmx_ldtr_test, test = control field EFER
 filter = vmx_ldtr_test, test = CR shadowing
 filter = vmx_ldtr_test, test = I/O bitmap
 filter = vmx_ldtr_test, test = instruction intercept
 filter = vmx_ldtr_test, test = EPT A/D disabled
 filter = vmx_ldtr_test, test = EPT A/D enabled
 filter = vmx_ldtr_test, test = PML
 filter = vmx_ldtr_test, test = interrupt
 filter = vmx_ldtr_test, test = nmi_hlt
 filter = vmx_ldtr_test, test = debug controls
 filter = vmx_ldtr_test, test = MSR switch
 filter = vmx_ldtr_test, test = vmmcall
 filter = vmx_ldtr_test, test = disable RDTSCP
 filter = vmx_ldtr_test, test = int3
 filter = vmx_ldtr_test, test = into
 filter = vmx_ldtr_test, test = exit_monitor_from_l2_test
 filter = vmx_ldtr_test, test = invalid_msr
 filter = vmx_ldtr_test, test = v2_null_test
 filter = vmx_ldtr_test, test = v2_multiple_entries_test
 filter = vmx_ldtr_test, test = fixture_test_case1
 filter = vmx_ldtr_test, test = fixture_test_case2
 filter = vmx_ldtr_test, test = invvpid_test
 filter = vmx_ldtr_test, test = vmx_controls_test
 filter = vmx_ldtr_test, test = vmx_host_state_area_test
 filter = vmx_ldtr_test, test = vmx_guest_state_area_test
 filter = vmx_ldtr_test, test = vmentry_movss_shadow_test
 filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test
 filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test
 filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test
 filter = vmx_ldtr_test, test = apic_reg_virt_test
 filter = vmx_ldtr_test, test = virt_x2apic_mode_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test
 filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test
 filter = vmx_ldtr_test, test = vmx_init_signal_test
 filter = vmx_ldtr_test, test = vmx_sipi_signal_test
 filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test
 filter = vmx_ldtr_test, test = vmx_ldtr_test
 
 Test suite: vmx_ldtr_test
 PASS: Expected 18 for L2 LDTR selector (got 18)
 PASS: Expected 0 for L1 LDTR selector (got 0)
 filter = vmx_ldtr_test, test = vmx_cr_load_test
 filter = vmx_ldtr_test, test = vmx_cr4_osxsave_test
 filter = vmx_ldtr_test, test = vmx_nm_test
 filter = vmx_ldtr_test, test = vmx_db_test
 filter = vmx_ldtr_test, test = vmx_nmi_window_test
 filter = vmx_ldtr_test, test = vmx_intr_window_test
 filter = vmx_ldtr_test, test = vmx_pending_event_test
 filter = vmx_ldtr_test, test = vmx_pending_event_hlt_test
 filter = vmx_ldtr_test, test = vmx_store_tsc_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_zero_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_tf_test
 filter = vmx_ldtr_test, test = vmx_preemption_timer_expiry_test
 filter = vmx_ldtr_test, test = ept_access_test_not_present
 filter = vmx_ldtr_test, test = ept_access_test_read_only
 filter = vmx_ldtr_test, test = ept_access_test_write_only
 filter = vmx_ldtr_test, test = ept_access_test_read_write
 filter = vmx_ldtr_test, test = ept_access_test_execute_only
 filter = vmx_ldtr_test, test = ept_access_test_read_execute
 filter = vmx_ldtr_test, test = ept_access_test_write_execute
 filter = vmx_ldtr_test, test = ept_access_test_read_write_execute
 filter = vmx_ldtr_test, test = ept_access_test_reserved_bits
 filter = vmx_ldtr_test, test = ept_access_test_ignored_bits
 filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_disabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_enabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_disabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_enabled
 filter = vmx_ldtr_test, test = ept_access_test_paddr_read_write
 filter = vmx_ldtr_test, test = 

[Bug 1966066] Re: audio from external sound card is distorted

2022-04-19 Thread Po-Hsu Lin
wuwei912 (wuwei912), please give the proposed kernel mentioned in #40 a
try, thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966066

Title:
  audio from external sound card is distorted

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940080] Re: ubuntu-kernel-selftests.ftrace fails on riscv64

2022-04-15 Thread Po-Hsu Lin
With Impish 5.13 riscv, this ftracetest is hanging on the same point:

 # selftests: ftrace: ftracetest
 # === Ftrace unit tests ===
 # [1] Basic trace file check   [PASS]
 # [2] Basic test for tracers   [PASS]
 # [3] Basic trace clock test   [PASS]
 # [4] Basic event tracing check[PASS]
 # [5] Change the ringbuffer size   [PASS]
 # [6] Snapshot and tracing setting [PASS]
 # [7] trace_pipe and trace_marker  [PASS]
 # [8] Test ftrace direct functions against tracers [UNRESOLVED]
 # [9] Test ftrace direct functions against kprobes [UNRESOLVED]
 # [10] Generic dynamic event - add/remove kprobe events[PASS]
 # [11] Generic dynamic event - add/remove synthetic events [UNSUPPORTED]
 # [12] Generic dynamic event - selective clear (compatibility) [UNSUPPORTED]
 # [13] Generic dynamic event - generic clear event [UNSUPPORTED]
 # [14] event tracing - enable/disable with event level files   [PASS]
 # [15] event tracing - restricts events based on pid notrace filtering [PASS]
 # [16] event tracing - restricts events based on pid   [PASS]
 # [17] event tracing - enable/disable with subsystem level files   [PASS]
 # [18] event tracing - enable/disable with top level files [PASS]
 # [19] Test trace_printk from module   [PASS]
 # [20] ftrace - function graph filters with stack tracer   [PASS]
 # [21] ftrace - function graph filters [PASS]
 # [22] ftrace - function trace with cpumask[PASS]
 # [23] ftrace - test for function event triggers   [FAIL]
 # [24] ftrace - function pid notrace filters   [PASS]
 # [25] ftrace - function pid filters   [PASS]
 # [26] ftrace - stacktrace filter command  [PASS]
 # [27] ftrace - function trace on module   [PASS]
* hang here

Failure:
 # [23] ftrace - test for function event triggers   [FAIL]


** Tags added: 5.13 impish sru-20220321

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940080

Title:
  ubuntu-kernel-selftests.ftrace fails on riscv64

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969147] Re: touchpad not working wifi graphics

2022-04-14 Thread Po-Hsu Lin
Hi, 
thanks for the bug report, 18.04 might be too old for your system, please give 
a newer release a try (e.g. 20.04.4, or even the upcoming 22.04) and let us 
know if it helps.

For bug reports, it would be nice to have one issue per report, see:
https://help.ubuntu.com/community/ReportingBugs
https://ubuntu.com/blog/the-keys-to-successful-bug-reporting

Thanks

** Changed in: linux-signed-hwe-5.4 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969147

Title:
  touchpad not working wifi graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1969147/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969090] Re: ubuntu_stress_smoke_test permission errors on jammy

2022-04-14 Thread Po-Hsu Lin
** Tags removed: 5.8
** Tags added: 5.15

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969090

Title:
  ubuntu_stress_smoke_test permission errors on jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961599] Re: i915 [drm] *ERROR* CPU pipe A FIFO underrun on Dell XPS13 9310

2022-04-13 Thread Po-Hsu Lin
Hi,
5.10 OEM kernel is no longer supported, please give 5.14 OEM kernel a try.

** Changed in: linux-oem-5.10 (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961599

Title:
  i915 [drm] *ERROR* CPU pipe A FIFO underrun on Dell XPS13 9310

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915747] Re: notebook lid open wont awake linux

2022-04-13 Thread Po-Hsu Lin
Hi,
5.10 OEM kernel is no longer supported, please give 5.14 OEM kernel a try.

** Changed in: linux-signed-oem-5.10 (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915747

Title:
  notebook lid open wont awake linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1915747/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921148] Re: USB devices fail after Kernel Update 5.10.0-1019-oem

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-signed-oem-5.10 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921148

Title:
  USB devices fail after Kernel Update 5.10.0-1019-oem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1921148/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933762] Re: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05

2022-04-13 Thread Po-Hsu Lin
Hi,
5.10 OEM kernel is no longer supported, please give 5.14 OEM kernel a try.

** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: linux-signed-oem-5.10 (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933762

Title:
  Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not
  working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937913] Re: [Ralink RT3290], Wifi keeps misconfiguring after some time

2022-04-13 Thread Po-Hsu Lin
Hi,
5.10 OEM kernel is no longer supported, please give 5.14 OEM kernel a try.

** Changed in: linux-signed-oem-5.10 (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937913

Title:
  [Ralink RT3290], Wifi keeps misconfiguring after some time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1937913/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933367] Re: Focal update: v5.10.46 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933367

Title:
  Focal update: v5.10.46 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937010] Re: Focal update: v5.10.47 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937010

Title:
  Focal update: v5.10.47 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938025] Re: Focal update: 5.10.48 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938025

Title:
  Focal update: 5.10.48 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938028] Re: Focal update: 5.10.49 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938028

Title:
  Focal update: 5.10.49 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938029] Re: Focal update: 5.10.50 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938029

Title:
  Focal update: 5.10.50 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938031] Re: Focal update: 5.10.51 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938031

Title:
  Focal update: 5.10.51 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938032] Re: Focal update: 5.10.52 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.10 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938032

Title:
  Focal update: 5.10.52 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1948005] Re: Dell 6000 dock freeze and restart since October 19.

2022-04-13 Thread Po-Hsu Lin
Hi,
5.10 OEM kernel is no longer supported, please give 5.14 OEM kernel a try.

** Changed in: linux-oem-5.10 (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948005

Title:
  Dell 6000 dock freeze and restart since October 19.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1954776] Re: Focal update: v5.14.18 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954776

Title:
  Focal update: v5.14.18 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1954780] Re: Focal update: v5.14.19 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954780

Title:
  Focal update: v5.14.19 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1954784] Re: Focal update: v5.14.20 upstream stable release

2022-04-13 Thread Po-Hsu Lin
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954784

Title:
  Focal update: v5.14.20 upstream stable release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >