Hi Mike, Yes, that's the machine I am stuck with. The attached file is the "dmesg" of this machine. Thanks a lot. Best Regards, Cheng Cui 578-5445 . 231 Johnston Hall . Baton Rouge, LA 70803 -----Original Message----- From: Mike Hibler [mailto:mike@flux.utah.edu] Sent: Wednesday, March 11, 2009 10:28 AM To: Cui, Cheng Cc: testbed-admins@flux.utah.edu Subject: Re: [Testbed-admins] Question about update MFS Is this the machine you have been having problems with? Sorry, I have not gotten back to you. You sent us the "pciconf" output, can you also send the output of the "dmesg" command? That will print out the kernel boot log. On Wed, Mar 11, 2009 at 10:07:37AM -0500, Cui, Cheng wrote: > Hello, > > > > Due to hardware features, I have one machine that seems not compatible with > current 5.0 version MFS. I have found one link which looks like outdated but > I still get something beneficial from it. > http://users.emulab.net/trac/emulab/wiki/UpdateMFS > > > > However, there is one question I am not clear with. In your source code of > testbed-080901\tftpboot folder, I read the MFS notification. It said every > MFS has a kernel with addition of emulab component, such as: > > - MROUTING > > - HZ=1000 > > - IPOD (Emulab "ping of death" mod) > > - EXT2FS (Linux filesystem support) > > - MOUNTD_SUX_HACK (Emulab client-side NFS hack to avoid race in mountd) > > > > But at the end, if installing a new kernel, it said that just cp a new > kernel and prepare it will be right. So what does that new kernel mean? How > can I modify and update my client FreeBSD with emulab component to generate > a compatible MFS? Thanks. > > > > Best Regards, > > > > Cheng Cui > > 578-5445 . 231 Johnston Hall . Baton Rouge, LA 70803 >
Attachment:
sun_w2100z_dmesg_freebsd.log
Description: Binary data