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 47FE61EB587 for ; Thu, 26 Aug 2010 12:03:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by chasm.ymmv.dk (Postfix) with ESMTP id C3FEA25840 for ; Thu, 26 Aug 2010 14:03:41 +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 q8vwt8QBT6Ub for ; Thu, 26 Aug 2010 14:03:37 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by chasm.ymmv.dk (Postfix) with ESMTP id C34FA2587C for ; Thu, 26 Aug 2010 14:03:37 +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 DC2FE25840 for ; Thu, 26 Aug 2010 14:03:36 +0200 (CEST) Date: Thu, 26 Aug 2010 14:03:30 +0200 From: Jon Clausen To: Alpine Devel Subject: [alpine-devel] Soekris 4801, alpine 2.0, kernel trouble Message-ID: <20100826120329.GA7723@nx8220.ymmv.dk> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Hi I'm in the process of setting up Alpine 2.0 as my main router/firewall. It's my first hike into "The Alps", so there's a lot to get used to, but overall I do like it :) Fortunately for me, I have two 4801's so I'm in a position to test stuff before I commit the system on the actual firewall hardware... which turns out to be very lucky indeed... The long story short: Booting the 2.6.32.18 kernel with the default parameters on the soekris results in a kernel panic. 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' 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 :) 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] - which I'm somewhat unhappy about, since those are two of the three onboard NICs :( (Incidentally the 2.6.32.15 kernel also has these collisions) The thing is that this system is going to be pretty 'complicated', with a bunch of vlans, and I'll be needing the NICs. I'm not too sure how to proceed from here? Do any of you have insights/experience about this kind of issue? >From what I've read so far, it may be related to: https://patchwork.kernel.org/patch/39988/ and symptoms range from 'more or less cosmetic, no real problems' to 'complete system lockup'. Obviously I'm not too thrilled by the prospect of the latter potentially happening to my firewall... :P I have a serial console on the box, so it's pretty esay for me to 'grab' the output. In fact I've saved the output from booting the various kernels (with various kernel parameters) but I've nowhere public to put them ATM. They're about 7K-9K each. If anyone's interested, let me know? tia /jon -- YMMV --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---