From: Pavel Machek <pavel@ucw.cz>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: bp@alien8.de, hpa@zytor.com,
kernel list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, tglx@linutronix.de, x86@kernel.org,
jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: v4.20-rc1: list_del corruption on thinkpad x220
Date: Wed, 21 Nov 2018 12:54:49 +0100 [thread overview]
Message-ID: <20181121115449.GA32455@amd> (raw)
In-Reply-To: <154279919462.20217.14259089584802660420@jlahtine-desk.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 5468 bytes --]
Hi!
> > My machine locked hard (thinkpad x220). After reboot, I found this in
> > syslog:
> >
> > Sounds like memory corruption..? Does not sound like easy to debug.
>
> Were you doing something GPU intense when you experienced the hard hang?
>
> And if so, have you been able to hit the issue more than once? At this
> point it doesn't look like anything we've hit previously, so would be
> great to have some more insight into how we could reproduce.
I seen another crash since that, but I don't think it counts at
"easily reproducible".
I may have been running flightgear at that point. That's fairly GPU intensive.
> There's one similar for nouveau in Bugzilla, but it seems like a genuine
> memory corruption (1 bit flipped):
>
> https://bugs.freedesktop.org/show_bug.cgi?id=84880
>
> Any extra information would be of use :)
>
> Regards, Joonas
>
> PS. Could you open a bug to Bugzilla, it'll help to collect the
> information in one consolidated place:
>
> https://01.org/linuxgraphics/documentation/how-report-bugs
I prefer email... certainly for bugs that can't be reproduced.
Best regards,
Pavel
> > > > ...otoh, it still looks like an addres, so maybe it is "just" race in
> > GPU drivers?
> >
> > Any ideas?
> > Pavel
> >
> > Nov 8 18:35:01 duo CRON[28511]: (root) CMD (command -v debian-sa1 >
> > /dev/null && debian-sa
> > 1 1 1)
> > Nov 8 18:42:57 duo kernel: list_del corruption. prev->next should be
> > ffff8801742b8178, but
> > was ffffc9000192fec8
> > Nov 8 18:42:57 duo kernel: ------------[ cut here ]------------
> > Nov 8 18:42:57 duo kernel: kernel BUG at
> > /data/fast/l/k/lib/list_debug.c:53!
> > Nov 8 18:42:57 duo kernel: invalid opcode: 0000 [#1] SMP PTI
> > Nov 8 18:42:57 duo kernel: CPU: 2 PID: 1082 Comm: i915/signal:1 Not
> > tainted 4.20.0-rc1+ #3
> > Nov 8 18:42:57 duo kernel: Hardware name: LENOVO 42872WU/42872WU,
> > BIOS 8DET74WW (1.44 ) 03
> > /13/2018
> > Nov 8 18:42:57 duo kernel: RIP:
> > 0010:__list_del_entry_valid+0x8e/0x90
> > Nov 8 18:42:57 duo kernel: Code: 66 88 d1 ff 0f 0b 48 89 fe 31 c0 48
> > c7 c7 90 74 5e 85 e8
> > 53 88 d1 ff 0f 0b 48 89 fe 31 c0 48 c7 c7 c8 74 5e 85 e8 40 88 d1 ff
> > <0f> 0b 55 48 89 d0 48
> > 8b 52 08 48 89 e5 48 39 f2 75 19 48 8b 32 48
> > Nov 8 18:42:57 duo kernel: RSP: 0000:ffffc9000196be78 EFLAGS:
> > 00210086
> > Nov 8 18:42:57 duo kernel: RAX: 0000000000000054 RBX:
> > ffff8801742b8178 RCX: 00000000000000
> > 00
> > Nov 8 18:42:57 duo kernel: RDX: 0000000000000000 RSI:
> > ffff88019e2a53d8 RDI: ffff88019e2a53
> > d8
> > Nov 8 18:42:57 duo kernel: RBP: ffffc9000196be78 R08:
> > ffff880196e2cd10 R09: 00000000000000
> > 00
> > Nov 8 18:42:57 duo kernel: R10: 00000000e7684eb9 R11:
> > 3863656632393101 R12: ffffc9000196be
> > c8
> > Nov 8 18:42:57 duo kernel: R13: ffff88019707e000 R14:
> > ffff8801742b8080 R15: ffffc9000192fd
> > d0
> > Nov 8 18:42:57 duo kernel: FS: 0000000000000000(0000)
> > GS:ffff88019e280000(0000) knlGS:000
> > 0000000000000
> > Nov 8 18:42:57 duo kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> > 0000000080050033
> > Nov 8 18:42:57 duo kernel: CR2: 00000000ed2bf000 CR3:
> > 000000000581e001 CR4: 00000000000606a0
> > Nov 8 18:42:57 duo kernel: Call Trace:
> > Nov 8 18:42:57 duo kernel: intel_breadcrumbs_signaler+0x162/0x330
> > Nov 8 18:42:57 duo kernel: kthread+0x116/0x150
> > Nov 8 18:42:57 duo kernel: ? intel_engine_wakeup+0x40/0x40
> > Nov 8 18:42:57 duo kernel: ? kthread_park+0x90/0x90
> > Nov 8 18:42:57 duo kernel: ret_from_fork+0x35/0x40
> > Nov 8 18:42:57 duo kernel: Modules linked in:
> > Nov 8 18:42:57 duo kernel: ---[ end trace 2f8da183a56f80f6 ]---
> > Nov 8 18:42:57 duo kernel: RIP:
> > 0010:__list_del_entry_valid+0x8e/0x90
> > Nov 8 18:42:57 duo kernel: Code: 66 88 d1 ff 0f 0b 48 89 fe 31 c0
> > 48 c7 c7 90 74 5e 85 e8 53 88 d1 ff 0f 0b 48 89 fe 31 c0 48 c7 c7 c8
> > 74 5e 85 e8 40 88 d1 ff <0f> 0b 55 48 89 d0 48 8b 52 08 48 89 e5 48
> > 39 f2 75 19 48 8b 32 48
> > Nov 8 18:42:57 duo kernel: RSP: 0000:ffffc9000196be78 EFLAGS:
> > 00210086
> > Nov 8 18:42:57 duo kernel: RAX: 0000000000000054 RBX:
> > ffff8801742b8178 RCX: 0000000000000000
> > Nov 8 18:42:57 duo kernel: RDX: 0000000000000000 RSI:
> > ffff88019e2a53d8 RDI: ffff88019e2a53d8
> > Nov 8 18:42:57 duo kernel: RBP: ffffc9000196be78 R08:
> > ffff880196e2cd10 R09: 0000000000000000
> > Nov 8 18:42:57 duo kernel: R10: 00000000e7684eb9 R11:
> > 3863656632393101 R12: ffffc9000196bec8
> > Nov 8 18:42:57 duo kernel: R13: ffff88019707e000 R14:
> > ffff8801742b8080 R15: ffffc9000192fdd0
> > Nov 8 18:42:57 duo kernel: FS: 0000000000000000(0000)
> > GS:ffff88019e280000(0000) knlGS:0000000000000000
> > Nov 8 18:42:57 duo kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> > 0000000080050033
> > Nov 8 18:42:57 duo kernel: CR2: 00000000ed2bf000 CR3:
> > 000000000581e001 CR4: 00000000000606a0
> >
> > --
> > (english) http://www.livejournal.com/~pavelmachek
> > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-11-21 11:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:58 v4.20-rc1: list_del corruption on thinkpad x220 Pavel Machek
2018-11-21 11:19 ` Joonas Lahtinen
2018-11-21 11:54 ` Pavel Machek [this message]
2018-11-23 8:17 ` Joonas Lahtinen
2018-11-24 15:23 ` Pavel Machek
2018-12-08 11:13 ` v4.20-rc1: list_del corruption on thinkpad x220, graphics related? Pavel Machek
2018-12-08 11:24 ` Pavel Machek
2018-12-09 11:18 ` v4.20-rc5+ on x220: Resetting chip for hang on rcs0 Pavel Machek
2018-12-10 8:30 ` Joonas Lahtinen
2018-12-10 8:28 ` v4.20-rc1: list_del corruption on thinkpad x220, graphics related? Joonas Lahtinen
2018-12-12 18:29 ` 4.20.0-rc6-next-20181210, " Pavel Machek
2018-12-13 8:29 ` Joonas Lahtinen
2018-12-27 8:34 ` [regression from v4.19] " Pavel Machek
2019-01-02 9:34 ` Joonas Lahtinen
2019-01-02 21:02 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181121115449.GA32455@amd \
--to=pavel@ucw.cz \
--cc=bp@alien8.de \
--cc=chris@chris-wilson.co.uk \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rodrigo.vivi@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).