public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Jacob Shin <jacob.shin@amd.com>,
	Andreas Herrmann <herrmann.der.user@googlemail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Issues with AMD microcode updates
Date: Thu, 19 Sep 2013 20:46:56 +0200	[thread overview]
Message-ID: <20130919184656.GF9412@pd.tnic> (raw)
In-Reply-To: <20130919181554.GA10055@khazad-dum.debian.net>

On Thu, Sep 19, 2013 at 03:15:54PM -0300, Henrique de Moraes Holschuh wrote:
> I can request help on debian-user or debian-devel to get someone with
> an AMD box to help with bissection, but it is usually best if we don't
> ask general users to bissect kernels (due to non-zero risk of data
> corruption if the bissect hit one of the problem spots that often show
> up during the development window).

I have a couple of AMD boxes so I can bisect - I just need a reproducer
how to trigger.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-09-19 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 14:58 Issues with AMD microcode updates Henrique de Moraes Holschuh
2013-09-19 16:44 ` Borislav Petkov
2013-09-19 18:15   ` Henrique de Moraes Holschuh
2013-09-19 18:46     ` Borislav Petkov [this message]
2013-09-19 19:26       ` Henrique de Moraes Holschuh
2013-09-24 23:35   ` Sherry Hurwitz
2013-09-25 13:49     ` Henrique de Moraes Holschuh
2013-09-26 17:36       ` Sherry Hurwitz
2013-09-27 19:36         ` Henrique de Moraes Holschuh

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=20130919184656.GF9412@pd.tnic \
    --to=bp@alien8.de \
    --cc=herrmann.der.user@googlemail.com \
    --cc=hmh@hmh.eng.br \
    --cc=jacob.shin@amd.com \
    --cc=linux-kernel@vger.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