From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: werner@guyane.dyn-o-saur.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: 2.6.33 problems
Date: Wed, 03 Mar 2010 09:56:45 +0900 [thread overview]
Message-ID: <4B8DB3CD.6050204@kernel.org> (raw)
In-Reply-To: <20100302135032.e3d11bbf.akpm@linux-foundation.org>
Hello,
On 03/03/2010 06:50 AM, Andrew Morton wrote:
> On Sat, 27 Feb 2010 14:09:11 -0300 (GFT)
> werner@guyane.dyn-o-saur.com wrote:
>
>> For better error searching / correction, I add below the whole syslog.
>>
>> This is refered to 2.6.33 published (without patchs)
>>
>> This are different errors.
>>
>> The most of them exists since 2.6.33-rc1 or appr. -rc5.
>>
>> I posted here already the whole syslog.bz2 but nobody toke care.
>>
>> the boot_vga error occurs only after I start the grafics mode. It's the mainboard's embedded nvidia grafics. I use the vesa framebuffer driver of X 1.8
>>
>> the int6_init error occurs also in text mode. I think it have something to do with internet.
>>
>> Also the printk errors occur only when start the computer in the grafics mode, but not when starting it in the text mode.
>>
>> Below is also the kernel config. Its the same like since -rc7 (but the errors are also the same)
Hmmmm... it seems like the percpu allocator failed to allocate space
for a new chunk in the vmalloc area. Looking through the config.
Hmmm, w/ 3G split, there should be enough vmalloc area. Strange.
Does kernel parameter "percpu_alloc=page" make the machine boot? If
so, can you please post the output of dmesg right after boot?
Thanks.
--
tejun
prev parent reply other threads:[~2010-03-03 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1267290551.13148@guyane.dyn-o-saur.com>
2010-03-02 21:50 ` 2.6.33 problems Andrew Morton
2010-03-02 22:42 ` Stephen Hemminger
2010-03-02 23:30 ` Eric Dumazet
2010-03-03 0:56 ` Tejun Heo [this message]
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=4B8DB3CD.6050204@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=werner@guyane.dyn-o-saur.com \
/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;
as well as URLs for NNTP newsgroup(s).