Re: Jenkins build is back to stable : FreeBSD_stable_10 #368

2016-09-01 Thread Craig Rodrigues 
Thank you for fixing this.

--
Craig

On Thursday, September 1, 2016,  wrote:

> See 
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: svn commit: r301752 - head/contrib/netbsd-tests/lib/libc/string

2016-08-31 Thread Craig Rodrigues 
Ngie,

Can you please MFC this to stable/10 branch?
I believe this has been causing a test failure in this branch
since June.

Thanks.

--
Craig


On Thu, Jun 9, 2016 at 11:35 AM, Garrett Cooper  wrote:

> Author: ngie
> Date: Thu Jun  9 18:35:37 2016
> New Revision: 301752
> URL: https://svnweb.freebsd.org/changeset/base/301752
>
> Log:
>   Update `goodResult` after recent changes made to the PRNG in libc
>
>   The PRNG was changed in r300953/r300956, and subsequently, the numbers
>   generated have changed. This is expected ABI breakage per ache
>
>   X-MFC with: r300953, r300956
>   Tested with: amd64, i386
>   Sponsored by: EMC / Isilon Storage Division
>
> Modified:
>   head/contrib/netbsd-tests/lib/libc/string/t_memcpy.c
>
> Modified: head/contrib/netbsd-tests/lib/libc/string/t_memcpy.c
> 
> ==
> --- head/contrib/netbsd-tests/lib/libc/string/t_memcpy.cThu Jun
> 9 18:27:41 2016(r301751)
> +++ head/contrib/netbsd-tests/lib/libc/string/t_memcpy.cThu Jun
> 9 18:35:37 2016(r301752)
> @@ -54,7 +54,7 @@ char result[100];
>  #ifdef __NetBSD__
>  const char goodResult[] = "7b405d24bc03195474c70ddae9e1f8fb";
>  #else
> -const char goodResult[] = "217b4fbe456916bf62a2f85df752e4ab";
> +const char goodResult[] = "5ab4443f0e3e058d94087d9f2a11ef5e";
>  #endif
>
>  static void
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Test failures on 10-STABLE

2016-08-29 Thread Craig Rodrigues 
I notice that there are some consistent test failures on 10-STABLE:

https://jenkins.freebsd.org/job/FreeBSD_stable_10/362/testReport/

sys.geom.class.gate.2
lib.libc.string.memcpy_test.memcpy_basic

have been failing for about a month.

Does anyone have any ideas about what caused them?
This looks like some bad merges happened.

--
Craig
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Jenkins build is still unstable: FreeBSD_stable_10 #356

2016-08-09 Thread Craig Rodrigues 
On Mon, Aug 8, 2016 at 4:26 PM, George Mitchell 
wrote:

> On 08/08/16 18:56, jenkins-ad...@freebsd.org wrote:
> > See 
> > [...]
>
> Can someone please clarify for me the distinction between
> succeeding vs. failing and being stable vs. unstable?   -- George
>
>
Unstable means the build succeeded, but one of the tests is failing.

Look at the bottom of https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/356/
to see which test is failing.

It would be nice if someone could fix this, since it seems to be a
legitimate bug that has
been introduced by recent merges.

--
Craig
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Cross buildworld on amd64 for i386 errors

2016-01-25 Thread Craig Rodrigues 
On Mon, Jan 25, 2016 at 1:55 PM, Daniel Eischen 
wrote:

>
> I'm trying to build an i386 buildworld on an amd64 system.
> I'm at r294370.
>
> This is what I've tried so far:
>
>   make TARGET_ARCH=i386 MAKEOBJDIRPREFIX=/opt/foo/obj.x86 -j8 buildworld
>   make TARGET=i386 MAKEOBJDIRPREFIX=/opt/foo/obj.x86 -j8 buildworld
>
> Neither of which work.  They both result in the error below.  What
> is the standard procedure for cross-building i386 from amd64?
>

