From: Danny ter Haar <dth@dth.net>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2/4] 2.6.23-rc4: known regressions
Date: Thu, 30 Aug 2007 10:21:38 +0200 [thread overview]
Message-ID: <20070830082138.GA32165@dth.net> (raw)
In-Reply-To: <46D59052.6040609@googlemail.com>
Quoting Michal Piotrowski (michal.k.k.piotrowski@gmail.com):
> Here is a list of some known regressions in 2.6.23-rc4.
> CPUFREQ
> Subject : ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
> References : http://lkml.org/lkml/2007/7/27/298
> http://lkml.org/lkml/2007/7/29/371
> Last known good : ?
> Submitter : dth <dth@dth.net>
> Caused-By : Len Brown <lenb@kernel.org>
> commit f79e3185dd0f8650022518d7624c876d8929061b
> Handled-By : Len Brown <lenb@kernel.org>
> Status : problem is being debugged
I just compiled 2.6.23-rc4 on this setup to check if we made any
progress. After reboot i see:
[SNIP]
NET: Registered protocol family 17
Using IPI Shortcut mode
Freeing unused kernel memory: 148 freed
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
input: AT Translated Set 2 keyboard as /devices/platform/i8042/
printk: 7888020 messages suppressed
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
[more of the last 2 lines repeated over and over]
Am i doing something wrong (very possible) or am i bitten by
another/new phenomena ?
Danny
--
next prev parent reply other threads:[~2007-08-30 8:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46D58CC6.4020605@googlemail.com>
2007-08-29 15:27 ` [2/4] 2.6.23-rc4: known regressions Michal Piotrowski
2007-08-29 15:42 ` Ivan N. Zlatev
2007-08-29 15:54 ` Takashi Iwai
2007-08-29 22:34 ` Bill Davidsen
2007-09-02 12:19 ` Jesper Juhl
2007-09-04 8:30 ` Takashi Iwai
2007-09-03 20:23 ` Thomas Meyer
2007-09-04 8:36 ` Takashi Iwai
2007-08-30 8:21 ` Danny ter Haar [this message]
2007-08-31 22:01 ` Len Brown
2007-10-12 11:10 ` Danny ter Haar
2007-08-29 15:27 ` [3/4] " Michal Piotrowski
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 21:54 ` [NFS] " J. Bruce Fields
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 15:27 ` [4/4] " Michal Piotrowski
2007-08-29 15:27 ` Michal Piotrowski
2007-08-30 10:42 ` Soeren Sonnenburg
2007-08-30 10:42 ` Soeren Sonnenburg
2007-09-02 22:33 ` Michal Piotrowski
2007-09-02 22:33 ` Michal Piotrowski
2007-09-03 6:12 ` Arkadiusz Miskiewicz
2007-09-03 6:12 ` Arkadiusz Miskiewicz
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=20070830082138.GA32165@dth.net \
--to=dth@dth.net \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.