boot in singleuser.
swapoff -a
swapon /dev/hdc2
insmod isofs
mount /dev/hdd /mnt/cdrom
exec su - egor
startx
Well.. This started, when I'm used xv very hardly in single user because of
memory leak (only 8 mb). xv hand up sometimes (very hard - even numlock
stopped), sometimes caused X crash, sometimes caused system death with black
screen. And now this happened. xv or X said smth about signal 4, and get
out. Then any try to start X (even just "X") caused signal 11.
Ok, this staring in about 50 seconds from boot. I mean - about 50 seconds
you can work, and then - signal 11 every time you try to run X.
Well, and kernel get crazy. "Ext2fs panic: smth not implemented, can't read
smth beyong smth" and hang up. fsck told all is ok. Sometimes system slowed
down like 33mhz 486, for about 5 seconds (look, this is unbelievable, but
true!), sometimes system stops for about 0.1 sec.
My system: redhat 3.0.3 (3.0.3 + "Updates"), kernel 2.0.25, Motherboard
noname, umc chipset. Processor amd 486dx4-100, but running at 120 mhz.
And my hd configuration: first channel - 40mb swap, second chanel - 730 wd
caviar, and "hdc2" is 60mb another swap partition. cdrom is on another
chanel.
Seems to me, I have broken hardware, because strange this started to happen
from 2.0.23 kernel, when it was out.
Yep, and forget: I get this regulary since 2.0.23:
Nov 11 12:57:20 fastware kernel: stack segment: 0000
Nov 11 12:57:20 fastware kernel: CPU: 0
Nov 11 12:57:20 fastware kernel: EIP: 0010:[<00184001>]
Nov 11 12:57:20 fastware kernel: EFLAGS: 00010282
Nov 11 12:57:20 fastware kernel: eax: f2ffb034 ebx: 74e35a01 ecx: d5ab778b edx: 3f31d2f0
Nov 11 12:57:20 fastware kernel: esi: e96b1b6e edi: 16492e23 ebp: a32e516b esp: 0040acfc
Nov 11 12:57:20 fastware kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Nov 11 12:57:20 fastware kernel: Process rnews (pid: 9984, process nr: 23, stackpage=0040a000)
Nov 11 12:57:20 fastware kernel: Stack: 0040ae5c 0100007f 0040ae9c 00489404 6c00c88b 4a85c14d e96b1b6e 001a46c4
Nov 11 12:57:20 fastware kernel: fffffff8 0040ae6c d5ab778b 16492e23 765c4de7 d5888585 2eb58dff 6265a6ec
Nov 11 12:57:20 fastware kernel: a7c541c1 91ae0d73 0e9be144 4ec7d1de dc5a2e63 fab40cf9 b27cfeae 69f3c1da
Nov 11 12:57:20 fastware kernel: Call Trace: [<0100007f>] [<00184c42>] [<00145d50>] [<0100007f>] [<0100007f>] [<00149188>] [<0100007f>]
Nov 11 12:57:20 fastware kernel: [<0100007f>] [<00152849>] [<0013afc8>] [<0100007f>] [<0013c520>] [<001520ca>] [<0013a2d6>] [<0013a959>]
Nov 11 12:57:20 fastware kernel: [<0013bd5e>] [<0010a842>]
Nov 11 12:57:20 fastware kernel: Code: 8b 94 25 f4 00 00 0f c1 c2 05 8f 84 24 f0 0f 00 00 33 8c 24
Nov 11 12:57:22 fastware kernel: stack segment: 0000
Nov 11 12:57:22 fastware kernel: CPU: 0
Nov 11 12:57:22 fastware kernel: EIP: 0010:[<00184001>]
Nov 11 12:57:22 fastware kernel: EFLAGS: 00010296
Nov 11 12:57:22 fastware kernel: eax: 0a04e38a ebx: b1332b5b ecx: d5ab768a edx: d6371036
Nov 11 12:57:22 fastware kernel: esi: 696b117e edi: d6492eab ebp: b17d75d9 esp: 00391cfc
Nov 11 12:57:22 fastware kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Nov 11 12:57:22 fastware kernel: Process rnews (pid: 9992, process nr: 26, stackpage=00391000)
Nov 11 12:57:22 fastware kernel: Stack: 00391e5c 0100007f 00391e9c 00489504 6c00c8ef 1a85c15c 696b117e 001a46c4
Nov 11 12:57:22 fastware kernel: fffffff8 00391e6c d5ab768a d6492eab 765c48f7 55888415 2eb58def 7265a470
Nov 11 12:57:22 fastware kernel: a7c54181 91ae0d7a 0e9be004 4ec7d17f 8c5a2e72 12b40cf1 a27cfeff c1f3c1c3
Nov 11 12:57:22 fastware kernel: Call Trace: [<0100007f>] [<00184c42>] [<00145d50>] [<0100007f>] [<0100007f>] [<00149188>] [<0100007f>]
Nov 11 12:57:22 fastware kernel: [<0100007f>] [<00152849>] [<0013afc8>] [<0100007f>] [<0013c520>] [<001520ca>] [<0013a2d6>] [<0013a959>]
Nov 11 12:57:22 fastware kernel: [<0013bd5e>] [<0010a842>]
Nov 11 12:57:22 fastware kernel: Code: 8b 94 25 f4 00 00 0f c1 c2 05 8f 84 24 f0 0f 00 00 33 8c 24
Nov 11 12:57:25 fastware kernel: Unable to handle kernel paging request at virtual address c6ccbc04
Nov 11 12:57:25 fastware kernel: current->tss.cr3 = 0057c000, Lr3 = 0057c000
Nov 11 12:57:25 fastware kernel: *pde = 00000000
Nov 11 12:57:25 fastware kernel: Oops: 0000
Nov 11 12:57:25 fastware kernel: CPU: 0
Nov 11 12:57:25 fastware kernel: EIP: 0010:[<00184001>]
Nov 11 12:57:25 fastware kernel: EFLAGS: 00010a82
Nov 11 12:57:25 fastware kernel: eax: 875f2c71 ebx: 2cba9b75 ecx: d5ab7589 edx: d3915b4c
Nov 11 12:57:25 fastware kernel: esi: e96b0f4f edi: 96492f32 ebp: f7ccbb10 esp: 006d9cfc
Nov 11 12:57:25 fastware kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Nov 11 12:57:25 fastware kernel: Process rnews (pid: 10001, process nr: 25, stackpage=006d9000)
Nov 11 12:57:25 fastware kernel: Stack: 006d9e5c 0100007f 006d9e9c 00489604 6c00c843 ea85c16f e96b0f4f 001a46c4
Nov 11 12:57:25 fastware kernel: fffffff8 006d9e6c d5ab7589 96492f32 765c47c7 d58886a4 2eb58ddf 4265a3d4
Nov 11 12:57:25 fastware kernel: a7c54141 91ae0d61 0e9be3c4 4ec7d09c 7c5a2e41 2ab40ce8 927cfe0c 39f3c1e9
Nov 11 12:57:25 fastware kernel: Call Trace: [<0100007f>] [<00184c42>] [<00145d50>] [<0100007f>] [<0100007f>] [<00149188>] [<0100007f>]
Nov 11 12:57:25 fastware kernel: [<0100007f>] [<00152849>] [<0013afc8>] [<0100007f>] [<0013c520>] [<001520ca>] [<0013a2d6>] [<0013a959>]
Nov 11 12:57:25 fastware kernel: [<0013bd5e>] [<0010a842>]
Nov 11 12:57:25 fastware kernel: Code: 8b 94 25 f4 00 00 0f c1 c2 05 8f 84 24 f0 0f 00 00 33 8c 24
Nov 11 17:26:35 fastware syslogd 1.3-0: restart.
Nov 11 17:26:36 fastware kernel: klogd 1.3-0, log source = /proc/kmsg started.
Nov 11 17:26:36 fastware kernel: Cannot find map file.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What's this ? Found on next reboot.
Nov 11 17:26:36 fastware kernel: Console: 16 point font, 400 scans
Nov 11 17:26:36 fastware kernel: Console: colour VGA+ 80x25, 1 virtual console (max 63)
Please, help me to solve this troube, I'm very tied of this. :~( I will
propably die, rather than say "goodbye" to Linux.
And I will, if this bug will not be solved. :)