It looks like you are not alone in encountering these problems.
For this build set up by Li-Wen Hsu:
https://jenkins.freebsd.org/job/FreeBSD_HEAD_i386

he downloads this image
http://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/10.2-RELEASE/base.txz
and then extracts that to create an i386 jail, where the build is performed
on an amd64 host.

--
Craig
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Have I got this VIMAGE setup correct?

2015-12-22 Thread Craig Rodrigues 
On Tue, Dec 22, 2015 at 9:05 AM, Garrett Wollman 
wrote:

> Any patches I should pull up to make this setup more
> reliable before I roll it out in production?
>
>
If you loook at CURRENT, bz@ has committed a few VIMAGE related fixes
this week which you might want to look at.

--
Craig
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Build failed in Jenkins: FreeBSD_stable_10 #1336

2015-04-06 Thread Craig Rodrigues 
On Sun, Apr 5, 2015 at 4:45 AM, Dimitry Andric d...@freebsd.org wrote:

  --- aslcompilerparse.c ---
  yacc: f - maximum table size exceeded
  *** [aslcompilerparse.c] Error code 2

 Strangely, this worked fine for me when making a universe on our
 reference stable/10 machine.  Is this particular Jenkins slave still at
 FreeBSD 10.1-RELEASE?


Yes, that's right.



 I suspect that it is missing r277086, which increases yacc's MAXTABLE.

 -Dimitry


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Apparent fxp regression in FreeBSD 8.4-RC3

2013-05-24 Thread Craig Rodrigues 
On May 24, 2013 1:58 AM, Jeremy Chadwick j...@koitsu.org wrote:

 I can't test anything without an ISO -- the system in question is truly
 bare-bones (no hard disk, can't boot USB memsticks, etc.).  I'm not a
 good test subject for changes on this one, I'm afraid.

On another system, if you can set up an NFS root file system of 8.4 and PXE
boot it, then you can help test individual changes to binaries such as
dhclient.  See:

http://www.freebsd.org/doc/en/books/handbook/network-pxe-nfs.html

PXE booting environment may or may not repro the problem, but
it would be very helpful if you could try it since you have the right
hardware.

As Glen and Josh have mentioned, unfortunately this is probably too late in
the 8.4 release cycle to fix and will have to be release noted.
--
Craig
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Apparent fxp regression in FreeBSD 8.4-RC3

2013-05-13 Thread Craig Rodrigues 
On Sat, May 11, 2013 at 7:57 PM, Michael L. Squires mi...@siralan.orgwrote:

 I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp driver on
 an older Supermicro single CPU single core Xeon motherboard.

 I know that 8.3-Release does not have this issue, but don't know when in
 the updates to that release the regression was introduced.

 I use the fxp driver to connect to a Motorola Surfboard cable modem, and
 immediately saw the following occur many times:

 May 10 23:00:04 familysquires kernel: fxp0: link state changed to DOWN
 May 10 23:00:04 familysquires dhclient: New Subnet Mask (fxp0):
 255.255.240.0
 May 10 23:00:04 familysquires dhclient: New Broadcast Address (fxp0):
 255.255.25
 5.255
 May 10 23:00:04 familysquires dhclient: New Routers (fxp0): xx.xxx.xxx.1
 May 10 23:00:06 familysquires kernel: fxp0: link state changed to UP
 May 10 23:00:22 familysquires dhclient: New IP Address (fxp0):
 xx.xxx.xxx.163
 May 10 23:00:22 familysquires kernel: fxp0: link state changed to DOWN
 May 10 23:00:22 familysquires dhclient: New Subnet Mask (fxp0):
 255.255.240.0
 May 10 23:00:22 familysquires dhclient: New Broadcast Address (fxp0):
 255.255.255.255
 May 10 23:00:22 familysquires dhclient: New Routers (fxp0): xx.xxx.xxx.1
 May 10 23:00:24 familysquires kernel: fxp0: link state changed to UP

 repeated without end.



I recently upgraded one of my systems from FreeBSD 7.4 to FreeBSD releng/8,
and had DHCP problems.
My system though is running a bge NIC, not fxp.
I don't know if this solution can help your case, but I found
that this helped me.  I added the following line to my /etc/rc.conf:

synchronous_dhclient=YES

Without that line, my system would not boot up properly with networking
working.

--
Craig
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso

2012-04-17 Thread Craig Rodrigues 
On Mon, Apr 16, 2012 at 9:29 PM, Adam Vande More amvandem...@gmail.com wrote:
 On Mon, Apr 16, 2012 at 10:30 PM, Craig Rodrigues rodr...@crodrigues.org
 wrote:

 After exchanging a few e-mails with Bernard, I think I understand the
 problem.
 According to the VirtualBox manual:

 http://www.virtualbox.org/manual/ch03.html#intro-64bitguests

 The CPU needs to support hardware-assisted virtualization in order for
 VirtualBox to support 64-bit guests.
 Without the CPU support, VirtualBox cannot do it.  I double checked
 this with CoreInfo.exe from Windows Sysinternals utilities,
 and also from the Intel data sheet for my CPU:

 http://ark.intel.com/products/30787
 (VT-x option not supported)


 I will use QEMU under Windows until I can get a better machine. :)


 I believe a Windows 7 product key will activate either 32 or 64 install, so
 unless you have a specific reason to install 64 bit then you are likely
 better using 32 anyway.  32 bit OS's and apps use less memory than their
 corresponding 64 bit counterparts.



 --
 Adam Vande More


