[Bug 2015688] Re: ould not resolve symbol [/_SB.PCI0.GPP7.UP00.DP40.UP00.DP68]

Thu Jul 6 15:52:10 UTC 2023

Today I got security updates, which I loaded, and there was a new NVIDIA
driver 535, which I loaded. Afterwards I still got the error messages,
but this time the boot process continued.

I wonder whether there might have been an update to NVIDIA 525 a few
days ago. Perhaps that was the culprit.

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

Title:
  ould not resolve symbol [/_SB.PCI0.GPP7.UP00.DP40.UP00.DP68]

Status in grub2 package in Ubuntu:
  Invalid

Bug description:
  UPDATE: LATEST ERROR MESSAGES:

  [00.243066] ACPI BIOS Error (bug): Could not resolve symbol [/_SB.PCI0.GPP7.UP00.DP40.UP00.DP68], AE_NOT_FOUND (20221020/dswload2-162)
  [00.243074] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
  [00.805442] hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19) /dev/sdc2: clean, 210180/30457856 files, 6717706/121820928 blocks
  [18.690139] Bluetooth: hci0: Failed to read codec capabilities (-22)
  [19.224107]

  MANUALLY TYPED THIS OUT D:

  [00.243401] ACPI BIOS Error (bug): Could not resolve symbol [/_SB.PCI0.GPP7.UP00.DP40.UP00.DP68], AE_NOT_FOUND (20221020/dswload2-162)
  [00.243411] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
  [01.013874] hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19) /dev/sdc2: clean, 165351/30457856 files, 6221676/121820928 blocks
  [14.235653] Bluetooth: hci0: Failed to read codec capabilities (-22)
  [19.155053] rtw89_8852be 0000:0a:00.0: MAC has already powered on
  [19.241064] b43-phy1 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
  [20.907235]

  I get the above error on boot. I think the issue with the hub is only
  because I have decided to use this USB hub, which requires a really
  invasive driver on Windows / OS X to actually work to its full
  capacity (ALOGIC Twin Dock HD PRO) but otherwise all the other errors
  are AFAIK related to my AM5 system. (ASUS PRIME X670P WIFI+CSM for AM5
  using the 7600X). There are other errors which I will try to report
  through the beta testing program but anyway this is the first problem
  that occurs if I install the system without making use of LVM+LUKS
  (pretty certain its an issue with the new installer so I am not even
  bothering with that issue. April 21st I'll be just upgrading my
  existing system anyway so it won't be a problem for me mostly.).

  What else....... Hmm....... I am using a NEXTECH SATA HDD Docking
  Station XC-4689 to boot the system, connected via USB, prefer
  connecting the drive to HDD2 but again this should be a non-issue. I'm
  on d/UBUNTU_HIDEOUT as you-nerd#8192 if you want me to run any
  additional tests / produce any additional logs. I will be swapping
  back to my installation of 22.10 (which also produces the same
  problem, in accordance with the error message -- 20221020) after I
  report all the bugs that are relevant.

  This could be a security vulnerability given that there is a rogue
  BIOS device/mechanism that is just connected and I am on blue team (so
  no pen testing), hence I will leave the checkbox unchecked because idk
  of any exploits surrounding this.

  Kind Regards,

  you-nerd

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 10 01:41:12 2023
  InstallationDate: Installed on 2023-04-09 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=<set>
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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