[panic] Re: small heads-up: Syncing amd64 GENERIC with i386
GENERIC (removing LINUX stuff)
bsam at ipt.ru
Sun Dec 3 06:09:04 PST 2006
On Sun, 3 Dec 2006 11:14:18 +0100 Divacky Roman wrote:
> 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@ 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@ 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?
The same panic.
> 2) plain kldload linux && kldunload linux doesnt trigger any panic?
Plain kld(un)load linux works fine.
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
More information about the freebsd-amd64