amd64 module of linuxolator

[Boris Samorodov]

On Mon, 19 Jun 2006 00:45:31 +0400 Boris Samorodov wrote:
> On Sun, 18 Jun 2006 18:24:18 +0400 Boris Samorodov wrote:
> > On Sat, 17 Jun 2006 13:07:56 +0200 Divacky Roman wrote:
> > > On Sat, Jun 17, 2006 at 02:42:56PM +0400, Yuri Pankov wrote:
> > > > On Sat, 2006-06-17 at 11:56 +0200, Alexander Leidinger wrote:

> > > > > Modify /usr/src/sys/modules to contain
> > > > > _linprocfs=     linprocfs
> > > > > _linsysfs=      linsysfs
> > > > > in the 
> > > > > .if ${MACHINE_ARCH} == "amd64"
> > > > > section and build the kernel again. Please report back if it works.

> > > > The build fails with:
> > > > /usr/src/sys/compat/linprocfs/linprocfs.c:91:36:
> > > > machine/../linux/linux.h: No such file or directory

> > > www.stud.fit.vutbr.cz/~xdivac02/linux-fs.patch [1]

> > > pls try this patch.. I commited this to my p4 branch and I just need the
> > > testing if it loads/works (compilation is ok)

> > The patch was applied against -current cvs cleanly except the first
> > hunk. Thanks to Alexander (quoted) I did it by hand.

> > After building/installing the kernel all went well. The only change I
> > did to GENERIC was deletting of the option LINPROCFS. New kernel was
> > loaded and linprocfs was able to be loaded/unloaded.

> > Seems that a patch created against -current cvs tree may be safely
> > committed. Thanks!

> Hm. While testing the patch [1] together with the one Roman calls
> linuxolator patch I got a panic (on AMD64). The kernel is GENERIC with
> deleted:
> options        COMPAT_LINUX32
> options        LINPROCFS
> options        LINSYSFS

> Loading/unloading of linux.ko and linprocfs.ko works like a
> charm. Loading of linsysfs works either. But unloading of linsysfs
> gives a panic when I logged via ssh. I see a panic message on the
> screen of the testing machine but the system does not respord to
> keyboard. If I do unloading of linsysfs on the console the system just
> hangs without any messages. In both cases only reset button helps.

I've got another panic but I'm not sure if it is caused by those
patches.

I've been testing a new patch for FC4 port on amd64. Building went
fine, so did installing (linuxolator hadn't been loaded at boot time
but was autoloaded when installing the port). Package building, make
deinstall, pkg_add and pkg_delete went fine. But while "make
reinstall" the process stopped (it was a remote ssh session) after
pkg-message:
-----
[skip]
Let your lists for hosts, passwd and group be resolved via nsswitch.conf:
        passwd: files nis
        shadow: files nis
        group:  files nis
        hosts:  files dns nis

Read from remote host amd64.sem.ipt.ru: Operation timed out
-----

The screen of testing machine is (600K):
http://www.ipt.ru/screen/DSCN0072.JPG


WBR
-- 
Boris B. Samorodov, Research Engineer
InPharmTech Co,     http://www.ipt.ru
Telephone & Internet Service Provider