Your message dated Thu, 30 Jul 2020 13:50:01 +0200
with message-id <[email protected]>
and subject line Re: Bug#758793: 758793
has caused the Debian Bug report #758793,
regarding base: Random lockups. Can only ALT+SYSRQ+REISUB to reboot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
758793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758793
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: base
Severity: important
Hello,
I've started getting random lockups while using XFCE, iceweasel, icedove. The
screen will freeze but the mouse cursor can be moved around,with no ability to
click anywhere.
Sometimes if I'm lucky I might be able to CTRL+ALT+F1 into a console and
manually restart lightdm. Everything is ok for a bit, then back to a random
lockup.
I can't find any error log entries, except these: (which are way too early in
the boot process)
Aug 21 15:15:17 kernel: [ 0.323186] Unpacking initramfs...
Aug 21 15:15:17 kernel: [ 1.201565] irq 9: nobody cared (try booting with
the "irqpoll" option)
Aug 21 15:15:17 kernel: [ 1.201628] CPU: 1 PID: 1 Comm: swapper/0 Not
tainted 3.14-2-amd64 #1 Debian 3.14.15-2
Aug 21 15:15:17 kernel: [ 1.201630] Hardware name: TOSHIBA Satellite
P300D/Satellite P300D, BIOS V3.30 09/23/2009
Aug 21 15:15:17 kernel: [ 1.201634] ffff8801310076c4 ffffffff814c5732
ffff880131007600 ffffffff810b37f8
Aug 21 15:15:17 kernel: [ 1.201639] ffff880131007600 0000000000000009
0000000000000000 ffffffff810b3d11
Aug 21 15:15:17 kernel: [ 1.201642] 0000000000000000 0000000000000000
0000000000000009 0000000000000000
Aug 21 15:15:17 kernel: [ 1.201647] Call Trace:
Aug 21 15:15:17 kernel: [ 1.201649] <IRQ> [<ffffffff814c5732>] ?
dump_stack+0x41/0x51
Aug 21 15:15:17 kernel: [ 1.201662] [<ffffffff810b37f8>] ?
__report_bad_irq+0x28/0xc0
Aug 21 15:15:17 kernel: [ 1.201666] [<ffffffff810b3d11>] ?
note_interrupt+0x241/0x290
Aug 21 15:15:17 kernel: [ 1.201670] [<ffffffff810b1781>] ?
handle_irq_event_percpu+0xc1/0x1b0
Aug 21 15:15:17 kernel: [ 1.201673] [<ffffffff810b18a3>] ?
handle_irq_event+0x33/0x50
Aug 21 15:15:17 kernel: [ 1.201677] [<ffffffff810b4728>] ?
handle_fasteoi_irq+0x58/0x100
Aug 21 15:15:17 kernel: [ 1.201684] [<ffffffff81015a58>] ?
handle_irq+0x18/0x30
Aug 21 15:15:17 kernel: [ 1.201688] [<ffffffff81015374>] ? do_IRQ+0x44/0xe0
Aug 21 15:15:17 kernel: [ 1.201692] [<ffffffff814cb3ad>] ?
common_interrupt+0x6d/0x6d
Aug 21 15:15:17 kernel: [ 1.201694] <EOI> [<ffffffff81297e16>] ?
inflate_fast+0x106/0x610
Aug 21 15:15:17 kernel: [ 1.201702] [<ffffffff81299709>] ?
zlib_inflate+0x11e9/0x19c0
Aug 21 15:15:17 kernel: [ 1.201708] [<ffffffff818d36fd>] ?
write_buffer+0x1d/0x2b
Aug 21 15:15:17 kernel: [ 1.201712] [<ffffffff818d370b>] ?
write_buffer+0x2b/0x2b
Aug 21 15:15:17 kernel: [ 1.201717] [<ffffffff8190632e>] ?
bunzip2+0x3ff/0x3ff
Aug 21 15:15:17 kernel: [ 1.201720] [<ffffffff8190657b>] ?
gunzip+0x249/0x30e
Aug 21 15:15:17 kernel: [ 1.201724] [<ffffffff818d39f9>] ?
unpack_to_rootfs+0x149/0x26a
Aug 21 15:15:17 kernel: [ 1.201727] [<ffffffff818d3676>] ?
initrd_load+0x3a/0x3a
Aug 21 15:15:17 kernel: [ 1.201731] [<ffffffff818d3e1f>] ?
maybe_link.part.2+0xff/0xff
Aug 21 15:15:17 kernel: [ 1.201735] [<ffffffff818d3e78>] ?
populate_rootfs+0x59/0x10c
Aug 21 15:15:17 kernel: [ 1.201740] [<ffffffff8100212a>] ?
do_one_initcall+0xca/0x170
Aug 21 15:15:17 kernel: [ 1.201744] [<ffffffff8107ede8>] ?
parse_args+0x228/0x400
Aug 21 15:15:17 kernel: [ 1.201749] [<ffffffff818d3066>] ?
kernel_init_freeable+0x15f/0x1e1
Aug 21 15:15:17 kernel: [ 1.201753] [<ffffffff818d28ac>] ?
do_early_param+0x81/0x81
Aug 21 15:15:17 kernel: [ 1.201757] [<ffffffff814b7e20>] ?
rest_init+0x70/0x70
Aug 21 15:15:17 kernel: [ 1.201760] [<ffffffff814b7e25>] ?
kernel_init+0x5/0xf0
Aug 21 15:15:17 kernel: [ 1.201763] [<ffffffff814d308c>] ?
ret_from_fork+0x7c/0xb0
Aug 21 15:15:17 kernel: [ 1.201767] [<ffffffff814b7e20>] ?
rest_init+0x70/0x70
Aug 21 15:15:17 kernel: [ 1.201769] handlers:
Aug 21 15:15:17 kernel: [ 1.201822] [<ffffffff812ed2a8>] acpi_irq
Aug 21 15:15:17 kernel: [ 1.201912] Disabling IRQ #9
Aug 21 15:15:17 kernel: [ 1.521932] Freeing initrd memory: 15860K
(ffff8800360f6000 - ffff880037073000)
Running with irqpoll leads to a different error (IMHO unrelated). Running
acpi=off leads to no error during boot up but random lockups again.
Didn't know which package I should file this bug against, since I honestly
don't know what's causing it. The system doesn't give any other indication
through logs that something is wrong when it locks up.
It can happen right after logging in, while idling on desktop, or while under
load. Again, no indication as to what is causing it, since what causes one
lockup doesn't cause the next one.
Running Jessie, but the problem started appearing a few months back in wheezy.
Suspected HDD, SMART data says it's fine. Suspected RAM, memtest86+ says its
fine after multiple rounds. It could be a faulty motherboard (the laptop is 5
years old) but I've seen mentions of ubuntu also having the same random lockups
on newer laptops. https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1184451
Thank you,
Demetris Demetriou
deZillium LTD
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
* deZillium <[email protected]> [200730 11:48]:
> Sep 22 07:55:52 hostname anacron[9071]: Job `cron.weekly' terminated
> Sep 22 07:55:52 hostname anacron[9071]: Normal exit (2 jobs run)
> Sep 22 07:57:49 hostname kernel: [68319.596102] radeon 0000:01:00.0: GPU
> lockup CP stall for more than 10000msec
> Sep 22 07:57:49 hostname kernel: [68319.596129] radeon 0000:01:00.0: GPU
> lockup (waiting for 0x0000000000080a57 last fence id 0x0000000000080a56 on
> ring 0)
> Sep 22 07:57:49 hostname kernel: [68319.596146] radeon 0000:01:00.0: failed
> to get a new IB (-35)
> Sep 22 07:57:49 hostname kernel: [68319.596156] [drm:radeon_cs_ib_fill]
> *ERROR* Failed to get ib !
Sorry, after 6 years it's unlikely someone will investigate this
further. If this is still a problem, it's probably best to take it
to the upstream radeon driver maintainers.
Chris
--- End Message ---
