On Iau, 2005-09-01 at 09:24 +0200, Ingo Molnar wrote:
> is this the right way to fix the UP assumption below?
Probably not. The ide_lock may already be held (randomly depending on
the code path) at the point we retune a drive on error. Actually you
probably crash before this anyway.
The ALi code
Ingo Molnar wrote:
Rui Nuno Capela wrote:
OK. The reported boot WARNING seems to be over now. Tested on the
offended laptop ([EMAIL PROTECTED]/UP, PCI chipset: ALi M1533) with
2.6.13-rt3, where the suggested patch on drivers/ide/pci/alim15x3.c
seems to fix the burp. All seems to be working fin
* Rui Nuno Capela <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> >is this the right way to fix the UP assumption below?
> >
> > Ingo
> >
> >Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
> >
> >Index: linux/drivers/ide/pci/alim15x3.c
> > [snip]
>
> OK. The reported boot WARNING seems to b
Ingo Molnar wrote:
is this the right way to fix the UP assumption below?
Ingo
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Index: linux/drivers/ide/pci/alim15x3.c
> [snip]
OK. The reported boot WARNING seems to be over now. Tested on the
offended laptop ([EMAIL PROTECTED]/UP, PCI
is this the right way to fix the UP assumption below?
Ingo
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Index: linux/drivers/ide/pci/alim15x3.c
===
--- linux.orig/drivers/ide/pci/alim15x3.c
+++ linux/drivers/ide/pci/alim1
5 matches
Mail list logo