Cert team has already fixed the test procedure to prevent this issue
happen, so I think this bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069400
Title:
Some DUTs can't boot up
@Dave, I didn't see anything displayed on the monitor with core20.
Only see there is a fixed pattern on ACT LED, 4 long flashes first, followed by
7 short flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Dave, the current focal server image originally can boot on the rev 1.4
rpi3b+, but core20(https://cdimage.ubuntu.com/ubuntu-
core/20/stable/current/) can't, so how do I verify the new firmware
works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "journal log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2070319/+attachment/5792126/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070319
Title:
Public bug reported:
I'm conducting the nvidia driver SRU testing, during test this version
on Focal, I found one of laptop can't perform auto-login after
installing this driver.
[Reproduce]
1. Install ubuntu 20.04
2. Run dist-upgrade to update all the packages.
3. Enable proposed pocket
4.
** Attachment added: "lspci.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069550/+attachment/5790121/+files/lspci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069550
Title:
Public bug reported:
During the SRU testing for 5.15.0-112 kernel on Focal, I found 2 AMD laptops
displayed a black screen.
After some investigation, the impacted laptops both with Picasso/Raven
2(1002:15d8) GPU.
Output for lscpi and journalctl are attached.
If you need more detail, please let
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069400
Title:
Some DUTs can't boot up after installing the hwe kernel in the
Public bug reported:
During the SRU testing for 5.15.0-112 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
Loading Linux 5.15.0-112-generic...
Loading initial ramdisk...
It looks like it's very similar to this bug.
** Description changed:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
- The last messages displayed on the screen are:
+ The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID
Public bug reported:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
** Also affects: linux-intel-iotg-5.15 (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/2056383
Title:
Audio turned to dummy output from
@Francis
I've confirmed that the DUT has already used the latest ubuntu-drivers from
proposed.
Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ...
But it doesn't seem to solve the issue. Please check following messages.
+ _run sudo ubuntu-drivers devices
+ ssh -t -o
Test results for 510 are available at
https://docs.google.com/spreadsheets/d/1VjZ1Jx9vuQPFtmTU-r9hJYDWlrA5dyopHQfQ9LWitlg/edit?usp=sharing
Test results for 390 are available at
https://docs.google.com/spreadsheets/d/1hZrugw1J2oNKFf4ZZzhBE5wmE1HWjZGSOqk6Llt_0ZM/edit?usp=sharing
No regression
** Description changed:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
** Description changed:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
Public bug reported:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
please see the attachment.
I tried glxgear before, it will use nvidia-driver, I can see it by nvidia-smi.
Since we define our test scope using firefox to check, so I report this bug.
Or should I add firefox as impacted package and remove linux package.
--
You received this bug notification because you are a member of
** Summary changed:
- Jammy didn't use nvidia driver whne executing firefox
+ Jammy didn't use nvidia driver when executing firefox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967456
Title:
Public bug reported:
[Reproduce step]
1. Install Jammy beta.
2. Install Nvidia driver by ubuntu-driver install.
3. Connect monitor to dGPU output port.
4. Run firefox, type "about:support" in url, and check column "GPU #1"
[Expected result]
should see nvidia driver info.
[Actual result]
** Also affects: gnome-shell
Importance: Undecided
Status: New
** No longer affects: gnome-shell
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This video shows that what I observed.
** Attachment added: "IMG_6015.mp4"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1967452/+attachment/5575459/+files/IMG_6015.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Reproduce steps]
1. Install jammy beta.
2. Install nvidia-driver by ubuntu-driver install
3. Suspend the system by clicking the button at the upper right corner.
[Expected result]
Should re-enter to desktop.
[Actual result]
Screen keep blinking and don't show the
Please find test results at
https://docs.google.com/spreadsheets/d/1VtJNgxFU4sO8foPgzP2Q-g-flo2sSELecOJnS9pGKXM/edit?usp=sharing.
No regressions were found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to test result at
https://certification.canonical.com/hardware/202002-27718/submission/245770/test-results/pass/?term=media.
This problem has been solved.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because
** Also affects: stress-ng (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/1929788
Title:
Some machines failed in stress-ng test on hirsute
To
@Alex
an update for this issue:
I just tested running fwts with --s3-sleep-type=s3, it can resume normally,
and I heard from Kent Lin and SWE member, dell's laptop don't support s3 for
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Alex, @Ivan
There are some systems' default sleep mode is deep.
Maybe I can ask @sylvain comment on this issue, for the fix is
appropriate to land in checkbox or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Ivan,
I just asked KC, he said if default sleep type is s2idle, it should test
with s2idle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914
Title:
Can't resume from suspend on some specific
That means if I don't use --s3-sleep-type=s2idle, fwts will test with
s3.
What I can see is most of systems can wake from s3, only 4 systems can't
for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Alex,
I use dell system(202001-27665) to test your step.
1.default sleep type is [s2idle] deep
2.use rtcwake to trigger a sleep, and dmesg shows the message ""PM:
suspend entry (s2idle)"
3.if force fwts use s2idle, system can wake.
there is additional information, if I use fwts-21.09 on
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914
Title:
Can't resume from suspend on some specific systems
** Changed in: fwts
Status: New => Confirmed
** Also affects: fwts (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/1956914
Title:
Can't
Test results for 495 are available at
https://docs.google.com/spreadsheets/d/14Kc4yMyGIqUr6oMGzqddlVcMMoY4qpq99crILaH58Os/edit?usp=sharing
Test results for 470 are available at
https://docs.google.com/spreadsheets/d/1kAo_Y8LFIDYY6skpkPGDCrNErG8-rN_ziQ0eJwmYDZ4/edit?usp=sharing
No regression were
You can find test results at
https://docs.google.com/spreadsheets/d/1bjCjuBFXykVvCb_NuxepUjJthqSiiiDQY854-Tqffyw/edit?usp=sharing
No regression were found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Can't read/write SD card after running CPU offline test in 5.11.0-41.45
+ Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Importance: High => Medium
** Changed in: linux-signed-hwe-5.13 (Ubuntu)
Public bug reported:
[Summary]
I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test
always fails.
I found that after CPU offline test, I can't read/write SD card.
After checking dmesg, I got those error msgs.
[ 232.577510] __common_interrupt: 7.34 No irq handler for
Nvidia SRU testing for 470.82 and 495.44 are completed, no regressions were
found.
Test results are available at
https://docs.google.com/spreadsheets/d/1QGCG0fSR9NV7SkURqcJG31nkwob9q4oRxcBni4lZL0w/edit?usp=sharing
and
The test results are available at
https://docs.google.com/spreadsheets/d/10rgG0qyrMdhwjrpHdPecCeDk4MGVZs7iPJdAZcHZZkk/edit#gid=1527963777
No regressions were found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After installing hirsute kernel -36 in Focal, touch pad and keyboard are
still not working. I also tried to install -36 kernel only without dist-
upgrade and disabled proposed then they're working, so I guess it's not
a kernel regression.
--
You received this bug notification because you are a
ii linux-modules-5.11.0-35-generic5.11.0-35.37~20.04.1
amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86
SMP
ii linux-modules-extra-5.11.0-35-generic 5.11.0-35.37~20.04.1
amd64Linux kernel extra modules for
Public bug reported:
[Summary]
Touchpad and keyboard are not working after installing 5.11.0-35 from proposed.
I tried to use 5.11.0-34, keyboard and touchpad are working.
I found there are some error msg through dmesg, not sure are they related to
this issue?
[ 14.586201] psmouse serio1:
Test results are available at
https://drive.google.com/drive/u/1/folders/1ZHwi-YQZUR7pGIo-QcT9NbupnUk5GJPp.
No regressions were found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939673
Title:
** Description changed:
[Summary]
I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from
suspend I can't ssh to it.
When I checked the status of that machine by using command ifconfig, I found
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.
Public bug reported:
[Summary]
I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from
suspend I can't ssh to it.
When I checked the status of that machine by using command ifconfig, I found
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.
[Step to
Test results of nvidia-driver-460 are available at
https://docs.google.com/spreadsheets/d/1OvcC1jFqSrm3fWTDh7HXIxy1uVdrRxfIyrMU8hYp5A4/edit#gid=312612113.
Test results of nvidia-driver-465 are available at
The link of Nvidia SRU testing results are following, no regressions
were found.
460.56: https://docs.google.com/spreadsheets/d/13fPRPMELE6Fal2xNE-
dTDZFJXJ0djH7W3tq0dJa0nB0/edit?usp=sharing
450.102.04: https://docs.google.com/spreadsheets/d
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917718
Title:
Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10
To manage
** Changed in: sssd (Ubuntu)
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/1917718
Title:
Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10
To manage
** Attachment added: "auth.log"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1917718/+attachment/5472408/+files/auth.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917718
Title:
Public bug reported:
[Summary]
Can't auto login after upgrading sssd to 2.3.1-3ubuntu in 20.10
[Steps to reproduce]
1. Install ubuntu 20.10
2. set login automatically while installing.
3. after installation reboot once, it works.
4. run apt update; apt install sssd
5. reboot.
[Failure rate]
5/5
** Attachment added: "output of journalctl -xe"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1917718/+attachment/5472404/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The link of Nvidia SRU testing result is following, no regression was found.
https://docs.google.com/spreadsheets/d/1-efzhthwiePkABHBgVGw8qBQwr8v0wznSEWcA52pjzs/edit#gid=1694297374
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The link of test results is as follows.
https://docs.google.com/spreadsheets/d/1ga7U4PUHjV2TF8ihcsDaEUdoGp7M7Iz11zVs442ZARw/edit?usp=sharing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902093
Hi Alberto,
The link of test results is as follows.
https://docs.google.com/spreadsheets/d/1uMpPgKC88H-mLNbYHm0EQNVp91g-
793H87IGZ16TTQg/edit?usp=sharing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Summary]
Can't boot into system after installing newer version of intel-microcode at the
first time reboot.
If force power off then power on again, machine can boot and reboot normally.
original package version is intel-microcode 3.20180425.
newer package version is
56 matches
Mail list logo
