M-am uitat putin pe surse si in fs/ext3/file.c la linia 66 de care se plange in log
arata asa:
struct inode *inode = file->f_dentry->d_inode;
Asta inseamna ca unul din pointeri este nul si nu exista nici o verificare pentru
asta. Iti sugerez sa incerci o verificare a lui file, apoi f_dentry si daca e 0 iesi
din functie cu un cod oarecare de eroare!
Sper ca asta sa-ti rezolve problema!
Succes!
Dragos
problema se complica :). cred ca provine dintr-o problema cu kernel-ul (am
2.4.21).
procesul e in "uninterruptable sleep":
golem3u 2995 0.0 2.9 52300 7376 ? D 12:42 0:00
/usr/local/bin/dcgui-qt
din cate am citit pe net, un asemenea proces NU poate fi omorat:
>>The process is in "Uninterruptable Sleep" ('D') status. This primarily
occurs when a process has asked the OS to perform I/O for it, and the
system is stuck on the I/O with (typically) a hardware related problem.
You can kill this sort of process all you want, but since the system won't
schedule it until the I/O completes, the kill signals will never be
delivered to it. The cure for this is to repair the underlying problem
causing the "Uninterruptable Sleep" condition, and the process will then
recover.<<
m-am uitat in syslog si am descoperit la ora 06:55 (ora la care probabil a
inghetat dcgui-ul) urmatoarea chestie:
Dec 25 06:55:03 golem3u kernel: kernel BUG at file.c:66!
Dec 25 06:55:03 golem3u kernel: invalid operand: 0000
Dec 25 06:55:03 golem3u kernel: CPU: 0
Dec 25 06:55:03 golem3u kernel: EIP: 0010:[<c01bf902>] Tainted: P
Dec 25 06:55:03 golem3u kernel: EFLAGS: 00010287
Dec 25 06:55:03 golem3u kernel: eax: 001f3e00 ebx: 00000f9f ecx:
00000009 edx: 00000000
Dec 25 06:55:03 golem3u kernel: esi: c9286040 edi: 001f4000 ebp:
ccd5fe40 esp: c9c63e54
Dec 25 06:55:03 golem3u kernel: ds: 0018 es: 0018 ss: 0018
Dec 25 06:55:03 golem3u kernel: Process dcgui-qt (pid: 2370,
stackpage=c9c63000)
Dec 25 06:55:03 golem3u kernel: Stack: c9286040 00000f9f c013d4b5 cfe75a00
00001000 00000e00 000001f3 00
000f9f
Dec 25 06:55:03 golem3u kernel: c013d8e3 c9286040 00000f9f ccd5fe40
00000001 c3046640 c3907000 c9
c63ea0
Dec 25 06:55:03 golem3u kernel: 00000200 c92860e4 ccd5fe40 c012d540
00000000 c109cd50 00000ebc 00
0001f3
Dec 25 06:55:03 golem3u kernel: Call Trace: [<c013d4b5>] [<c013d8e3>]
[<c012d540>] [<c013e074>] [<c01
bf880>]
Dec 25 06:55:03 golem3u kernel: [<c01c1466>] [<c01bf880>] [<c012fab6>]
[<c01bf9f5>] [<c01bf9b7>] [<c01
3afd3>]
Dec 25 06:55:03 golem3u kernel: [<c0108e7f>]
Dec 25 06:55:03 golem3u kernel:
Dec 25 06:55:03 golem3u kernel: Code: 0f 0b 42 00 68 95 44 c0 ba fb ff ff
ff eb bb 8b 86 90 00 00
are cineva idee ce va sa zica "golem3u kernel: kernel BUG at file.c:66!"??
banuiesc ca asta a cauzat inghetarea dcgui-ului, pentru ca am mai dat
peste faza asta si in alt syslog mai vechi, in exact acelasi context (in
aceeasi secunda apare chestia cu kernel bug tralala, dupa care apare o
linie cu dcgui stackpage tralalala).
any ideas people? ce se intampla? ce pot sa fac ca sa nu se mai intample?
--
Linux registered user #327471.
---
Detalii despre listele noastre de mail: http://www.lug.ro/
---
Detalii despre listele noastre de mail: http://www.lug.ro/
