2.4.4 bug...
I found a bug in the patches for kernel 2.4.4. When i use 2.4.4 clean, with no patches hde: IBM-DTLA-307020, ATA DISK drive hde: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=39870/16/63, UDMA(100) then, using kernel 2.4.4 with ac11 patch... hde: IBM-DTLA-307020, ATA DISK drive hde: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=39870/16/63, UDMA(44) why the hard-disk is found at udma 3?? -- -=[/home/slump]=- hdparm -t /dev/hde /dev/hde: Timing buffered disk reads: 64 MB in 2.29 seconds = 27.95 MB/sec -- -=[/home/slump]=- hdparm -X69 /dev/hde /dev/hde: setting xfermode to 69 (UltraDMA mode5) -=[/home/slump]=- hdparm -t /dev/hde /dev/hde: Timing buffered disk reads: 64 MB in 1.84 seconds = 34.78 MB/sec My machine is an athlon 950, with abit-kt7raid motherboard. My hard-disk is an IBM DTLA 307020 20gb UDMA 5. thank's to all ;) Guilherme M. Schroeder [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.4 bug...
I found a bug in the patches for kernel 2.4.4. When i use 2.4.4 clean, with no patches hde: IBM-DTLA-307020, ATA DISK drive hde: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=39870/16/63, UDMA(100) then, using kernel 2.4.4 with ac11 patch... hde: IBM-DTLA-307020, ATA DISK drive hde: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=39870/16/63, UDMA(44) why the hard-disk is found at udma 3?? -- -=[/home/slump]=- hdparm -t /dev/hde /dev/hde: Timing buffered disk reads: 64 MB in 2.29 seconds = 27.95 MB/sec -- -=[/home/slump]=- hdparm -X69 /dev/hde /dev/hde: setting xfermode to 69 (UltraDMA mode5) -=[/home/slump]=- hdparm -t /dev/hde /dev/hde: Timing buffered disk reads: 64 MB in 1.84 seconds = 34.78 MB/sec My machine is an athlon 950, with abit-kt7raid motherboard. My hard-disk is an IBM DTLA 307020 20gb UDMA 5. thank's to all ;) Guilherme M. Schroeder [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: kernel 2.4.4: BUG in ll_rw_blk.c?
On Wed, May 09 2001, Giacomo Mulas wrote: > I am running a 2.4.4 kernel compiled from the sources in the > debian kernel-source package (it only includes a couple of small patches > taken from pre and ac, as far as I can tell) and run in the following > oopses, always while compiling the kernel itself. Here I included three > different oopses, and the computer had been rebooted between them (for > different reasons). Is this a known bug? Any fix available for it? > The computer is a 500MHz PIII, with a 440BX chipset on the motherboard, > more data available if required (just ask) running debian potato. The only > "nonstandard" system component is a 2.1.3 libc6 compiled with the 2.4.4 > kernel headers, to be able to use large files. Here come the > (decoded) oopses: > > May 7 14:57:11 stampace kernel: elevator returned crap (-1072325408) > May 7 14:57:11 stampace kernel: kernel BUG at ll_rw_blk.c:778! > May 7 14:57:11 stampace kernel: invalid operand: If this happens, either your kernel or hardware is seriously screwed -- this is a _never happens_ case. So I suggest that you try a pristine kernel, most likely this one has been mangled. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
kernel 2.4.4: BUG in ll_rw_blk.c?
I am running a 2.4.4 kernel compiled from the sources in the debian kernel-source package (it only includes a couple of small patches taken from pre and ac, as far as I can tell) and run in the following oopses, always while compiling the kernel itself. Here I included three different oopses, and the computer had been rebooted between them (for different reasons). Is this a known bug? Any fix available for it? The computer is a 500MHz PIII, with a 440BX chipset on the motherboard, more data available if required (just ask) running debian potato. The only "nonstandard" system component is a 2.1.3 libc6 compiled with the 2.4.4 kernel headers, to be able to use large files. Here come the (decoded) oopses: May 7 14:57:11 stampace kernel: elevator returned crap (-1072325408) May 7 14:57:11 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 7 14:57:11 stampace kernel: invalid operand: May 7 14:57:11 stampace kernel: CPU:0 May 7 14:57:11 stampace kernel: EIP:0010:[__make_request+950/1696] May 7 14:57:11 stampace kernel: EFLAGS: 00010082 May 7 14:57:11 stampace kernel: eax: 001f ebx: ecx: ccdcc000 edx: c0229328 May 7 14:57:11 stampace kernel: esi: cc147840 edi: 0008 ebp: c02af660 esp: cc257e08 May 7 14:57:11 stampace kernel: ds: 0018 es: 0018 ss: 0018 May 7 14:57:11 stampace kernel: Process cpp (pid: 18004, stackpage=cc257000) May 7 14:57:11 stampace kernel: Stack: c01f801f c01f8262 030a 00ff cc147840 0001 000c c02ac9a0 May 7 14:57:11 stampace kernel:c02af688 000c 1000 0246 2000 c02af690 c1472d80 c02af688 May 7 14:57:11 stampace kernel:00ff 012a19c8 c0158f81 c02af660 May 7 14:57:11 stampace kernel: Call Trace: [generic_make_request+293/308] [submit_bh+87/116] [block_read_full_page+525/548] [add_to_page_cache_unique+198/208] [ext2_readpage+15/20] [ext2_get_block+0/1168] [generic_file_readahead+548/668] May 7 14:57:11 stampace kernel:[do_generic_file_read+838/1292] [generic_file_read+91/120] [file_read_actor+0/84] [sys_read+150/204] [system_call+51/56] May 7 14:57:11 stampace kernel: May 7 14:57:11 stampace kernel: Code: 0f 0b 83 c4 0c 83 7c 24 38 00 74 12 8b 44 24 38 89 44 24 40 May 8 15:35:06 stampace kernel: elevator returned crap (-1072325408) May 8 15:35:06 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 8 15:35:06 stampace kernel: invalid operand: May 8 15:35:06 stampace kernel: CPU:0 May 8 15:35:06 stampace kernel: EIP:0010:[__make_request+950/1696] May 8 15:35:06 stampace kernel: EFLAGS: 00010082 May 8 15:35:06 stampace kernel: eax: 001f ebx: ecx: c33f2000 edx: c0227b48 May 8 15:35:06 stampace kernel: esi: c3d8a6e0 edi: 0008 ebp: c02ad660 esp: c6f97e08 May 8 15:35:06 stampace kernel: ds: 0018 es: 0018 ss: 0018 May 8 15:35:06 stampace kernel: Process cpp (pid: 18605, stackpage=c6f97000) May 8 15:35:06 stampace kernel: Stack: c01f7957 c01f7b62 030a 00ff c3d8a6e0 0001 000c c02aa9a0 May 8 15:35:06 stampace kernel:c02ad688 000c 1000 0246 2000 c02ad690 c1470a80 c02ad688 May 8 15:35:06 stampace kernel:00ff 00cc8ca0 c0158f81 c02ad660 May 8 15:35:06 stampace kernel: Call Trace: [generic_make_request+293/308] [submit_bh+87/116] [block_read_full_page+525/548] [add_to_page_cache_unique+198/208] [ext2_readpage+15/20] [ext2_get_block+0/1168] [generic_file_readahead+548/668] May 8 15:35:06 stampace kernel:[do_generic_file_read+838/1292] [generic_file_read+91/120] [file_read_actor+0/84] [sys_read+150/204] [system_call+51/56] May 8 15:35:06 stampace kernel: May 8 15:35:06 stampace kernel: Code: 0f 0b 83 c4 0c 83 7c 24 38 00 74 12 8b 44 24 38 89 44 24 40 May 9 16:15:22 stampace kernel: elevator returned crap (-1072325408) May 9 16:15:22 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 9 16:15:22 stampace kernel: invalid operand: May 9 16:15:22 stampace kernel: CPU:0 May 9 16:15:22 stampace kernel: EIP:0010:[__make_request+950/1696] May 9 16:15:22 stampace kernel: EFLAGS: 00010082 May 9 16:15:22 stampace kernel: eax: 001f ebx: ecx: c289a000 edx: c0227b48 May 9 16:15:22 stampace kernel: esi: cd389ae0 edi: 0008 ebp: c02ad660 esp: c3b09e08 May 9 16:15:22 stampace kernel: ds: 0018 es: 0018 ss: 0018 May 9 16:15:22 stampace kernel: Process cpp (pid: 13267, stackpage=c3b09000) May 9 16:15:22 stampace kernel: Stack: c01f7957 c01f7b62 030a 00ff cd389ae0 0001 000c c02aa9a0 May 9 16:15:22 stampace kernel:c02ad688 000c 1000 0246 2000 c02ad690 c146e240 c02ad688 May 9 16:15:22 stampace kernel:00ff 0108d270 c0158f81 c02ad660 May 9 16:15:22 stampace kernel: Call Trace: [generic_make_request+293/308] [submit_bh+87/116]
kernel 2.4.4: BUG in ll_rw_blk.c?
I am running a 2.4.4 kernel compiled from the sources in the debian kernel-source package (it only includes a couple of small patches taken from pre and ac, as far as I can tell) and run in the following oopses, always while compiling the kernel itself. Here I included three different oopses, and the computer had been rebooted between them (for different reasons). Is this a known bug? Any fix available for it? The computer is a 500MHz PIII, with a 440BX chipset on the motherboard, more data available if required (just ask) running debian potato. The only nonstandard system component is a 2.1.3 libc6 compiled with the 2.4.4 kernel headers, to be able to use large files. Here come the (decoded) oopses: May 7 14:57:11 stampace kernel: elevator returned crap (-1072325408) May 7 14:57:11 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 7 14:57:11 stampace kernel: invalid operand: May 7 14:57:11 stampace kernel: CPU:0 May 7 14:57:11 stampace kernel: EIP:0010:[__make_request+950/1696] May 7 14:57:11 stampace kernel: EFLAGS: 00010082 May 7 14:57:11 stampace kernel: eax: 001f ebx: ecx: ccdcc000 edx: c0229328 May 7 14:57:11 stampace kernel: esi: cc147840 edi: 0008 ebp: c02af660 esp: cc257e08 May 7 14:57:11 stampace kernel: ds: 0018 es: 0018 ss: 0018 May 7 14:57:11 stampace kernel: Process cpp (pid: 18004, stackpage=cc257000) May 7 14:57:11 stampace kernel: Stack: c01f801f c01f8262 030a 00ff cc147840 0001 000c c02ac9a0 May 7 14:57:11 stampace kernel:c02af688 000c 1000 0246 2000 c02af690 c1472d80 c02af688 May 7 14:57:11 stampace kernel:00ff 012a19c8 c0158f81 c02af660 May 7 14:57:11 stampace kernel: Call Trace: [generic_make_request+293/308] [submit_bh+87/116] [block_read_full_page+525/548] [add_to_page_cache_unique+198/208] [ext2_readpage+15/20] [ext2_get_block+0/1168] [generic_file_readahead+548/668] May 7 14:57:11 stampace kernel:[do_generic_file_read+838/1292] [generic_file_read+91/120] [file_read_actor+0/84] [sys_read+150/204] [system_call+51/56] May 7 14:57:11 stampace kernel: May 7 14:57:11 stampace kernel: Code: 0f 0b 83 c4 0c 83 7c 24 38 00 74 12 8b 44 24 38 89 44 24 40 May 8 15:35:06 stampace kernel: elevator returned crap (-1072325408) May 8 15:35:06 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 8 15:35:06 stampace kernel: invalid operand: May 8 15:35:06 stampace kernel: CPU:0 May 8 15:35:06 stampace kernel: EIP:0010:[__make_request+950/1696] May 8 15:35:06 stampace kernel: EFLAGS: 00010082 May 8 15:35:06 stampace kernel: eax: 001f ebx: ecx: c33f2000 edx: c0227b48 May 8 15:35:06 stampace kernel: esi: c3d8a6e0 edi: 0008 ebp: c02ad660 esp: c6f97e08 May 8 15:35:06 stampace kernel: ds: 0018 es: 0018 ss: 0018 May 8 15:35:06 stampace kernel: Process cpp (pid: 18605, stackpage=c6f97000) May 8 15:35:06 stampace kernel: Stack: c01f7957 c01f7b62 030a 00ff c3d8a6e0 0001 000c c02aa9a0 May 8 15:35:06 stampace kernel:c02ad688 000c 1000 0246 2000 c02ad690 c1470a80 c02ad688 May 8 15:35:06 stampace kernel:00ff 00cc8ca0 c0158f81 c02ad660 May 8 15:35:06 stampace kernel: Call Trace: [generic_make_request+293/308] [submit_bh+87/116] [block_read_full_page+525/548] [add_to_page_cache_unique+198/208] [ext2_readpage+15/20] [ext2_get_block+0/1168] [generic_file_readahead+548/668] May 8 15:35:06 stampace kernel:[do_generic_file_read+838/1292] [generic_file_read+91/120] [file_read_actor+0/84] [sys_read+150/204] [system_call+51/56] May 8 15:35:06 stampace kernel: May 8 15:35:06 stampace kernel: Code: 0f 0b 83 c4 0c 83 7c 24 38 00 74 12 8b 44 24 38 89 44 24 40 May 9 16:15:22 stampace kernel: elevator returned crap (-1072325408) May 9 16:15:22 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 9 16:15:22 stampace kernel: invalid operand: May 9 16:15:22 stampace kernel: CPU:0 May 9 16:15:22 stampace kernel: EIP:0010:[__make_request+950/1696] May 9 16:15:22 stampace kernel: EFLAGS: 00010082 May 9 16:15:22 stampace kernel: eax: 001f ebx: ecx: c289a000 edx: c0227b48 May 9 16:15:22 stampace kernel: esi: cd389ae0 edi: 0008 ebp: c02ad660 esp: c3b09e08 May 9 16:15:22 stampace kernel: ds: 0018 es: 0018 ss: 0018 May 9 16:15:22 stampace kernel: Process cpp (pid: 13267, stackpage=c3b09000) May 9 16:15:22 stampace kernel: Stack: c01f7957 c01f7b62 030a 00ff cd389ae0 0001 000c c02aa9a0 May 9 16:15:22 stampace kernel:c02ad688 000c 1000 0246 2000 c02ad690 c146e240 c02ad688 May 9 16:15:22 stampace kernel:00ff 0108d270 c0158f81 c02ad660 May 9 16:15:22 stampace kernel: Call Trace: [generic_make_request+293/308] [submit_bh+87/116]
Re: kernel 2.4.4: BUG in ll_rw_blk.c?
On Wed, May 09 2001, Giacomo Mulas wrote: I am running a 2.4.4 kernel compiled from the sources in the debian kernel-source package (it only includes a couple of small patches taken from pre and ac, as far as I can tell) and run in the following oopses, always while compiling the kernel itself. Here I included three different oopses, and the computer had been rebooted between them (for different reasons). Is this a known bug? Any fix available for it? The computer is a 500MHz PIII, with a 440BX chipset on the motherboard, more data available if required (just ask) running debian potato. The only nonstandard system component is a 2.1.3 libc6 compiled with the 2.4.4 kernel headers, to be able to use large files. Here come the (decoded) oopses: May 7 14:57:11 stampace kernel: elevator returned crap (-1072325408) May 7 14:57:11 stampace kernel: kernel BUG at ll_rw_blk.c:778! May 7 14:57:11 stampace kernel: invalid operand: If this happens, either your kernel or hardware is seriously screwed -- this is a _never happens_ case. So I suggest that you try a pristine kernel, most likely this one has been mangled. -- Jens Axboe - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.4 bug report, non-member post
I'm using a brand-new 2.4.4 kernel without devfs. If you need to know some option I turned off or on while compiling, email me and I'll tell you. I did use 'kgcc' (egcs-2.91.66) from RH 7.0. I mounted an MSDOS floppy image using the 'vfat' filesystem through the loopback device, and every program which tried to access files on this filesystem was promptly killed, and this message appear in the kernel logs: Apr 29 17:01:58 monster kernel: Unable to handle kernel NULL pointer dereference at virtual address Apr 29 17:01:58 monster kernel: printing eip: Apr 29 17:01:58 monster kernel: Apr 29 17:01:58 monster kernel: *pde = Apr 29 17:01:58 monster kernel: Oops: Apr 29 17:01:58 monster kernel: CPU:0 Apr 29 17:01:58 monster kernel: EIP:0010:[agp_frontend_cleanup+0/-1072693248] Apr 29 17:01:58 monster kernel: EFLAGS: 00010286 Apr 29 17:01:58 monster kernel: eax: ebx: d3336c40 ecx: 0001 edx: d3336c60 Apr 29 17:01:58 monster kernel: esi: 080af768 edi: 0001 ebp: b5f0 esp: c5265f84 Apr 29 17:01:58 monster kernel: ds: 0018 es: 0018 ss: 0018 Apr 29 17:01:58 monster kernel: Process vi (pid: 8746, stackpage=c5265000) Apr 29 17:01:58 monster kernel: Stack: e5a65a2d d3336c40 080af768 0001 d3336c60 ffea d3336c40 c012ed6e Apr 29 17:01:58 monster kernel:d3336c40 080af768 0001 d3336c60 c5264000 0001 080af768 c0106ce7 Apr 29 17:01:58 monster kernel:0003 080af768 0001 0001 080af768 b5f0 0003 002b Apr 29 17:01:58 monster kernel: Call Trace: [] [sys_read+142/208] [system_call+51/56] Apr 29 17:01:58 monster kernel: Apr 29 17:01:58 monster kernel: Code: Bad EIP value. On an unrelated note. After installing the 2.4.4 kernel, I'm getting weird process hangs whenever I try to su from 'root' to anybody else. If I run strace on 'su' when I do this, it works fine. When su hangs, I kill it, and it tells me it's killing the child shell process, then, after a few seconds, comes back to my prompt. It's like the child shell process isn't being allowed to use the pty or something. These two problems have me spooked, and I'm moving back to 2.4.3 soon. If anybody has suggestions, or requests for info, please email me. Thanks, -- The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper ([EMAIL PROTECTED] http://www.omnifarious.org/~hopper) -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.4 bug report, non-member post
I'm using a brand-new 2.4.4 kernel without devfs. If you need to know some option I turned off or on while compiling, email me and I'll tell you. I did use 'kgcc' (egcs-2.91.66) from RH 7.0. I mounted an MSDOS floppy image using the 'vfat' filesystem through the loopback device, and every program which tried to access files on this filesystem was promptly killed, and this message appear in the kernel logs: Apr 29 17:01:58 monster kernel: Unable to handle kernel NULL pointer dereference at virtual address Apr 29 17:01:58 monster kernel: printing eip: Apr 29 17:01:58 monster kernel: Apr 29 17:01:58 monster kernel: *pde = Apr 29 17:01:58 monster kernel: Oops: Apr 29 17:01:58 monster kernel: CPU:0 Apr 29 17:01:58 monster kernel: EIP:0010:[agp_frontend_cleanup+0/-1072693248] Apr 29 17:01:58 monster kernel: EFLAGS: 00010286 Apr 29 17:01:58 monster kernel: eax: ebx: d3336c40 ecx: 0001 edx: d3336c60 Apr 29 17:01:58 monster kernel: esi: 080af768 edi: 0001 ebp: b5f0 esp: c5265f84 Apr 29 17:01:58 monster kernel: ds: 0018 es: 0018 ss: 0018 Apr 29 17:01:58 monster kernel: Process vi (pid: 8746, stackpage=c5265000) Apr 29 17:01:58 monster kernel: Stack: e5a65a2d d3336c40 080af768 0001 d3336c60 ffea d3336c40 c012ed6e Apr 29 17:01:58 monster kernel:d3336c40 080af768 0001 d3336c60 c5264000 0001 080af768 c0106ce7 Apr 29 17:01:58 monster kernel:0003 080af768 0001 0001 080af768 b5f0 0003 002b Apr 29 17:01:58 monster kernel: Call Trace: [e5a65a2d] [sys_read+142/208] [system_call+51/56] Apr 29 17:01:58 monster kernel: Apr 29 17:01:58 monster kernel: Code: Bad EIP value. On an unrelated note. After installing the 2.4.4 kernel, I'm getting weird process hangs whenever I try to su from 'root' to anybody else. If I run strace on 'su' when I do this, it works fine. When su hangs, I kill it, and it tells me it's killing the child shell process, then, after a few seconds, comes back to my prompt. It's like the child shell process isn't being allowed to use the pty or something. These two problems have me spooked, and I'm moving back to 2.4.3 soon. If anybody has suggestions, or requests for info, please email me. Thanks, -- The best we can hope for concerning the people at large is that they be properly armed. -- Alexander Hamilton -- Eric Hopper ([EMAIL PROTECTED] http://www.omnifarious.org/~hopper) -- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
