Chris wrote:
On 12/05/06, Matthias Andree [EMAIL PROTECTED] wrote:
Mike Jakubik [EMAIL PROTECTED] writes:
Jonathan Noack wrote:
The *entire* errata page was from 6.0; it was a mistake. This wasn't
some put on the rose-colored classes and gloss over major issues
thing. It was a long
Brent Casavant wrote:
On Sun, 21 May 2006, Colin Percival wrote:
In order to better understand
which FreeBSD versions are in use, how people are (or aren't) keeping
them updated, and why it seems so many systems are not being updated, I
have put together a short survey of 12 questions.
I
Dmitriy Kirhlarov wrote:
Hi!
On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote:
6.1-STABLE after 6.1-RELEASE is releases. So I think you may want
If you use snapshots with your quotas, update to 6.1-STABLE. If you
Sorry, guys. You are mean RELENG_6_1 or RELENG_6?
WBR
Andriy Gapon wrote:
It seems that UDF fs has been in not-well-supported state for a while
now. It seems that Scott Long, original author and maintainer, has moved
on to other more important (and, perhaps, interesting) things.
(perhaps - because RE does not seem to be too exciting on the first
David Wolfskill wrote:
In testing a vendor's product, I managed (as I had been warned might
happen) to crash the machine on which the product was running.
It's a moderately-recent 6.1-STABLE:
mx-out05# uname -a
FreeBSD mx-out05.lab.example.org 6.1-STABLE FreeBSD 6.1-STABLE #3: Sun May 7
This looks like a pretty fundamental problem with the aue driver.
Scott
Scott Ullrich wrote:
Sleeping on usbsyn with the following non-sleepable locks held:
exclusive sleep mutex in_multi_mtx r = 0 (0xc0acfbc0) locked @
/usr/src/sys/neti
net/in.c:971
KDB: stack backtrace:
Doug White wrote:
On Mon, 5 Jun 2006, Andy Dills wrote:
I'm trying to get a Supermicro 6024H-32R setup with 6.1, but I'm
discovering that the Adaptec SAS AIC9410 controller isn't yet supported.
I see one brief thread about it on this mailing list back in March,
but no
further mention or
Andy Dills wrote:
On Fri, 9 Jun 2006, Scott Long wrote:
Doug White wrote:
On Mon, 5 Jun 2006, Andy Dills wrote:
I'm trying to get a Supermicro 6024H-32R setup with 6.1, but I'm
discovering that the Adaptec SAS AIC9410 controller isn't yet supported.
I see one brief thread about
Peter Losher wrote:
Thanks to all who answered my 'make release' questions; now that I have
done the initial release cut, now I am trying out 'make rerelease', and
it's bombing at the stage 4.4: building everything stage.
-=-
=== sbin/camcontrol (all)
cc -O2 -fno-strict-aliasing -pipe
Doug Poland wrote:
Hello,
I'm in the middle of an attempt to upgrade an i386 box from 5.5-STABLE
to 6.1-STABLE. Just in case it's apropos, the box was recently upgraded
from 5.2.1-RELEASE to 5.5-STABLE.
I am following the handbook's The Canonical Way to Update Your System
and have sucessfully
Doug Poland wrote:
Hello,
I'm in the middle of an attempt to upgrade an i386 box from 5.5-STABLE
to 6.1-STABLE. Just in case it's apropos, the box was recently upgraded
from 5.2.1-RELEASE to 5.5-STABLE.
I am following the handbook's The Canonical Way to Update Your System
and have sucessfully
Michel Talon wrote:
Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as
clients on a 100Mb/s network. The time trial used a dummy 100Meg file
transfered from the server to the client.
I have similar experiences here. With FreeBSD-6.1 as client (using an Intel
Michel Talon wrote:
BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was never
backed out. An immediate question for people experiencing new rpc.lockd
problems with 6.x should be whether or not backing out that change helps.
So it may be relevant to say that i have
up *after* upgrading to
FreeBSD 6.x, and only acting up under load ...
There are two normal approaches:
(1) Switch controllers and see if the problem goes away, then blame the
controller that was replaced. :-)
(2) Debug the driver when the system is in the wedged state. When
Scott Long
Guy Helmer wrote:
We just tried running programs under RELENG_6_1 that were compiled under
RELENG_6 checked out 2006-07-19, and couldn't because of the undefined
symbol __res_statel, which I would assume is a result of the recent
MFC of the BIND 9 resolver library.Is this to be expected?
Guy Helmer wrote:
Scott Long wrote:
Guy Helmer wrote:
We just tried running programs under RELENG_6_1 that were compiled
under RELENG_6 checked out 2006-07-19, and couldn't because of the
undefined symbol __res_statel, which I would assume is a result of
the recent MFC of the BIND 9
Peter Jeremy wrote:
On Wed, 2006-Jul-19 22:38:56 -0400, Ed Maste wrote:
- You may have to adjust some parameters in the kern.polling sysctl
tree - specifically, kern.polling.burst_max, kern.polling.each_burst
and kern.polling.user_frac might need tweaking.
Note that increasing
Marcelo Gardini do Amaral wrote:
The limited testing I've done on a Sun V20z at work suggests that you
can get better routing throughput in interrupt mode than polling mode.
YMMV and this is before tweaking the polling parameters. (My testing
also suggests that I don't really need to do any
Ok guys, time for a small breather here. All these claims about
EoE and orphanage and whatnot are a bit premature and underinformed.
First, the iir driver is being worked on when the need arises. Several
bugs were fixed in it a few months ago, and until Mark's recent series
of mails on it, no
clinth wrote:
Hi All,
This morning I upgraded a Dell PowerEdge 2850 from 6.0-RELEASE to
6.1-RELEASE and found that amr(4) no longer detects my Seagate DAT via
sa(4).
The system has an embedded Dell PERC 4e/Di with two channels. Channel 0
contains two disks in RAID 1 and works fine.
Darn, I thought that that was already fixed. I'll go dig up my patches
and take care of this.
Scott
Pavel Merdin wrote:
Hello.
There's a problem with a very busy server (ad server, CPU is close to
0% idle most of the time).
Configuration: Dual AMD Opteron 252 2.6GHz
Chipset: AMD 8131
Patrick M. Hausen wrote:
Hi, all!
We just set a brand new Intel SSR212CC box into production.
This is basically a standard server with 2 LSI SATA RAID
controllers and 12 drive bays in 2 rack units height.
Intel sells it as a storage product. There's a variant
of Windows 2003 server that turns
Julian H. Stacey wrote:
[EMAIL PROTECTED]
Message-id: [EMAIL PROTECTED]
From: Kris Kennaway [EMAIL PROTECTED]
lol, that's the stupidest thing I've heard all week.
Inflamatory. Refered to postmaster.
Julian, meet Kris. Kris has been the head of the FreeBSD ports team for
a large
Jan Mikkelsen wrote:
Hi,
Doug White wrote:
On Fri, 22 Sep 2006, Jan Mikkelsen wrote:
Quick summary: sym(4) assumes on amd64 that virtual
addresses provided by
bus_dmamem_alloc() have the same alignment as the physical
addresses (in
this case, 2*PAGE_SIZE). They don't, and stuff
Stefan Esser wrote:
Scott Long schrieb:
Jan Mikkelsen wrote:
Hi,
Doug White wrote:
On Fri, 22 Sep 2006, Jan Mikkelsen wrote:
Quick summary: sym(4) assumes on amd64 that virtual
addresses provided by
bus_dmamem_alloc() have the same alignment as the physical
addresses
Jan Mikkelsen wrote:
Attached is a simpler patch, after some feedback from Stefan over general
niceness.
It removes the amd64 special case by splitting the target member (an array
of struct sym_tcb) of sym_hcb out into a separately allocated structure.
This way there is never a need to
Oliver Brandmueller wrote:
Hi,
On Wed, Sep 27, 2006 at 08:00:21AM +0200, Martin Nilsson wrote:
I get tons of these:
em0: watchdog timeout -- resetting
em0: link state changed to DOWN
em0: link state changed to UP
mailbox# pciconf -lv
[EMAIL PROTECTED]:0:0: class=0x02 card=0x108c15d9
Oliver Brandmueller wrote:
Hi,
On Wed, Sep 27, 2006 at 08:55:53AM -0700, Jeremy Chadwick wrote:
The SMBus Interface is not used at all (it's not even really usable).
Anyway, as soon as I unload the ichsmb module I cannot triger the
problem anymore. If I load it again, the problem cann again
Peter Jeremy wrote:
On Wed, 2006-Sep-27 10:32:49 -0600, Scott Long wrote:
My theory here is that something in the kernel, likely VM/VFS, is
holding the Giant lock for an inordinate amount of time.
In the past (RELENG_5) I've had major problems with syncer delaying
interrupt threads for long
David G Lawrence wrote:
In the past (RELENG_5) I've had major problems with syncer delaying
interrupt threads for long periods (I've seen 8msec). See
http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/012346.html
I'm not sure if this is still a problem (but I am still having some
Volker wrote:
On 37378-12-23 20:59, Patrick M. Hausen wrote:
Hello!
Well, the best I can say at the moment is, Wow. =-( I guess the
thing to do here is to figure out if the problem lies with the em
interrupt handler not getting run, or the taskqueue not getting run.
I helped Pyun with
All,
Attached is my first cut at addressing the problems described in this
thread. As I discussed earlier, the VM syncer thread is likely starving
the USB interrupt thread. This causes the shared usb+network interrupt
to remain masked, preventing network interrupts from being delivered,
and
O. Hartmann wrote:
Scott Long wrote:
All,
Attached is my first cut at addressing the problems described in this
thread. As I discussed earlier, the VM syncer thread is likely starving
the USB interrupt thread. This causes the shared usb+network
interrupt to remain masked, preventing
Mike Tancsa wrote:
At 03:15 PM 9/28/2006, O. Hartmann wrote:
/usr/src/sys/dev/usb/usb.c:282: error: for each function it appears in.)
/usr/src/sys/dev/usb/usb.c: At top level:
/usr/src/sys/dev/usb/usb.c:863: warning: 'usb_intr_task' defined but
not used
*** Error code 1
Are you sure the
Albert Chin wrote:
I have an Intel S875PWP1 motherboard with a Pentium4 [EMAIL PROTECTED] PCI
bus is 33Mhz, 32-bit. I recently purchased an LSI 320-2/128MB on eBay
(though the card really looks like a PERC4/DS) and just ran some
bonnie++ tests on a RAID 1 array between two U320 drives for the
Craig Boston wrote:
On Thu, Sep 28, 2006 at 01:48:42PM -0600, Scott Long wrote:
http://people.freebsd.org/~scottl/usb_fastintr_RELENG_6.diff
At first glance it appeared to work, but I'm about to do some more
testing since I just discovered that I have to kldload something
(anything) first
David G Lawrence wrote:
Attached is a simple user program that will immediately cause pretty much
all of the network drivers (at least the ones I own) to stop working and
get watchdog timeouts.
I am runnign this on a single processor machine with an SMP kernel and
it does not have any
Martin Nilsson wrote:
Just an observation.
All the boxes I've had this problem on have _two_ em interfaces. I have
never seen it on my boxes with just one em NIC.
The error is always em0 timeout - never em1 (I haven't seen any!)
Yesterday my local network got completely wacky, the gateway
John Marshall wrote:
$ dmesg | grep bge
bge0: Broadcom BCM5705K Gigabit Ethernet, ASIC rev. 0x3003 mem
0xe820-0xe820 irq 17 at device 4.0 on pci4
miibus1: MII bus on bge0
bge0: Ethernet address: 00:0b:cd:e7:51:ba
bge0: watchdog timeout -- resetting
bge0: link state changed to DOWN
bge0:
David G Lawrence wrote:
Very interesting data point. I wonder if this accounts for some of the
inconsistency in the reporting from others. In any case, SCHED_ULE is
still considered to be highly experimental. Hopefully it will get some
more attention in the near future to bring it closer to
Guy Brand wrote:
Craig Boston ([EMAIL PROTECTED]) on 29/09/2006 at 20:19 wrote:
One thing this patch definitely did do though, is break the nvidia
driver pretty badly. Couldn't keep the X server running for more than a
minute before it froze solid. Lots of Xid: blah blah blah messages.
Yes
All,
I'm seeing some patterns here with all of the network driver problem
reports, but I need more information to help narrow it down further.
I ask all of you who are having problems to take a minute to fill
out this survey and return it to Kris Kennaway (on cc:) and myself.
Thanks.
1. Are
Bill Moran wrote:
I've copied many of the people who I've been working with directly on
this issue.
Can anyone provide a status update on these problems? Discussion seems
to have stopped since Oct 5.
Any new patches to test?
I'm actively working on fixing the driver right now.
Scott
Yeah, the error is probably a PCI error coming from the chipset,
not a RAM error. Unfortunately, there are a lot of mystery reasons
why a PCI error might get triggered, and the message isn't enough
to say what exactly it is. However, one simple test you can to
is to disable the EISA device in
Tom Judge wrote:
Scott Long wrote:
Bill Moran wrote:
I've copied many of the people who I've been working with directly on
this issue.
Can anyone provide a status update on these problems? Discussion seems
to have stopped since Oct 5.
Any new patches to test?
I'm actively working
Mike Tancsa wrote:
At 10:34 PM 10/5/2006, Kris Kennaway wrote:
Based on successful testing on a machine with shared em interrupt, the
following patch should work around the problem *in that case*.
Note that this patch will not help you if you are not using the em
driver, or if you are seeing
Mike Tancsa wrote:
At 08:09 AM 10/14/2006, Balgansuren Batsukh wrote:
Hello,
I installed FreeBSD-6.1 on my home PC. After sometime frequently get
em0 UP/DOWN message.
There is a patch you can try that might help you at
Danial Thom wrote:
--- Mark Linimon [EMAIL PROTECTED] wrote:
On Sun, Oct 15, 2006 at 07:57:32AM -0700,
Danial Thom wrote:
Stating facts is not trolling.
true, but ...
The fact that you may not want to hear it is
your own problem [...]
You can't keep promoting this junk they're
putting
Conrad Burger wrote:
Hi
It looks like there is a new version of the bce driver in HEAD.
When will it be incorporated into Releng_6?
It will be merged when someone, preferably 2-3 people, tell me that
the changes in HEAD work for them. So far, no one has.
Scott
Kevin Kramer wrote:
and will it support the BCM5754 in the Precision 390?
No idea, ask the vendor.
Scott
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL
Tom Judge wrote:
Kris Kennaway wrote:
On Wed, Oct 18, 2006 at 06:15:14PM +0100, Jason Thomson wrote:
Using the driver from HEAD* in the latest RELENG_6 didn't fix our
problems.
We could still trigger the Watchdog timeout when copying a local file to
an NFS mounted filesystem (UDP mount,
Bill Paul wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
On 10/19/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
The engineer in our test group has installed 6.2 BETA2 and attempted via a
number of tests to reproduce
Bill Paul wrote:
Yes, but did you do it with a Smartbits though, or just with a couple of
other FreeBSD machines? Unfortunately, a typical FreeBSD system on its own
won't generate frames anywhere near fast enough to really torture test a
gigE interface. At best you might hit around 20 to
Bill Moran wrote:
In response to Jason Thomson [EMAIL PROTECTED]:
Scott Long wrote:
Conrad Burger wrote:
Hi
It looks like there is a new version of the bce driver in HEAD.
When will it be incorporated into Releng_6?
It will be merged when someone, preferably 2-3 people
of the threads
regarding Broadcom issues.
--
Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.com
Scott Long wrote the following on 10/18/06 10:26:
Kevin Kramer wrote:
and will it support the BCM5754 in the Precision 390
odd though, is that copying +100 gig of data from
nfs to the 2950 which it was doing previously didn't lock things up
with the old driver.
My thanks to Scott Long and all others who worked on this!
Regards,
Ruben van Staveren
~BAS
On Mon, 23 Oct 2006, Bill Moran wrote:
In response
Lawrence Farr wrote:
I'd like to install stable directly onto a 6Tb Areca array, and
have run out of clues how to do it. In the past I've always
used a separate boot volume that was small enough for sysinstall
to work with, but I have no space to fit more drives in this
chassis. I've tried
Sam Baskinger wrote:
Bill Moran wrote:
[snip]
The driver from HEAD (if_bce.c 1.17) is looking much better - thanks
Scott!
We couldn't trigger this bug using UDP NFS mounts.
Neither could we trigger it with multiple simultaneous TCP connections.
I'm seeing similar improvement. I've been
Stefan Bethke wrote:
Am 25.10.2006 um 19:36 schrieb Robert Watson:
On Wed, 25 Oct 2006, Stefan Bethke wrote:
We're consistely getting this panic even under smallish loads. I've
experimented with various values for VM_KMEM_SIZE_MAX (384, 512, 768
and 1024 MB), but the boxes are still
post from Chris Knight in January, but he was on 6 and that was apparently right at a change to the aac driver. Searching FreeBSD.org turned up a similar problem back in March 2004 [5.2.1]. Scott Long responded to that one as a known issue being resolved.
The BIOS firmware was 'Build 7244
Josh Paetzel wrote:
On Wednesday 25 October 2006 19:24, Scott Long wrote:
Sam Baskinger wrote:
Bill Moran wrote:
[snip]
The driver from HEAD (if_bce.c 1.17) is looking much better -
thanks Scott!
We couldn't trigger this bug using UDP NFS mounts.
Neither could we trigger it with multiple
Glen Van Lehn wrote:
Scott Long [EMAIL PROTECTED] 10/25/06 7:36 PM
Glen Van Lehn wrote:
Hi, I'm new to the FreeBSD lists, and still uncertain on protocol.
I posted this today on the freebsd-hardware list, but from the discussion I'm
seeing today, it may better apply to 5-stable than
All,
Now that 5.3 is about to be released (really, I mean it this time!) and
5.x is considered -STABLE, further 5.x discussions and bug reports
should migrate over to the freebsd-stable mailing list. I know that
after 4+ years, there is probably a lot of sentimental attachment to
Mike Tancsa wrote:
At 05:04 PM 11/07/2005, Robert Watson wrote:
As a further FYI, a variety of debugging features are still enabled by
default in RELENG_6, including INVARINTS, WITNESS, and user space
malloc debugging. These will remain enabled through the first
snapshot from the
Apart
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.0-BETA1, which marks the beginning of the
FreeBSD 6.0 Release Cycle.
FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 branch
than the FreeBSD 5 branch was from
Marc G. Fournier wrote:
And, for the stupid question of the day ... how long before 5.x is no
longer supported? I'm just about to deploy a new server, and was
*going* to go with 5.x, but would I be better just skipping 5.x
altogether? Or are there such drastic changes in 6.x that doing so
Wilko Bulte wrote:
On Sat, Jul 16, 2005 at 06:33:24PM -0400, Garance A Drosihn wrote..
At 1:06 PM +0200 7/16/05, Øystein Holmen wrote:
I was looking for a place to download 6.0-BETA1-powerpc-bootonly.iso
to test om my PowerMac G4. But I cannot find it on any of
the ftp-sites og mirrors.
.
Thanks Robert Watson and Scott Long for their kind help.
Open tasks:
1. When writing the document, try to figure out the sebsd userland
utils that need to be ported.
2. Test and edit more policies for BSD environment
fbsd wrote:
Hello All,
For 5.4, FreeBSD AMD64 (and i386) is not able to recognize my diamond-max 160G
SATA drives on a Supermicro 6024H-T / X6DHT-G board with the default Marvell H2
SATA ctrl'r. There are SATA drivers for RH, FC3 and Windows from Supermicro:
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.0-BETA4.
ISO images are available for i386, amd64, pc98, alpha, powerpc, and
ia64 architectures. sparc64 is still in the process of being built
and will be uploaded as soon as
All,
It looks like I accidentally put amd64 packages onto the
i386 ISO images. I'm generating new ISOs and will upload
then as soon as possible. This likely explians the problems
with installing X11 from the ISO. Sorry for the confusion.
Scott
Scott Long wrote:
Announcement
This is a well known problem. A fix is hopefully being worked on.
Scott
Slawek Zak wrote:
Hi,
A panic occured on tmpfs overfill. /tmp with tmpmfs was configured for
100MB size. Backtrace from debugger:
db where
Tracing pid 60288 tid 100299 td 0xff02c3cba980
putc() at putc+0xa9
All,
I've turned off kernel deubgging (INVARIANTS, WITNESS, KDB) and malloc
debugging (the default is now 'aj) in the RELENG_6 branch in preparation
for 6.0-BETA5. I've also turned off SMP in the i386 and amd64 GENERIC
kernels and have added and SMP kernel config for those architectures.
All of
Paul T. Root wrote:
In the past, x.0 releases are meant for the adventurous
not the production oriented.
I never go before x.1. And I skipped 3.x completely.
I just got my final server from 4.11 to 5.4 in July.
6.x is probably still 9-12 months away from prime time.
But that's just a guess on
Christoph Sold wrote:
Hi All,
trying to install 6-stable in a VMWare 4.5.2 WS installation, running on
an 1.6 GHz Celeron CPU.
After 3 hours, it still extracts scontrib into /usr/src directory.
On tty 3, top tells cpio ist in vlruwk state for ages.
CPU states: 0.1% user, 0.0% nice, 0.4%
Sorry, but I really cannot imagine what is going on here. According to
the messages, the card seems to have crashed. You're using firmware rev
7244 on it, and I can't say that I've ever been happy with the 7xxx
series firmware. Would it be possible to back down to rev 6011? I
believe that you
Tuomo Latto wrote:
Alexander S. Usov wrote:
Just pointed firefox to freebsd.org and I was greeted with a new look!
...
And in general, I have already heard from quite a lot of people today that
the old design was quite authentic and recognizable, while the new one
looks as a quite standard
Announcement
The release engineering team is proud to announce the availability of
FreeBSD 6.0.
We encourage everyone to help with testing so any final bugs can be
identified and worked out. Availability of ISO images is given below.
If you have an older system you want to
All,
Wanted to let everyone know that the testing on RC1 has gone well enough
that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone
that we have talked to has applauded the stability and functionality of
the system, so we are really pleased and really eager to wrap it up and
Marcin Jessa wrote:
On Thu, 27 Oct 2005 20:09:36 +0200
Felipe Alfaro Solana [EMAIL PROTECTED] wrote:
Wanted to let everyone know that the testing on RC1 has gone well
enough that we've decided to skip RC2 and go straight to
6.0-RELEASE. Everyone that we have talked to has applauded the
Vladimir Sharun wrote:
What about Gleb Smirnoff NFS locking leak patch ? I put it on
production, everything works just fine. The question is: this
patch will be merged to main source tree for 6.0-RELEASE ?
Scott Long wrote:
SL Wanted to let everyone know that the testing on RC1 has gone well
Felipe openglx wrote:
On 10/27/05, Scott Long [EMAIL PROTECTED] wrote:
All,
Wanted to let everyone know that the testing on RC1 has gone well enough
that we've decided to skip RC2 and go straight to 6.0-RELEASE. Everyone
that we have talked to has applauded the stability and functionality
Marc Olzheim wrote:
On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote:
Everyone is still welcome to update their sources on the RELENG_6_0
branch and provide feedback for the next 48 hours or so. The release
will likely be announced by the end of the weekend or early next
week
Warner Losh wrote:
The ACPI+sio problem is known. I have a motherboard with a similar
problem, though a different brand than yours. I solved it by removing
the ACPI attachment from the sio code. The better solution is to allow
loader hints to override ACPI hints. I tried talking to John
Marc Olzheim wrote:
On Tue, Nov 01, 2005 at 06:33:21PM +0600, Max Khon wrote:
Hi!
On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote:
Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb
The program no longer exists. problem for me on RELENG_6.
Well, yes, but
The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!,
Sentex Communications, and SPARTA.
The release engineering team for 6.0-RELEASE includes:
Scott Long [EMAIL PROTECTED] Release Engineering,
I386 and AMD64 Release Building
Ken Smith
Boris Samorodov wrote:
Remove CC: to current. ;-)
On Fri, 04 Nov 2005 08:40:58 -0700 Scott Long wrote:
It is my great pleasure and privilege to announce the availability of
FreeBSD 6.0-RELEASE.
[skip]
Typo at http://www.freebsd.org/releases/6.0R/announce.html:
-
Date: Fri, 04 Oct 2005
Joerg Pulz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
I'm running an Fujitsu-Siemens Primergy RX300 dual-XEON hyperthreading
enabled server with an onboard LSI MegaRAID controller and an Adaptec
39320A Ultra320 dual channel SCSI adapter. The LSI MegaRAID controller
is
Goran Gajic wrote:
Hi,
I don't know if this is known, but when I have tried compiling PAE kernel
with SMP enabled on 6.0-RELEASE I've got this mistake:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual
Nate Lawson wrote:
Here is a patch that should fix the battery hangs on RELENG_6. It was
tested to work fine, although I need testing from an affected user to
verify it fixes the problem. It was committed to HEAD and will be MFCed
if it fixes the problem.
Thanks a lot!
I'm a bit
Sergey N. Voronkov wrote:
Looks like it is broken for a while - _sym_calloc2: failed to allocate HCB
is always there...
And... Looks like Gerard Roudier havn't more interest in maintaining this
driver - there is the second generation of the original driver into linux
source three since 2001,
get any kind of error messages, so I haven't had
much luck in tracking it down.
With help from Scott Long and John Baldwin, i have my system up and
running again without problems.
You should build your own kernel which should have
options MUTEX_NOINLINE
in the kernel configuration
Thomas E. Zander wrote:
Hi,
just installed a fresh 6.0 on a laptop, using the standard boot
manager. The problem is: The default volume of pcspeaker can't be tuned
in bios or anywhere else before loading a sound driver (in this case
snd_ich). This especially means the pc speaker volume is
Wilko Bulte wrote:
On Fri, Dec 09, 2005 at 07:49:33AM -0700, Scott Long wrote..
Thomas E. Zander wrote:
Hi,
just installed a fresh 6.0 on a laptop, using the standard boot
manager. The problem is: The default volume of pcspeaker can't be tuned
in bios or anywhere else before loading a sound
jonathan michaels wrote:
On Fri, Dec 09, 2005 at 05:38:43PM +0100, Thomas E. Zander wrote:
On Fri, 09. Dec 2005, at 16:00 +, David Malone wrote
according to [Re: Boot manager beep]:
On Fri, Dec 09, 2005 at 08:43:14AM -0700, Scott Long wrote:
It is highly irritating for everyone else
Gleb Smirnoff wrote:
On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote:
F I triggered a few reproducible panics on FreeBSD 6.0-STABLE.
F
F I created a ramdisk with:
F
F /sbin/mdconfig -a -t malloc -s 256M -u 10
F /sbin/newfs -U /dev/md10
F /sbin/mount
Kevin Oberman wrote:
I recently upgraded my last desktop system from 4.11-Stable to
6.0-Stable. I did an update to 5.3 then to RELENG_5,
RELENG_6_0_0_RELEASE and on to RELENG6_0.
This system has been updated regularly from the days of at least 4.1.
The hardware is a 1GHz PIII with an ICH2
Jonathan Noack wrote:
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never realized
All,
The following is the approximate schedule for FreeBSD releases in 2006:
Jan 30: Freeze RELENG_5 and RELENG_6
Mar 20: Release FreeBSD 6.1
Apr 3: Release FreeBSD 5.5
Jun 12: Freeze RELENG_6
Jul 31: Release FreeBSD 6.2
Oct 23: Freeze RELENG_6
Dec 11: Release FreeBSD 6.3
A 'freeze' means
Gary Kline wrote:
On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote:
All,
The following is the approximate schedule for FreeBSD releases in 2006:
Jan 30: Freeze RELENG_5 and RELENG_6
Mar 20: Release FreeBSD 6.1
Apr 3: Release FreeBSD 5.5
Jun 12: Freeze RELENG_6
Jul 31: Release
1 - 100 of 467 matches
Mail list logo
