Re: PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131

["Alexandre P. Nunes" <alex@PolesApart.wox.org>]

David S. Miller wrote:

>   From: "Alexandre P. Nunes" <alex@PolesApart.wox.org>
>   Date: Mon, 24 Jun 2002 12:06:32 -0300
>   
>   Maybe I got it the wrong way, but it seems to me that from your point of 
>   view, as long as proprietary driver is in use, it's not anyone else 
>   problem but to the vendor, even if the bug could happen to be in the 
>   kernel, is that right? If so, everyone else in this list who could try 
>   to fix this (again assuming it could be something related to the kernel 
>   and not to the proprietary driver) necessarily share your oppinion? (I'm 
>   not flaming in here, just trying to get the path).
>
>This has to do with facts, not opinions.  Since we lack the source to
>their drivers, we have no idea if some bug in their driver is
>scribbling over (ie. corrupting) memory.  It is therefore an unknown
>which makes it a waste of time for us to pursue the bug report.
>  
>
Thanks, now with your report (and in fact Zwane's one, which cleared the 
fact this bug scenario have been seen before) it's all clear to me. I 
don't subscribe to nor used to read this list archives, so I couldn't 
take a better picture and guess without actually someone pointing this out.

I'll direct the pressure all over nvidia, and in mean time I'll read the 
relevant articles in the archives, which seems the way to avoid  
unnecessary redundancy ...

Sorry folks if I bothered too much, I'll try avoid that :-)

Thanks for all of you,

Alexandre