X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@lists.alpinelinux.org
Received: from chasm.ymmv.dk (unknown [193.106.164.142])
	by lists.alpinelinux.org (Postfix) with ESMTP id 1243C1EB587
	for <alpine-devel@lists.alpinelinux.org>; Fri, 27 Aug 2010 11:02:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by chasm.ymmv.dk (Postfix) with ESMTP id 6FB4F269F1
	for <alpine-devel@lists.alpinelinux.org>; Fri, 27 Aug 2010 13:02:43 +0200 (CEST)
X-Virus-Scanned: by amavisd-new at ymmv.dk
Received: from chasm.ymmv.dk ([127.0.0.1])
	by localhost (chasm.ymmv.dk [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RehjMee+B8Ww for <alpine-devel@lists.alpinelinux.org>;
	Fri, 27 Aug 2010 13:02:39 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by chasm.ymmv.dk (Postfix) with ESMTP id 1A54126B59
	for <alpine-devel@lists.alpinelinux.org>; Fri, 27 Aug 2010 13:02:39 +0200 (CEST)
Received: from nx8220.ymmv.dk (unknown [10.9.8.112])
	(Authenticated sender: jon@ymmv.dk)
	by chasm.ymmv.dk (Postfix) with ESMTPSA id 1C032269F1
	for <alpine-devel@lists.alpinelinux.org>; Fri, 27 Aug 2010 13:02:38 +0200 (CEST)
Date: Fri, 27 Aug 2010 13:02:36 +0200
From: Jon Clausen <alpine@ymmv.dk>
To: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Soekris 4801, alpine 2.0, kernel trouble
Message-ID: <20100827110236.GB2463@nx8220.ymmv.dk>
References: <20100826120329.GA7723@nx8220.ymmv.dk>
 <AANLkTim_gytd4jh_B5DHPNdd=_6wy8Ddxeg=eQD_AcLr@mail.gmail.com>
 <20100826170848.GA5518@nx8220.ymmv.dk>
 <1282901880.27194.46.camel@ncopa-desktop.nor.wtbts.net>
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1282901880.27194.46.camel@ncopa-desktop.nor.wtbts.net>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Fri, 27 Aug, 2010 at 11:38:00 +0200, Natanael Copa wrote:
> On Thu, 2010-08-26 at 19:08 +0200, Jon Clausen wrote:
> > On Thu, 26 Aug, 2010 at 17:08:08 +0200, Natanael Copa wrote:
> > > On Thu, Aug 26, 2010 at 2:03 PM, Jon Clausen <alpine@ymmv.dk> wrote:

> > > > pci 0000:00:07.0: BAR 6: address space collision on of device
> > > > [0x3f000000-0x3f00ffff]
> > > > pci 0000:00:08.0: BAR 6: address space collision on of device
> > > > [0x3f000000-0x3f00ffff]
> 
> This is a different issue. I'd prefer keep this separated. Lets fix the
> kernel panic first.

OK.

> > > The ones that panic would be interesting to see. Not sure how much i
> > > can help there though.
> > 
> > OK, I'll tar 'em up and send them in a PM.
> 
> got them. I talked with pipacs on #grsecurity on OFTC on irc. He is the
> author of the PAX patches. This will be difficult to debug since its not
> reproduceable on qemu and he nor me has this hardware.

Right. I'm happy to help anyone help me ;)

Before we go further with the grsec trail, however, I was thinking something
else might help narrow down the issue:

Looking at the config-<kernel-version> files that come with the *.iso'es, I
noticed a number of *VIRT* options are set.
Now, I'm not too familiar with those, but I was thinking it might be worth a
shot with a kernel:

* with grsec patches
* without the "virtualization" options

The reasoning being, that 'noreplace-paravirt' might conceivably change the
behaviour of parts of the kernel affected by options such as:

CONFIG_PARAVIRT_GUEST=y
CONFIG_PARAVIRT=y

Should be interesting to see what happens with a 'bare metal' kernel with
the grsec patches.

I don't have the build environment, though, so... is it possible for you to
build a 'non paravirtualized' kernel for me to test?

> Basicly, we will need to help him to help us fix it. Would be nice if
> you had a chance to join on irc. so we both could talk directly with
> pipacs on how to do this.

Yeah... That's unlikely this side of the weekend... I've got a pretty tight
schedule... :P

> > - speaking of which;
> > 
> > What's the 'listiquette'?
> > 
> > Attachment size limits, etc?
> 
> I dint we have any written rules for that really. I'd think attachment
> size up to atleast 1MB is ok or til someone complains.

Right.

> > I see in the archives that people generally respond to both the poster and
> > the list. Is that the norm? (This message is going to the list only)
> 
> I normally just hit reply-all. Just in case sender has not joined the
> list.

Hmm... I'm gonna have to play around with sieve, and see if I can get it
to match the list and PM 'duplicates' reliably, then...

Oh well, that's another issue entirely.

regards
/jon
-- 
YMMV


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---