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, graphics related?
Date: Sat, 8 Dec 2018 12:24:47 +0100 [thread overview]
Message-ID: <20181208112447.GA9663@amd> (raw)
In-Reply-To: <20181208111346.GA5535@amd>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
On Sat 2018-12-08 12:13:46, Pavel Machek wrote:
> Hi!
>
> > > > > 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.
> > >
> > > By adding it to the Bugzilla it may be recognized by somebody else
> > > who is experiencing a similar issue. Internet points are not deducted
> > > for submitting bugs in good faith, even if they get closed as
> > > NOTABUG.
>
> Well, your documentation suggests you'll deduce my internet points:
>
> Before filing the bug, please try to reproduce your issue with the
> latest kernel. Use the latest drm-tip branch from
> http://cgit.freedesktop.org/drm-tip and build as instructed on our
> Build Guide.
>
> :-)
I'd prefer not to run drm-tip. I'll update to 2.6.20-rc5+ and see if
it re-appears (but it takes long time to reproduce :-().
If you think it is useful, I can try to update my machine to
linux-next.
Best regards,
Pavel
--
(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-12-08 11:24 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
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 [this message]
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=20181208112447.GA9663@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