[Kernel-packages] [Bug 1752437]

2018-11-28 Thread developer
Is anyone else seeing the issue where the touchscreen/pen don't work
when the computer is first powered on (needs to be rebooted at least
once)? If so, was this supposed to be fixed by this or should that be a
separate bug report?

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1871408] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

2020-08-31 Thread Kh Developer
** Also affects: linux
   Importance: Undecided
   Status: New

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel related? 
(This is getting quickly above my pay grade.) I used Grub Customizer to boot 
with kernel 4.18.5-041805-generic and network connectivity/throughput is now 
functioning as it should.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vtpoet 1245 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=b16057ef-f72d-4c02-9450-99b744e2e79c
  InstallationDate: Installed on 2017-08-12 (971 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   wlp58s0   no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20HF0012US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1d490228-1cc4-4d6b-a766-2a6a6b9dbe7d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0012US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HF0012US:pvrThinkPadT470s:rvnLENOVO:rn20HF0012US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0012US
  dmi.product.sku: LENOVO_MT

[Kernel-packages] [Bug 1871408] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

2020-08-31 Thread Kh Developer
The only solution I found to that speed drop was to reconnect to Wi-Fi
or turn it off and on again. I'm not a developer and I don't know how to
report with more data.

All I know is that running the command lspci:

01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 
MGL XL [Radeon Pro WX Vega M GL] (rev c0)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)

