On Sun, Dec 03, 2006 at 02:18:28AM +0300, Boris Samorodov wrote: > On Sat, 02 Dec 2006 22:40:51 +0300 Boris Samorodov wrote: > > > On Sat, 2 Dec 2006 16:07:40 +0100 Alexander Leidinger wrote: > > > > the linux module is now usable on amd64 (thanks to kib_at_ and his commit > > > to the kernel linker in HEAD). > > > Cvsupped a couple of hours ago my amd64-current, rebuilt/reinstalled > > world/kernel. The kernel is GENERIC without COMPAT_LINUX32, LINPROCFS, > > LINSYSFS. But linux.ko hadn't been built. Should I cvsup once more or > > did I miss something? > > > I'd tested kib_at_ patches (about two weeks ago) and noticed that linux > > kernel module can't be unloaded _after_ mounting/unmounting linprocfs, > > linsysfs or linux devfs. Can anybody confirm? > > OK, after cvsup and rebuild/install kernel I do: > > # kldload linux > # kldload linsysfs > # kldunload linsysfs > > and get a reprodusable panic: 1) if you have linux "module" built statically in kernel can you reproduce this panic by kldload linsysfs && kldunload linsysfs? 2) plain kldload linux && kldunload linux doesnt trigger any panic? thnx romanReceived on Sun Dec 03 2006 - 09:14:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:03 UTC