From: Niklas Schnelle <niklas@komani.de>
To: linux-kernel@vger.kernel.org
Subject: 3.2-rc1 doesn't boot on dual socket opteron without swap
Date: Thu, 10 Nov 2011 21:09:29 +0100 [thread overview]
Message-ID: <1320955769.1718.8.camel@jupiter> (raw)
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Hi Kernel Hackers,
still can't find the Kernel Bugzilla after the kernel.org troubles and
G+ would have felt weired so here comes my bug report.
I'm trying to run Linux 3.2-rc1 on an Arch Linux Box with the following
specs:
- Tyan S8320G Motherboard with Dual Socket Magny Cours Opterons 6128
- 16 GB RAM.
I'm getting the following error (sorry for bad picture quality, I can
retry if requested)
http://niklas.sceneproject.org/coding/kernel-3.2-rc1-bug.jpg
The exact same build (from a linux-mainline repository for Arch Linux)
runs well on a friends laptop.
One thing that could play a role is that due to enough RAM I'm running
without swap. It's just so much easier if rampant processes get shot
down by the OOM killer before things get swapping and slow.
Greetings Niklas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2011-11-10 20:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1320955769.1718.8.camel@jupiter \
--to=niklas@komani.de \
--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