Re: [PARPORT] DMESG Errors-- Please Help


Tim Waugh (tim@cyberelk.demon.co.uk)
Fri, 19 Feb 1999 18:17:00 +0000 (GMT)


On Fri, 19 Feb 1999 mdriggers@nextlink.net wrote:

> 1. fdisk /dev/sda
> 2. d 4 (to delete partition 4)
> 3. n primary 4 1-96 (to create a new partition 4 using sectors 1-96)
> 4. w (to write the new partition to disk)

(Why do you do this?)

> EXT2-fs error (device 08:04): ext2_find_entry: bad entry in directory #2:
> rec_len % 4 != 0 - offset=0,
> inode=4134912133, rec_len=60553, name_len=50013

Have you tried 'fsck /dev/sda', to check the filesystem?

> Unable to handle kernel paging request at virtual address c5553ce4
> current->tss.cr3 = 02feb000, %cr3 = 02feb000
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<00164f34>]
> EFLAGS: 00010202
> eax: 025e7a18 ebx: 00000003 ecx: 41ed000b edx: 05553ce0
> esi: 001f6b14 edi: 03d64800 ebp: 05553ce0 esp: 00c23e3c
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process mount (pid: 6823, process nr: 61, stackpage=00c23000)
> Stack: 001f6b14 00000804 001dae08 08050804 0008cf00 00000000 0008cf00 0008cf00
> 00976400 00c23f2c 00976400 00c23f2c 00000003 00de8005 00000001 00000000
> 00000700 025e7a18 00000000 00000200 00000000 00c23ee8 00000003 00976400
> Call Trace: [<0015d38f>] [<001248c1>] [<0012bed8>] [<00166b0d>] [<001287cf>]
> [<00128c0d>] [<00129103>]
> [<0010abc5>]
> Code: 8b 4d 04 81 f9 72 72 41 61 74 11 51 68 e2 24 1c 00 e8 da f6

Eek! That shouldn't happen. Does Red Hat ship a System.map for the
kernel image, does anyone know?

Mike, after this last bit ("Oops: 0000"), is the machine still usable?
Can you make the problem happen again? What does lsmod say?

Tim.
*/

-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --



This archive was generated by hypermail 2.0b3 on Fri 19 Feb 1999 - 13:35:55 EST