-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
apologies in advance if this isn't the right mailing list, I saw earlier
messages regarding nvidia binary driver so this should be ok.
Anyway, I was having a lot of these messages (kernel BUG at
page_alloc.c) with the current version of nvidia dr
On 2002-07-22 at 15:16 +0200, Luca Olivetti uttered:
[snip]
| Anyway, I was having a lot of these messages (kernel BUG at
| page_alloc.c) with the current version of nvidia driver (1.0-2960) and
| afterwards the system is unpredictable (possible hard locks, file system
| corruption, anything).
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
krjw wrote:
| Ack. Makes you wish you could poke around in the source, eh?
Well, not really, I wouldn't understand much of it. Other more
knowledgeable people could, though.
| Anyway,
| does this only occur when you attempt to do 3D things? Or
On 2002-07-22 at 16:34 +0200, Luca Olivetti uttered:
|
| | The only real issue I've seen thus far is related to agpgart but this
| | probably has nothing to do with your problem.
|
| well, it could be, since the "nv" driver doesn't use agp
|
The issue I've seen is reproducable like so:
1) boot l
On Mon, Jul 22, 2002 at 03:16:40PM +0200, Luca Olivetti wrote:
>Anyway, I was having a lot of these messages (kernel BUG at
>page_alloc.c) with the current version of nvidia driver (1.0-2960) and
>afterwards the system is unpredictable (possible hard locks, file system
>corruption, anything).
>At
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
krjw wrote:
| The issue I've seen is reproducable like so:
| 1) boot linux box
| 2) enable use of kernel AGPGART (not internal nvidia AGPGART code) in
| XF86Config (load agpgart kernel module if needed)
| 3) Start X
| 4) Leave X
| 5) enable use of i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Stilson wrote:
| FWIW I had the same issues.
| The problem I had was that it would crash kswapd with the following
In my case it was either kdeinit, xmessage, kswapd, startkde,...
| kernel: kernel BUG at page_alloc.c:82!
| kernel: invalid oper
On Mon, Jul 22, 2002 at 11:25:35PM +0200, Luca Olivetti wrote:
>Mike Stilson wrote:
>
>| FWIW I had the same issues.
>| The problem I had was that it would crash kswapd with the following
>
>In my case it was either kdeinit, xmessage, kswapd, startkde,...
99% of the time it would crash kswapd, mo
On Mon, Jul 22, 2002 at 11:25:35PM +0200, Luca Olivetti wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Mike Stilson wrote:
>Are you sure the nvidia module was loaded at the time of this crash?
>It would taint the kernel if loaded:
>
>Jul 7 20:20:54 pippo kernel: kernel BUG at page_allo
On Tue, Jul 23, 2002 at 07:16:50AM -0400, Mike Stilson wrote:
> Just to follow up after giving a little more thought...
> The kernel module doesn't taint it since I'm recompiling it from source.
> the NVdriver.o module (although it doesn't specifically have a
> MODULE_LICENSE("GPL")) also doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Stilson wrote:
| Just to follow up after giving a little more thought...
| The kernel module doesn't taint it since I'm recompiling it from source.
No, you're just recompiling some glue code, the real module is binary only.
| the NVdriver.o m
On Tue, Jul 23, 2002 at 01:36:39PM +0200, Charl P. Botha wrote:
>On Tue, Jul 23, 2002 at 07:16:50AM -0400, Mike Stilson wrote:
>> Just to follow up after giving a little more thought...
>> The kernel module doesn't taint it since I'm recompiling it from source.
>> the NVdriver.o module (although i
On Fri, 26 Jul 2002, Luca Olivetti wrote:
> Mike Stilson wrote:
>
> | BTW: Since I stepped back to 2314 it's been nice and stable (Only 3 days
> | so far but better than the 10 hours I could manage with the latest
> | driver.)
>
> I'm using this release now and while it seems better, it's still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Stilson wrote:
| BTW: Since I stepped back to 2314 it's been nice and stable (Only 3 days
| so far but better than the 10 hours I could manage with the latest
| driver.)
I'm using this release now and while it seems better, it's still not
total
Mark Vojkovich wrote:
>Don't use AGPGART. Use NVGART instead. It's not clear that this
> is NVIDIA's bug, and even if it were, it would definitely be in the open
> source part of the driver.
Ok, I assumed that AGPGART was the preferred way since it's the default
configuration, I'll try wi
On Fri, Jul 26, 2002 at 11:18:13AM -0700, Mark Vojkovich wrote:
>On Fri, 26 Jul 2002, Luca Olivetti wrote:
>
>> Mike Stilson wrote:
>>
>> | BTW: Since I stepped back to 2314 it's been nice and stable (Only 3 days
>> | so far but better than the 10 hours I could manage with the latest
>> | driver.
16 matches
Mail list logo
