public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Farthing <rfarthing@iee.org>
To: Jiri Slaby <jslaby@suse.cz>, Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel boot panic 3.12-34 > 3.12.35
Date: Fri, 02 Jan 2015 10:46:04 +0000	[thread overview]
Message-ID: <54A676EC.1050808@iee.org> (raw)
In-Reply-To: <548EC64D.6000104@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

Hi,

So I built 3.12.35 from the SLE12 repo and another crash on boot !  See 
attached screenshot.
Something weird going on with btrfs here (it's built with the same 
options as 3.12.34).  All the other longterm kernels I've tested have 
been OK (stock kernel, 3.2.65, 3.4.105, 3.10.63 and 3.12.34 of course.

regards
Richard

On 15/12/2014 11:30, Jiri Slaby wrote:
> On 12/15/2014, 11:06 AM, Richard Farthing wrote:
>> I installed the kernel via YAST2 which makes and installs the initrd
>> too, and have done this many times before on this test machine, so it
>> seems unlikely to be my mistake, but it's always possible!  I will have
>> a look at it again
> Oh, yast... What about trying RPMs from
> http://download.opensuse.org/repositories/Kernel:/SLE12/standard/
> ?
>
> Either kernel-vanilla which is pure 3.12.35 (or later) or kernel-default
> which is SLE12 kernel based on 3.12.35 (or later).
>
> thanks,


[-- Attachment #2: IMG_2685 (Medium).JPG --]
[-- Type: image/jpeg, Size: 268602 bytes --]

      reply	other threads:[~2015-01-02 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 15:41 Kernel boot panic 3.12-34 > 3.12.35 Richard Farthing
2014-12-14 18:25 ` Borislav Petkov
2014-12-15  9:28   ` Jiri Slaby
2014-12-15 10:06     ` Richard Farthing
2014-12-15 11:30       ` Jiri Slaby
2015-01-02 10:46         ` Richard Farthing [this message]

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=54A676EC.1050808@iee.org \
    --to=rfarthing@iee.org \
    --cc=bp@alien8.de \
    --cc=jslaby@suse.cz \
    --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