Hi,

Yes, you are right.  Windows 7 comes on 2-DVD's, one for 32-bit and one for
64-bit.  The same product key can be used for either version.

I had installed 64-bit Windows with the intent of testing out 64-bit guest
OS's under FreeBSD, and was unaware of the requirements for
hardware assisted virtualization. :)
I am interested in developing and testing 32-bit and 64-bit Windows binaries
anyways, so I will keep my install for now. :)

Thanks.
-- 
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso

2012-04-16 Thread Craig Rodrigues 
Hi,

I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso
inside VirtualBox and am having some problems.

The error messages I am getting are similar to the ones mentioned here:

http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html




My host environment
===

Operating System: Windows 7, home edition, 64-bit
VirtualBox for Windows, version 4.1.12 r77245

CPU Information


I downloaded the CoreInfo.exe utility which is part of Windows
Sysinternals utilities
( http://technet.microsoft.com/en-us/sysinternals/bb545027 )

According to this utility, my CPU is:

Intel(R) Core(TM)2 Duo CPU T5450  @ 1.66GHz
Intel64 Family 6 Model 15 Stepping 13, GenuineIntel
HTT *   Hyperthreading enabled
HYPERVISOR  -   Hypervisor is present
VMX -   Supports Intel hardware-assisted virtualization
SVM -   Supports AMD hardware-assisted virtualization
EM64T   *   Supports 64-bit mode


So my CPU support 64-bit mode, but does not support hardware-assisted
virtualization.



Error message
=
If I try to mount and then boot it under VirtualBox, I get this error:

   CPU doesn't support long mode

   Consoles: internal video/keyboard
   BIOS drive C: is disk0
   BIOS 639kB/523264kB available memory

   FreeBSD/x86 bootstrap loader, Revision 1.1
   (r...@farrell.cse.buffalo.edu, Tue Jan  3 06:51:49 UTC 2012)
   Can't work out which disk we are booting from.
   Guess BIOS device 0x not found by probes, defaulting to disk0:
   FATAL: int13_harddisk: function 42. Can't use 64bits lba



Does anyone know how to fix this problem in VirtualBox?




QEMU for Windows


Just to try something else, I downloaded QEMU 0.9.0 for Windows from:

http://www.h7.dion.ne.jp/~qemu-win/

I extracted the zip file into a directory:  C:\local\qemu-0.9.0-windows

I then ran:

   cd c:\local\qemu-0.9.0-windows
   qemu-system-x86_64.exe -L . -m 128 -cdrom
c:\temp\FreeBSD-9.0-RELEASE-amd64-bootonly.iso

The ISO booted up just fine.  From the dmesg output, this was the emulated CPU:

   CPU: QEMU Virtual CPU version 0.9.0 (1666.98-MHz K8-class CPU)
Origin = AuthenticAMD Id = 0x623 Family = 6 Model = 2 Stepping = 3

Features=0x78bfbfdFPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,SE36,CLFLUSH,MMX,FXSR,SSE,SSE2
Features2=0x1SSE3
AMD Features=0x20100800SYSCALL,NX,LM




Does anyone know how I can get VirtualBox to behave the same way
as QEMU for FreeBSD-9.0-RELEASE-amd64-bootonly.iso?

Thanks.

--
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso

2012-04-16 Thread Craig Rodrigues 
On Mon, Apr 16, 2012 at 12:08 AM, Craig Rodrigues
rodr...@crodrigues.org wrote:
 My host environment
 ===

 Operating System: Windows 7, home edition, 64-bit
 VirtualBox for Windows, version 4.1.12 r77245

 CPU Information
 

 I downloaded the CoreInfo.exe utility which is part of Windows
 Sysinternals utilities
 ( http://technet.microsoft.com/en-us/sysinternals/bb545027 )

 According to this utility, my CPU is:
 
    Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz
    Intel64 Family 6 Model 15 Stepping 13, GenuineIntel
    HTT         *       Hyperthreading enabled
    HYPERVISOR  -       Hypervisor is present
    VMX         -       Supports Intel hardware-assisted virtualization
    SVM         -       Supports AMD hardware-assisted virtualization
    EM64T       *       Supports 64-bit mode
 

 So my CPU support 64-bit mode, but does not support hardware-assisted
 virtualization.



 Error message
 =
 If I try to mount and then boot it under VirtualBox, I get this error:

   CPU doesn't support long mode

   Consoles: internal video/keyboard
   BIOS drive C: is disk0
   BIOS 639kB/523264kB available memory

   FreeBSD/x86 bootstrap loader, Revision 1.1
   (r...@farrell.cse.buffalo.edu, Tue Jan  3 06:51:49 UTC 2012)
   Can't work out which disk we are booting from.
   Guess BIOS device 0x not found by probes, defaulting to disk0:
   FATAL: int13_harddisk: function 42. Can't use 64bits lba



 Does anyone know how to fix this problem in VirtualBox?


Hi,

After exchanging a few e-mails with Bernard, I think I understand the problem.
According to the VirtualBox manual:

http://www.virtualbox.org/manual/ch03.html#intro-64bitguests

The CPU needs to support hardware-assisted virtualization in order for
VirtualBox to support 64-bit guests.
Without the CPU support, VirtualBox cannot do it.  I double checked
this with CoreInfo.exe from Windows Sysinternals utilities,
and also from the Intel data sheet for my CPU:

http://ark.intel.com/products/30787
(VT-x option not supported)


I will use QEMU under Windows until I can get a better machine. :)

--
Craig Rodrigues
rodr...@crodrigues.org



-- 
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: can audio CDs be played with ATA_CAM ?

2011-10-26 Thread Craig Rodrigues 
On Wed, Oct 26, 2011 at 9:57 AM, Claude Buisson clbuis...@orange.fr wrote:

 Doing my home work step by step:

 I found only 1 place in VLC where the first message:

 [0x2caf2a3c] cdda access error: Could not set block size

 is emitted, after an:

 ioctl( p_vcddev-i_device_handle, CDRIOCSETBLOCKSIZE, i_size )

 CDRIOCSETBLOCKSIZE is defined in sys/cdrio.h, and in the kernel used in:

 sys/dev/ata/atapi-cd.c

 which is a brought into the kernel by:

 device atapicd

 So the natural question is:

 Is this ioctl supported with ATA_CAM (and atapicam) ?

 If not, what is to be used instead ?

Claude,

Thanks for digging into this a bit.

I just added some code to make it easier for applications to detect
at runtime if ATA_CAM has been configured in the kernel:

http://lists.freebsd.org/pipermail/svn-src-stable-9/2011-October/000114.html

I am not 100% sure how the CD driver works with ATA_CAM.

I think you might need to look at:

src/sys/cam/scsi/scsi_cd.c

and also read the cd(4) man page.

We may need to extend scsi_cd.c, but I'm not sure.

-- 
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Craig Rodrigues 
On Tue, Oct 25, 2011 at 3:15 AM, Claude Buisson clbuis...@orange.fr wrote:
 Hi,

 When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
 ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
 atapicam (and reverting from cdN to acdN of course), vlc was OK again.

Hi,

Would vlc have worked if, while ATA_CAM was enabled,
there was a symlink so that /dev/acd0 - cd0 ?
-- 
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ssh to FreeBSD 4 systems: xmalloc: zero size

2008-09-24 Thread Craig Rodrigues 
Hi,

I have received no feedback about this problem.
Can someone apply the patch to SSH to fix the regression
which I mentioned earlier?
--
Craig Rodrigues
[EMAIL PROTECTED]


On Mon, Sep 15, 2008 at 10:17:04PM +, Craig Rodrigues wrote:
 Hi,
 
 I can confirm that this patch solves my problem:
 
 https://bugzilla.mindrot.org/attachment.cgi?id=1554
 
 That patch is part of this ssh bug:
 
 https://bugzilla.mindrot.org/show_bug.cgi?id=1496
 
 Can we get this fix into FreeBSD before the 7.1 RELEASE?
 
 Thanks.
 --
 Craig Rodrigues
 [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ssh to FreeBSD 4 systems: xmalloc: zero size

2008-09-24 Thread Craig Rodrigues 
On Wed, Sep 24, 2008 at 05:24:24PM -0700, Alfred Perlstein wrote:
 Hey Craig, if no one replies by next week, please just apply
 the patch, it's pretty critical that FreeBSD be able to talk
 ssh to other machines out there.


Des applied the necessary fix:
http://lists.freebsd.org/pipermail/cvs-src/2008-September/095939.html

so all is well.  Thanks!

-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

ssh to FreeBSD 4 systems: xmalloc: zero size

2008-09-15 Thread Craig Rodrigues 
Hi,

With the latest FreeBSD 7.1 PRE-RELEASE, I am having trouble
ssh'ing to FreeBSD 4 systems.

I am getting this error:
OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connection established.
debug1: identity file /homes/rodrigc/.ssh/identity type -1
debug1: identity file /homes/rodrigc/.ssh/id_rsa type -1
debug1: identity file /homes/rodrigc/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1 
FreeBSD-20060930
debug1: match: OpenSSH_3.5p1 FreeBSD-20060930 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 FreeBSD-20080901
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-cbc hmac-md5 none
debug1: kex: client-server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'bbuild47.juniper.net' is known and matches the DSA host key.
debug1: Found key in /homes/rodrigc/.ssh/known_hosts:100
debug1: ssh_dss_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
xmalloc: zero size

At this point I cannot log in.  The system I am trying to log into
is: 4.11-RELEASE-p26
Any ideas?

This is a big problem for me, because I have a lot of FreeBSD 4.x
servers that I need to log into.

Thanks.
-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ssh to FreeBSD 4 systems: xmalloc: zero size

2008-09-15 Thread Craig Rodrigues 
On Mon, Sep 15, 2008 at 08:08:38PM +, Craig Rodrigues wrote:
 Hi,
 
 With the latest FreeBSD 7.1 PRE-RELEASE, I am having trouble
 ssh'ing to FreeBSD 4 systems.

 xmalloc: zero size

This looks like the same problem:

https://bugzilla.mindrot.org/show_bug.cgi?id=1496

-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ssh to FreeBSD 4 systems: xmalloc: zero size

2008-09-15 Thread Craig Rodrigues 
Hi,

I can confirm that this patch solves my problem:

https://bugzilla.mindrot.org/attachment.cgi?id=1554

That patch is part of this ssh bug:

https://bugzilla.mindrot.org/show_bug.cgi?id=1496

Can we get this fix into FreeBSD before the 7.1 RELEASE?

Thanks.
--
Craig Rodrigues
[EMAIL PROTECTED]


On Mon, Sep 15, 2008 at 08:08:38PM +, Craig Rodrigues wrote:
 Hi,
 
 With the latest FreeBSD 7.1 PRE-RELEASE, I am having trouble
 ssh'ing to FreeBSD 4 systems.
 
 I am getting this error:
 OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007
 debug1: Applying options for *
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: Connection established.
 debug1: identity file /homes/rodrigc/.ssh/identity type -1
 debug1: identity file /homes/rodrigc/.ssh/id_rsa type -1
 debug1: identity file /homes/rodrigc/.ssh/id_dsa type 2
 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1 
 FreeBSD-20060930
 debug1: match: OpenSSH_3.5p1 FreeBSD-20060930 pat OpenSSH_3.*
 debug1: Enabling compatibility mode for protocol 2.0
 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 FreeBSD-20080901
 debug1: SSH2_MSG_KEXINIT sent
 debug1: SSH2_MSG_KEXINIT received
 debug1: kex: server-client aes128-cbc hmac-md5 none
 debug1: kex: client-server aes128-cbc hmac-md5 none
 debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent
 debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
 debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
 debug1: Host 'bbuild47.juniper.net' is known and matches the DSA host key.
 debug1: Found key in /homes/rodrigc/.ssh/known_hosts:100
 debug1: ssh_dss_verify: signature correct
 debug1: SSH2_MSG_NEWKEYS sent
 debug1: expecting SSH2_MSG_NEWKEYS
 debug1: SSH2_MSG_NEWKEYS received
 debug1: SSH2_MSG_SERVICE_REQUEST sent
 debug1: SSH2_MSG_SERVICE_ACCEPT received
 xmalloc: zero size
 
 At this point I cannot log in.  The system I am trying to log into
 is: 4.11-RELEASE-p26
 Any ideas?
 
 This is a big problem for me, because I have a lot of FreeBSD 4.x
 servers that I need to log into.
 
 Thanks.
 -- 
 Craig Rodrigues
 [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: -o union

2007-10-27 Thread Craig Rodrigues 
On Thu, Oct 25, 2007 at 06:22:26PM +1000, Bruce Evans wrote:
 (1) It is broken for all file systems except ffs and ext2fs, since
 all (?) file systems now use nmount(2) and only these two file
 systems have union in their mount options list.  It is still in
 the global options list in mount/mntopts.h, but this is only used
 with mount(2).  The global options list in mount/mntopts.h has
 many bogus non-global options, and even the global options list
 in kern/vfs_mount.c has some bogus non-global options, but union
 actually is a global options.  ext2fs loves union more than
 ffs -- although its options list is less disordered than ffs's,
 it has enough disorder to have 2 copies of union.
 (2) After fixing (1) by not using nmount(2), following of symlinks works
 strangely for at least devfs:


The long term path is to move to use nmount(2) in place of mount(2) everywhere.
Inside the kernel, when you call mount(2), you eventually call vfs_cmount
(if your file system implements vfs_cmount), which in turn eventually calls
vfs_donmount().  nmount(2) calls vfs_donmount() directly.

If -o union is a mount option that can apply to any file system
(even ones like procfs, tmpfs, unionfs, devfs), then we can add it
to global_opts in vfs_mount.c, so that it will be valid for any
file system.  If it does not make sense to do that, then we can add it to the
file systems where it works.

Right now, -o union is converted to MNT_UNION.
I don't understand enough about MNT_UNION to judge if it is valid
for all file systems, or just UFS and EXT2FS.

When I converted the mount programs for UFS and EXT2FS to nmount(),
I noticed that the old mount(2) based mount programs for these file systems
 specifically allowed -o union for these two file systems, so I added
union to the local options array for these two file systems.

I don't understand enough about MNT_UNION to determine if it belongs
in global_opts or not.

-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD mysql Benchmark on 4BSD/ULE scheduler and i386/amd64

2007-03-13 Thread Craig Rodrigues 
On Tue, Mar 13, 2007 at 09:13:56PM +0100, Martin wrote:
 I use GENERIC kernel file for 6.2
 and GENERIC on 7 and I removed WITNESS 

You did not remove WITNESS in all your configs.
I see this message: 
WARNING: WITNESS option enabled, expect reduced performance.
in the dmesg output of two of your tests.

Can you just publish the exact kernel config in the results table
that you used, to make it easier to figure out your exact configuration,
instead of guessing?


-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

[HEADSUP] New unionfs merged to RELENG_6 (stable)

2007-02-14 Thread Craig Rodrigues 
Hi,

I have merged the new unionfs implementation from
CURRENT to RELENG_6 (stable branch).  This code
was submitted by Daichi GOTO and Masanori OZAWA.
Many, many thanks to GOTO-san and OZAWA-san for their work.

This code solves a lot of crashing problems that the old
unionfs implementation had.

Reports from people running SMP systems would be appreciated.
There probably is some room for performance optimization on SMP systems.

Also, thanks a lot to Kostik Belousov, who recently fixed some deadlock
problems in vfs_lookup.c, which helps a lot with unionfs.
-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 6.2-RELEASE - Fatal trap 12 - nvidia driver ?

2007-02-07 Thread Craig Rodrigues 
On Thu, Feb 01, 2007 at 11:39:33AM +0100, Henri Hennebert wrote:
 I experience Fatal trap 12 when I shutdown if I have run the X server 
 (with nvidia driver 1.0.9746). This crash happen 4/5 of the time. It is 
 in devfs_populate_loop() in devfs.c. I don't have the vmcore anymore :-/.

Hi,

Can you try to the patch to the 9746 driver available at:

   http://www.nvnews.net/vbulletin/showpost.php?p=1143321postcount=27

The full thread is here:
   http://www.nvnews.net/vbulletin/showthread.php?p=1143321#post1143321

I received this information from [EMAIL PROTECTED] which
is the e-mail address for reporting FreeBSD nVidia graphics driver
bugs back to nVidia.
--
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Filesystem hang on 3ware 6.2 system

2007-02-01 Thread Craig Rodrigues 
On Thu, Feb 01, 2007 at 02:24:54PM -0500, Michael R. Wayne wrote:
 As I read the kernel deadlock debugging chapter, I see that it
 operates on core dumps.  Once the machine enters this state, my

You didn't read properly:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html

That section mentions using ddb and the following ddb commands:
ps, show pcpu, show allpcup, show locks, show alllocks, 
show lockedvnods, show alltrace.

It doesn't mention core files.

-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: kernel panic on 6.2-RC2 with GENERIC.

2007-01-07 Thread Craig Rodrigues 
On Fri, Jan 05, 2007 at 06:59:10PM +0200, Nikolay Pavlov wrote:
 Hello folks.
 I have kernel panic on GENERIC kernel while executing postmark.

The sequence of steps that Nikolay used to produce this panic was:

- install benchmarks/postmark from ports

root# postmark
PostMark v1.5 : 3/27/01
pmset number=1
pmset transactions=1
pmset subdirectories=1
pmshow
pmrun

-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: NFS : mount option update is unknown

2006-06-03 Thread Craig Rodrigues 
On Tue, May 30, 2006 at 09:12:21PM +, Arno J. Klaassen wrote:
   mount option update is unknown
   May 31 01:54:18 accuracy mountd[443]: can't delete exports for 
 /users/angora/u4: Invalid argument


Can you update RELENG_6, and rebuild the kernel and world?
I merged some more fixes from CURRENT to RELENG_6.

What type of filesystem is /usrs/angora/u4?
Is it a local UFS filesystem on yoru machine that you are exporting,
or is it something else?

-- 
Craig Rodrigues
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: usb connected lite-on CR writer

2004-10-19 Thread Craig Rodrigues 
On Wed, Oct 06, 2004 at 04:31:36PM -0400, munn wrote:
 How do I mount the disk with mount_msdos?

You should use mount_cd9660 instead.

On FreeBSD 4.x:

mount -t cd9660 /dev/cd0c /mnt

On FreeBSD 5.x:
mount -t cd9660 /dev/cd0 /mnt

-- 
Craig Rodrigues
http://crodrigues.org
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Memory corruption in -STABLE on P4/2GHz

2002-11-17 Thread Craig Rodrigues 
On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote:
 Hi there,
 
 I'm observing very strange memory corruption problems with 2GHz P4
 system running 4.7 (security branch as of today). Under the load
 (make -j20 buildworld) the compiler or make(1) often die with signal
 11. I found in mailing lists that there is similarly looking problem
 with -current, any chances that -stable is affected as well?

I'm seeing similar errors on -current on my AMD K6-2 machine:

CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU)
  Origin = AuthenticAMD  Id = 0x58c  Stepping = 12
  Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
  AMD Features=0x8800SYSCALL,3DNow!
Data TLB: 128 entries, 2-way associative
Instruction TLB: 64 entries, 1-way associative
L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative
L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative
Write Allocate Enable Limit: 384M bytes
Write Allocate 15-16M bytes: Enable

I am seeing make or /usr/libexec/cc1 intermittently coredump with SIG 11 or 
SIG 10 errors when trying to do a buildworld.
I wasn't sure if it was because I had flaky hardware or not.
 
-- 
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message

4.6-STABLE boot fails at Mounting root from ufs:/dev/md0c

2002-07-03 Thread Craig Rodrigues 

Hi,

I downloaded the 4.6-STABLE boot floppies, and tried to install
FreeBSD on my new Winbook N3 laptop.  The specs for the laptop are at:

http://www.winbookcorp.com/support/n3/n3_support.html

The bios is:

PhoenixBIOS 4.0 Release 6.0
Copyright 1985-2000 Phoenix Technologies Ltd.
All Rights Reserved
Keyboard BIOS Rev 180A.ROM
30N3/CY20 BIOS(NB:VIA8603,SB:VIA686B) V1.80A


When I try to boot, the boot screen hangs at:
Mounting root from ufs:/dev/md0c

This problem seems to be identical to PR 30860:
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=30860

One of the solutions in that PR was to set in my BIOS
Assign IRQ to USB.  Unfortunately, my Phoenix BIOS for the Winbook
does not have this option.  Is there any way to debug this?

Just for fun I downloaded the FreeBSD 5.0-DP1 boot floppies, and I
did NOT have this problem, so it seems to be a problem in the 4.6-STABLE
boot sequence.  I don't really want to run CURRENT at this time.

Anyone have any ideas how I can solve this problem with STABLE?

Thanks.

Here are some of the boot messages that I could see before they scrolled
off the screen:

 




===
sa0: unknown card DF@0020 (0x10c00020) at slot 1
orm0: Option ROMs at iomem 0xc-0xcbfff,0xe4000-0xe7fff on isa0
fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0
vga0: Generic ISA VGA at port 0x3c0-03df iomem 0xa000-0xb on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio2: configured irq 4 not in bitmap of probed irqs 0
sio09 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 9250
sio1: configured irq 3 not in bitmap of probed irqs 0
pppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
plip0: PLIP network interface on ppbus0
ad0: 19077MB TOSHIBA MK2018GAP [38760/16/63] at ata0-master UDMA100
acd0: CD-RW TOSHIBA DVD-ROM SD-R2002 at ata1-master using PIO4
Mounting root from ufs:/dev/md0c
( This is where it hangs)
===
-- 
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message