Lexan Software Inc.
Dear Sir or Madam:
We have allowed ourselves to write to you because you have posted your e-mail address
([EMAIL PROTECTED]) to the following Web page: http://www.freebsd.org/./platforms/index.html
If
On Sunday, 2 December 2001 at 17:53:37 +1030, Richard Sharpe wrote:
> Greg Lehey wrote:
>> On Saturday, 1 December 2001 at 13:05:53 +0100, Søren Schmidt wrote:
>>
>>> It seems Zwane Mwaikambo wrote:
>>>
Hi,
I've got a box which boots up with UDMA33 but during the boot
sequence
Greg Lehey wrote:
> On Saturday, 1 December 2001 at 13:05:53 +0100, Søren Schmidt wrote:
>
>>It seems Zwane Mwaikambo wrote:
>>
>>>Hi,
>>> I've got a box which boots up with UDMA33 but during the boot
>>>sequence gets write problems and ends up disabling it and i presume
>>>falling back to
You may want to mention that which branch (5-current, 4-stable, etc)
you wanna try. Also you may want to clear that when you sup your code.
kerberus> ===> share/doc/usd/13.viref
kerberus> make: don't know how to make ref.so. Stop
kerberus> *** Error code 2
src/contrib/nvi/docs/USD.doc/vi.ref/r
On Saturday, 1 December 2001 at 1:21:04 -0800, Julian Elischer wrote:
> On Fri, 30 Nov 2001, Peter Wemm wrote:
>
>> Julian Elischer wrote:
>>>
>>> I've tried getting information about our (FreeBSD) mail
>>> system by mailing to "postmaster" but no-one answers..
>>>
>>> so, who IS the postmaster
Had to go home to get the messages. Whilst i was there i examined the
verbose boot and pinpointed the DMA problem to the PIO cdrom i have (i
thought it was a UDMA one). Removing that from the same cable fixed the
DMA problem. Thanks for your time. But hopefully this might still help you
with my dr
Hi,
I've got a box which boots up with UDMA33 but during the boot
sequence gets write problems and ends up disabling it and i presume
falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have
had no problems running it at UDMA33.
Host: SiS 5591 (revision?)
Disk: Seagate 3.2G
Hi,
I've been trying to install FreeBSD 4.x on a box on of mine to no
avail. Essentially its a drive geometry problem (Seagate 3.2G), FreeBSD
"guesses" 6296/16/63 (which the BIOS (AMI) POST states it as as well, LBA
enabled) but i end up being unable to mkfs filesystems (access beyond
devi
On Sat, 1 Dec 2001, Søren Schmidt wrote:
> Ohhh, I need alot more info before I can tell whats going on..
> I need at least the dmesg from a verbosely booted system and
> also a pciconf -l to tell what chips you have.
Ok i can get the pciconf but how do i set the bootverbose flag?
Thanks.
Zwan
> > I am wondering whether we need contiguous memory for a PHYSICAL buffer to
> > perform the DMA I/O.
>
> yes. The DMA request should either not cross a physical page or
> if the request does cross a physical page, those pages must be
> contiguous.
Er, no.
> the exception to this is if your DM
It just fails ...
touch _stamp.extraobjs
(cd
/usr/src/share/doc/usd/11.vitut/../../../../contrib/nvi/docs/USD.doc/edit; g
roff -mtty-char -Tascii -t -ms -o1-
/usr/src/share/doc/usd/11.vitut/../../../../
contrib/nvi/docs/USD.doc/edit/edittut.ms) | gzip -cn > paper.ascii.gz
===> share/doc/usd/12.v
Oh, I forgot to mention... there's still a bug. You have to turn off
delayed acks to get the below numbers. Otherwise the window 0 recovery
ack ... gets delayed. Joy. It's easy to fix, but I'm off to see
Potter so it will be tonight.
:
:rxvt.
:=20
:
:Joe
Ok, please try w/ patch #2 that I just posted (the fix is is on the
client side... whoever is receiving the data). I only give it a 10%
chance of solving the workstation 'ls' stall issue because ssh does
not appear to use recv() w/ MSG_WAITALL. I can't rep
Richard (and others), please try this patch. With this patch I
get the following between two machines connected via a 100BaseTX
switch (full duplex):
test1:/home/dillon/dbench> ./tbench 1 test2
.1 clients started
..+*
Throughput 6
!@#%@#^%^$#^@#$%#@!$%!@%@#@# Whos the blasted bozo that broke TCP! :-)
:-(
I believe I have found another problem. It may not be related to this
one but I sure hope it is.
When the receiver's window contracts to zero causing the sender to
stop transmitting, TCP stalls
> I am not using compression and netstat -s confirms that it is really
> resending data. I examined it a bit more now and it seems OpenSSH 2.5 is
> sending a burst of small packets, each with 100 or 116 bytes
>
> 14:30:46.232151 server.22 > client.1525: P 30977:31077(100) ack 1144 win 24820
> 14
> Uh, I'm not sure what to make of that mangling of my name. However, I
> think the pointer to Steven's book you provided may be the thing he
> needs. I certainly don't know what he needs based on his followup.
I'm really sorry for messing up your name like that. I suppose your domain
name was st
On Sat, Dec 01, 2001 at 10:12:27AM -0500, Dragon Fire wrote:
>
> I have created a PCI device driver but I have a problem. The core code was
> developed using the current make_device_driver.sh then modified to fill in
> the details of the device.
>
> The problem is the make_dev call in attach is
I am not using compression and netstat -s confirms that it is really
resending data. I examined it a bit more now and it seems OpenSSH 2.5 is
sending a burst of small packets, each with 100 or 116 bytes
14:30:46.232151 server.22 > client.1525: P 30977:31077(100) ack 1144 win 24820
14:30:46.23335
Eric Melville <[EMAIL PROTECTED]> types:
> > The system call is being interrupted, it just gets restarted right away by
> > default. See Steven's "UNIX Network Programming" for a means of avoiding
> > this behavior.
> Of course, I'm completely wrong because we're not even talking about a
> system
On Sat, Dec 01, 2001 at 05:05:21AM -0800, Seth Kingsley wrote:
> On Sat, Dec 01, 2001 at 01:22:35AM -0500, kerberus wrote:
> > Okay ill ask again just in case nobody saw this!
> > is make release broken in 4.4-STABLE ?? Or is there a definitive
> > guide/FAQ on how to properly use make release to
Hi Folks,
A simple question.
I have created a PCI device driver but I have a problem. The core code was
developed using the current make_device_driver.sh then modified to fill in
the details of the device.
The problem is the make_dev call in attach is succeeding but not making the
device node i
On Sat, Dec 01, 2001 at 03:02:24AM -0700, Joesh Juphland wrote:
>
> Vanilla x86 system with two identical scsi disks attached to a single 2940.
> Installation is flawless - in custom install, I choose da0 and then da1, one
> after the other, to partition. Again, I say, installation goes flawl
On Sat, Dec 01, 2001 at 01:22:35AM -0500, kerberus wrote:
> Okay ill ask again just in case nobody saw this!
> is make release broken in 4.4-STABLE ?? Or is there a definitive
> guide/FAQ on how to properly use make release to cut a modified
> distribution ? cause either im doing something wrong,
It seems Zwane Mwaikambo wrote:
> On Sat, 1 Dec 2001, Søren Schmidt wrote:
>
> > Ohhh, I need alot more info before I can tell whats going on..
> > I need at least the dmesg from a verbosely booted system and
> > also a pciconf -l to tell what chips you have.
>
> Ok i can get the pciconf but how
It seems Zwane Mwaikambo wrote:
> Hi,
> I've got a box which boots up with UDMA33 but during the boot
> sequence gets write problems and ends up disabling it and i presume
> falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have
> had no problems running it at UDMA33.
>
> H
Matthew Dillon wrote:
> Index: tcp_output.c
> ===
> RCS file: /home/ncvs/src/sys/netinet/tcp_output.c,v
> retrieving revision 1.39.2.10
> diff -u -r1.39.2.10 tcp_output.c
> --- tcp_output.c 2001/07/07 04:30:38 1.39.2.10
> ++
On Sat, Dec 01, 2001 at 12:46:04AM -0800, Matthew Dillon wrote:
> I haven't been able to reproduce this. Two things, though... (1) are
> you using a compressed ssh connection or an uncompressed connection?
> It makes a big difference in regards to how ssh generates packet data.
>
On Sat, Dec 01, 2001 at 03:26:22AM +0100, Tomas Svensson wrote:
> JK> Is this the same problem that I experience on ssh connections between
> JK> my 5.0-current laptop and my releng_4 server? When I run an 'ls'
> JK> from the shell on large directories I get the response back block
> JK> delay bl
Hi,
On Sat, Dec 01, 2001 at 02:07:41PM +1030, Greg Lehey wrote:
> > so my drive is now running at UDMA 100.
>
> Can you send me dmesg output? In particular, I had a printf output
> there to show what the BIOS had set.
>
> Background for other people: Richard has an IDE chip which claims to
>
Vanilla x86 system with two identical scsi disks attached to a single 2940.
Installation is flawless - in custom install, I choose da0 and then da1, one
after the other, to partition. Again, I say, installation goes flawlessly.
When the system boots though, it cannot get past the boot manage
thanks.. That's quite amazing..
On Fri, 30 Nov 2001, Peter Wemm wrote:
> Julian Elischer wrote:
> >
> > I've tried getting information about our (FreeBSD) mail
> > system by mailing to "postmaster" but no-one answers..
> >
> > so, who IS the postmaster at the moment?
> >
> > I have the .elisc
On Sat, Dec 01, 2001 at 07:56:51AM -, Matthew wrote:
> any one know if there's supported IDE cdrw for freebsd4.1? Any software on
> FBSD4.1 to do the cdrw work?
Most IDE cdrw drives should work. Have a look at "man burncd" - It
claims to having been there since 4.0.
David.
To Unsubs
I haven't been able to reproduce this. Two things, though... (1) are
you using a compressed ssh connection or an uncompressed connection?
It makes a big difference in regards to how ssh generates packet data.
'ls' contains a lot of repetitive data and compresses well.
(2) Als
this adds a -p option to ldconfig so you can do something like:
ldconfig -p /usr/local/lib/libsafe.so
to set a preload, and:
ldconfig -pm /usr/local/lib/libsafe.so
to merge one.
the major problem i know of with this patch is that setting a preload ELF
library will hose your ability to run li
35 matches
Mail list logo
