From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [Ops] 2.6.18
Date: Sun, 1 Oct 2006 19:11:46 +0300 [thread overview]
Message-ID: <200610011911.47131.caglar@pardus.org.tr> (raw)
In-Reply-To: <20061001103442.GA94076@muc.de>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
01 Eki 2006 Paz 13:34 tarihinde, Andi Kleen şunları yazmıştı:
> On Sun, Oct 01, 2006 at 03:32:49AM +0300, S.??a??lar Onur wrote:
> The first thing when you get lots of weird oopses is to save your .config,
> do a make distclean and try again. Sometimes kernels get miscompiled.
I'm sure this is not miscompiled cause currently its used by lots of Pardus
alpha testers but none of them except some of them have problems. That nasty
lockup occurs on one of our buildfarm machines and this opps in vmware test
installations.
> Also your oopses do not fit completely on the screen. Best you enable
> CONFIG_VIDEO_SELECT and boot with vga=0x0f07
> (if that doesn't work vga=ask and select the smallest resolution)
I'll enable and report back.
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-01 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 0:32 [Ops] 2.6.18 S.Çağlar Onur
2006-10-01 10:34 ` Andi Kleen
2006-10-01 16:11 ` S.Çağlar Onur [this message]
2006-10-02 17:36 ` john stultz
2006-10-04 13:38 ` S.Çağlar Onur
2006-10-04 14:47 ` Andi Kleen
2006-10-04 16:08 ` S.Çağlar Onur
2006-10-04 17:56 ` Andi Kleen
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=200610011911.47131.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ak@muc.de \
--cc=johnstul@us.ibm.com \
--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