Re: Dell M600 Blade: 6.4 works, 7.x and 8.x fail to boot

[Thierry Herbelot]

Le Saturday 14 November 2009, Peter Beckman a écrit :
[SNIP]
> >>>
> >>> then, one of the first steps would be a the dmesg of both a succeeding
> >>> and a failing kernels (verbose !)
> >>
> >>   I tried the bootonly ISOs for 7.x and 8.x, both amd64 and i386, all of
> >>   which fail to boot on the Dell M600.
> >
> > aha !
> >
> > anyway, even with a CDROM, you can boot *verbose* and note where the boot
> > stops (even if there won't be a serial console, write down the blocking
> > device probe)
>
>   Can you shoot me a link to the docs on how to do this?  I haven't been
>   able to find out how.

speaking from memory : just before the kernel starts, you should have the 
*loader* menu (with the ASCII graphics depicting beastie), where you can 
choose between boot options, and option 5 is boot verbose (like 4 is boot 
single)

TfH
>
> ---
> Peter Beckman  Internet Guy
> beck...@angryox.com http://www.angryox.com/
> ---


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

Re: Dell M600 Blade: 6.4 works, 7.x and 8.x fail to boot

[Thierry Herbelot]

Le Saturday 14 November 2009, Peter Beckman a écrit :
> On Sat, 14 Nov 2009, Thierry Herbelot wrote:
> > Le Friday 13 November 2009, Peter Beckman a écrit :
> >> I've been scratching my head all day on an issue that's been
> >> frustrating.
> >>
> >> I've got two FreeBSD 6.2 instances installed on two M600 blades, and am
> >> moving to a new datacenter with M600 blades and trying to install
> >> FreeBSD 7.2 or 8.  But as others on this list and elsewhere have
> >> mentioned, seemingly without resolution, is that it doesn't work.
> >>
> >>
> >> http://lists.freebsd.org/pipermail/freebsd-hackers/2009-July/029147.html
> >> http://forums.freebsd.org/showthread.php?t=486
> >>
> >> I was able to install 6.4 on it today, but I'm still at a loss as to why
> >> 7.x and even 8.x will not.  Did the architecture change in such a way
> >> that it could no longer support M600 blades?  Did someone leave
> >> something out of the standard ISO kernel?  Am I not doing it right?
> >>
> >> Happy to pass along my dmesg.boot;
> >
> > from the two URLs you provide, it seems that i386 is working (for all
> > FreeBSD versions) and only amd64 is failing : can you confirm this ?
> >
> > then, one of the first steps would be a the dmesg of both a succeeding
> > and a failing kernels (verbose !)
>
>   I tried the bootonly ISOs for 7.x and 8.x, both amd64 and i386, all of
>   which fail to boot on the Dell M600.

aha !

anyway, even with a CDROM, you can boot *verbose* and note where the boot 
stops (even if there won't be a serial console, write down the blocking 
device probe)

TfH

>
>   I was able to boot the bootonly 6.4 ISO, install via the net, and a
> friend suggested I try binary updating.  I have been able to binary update
> to 7.0-RELEASE thus far.  I'm trying to get to 8.0-RC3 via binary update
> now, and will report back.

(a more robust, and slower, way to upgrade is via make buildworld / make 
buildkernel)
>
>   I believe the issue is not with FreeBSD but the bootonly ISO.  It could
>   also be a problem with the other ISOs, I'm not yet sure.

we may get a hint if/when someone sends some verbose dmesg ;-)
>
> > PS : is there any more recent version of the Dell BIOS ?
>
>   According to the iDRAC, the firmware 2.2.3 reported as installed is what
>   Dell reports as the latest version (August 2009).

fine
>
> ---
> Peter Beckman  Internet Guy
> beck...@angryox.com http://www.angryox.com/
> ---
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: Dell M600 Blade: 6.4 works, 7.x and 8.x fail to boot

[Thierry Herbelot]

Le Saturday 14 November 2009, Steven Hartland a écrit :
> Yes I can confirm that.

then, could you please provide the verbose dmesg for both working and 
non-working configurations ?

TfH
>
> Regards
> Steve
> - Original Message -
> From: "Thierry Herbelot" 
>
> > from the two URLs you provide, it seems that i386 is working (for all
> > FreeBSD versions) and only amd64 is failing : can you confirm this ?
>
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: Dell M600 Blade: 6.4 works, 7.x and 8.x fail to boot

[Thierry Herbelot]

Le Friday 13 November 2009, Peter Beckman a écrit :
> I've been scratching my head all day on an issue that's been frustrating.
>
> I've got two FreeBSD 6.2 instances installed on two M600 blades, and am
> moving to a new datacenter with M600 blades and trying to install FreeBSD
> 7.2 or 8.  But as others on this list and elsewhere have mentioned,
> seemingly without resolution, is that it doesn't work.
>
> 
> http://lists.freebsd.org/pipermail/freebsd-hackers/2009-July/029147.html
> http://forums.freebsd.org/showthread.php?t=486
>
> I was able to install 6.4 on it today, but I'm still at a loss as to why
> 7.x and even 8.x will not.  Did the architecture change in such a way that
> it could no longer support M600 blades?  Did someone leave something out of
> the standard ISO kernel?  Am I not doing it right?
>
> Happy to pass along my dmesg.boot;

Hello,

from the two URLs you provide, it seems that i386 is working (for all FreeBSD 
versions) and only amd64 is failing : can you confirm this ?

then, one of the first steps would be a the dmesg of both a succeeding and a 
failing kernels (verbose !)

TfH

PS : is there any more recent version of the Dell BIOS ?

> I'm not sure how to troubleshoot this, 
> or where to look for documentation that says something in the M600 is no
> longer supported, or that what was supported in the M600 was changed that
> now causes FreeBSD to hang instead of booting.
>
> Beckman
> ---
> Peter Beckman  Internet Guy
> beck...@angryox.com http://www.angryox.com/
> ---
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


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

Re: GA-MA780G-UD3H motherboard

[Thierry Herbelot]

Le Tuesday 25 August 2009, Bernt Hansson a écrit :
> Andriy Gapon said the following on 2009-08-25 18:35:
> > I have become to own Gigabyte GA-MA780G-UD3H motherboard:
> > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassV
> >alue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H It is based on
> > AMD 780G + SB700.
> > BTW, CPU I am using is Athlon II X2 250.
> >
> > Sorry for the broadcast announcement, but this is my first AMD-based
> > system in many years, so I eagerly started exploring it and hacking for
> > it.
> >
> > For this reason please expect a number of questions from me as well as
> > some reports and hopefully code related to this motherboard. I am going
> > to post them as follow-ups to this email.
> >
> > Meanwhile, if you interested in any information about this motherboard -
> > data dumps, outputs from tools, etc - please let me know, I will try my
> > best to provide that.
>
> It would be interesting to know if you can have usb devices connected
> and detected during boot. With SB600 you can not.

This maybe the explanation why I have to re-plug the USB mouse each time the 
machine is restarted ;-) (with an SB700)

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

Re: GA-MA780G-UD3H motherboard

[Thierry Herbelot]

Le Tuesday 25 August 2009, Robert Noland a écrit :
> On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote:
> > Le Tuesday 25 August 2009, Sam Fourman Jr. a écrit :
> > > > Meanwhile, if you interested in any information about this
> > > > motherboard - data dumps, outputs from tools, etc - please let me
> > > > know, I will try my best to provide that.
> > >
> > > it would be interesting to see a dmesg as a starting point.
> >
> > here you are ;-)
> >
> > I have plugged a PCI sound board in the machine, but it does seem to be
> > detected (there could be some issue with PCI bus enumeration : I also
> > include a pciconf log)
>
> I'm curious why you would plug in a pci sound card?  You already have
> both a standard hda codec as well as the hda codec for the hdmi port of
> the video.  If you are discovering that it isn't working... set

Initially, this was the issue, before other people sent various howtos around 
the probe of the hdmi hda port (which by the way sounds *much* better than my 
previous cmi board).

Afterwards, the PCI board remained in the machine (leftover from a previous 
box), but it is still *not* seen by the PCI enumeration (I'm a bit too lazy 
to find another spare PCI board and plug it in see what happens : is it also 
ignored by the BIOS/ACPI/whatever and/or the kernel ?).

It seems that it is not either detected by a Linux kernel.

TfH

> hw.snd.default_unit=1 which is typcially your normal analog audio port.
> The hdmi port on radeon chips tends to be enumerated before the normal
> system codecs, so people tend to think that sound isn't working.
>
> robert.
>
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: GA-MA780G-UD3H motherboard

[Thierry Herbelot]

Le Tuesday 25 August 2009, Sam Fourman Jr. a écrit :
> > Meanwhile, if you interested in any information about this motherboard -
> > data dumps, outputs from tools, etc - please let me know, I will try my
> > best to provide that.
>
> it would be interesting to see a dmesg as a starting point.
>
here you are ;-)

I have plugged a PCI sound board in the machine, but it does seem to be 
detected (there could be some issue with PCI bus enumeration : I also include 
a pciconf log)

TfH
>
> Sam Fourman Jr.
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-STABLE #12: Mon Jul  6 09:37:34 CEST 2009
x...@yyy:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3106.64-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x60fb2  Stepping = 2
  
Features=0x178bfbff
  Features2=0x2001
  AMD Features=0xea500800
  AMD Features2=0x11f
  TSC: P-state invariant
  Cores per package: 2
