Launchpad has imported 7 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201379.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2018-10-11T18:32:59+00:00 caravena wrote: Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1796385 "I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg." Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/5 ------------------------------------------------------------------------ On 2018-10-12T11:41:09+00:00 linux wrote: Talk about shooting the messenger. The kernel's watchdog (kernel/watchdog.c) reports a stalled CPU. This is not a problem with the kernel's watchdog. The kernel watchdog just reports the problem. It is also not a problem with the watchdog subsystem, which is not even involved. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/7 ------------------------------------------------------------------------ On 2018-10-12T11:49:55+00:00 caravena wrote: @Guenter, Could you change to where it corresponds in bugzilla if it is not in 'watchdog' this report? Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/8 ------------------------------------------------------------------------ On 2018-10-12T11:57:40+00:00 linux wrote: The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/9 ------------------------------------------------------------------------ On 2018-10-12T11:59:53+00:00 linux wrote: Also, I don't think I have permission to change any of the bug status fields. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/10 ------------------------------------------------------------------------ On 2018-10-12T12:15:48+00:00 caravena wrote: @Guenter, I change it, but I do not know what 'Product' and 'Component'. Best regards, -- Cristian Aravena Romero (caravena) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/11 ------------------------------------------------------------------------ On 2018-10-12T17:12:33+00:00 linux wrote: Unfortunately we do not have information to determine 'Product' and 'Component'. The only information we have is that the hanging process is gnome-shell (or at least that this was the case in at least one instance), that the screen blinks and freezes when the problem is observed, and that the hanging CPU served most of the graphics card interrupts. If it is persistent, it _might_ suggest that graphics (presumably the Radeon graphics driver and/or the graphics hardware) is involved. This would be even more likely if the observed PCIe errors point to the graphics card (not sure if the information provided shows the PCIe bus tree; if so I have not found it). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/comments/13 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- 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/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F.... pulseaudio /dev/snd/controlC1: greg 2039 F.... pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lo no wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+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
