Re: Bugreport kernel 2.4.0-test8
On 2000-09-19 8:33:49 Michael Zieger wrote: >I just found a big bug in kernel 2.4.0-test8 that leads to a major >crash because PID 4 [kupdate] dies. >I could reproduce the problem by doing this: >- Open StarOffice under KDE >- Create new textfile >- Try to save it under a via NFS mounted directory I experienced this same problem with 2.4.0-test9-pre4. The NFS server was a stock Red Hat 6.0 box running 2.2.5. My workstation is running Linux-Mandrake 7.2 beta 2 with 2.4.0.9.4 patched for ReiserFS 3.6.16, with all partitions formatted with ReiserFS 3.5.24. When I tried to save a StarOffice 5.2 file in .doc format to the NFS server, the workstation hung and did not respond for 10 minutes. I could not telnet to it, but it did respond to pings. I had to hit the big switch. Afterwards, the only lines in /var/log/messages (at the time of the problem) were: Sep 19 13:11:27 spc kernel: NFS: NFSv3 not supported. Sep 19 13:11:27 spc kernel: nfs warning: mount version older than kernel I experienced some file corruption. StarOffice would not run after reboot, complaining about missing configuration files. I hope this helps, Steven - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Bugreport kernel 2.4.0-test8
I just found a big bug in kernel 2.4.0-test8 that leads to a major crash because PID 4 [kupdate] dies. I could reproduce the problem by doing this: - Open StarOffice under KDE - Create new textfile - Try to save it under a via NFS mounted directory Here are the two kernel oopses that occured on both tests: - kernel BUG at ll_rw_blk.c:711! invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010286 eax: 001f ebx: cb4e5cc0 ecx: 001f edx: 0002 esi: cb4e5cc0 edi: cff3f298 ebp: 0001 esp: cff4bf34 ds: 0018 es: 0018 ss: 0018 Process kupdate (pid: 4, stackpage=cff4b000) Stack: c02876a5 c0287982 02c7 cb4e5cc0 0001 0020 001e8480 cff3f2b0 cff3f2a8 0008 c0187fef 00fe c0188c2d cff3f298 0001 cb4e5cc0 cb4e5cc0 0001 cff4bfd0 Call Trace: [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 0f b6 46 15 0f b7 4e 14 8b 14 85 a0 de 35 c0 - kernel BUG at ll_rw_blk.c:711! invalid operand: CPU:1 EIP:0010:[] EFLAGS: 00010286 eax: 001f ebx: cf1152c0 ecx: 0097 edx: 0100 esi: cf1152c0 edi: cff3f298 ebp: 0001 esp: cff4bf34 ds: 0018 es: 0018 ss: 0018 Process kupdate (pid: 4, stackpage=cff4b000) Stack: c02876a5 c0287982 02c7 cf1152c0 0001 0020 001e8480 cff3f2b0 cff3f2a8 0008 c0187fef 00fe c0188c2d cff3f298 0001 cf1152c0 cf1152c0 0001 cff4bfd0 Call Trace: [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 0f b6 46 15 0f b7 4e 14 8b 14 85 a0 de 35 c0 - After this, you StarOffice dies and can't even be killed via kill -9. On shutdown, the system hangs. After reboot, the /tmp filesystem was corrupted requiring manual fsck, which moves a file to lost+found (a temporary file from StarOffice). My system is otherwise rock solid, I switched back to kernel 2.4.0-test5 which is OK for me. I hope this helps, and please don't hurt me if this bug has already been reportet, but I don't read this list 'cause I'm not a developer. If you need to know more, feel free to contact me. greets, and go on with The Good Work mike -- // Ing. Michael Zieger, BSc. ---Zieger Michael EDV-Lösungen // http://www.zmi.at Linux 2.2.15 SMP // // May those who love us, love us. // And for those who don't love us, may the good Lord turn their hearts. // And if He can't turn their hearts, may He turn their ankles // So we'll know them by their limping. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Bugreport kernel 2.4.0-test8
I just found a big bug in kernel 2.4.0-test8 that leads to a major crash because PID 4 [kupdate] dies. I could reproduce the problem by doing this: - Open StarOffice under KDE - Create new textfile - Try to save it under a via NFS mounted directory Here are the two kernel oopses that occured on both tests: - kernel BUG at ll_rw_blk.c:711! invalid operand: CPU:0 EIP:0010:[c01885fd] EFLAGS: 00010286 eax: 001f ebx: cb4e5cc0 ecx: 001f edx: 0002 esi: cb4e5cc0 edi: cff3f298 ebp: 0001 esp: cff4bf34 ds: 0018 es: 0018 ss: 0018 Process kupdate (pid: 4, stackpage=cff4b000) Stack: c02876a5 c0287982 02c7 cb4e5cc0 0001 0020 001e8480 cff3f2b0 cff3f2a8 0008 c0187fef 00fe c0188c2d cff3f298 0001 cb4e5cc0 cb4e5cc0 0001 cff4bfd0 Call Trace: [c02876a5] [c0287982] [c0187fef] [c0188c2d] [c0188d91] [c0135c4a] [c0271f36] [c0135cfd] [c013601a] [c0109618] Code: 0f 0b 83 c4 0c 0f b6 46 15 0f b7 4e 14 8b 14 85 a0 de 35 c0 - kernel BUG at ll_rw_blk.c:711! invalid operand: CPU:1 EIP:0010:[c01885fd] EFLAGS: 00010286 eax: 001f ebx: cf1152c0 ecx: 0097 edx: 0100 esi: cf1152c0 edi: cff3f298 ebp: 0001 esp: cff4bf34 ds: 0018 es: 0018 ss: 0018 Process kupdate (pid: 4, stackpage=cff4b000) Stack: c02876a5 c0287982 02c7 cf1152c0 0001 0020 001e8480 cff3f2b0 cff3f2a8 0008 c0187fef 00fe c0188c2d cff3f298 0001 cf1152c0 cf1152c0 0001 cff4bfd0 Call Trace: [c02876a5] [c0287982] [c0187fef] [c0188c2d] [c0188d91] [c0135c4a] [c0271f36] [c0135cfd] [c013601a] [c0109618] Code: 0f 0b 83 c4 0c 0f b6 46 15 0f b7 4e 14 8b 14 85 a0 de 35 c0 - After this, you StarOffice dies and can't even be killed via kill -9. On shutdown, the system hangs. After reboot, the /tmp filesystem was corrupted requiring manual fsck, which moves a file to lost+found (a temporary file from StarOffice). My system is otherwise rock solid, I switched back to kernel 2.4.0-test5 which is OK for me. I hope this helps, and please don't hurt me if this bug has already been reportet, but I don't read this list 'cause I'm not a developer. If you need to know more, feel free to contact me. greets, and go on with The Good Work mike -- // Ing. Michael Zieger, BSc. ---Zieger Michael EDV-Lösungen // http://www.zmi.at Linux 2.2.15 SMP // // May those who love us, love us. // And for those who don't love us, may the good Lord turn their hearts. // And if He can't turn their hearts, may He turn their ankles // So we'll know them by their limping. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