usable memory = 4008947712 (3823 MB)
avail memory  = 3836862464 (3659 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
This module (opensolaris) contains code covered by the
Common Development and Distribution License (CDDL)
see http://opensolaris.org/os/licensing/opensolaris_license/
ioapic0: Changing APIC ID to 2
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, bfce (3) failed
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
acpi_hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vgapci0:  port 0xee00-0xeeff mem 
0xd000-0xdfff,0xfdfe-0xfdfe,0xfde0-0xfdef irq 18 at 
device 5.0 on pci1
hdac0:  mem 0xfdffc000-0xfdff 
irq 19 at device 5.1 on pci1
hdac0: HDA Driver Revision: 20090329_0131
hdac0: [ITHREAD]
pcib2:  irq 18 at device 10.0 on pci0
pci2:  on pcib2
re0:  port 0xde00-0xdeff mem 0xfdaff000-0xfdaf,0xfdae-0xfdae 
irq 18 at device 0.0 on pci2
re0: Using 1 MSI messages
re0: Chip rev. 0x3c00
re0: MAC rev. 0x0040
miibus0:  on re0
rgephy0:  PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
re0: Ethernet address: 00:1f:d0:56:75:23
re0: [FILTER]
atapci0:  port 
0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 
0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 6 ports detected
ata2:  on atapci0
ata2: [ITHREAD]
ata3:  on atapci0
ata3: [ITHREAD]
ata4:  on atapci0
ata4: [ITHREAD]
ata5:  on atapci0
ata5: [ITHREAD]
ata6:  on atapci0
ata6: [ITHREAD]
ata7:  on atapci0
ata7: [ITHREAD]
ohci0:  mem 0xfe02e000-0xfe02efff irq 16 at 
device 18.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0:  on ohci0
usb0: USB revision 1.0
uhub0:  on usb0
uhub0: 3 ports with 3 removable, self powered
ohci1:  mem 0xfe02d000-0xfe02dfff irq 16 at 
device 18.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1:  on ohci1
usb1: USB revision 1.0
uhub1:  on usb1
uhub1: 3 ports with 3 removable, self powered
ehci0:  mem 0xfe02c000-0xfe02c0ff irq 17 at 
device 18.2 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: companion controllers, 3 ports each: usb0 usb1
usb2:  on ehci0
usb2: USB revision 2.0
uhub2:  on usb2
uhub2: 6 ports with 6 removable, self powered
ohci2:  mem 0xfe02b000-0xfe02bfff irq 18 at 
device 19.0 on pci0
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb3: OHCI version 1.0, legacy support
usb3:  on ohci2
usb3: USB revision 1.0
uhub3:  on usb3
uhub3: 3 ports with 3 removable, self powered
ohci3:  mem 0xfe02a000-0xfe02afff irq 18 at 
device 19.1 on pci0
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: SMM does not respond, resetting
usb4:  on ohci3
usb4: USB revision 1.0
uhub4:  on usb4
uhub4: 3 ports with 3 removable, self powered
ehci1:  mem 0xfe029000-0xfe0290ff irq 19 at 
device 19.2 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers,

Re: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl (3) setting `odd' errno's

[Thierry Herbelot]

Le Friday 16 January 2009, Garrett Cooper a écrit :
> On Fri, Jan 16, 2009 at 2:21 AM, Christoph Mallon
>
> #include 
> #include 
> #include 
>
> int
> main()
> {
>
> struct stat sb;
>
> int o_errno;
>
> if (stat("/some/file/that/doesn't/exist", &sb) != 0) {
> o_errno = errno;
> printf("Errno: %d\n", errno);
> printf("%s\n", strerror(o_errno));
> }
>
> return 0;
>
> }
>
with this, it's better on an amd64/ RELENG_7 machine :

% diff -ub badfile.c.ori badfile.c
--- badfile.c.ori   2009-01-16 11:49:44.778991057 +0100
+++ badfile.c   2009-01-16 11:49:03.470465677 +0100
@@ -1,6 +1,7 @@
 #include 
 #include 
 #include 
+#include 

 int
 main()

Cheers

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

Re: FreeBSD 5.4 - filesystem full

[Thierry Herbelot]

Le Wednesday 12 November 2008, Varshavchick Alexander a écrit :
> I have an old enough server with FreeBSD 5.4 which from time to time
> complains about filesystem full. But the problem is that the partition
> in question has about 15G free space and more than 1000 free inodes.
> Then all by itself the error dissapears, only to be repeated several hours
> later. What can it be and where to look? The server runs mainly apache and
> sendmail, nothing special.

Hello,

I saw a full disk because of a runaway background fsck : bg_fsck built some 
image of the disk in the top-level ".snap" directory, which grew and grew and 
grew 

the workaround was to reboot in single-user, then fsck in foreground, and 
finally switch to Zfs (but obviously, only for a Releng7 machine)

TfH
>
> Thanks and regards
>
> 
> Alexander Varshavchick, Metrocom Joint Stock Company
> Phone: (812)718-3322, 718-3115(fax)
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: strange behaviour with /sbin/init and serial console

[Thierry Herbelot]

Le Friday 31 October 2008, Jeremy Chadwick a écrit :
> On Fri, Oct 31, 2008 at 05:46:23PM +0100, Thierry Herbelot wrote:
> > with the following patch on /sbin/init, I have two different behaviours
> > depending on the console type (on a i386/32 PC) :
> > - on a video console, I see the expected two messages,
> > - on a serial console, the messages are not displayed (init silently
> > finishes its job and gets to start /etc/rc and everything)
>
> I thought this was normal behaviour on FreeBSD, but it's very likely I'm
> misunderstanding.  The charts in Section 27.6.4 describe what "level" of
> logging is shown where and at what stage, depending upon which boot
> flags and device settings you use:
>
> http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html

Hello,

I had not taken the time to read this link as thouroughly as should  have 
been.

nevertheless, I think the config is right, as the serial console is selected 
with "-h" in /boot.config (from memory, the machine is at work ...) and all 
*other* expected messages from the kernel ("dmesg") and the rc scripts are 
correctly displayed on respectively the serial and video console.

what struck me is that, from all the startup messages, just the messages 
from /sbin/init are displayed only on the video console

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

strange behaviour with /sbin/init and serial console

[Thierry Herbelot]

Hello,

with the following patch on /sbin/init, I have two different behaviours 
depending on the console type (on a i386/32 PC) :
- on a video console, I see the expected two messages,
- on a serial console, the messages are not displayed (init silently finishes 
its job and gets to start /etc/rc and everything)

I assume that the writev system call is implemented in 
src/sys/kern/tty_cons.c::cnwrite(), but I could not parse the code to find an 
explanation.

any taker ?

TfH

PS : this is initially for a RELENG_6 machine, but the code is quite similar 
under RELENG_7 or Current

--- usr/src/sbin/init/init.c.ori2008-10-31 14:20:48.294794898 +0100
+++ usr/src/sbin/init/init.c2008-10-31 14:12:16.168062031 +0100
@@ -44,6 +44,8 @@
   "$FreeBSD: src/sbin/init/init.c,v 1.60.2.2 2006/07/08 15:34:27 kib Exp $";
 #endif /* not lint */

+#include 
+
 #include 
 #include 
 #include 
@@ -239,6 +241,23 @@
 */
openlog("init", LOG_CONS|LOG_ODELAY, LOG_AUTH);

+   warning("warning after openlog");
+{
+int fd;
+  if ((fd = open("/dev/console", O_WRONLY|O_NONBLOCK, 0)) >= 0) {
+   struct iovec iov[2];
+   struct iovec *v = iov;
+
+   v->iov_base = (void *)"iov direct write test";
+   v->iov_len = 21;
+   ++v;
+   v->iov_base = (void *)"\r\n";
+   v->iov_len = 2;
+   (void)writev(fd, iov, 2);
+   (void)close(fd);
+   }
+
+}
/*
 * Create an initial session.
 */
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: question about sb->st_blksize in src/sys/kern/vfs_vnops.c

[Thierry Herbelot]

Le Saturday 25 October 2008, Bruce Evans a écrit :
> On Fri, 24 Oct 2008, Thierry Herbelot wrote:
> > the [SUBJ] file contains the following extract (around line 705) :
> >
> > * Default to PAGE_SIZE after much discussion.
> > * XXX: min(PAGE_SIZE, vp->v_bufobj.bo_bsize) may be more correct.
> > */
> >
> >sb->st_blksize = PAGE_SIZE;
> >
> > which arrived around four years ago, with revision 1.211 (see
> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_vnops.c.diff?r1=1.
> >210;r2=1.211;f=h)
>
> Indeed, this was completely broken long ago (in 1.211).  Before then, and
> after 1.128, some cases worked as intended if not perfectly:
> - regular files: file systems still set va_blksize to their idea of the
>best i/o size (normally to the file system block size, which is
>normally larger than PAGE_SIZE and probably better in all cases) and
>this was used here.  However, for regular files, the fs block size
>and the application's i/o size are almost irrelevant in most cases
>due to vfs clustering.  Most large i/o's are done physically with
>the cluster size (which due to a related bug suite ends up being
>hard-coded to MAXPHYS (128K) at a minor cost when this is different
>from the best size).
> - disk files: non-broken device drivers set si_iosize_best to their idea
>of the best i/o size (normally to the max i/o size, which is normally
>better than PAGE_SIZE) and this was used here.  The bogus default
>of BLKDEV_IOSIZE was used for broken drivers (this is bogus because it
>was for the buffer cache implementation for block devices which no
>longer exist and was too small for them anyway).
> - non-disk character-special files: the default of PAGE_SIZE was used.
>The comment about defaulting to PAGE_SIZE was added in 1.128 and is
>mainly for this case.  Now the comment is nonsense since the value is
>fixed, not a default.
> - other file types (fifos, pipes, sockets, ...): these got the default of
>PAGE_SIZE too.
>
> In rev.1.1, st_blksize was set to va_blksize in all cases.  So file systems
> were supposed to set va_blksize reasonably in all cases, but this is not
> easy and they did nothing good except for regular files.

agreed, anyway the comment by phk about using ioctl(DIOCGSECTORSIZE) applies.
>
> Versions between 1.2 and 1.127 did weird things like defaulting to DFLTPHYS
> (64K) for most cdevs but using a small size like BLKDEV_IOSIZE (2K) for
> disks. This gave nonsense like 64K buffers for slow tty devices (keyboards)
> and 2K buffers for fast disks.  At least for programs that trust st_blksize
> o be reasonable.  Fortunately, st_blsize is rarely used...
>
> > the net effect of this change is to decrease the block buffer size used
> > in libc/stdio from 16 kbytes (derived from the underlying ufs partition)
> > to PAGE_SIZE ==4 kbytes (fixed value), and consequently the I/O bandwidth
> > is lowered (this is on a slow Flash).
>
> ... except it is used by stdio.  (Another mess here is that stdio mostly
> doesn't use its own BUFSIZ.  It trusts st_blksize if fstat() to determine

This is indeed what I saw, meandering between the libc and the vfs part of the 
kernel.

In fact, I was essentially wondering if st_blksize was used *elsewhere*, and 
bumping the value could break some memory allocation ...

> st_blksize works.  Of course, the existence of BUFSIZ is a related
> historical mistake -- no fixed size can work best for all cases.  But
> when BUFSIZ is used, it is an even worse default than PAGE_SIZE.)

(as it is even smaller ?)
>
> It's interesting that you can see the difference.  Clustering is especially
> good for hiding slowness on slow devices.  Maybe you are using a
> configuration that makes clustering ineffective.  Mounting the file system
> with -o sync or equivalently, doing a sync after every (too-small) write
> would do it. Otherwise, writes are normally delated until the next cluster
> boundary.

My use case is for small (buffered) writes to a file between 4 kbytes and 16 
16 kbytes.

For example, writing a 16-kbyte file with a st_blksize of 4k is twice as slow 
as with 16k (220 ms compared to 110). The penalty is less for 8k-byte (105 ms 
vs 66).
>
> > I have patched the kernel with a larger, fixed value (simply 4*PAGE_SIZE,
> > to revert to the block size previoulsly used), and the kernel and world
> > seem to be running fine.
> >
> > Seeing the XXX coment above, I'm a bit worried about keeping this new
> > st_blksize value.
> >
> > are there any drawbacks with running with this bigger buffer size value ?
>
> Mostly it doesn't matter, since buffering (clustering) hides the
>

question about sb->st_blksize in src/sys/kern/vfs_vnops.c

[Thierry Herbelot]

Hello,

the [SUBJ] file contains the following extract (around line 705) :

 * Default to PAGE_SIZE after much discussion.
 * XXX: min(PAGE_SIZE, vp->v_bufobj.bo_bsize) may be more correct.
 */

sb->st_blksize = PAGE_SIZE;

which arrived around four years ago, with revision 1.211 (see 
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_vnops.c.diff?r1=1.210;r2=1.211;f=h)

the net effect of this change is to decrease the block buffer size used in 
libc/stdio from 16 kbytes (derived from the underlying ufs partition) to 
PAGE_SIZE ==4 kbytes (fixed value), and consequently the I/O bandwidth is 
lowered (this is on a slow Flash).

I have patched the kernel with a larger, fixed value (simply 4*PAGE_SIZE, to 
revert to the block size previoulsly used), and the kernel and world seem to 
be running fine.

Seeing the XXX coment above, I'm a bit worried about keeping this new 
st_blksize value.

are there any drawbacks with running with this bigger buffer size value ?

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

Re: NFS locking from a qemu machine ?

[Thierry Herbelot]

Le Saturday 19 July 2008, Thierry Herbelot a écrit :
> Hello,
>
> I'm trying to use NFS locking from an NFS client running in a qemu virtual
> PC to an NFS server running on the host machine, but with no success so far
> :
>
> configuration for the host PC (server) :
> operating system : FreeBSD 7.0-Stable
>
> % cat /etc/exports
> /shared/  127.0.0.1
>
> and in /etc/rc.conf :
> nfs_server_enable="YES"
> weak_mountd_authentication="YES" # Allow non-root mount requests to be
> served. rpcbind_enable="YES"# Run the portmapper service
> (YES/NO). rpc_lockd_enable="YES"  # Run NFS rpc.lockd needed for
> client/server. rpc_statd_enable="YES"  # Run NFS rpc.statd needed
> for client/server.
>
> configuration for the qemu machine (client) :
> operating system : FreeBSD 7.0-Stable
>
> in /etc/fstab :
> 10.0.2.2:/shared /shared nfs rw 0 0
>
> in /etc/rc.conf :
> nfs_client_enable="YES" # This host is an NFS client (or NO).
> rpcbind_enable="YES"# Run the portmapper service (YES/NO).
> rpc_lockd_enable="YES"  # Run NFS rpc.lockd needed for
> client/server. rpc_statd_enable="YES"  # Run NFS rpc.statd needed
> for client/server.
>
>
> I'm using tools/regression/file/flock to check the correct file locking :
> $ ./flock ../../shared
>
> and the client machine seems locked
>
> the ethernet traffic between the client and the server when the client is
> blocked is the following :
>
> (the "tunnel" port is the one used by the lockmanager according to rpcinfo)

this is most likely due to misconfiguration, as the nat-ed configuration used 
for the qemu client does not allow back communication from the server lockd 
to the client rpcbind.

TfH

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

NFS locking from a qemu machine ?

[Thierry Herbelot]

Hello,

I'm trying to use NFS locking from an NFS client running in a qemu virtual PC 
to an NFS server running on the host machine, but with no success so far :

configuration for the host PC (server) :
operating system : FreeBSD 7.0-Stable

% cat /etc/exports
/shared/  127.0.0.1

and in /etc/rc.conf :
nfs_server_enable="YES"
weak_mountd_authentication="YES" # Allow non-root mount requests to be served.
rpcbind_enable="YES"# Run the portmapper service (YES/NO).
rpc_lockd_enable="YES"  # Run NFS rpc.lockd needed for client/server.
rpc_statd_enable="YES"  # Run NFS rpc.statd needed for client/server.

configuration for the qemu machine (client) :
operating system : FreeBSD 7.0-Stable

in /etc/fstab :
10.0.2.2:/shared /shared nfs rw 0 0

in /etc/rc.conf :
nfs_client_enable="YES" # This host is an NFS client (or NO).
rpcbind_enable="YES"# Run the portmapper service (YES/NO).
rpc_lockd_enable="YES"  # Run NFS rpc.lockd needed for client/server.
rpc_statd_enable="YES"  # Run NFS rpc.statd needed for client/server.


I'm using tools/regression/file/flock to check the correct file locking :
$ ./flock ../../shared

and the client machine seems locked

the ethernet traffic between the client and the server when the client is 
blocked is the following :

(the "tunnel" port is the one used by the lockmanager according to rpcinfo)

16:54:47.907919 IP (tos 0x0, ttl 64, id 48249, offset 0, flags [none], proto 
UDP (17), length 84) localhost.53807 > localhost.sunrpc: [udp sum ok] UDP, 
length 56
16:54:47.908030 IP (tos 0x0, ttl 64, id 48250, offset 0, flags [none], proto 
UDP (17), length 56) localhost.sunrpc > localhost.53807: [udp sum ok] UDP, 
length 28
16:54:47.909791 IP (tos 0x0, ttl 64, id 48251, offset 0, flags [none], proto 
UDP (17), length 204) localhost.61180 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:54:47.909834 IP (tos 0x0, ttl 64, id 48252, offset 0, flags [none], proto 
UDP (17), length 92) localhost.790 > localhost.sunrpc: [udp sum ok] UDP, 
length 64
16:54:47.909932 IP (tos 0x0, ttl 64, id 48253, offset 0, flags [none], proto 
UDP (17), length 72) localhost.sunrpc > localhost.790: [udp sum ok] UDP, 
length 44
16:54:47.909956 IP (tos 0x0, ttl 64, id 48254, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum ok] UDP, 
length 112
16:55:27.490768 IP (tos 0x0, ttl 64, id 48255, offset 0, flags [none], proto 
UDP (17), length 204) localhost.61180 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:55:27.490814 IP (tos 0x0, ttl 64, id 48256, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum ok] UDP, 
length 112
16:56:07.069067 IP (tos 0x0, ttl 64, id 48257, offset 0, flags [none], proto 
UDP (17), length 204) localhost.61180 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:56:07.069110 IP (tos 0x0, ttl 64, id 48258, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum ok] UDP, 
length 112
16:56:46.683998 IP (tos 0x0, ttl 64, id 48276, offset 0, flags [none], proto 
UDP (17), length 204) localhost.61180 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:56:46.684042 IP (tos 0x0, ttl 64, id 48277, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum ok] UDP, 
length 112
16:57:26.375646 IP (tos 0x0, ttl 64, id 48281, offset 0, flags [none], proto 
UDP (17), length 84) localhost.50653 > localhost.sunrpc: [udp sum ok] UDP, 
length 56
16:57:26.375758 IP (tos 0x0, ttl 64, id 48282, offset 0, flags [none], proto 
UDP (17), length 56) localhost.sunrpc > localhost.50653: [udp sum ok] UDP, 
length 28
16:57:26.376715 IP (tos 0x0, ttl 64, id 48283, offset 0, flags [none], proto 
UDP (17), length 204) localhost.63595 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:57:26.376755 IP (tos 0x0, ttl 64, id 48284, offset 0, flags [none], proto 
UDP (17), length 92) localhost.790 > localhost.sunrpc: [udp sum ok] UDP, 
length 64
16:57:26.376851 IP (tos 0x0, ttl 64, id 48285, offset 0, flags [none], proto 
UDP (17), length 72) localhost.sunrpc > localhost.790: [udp sum ok] UDP, 
length 44
16:57:26.376874 IP (tos 0x0, ttl 64, id 48286, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum ok] UDP, 
length 112
16:58:06.271603 IP (tos 0x0, ttl 64, id 48297, offset 0, flags [none], proto 
UDP (17), length 204) localhost.63595 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:58:06.271647 IP (tos 0x0, ttl 64, id 48298, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum ok] UDP, 
length 112
16:58:46.178361 IP (tos 0x0, ttl 64, id 48301, offset 0, flags [none], proto 
UDP (17), length 204) localhost.63595 > localhost.tunnel: [udp sum ok] UDP, 
length 176
16:58:46.178409 IP (tos 0x0, ttl 64, id 48302, offset 0, flags [none], proto 
UDP (17), length 140) localhost.790 > localhost.tunnel: [udp sum 

Re: 3D for AMD64 (was Re: Lack of Flash support is no longer acceptable. Bounty established...)

[Thierry Herbelot]

Le Wednesday 25 June 2008, Ben Kaduk a écrit :
> On Tue, Jun 24, 2008 at 6:06 PM, Thierry Herbelot <[EMAIL PROTECTED]> 
wrote:
> > is there any hope for having the newly open-sourced radeon/radeon-hd AMD
> > drivers (and the related 3D acceleration) to work under FreeBSD-AMD64 ?
>
> Well, I'm using radeonhd right now on a
> [EMAIL PROTECTED] /usr/src/sys/contrib/dev/ath/public]$ uname -a
> FreeBSD periphrasis.mit.edu 7.0-STABLE FreeBSD 7.0-STABLE #4: Wed May
> 14 00:27:26 EDT 2008
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PERIPHRASIS  amd64

good news !
>
> I don't think I have anything that uses 3d installed at the moment, but
> the 2d seems like it's getting accelerated (non-accelerated dual-monitors
> can be painfully slow).

what are the details for your machine ? (graphics board make, motherboard 
chipset etc)

I was thinking of buying a new machine with AMD 780G or 790GX chipsets, whose 
integrated graphics board is supposed to be driven by radeonhd.

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

3D for AMD64 (was Re: Lack of Flash support is no longer acceptable. Bounty established...)

[Thierry Herbelot]

[CC trimmed]

Le Tuesday 24 June 2008, Garrett Cooper a écrit :
> On Tue, Jun 24, 2008 at 8:55 AM, Scott T. Hildreth
>
[SNIP]
>
> (not designed to be troll-bait, just my personal opinion on the matter
> -- don't comment on it please) FWIW, Personally I don't think that
> Flash support is as critical as getting working x64 compatible OpenGL
> enabled video drivers, but then again my opinion differs from your's
> most likely.

is there any hope for having the newly open-sourced radeon/radeon-hd AMD 
drivers (and the related 3D acceleration) to work under FreeBSD-AMD64 ?

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

Re: FreeBSD on non-fpu device

[Thierry Herbelot]

Le Sunday 20 January 2008, Peter Jeremy a écrit :
> On Sun, Jan 20, 2008 at 02:33:14AM +0200, Heikki Suonsivu wrote:
> >Why anyone would be interested?  The eBOX 2300SX cpu is a SoC device,
> > which is by far the lowest power consumption I have seen, and this is
> > probably cheapest computer on the market, still suitable for number of
> > applications. While it is not exactly a speed daemon, it works well
> > enough for all kinds of mp3-playing, small servers and control
> > applications.
>
> I very much doubt MP3 playing is going to work without an FPU. 

mad is a good (integer-only) candidate for MP3 rendering with a slow CPU

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

Re: AMD64 depenguinator?

[Thierry Herbelot]

Le Friday 07 December 2007, Stanislaw Halik a écrit :
> Heya,
>
> I'd like to use depenguinator
>  to get rid of Linux on my
> dedicated servers. This one only works for IA-32 and my machines are
> mostly AMD64.
>
> Could you please share an AMD64 depenguinator so I won't have to either
> stick with Linux or change my dedicated server provider?
>
> TIA,
> -sh

Hello,

you can always use the ia32 depenguinator to install an AMD64 server by using 
an intermediate ia32 FreeBSD partition :
1/ install depenguinator in the linux swap
2/ reboot into the ia32 FreeBSD installer
3/ partition your disk with a main and *one more* BIOS partition (around 
200MB - see end of post)
4/ install a minimal i386 system in the supplemental partition
5/ reboot into the i386 minimal partition
6/ disklabel the main partition
7/ install the AMD64 binaries into the main partition
8/ reboot and switch to the AMD64 partition

there you are ! a full amd64 system is available ;-)

TfH

PS : disk space needed for a minimal 6.3 i386 installation :
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/ad0s1a116M 38M 69M35%/
/dev/ad0s1d 58M 12K 53M 0%/tmp
/dev/ad0s1e 58M368K 53M 1%/var
/dev/ad0s1f646M103M491M17%/usr
PS2 : new installation in the main partition (ad0s1)
# newfs -U /dev/ad0s1f
# newfs -U /dev/ad0s1e
# newfs -U /dev/ad0s1d
# newfs /dev/ad0s1a
# mount /dev/ad0s1a /mnt
# mkdir /mnt/var
# mkdir /mnt/tmp
# mkdir /mnt/usr
# mount /dev/ad0s1d /mnt/tmp
# mount /dev/ad0s1e /mnt/var
# mount /dev/ad0s1f /mnt/usr

# cat base/base.?? | tar --unlink -xpzf - -C /mnt
# cat kernels/generic.?? | tar --unlink -xpzf - -C /mnt/boot
# rmdir /mnt/boot/kernel
# mv /mnt/boot/GENERIC/ /mnt/boot/kernel

(adjust configuration files and reboot)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to write a raw socket server using UDP

[Thierry Herbelot]

Le Tuesday 27 November 2007, sourav das a écrit :
> hello all,
>
>  i m a new comer. i wrote a raw socket client
> using setsockopt (sock, IPPROTO_IP. IPHDRINCL, )using UDP. ihave
> followed MS_Press network programming . it is showing 19 bytes sent

is this the best reference you found ? a better text is "Unix network 
programming" by Stevens.

the canonical program using raw socket is ping, and you can find its source in 
the FreeBSD src tree

Happy reading

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

Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround.

[Thierry Herbelot]

Le Tuesday 20 November 2007, Ari Suutari a écrit :

> I have Promise TX2 (PDC20575). It didn't work with 7.0 betas
> before, but with this patch things run as well as they did
> on 6.x.
>
>  Ari S.

Hello,

Has anyone an idea why the Promise controllers seemed to work correctly under 
6.x, then have issues with 7.0 ? (more precisely : was the existing bug not 
triggered by the 6.x kernel ?)

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

Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround.

[Thierry Herbelot]

Le Monday 19 November 2007, Søren Schmidt a écrit :
> Hi All!
>
> I'd like to get the final verdict of the attached patch and if it fixes
> the problem or not.
>
> Please test and report, its a bit urgent if it need to get into R7 :)
>
>
> -Søren

Hello SoS,

From what I read, it seems that the last promise-fix3 patch is the same as the 
previous promise-fix2, except a cosmetic change.

Then, I'd say go for it as I was happy with promise_fix2.

Thanks

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

Re: installing fbsd from foreign system

[Thierry Herbelot]

Le Sunday 28 January 2007 16:22, Oliver Fromme a écrit :
> Another possibility is to prepare a boot image, i.e. a file
> containing boot sector and a UFS root partition with
> wverything needed for bootstrapping (/boot/loader etc.,
> kernel, base system).  It doesn't have to cover the whole
> disk, it should be just large enough for a base system and
> some support software.  It should contain a script which
> configures the rest of the disk when it's booted (e.g.
> set up remaining disk space, fetch packages from the net,
> whatever).
>
> >From within your Linux deployment process, simply copy
>
> the image to the beginning of the hard disk, then reboot.
>

Oone good *starting point* is the depenguinator 
(http://www.daemonology.net/depenguinator/), which I used some time ago.

There are rough edges, but at least, it gives a way to convert a PC running 
some version of Linux to FreeBSD. (in my experience, I had to resort to 
manual tweakings to get the final BSD to run).

TfH

-- 
Internet users, on the other hand, are perhaps not dealt
with harshly enough; ultimately, the only way to secure the
Internet is to ensure that these users secure their systems.
Harvard Law Review, june06 ("immunizing the internet")
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

High-speed transfers

[Thierry Herbelot]

Le Saturday 1 July 2006 15:31, Hans Petter Selasky a écrit :
>
> Yes, but don't forget high-speed USB transfers. They require larger
> buffers. For example 1024 bytes for ULPT is too little. The interrupt rate
> will be so high, that it is unrealistic to transfer 20MB/s using 1024 byte
> interrupts. My rewritten ULPT now uses "2*(1<<17)" buffers.
>

Hello,

I wonder what kind of speed you are getting : I would like to see improvements 
for reads (and writes) on standard endpoints, without having to resort to 
writing specific drivers (using ugen on the standard FreeBSD USB stack).

One goal would be to achieve something like 25 to 30 Mbytes/s, sustained, 
(finally getting to some interesting fraction of the peak USB2 data rate).

TfH

PS : from experience, 300Mbps can be sustained on a decent PC, using for 
example Suse 10.1 (but don't try with an ATI southbridge : they suck)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: setting up a serial console..

[Thierry Herbelot]

Le Thursday 25 May 2006 17:16, OxY a écrit :
> hi!
>
> i have a simple question, but i didn't found the answer.
>
> after i set console=comconsole in the /boot/loader.conf
> and rebooted every output has been sent to the serial console,
> it's normal...

in /boot/defaults/loader.conf you will find the following line :
#console="vidconsole"   # A comma separated list of console(s)

you can have both a serial console and a video console by setting :
console="vidconsole,comconsole"

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

Re: NetBSD disk backup over network

[Thierry Herbelot]

Le Tuesday 7 March 2006 15:46, Dag-Erling Smørgrav a écrit :
> Ashley Moran <[EMAIL PROTECTED]> writes:
> > I just saw this slashdotted article:
> > http://ezine.daemonnews.org/200603/dermouse.html
> >
> > Just to satisfy my curiosity, is it the sort of thing that can be
> > implemented as a GEOM layer?  The idea is bloody clever but sounds
> > like a bit of a hack right now.

It's just bad that the FreeBSD champion is (was ?) Yahoo and not Google, as 
Google seems to be soon offering a large online storage (see 
http://today.reuters.co.uk/news/NewsArticle.aspx?type=internetNews&storyID=2006-03-07T080717Z_01_N07296137_RTRIDST_0_OUKIN-UK-GOOGLE-STORAGE.XML)

An enterprising hacker could create a new geom class to build a mirror with 
the local disk and the new google remote disk.

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

Promise FastTrak RAID 5 support ?

[Thierry Herbelot]

Hello,

I've been googling for some time and I can't seem to find out whether the ata 
subsystem of FreeBSD supports the RAID5 feature of the Promise boards.

Two boards seem interesting : (by Promise)   FastTrak S150 SX4-M and   
FastTrak SX4100 (I haven't exactly seen the differences, though)

from the ATA mkIII update commit log, it seems that the RAID support for 
Promises is fairly good, but even after a glimpse at the ata-raid src in 
cvsweb, I'm not sure of anything.

Has any one a hint on a cost-effective, FreeBSD-supported  RAID-5 SATA disk 
controller ?

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

Re: Xen dom0 support

[Thierry Herbelot]

Le Tuesday 22 November 2005 23:17, Darcy Buskermolen a écrit :
> Hello,
>
> I know Kip Macy was working on Xen support for FreeBSD.  How is FreeBSD
> Dom0 coming along as well as SMP support ?

Hello,

With the instructions on Kip's site or the patch included with the xen 
sources, it's possible to build a functioning XenU kernel. (I have run it 
under NetBSD/Xen0 and Debian/Linux2.6/Xen0).

One limitation is that all patches have developed for 5.3-Release, and have 
not been recently updated.

I have found the FreeBSD/Xen0 very unstable : I had crashes under even 
moderate load, and I did not see how to add debugging DDB support (but I did 
not look very far)

Too bad : even just a Xen0 support would be fine (but Xen3 should make it 
possible to run an "untouched" FreeeBSD kernel on a DomU virtual machine)

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

Grub capabilities (Re: Multiple Bootable FreeBSD partitions?)

[Thierry Herbelot]

Le Monday 19 July 2004 22:43, Eitarou Kamo a écrit :

> Me too. WinXP, RedHat, FreeBSD-4.10 and Solaris8 live
> in my laptop. And RedHat has 2 kernels bootable. So I have
> 5 OSes bootable. If 2 linux live in dos basic partition each other
> and each linux create extend partition, is it possible to create
> 10 bootable partition with grub?

one very good point of grub is that it allows booting from a "logical" 
partition inside an "extended" partition : the number of bootable OSes is 
therefore un-limited, as log as they can live in an extended partition (that 
is, none of the BSD's for now ; you may also have for example up to 3x6=18 
versions of FreeBSD alongside your numerous versions of Linux or Zin$$)

TfH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Multiple Bootable FreeBSD partitions?

[Thierry Herbelot]

Hello,

I've got a grub.conf example with 5 OS'es at :
http://therbelot.free.fr/Install_Linux/grub.conf

(including 2 FreeBSD's in the same slice/"primary partition")

Happy reading,

TfH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: problems mounting firewire HDD

[Thierry Herbelot]

Le Thursday 08 April 2004 02:01, Tadimeti Keshav a écrit :
> I am running x86, not sparc.
> Any solns?
> Thx in advance...

try using fdisk on da0 : fdisk will tell you if there are any partition on 
your disk

TfH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: problems mounting firewire HDD

[Thierry Herbelot]

Le Wednesday 07 April 2004 20:02, Tadimeti Keshav a écrit :
> Hi all,
> I am doing the following to mount a 10GB Quantum
> Fireball FAT32 HDD via firewire as root.
> FreeBSD 5.2.1, lucent F322/323 (firewire card). This
> setup works under Windows 2000.
>
> #camcontrol devlist -v
> #camcontrol start da0
> #mount_msdosfs /dev/da0 /bck
> mount_msdosfs: /dev/da0: operation not permitted.

you can try : 
mount_msdosfs /dev/da0s1 /bck
(mount the 1st partition)

TfH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: implications of SMP kernel on UP

[Thierry Herbelot]

Le Thursday 01 April 2004 09:10, Bjoern A. Zeeb a écrit :
> Hi,
>
> what are the implications on running an SMP enabled kernel on a UP
> machine ?
>
> I first thought of things like:
> - performence (most likely not worth the discussion ?)

I got an improvement with a factor of ten between an SMP and a UP kernel on a 
HTT-enabled P4/2,6GHz/800MHz FSB on network transfers (with gigabit Ethernet 
boards : SMP gives about 6MB/s for FTP transfer rate, and UP gives up to 
75MB/s)

So : as long as the network stack is not fully locked (this is coming - 
perhaps for 5.3), a server should definitely run a UP kernel.

TfH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Keeping an eye on the text console while in X11 ?

[Thierry Herbelot]

Hello,

[long message]

I'm chasing strange freezes on my work PC, with a recent -Current (5.2-SNAP 
from 01/30). The machine is NEC PeeCee, using a Gigabyte MB, a SIS chipset 
and a P4-1,8GHz (dmesg to follow). The kernel is just GENERIC, with all 
debugging options commented out.

sometimes (still, around once a day), when the machine starts swapping, it 
just freezes (it's possible sometimes to switch to a text virtual console and 
see the system messages), and it may unfreeze (or not). As the BIOS enables 
ACPI, it's even possible to shutdown gracefully from the power button.
I have tried to start with all "defensive" options in /boot/loader.conf :
hint.acpi.0.disabled=1
loader.acpi_disabled_by_user=1
hw.ata.ata_dma=0
hw.ata.atapi_dma=0
hw.ata.wc=0
hint.apic.0.disabled=1

and the freezes still happen.

I will try to swap the disk (I did not see any ATA error message, like when 
the driver cannot read one disk sector - SMART is enabled on this disk, and 
the BIOS does not see any SMART error count)

I have added a second (PCI) graphics card to the AGP board, and I'v setup the 
BIOS to use the PCI board as the console, the AGP board is only declared 
in /etc/X11/XF86Config. 
I wanted to see the vty0 messages while being under X11, but it seems as if 
the switch to X11 freezes the vty0, and the display is not refreshed (for 
example, if I leave a "top" in vty0, the display stays frozen with the last 
display).

So [at long last] : is there a way to still have the display of vty0 refreshed 
on the PCI board, while X11 is displayed on the AGP board ?
I suspect the keyboard is the blocking factor here (being exclusively attached 
to vty0 or X11) ?

in the meantime, I'll try to keep an eye on xconsole, hoping all messages end 
up in the window.

TfH

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

ICH5 + SATA + Seagate Barracuda 7200.7 ?

[Thierry Herbelot]

Hello,

I'm in the process of selecting new computers, and I'm tempted by an 
ASUS P4P800, with Seagate SATA disks.

After googling a bit, it seems that the ICH5 is indeed supported in SATA 
mode from the 4.9-Release (perhaps also 5.1 ?)
(at least the chip is correctly identified by
)

The driver seems to be a bit fragile, if this message is to be relied on :


Under Linux, the SATA support also is very recent :

it should be included in 2.4.23

So the question is : 
is there some actual, positive, experience in using the above combination, and 
with which stability ?

Cheers

TfH

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

Re: failed freebsd 5.1 install

[Thierry Herbelot]

Le Wednesday 09 July 2003 07:56, Greg Kutzbach a écrit :
> Motherboard
> Intel® VS440FX Motherboard
> http://www.intel.com/support/motherboards/desktop/VS440FX/
> 84MB RAM
> IBM 40GP Hard drive
> removed all PCI cards except video
> Running Matrox MGA 4MB video
> Pentium Pro 200
> IDE Generic CD Rom (secondary master)
>
> Error**

Hello,

as 5.1 is still a development release, such mishaps can happen.

does 4.8-Release run correctly on this ancient machine ?

If yes, it would be very interesting to get the dmesg of a verbose boot.

TfH

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

strange 5.1 fxp behaviour [was Re: "jumpstation" configuration]

[Thierry Herbelot]

[I've seen your previous answer, but I still will describe my setup]
[problems netbooting machines between fxp and em NICs]

Hello,

I am too seeing problems jumpstarting a machine (client) using a fxp NIC from 
a server (runnning 5.1-Rel) using an em NIC : the em NIC is wired down as 
100baseTX full-duplex, but the 5.1-Release kernel seems unable to see it and 
tries to use a half-duplex setting (this surprisingly works when loading the 
install bits via ftp, with a rate of around 44kB/s, but fails completely when 
NFS is selected as install media).

Everything works finer after switching virtual consoles on the client and 
"ifconfig'ing" the fxp1 as full-duplex, from the holographic shell. What is 
even more startling is that the same fxp1 is correctly set up as full duplex 
with the 4.8-RELEASE install kernel (from the same boot server, with the same 
setup for its NIC : I've installed two tftpboot directories so as to select 
which release is loaded via PXE).

On monday , I'll try to wire the server em NIC as half-duplex to see wether 
the client fxp1 has a better throughput (afterwards, I'll try and look for 
differences in the 4.8 and 5.1 fxp drivers).

Happy hacking

TfH

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

Re: make world + kernel with gcc 3.2?

[Thierry Herbelot]

Le Saturday 15 March 2003 18:14, Avleen Vig a écrit :
> I don't expect HUGE problems with making world, but am I asking for
> trouble if I make a new kernel with GCC3.2?

good luck to you !

just have a look at the differences in the source code between current and 
stable to enable the compilation of current with gcc3 (FriBi -Stable will not 
compile with anything other than gcc 2.95)

TfH

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

Re: Realtek

[Thierry Herbelot]

Le Friday 07 March 2003 18:16, Doug Ambrisko a écrit :
[SNIP]
> everything at once.  This illustrated the HW issue with the new D-Link 4
> port card since none of their "supported" drivers and OSes could get over
> 20Mbs.  We had 100FDX links to each client and a Gig link to the server.
> FreeBSD could peak to 40Mbs if I recall right and we were told FreeBSD
> must be broken even though it was faster then their supported OSes
> (Windows < 1Mbs)!  To be honest I did fix a bunch of bugs in the FreeBSD
> driver.
>
[re-SNIP]
>
> Our bigger issue is bus performance on a 32bit/33Mhz bus with 3, 4-port
> cards.

and the avid reader asks : so, now, what NIC are you really using ? (I too 
have used with great pleasure quite a bunch of DLink-DFE-570), and I was 
leaning towards using the newer DFE-580 4-port on another project ...)

any suggestions (with benchmark results ?) heartily welcome !

TfH
>
> To date we haven't had any trouble with them and we've shipped a bunch.

then, what are these "them" ?

>
> Doug A.
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message


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

Re: IPC and jail.

[Thierry Herbelot]

Hello,

PostGreSQL (see the ports) is one (big) program which is difficult to set up 
in a pure jail, as it uses shared memory : it could be a good candidate for 
your test.

you may want to have first a patch against -Current, as this is the "One True 
Way" to introduce a new functionality to FreeBSD (futhermore, -Current is 
quite stable, these days)

TfH

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

Re: Another EPIA M 9000 update (was Re: More compartive power/performance results (was Re: Lower power SMP boxes?))

[Thierry Herbelot]

Le Monday 10 February 2003 21:51, Joe O a écrit :
> If the linux XFree86 4.x driver was correctly written you should be able
> to dump it into /usr/X11R6/lib/modules/drivers and use it.
>
> One of the goals with XFree86 4.x was that the X server modules be OS
> independent.
>

Indeed, that's how I got XVideo working on my neomagic : this OS-independant 
dynamic module linking is really a good thing

Tfh

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

Re: Another EPIA M 9000 update

[Thierry Herbelot]

Hello, Matt,

with your copious free time and this new baby, what would you think of porting 
over the ehci driver from NetBSD over to FreeBSD (this will enable USB2.0)

ISTR a call for help (must have been by Joe K.)

TfH

PS : I confess : this is a shameless plug to get USB2.0 working on my own WS

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

Re: cdrom upgrade of existing installation, defining a swap part

[Thierry Herbelot]

Le Friday 10 January 2003 20:46, John Baldwin a écrit :
[SNIP]
> >
> > I now want to install 5.0-DP2 on ad0s3e so that I can test it for a
> > while. I have the cdrom and have created boot floppies. I've booted the
> > floppy and selected "upgrade existing installation", but it won't let me
> > define the current ad0s3b partition as swap in the disklabel editor. It

one work-around is to delete the ad0s3b partition in sysinstall, then 
immediately create another swap partition, which uses the newly free space.

TfH

[SNIP]

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

Re: problems with a firewire external hard disk [long]

[Thierry Herbelot]

Le Wednesday 04 December 2002 23:41, Julian Elischer a écrit :
> On Wed, 4 Dec 2002, Thierry Herbelot wrote:
> > Hello,
> >
> > I can't seem to use my new external firewire hard disk : (this is
> > with 5.0-DP2, there are the same kinds of symptoms under 4.7-Stable)
> >
> > My main question is to know where the problems are : is the hard
> > disk dead ?  is the firewire/ATA bridge fried ? are all problems due
> > to the driver ?
>
> What bridge do you have?
> I have an Indigita bridge.. seems to work fine for my DVD writer at
> least..  That would be ATAPI not ATA right?

excerpt from dmesg :

fwohci0:  mem 0xfedffc00-0xfedffdff,0xfedff000-0xfedff7ff at 
device 8.0 on pci0
fwohci0: PCI bus latency was changing to 250.
cache size 8.
pcib0: slot 8 INTA is routed to irq 9
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channel is 4.
fwohci0: resetting OHCI...done (0)
fwohci0: BUS_OPT 0xa002 -> 0xf800a002
fwohci0: Link 1394a available S400, 3 ports, maxrec 2048 bytes.
fwohci0: Enable 1394a Enhancements
fwohci0: EUI64 08:00:46:03:00:9d:41:5e
fwochi_set_intr: 1
firewire0:  on fwohci0
firewire0: firewire bus attach
sbp_identify
sbp_probe
sbp0:  on firewire0
sbp_attach

firewire0: BUS reset
firewire0: node_id = 0xc800ffc1, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
fw_set_bus_manager: 63->1 (loop=0)


Le Thursday 05 December 2002 00:31, Kenneth D. Merry a écrit :
[SNIP explanations on non-harmful error messages]
> > 
> >
> > PS : I recently tried to read from the firewire disk of a colleague,
> > which was formatted as HFS+, so these attempts did not go very far
>
> You can use dd to read from the drive and see at least whether reads work
> correctly.

done :
portable-cur# dd if=/dev/da0 of=/dev/null bs=64k count=40
40+0 records in
40+0 records out
2621440 bytes transferred in 1493.586586 secs (17551309 bytes/sec)
portable-cur#

this hopefully means neither the disk nor the adapter are fried - good news 
indeed ! (and the read speed is very good : 17Mbyte/sec)

TfH
>
> Ken

PS : this is with
FreeBSD 5.0-DP2 #1: Sat Nov 16 13:38:33 GMT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xc06be000.
Preloaded elf module "/boot/kernel/snd_ds1.ko" at 0xc06be0a8.
Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc06be154.
Preloaded elf module "/boot/kernel/firewire.ko" at 0xc06be200.
Preloaded elf module "/boot/kernel/sbp.ko" at 0xc06be2b0.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06be358.

I'll try ASAP with an up-to-date -Current



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

problems with a firewire external hard disk [long]

[Thierry Herbelot]

Hello,

I can't seem to use my new external firewire hard disk :
(this is with 5.0-DP2, there are the same kinds of symptoms under 4.7-Stable)

My main question is to know where the problems are : is the hard disk dead ? 
is the firewire/ATA bridge fried ? are all problems due to the driver ?

Any help very much appreciated
(or hints to get debugging / trace info)

TfH

Here follows a list of problems encountered :


1/ error messages at startup


when booting, the disk is detected as : (for 5.0-DP2)

firewire0:Discover new S400 device ID:00a0b80037aa
bus_explore done
Device SBP-II
sbp_post_explore: EUI:00a0b80037aa spec=1 key=1.
sbp0:0:0 LOGIN
sbp0:0:0 ordered:0 type:0 EUI:00a0b80037aa node:0 speed:2 maxrec:5 new!
sbp0:0:0 'LSI Logic' 'SYM13FW500-DISK DRIVE' 'a0b835'
sbp0:0:0 login: len 16, ID 0, cmd f001, recon_hold 1
sbp0:0:0 sbp_busy_timeout
sbp0:0:0 sbp_agent_reset
sbp0:0:0 sbp_do_attach
sbp0:0:0 sbp_cam_scan_lun
sbp0:0:0 ORB status src:1 resp:0 dead:1 len:3 stat:c orb:0008c83a4
sbp0:0:0 Request aborted
sbp0:0:0 sbp_agent_reset
sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b 
cmd/255b data/18b sense
sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 3
sbp0:0:0 ORB status src:1 resp:0 dead:1 len:3 stat:c orb:0008c84d8
sbp0:0:0 Request aborted
sbp0:0:0 sbp_agent_reset
sbp0:0:0 XPT_SCSI_IO: cmd: 00 00 00 00 00 00 00 00 00 00, flags: 0xc0, 6b 
cmd/0b data/32b sense
sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 6 code 29 qlfr 0 len 3
sbp0:0:0 ORB status src:1 resp:0 dead:1 len:3 stat:c orb:0008c89a8
sbp0:0:0 Request aborted
sbp0:0:0 sbp_agent_reset
sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b 
cmd/255b data/18b sense
sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 3
da0 at sbp0 bus 0 target 0 lun 0
da0:  Fixed Simplified Direct Access SCSI-0 
device
da0: 50.000MB/s transfers
da0: 28615MB (58605120 512 byte sectors: 255H 63S/T 3648C)

I'm a bit disturbed by the "Request aborted" messages


2/ Geometry problems

furthermore, I can't use more than the first 1024 cylinders of the disk : I 
cannot create a BIOS partition above cylinder 1024 (all partitions seem cut 
at 1024, when seen from the 4.7-Stable of 5.0 fdisk, even when forcing 3648 
cylinders for the size)

for now, I've tried to just use 4 1G partitions :

portable-cur# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=3648 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=3648 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 2040192 (996 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 126/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 2040255, size 2040255 (996 Meg), flag 80 (active)
beg: cyl 127/ head 0/ sector 1;
end: cyl 253/ head 254/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 4080510, size 2040255 (996 Meg), flag 80 (active)
beg: cyl 254/ head 0/ sector 1;
end: cyl 380/ head 254/ sector 63
The data for partition 4 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 6120765, size 2040255 (996 Meg), flag 80 (active)
beg: cyl 381/ head 0/ sector 1;
end: cyl 507/ head 254/ sector 63
portable-cur#

(why are all partitions active ?)


3/ Write errors

when I try to write to any partitions, one write operations ends "as stuck", 
with an error message such as :
Dec  4 21:41:09 portable-cur kernel: sbp_scsi_status: unknown scsi status
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 sbp_abort_ocb 0x1b
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 
9f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 ORB status src:0 resp:1 dead:1 
len:3 stat:4 orb:0008c8fac
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 Object: Operation request block 
(ORB), Serial Bus Error: Busy retry limit exceeded(X)
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 unordered execution order:1
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 sbp_agent_reset
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 
9f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense
Dec  4 21:41:09 portable-cur kernel: sbp0:0:0 SCSI status 8 sfmt 0 valid 0 key 
b code 8 qlfr 0 len 3
Dec  4 21:41:09 portable-cur kernel: sbp_scsi_status: unknown scsi status
Dec  4 21:41:09 portable-cur kernel: sbp0:0:

Re: [nephtes@openface.ca: [Xmame] Use of usleep() with -sleepidle]

[Thierry Herbelot]

Le Monday 02 December 2002 18:49, Mike Silbersack a écrit :
[SNIP]
>
> The time select() takes should be directly related to your system's hz
> setting.  The default for FreeBSD is 100, which means that the interrupt
> timer will fire every 10ms.  If you want to play with that, edit
> /etc/sysctl.conf and set kern.hz="1000", which should give you 1 ms
> accuracy.
>

the line :
kern.hz="1000"
must be placed in /boot/loader.conf

TfH

[SNIP]

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

Reading from an OS-X HFS disk drive ?

[Thierry Herbelot]

Hello,

I've installed 5.0-DP2 on my Vaio which has a firewire port.

I already had loaded the firewire driver in 4.7-Stable, to see what happened 
(nothing remarkable : the chipset is indeed probed and recognized, 
nevertheless, thanks for the driver !).

To go a bit further, I've borrowed a 80Gb disk from a colleague, who runs OS-X 
on his machine. I'm trying to read from this disk under 5.0-DP2

after loading the sbp.ko module, the disk is detected as :
sbp0:  on firewire0
sbp_attach
sbp_post_explore: EUI:0030e001e005 spec=1 key=1.
sbp0:0:0 LOGIN
sbp0:0:0 ordered:1 type:14 EUI:0030e001e005 node:1 speed:2 maxrec:5 new!
sbp0:0:0 'Oxford Semiconductor Ltd.   ' 'OXFORD IDE Device   ' '31'
sbp0:0:0 login: len 16, ID 0, cmd f010, recon_hold 0
sbp0:0:0 sbp_busy_timeout
sbp0:0:0 sbp_agent_reset
sbp0:0:0 sbp_do_attach
sbp0:0:0 sbp_cam_scan_lun
pass0 at sbp0 bus 0 target 0 lun 0
pass0:  Fixed Simplified Direct Access SCSI-4 
device
pass0: Serial Number   VNC402A4L6Z6LA
pass0: 50.000MB/s transfers
da0 at sbp0 bus 0 target 0 lun 0
da0:  FixedSimplified Direct Access SCSI-4 
device
da0: Serial Number   VNC402A4L6Z6LA
da0: 50.000MB/s transfers
da0: 78533MB (160836480 512 byte sectors: 255H 63S/T 10011C)
GEOM: new disk da0

I've tried both /usr/ports/emulators/hfs and hfsutils, but I can't read the 
HFS partition. I only have the root directory :

portable-cur# hfs dir -d /dev/da0

Volume is Musique
Directory of :

DMGR   BTFL1257472 0  Aug 29 14:23   Desktop DB
DMGR   DTFL  0 0  Aug 29 14:23   Desktop DF
MACS   FNDR  0 0  Aug 29 14:23   Finder
ttxt   ttro   1781 0  Aug 29 14:23   ReadMe
MACS   zsys  0 22233  Aug 29 14:23   System

   5 file(s) 1259253 bytes (data)
   22233 bytes (resource)
   0 bytes free

Is it a special form of HFS (HFS+ ?) ? is there some utility to mount this 
kinds of partitions ?

Thanks in advance

TfH

PS : the first sentence of the ReadMe file is :
"This hard disk is formatted with the Mac OS Extended format. Your files and 
information are still on the hard disk, but you cannot access them with the 
version To access your files you must mount this hard disk on a computer that 
has Mac OS 8.1 or later installed."


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

Re: About 5.0 and Nvidia drivers

[Thierry Herbelot]

Le Saturday 03 August 2002 22:09, Matthew N. Dodd a écrit :
> On Sat, 3 Aug 2002, Alp ATICI wrote:
> > And what's the latest about the Nvidia drivers? It's mentioned that
> > Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to
> > know what's going on in that issue too.
>
> "Any day now."

wow !

what will this driver know to do ? (any URL to begin RTFMing ?)

TfH

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

Re: A time resolution problem

[Thierry Herbelot]

Paolo Di Francesco wrote:
> 
[SNIP]
> 1 msec. (recompiled the kernel with HZ=10)
> 

in my experience, compiling a kernel with HZ greater than 10.000 (ten
thousand) is uselesss (I even had crash with greater HZ)

TfH

[SNIP]

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

Re: "boot -a" in 4.5-STABLE

[Thierry Herbelot]

Marc Heckmann wrote:
> 
> I've got 4.5-STABLE setup here with vinum as per the Vinum bootstrapping howto
> (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html).
> 
> I have ad0s1a which is "/" and ad2s1a which is mounted on /rootback, it's an
> exact copy of the "/" filesystem.
  ^
[SNIP]
> mountroot> ufs:/dev/ad2s1a
> Mounting root from ufs:/dev/ad0s1a   < NOTE this

if the root partitions are identical, the /etc/fstab files are also
identical, so you are truing to mount the initial root paartition from
the second disk.

TfH

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

Re: Contributing to FreeBSD

[Thierry Herbelot]

Christian Flügel wrote:
> 
> Hi,

Welcome,

> 
> I use FreeBSD regularly for over 4 years now (since I have read an Article
> about 3.0 in the c't magazine) and since I deem it such a great product I'd
> very much like to contribute to it to help make it even better.

this is clearly how FreeBSD has become what it is

> 
> I just don't know where to start. I am a Comp. Sci. Major with not much
> experience in the Programming Aspects of FreeBSD but I am willing to learn
> so what would be a good headstart? Which projects are desperatly seeking
> assistance? Any hints would be greatly appreciated.

the "canonical" answer is to have a look at the open Problem Report
database (PR database), which you can find at
 - the list is quite
long)
(and perhaps get in touch with one of the committers of FreeBSD)

then, find a PR with a title you like, and investigate (and then have a
solution, as a patch to a version of FreeBSD).
the preferred way to submit patches is toward the -Current version of
FreeBSD, but this version can be tricky to even use, so a patch toward
the -Stable version is also very valuable.

Happy hacking
> 
> Regards
> 
> Christian
> 

TfH

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

Re: getting started with -CURRENT

[Thierry Herbelot]

Steve Tremblett wrote:
> 
> I would think it is reasonable to dual-boot -CURRENT and -STABLE on
> this box.  Is this possible on the same hard disk, or will multiple
> hard disks be required for that?  I'm thinking that the BIOS should
> complain about multiple partitions of the same type?  I'm so out of the
> loop in the PC world that I don't know if that is still a problem :)

one disk (if large enough) is sufficient to boot numerous versions of
FreeBSD (at the very least, one version for each of the 4 BIOS principal
partitions, then even multple versions inside each BIOS partition)

One example :

multi% df
Filesystem  1K-blocks UsedAvail Capacity  Mounted on
/dev/ad0s3a 49583353841023378%/
devfs   110   100%/dev
/dev/ad0s3f724303   399635   26672460%/usr
/dev/ad0s3e 19815 55591267130%/var
procfs  440   100%/proc
/dev/ad0s1a 4958338531 708684%/old_root
/dev/ad0s1f704495   477161   17097574%/old_usr
/dev/ad0s1e 1981514297 393378%/old_var
/dev/ad0s2e  15302928 13682913  100789893%/files3
multi%

ad0s3 (3rd BIOS part of the first IDE disk) hosts -Current, and ad0s1
hosts -Stable. Shared resources are in ad0s2e (notably -Current sources,
which are built when booted on -Stable)

TfH

you may also want to read carefully one post by Matt Dillon :


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

Re: Clock Granularity (kernel option HZ)

[Thierry Herbelot]

I've used a large collection of PCs running somewhat real-time network
analysis with a HZ set at 5000Hz with absolutely no ill effects (this
was with P-III-450's)

using HZ=1 was outside of the possibilities of the machines.

one big gain is with timing, which will be better (I myself used NTP to
have a coherent timing on the collection of PC's, with an
inter-correlation better than 1 ms)

TfH

Eugene Panchenko wrote:
> 
> Hello!
> 
> I've seen various postings on the Net where people reported
> network-related and overall performance improvements caused
> by settig HZ kernel option to 1000 (for example), that is,
> reducing a tick size to 1ms for their FreeBSD and Linux
> systems.  However, several problems seem to arise, such as
> some device drivers do not include HZ in calculating their
> timeout value, but simply assume HZ to be 100, and also some
> utility programs such as top or ps take timing information
> from the kernel in ticks, also assuming 10ms ticks, however,
> most of these saying were related to Linux.  How safe it is
> to bump up HZ to, say, 1000 in FreeBSD (I use 4.5-STABLE)?
> What pitfals will I encounter (drivers, top/ps)?  Is there
> are going to be [promised] performance increase?  Do I
> really need it?  Thank you.

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

suspected dying CD-writer ?

[Thierry Herbelot]

Hello,

I've got an SCSI CD-Writer, which only gives errors when I try to use
cd-record (see full log at the end of the message)

As the problem is identical on a fresh 4.4-Rel (with cd-record installed
from the CD as a binary package) and a recently updated 4.5-RC, there is
strong suspicion the drive itself is dying.

can anyone decode the ASCII dump of the SCSI error message ?

(I've also cleaned the optics, in case there was too much dust, but no
joy)

time to buy a new Yamaha 2100S ?

TfH 

# cdrecord -v dev=0,2,0 speed=1 blank=fast
Cdrecord 1.10 (i386-unknown-freebsd4.4) Copyright (C) 1995-2001 J
RTOC Type: 1 = CD-ROM
scsidev: '0,2,0'
scsibus: 0 target: 2 lun: 0
Using libscg version 'schily-0.5'
atapi: 0
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities   : SYNC
Vendor_info: 'PHILIPS '
Identifikation : 'CDD3600 CD-R/RW '
Revision   : '2.00'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Drive buf size : 786432 = 768 KB
Current Secsize: 2048
Trying to clear drive status.
cdrecord: Drive needs to reload the media to return to proper status.
  ATIP start of lead out: 1166730 (03:18/30)
Blocks total: 1166730 Blocks current: 1166730 Blocks remaining: 1166880
Starting to write CD/DVD at speed 1 in write mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Blanking PMA, TOC, pregap
cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error
CDB:  A1 01 00 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 00 00 00 00 28 00 00 04 D8 20 00 00 80 00 00 01 19
04 00 00 00 80 01 00 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x20 Qual 0x00 (invalid command operation code) Fru 0x0
Sense flags: Blk 0 (valid) error refers to data part, bit ptr 0 (not
valid) field ptr 0
cmd finished after 5.618s timeout 9600s
cdrecord: Cannot blank disk, aborting.

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

Re: Phobos 4-port NIC

[Thierry Herbelot]

Eric Busto wrote:
> 
> Howdy,
> 
> I have recently acquired a pair of Phobos 4-port NIC's, the P430TX
> model.  On it, it has 4 Intel 21143TD chips, and one larger Intel
> 21152AB chip.
> 

Hello,

this seems similar to the DLINK D570-TX 4-port NIC, which works very
well with the dc driver

-- 
Thierry Herbelot

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

Re: kernel error messages

[Thierry Herbelot]

Hello,

this may be due to a bad block on your hard disk, in the swap partition
(matt ?)

TfH

PS : anyway, the "error 22" comes from some code (happy RTFS'ing !)

Dmitry Mottl wrote:
> 
> Hi, All
> 
> I got following error, while I say 'reboot'.
> Please, help me with description, what's going on
> Why 'pagein' and 'pageout' failed?
> What is error 22?
> 
> 
> Nov 14 18:07:00 spectre /kernel: swap_pager: I/O error - pageout failed;
> blkno 1552,size 16384, error 22
> Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed;
> blkno 336,size 4096, error 22
> Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd)
> Nov 14 18:08:03 spectre /kernel: swap_pager: I/O error - pagein failed;
> blkno 760,size 4096, error 22
> Nov 14 18:08:03 spectre /kernel: vm_fault: pager read error, pid 707 (sshd)
> Nov 14 18:08:03 spectre /kernel: pid 707 (sshd), uid 0: exited on signal 11
> Nov 14 18:10:47 spectre reboot: rebooted by dima
> Nov 14 18:10:48 spectre syslogd: exiting on signal 15
> 
> 
> Thank you
> 
> --
> best regards,
> Dmitry Mottl
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot

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

Re: Tagged Command Queuing support for IC-35L0?0 ?

[Thierry Herbelot]

David O'Brien wrote:
> 
> On Wed, Sep 05, 2001 at 09:33:55PM +0200, Thierry Herbelot wrote:
> > "known-bad" revision for these babies -, and the 762 North Bridge of the
> > soon to be there SMP Athlon)
> 
> "Soon to be there"??  Hum... I'm typing to you from one.

Excuse me : I meant for the common mortal, with prices more in line with
what can be expected from Asus or Abit 

Nice to hear it works (and works well, I assume)

    TfH
> 
> --
> -- David  ([EMAIL PROTECTED])

-- 
Thierry Herbelot

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

Re: Tagged Command Queuing support for IC-35L0?0 ?

[Thierry Herbelot]

Hello, sos

"Søren Schmidt" wrote:
> 
[SNIP]
> Anyhow, the problem at hand is more like bad chipsets, there is ALOT
> of ATA chipsets thats not working right when used the way needed for
> tagged queuing. That said, the IBM DTLA's series of drives are extremely

is there some place where a "recommended" list of chipsets is compiled ?
(my interest would be about oldies like 440LX/400BX - there may be some
"known-bad" revision for these babies -, and the 762 North Bridge of the
soon to be there SMP Athlon)

    Cheers (and keep up the ata)

-- 
Thierry Herbelot

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

clock synchronization quality via NTP ?

[Thierry Herbelot]

Hello,

I know FreeBSD can be used with great success for timing solutions (at
least two core members do it ?).

has someone some performance data of the quality of system clock
synchronization, while using NTPd with a GPS reveiver and a hard 1PPS
signal ?

More precisely : is it reasonable to hope having a system clock not
farther from the GPS clock by more than 50 micro-seconds ?

-- 
Thierry Herbelot

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

Re: FreeBSD for ARM processor

[Thierry Herbelot]

I *am* interested by any progress on an ARM machine : I don't yet have
resources to work on such a beast, but I thought on installing NetBSD on
one of our ARM eval boards.

If this is FreeBSD, all the better ...

TfH

PS : a fuller dmesg will be appreciated (along with more detail on your
machine : it seems to be a (fomer-Corel) NetWinder)

"Stephane E. Potvin" wrote:
> 
> I tought that some might be interested by this:
> 
> Copyright (c) 1992-2001 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> sysinit->subsystem 0x0081
> FreeBSD 5.0-CURRENT #271: Sun Jul 22 08:36:22 EDT 2001
> [EMAIL PROTECTED]:/usr/local/users/spotvin/work/FreeBSD/src/sys/arm/
> compile/NETWINDER
> sysinit->subsystem 0x0100
> <... some more subsystems ...>
> sysinit->subsystem 0x0840
> panic: spin lock (null) held by 0 for > 5 seconds
> Uptime: 0s
> Automatic reboot in 15 seconds - press a key on the console to abort
> 
> If there's any interest, I will continue to keep the list posted of my progresses.
> 
> Steph
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot

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

Re: dual booting -stable & -current

[Thierry Herbelot]

Garance A Drosihn wrote:
> 
[SNIP]
> 
> How did you do those two installs though?  David is not saying that

I don't remember very well : it may well have been done via cloning an
existing slice via dump/restore (thus no sysinstall troubles ...)

[SNIP]
> 
> Where you have trouble is if you have two dos-style slices defined,
> both of type freebsd, and you want sysinstall to install into the
> second of those two slices.
  ^^

OK, got it : I also installed a 3.5.1 from CD/sysinstall, but it was on
the 3rd BIOS partition, where the 4th was also FreeBSD (but situated in
the disk *after* ad0s3 which was to be the new boot partition)

[SNIP]

BTW : thanks for the *detailed* explanation

-- 
Thierry Herbelot

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

Re: dual booting -stable & -current

[Thierry Herbelot]

David O'Brien wrote:
> 
> On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote:
> > I'm probably completely dim today so please bear with me :/
> > Thing is I want to setup a dual-boot box, running -stable & -current.
> > This box, a P2/266 has a 30G IDE disk.
> >
> > What I did is create
> >   ad0s1 -> 256MB -> holds root for -stable
> >   ad0s2 -> 256MB -> was supposed to hold root for -current
> >   ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable
> >   ad0s4 -> ditto for -current
> 
> You are getting bit by the "root" aliasing code (IIRC this is the right
> way to describe the problem).  This makes it impossible to install
> multiple copies of FreeBSD on a single disk w/o hacking around the
> system. :-(

I do not understand what this problem is : 
- I've got one system with two bootable FreeBSD "BIOS" partitions (the
one I already sent info about (these are two -Stable versions) and both
versions have been installed via /stand/sysinstall
- Another system runs with two FreeBSD "BIOS" partitions (used to switch
between 3-Stable and 4-Stable) the boot0 boot selector is used to switch
between releases
- a third (a notebook) has one FreeBSD "BIOS" partition and used to be
shared between 4-Stable and -Current (using all 8 FreeBSD partitions in
the slice and using the loader to select ad0s4a or ad0s4e for root
partition) - In this case, /stand/sysinstall was unable to create all 8
FreeBSD partitions : I had to first install FreeBSD on ad0s3, cut 8
partitions in ad0s4, then reinstall in ad0s4.

[SNIP]
-- 
Thierry Herbelot

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

Re: dual booting -stable & -current

[Thierry Herbelot]

Wilko Bulte wrote:
> 
> I'm probably completely dim today so please bear with me :/
> Thing is I want to setup a dual-boot box, running -stable & -current.
> This box, a P2/266 has a 30G IDE disk.
> 
> What I did is create
> ad0s1 -> 256MB -> holds root for -stable
> ad0s2 -> 256MB -> was supposed to hold root for -current
> ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable
> ad0s4 -> ditto for -current
> 
> My recollection is that as long as you keep the root partitions <2 (or 8) GB
> it should be bootable. Hence this somewhat strange slicing.
> 
> Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want
> to go current from there).
> 
> I'm probably missing something obvious here?

here's what I have on my (just -Stable for the moment) workstation :
multi# fdisk ad4
*** Working on device /dev/ad4 ***
parameters extracted from in-core disklabel are:
cylinders=35390 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 63, size 2457441 (1199 Meg), flag 0
The data for partition 2 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 4095504, size 31577616 (15418 Meg), flag 0
he data for partition 3 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 2457504, size 1638000 (799 Meg), flag 80 (active)
The data for partition 4 is:

// main bootable partition 
multi# disklabel -r ad4s1  
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   10240004.2BSD 1024  819216 on /
  b:   860160   102400  swap  shared swap
  c:  24574410unused0 0
  e:40960   9625604.2BSD 1024  819216 on /var
  f:  1453921  10035204.2BSD 1024  819216 on /usr
// alternate bootable partition (will be -Current)
multi# disklabel -r ad4s3
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   10240004.2BSD 1024  819216 on alternate / 
  c:  16380000unused0 0  
  e:40960   1024004.2BSD 1024  819216 alt. /var 
  f:  1494640   1433604.2BSD 1024  819216 alt. /usr
multi# disklabel -r ad4s2
#size   offsetfstype   [fsize bsize bps/cpg]
  c: 315776160unused0 0   
  e: 3157761604.2BSD0 0 0 shared expanse

you may want to use a similar setup (with larger bootable partitions :
my setup was initially one only 2G partition, but I cut it this way,
with a shared swap to be able to dual-boot)

PS : I also had problems with a 40G disk on my oldish P-II/266 : it
would not boot from the large disk (I just added a spare 8G which I boot
from)

-- 
Thierry Herbelot

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

Swapping in diskless ? (was :Re: [hackers] Re: getting rid of sysinstall)

[Thierry Herbelot]

David Gilbert wrote:
> 
[SNIP]
> 
> I'm still having trouble with diskless operation.  If I specify the
> swap option in DHCP, the pxeboot chokes on it.  If I don't specify the
> swap there, things boot, but I have no swap.  There isn't an obvious
> way to add nfs swap once a server is running.
> 
> Is there a way to do this in loader.conf or loader.rc?

I don't know : my application was "embedded" and used much less than the
128MBytes installed in the machines (thus no swap!)

-- 
Thierry Herbelot

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

Re: getting rid of sysinstall

[Thierry Herbelot]

Alfred Perlstein wrote:
> 
[SNIP]
> Actually, this is what I did for Google, we were able to have 40 machines
> installed in about an hour:
> 
> http://people.freebsd.org/~alfred/pxe/
> 
> --
> -Alfred Perlstein [[EMAIL PROTECTED]]
> Ok, who wrote this damn function called '??'?
> And why do my programs keep crashing in it?

first : a big thank you for your paper : I finally could use PXE for
diskless booting (not install, just running a full, diskless, FreeBSD)

then : I thought Google used some version of Linux in its server farms


TfH
-- 
Thierry Herbelot

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

memory leak in libfetch ? (with patch)

[Thierry . Herbelot]

hello,

[this is using a 4.3-Release machine]

I'm using libfetch for automated file transfers from a program (via ftp).

The program is running for long periods of time, and seems to be leaking memory (at 
least it's SIZE in top(1) just grows and grows - the swap is also increasingly used).

As there is no dynamically allocated memory in my program, one suspect could be 
libfetch(3).

Indeed, there are 5 calls to malloc(3) in the source code of the lib :
- in common.c, line 263, which should not cause a leak as the pointer is stored in 
buf, which is later saved,
- in common.c, line 362, in a function which is not used in my app (the file name is 
known)
- in fetch.c, line 377, in a function which is used only for http/https transfers, 
thus not in my app,
- in http.c, line 517, in a function which is used only for http/https transfers, thus 
not in my app,
- finally in ftp.c, line 434, in a suspicious manner : the "io" variable is located on 
the stack, thus visible only from this function, gets a pointer to a newly allocated 
ftpio struct and disappears after _ftp_setup() returns.

The comparison between usr.bin/compress/zopen.c:zclose() and 
lib/libfetch/ftp.c:_ftp_close() shows a missing free(cookie) at the end of the 
function.

the following patch seems to cure the memory leak :
-
--- ftp.c.ori  Sat Apr  7 19:30:48 2001
+++ ftp.c Mon May 21 15:26:42 2001
@@ -422,7 +422,9 @@
 io->err = 0;
 close(io->csd);
 io->csd = -1;
-return io->err ? -1 : 0;
+r = io->err ? -1 : 0;
+free(io);
+return (r);
 }

 static FILE *
-

 TfH



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

Re: no keyboard

[Thierry Herbelot]

Chris Faulhaber wrote:
> 
> On Sat, May 05, 2001 at 07:36:07PM +0200, Ingo Flaschberger wrote:
> > Hi
> >
> > i'm not sure if that is the right list, but i hope u could help me.
> >
> > i'm working at an iap, and we are using freebsd (4.2) boxes as routers.
> > normally no keyboard or monitor is attached to the box.
> > the problem is, when i connect after the boot a keyboard at the box, it is
> > not recognized. at the colocations we often need access to this boxes (not
> > remote access).
> > is there a solution for this problem?

Note : this is a way to kill your keyboard : an AT keyboard is not
hot-plug compatible

two better solutions :
- a KVM (keyboard video mouse) switch (for example, from Blackbox)
- a serial console (via console="comconsole" in /boot/loader.conf + the
right conf in /etc/ttys

-- 
Thierry Herbelot

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

AMD and SMP ? (was :Re: x86-64 Hammer and IA64 Itainium)

[Thierry Herbelot]

BTW, is there any AMD SMP machine already running FreeBSD ? (my BP6 is
getting old and tired, and I'd like to keep an SMP machine)

-- 
Thierry Herbelot

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

Re: Routing latency

[Thierry Herbelot]

Mårten Wikström wrote:
> 
[SNIP]
> 
> I'm using the de driver. Alas, the NICs seems quite old. They are 21140's.
> I've only got one 21143. I think there is a 3COM 3c905b in the lab too.
> Would it be better to use the 21143 + 3com than two 21140s?

definitely : in my packet blaster, I get an order of magnitude less
packet drops with a 3c905 than with a dc NIC (which is on a multi-port
NIC : the PCI-PCI bridge may be a hindrance there)

    TfH
> 
> /Mårten

-- 
Thierry Herbelot

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

Re: Routing latency

[Thierry Herbelot]

Dennis wrote:
> 
[SNIP]
> 
> If you are using the dc driver, make certain it is operating in
> store-and-forward mode, the default configuration starts in a mode that
> only works on 10mb/s connections.

patches ?

> 
> dennis

-- 
Thierry Herbelot

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

Re: Routing latency

[Thierry Herbelot]

Gilbert Gong wrote:
> 
> Is this HZ option present in 4.2-STABLE?

yes, but I don't know why it does not appear in LINT.

This is what I've got in my home box kernel config file :

options HZ=1000 

TfH
> 
> >From sources update about a week ago:
> c106 - ggong@ggong:/usr/src/sys/i386/conf>ls -l LINT
> -rw-r--r--  1 root  wheel  88928 Mar 11 21:14 LINT
> c107 - ggong@ggong:/usr/src/sys/i386/conf>date
> Mon Mar 19 15:34:51 PST 2001
> c108 - ggong@ggong:/usr/src/sys/i386/conf>grep HZ LINT
> c109 - ggong@ggong:/usr/src/sys/i386/conf>
> 

-- 
Thierry Herbelot

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

Re: scheduling frequency for threaded applications ?

[Thierry Herbelot]

Alfred Perlstein wrote:
> 
> * Thierry Herbelot <[EMAIL PROTECTED]> [010319 11:43] wrote:
> > Hello,
> >
> > I'm developping a network benchmark application ("packet blaster").
> >
> > The current version uses many processes, to send and receive packets,
> > and collate statistics.
> > when I look at top(1), I see most of the time taken is in the "system"
> > category. I assume this is due to the many context switches between the
> > collaborating processes.
> 
> You're incorrect.  System means just about any time spent inside the
> kernel (except interrupts), so basically syscalls count towards this
> meaning that your application is driving the kernel pretty hard.
> 
> This is easy for a team of processes, but nearly impossible with
> a thread based approach.

could you please elaborate ? (indeed, if you could also shed some light
on the first question : how frequently are threads rescheduled ?)

> 
> You don't want to use threads.
> 
> --
> -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]

PS : the TI-RPC commit was a nice one !

-- 
Thierry Herbelot

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

scheduling frequency for threaded applications ?

[Thierry Herbelot]

Hello,

I'm developping a network benchmark application ("packet blaster").

The current version uses many processes, to send and receive packets,
and collate statistics.
when I look at top(1), I see most of the time taken is in the "system"
category. I assume this is due to the many context switches between the
collaborating processes.

If I want to get rid of this system overhead, one solution is to use
threads (all sharing the same address space, thus no more context
switching).

My question is : how otfen are the threads rescheduled ?
(all threads are mainly always blocked until an event arrives, either a
timeout with select() or a packet with recevmsg())

I've had a quick look a TFM, but I don't see anything applicable
(pthread_setschedparam(3) for example does not speak of scheduling
frequency)

-- 
Thierry Herbelot

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

Re: Routing latency

[Thierry Herbelot]

Hello,

the FreeBSD TCP/IP stack uses the "system tick timer" for some delay
(maybe only for TCP).

you may want to use a HZ=1000 option (see the LINT config file) in a
recompiled kernel and see if things go better. (moreover, the dc(4)
driver which is used for your NIC has some interesting performance
improvements in the forthcoming 4.3-Release)

TfH

Mårten Wikström wrote:
> 
> I've performed a routing test between a FreeBSD box and a Linux box. I
> measured the latency and the result was not what I had expected. Both
> systems had the peak at 100 us (microseconds), but whereas the Linux box had
> _no_ packet over 200 us, the FreeBSD box delayed some packets up to 2 ms!
> Looking at the time series, it seems that the packets are delayed at regular
> intervals, about every second. My guess is that some timer interrupt
> triggers every second and steals too much cpu. So my question is, how can I
> decrease this routing delay?
> 
> Test info:
> I used two identical boxes, each equipped with a Pentium Pro 200Mhz and 64Mb
> mem. RedHat 7.0 with 2.4 kernel in one and FreeBSD 4.2-RELEASE in the other.
> I used two DEC 100Mbit ethernet cards (21140 I think).
> I measured the latency with a SmartBits instrument. Fastforwarding was
> disabled. Three UDP streams was sent from the SmartBits to one of the
> ethernet cards in the box, which routed the streams to the other interface,
> which in turn was connected back to the SmartBits.
> I had not made any changes to the standard kernel configuration. No other
> processes was running in the background, apart from those necessary to
> perform the test. The ARP table was set statically, so no ARP traffic would
> disturb.
> 
> I would at least want to know what is causing the extra delays.
> 
> /Mårten
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot

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

Re: Remote boot, but not diskless operation

[Thierry Herbelot]

Paul Saab wrote:
> 
> Thierry Herbelot ([EMAIL PROTECTED]) wrote:
> > they've done this, but their newest BIOS (8 days old) still has a 0.78
> > PXE revision (I've seen more recent DELL machines with a 0.99 - I assume
> > this is better)
> 
> No.. 0.99 is the orginal PXE v1.  PXE v2 (build 78) is what you have
> and is highly buggy.  You must request an update of the PXE rom from
> your motherboard manufacturer.

I'm not at work, so all is from memory (bad). I'll check once again on
monday

Thanks for the info

-- 
Thierry Herbelot

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

Re: Remote boot, but not diskless operation

[Thierry Herbelot]

Paul Saab wrote:
> 
> Thierry Herbelot ([EMAIL PROTECTED]) wrote:
> > Paul Saab wrote:
> > >
> >
> > Hi,
> >
> > My problem is that the NIC I'm trying to boot from is an on-board fxp on
> > a Motorola p-III M/B (I assume there is no specific "PXE rom", as PXE
> > may be included in the BIOS)
> >
> > will your "intel board" upgrade .exe work in this setup ?
> 
> You need to get an updated bios which contains a newer PXE rom.
> Motorola should contact Intel for the updated ROM.

they've done this, but their newest BIOS (8 days old) still has a 0.78
PXE revision (I've seen more recent DELL machines with a 0.99 - I assume
this is better)

-- 
Thierry Herbelot

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

Re: Remote boot, but not diskless operation

[Thierry Herbelot]

Paul Saab wrote:
> 

Hi,

My problem is that the NIC I'm trying to boot from is an on-board fxp on
a Motorola p-III M/B (I assume there is no specific "PXE rom", as PXE
may be included in the BIOS)

will your "intel board" upgrade .exe work in this setup ?

TfH

> Upgrade the PXE rom
> http://people.freebsd.org/~ps/pxeroms/
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot

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

Re: Remote boot, but not diskless operation

[Thierry Herbelot]

Hi,

One way to boot the kernel over the network is to use PXE (if your
machine is recent enough to support it *well* : that is with a recent
version of the PXE firmware)

there is no real document on PXE booting
you can read a note by Alfred Perlstein on
<http://people.freebsd.org/~alfred/pxe.html>, the manpage for pxeboot,
the code in rc.diskless{1,2}, the configuration of the boot server with
dhcp and tftp/nfs (you may have to tweak /etc/fstab in order to mount a
root partition which was not used to load /kernel ?)

there is also somme documentation on Intel's web site

I'm trying to use PXE, but it's not completly reliable (sometimes
pxeboot just crashes)

TfH

Rohit Rakshe wrote:
> 
> Hello,
> 
> I am running FreeBSD 4.1 on an Intel-III box. It is not a diskless
> machine, so root fs is still local, but I need to boot kernel over
> ethernet.
> 
> Reason for such a requirement: I am doing some kernel debugging and it is
> relatively quicker (after a panic) to recompile kernel on a server and
> reboot the test machine with the kernel on the server.
> 
> Currently available info doesn't seem to help me a lot. Any suggestions ?
> Thanks a lot !!
> 
> - Rohit
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot

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

Re: Request

[Thierry Herbelot]

The recommended work for any new developper of FreeBSD (did I say
welcome ?) is to search in the PR (problem reports) database on the
FreeBSD web site, to take one problem and then give a solution
(generally as a patch to the sources of the OS)

when you are done, find some committer of FreeBSD and bother him until
he/she will integrate your changes in the core OS (then, take another
problem)

TfH

Saikat Kanjilal wrote:
> 
> To Whom It May Concern:
> I am writing this letter to volunteer my time to the following areas of the
> freeBSD project
> 
> Implement Int13 vm86 disk driver.
> Port existing ISA drivers to new architecture.
> Move all interrupt-management code to appropriate parts of the bus drivers.
> Port PCI subsystem to new architecture
> Kernel issues.
> Add more pro-active security infrastructure.
> Security and cryptography
> 
> Please let me know how and why I can immediately get involved with code.
> 
> Thanks
> Saikat
> _
> Get your FREE download of MSN Explorer at http://explorer.msn.com
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot

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

Re: Porting NVidia linux kernel modules to FreeBSD

[Thierry Herbelot]

Alexey Dokuchaev wrote:
> 
> Hello!
> 
> I'm quite interested in having true 3D hardware acceleration on my ASUS
> AGP-V3800Magic video card based on TNT2 M64 chip, while running
> XFree86-4.0.2 on FreeBSD 4.2-STABLE.
> 
 Me too 

3D acceleration (or the lack thereof) is supposed to be one of the
reasons why XFree 336 is still the standard version delivered for
FreeBSD.

I have not searched exactly how it is possible to have glx acceleration
with 336 and NVidia boards, but Iwould be intersted to know if some
how-to existed (I've switched to 4.0.x as this should have been the way
to DRI and fully-supported, OS-independant, 3D acceleration)

nevertheless, the NVidia "Linux kernel module" seems to be a
encapsulation of their Win$$ driver, so as to be usable under Linux.
Maybe the careful study of the source included in the "kernel module"
can give some hints on how to do the same kind of wrapper for FreeBSD

good luck

-- 
Thierry Herbelot

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

Re: if_fxp status?

[Thierry Herbelot]

Luigi Rizzo wrote:
> 
[SNIP]
 
> Now, the 21143 (which is a pretty nice chip and has available
> documentation and a decent driver, "dc") is discontinued, but there
> are clones which work reasonably well (and are even cheaper, around
> $30 or so at compusa, i think netgear or linksys does one of these
> cards). I'd go with them. No multiport card, at least as far as i know.

What : no more dc multiport board ? are you sure of this ? if so, it may
be wise to buy some D-link 570-TX boards in advance for my project.

    Cheers
-- 
Thierry Herbelot

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

Re: detecting a closing socket from a Lex/Yacc interpreter ?

[Thierry Herbelot]

Jordan DeLong wrote:
> 
> I'm assuming right now you are just setting yyin to the fd for the socket.
> What you're gonna want to do is define the macro YY_INPUT (see the man page for
> details) so that it calls recv on your socket.  and then if it errors you can
> have YY_INPUT return as an EOF and your <> rule will work fine.
> 

indeed, taking the very simple YY_INPUT code from the man page of lex
did the trick (+ remembering to close the fd's associated to the socket
...)

Thanks

-- 
Thierry Herbelot

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

detecting a closing socket from a Lex/Yacc interpreter ?

[Thierry Herbelot]

Hello,

I'm currently writing a small interpreter for a client/server
application.

the Lex and Yacc files seem to be OK, as the tests are running fine (as
long as there is only one client, and the client dos not close its
socket ...)

I still have one problem : the server has a single thread : the process
accept()s a connection, then processes the commands (with yyparse()),
and after the current client disconnects, gets back to listening to the
socket, and so on.

the problem is that the yyparse() function does not return when the
socket is closed. I've had a look at the sources of ftpd, where yacc is
used, but from what I've seen, the yylex() function has been hand
written (which I would like not to do)

I've added a <> target in the lex file, but it does not seem to
detect the socket close()

taker for any solution,

    TfH
-- 
Thierry Herbelot

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

What is the latest "known-good" PXE build ?

[Thierry . Herbelot]

Hello,

I'm trying to use the pxeboot loader from 4.2-RELEASE, to diskless
boot some rack-mount PCs.

Using documentation from Alfred Perlstein and Mike Smith, I've configured
a DHCP server and a tftp server, and I'm still having problems
with at least one machine not being able to start each time it is powered on :
BTX halts (sometimes it is "Stack underflow", some other times, it goes to
a register crash dump, with eip often equal to ff - I'm going to redirect the BIOS
output to a serial port)

the configuration of the server must be correct as the diskless machine
sometimes can start (it loads pxeboot and the kernel via tftp, and then
the rest of the partitions via NFS).

The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
perhaps better version of it ? (the on-board NIC on the machine is an fxp)

 TfH

PS : As I've seen, rc has been modified to get rid of "early_nfs_mounts". After
this change, the rc.diskless2 does no longer work, as this script uses
/usr/bin/find and /usr is not yet mounted.




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

Re: What to do if a box is just "frozen"

[Thierry Herbelot]

False alarm : a reinstall of a fresh 4.2-R from a CD-ROM cured
everything (I thought I was careful when upgrading via make world ;-))

Peter Jeremy wrote:
> 
> On Mon, 15 Jan 2001 23:01:15 +0100, Thierry Herbelot <[EMAIL PROTECTED]> 
>wrote:
> >I've got a little application at work which can "just freeze" a
> >4.2-Release : the purpose of the application is just a packet blaster
> >used for telecom equipement test (send as many UDP packets as ordered,
> >on as many interfaces as there are on a machine).
[SNIP]
> 
> Can you send an NMI to the box?  (NMI can usually be generated by
> pulling I/0 channel check on the ISA bus low.  I/0 channel check is
> pin A1 (and there's a convenient ground on pin B1).  ([AB]1 is the
> pins closest to the rear of the machine).  NMI should trap to DDB.

thanks for the tip

> 
> Peter
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

cheers
-- 
Thierry Herbelot


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

Re: What to do if a box is just "frozen"

[Thierry Herbelot]

Eric Lee Green wrote:
> 
> On Mon, 15 Jan 2001, Thierry Herbelot wrote:
> > I've got a little application at work which can "just freeze" a
> > 4.2-Release : the purpose of the application is just a packet blaster
> 
> Are you sure it's not a hardware problem? Have you tried it with different
> hardware?

positive : the box makes regularly the world or a kernel, and this is as
good a hardware test as can be (furthermore, the same programs, when run
in a smaller number, runs happyly)

> 
> I had a "just freeze" problem in FreeBSD 3.3, but I was able to duplicate
> the behavior on other machines. They managed to whomp it for 3.4. Just
> curious to see whether it has made it back for 4.2 ("It's BCK!!!").

I hope it isn't so : 4.x architecture is quite different when compared
to 3.x 

-- 
Thierry Herbelot


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

What to do if a box is just "frozen"

[Thierry Herbelot]

Hello,

I've got a little application at work which can "just freeze" a
4.2-Release : the purpose of the application is just a packet blaster
used for telecom equipement test (send as many UDP packets as ordered,
on as many interfaces as there are on a machine).

So, on my 4.2-R test box (no-thrills BX, P-III 700 intel box), I have
some tens (around 30 of them) of such processes sending their packets,
and after some time (I have to more precisely determine this "some
time"), the box simply locks.
I do not see any message on console.

I have connected a real keyboard (the box was connected to a KVM
switch), I have DDB enabled in the kernel, and the box is still freezing
(if it were at least panicing, this would be a good start) : I can't
jump with ctrl-alt-esc to DDB (even Ctrl-Alt-Del does not reboot the
machine).

The memory does not seem to be a problem, as there are around 50 free
megabytes (out of 128), if top is to be believed (the box does not run
anything else than the blaster). the kernel is compiled with 8192 Mbuf
clusters (runs of netstat -m give a use of around 400 out of the 8192
clusters)

the "freezing" happens when the blaster is run as root, and also happens
when run as a casual user.

the box has a reset button, but this obvioulsy erases any data in
memory.

Is there something I could do to debug this problem ? (is there any way
to force a crash dump, via a serial console perhaps ? what is really
depressing is the loss of control from the keyboard, not being able to
switch to DDB)

I will try to upgrade the boxes to a more recent -Stable, to see if the
problem still exists.

    TIA for any idea

-- 
Thierry Herbelot


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

Re: rpc.lockd and true NFS locks?

[Thierry Herbelot]

Hello,

I've recently seen in the NetBSD 1.5 release Notes that *they* claim to
have a fully functional rpc.lockd manager : "Server part of NFS locking
(implemented by rpc.lockd(8)) now works."

could someone have a look at what our cousins have done and perhaps
import it in -current ?

    TfH
-- 
Thierry Herbelot


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

Re: Legacy ethernet cards in FreeBSD

[Thierry Herbelot]

"Koster, K.J." wrote:
> 
> Dear All,
> 
> Last night I cvsupped my trusty old Compaq Deskpro XL 6200 from 4.0-release
> to 4.2-beta. As part of that process, I seem to have lost support for the
> on-board NIC (lnc0: PCNet/PCI Ethernet Adapter, PC-net-32 VL-Bus).
> 
> What is the newest version of FreeBSD that will propely support that card?
> 
> If there are people who are cleaning up the support for older network cards
> in FreeBSD I'd like to help out by sending you my old NICs. It's not like
> they're any good to me without OS support.
> 
> Please contact me off-list for any of the following cards:
> 
>   3Com 3c503ISA

should be ok with the ed driver, for correct values of irq and io range

>   DEC EtherworksISA
>   DEC DE205 ISA
>   SMC EtherEZ   ISA

ditto

>   RealTek "TP-Link" PCI
> 
> As far as I've been able to determine, none of these work properly. In
> particular, the RealTek card gets detected and pretends to work, but loses
> the link after a bit (The link status LED goes out, and I need to reboot the
> box.)
> 
> I'll be happy to try out patches for the lnc driver to fix the problem of
> the Deskpro, or to give remote access to it if you want to work on it.
> 
> Kees Jan

-- 
Thierry Herbelot


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

Re: Routing issues

[Thierry Herbelot]

Gregory Sutter wrote:
> 
> I'm setting up a network that looks like this:
> 
> --InternetRouter---Firewall
>   |
>   |   /--- host
>SwitchNAT-<- host
>   |   \- host
>   |\- etc...
>  -
>  |   |
>email ns
> 
> In other words, a fairly typical small network.  I've got an 8-IP
> subnet; all hosts outside the NAT have real IPs:
> 
> router: 1.2.3.193
> firewall: 1.2.3.196  fxp0
>   1.2.3.197  fxp1
> nat:  1.2.3.198
> email:1.2.3.194
> ns:   1.2.3.195
> 
> The problem I'm having is with my routing.  Surprise.  Here is
> the routing table for the firewall:
> 
> default 1.2.3.193 fxp0
> 1.2.3.193   link#1 fxp0
> 1.2.3.192/29link#2 fxp1
> 1.2.3.196   lo0
> 1.2.3.197   lo0
> 
> The gateway_enable (net.inet.ip.forwarding) is also enabled on
> the firewall.

with a *routing* firewall, like the one you are using, you must have two
different IP subnets, one for each physical interface (or else, the
kernel will not know which interface to use to send a packet).

In your case, you should use a "bridging" firewall, where ony one of the
ethernet interfaces has an IP address (you can then set up your firewall
in a "stealth" config, where it does not touch the TTL in the IP
packets)

TfH

-- 
Thierry Herbelot


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

Re: finding source to functions

[Thierry Herbelot]

Marc Tardif wrote:
> 
> How can I find the source to specific functions in /usr/src/sys? I tried
> running ctags (find /usr/src/sys/ -type f -print | xargs ctags -w), but it
> dumps core because it can't accept so many args. I then tried creating a
> tags file for each subdirectory like so:
> for i in /usr/src/sys/
> do
>   if test -d $i
>   then
> cd $i
> find ./ -type f -print | xargs ctags -w
> cd ..
>   fi
> done
> 
> But that didn't work either. Any suggestions to make browsing the source
> code easier?

There is glimpse in the ports tree (/usr/ports/textproc/glimpse), which
can create a very efficient index for lots of text files (like source
files)

TfH
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Thierry Herbelot


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

Re: New ATA tagged queuing patch available

[Thierry Herbelot]

Soren Schmidt wrote:
> 
> >From the README:
> 
> ATA-tagged-queueing-diff-0908:
>   Add support for ATA channels with both a master and a slave, even
>   combos where only on of them supports tagged queuing should work now.
>   Also only switch on tagged queuing on IBM DPTA & DTLA series
>   drives, the older DJNA has firmware problems. I am working on
>   a SW solution to that, but for now only enable tagged queuing
>   on drives that is known to work.
> 
> Get it from http://freebsd.dk, and let me know your results
> 
> If I dont get any serious problem reports I'll commit this
> shortly, making FreeBSD the first OS that has tagged Queuing
> support for ATA drives :)
> 
> -Søren

Nice try !

Any chance an older IBM drive might be supported ?


TfH

-- 
Thierry Herbelot


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

Re: solicit hardware and/or testers for newbusified drivers

[Thierry Herbelot]

Jake Burkholder wrote:
> 
> I'm working on converting some of the older drivers to newbus and
> need hardware or testers to verify that this stuff still works.
> 
> If you have any of the hardware listed below and are willing to
> either loan it to me or be a guinea pig, please let me know.
> I have patches for some of them on my web page: http://io.yi.org
> 
> These compile with LINT and a kernel with no compat shims; they should
> apply cleanly to a recent -current.  I've booted a kernel with all these
> drivers compiled in to verify they were correctly not detected and didn't
> panic my machine.
> 
> If you use other drivers that still require compatibility shims you'll
> have to remove the entries for the drivers you are patching from
> sys/i386/isa/isa_compat.h or I believe the kernel will not link.
> This applies to LINT.
> 
> Hardware or Testers Needed:
> 
> ctx:Cortex-I frame grabber.
> spigot: Creative Labs Video Spigot video-acquisition board.
> meteor: Matrox Meteor video capture board.
> asc:GI1904-based hand scanners, e.g. the Trust Amiscan Grey.
> gsc:Genius GS-4500 hand scanner.
> el: 3Com 3C501 ethernet card.
> le: Digital Equipment EtherWorks 2 and EtherWorks 3 (DEPCA, DE100,
> DE101, DE200, DE201, DE202, DE203, DE204, DE205, DE422).

hello,

the le driver (or the board) does not work very well , but I can test a
newbusified version of it (as long as it runs under 4.0-R)

TfH
[SNIP]
> 
> Thank you
> 
> Jake

-- 
Thierry HerbelotASCII RIBBON CAMPAIGN   /"\
Dir. technique LUCCAS  AGAINST HTML MAIL & NEWS \ /
tout le cable sur  http://www.luccas.org  PAS DE HTML DANS   X 
un CV :  http://perso.cybercable.fr/herbelotLES COURRIELS   / \


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

Re: Voice Over IP (VOIP) support?

[Thierry Herbelot]

Ollivier Robert wrote:
> 
> According to Kris Kirby:
> > Do we have anyone actively working on Voice Over IP (VOIP) programs or
> > other interfaces for FreeBSD? I'm highly interested and would be willing
> > to assist in anyway that I can.
> 
> We -- Eurocontrol, my work company -- have a product called AudioLAN. It is a
> VoIP product that runs on Solaris for the moment. It is being ported to
> FreeBSD at the moment but we have problem with audio handling.
> 
Hello,

Will this "AudioLAN" be accessible ? (open source, even ?)

TfH

[SNIP]


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

Re: Voice Over IP (VOIP) support?

[Thierry Herbelot]

There is a very recent and not yet complete "openH323" port which should
be a way to VoIP.

TfH

Kris Kirby wrote:
> 
> Do we have anyone actively working on Voice Over IP (VOIP) programs or
> other interfaces for FreeBSD? I'm highly interested and would be willing
> to assist in anyway that I can.
> 
[SNIP]


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

Re: PCI IDE Controller (HPT-366) supported?

[Thierry Herbelot]

Of course, it works with FreeBSD (TM)

The new IDE driver (ata) from the soon-to-become-Stable 4.0 supports the
HPT366 :

(from the dmesg of my BP6)

ata-pci1:  port 0xd400-0xd4ff,
0xd000-0xd003,0xcc00-0xcc07 irq 18 at device 19.0 on pci0
ata2-master: success setting up UDMA4 mode on HPT366 chip
ad4:  ATA-5 disk at ata2 as master
ad4: 17418MB (35673120 sectors), 35390 cyls, 16 heads, 63 S/T, 512 B/S
ad4: 16 secs/int, 1 depth queue, UDMA66

TfH

Kris Kirby wrote:
> 
> Is anyone actively working on a driver for the High Point Technologies PCI
> disk controller (HPT-366)? I have a machine I can test on, and would be
> willing to assist. I'm tired of telling people that my motherboard has
> four IDE ports, but I can't use more than two under FreeBSD :-).
> 
> ---
> Kris Kirby, KE4AHR  | TGIFreeBSD... 'Nuff said.
> <[EMAIL PROTECTED]>|
> ---
> "God gave them the ability to reproduce...
> ... Science gave us the hope they won't." -KBK
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message


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

Re: disappearing mount points after install

[Thierry Herbelot]

Hello

[-mobile trimmed]

Marwan Fayed wrote:
> 
> Hello,
> 
> I am a seasoned UNIX user but have been using freebsd for only about 6
> months. I have posted this problem to freebsd-questions with no response
> so, figuring it must be a bug in the install program i'm going to try
> here. Oh, I would like to have traced the code to try to find the bug (if
> one exists) but being a senior year undergrad with a full course load and
> thesis, I have been left with little time... please forgive me.
> 
> My problem is this. I am trying to install 3.3-R on an IBM Thinkpad 365XD
> (although I have received mail from a man in France who is having the same
> problem on a desktop). The installation runs completely smoothly but when
> I finish and reboot the machine reports no resident O.S.

This may be due to a faulty BIOS : some BIOSes do not like at all not
having a DOS partition at the beginning of the disk (I have some HP PCs
with just 20 Megs of FAT at the start of the disk to keep them booting -
from , which is FreeBSD)

> 
> After trying many different things (including messing with the MBR, double
> and triple checking disk geometry, and using a Fixit disk to try to
> diagnose the problem), I booted from the install floppy to the main
> install menu.  Rather than re-install all over again for the nth time I
> just entered the label editor. The partitions were still there but the
> mount points were lost. What appeared was
> this:
> 
>  40M // supposed to be root
>  swap  84M // swap is obviously OK
>  651M// supposed to be /usr

The mount points for each partition are recorded in /etc/fstab : what
you are seeing is completely normal, as sysinstall has not read the
fstab file from the root partition of your disk.

> 
> This is clearly not what I designated so I tried relabelling the mount
> points, writing the information using 'w' and exiting install only to have
> the BIOS report no O.S. yet again!

Try and leave a small DOS partition at the beginning of your disk, as
said above.

> 
> The machine is a P100,40M ram,810HD, standard PCI (as far as I have been
> able to tell/test). Has anyone encountered this or know the problem?
> 
> Thanks a TON!
> 
> Marwan :-)

TfH

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


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

Anyone working on a DOMEX scsi driver ?

[Thierry Herbelot]

Hello,

I've just bought a Mustek SCSI scanner, and it is bundled with a
seemingly very simple SCSI controller built by a DOMEX company (from
Taiwan)

Does someone know where there could be some info ? (perhaps a driver
under Linux ?)

TfH

PS : the board identifier is DMX3191D - the chip itself seems to be a
Domex536


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

Re: multi-nics in FreeBSD 3.3 Release

[Thierry Herbelot]

Of course FreeBSD supports more than one NIC :

gw# ifconfig -a
ed0: flags=8843 mtu 1500
inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255
ether 52:54:4c:1b:90:1b 
ed1: flags=8843 mtu 1500
inet 212.198.30.16 netmask 0xff00 broadcast 212.198.30.255
ether 00:40:05:61:20:3e 
lp0: flags=8810 mtu 1500
lo0: flags=8049 mtu 16384
inet 127.0.0.1 netmask 0xff00 
gw# 

To use more than one NIC, you've two things to do :
1/ enable the NIC in your kernel, that is most likely recompiling your
kernel, as it is explained on :

2/ enable both NICs in the /etc/rc.conf file where wou will write
something like :
network_interfaces="ed0 ed1 lo0"
ifconfig_ed0="inet 192.168.1.3  netmask 255.255.255.0"
ifconfig_ed1="DHCP"
(my second board uses DHCP, but you may set a fixed IP address)

TfH

PS : you should also read


"Brian D. Moffet" wrote:
> 
> Of course some one knows this, but does FreeBSD support 2 NICS?
> I have a 3com 3c905 and a 3com 3c509 in my box, but no matter how I adjust the
> configuration file, I cannot get the 509 to be recognized.  I could put
> the Ne2000 clone in there instead, but the 509 is a better card.
> 
> Also, does the sio driver support PCI sio boards?  The 3com / US Robotics
> 56K faxmodem is an sio card with a modem on the other side, so that the
> computer should be able to talk to it as a 16550.  Though the IO address may
> be a bit strange (in the 0x4000 or 0xa000 range).  I guess this boils down
> to 2 questions, IO space as well as PCI interrupts.
> 
> And as soon as I find out more information, I plan on modifying pciconf
> to be able to parse more of the PCI BIOS information instead of just
> the vendor and card IDs, unless someone has already done so.  Where should
> I send the changes?
> 
> Thanks
> Brian Moffet
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message


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

Re: netgraph into -stable.

[Thierry Herbelot]

Julian Elischer wrote:
> 
> I admit that it doesn't seem  a minor addition, but
> I'd like ot get netgraph down -nto 3.x now that it has been shaken down a
> bit in 4.x
> 
> reasons:
> 1/ DSL in Canada is now switching rapidly to PPPoE.
> 2/ PPP will start using it soon (other than with pppoe)
> and we'd like ONE version not 2 for Brian to maintain.
> 3/ ISPs who may wan tto use the PPPOE server side are generally running
>   3.x, not 4.x

Is there any doc on how to implement ISP-side PPPoE ? (or is it PPP over
ATM, on the PVCs terminating the ADSL connections ?)

TfH


> 
> Supporting facts:
> Netgraph is written to generally be non intrusive.
> No code is changed in the non "options NETGRAPH" case and only minor
> changes are made in normal code paths in the NETGRAPH case.
> (with the exception of the if_sr and if_ar drivers)
> 
> I might hold off on some of the more intrusive of those
> changes (e.g. no real need to add it to netstat immediatly)
> which will not really effect the functionality.
> 
> And last but not least:
> We are actually developing Netgraph under 3.3 so we are already keeping
> two source trees in sync, 3.3. and 4.0 so we might as well let others get
> at it.
> 
> Anyone violently object?
> 
> Julian
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message


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