Subject: Re: [alpine-devel] Soekris 4801, alpine 2.0, kernel trouble
From: Natanael Copa <ncopa@alpinelinux.org>
To: Jon Clausen <alpine@ymmv.dk>
Cc: alpine-devel@lists.alpinelinux.org
In-Reply-To: <20100826170848.GA5518@nx8220.ymmv.dk>
References: <20100826120329.GA7723@nx8220.ymmv.dk>
	 <AANLkTim_gytd4jh_B5DHPNdd=_6wy8Ddxeg=eQD_AcLr@mail.gmail.com>
	 <20100826170848.GA5518@nx8220.ymmv.dk>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 27 Aug 2010 11:38:00 +0200
Message-ID: <1282901880.27194.46.camel@ncopa-desktop.nor.wtbts.net>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

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:
> 
> > > It's my first hike into "The Alps", so there's a lot to get used to, but
> > > overall I do like it :)
> > 
> > nice!
> 
> :)
> 
> > > The long story short:
> > >
> > > Booting the 2.6.32.18 kernel with the default parameters on the soekris
> > > results in a kernel panic.
> > 
> > not good.
> 
> Agreed
> 
> > > After trying out the kernels of alpine 2 beta-* and rc-* I found that:
> > >
> > > 2.6.32.15 boots ok
> > > 2.6.32.16 upwards 'panic'
> > 
> > This is very useful information.
> 
> Good :)
> 
> > form the git log, the only thing that changed really was support for EFI.
> > 
> > http://git.alpinelinux.org/cgit/aports/log/main/linux-grsec?h=2.0-stable
> > 
> > > After searching the web I found a hint that 'noreplace-paravirt' had worked
> > > for someone else. So I tried adding that to the append line in syslinux.cfg
> > > - and lo and behold: Now the kernel boots :)
> > 
> > Thats interesting. I wonder how that could be?
> 
> Frankly, I have no idea - except I did notice a kernel message:
> 
> "Booting paravirtualized kernel on bare hardware"
> 
> But my first thought was that noreplace-paravirt would make matters worse.
> 
> > Could you try the vserver iso image too? It has a different kernel,
> > without the grsecurity patches. The syslinux.cfg is broken so you'd
> > need enter 'vserver' at the boot prompt where it complains about
> > missing grsec.
> 
> Will do. Probably not tonight, but yeah it makes sense to test that.
> 
> > > So far so good, except now I get:
> > >
> > > 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.

> > 
> > 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.

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.

> - 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.

> 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.

> /jon
-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---