From: Len Brown <lenb@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Len Brown <len.brown@intel.com>, Lin Ming <ming.m.lin@intel.com>,
Bob Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: acpi_ex_system_memory_space_handler oops
Date: Wed, 12 Aug 2009 20:18:37 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0908122009170.22946@localhost.localdomain> (raw)
In-Reply-To: <20090812201034.GA2983@localdomain.by>
> Kernel oopses on early boot stages (boots normally with boot_delay=10).
> rc5-git8
Please find which kernel this failure starts in.
Start by testing 2.6.30.stable so we can tell
if this is a regression in the current RC.
What is the difference between the two dmesg?
they have the same cmdline, neither has boot_delay,
and neither dmesg shows the oops.
The fact that boot_delay=10 makes the problem go away
suggests some sort of race condition. Is 10 the smallest
value of printk_time that works, or is it a random value?
Do you still see the oops with CONFIG_PRINTK_TIME=n?
Do you still see the oops with maxcpus=1?
Do you still see the oops with "acpi_serialize=1"?
Please open a bug report here:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
answer the questions above and attach the output from acpidump
thanks,
-Len Brown, Intel Open Source Technology Center.
next prev parent reply other threads:[~2009-08-13 0:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 20:10 acpi_ex_system_memory_space_handler oops Sergey Senozhatsky
2009-08-12 21:46 ` Rafael J. Wysocki
2009-08-13 0:18 ` Len Brown [this message]
2009-08-13 8:34 ` Sergey Senozhatsky
2009-08-13 9:53 ` Sergey Senozhatsky
2009-08-13 11:02 ` Sergey Senozhatsky
2009-08-13 12:46 ` Sergey Senozhatsky
2009-08-14 2:34 ` Lin Ming
2009-08-14 7:40 ` Sergey Senozhatsky
2009-08-14 7:53 ` Sergey Senozhatsky
2009-08-14 9:12 ` Sergey Senozhatsky
2009-08-14 9:38 ` Sergey Senozhatsky
2009-08-14 12:48 ` Sergey Senozhatsky
2009-08-13 13:43 ` Sergey Senozhatsky
2009-08-17 8:43 ` Lin Ming
2009-08-17 11:30 ` Sergey Senozhatsky
2009-08-17 13:22 ` Lin Ming
2009-08-18 7:13 ` Sergey Senozhatsky
2009-08-18 7:18 ` Lin Ming
2009-08-18 7:45 ` Sergey Senozhatsky
2009-08-18 8:00 ` Sergey Senozhatsky
2009-08-27 7:52 ` Sergey Senozhatsky
2009-08-27 7:59 ` Lin Ming
2009-08-27 8:29 ` Sergey Senozhatsky
2009-08-27 8:44 ` Lin Ming
2009-08-27 9:05 ` Sergey Senozhatsky
2009-08-31 21:12 ` Sergey Senozhatsky
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=alpine.LFD.2.00.0908122009170.22946@localhost.localdomain \
--to=lenb@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
--cc=sergey.senozhatsky@gmail.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