public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Steinhuber <sebastian.steinhuber@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Panic with latest git kernel
Date: Sun, 26 Jan 2014 21:42:27 +0100	[thread overview]
Message-ID: <lc3rv7$nkf$1@ger.gmane.org> (raw)
In-Reply-To: <52E568C2.5050001@gmail.com>

Am 26.01.2014 20:57, schrieb Harald Arnesen:
> Seems you are right. I just tried to compile a 3.13.0 kernel again
> (which I did when i was released, and it worked then), and I got the
> same panic.
>
> Must be a Debian bug. I will pester them instead.

I had to downgrade busybox-static to 1.21.0-1 (testing)



      reply	other threads:[~2014-01-26 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 12:50 Panic with latest git kernel Harald Arnesen
2014-01-26 13:01 ` Madper Xie
2014-01-26 13:03 ` Richard Weinberger
     [not found]   ` <52E50ED7.9070808@gmail.com>
2014-01-26 13:36     ` Richard Weinberger
2014-01-26 13:41       ` Harald Arnesen
2014-01-26 14:47       ` Harald Arnesen
2014-01-26 15:00         ` Richard Weinberger
2014-01-26 19:57           ` Harald Arnesen
2014-01-26 20:42             ` Sebastian Steinhuber [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='lc3rv7$nkf$1@ger.gmane.org' \
    --to=sebastian.steinhuber@googlemail.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