All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timo Teräs" <timo.teras@iki.fi>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: powerpc boot failure
Date: Thu, 08 Apr 2010 10:48:01 +0300	[thread overview]
Message-ID: <4BBD8A31.2080007@iki.fi> (raw)
In-Reply-To: <20100408174549.2f45ceea.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi,
> 
> On Thu, 08 Apr 2010 10:29:49 +0300 Timo Teräs <timo.teras@iki.fi> wrote:
>> You don't probably have any xfrm policies then. And that code should not
>> really get executed.
>>
>> Some of the changes touch globally visible structs, and inline functions.
>> Was this a clean rebuild? And did you update all kernel modules, also in
>> the initramfs?
> 
> Yes, the build is started from scratch and the kernel and modules are
> updated (this is our automated build and test system).
> 
> I have attached the config in case that is of use.

Thanks, I'll check some of the xfrm related configs.

Can you on running system do:
 ip xfrm policy

That shows if there's any policies due to e.g. ipsec or tcp-md5.

  reply	other threads:[~2010-04-08  7:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  6:58 linux-next: powerpc boot failure Stephen Rothwell
2010-04-08  6:58 ` Stephen Rothwell
2010-04-08  7:11 ` Timo Teräs
2010-04-08  7:23   ` Stephen Rothwell
2010-04-08  7:29     ` Timo Teräs
2010-04-08  7:45       ` Stephen Rothwell
2010-04-08  7:48         ` Timo Teräs [this message]
2010-04-08  8:40         ` Timo Teräs
2010-04-08 18:55           ` Tony Luck
2010-04-08 20:13             ` David Miller
2010-04-08 20:13               ` David Miller
2010-04-09  0:08           ` Stephen Rothwell

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=4BBD8A31.2080007@iki.fi \
    --to=timo.teras@iki.fi \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.