Hi Venkatesh,
It looks like your commit 0dc698b93f3eecdda43b22232131324eb41e510c
causes init to segfault on one of my computers.
Reverting 0dc698b9 on top of 2.6.35-rc2 solves the problem.
Let me know if you would like more details or if I can help with testing.
Tom
On Sun, Jun 6, 2010 at 6:00 PM, Tom Gundersen <[email protected]> wrote:
> Hi Venkatesh,
>
> It looks like your commit 0dc698b93f3eecdda43b22232131324eb41e510c
> causes init to segfault on one of my computers.
>
Hi Tom,
Hmm... Do you have the actual message you see on fault?
Does the problem happen at the boot time?
> Reverting 0dc698b9 on top of 2.6.35-rc2 solves the problem.
>
> Let me know if you would like more details or if I can help with testing.
If you can provide some addittional info above and 'dmesg' from no
error case (with this revert) and put them all in a bug at
bugzilla.kernel.org under ACPI, it will be great.
Thanks,
Venki
Hi Venki,
On Mon, Jun 7, 2010 at 5:33 AM, Venkatesh Pallipadi <[email protected]> wrote:
> Hmm... Do you have the actual message you see on fault?
> Does the problem happen at the boot time?
Yes, the problem happens at boot time (so don't have the message
readily available). I will write it down after work tonight and report
a bug as you suggested.
-t
On Mon, Jun 7, 2010 at 5:33 AM, Venkatesh Pallipadi <[email protected]> wrote:
> If you can provide some addittional info above and 'dmesg' from no
> error case (with this revert) and put them all in a bug at
> bugzilla.kernel.org under ACPI, it will be great.
Created report: <https://bugzilla.kernel.org/show_bug.cgi?id=16145>.
-t