TB --- 2010-03-29 09:45:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-29 09:45:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-03-29 09:45:00 - cleaning the object tree
TB --- 2010-03-29 09:45:30 - cvsupping the source tree
TB --- 2010-03-29 09:45:30 -
TB --- 2010-03-29 10:34:35 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-29 10:34:35 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-03-29 10:34:35 - cleaning the object tree
TB --- 2010-03-29 10:34:54 - cvsupping the source tree
TB --- 2010-03-29 10:34:54 -
TB --- 2010-03-29 11:29:49 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-29 11:29:49 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-03-29 11:29:49 - cleaning the object tree
TB --- 2010-03-29 11:30:08 - cvsupping the source tree
TB --- 2010-03-29 11:30:08 -
TB --- 2010-03-29 11:37:24 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-29 11:37:24 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-03-29 11:37:24 - cleaning the object tree
TB --- 2010-03-29 11:37:36 - cvsupping the source tree
TB --- 2010-03-29 11:37:36 -
If you want to make sure that I see your reply please include me into recipient
list. FreeBSD mailing lists sometimes have high volume and it's easy to miss a
followup even if you are interested in reading it.
on 28/03/2010 18:25 Fabian Keil said the following:
Andriy Gapon a...@icyb.net.ua
On Saturday 27 March 2010 9:49:23 am Rick Macklem wrote:
On Fri, 26 Mar 2010, Petr Lampa wrote:
I've got several panic: nfsrelpath, see attached photo. I've found
one place where it could probably happen, please, can you look at this?
First name buffer is initialized in
On Sun, Mar 28, 2010 at 10:46:10PM +0300, Eugene Dzhurinsky wrote:
Okay, with simplified config things didn't change, so I submitted
PR: kern/145123
Sometimes I'm felling like being an idiot. I just realized that I had
configured both laptops to use same IP address, which was noticed on logs
Andriy Gapon a...@freebsd.org wrote:
on 28/03/2010 18:25 Fabian Keil said the following:
Andriy Gapon a...@icyb.net.ua wrote:
Looking at the code in mountmsdosfs(), it seems that SecPerClust can
have zero value at the place of the crash only if pm_BlkPerSec is
zero. See this line and the
on 29/03/2010 23:29 Fabian Keil said the following:
Andriy Gapon a...@freebsd.org wrote:
Thus, clearly, it is a fault of a tool that formatted the media for FAT.
It should have picked correct values, or rejected incorrect values if
those were provided as overrides via command line options.
On Mon, 29 Mar 2010, John Baldwin wrote:
I've cc'd freebsd-current, so that anyone conversant with the FreeBSD
VFS can jump in here. Am I right to assume that VOP_LOOKUP() for CREATE
will set SAVENAME when returning error == 0?
No, the caller has to set that flag. Some filesystems set it
hi there,
when doing fsck on my / fs i get this error:
Cannot Read BLK. 471617640 and The Following Disk Sectors could not be
read: 471617643. after this message the partition gets marked dirty.
i performed the following steps to verify the problem:
1) dd if=/dev/ada0 of=/dev/null bs=1m
2)
On 3/29/10, Alexander Best alexbes...@wwu.de wrote:
hi there,
when doing fsck on my / fs i get this error:
Cannot Read BLK. 471617640 and The Following Disk Sectors could not be
read: 471617643. after this message the partition gets marked dirty.
i performed the following steps to verify
On Mon, 29 Mar 2010, Andriy Gapon wrote:
...
I am not a FAT expert and I know to take Wikipedia with a grain of salt.
But please take a look at this:
http://en.wikipedia.org/wiki/File_Allocation_Table#Boot_Sector
In our formula:
SecPerClust *= pmp-pm_BlkPerSec;
we have the following
BTW, why can't gdb find any variables? They are just stack variables whose
address is easy to find.
...
#14 0x8042f24e in bread (vp=Variable vp is not available.
) at /usr/src/sys/kern/vfs_bio.c:748
... and isn't vp a variable? Maybe the bad default -O2 is destroying
14 matches
Mail list logo
