Comment 50 for bug 63134

Revision history for this message
NoWhereMan (e.vacchi) (uncommonnonsense) wrote : Re: [Bug 63134] Re: Kernel panic - not syncing, when installing Edgy Beta1

> NoWhereMan, thank you for the reference to the bugzilla.kernel.org
> report. However, I'm a little concerned with some of the comments
> posted by the developer of the patch:
>
> "But in fact the above problems are related to BIOS. So it is more
> appropriate to fix this bug by updateing BIOS than the workaround
> patch."

unfortunately (I'm the e.vacchi of the bugreport) the released updates
for the bios does not work as expected; from other reports here on
launchpad IIRC it looks like they don't addres this issue at all

> "The above two patches in comment #127 and #128 can fix the problems for
> this bug. But they seem ugly and I am not willing to send the patches to
> kernel."
>
> Have you actually verified these patches resolve your issue? It is a
> lot of extra work for the Ubuntu kernel team to maintain out of tree
> patches. As such they require evidence of upstream submission before
> considering to maintain community patches locally.

I've tested one of the patches listed a few comments before the one
you're quoting; as I've answered, #127 and #128 are essentially a
pretty printed version of the one I've tried and an automated
acpi=force; I've tried to recompile 2.6.22 today (before I had only
tried 2.6.20) but looks like the new linux-source-2.6.22 on the
contrary of linux-source-2.6.20 lacks many of the drivers and it would
take for me a lot of time to figure out the whole procedure

> Since the developer
> of the patches commented he's unwilling to send the patches upstream,
> this might not qualify against the team's standard. Also is seems the
> patches are really just to bandaid a buggy BIOS, in which case I'm not
> sure they'd be accepted upstream nor maintained separately for Ubuntu.
> I'll defer to the kernel team for their comment. Thanks.

They *are* a bandaid for a buggy bios, but the whole point in this is
"if it works in Windows, why must have linux users to be penalized?";
the whole bug report is an interesting reading in this sense

> Something else you might want to try. . .

> The Hardy Heron kernel was recently uploaded for testing.

I don't think this would help; and btw I've tried 2.6.23 and it didn't
fix the issue; unfortunately this ugly patch seems the only way to
make it work; I would rather try to push the kernel devs so that this
hack can make it into upstream, so that
1) not only ubuntu but the whole community can benefit of the "bandaid"
2) ubuntu devs won't have to locally maintain the patch :)