From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: linux-kernel@vger.kernel.org
Subject: bugreport kernel panic on early stage, with HIGHMEM4G:
Date: Mon, 7 Jan 2008 07:47:18 +0200 [thread overview]
Message-ID: <20080107053908.M5584@visp.net.lb> (raw)
Hi
After physical memory upgrade from 3GB to 4GB (also it happens on 5GB) got
kernel panic.
Because it is happening on early stage and my machine doesn't contain serial
port, i had to take photo.
Kernel boots fine with 64GB highmem, no highmem, or highmem4G with limited
memory by mem=3G. All dmesg attached.
Also i attach dmidecode and lspci -vvv output, probably it will be useful.
Photo (2.8MB, sorry, just original size from camera):
http://www.nuclearcat.com/files/panic-07012008/img_1232.jpg
dmesg without highmem
http://www.nuclearcat.com/files/panic-07012008/dmesg-nohighmem.txt
with highmem64G
http://www.nuclearcat.com/files/panic-07012008/dmesg-highmem64G.txt
with highmem4G limited by mem=3G
http://www.nuclearcat.com/files/panic-07012008/dmesg-highmem4G-memlim3G.txt
Kernel config for this specific boot:
http://www.nuclearcat.com/files/panic-07012008/config.txt
dmidecode output
http://www.nuclearcat.com/files/panic-07012008/dmidecode.txt
lspci output
http://www.nuclearcat.com/files/panic-07012008/lspci.txt
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next reply other threads:[~2008-01-07 5:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 5:47 Denys Fedoryshchenko [this message]
2008-01-15 11:39 ` bugreport kernel panic on early stage, with HIGHMEM4G: Ingo Molnar
2008-01-15 13:13 ` Ingo Molnar
2008-01-17 12:26 ` Mel Gorman
2008-01-17 13:31 ` Denys Fedoryshchenko
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=20080107053908.M5584@visp.net.lb \
--to=denys@visp.net.lb \
--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