Re: KernelOops

2007-01-31 Thread Vitezslav Kotrla 
Wolfgang Mader píše v Út 30. 01. 2007 v 22:21 +0100:

> I have found these messages in /var/log/messages. I am using the nvidia 
> driver 
> for my GForce6600-GT card. Can someone please explain to me what is going on 
> on my system?
> Thank you -- W. Mader
> 
> -/var/log/messages---
> 
> Nov  5 21:27:17 FUCKUP kernel: Process Xorg (pid: 3404, threadinfo 
> 8100359ea000, task 810037bd3770)
> Nov  5 21:27:17 FUCKUP kernel: Stack:  8025e93f 80210aaa 
> 81003f38a868 8100192b9200

I can't explain what's going on, but I've just tried to grep FUCKUP
string in vanilla 2.6.18 tree and found nothing. Also grepping nvidia
source yields nothing. Could you please provide output of 'uname -a'?

Vit




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KernelOops

2007-01-31 Thread Lennart Sorensen 
On Wed, Jan 31, 2007 at 09:17:18PM +0100, Vitezslav Kotrla wrote:
> Wolfgang Mader pe v ??t 30. 01. 2007 v 22:21 +0100:
> 
> > I have found these messages in /var/log/messages. I am using the nvidia 
> > driver 
> > for my GForce6600-GT card. Can someone please explain to me what is going 
> > on 
> > on my system?
> > Thank you -- W. Mader
> > 
> > -/var/log/messages---
> > 
> > Nov  5 21:27:17 FUCKUP kernel: Process Xorg (pid: 3404, threadinfo 
> > 8100359ea000, task 810037bd3770)
> > Nov  5 21:27:17 FUCKUP kernel: Stack:  8025e93f 80210aaa 
> > 81003f38a868 8100192b9200
> 
> I can't explain what's going on, but I've just tried to grep FUCKUP
> string in vanilla 2.6.18 tree and found nothing. Also grepping nvidia
> source yields nothing. Could you please provide output of 'uname -a'?

That would be the 'hostname'.

--
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KernelOops

2007-01-31 Thread Vitezslav Kotrla 
[EMAIL PROTECTED] píše v St 31. 01. 2007 v 22:30 +0100:

> That would be the 'hostname'.

(Of course, I must have been too sleepy. At the first glance it looked
like some euphemism for 'error')

Vit


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KernelOops

2007-02-06 Thread Wolfgang Mader 
I found out, that on heavy system load, my power supply only delivers +11,4V. 
This seemes to be the lower limit to the specs. Could this course the 
problems "descripet" below?


