[Kernel-packages] [Bug 2039481] Re: cannot allocate memory using vbi0
Nobody? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039481 Title: cannot allocate memory using vbi0 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I think this issue started happening with a late 5.x kernel and has persisted through 6.x # cat < /dev/vbi0 cat: -: Cannot allocate memory I should be getting data from the vbi0 device. # lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 I'm not sure if this is a bt878 bug but seems a good place to start. Happy to provide more details as requested. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 13:33:05 2023 Dependencies: linux-modules-6.2.0-34-generic 6.2.0-34.34~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2022-01-26 (627 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039481/+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 2039481] Re: cannot allocate memory using vbi0
Nobody? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039481 Title: cannot allocate memory using vbi0 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I think this issue started happening with a late 5.x kernel and has persisted through 6.x # cat < /dev/vbi0 cat: -: Cannot allocate memory I should be getting data from the vbi0 device. # lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 I'm not sure if this is a bt878 bug but seems a good place to start. Happy to provide more details as requested. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 13:33:05 2023 Dependencies: linux-modules-6.2.0-34-generic 6.2.0-34.34~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2022-01-26 (627 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039481/+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 2039481] [NEW] cannot allocate memory using vbi0
Public bug reported: I think this issue started happening with a late 5.x kernel and has persisted through 6.x # cat < /dev/vbi0 cat: -: Cannot allocate memory I should be getting data from the vbi0 device. # lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 I'm not sure if this is a bt878 bug but seems a good place to start. Happy to provide more details as requested. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 13:33:05 2023 Dependencies: linux-modules-6.2.0-34-generic 6.2.0-34.34~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2022-01-26 (627 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bt878 bttv jammy v4l vbi vbi0 video4linux ** Tags added: bt878 bttv v4l vbi vbi0 video4linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039481 Title: cannot allocate memory using vbi0 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I think this issue started happening with a late 5.x kernel and has persisted through 6.x # cat < /dev/vbi0 cat: -: Cannot allocate memory I should be getting data from the vbi0 device. # lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 I'm not sure if this is a bt878 bug but seems a good place to start. Happy to provide more details as requested. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 13:33:05 2023 Dependencies: linux-modules-6.2.0-34-generic 6.2.0-34.34~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2022-01-26 (627 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039481/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Another Ryzen 7 1800X user here with similar random crashes. [165716.089703] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [165716.095949] rcu:1-...!: (0 ticks this GP) idle=354/0/0x0 softirq=2154363/2154363 fqs=0 [165716.104512] rcu:3-...!: (0 ticks this GP) idle=29c/0/0x0 softirq=883832/883832 fqs=0 [165716.112873] rcu:4-...!: (8 GPs behind) idle=ad8/0/0x0 softirq=2165586/2165586 fqs=0 [165716.121179] rcu:9-...!: (9 GPs behind) idle=acc/0/0x0 softirq=1340600/1340600 fqs=0 [165716.129467] rcu:11-...!: (2 GPs behind) idle=a18/0/0x0 softirq=4538536/4538537 fqs=0 [165716.137828] rcu:12-...!: (0 ticks this GP) idle=870/0/0x0 softirq=2158040/2158040 fqs=0 [165775.697763] rcu: rcu_sched kthread starved for 29898 jiffies! g36134941 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 [165775.709013] rcu: RCU grace-period kthread stack dump: [165837.494623] watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [(resolved):52315] [165865.494840] watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [(resolved):52315] [165893.495058] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [(resolved):52315] [165921.495276] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [(resolved):52315] [165949.495494] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [(resolved):52315] Unfortunaltey I didn't have sysrq configured so I can't provide more information other than I also have an X370 motherboard. The system is not not has it ever been overlocked. I've owned all the componentes since new so I'm not going to be able to RMA them like some others have. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel:
