Yesterday i posted a message about troubles compiling 2.2.20RAID or
2.4.18/2.4.19rc1/2.4.19rc1aa2 kernel for an Alpha PC164LX.
I got a tip to use gcc-3.1 but i didn't find it from debian-trees,
so i used the latest 3.0 (gcc-3.0.4) compiler, and tried again.
2.2.20 w/RAID doesn't compile, so doesn't aa2-patched 2.4.19rc1.
I tried 2.4.18 using gcc-3.0.4 and it did compile and almost work.
I was able to make raid-1 /dev/md0, mke2fs -j for it and mount it
without any errors, but when i tried to use it, got crash.
Then i downloaded the latest 2.4-patch, 2.4.19-rc3 and compiled it
again. That went successfully and again it does allow me to create
raid, make filesystem and mount it, but using will crash.
Couple of minutes ago, i make very interesting notification.
This may be a reason, but how can it be solved:
pleco:/# free
total used free shared buffers cached
Mem: 514112 95408 418704 0 1976 27864
pleco:/# ls -l /proc/kcore
-r-------- 1 root root 4380869902336 hein?? 22 09:59 /proc/kcore
pleco:/# ls -lh /proc/kcore
-r-------- 1 root root 4.0T hein?? 22 10:38 /proc/kcore
The core shows a bit huge :-/ Four terabytes... huh.
What's up next?!
Please, CC directly to me: [email protected]
--sl
On Mon, Jul 22, 2002 at 04:40:23AM -0600, Thunder from the hill wrote:
> Hi,
>
> On Mon, 22 Jul 2002, Sami Louko wrote:
> > -r-------- 1 root root 4.0T hein?? 22 10:38 /proc/kcore
> >
> > The core shows a bit huge :-/ Four terabytes... huh.
>
> Mine (2.4.19-rc2-aa1) is 2 Giga, exactly the RAM size, here...
I wasn't able to compile 2.4.19-rc1-aa2, i should to try compile the
same kernel you have.
I would like to know is it possible to manually fix the size of kcore,
because i do have 512MB mem, not 4080GB, anybody doesn't have that much. =)
I just notified, an errormessage that shows at boot-time, got it from log,
Jul 22 09:07:55 mikrolahti kernel: Error seeking in /dev/kmem
What may be wrong??!
--sl
Hi,
On Mon, 22 Jul 2002, Sami Louko wrote:
> Jul 22 09:07:55 mikrolahti kernel: Error seeking in /dev/kmem
>
> What may be wrong??!
Some of the /proc file mappings. Are the other files in /proc OK? One can
always have a 4TiB+ file, you just have to trick the system in thinking
the file is that big. Otherwise it's just a plain procfs bug.
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
Hi,
On Mon, 22 Jul 2002, Sami Louko wrote:
> -r-------- 1 root root 4.0T hein?? 22 10:38 /proc/kcore
>
> The core shows a bit huge :-/ Four terabytes... huh.
Mine (2.4.19-rc2-aa1) is 2 Giga, exactly the RAM size, here...
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------