Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Nov 2011 11:30:23 -0500
From:      George Mitchell <george+freebsd@m5p.com>
To:        freebsd-stable@freebsd.org, freebsd@jdc.parodius.com
Subject:   Re: TCP Reassembly Issues
Message-ID:  <4ED1141F.3010501@m5p.com>
In-Reply-To: <20111126075647.GA33048@icarus.home.lan>
References:  <CAPNZ-Wq38=F3o2hYuYF_unBj3SZQ52XhVhdcwQ8PE_vU9xc2YA@mail.gmail.com> <4ECEF6FD.5050006@freebsd.org> <4ED077BF.10205@freebsd.org> <CAPNZ-WqZsSjcO=dVZpOOMtB_Y_hNcj%2BpYDA4nWPXX9kY9Vj1Wg@mail.gmail.com> <20111126075647.GA33048@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/26/11 02:56, Jeremy Chadwick wrote:
> [...]
> This entire situation leads me to believe very few people are doing
> quality testing of RELENG_9, yet we're already into 9.0-RC2.  Please
> don't tell me "that's exactly why you should be running RELENG_9!"; that
> is completely backwards and I refuse to get into a flame war about it,
> because it's this simple: 90%+ of those running FreeBSD on servers need
> something that's stable, we can't risk wonkiness (especially of this
> degree!) on systems taking production traffic.  Did no one actually test
> the change *thoroughly*?  Imagine had this lay dormant until 9.0-RELEASE.
> [...]

PPPP  L     U   U  SSSS      OOO  N   N EEEEE
P   P L     U   U S         O   O NN  N E
PPPP  L     U   U  SSS      O   O N N N EEE
P     L     U   U     S     O   O N  NN E
P     LLLLL  UUU  SSSS       OOO  N   N EEEEE

I didn't get a warm, fuzzy feeling about FreeBSD 7 until 7.1, and
FreeBSD 8 was worse -- no warm, fuzzy feeling until 8.2.  And I am still
not sold on SCHED_ULE:  Start as many compute-bound programs as there
are CPUs, and prepare for poor (to put it kindly) interactive response.
That's not everybody's usage pattern, but it seems plausible enough to
me to preclude SCHED_ULE as the default scheduler until it is fixed.

On the good side, I'm pleased with the new 9.0 boot menu, and I'm very
happy that the ahci driver automatically creates symbolic links to the
old device names for its disks.  I like that I don't have to tab to the
"Okay" button in configuration dialogs any more (though I was surprised
the first time it happened).

But I hope this gets fixed for my flash card reader/writer:

ugen0.5: <vendor 0x05e3> at usbus0
umass0: <vendor 0x05e3 USB TO IDE, class 0/0, rev 2.00/0.32, addr 5> on 
usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x4101
umass0:2:0:-1: Attached to scbus2
(probe0:umass-sim0:0:0:0): AutoSense failed
(da0:umass-sim0:0:0:0): got CAM status 0x4
(da0:umass-sim0:0:0:0): fatal error, failed to attach to device
(da0:umass-sim0:0:0:0): lost device - 0 outstanding
(da0:umass-sim0:0:0:0): removing device entry

-- George Mitchell



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ED1141F.3010501>