> -/var/log/messages---
>
> Nov  5 21:27:17 FUCKUP kernel: Process Xorg (pid: 3404, threadinfo
> 8100359ea000, task 810037bd3770)
> Nov  5 21:27:17 FUCKUP kernel: Stack:  8025e93f 80210aaa
> 81003f38a868 8100192b9200
> Nov  5 21:27:17 FUCKUP kernel:  0001 802a9ac0
> 4000 0020
> Nov  5 21:27:17 FUCKUP kernel:   
> 0020 
> Nov  5 21:27:17 FUCKUP kernel: Call Trace:
> Nov  5 21:27:17 FUCKUP kernel:
> [] .text.lock.spinlock+0x7b/0x8a
> Nov  5 21:27:17 FUCKUP kernel:  []
> remove_mapping+0x1a/0x94 Nov  5 21:27:17 FUCKUP kernel: 
> []
> shrink_inactive_list+0x4ce/0x7e1
> Nov  5 21:27:17 FUCKUP kernel:  []
> __pagevec_release+0x19/0x22
> Nov  5 21:27:17 FUCKUP kernel:  []
> shrink_active_list+0x46f/0x47d
> Nov  5 21:27:17 FUCKUP kernel:  [] shrink_zone+0xd4/0xf7
> Nov  5 21:27:17 FUCKUP kernel:  []
> try_to_free_pages+0x16a/0x273
> Nov  5 21:27:17 FUCKUP kernel:  []
> __alloc_pages+0x1a8/0x2a9 Nov  5 21:27:17 FUCKUP kernel: 
> []
> __handle_mm_fault+0x1a3/0x91a
> Nov  5 21:27:17 FUCKUP kernel:  []
> do_page_fault+0x39d/0x706 Nov  5 21:27:17 FUCKUP kernel: 
> [] thread_return+0x0/0xe6 Nov  5 21:27:17 FUCKUP kernel: 
> [] do_brk+0x1be/0x272 Nov  5 21:27:17 FUCKUP kernel: 
> [] error_exit+0x0/0x84
>
> ---
>
>-- Jan 26 00:06:16 FUCKUP kernel:
> Jan 26 00:06:16 FUCKUP kernel: Call Trace:
> Jan 26 00:06:16 FUCKUP kernel:  [] clear_page+0x7/0x39
> Jan 26 00:06:16 FUCKUP kernel:  [] bad_page+0x4e/0x78
> Jan 26 00:06:16 FUCKUP kernel:  []
> get_page_from_freelist+0x26d/0x3a6
> Jan 26 00:06:16 FUCKUP kernel:  []
> __alloc_pages+0x5c/0x2a9 Jan 26 00:06:16 FUCKUP kernel: 
> []
> __handle_mm_fault+0x1a3/0x94f
> Jan 26 00:06:16 FUCKUP kernel:  [] vma_merge+0x147/0x1f4
> Jan 26 00:06:16 FUCKUP kernel:  []
> do_page_fault+0x39d/0x706 Jan 26 00:06:16 FUCKUP kernel: 
> [] do_mmap_pgoff+0x3d8/0x77f Jan 26 00:06:16 FUCKUP
> kernel:  [] do_mmap_pgoff+0x614/0x77f Jan 26 00:06:16
> FUCKUP kernel:  [] __up_write+0x21/0x10d Jan 26 00:06:16
> FUCKUP kernel:  [] error_exit+0x0/0x84 Jan 26 00:06:16
> FUCKUP kernel:
> Jan 26 00:11:32 FUCKUP kernel: --- [cut here ] - [please
> bite here ] -
>
> ---
>
>-- Jan 28 22:59:02 FUCKUP kernel: Pid: 11085, comm: kpdf Tainted: P
> 2.6.18-3-amd64 #1
> Jan 28 22:59:02 FUCKUP kernel: RIP: 0010:[]
> [] __fput+0x16/0x16e
> Jan 28 22:59:02 FUCKUP kernel: RSP: :81000ccef8b8  EFLAGS: 00010202
> Jan 28 22:59:02 FUCKUP kernel: RAX: 000d RBX: 810016d13138
> RCX: 
> Jan 28 22:59:02 FUCKUP kernel: RDX:  RSI: 810016d13298
> RDI: 81002f6c8cc0
> Jan 28 22:59:02 FUCKUP kernel: RBP: 81002f6c8cc0 R08: 81003e348ac0
> R09: 8100b400
> Jan 28 22:59:02 FUCKUP kernel: R10: 81000ccefa18 R11: 0010
> R12: 81003e348ac0
> Jan 28 22:59:02 FUCKUP kernel: R13: c8ff8100343c1f20 R14: 81003e79dcc0
> R15: 000d
> Jan 28 22:59:02 FUCKUP kernel: FS:  2ae642f3bc90()
> GS:8052 () knlGS:
> Jan 28 22:59:02 FUCKUP kernel: CS:  0010 DS:  ES:  CR0:
> 8005003b
> Jan 28 22:59:02 FUCKUP kernel: CR2: 00bf5258 CR3: 00201000
> CR4: 06e0
> Jan 28 22:59:02 FUCKUP kernel: Process kpdf (pid: 11085, threadinfo
> 81000ccee000, task 81000703b830)
> Jan 28 22:59:02 FUCKUP kernel: Stack:  810016d13138 8100225ab1e8
> 81003e348ac0 000b
> Jan 28 22:59:02 FUCKUP kernel:  8040184e 80218bfb
>  81000100a2a0
> Jan 28 22:59:02 FUCKUP kernel:  810016d13138 80237e19
> 16f5 81000100a2a0
> Jan 28 22:59:02 FUCKUP kernel: Call Trace:
> Jan 28 22:59:02 FUCKUP kernel:  [] remove_vma+0x35/0x5c
> Jan 28 22:59:02 FUCKUP kernel:  [] exit_mmap+0xcd/0xf1
> Jan 28 22:59:02 FUCKUP kernel:  [] mmput+0x28/0x98
> Jan 28 22:59:02 FUCKUP kernel:  [] do_exit+0x220/0x8ae
> Jan 28 22:59:02 FUCKUP kernel:  []
> do_unblank_screen+0xd/0x11a
> Jan 28 22:59:02 FUCKUP kernel:  []
> kernel_math_error+0x0/0x90
> Jan 28 22:59:02 FUCKUP kernel:  []
> do_general_protection+0xfe/0x107
> Jan 28 22:59:02 FUCKUP kernel:  [] error_exit+0x0/0x84
> Jan 28 22:59:02 FUCKUP kernel:  [] unix_poll+0x0/0xa4
> Jan 28 22:59:02 FUCKUP kernel:  [] do_select+0x256/0x439
> Jan 28 22:59:02 FUCKUP kernel:  [] do_select+0x241/0x439
> Jan 28 22:59:02 FUCKUP ker

Re: KernelOops

2007-02-07 Thread Anton Piatek 
On Tuesday 06 February 2007 23:12, Wolfgang Mader wrote:
> I found out, that on heavy system load, my power supply only delivers
> +11,4V. This seemes to be the lower limit to the specs. Could this course
> the problems "descripet" below?
>
> > -/var/log/messages---
> >
> > Nov  5 21:27:17 FUCKUP kernel: Process Xorg (pid: 3404, threadinfo
> > 8100359ea000, task 810037bd3770)
> > Nov  5 21:27:17 FUCKUP kernel: Stack:  8025e93f 80210aaa
> > 81003f38a868 8100192b9200
> > Nov  5 21:27:17 FUCKUP kernel:  0001 802a9ac0
> > 4000 0020
> > Nov  5 21:27:17 FUCKUP kernel:   


Not enough power can cause all sorts of problems. If you think your 
powersupply is underspecced for your hardware it is worth upgrading it. I 
would be surprised if anything >400W is causing problems though (unless they 
only happen when using the graphics card intensively).

Anton
-- 
Anton Piatek
email: [EMAIL PROTECTED] 
blog/photos:http://www.strangeparty.com
pgp: [0xB307BAEF]   (http://tastycake.net/~anton/anton.asc)
fingerprint: 116A 5F01 1E5F 1ADE 78C6 EDB3 B9B6 E622 B307 BAEF


pgpFET0GQ0lrs.pgp
Description: PGP signature

Re: KernelOops

2007-02-08 Thread Wolfgang Mader 
>
> Not enough power can cause all sorts of problems. If you think your
> powersupply is underspecced for your hardware it is worth upgrading it. I
> would be surprised if anything >400W is causing problems though (unless
> they only happen when using the graphics card intensively).

If I remeber right, my power supply has 350W. This IS REALLY low end! I know. 
But till now, all went good. :)


pgpMjCJS6zuWQ.pgp
Description: PGP signature