On 13-Mar-01 Matthew Jacob wrote:
> To refresh memory:
>> fatal kernel trap:
>> trap entry = 0x4 (unaligned access fault)
>> a0 = 0xc3615fe1a88f382
>> a1 = 0x29
>> a2 = 0x1b
>> pc = 0xfffffc0000467578
>> ra = 0xfffffc00004627c4
>> curproc = 0xfffffe0009f5dbe0
>> pid = 1, comm = init
>> Stopped at vfs_object_create+0x38: jsr
>> db> t
>> vfs_object_create() at vfs_object_create+0x38
>> getnewvnode() at getnewvnode+0x564
>> devfs_allocv() at devfs_allocv+0xe0
>> devfs_root() at devfs_root+0x38
>> devfs_mount() at devfs_mount+0xf0
>> vfs_mount() at vfs_mount+0x910
>> mount() at mount+0xd8
>> syscall() at syscall+0x3f4
>> XentSys1() at XentSys1+0x10
> Interestingly enough, as Christian had also reported, a build of a GENERIC
> kernel seems to solve this problem.
> This is almost more alarming than a potential bug in vfs_object_create- as
> difference between the config file I was using should not cause this.
> *I* sure can't spot what config option might be different. I also had done a
> complete removal of the build directory and complete fresh build of GPLUS.
> (sounds of hair tearing).
Can you possibly try to narrow the differences down by tring out various kernel
configs in between GPLUS and GENERIC?
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message