** Project changed: linux => ubuntu

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel related? 
(This is getting quickly above my pay grade.) I used Grub Customizer to boot 
with kernel 4.18.5-041805-generic and network connectivity/throughput is now 
functioning as it should.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vtpoet 1245 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=b16057ef-f72d-4c02-9450-99b744e2e79c
  InstallationDate: Installed on 2017-08-12 (971 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   wlp58s0   no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20HF0012US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1d490228-1cc4-4d6b-a766-2a6a6b9dbe7d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 

[Kernel-packages] [Bug 1871408] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

2020-08-31 Thread Kh Developer
apport information

Distro: Ubuntu 20.04 LTS (Focal Fossa)
Kernel version: 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel related? 
(This is getting quickly above my pay grade.) I used Grub Customizer to boot 
with kernel 4.18.5-041805-generic and network connectivity/throughput is now 
functioning as it should.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vtpoet 1245 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=b16057ef-f72d-4c02-9450-99b744e2e79c
  InstallationDate: Installed on 2017-08-12 (971 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   wlp58s0   no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20HF0012US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1d490228-1cc4-4d6b-a766-2a6a6b9dbe7d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0012US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HF0012US:pvrThinkPadT470s:rvnLENOVO:rn20HF0012US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrN

[Kernel-packages] [Bug 1871408] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

2020-08-31 Thread Kh Developer
apport information

The problem affects other linux distributions:
https://forums.linuxmint.com/viewtopic.php?t=309561

** Bug watch added: Linux Kernel Bug Tracker #203709
   https://bugzilla.kernel.org/show_bug.cgi?id=203709

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel related? 
(This is getting quickly above my pay grade.) I used Grub Customizer to boot 
with kernel 4.18.5-041805-generic and network connectivity/throughput is now 
functioning as it should.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vtpoet 1245 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=b16057ef-f72d-4c02-9450-99b744e2e79c
  InstallationDate: Installed on 2017-08-12 (971 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   wlp58s0   no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20HF0012US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1d490228-1cc4-4d6b-a766-2a6a6b9dbe7d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0012US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HF0012US:pvrThinkPadT470s:

[Kernel-packages] [Bug 1871408] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

2020-08-31 Thread Kh Developer
apport information

More information about the problem:
https://bugzilla.kernel.org/show_bug.cgi?id=203709

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel related? 
(This is getting quickly above my pay grade.) I used Grub Customizer to boot 
with kernel 4.18.5-041805-generic and network connectivity/throughput is now 
functioning as it should.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vtpoet 1245 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=b16057ef-f72d-4c02-9450-99b744e2e79c
  InstallationDate: Installed on 2017-08-12 (971 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   wlp58s0   no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20HF0012US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1d490228-1cc4-4d6b-a766-2a6a6b9dbe7d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0012US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HF0012US:pvrThinkPadT470s:rvnLENOVO:rn20HF0012US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name:

[Kernel-packages] [Bug 1871408] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

2020-09-01 Thread Kh Developer
It seems that the error is with some IPv6 configuration. In Ubuntu, I
disabled DNS and Auto Routes and the error went almost unnoticed

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:0010]:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel related? 
(This is getting quickly above my pay grade.) I used Grub Customizer to boot 
with kernel 4.18.5-041805-generic and network connectivity/throughput is now 
functioning as it should.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vtpoet 1245 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=b16057ef-f72d-4c02-9450-99b744e2e79c
  InstallationDate: Installed on 2017-08-12 (971 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   wlp58s0   no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20HF0012US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1d490228-1cc4-4d6b-a766-2a6a6b9dbe7d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0012US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HF0012US:pvrThinkPadT470s:rvnLENOVO:rn20HF0012US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkP

[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-15 Thread Epitiro Developer Account
Please find attached the output of "sudo lspci -vvv" for a 'good state'.

The output for the bad state is empty.

** Attachment added: "sudo lspci -vvv (good state)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862832/+files/lspci_vvv_good_state.txt

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2109794] [NEW] iwlwifi firmware crash (25.04 on CM4 with Intel BE200 96.44729d4e.0)

2025-05-01 Thread Epitiro Developer Account
Public bug reported:

Platform: Raspberry Pi CM4
Wi-Fi chipset: Intel BE200 (Wi-Fi 7).
Driver: iwlwifi loaded with firmware version 96.44729d4e.0.
Error:
iwlwifi :01:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
"This indicates a Non-Maskable Interrupt (NMI), which is typically a critical, 
unhandled error inside the firmware or hardware.
The dump of internal PC (Program Counter) states and memory addresses also 
implies that the firmware encountered a fatal condition and triggered an error 
log dump.

Running the latest image ubuntu-25.04-preinstalled-server-
arm64+raspi.img.xz (from https://ubuntu.com/download/raspberry-pi)

Same hardware works fine in 24.04.

Full apport attached.

Dmesg excerpt:
 May 01 17:07:52 ubuntu kernel: Intel(R) Wireless WiFi driver for Linux
 May 01 17:07:52 ubuntu kernel: iwlwifi :01:00.0: enabling device ( -> 
0002)
 May 01 17:07:52 ubuntu kernel: iwlwifi :01:00.0: Detected crf-id 
0x2001910, cnv-id 0x2001910 wfpm id 0x8000
 May 01 17:07:52 ubuntu kernel: iwlwifi :01:00.0: PCI dev 272b/00f4, 
rev=0x472, rfid=0x112200
 May 01 17:07:52 ubuntu kernel: iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 7 
BE200 320MHz
 May 01 17:07:52 ubuntu kernel: iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 0.0.4.196
 May 01 17:07:52 ubuntu kernel: iwlwifi :01:00.0: loaded firmware version 
96.44729d4e.0 gl-c0-fm-c0-96.ucode op_mode iwlmvm
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: SecBoot CPU1 Status: 
0xf47b, CPU2 Status: 0xb03
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 
WFPM_LMAC1_PD_NOTIFICATION: 0x0
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 
HPM_SECONDARY_DEVICE_STATE: 0x42
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: WFPM_MAC_OTP_CFG7_ADDR: 
0x0
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: WFPM_MAC_OTP_CFG7_DATA: 
0x0
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: UMAC CURRENT PC: 0xd05c18
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: LMAC1 CURRENT PC: 0xd05c20
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: LMAC2 CURRENT PC: 0xd05c24
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: UMAC CURRENT PC 1: 
0xd05c1c
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: TCM1 CURRENT PC: 0xa0444c
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: RCM1 CURRENT PC: 0xa0bd7c
 May 01 17:07:55 ubuntu kernel: Bluetooth: hci1: command 0xfc18 tx timeout
 May 01 17:07:55 ubuntu kernel: Bluetooth: hci1: BCM: failed to write update 
baudrate (-110)
 May 01 17:07:55 ubuntu kernel: Bluetooth: hci1: Failed to set baudrate
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: RCM2 CURRENT PC: 0xb0bd7c
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: Start IWL Error Log Dump:
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: Transport status: 
0x0042, valid: 6
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: Loaded firmware version: 
96.44729d4e.0 gl-c0-fm-c0-96.ucode
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0084 | 
NMI_INTERRUPT_UNKNOWN   
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x02F0 | 
trm_hw_status0
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x | 
trm_hw_status1
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x002C403E | branchlink2
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x002B89AC | 
interruptlink1
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x002B89AC | 
interruptlink2
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x002A57FE | data1
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x6000 | data2
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0F002307 | data3
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x | beacon time
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x001E35D6 | tsf low
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x | tsf hi
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x | time gp1
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0020E765 | time gp2
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0001 | uCode 
revision type
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0060 | uCode 
version major
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x44729D4E | uCode 
version minor
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0472 | hw version
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x00C80002 | board version
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x8006FC00 | hcmd
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x0002 | isr0
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x | isr1
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x48F2 | isr2
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0: 0x00C0001C | isr3
 May 01 17:07:55 ubuntu kernel: iwlwifi :01:00.0:

[Kernel-packages] [Bug 2098131] Re: iwlwifi Microcode SW error and restart issue on Ubuntu 24.04/24.10

2025-02-27 Thread Epitiro Developer Account
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  iwlwifi Microcode SW error and restart issue on Ubuntu 24.04/24.10

Status in linux package in Ubuntu:
  New

Bug description:
  Several of our devices are experiencing crashes/reboots, after which
  the PCI bus is not fully reset and the Wi-Fi card (Intel BE200) is not
  visible until a hard-reboot is performed.

  We're running 
  ubuntu/24.10 (arm64) linux
  6.11.0-1007-raspi
  Firmware version: 92.67ce4588.0 gl-c0-fm-c0-92.ucode

  Review of the logs shows "Microcode SW error detected. Restarting
  0x0." which we assume might be related

  
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Microcode SW error 
detected. Restarting 0x0.
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Start IWL Error Log Dump:
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Transport status: 
0x004A, valid: 6
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Loaded firmware version: 
92.67ce4588.0 gl-c0-fm-c0-92.ucode
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x28BF | 
ADVANCED_SYSASSERT  
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x00A002F0 | 
trm_hw_status0
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | 
trm_hw_status1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002C43D6 | branchlink2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002B89BE | 
interruptlink1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002B89BE | 
interruptlink2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0002 | data1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x009B | data2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0xDEADBEEF | data3
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0xF240E965 | beacon time
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x11C788C6 | tsf low
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0CA4 | tsf hi
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | time gp1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x39C9A6E0 | time gp2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0001 | uCode 
revision type
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x005C | uCode 
version major
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x67CE4588 | uCode 
version minor
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0472 | hw version
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x00C80002 | board 
version
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x8021FD26 | hcmd
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0002 | isr0
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0040 | isr1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x48F80002 | isr2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x44D0041C | isr3
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x3000 | isr4
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x01EE001C | last cmd Id
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x00015776 | wait_event
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x1414 | l2p_control
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | l2p_duration
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | l2p_mhvalid
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | 
l2p_addr_match
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | timestamp
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0xD8D8 | flow_handler
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Start IWL Error Log Dump:
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Transport status: 
0x004A, valid: 6
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: Loaded firmware version: 
92.67ce4588.0 gl-c0-fm-c0-92.ucode
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0073 | 
NMI_INTERRUPT_OTHER_LMAC_FATAL
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x02F0 | 
trm_hw_status0
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | 
trm_hw_status1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002C43D6 | branchlink2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002B89BE | 
interruptlink1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002B89BE | 
interruptlink2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x002A58E6 | data1
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x0002 | data2
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0x | data3
  Feb 11 10:01:16 ubuntu kernel: iwlwifi :01:00.0: 0xF240E919 | beacon time
  Feb 11 10:0

[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-07 Thread Epitiro Developer Account
>> >> FWIW, can you test this kernel:
https://people.canonical.com/~juergh/lp2099935/

Got it working (I think) by removing linux-image-6.11.0-1010.

Unfortunately, the PCI problem persists.


ubuntu@ubuntu:~$ uname -a
Linux ubuntu 6.11.0-1009-raspi #9+cbd1 SMP PREEMPT_DYNAMIC Thu Mar  6 12:57:06 
UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@ubuntu:~$ lspci -vvv
ubuntu@ubuntu:~$

I've attached the fill dmesg output from initial boot (working) and
following panic (not working).



** Attachment added: "dmesg_6.11.0-1009-outputs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862948/+files/dmesg_6.11.0-1009-outputs.zip

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-07 Thread Epitiro Developer Account
Full output from:
sudo dpkg -i linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb

** Attachment added: "dpkg output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862885/+files/dpkg_output.txt

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-06 Thread Epitiro Developer Account
Yes, the problem exists with 6.8 (that's actually where we first noticed it was 
occurring).
"operatingSystem": "Ubuntu 24.04 LTS"
"kernel": "6.8.0-1019-raspi"

One update to share is that the problem does also occur on Raspberry Pi
OS as well (contrary to what I stated above). It also occurs ~50% of the
time (I just got lucky when previously testing and got a string of
successful tests).

Given that it works ~50% of the time it might be some kind of race
condition. I wonder if there are any ways to test delaying the pci
initialization that can be applied via configuration?

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-07 Thread Epitiro Developer Account
Full output from:
sudo dpkg -i linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb

** Attachment added: "dpkg output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5862884/+files/dpkg_output.txt

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-07 Thread Epitiro Developer Account
>> FWIW, can you test this kernel:
https://people.canonical.com/~juergh/lp2099935/

Are you able to give some pointers on how to install this correctly?
I've tried several things but I must be doing something wrong or missing
a step.

As a starting point my test system already had(/has) 6.11.0-1010-raspi
installed.

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 6.11.0-1010-raspi #10-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 25 
02:37:49 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

I tried these steps:
sudo dpkg -i linux-buildinfo-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
sudo dpkg -i linux-headers-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
sudo dpkg -i linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb
sudo dpkg -i linux-modules-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb

and they complete with no errors, but following reboot, 'uname -a' still
reports 6.11.0-1010-raspi and not 6.11.0-1009-raspi as I assume it
should.

I note that the output to 'ubuntu@ubuntu:~/test_kernel$ sudo dpkg -i
linux-image-6.11.0-1009-raspi_6.11.0-1009.9+cbd1_arm64.deb' indicated it
was installing 1009 and then 1010... which looks suspicious (full output
attached):

update-initramfs: Generating /boot/initrd.img-6.11.0-1009-raspi
Using DTB: bcm2711-rpi-cm4.dtb
Installing 
/lib/firmware/6.11.0-1009-raspi/device-tree/broadcom/bcm2711-rpi-cm4.dtb into 
/boot/dtbs/6.11.0-1009-raspi/./bcm2711-rpi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
flash-kernel: deferring update (trigger activated)
/etc/kernel/postinst.d/zz-flash-kernel:
Using DTB: bcm2711-rpi-cm4.dtb
Installing 
/lib/firmware/6.11.0-1009-raspi/device-tree/broadcom/bcm2711-rpi-cm4.dtb into 
/boot/dtbs/6.11.0-1009-raspi/./bcm2711-rpi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
flash-kernel: deferring update (trigger activated)
Processing triggers for flash-kernel (3.107ubuntu13~24.10.2) ...
Using DTB: bcm2711-rpi-cm4.dtb
Installing 
/lib/firmware/6.11.0-1010-raspi/device-tree/broadcom/bcm2711-rpi-cm4.dtb into 
/boot/dtbs/6.11.0-1010-raspi/./bcm2711-rpi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
flash-kernel: installing version 6.11.0-1010-raspi

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
Is it possible that the issue might be related to the hardware watchdog
timer? I note the following lines in the dmesg output:

[2.214004] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[2.288820] watchdog: Delayed init of the lockup detector failed: -19
[2.295372] watchdog: Hard watchdog permanently disabled

Is this expected output for a CM4? I've tried researching how to enable
it but am a little out of my depth.

cat /boot/config-$(uname -r) | grep BCM2835_WDT
CONFIG_BCM2835_WDT=y

This suggests the BCM2835 support is compiled into the kernel.

Are there any other configuration items I can modify to properly enable
the hard watchdog?

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
The CM4 is plugged into "CM4_WiFi7-PoE" board, please see
http://wiki.mcuzone.com/index.php?title=2004_CM4_WiFi7_WiFi6_WLANPi for
more information.

Is this the correct way to check the bootloader version?

ubuntu@ubuntu:~$ sudo vcgencmd bootloader_version
2023/01/11 17:40:52
version 8ba17717fbcedd4c3b6d4bce7e50c7af4155cba9 (release)
timestamp 1673458852
update-time 0
capabilities 0x007f
ubuntu@ubuntu:~$

ubuntu@ubuntu:~$ sudo vcgencmd version
Feb 29 2024 12:24:53
Copyright (c) 2012 Broadcom
version f4e2138c2adc8f3a92a3a65939e458f11d7298ba (clean) (release) (start)


A few notes:
- The manufacturer is able to reproduce the same issue. They have reported that 
the same issue does not occur if you swap the CM4 with a CM5, but I need to 
verify this once I obtain a CM5.
- The issue does not occur when using Raspberry Pi OS (as noted above)

>> I cannot reproduce this locally. For me, PCI devices always show up
after a reboot-after-crash.

Thanks for trying to reproduce - I can make a remote test environment
available if that helps.

It occurs ~half the time for us. I've attached some example test runs
dmesg outputs (these were done with additional
/boot/firmware/cmdline.txt parameters set (pcie_aspm=off as part of an
experiment)

** Attachment added: "dmesg output after panic - 10 runs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5861155/+files/dmesg%20output%20from%2010%20tests.zip

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
The CM4 is plugged into a Wi-Fi 7 Expansion Board (with Intel BE200 Wi-
Fi card) with PoE Ethernet from MCU Zone.

The system is configured to reboot by modifying the /etc/sysctl.conf
file to include:

kernel.panic = 5

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
dmesg output from cold boot (where pci is working) and following
panic/restart (where pci is not working) captured from upgraded kernel:

** Attachment added: "dmesg output from  Linux ubuntu 6.11.0-1008-raspi"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5860609/+files/6_11_dmesg_before_and_after_panic.zip

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
Yes, it's reproducible on the latest raspi kernel.

Please find attached the dmesg output from cold boot (where pci is
working) and following panic/restart (where pci is not working) captured
from upgraded kernel:

Linux ubuntu 6.11.0-1008-raspi #8-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 21
12:05:23 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
>> via the -proposed pocket you could even try out the latest version
6.11.0-1010.10.

With the proposed pocket the issue is improved- the issue occurs about
~50% of the time the test is repeated.


Linux ubuntu 6.11.0-1010-raspi #10-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 25 
02:37:49 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux


I added 'proposed' to the config in
/etc/apt/sources.list.d/ubuntu.sources 

and installed with
sudo apt install linux-image-raspi -t oracular-proposed
sudo apt install linux-firmware -t oracular-proposed

I've attached dmesg output for the two cases:
6_11_1010_dmesg_after_panic_initialized_ok.txt
6_11_1010_dmesg_after_panic_initialization_failed.txt

That seems like progress - do you have any recommendations on further
troubleshooting/investigation steps from here?

** Attachment added: "dmesg output from 6.11.0-1010-raspi"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5860659/+files/6_11_1010_dmesg_after_panic.zip.zip

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
The problem doesn't occur on Raspberry Pi OS so I thought it might be
helpful to compare the following for each platform:

/boot/config-$(uname -r)
/boot/firmware/cmdline.txt
/boot/firmware/config.txt
dmesg

The zip file attached contains the files.


** Attachment added: "Ubuntu and RPI OS kernel config, cmdline, config and 
dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5860496/+files/ubuntu_vs_rpios.zip

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-04 Thread Epitiro Developer Account
After upgrade to pieeprom-2024-04-15.bin the problem is still
reproducible following panic/reboot.


ubuntu@ubuntu:~$ sudo dmesg | grep Down
[   24.148659] bcmgenet fd58.ethernet eth0: Link is Down

ubuntu@ubuntu:~$ lspci

ubuntu@ubuntu:~$ sudo vcgencmd bootloader_version
2024/04/15 14:12:14
version e608a69d210bb737ebb095ad04f7f1a05373a6ec (release)
timestamp 1713186734
update-time 1740768767
capabilities 0x007f

ubuntu@ubuntu:~$ sudo vcgencmd version
Feb 29 2024 12:24:53
Copyright (c) 2012 Broadcom
version f4e2138c2adc8f3a92a3a65939e458f11d7298ba (clean) (release) (start)

ubuntu@ubuntu:~$ sudo dmesg | grep firmware
[0.091203] raspberrypi-firmware soc:firmware: Attached to firmware from 
2024-02-29T12:24:53, variant start
[0.092217] raspberrypi-firmware soc:firmware: Firmware hash is 
f4e2138c2adc8f3a92a3a65939e458f11d7298ba

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-06 Thread Epitiro Developer Account
>> The manufacturer is able to reproduce the same issue. They have
reported that the same issue does not occur if you swap the CM4 with a
CM5, but I need to verify this once I obtain a CM5

Confirmed - this issue does not occur with the CM5.

For whatever reason, it's specific the CM4

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-01 Thread Epitiro Developer Account
** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-02-28 Thread Epitiro Developer Account
RE #5: A attached the apport information to the ticket submission. It's
a headless system so I just copied/attached it directly. Are there any
debug outputs I can gather to help troubleshoot?

RE #6: "Was there a time in the past when you did not encounter this
behavior with an Ubuntu image, or has this always been an issue?

We've only ever used 24.04 and 24.10. Both exhibit the same issue. We've
selected 24.04 and 24.10 because we are connecting with intel BE200 Wi-
Fi 7 which requires kernel 6.5 or higher with

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-02-28 Thread Epitiro Developer Account
dmesg output in cold boot with pci initialization working

** Attachment added: "ubuntu_dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+attachment/5860224/+files/ubuntu_dmesg.txt

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-02-28 Thread Epitiro Developer Account
correcting package to 'linux'

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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


[Kernel-packages] [Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

2025-03-13 Thread Epitiro Developer Account
Hi Juerg,

The problem appears to be fixed by updating the unit with the latest
pieeprom-2025-02-11.bin that is shipping with Raspberry Pi OS

https://github.com/raspberrypi/rpi-
eeprom/blob/master/firmware-2711/default/pieeprom-2025-02-11.bin.

I've been unable to reproduce the issue after upgrading to this version
(200+ tests so far).

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

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Server 24.10 
  Linux ubuntu 6.11.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 
22:25:34 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

  We're seeing that following a kernel panic and reboot, the PCI fails
  to initialize correctly and associated  devices (such as Wi-Fi card)
  are not available.

  Issue Description:
  • On the first boot, everything works correctly.
  • However, after a Kernel Panic, the device reboots, but PCIe does not 
reset or re-initialize properly.
  • When this happens:
  o The Wi-Fi card is not recognized.
  o The lspci command shows no PCI devices.
  o The dmesg log includes the message:

  [0.591441] brcm-pcie fd50.pcie: link down

  • A soft reboot does not fix the issue.
  • The only way to recover is to completely remove and reconnect power 
(hard reboot).

  
  We have tried modifying /boot/firmware/config.txt and 
/boot/firmware/cmdline.txt, which has reduced but not fully resolved the issue.

  How to Reproduce The Problem:
  1.Power up the hardware
  2.Run ‘lspci’ – observe the result includes the PCI Bridge and Wi-Fi card
  3.Trigger a kernel panic with the command ‘echo c | sudo tee 
/proc/sysrq-trigger’, causing a reboot
  4.Run ‘lspci’ – observer the output is now empty

  
  The same issue does not occur on Raspberry Pi OS - it seems to be specific to 
Ubuntu.

  Any assistance/guidance on how to troubleshoot this would be much
  appreciated!

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


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