My system has been working reliably with 6.3 for quite some time... when
I rebooted into single user mode to do the installworld with the
7.0-RELEASE kernel, the install died about halfway through with READ_DMA
TIMEOUT errors. Since I had a mixed system at that point, I set
hw.ata.ata_dma=0
Hello,
I updated a system with 12 dc-interfaces to a new hardware
with 14 em-interfaces. Yes, it is a firewall.
New System is 6.2-RELEASE-p8.
What I now experience between two internal networks (100MBit/s each)
is the following:
1318 packets transmitted, 1317 packets received, 0% packet loss
On Wed, Feb 27, 2008 at 01:11:36AM -0800, Stephen Hurd wrote:
... The corrupted sync message scared the heck out of me:
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiti
Synncgi n(gm adxi sk6s0, svencoodnedss )r efmoari nsiynsgte.m. .pr1o0c ess
`syncer' to stop...8 7
Andrew N. Below wrote:
RELENG_6 cvsuped at 2007-01-15
what should I check (source revisions) to ensure we have same bug?
This is a quite old version of FreeBSD. I don't know for sure if the bug
was fixed by that time, but you should update to newest RELENG_6 or
RELENG_6_3 to make sure.
On Wednesday 27 February 2008 07:49:42 Holger Kipp wrote:
Hello,
I updated a system with 12 dc-interfaces to a new hardware
with 14 em-interfaces. Yes, it is a firewall.
New System is 6.2-RELEASE-p8.
What I now experience between two internal networks (100MBit/s each)
is the following:
Hi,
I've just noticed a regression in tar from 6.2 to 6.3:
Running this on 6.2 produces no output:
#!/bin/sh
mkdir -p a b output
touch a/file1 b/file2
tar cf test.tar a b
tar -x -C output --strip-components 1 -f test.tar
On 6.3, it produces this output:
: Invalid empty pathname
: Invalid
Hi,
On Thu, Feb 28, 2008 at 12:09:50AM +1100, Jan Mikkelsen wrote:
And the tar extraction returns a failure.
I can confirm this does not work on 8-CURRENT either.
Is this known? Should I raise a PR?
That seems a good idea to me. Thanks!
--
Rink P.W. Springer
Jan Mikkelsen wrote:
Hi,
I've just noticed a regression in tar from 6.2 to 6.3:
Running this on 6.2 produces no output:
#!/bin/sh
mkdir -p a b output
touch a/file1 b/file2
tar cf test.tar a b
tar -x -C output --strip-components 1 -f test.tar
On 6.3, it produces this output:
: Invalid empty
At 05:49 AM 2/27/2008, Holger Kipp wrote:
I therefore assume that the problem is between receiving the
irq from emx and getting the data from the interface on the firewall
itself.
I would try upgrading to 6.3R (there are several em driver bug fixes)
and then try the box with
% cat
This isn't enough time. Please try this instead.
# /etc/rc.d/ntpd stop
# /etc/rc.d/ntpdate start
This should set your clock, even if only by a few milliseconds.
Assuming the ntpdate part is successful, continue on:
# tcpdump -l -n -s 8192 -p port 123
Now, in another window,
On Wed, Feb 27, 2008 at 09:58:28PM +0700, Pongthep Kulkrisada wrote:
[EMAIL PROTECTED]:~# /etc/rc.d/ntpdate start
Setting date via ntp.
27 Feb 20:46:53 ntpdate[2000]: no server suitable for synchronization found
[EMAIL PROTECTED]:~# tcpdump -l -n -s 8192 -p port 123
tcpdump: verbose output
Jim Pingle wrote:
Jim Pingle wrote:
I'm having some trouble with a SuperMicro SuperServer 6022L-6 that
previously ran 7.0-BETA4 without problems. Today, I updated this
machine to 7.0-PRERELEASE and now it will not fully boot unless I
disable ACPI. A quick search of the PR database didn't turn
Hi, all,
is there an exhaustive list of all possible NO_* knobs
for make.conf? While experimenting with NanoBSD I found
e.g. that the handbook
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html
mentions
NO_EXAMPLES
NO_SYSCONS
...
- just two out of many. Yet, these are not
On Wed, Feb 27, 2008 at 05:32:55PM +0100, Patrick M. Hausen wrote:
is there an exhaustive list of all possible NO_* knobs
for make.conf? While experimenting with NanoBSD I found
e.g. that the handbook
- just two out of many. Yet, these are not in the manpage of
make.conf(5) on a 6.3-RELEASE.
Jeremy Chadwick wrote:
And after the reboot, the READ_DMA timeouts were back.
You're not the only one seeing this behaviour. There are too many posts
in the past reporting similar. Here's the breakdown:
* Some have switched to alternate operating systems (usually Linux) for
a short
Olivier Mueller wrote:
fsck_ufs: cannot alloc 94208 bytes for inoinfo
This is what I get after about one hour while trying a fsck on a large
(1.4TB) partition broken since a power outage.
HW: HP DL380G5, under freebsd 6.1/i386, with 1GB of RAM and:
Your fsck will need roughly 1
Hello,
On Wed, Feb 27, 2008 at 09:18:31AM -0800, Jeremy Chadwick wrote:
I think you're looking for all the WITHOUT knobs in src.conf(5).
I'm running RELENG_6_3 on production machines unlikely to change
any time real soon.
Note that src.conf(5) does not apply to RELENG_6 or earlier, where the
On Wed, Feb 27, 2008 at 10:32:48AM -0800, Stephen Hurd wrote:
Booting the 6.3-RELEASE CD seems to make the problem go away... possibly
7.0 stresses the HD more?
We don't know. The author of the ATA subsystem is somewhat MIA, likely
busy with real-life things (jobs, etc.). My main point was
I've just noticed a regression in tar from 6.2 to 6.3:
Running this on 6.2 produces no output:
#!/bin/sh
mkdir -p a b output
touch a/file1 b/file2
tar cf test.tar a b
tar -x -C output --strip-components 1 -f test.tar
On 6.3, it produces this output:
: Invalid empty pathname
: Invalid empty
Stephen Hurd wrote:
Jeremy Chadwick wrote:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 253 253
On Wed, Feb 27, 2008 at 09:50:16AM -0500, Mike Tancsa wrote:
more details below. as it currently is, polling seems to do
the trick, however handling several em-interfaces with the
same irq (mind you, it is pci) shouldn't cause delays of
up to 1.5 seconds for a simple ping... Therefore I consider
fsck's memory usage is directly related to the number of inodes and
the number of directories in the filesystem. Directories are
particularly memory intensive.
I've found on my backup system that a UFS1 filesystem with 40 million
inodes is about the limit that can be
On Wed, Feb 27, 2008 at 08:50:58PM +0100, Holger Kipp wrote:
On Wed, Feb 27, 2008 at 09:50:16AM -0500, Mike Tancsa wrote:
more details below. as it currently is, polling seems to do
the trick, however handling several em-interfaces with the
same irq (mind you, it is pci) shouldn't cause
At 03:09 PM 2/27/2008, Holger Kipp wrote:
On Wed, Feb 27, 2008 at 08:50:58PM +0100, Holger Kipp wrote:
On Wed, Feb 27, 2008 at 09:50:16AM -0500, Mike Tancsa wrote:
more details below. as it currently is, polling seems to do
the trick, however handling several em-interfaces with the
same irq
Stephen Hurd wrote:
This shows you've had 4 reallocated sectors, meaning your disk does in
fact have bad blocks. In 90% of the cases out there, bad blocks
continue to grow over time, due to whatever reason (I remember reading
an article explaining it, but I can't for the life of me find the
On Wed, Feb 27, 2008 at 11:50 AM, Holger Kipp [EMAIL PROTECTED] wrote:
On Wed, Feb 27, 2008 at 09:50:16AM -0500, Mike Tancsa wrote:
more details below. as it currently is, polling seems to do
the trick, however handling several em-interfaces with the
same irq (mind you, it is pci)
On Wed, Feb 27, 2008 at 12:16:27PM -0800, Jack Vogel wrote:
Hmmm, something is really broken here that POLL just is just bypassing,
what was the adapter type exactly (pciconf -l). Sorry, but I must have
missed this email earlier.
Problem is with em0-em13 that many share an IRQ 16/17, and
Greetings. I was trying to install FreeBSD 7 on an old machine to make it a
fileserver. Machine is an AMD K7 1200 on an Abit AN-7 mobo (nforce2 400), which
has booted Freebsd 7.0 RC1 beforehand (for testing ZFS; only ACPI didn't work
as it hung it).
I recently bought a PCI SATA card on the
Tim Kientzle wrote:
Please file this in a PR so I won't lose
track. I don't have time to investigate this
right now, but I should be able to get to it
sometime next week.
Filed as PR bin/121158.
Thanks!
Jan.
___
freebsd-stable@freebsd.org
On Monday 18 February 2008 05:10:24 am Sergey Matveychuk wrote:
+stable@
Yoshihiro Ota wrote:
Why are so many people are bitten by this? Is that the jobs of
port-upgrading
tool to safe copy these libraries to compat so that all programs using
the old libraries works?
Portupgrade
On Saturday 23 February 2008 03:32:41 pm Dominic Fandrey wrote:
Oliver Herold wrote:
Hi
the Razer Copperhead mouse did work in FreeBSD 7 (current) for a long
time, but after some period it stopped working. This patch from Uwe
Grohnwaldt:
Jisakiel wrote:
Greetings. I was trying to install FreeBSD 7 on an old machine to make it a
fileserver. Machine is an AMD K7 1200 on an Abit AN-7 mobo (nforce2 400),
which has booted Freebsd 7.0 RC1 beforehand (for testing ZFS; only ACPI
didn't work as it hung it).
I recently bought a
Just in case some interested parties are not subscribed to the
freebsd-announce mailing list... FreeBSD 7.0-RELEASE has been formally
released. If you would like to see the release announcement it's here:
http://www.freebsd.org/releases/7.0R/announce.html
On behalf of the FreeBSD Project
Hi
this patch works (console, mousepointer) but it doesn't work in X.
ums0: Razer Razer Copperhead Laser Mouse, class 0/0, rev 1.10/21.00, ad
dr 3 on uhub0
ums0: 7 buttons and Z dir.
ukbd1: Razer Razer Copperhead Laser Mouse, class 0/0, rev 1.10/21.00,
addr 3 o
n uhub0
kbd3 at ukbd1
---
AUDIT:
Ken Smith [EMAIL PROTECTED] writes:
[...]
http://www.freebsd.org/releases/7.0R/announce.html
On behalf of the FreeBSD Project thanks for your interest in FreeBSD.
We hope you enjoy the new release.
Thanks for all your work (done and to be done).
Dirk
Scott Long wrote:
I'm betting that it's a driver problem and not
a hardware problem, though you should probably think about migrating
your data off to a new drive sometime soon.
Yeah, ordered a replacement drive today.
I'd like to attack these driver problems. What I need is to spend a
Scott Long wrote:
I'd like to attack these driver problems. What I need is to spend a
couple of days with an affected system that can reliably reproduce the
problem, instrumenting and testing the driver. I have a number of
theories about what might be going wrong, but nothing that I'm
Jisakiel wrote:
Is there any way to make this card work on FreeBSD 7, or anything
else that I could try?
Did you find any new BIOS versions for you motherboard?
--
WBR, Andrey V. Elsukov
___
freebsd-stable@freebsd.org mailing list
Ken Smith wrote:
Just in case some interested parties are not subscribed to the
freebsd-announce mailing list... FreeBSD 7.0-RELEASE has been formally
released. If you would like to see the release announcement it's here:
http://www.freebsd.org/releases/7.0R/announce.html
On behalf of the
On Wed, Feb 27, 2008 at 11:53:01AM -0800, Matthew Dillon wrote:
You can also reduce fsck time by reducing the number of cylinder
groups on the disk. I usually max them out (-c 999 and newfs then
sets it to the maximum, usually in the 50-80 range). This will
improve
I have just installed 7.0 on some new hardware. Have never tried
earlier versions. There are a couple of unexpected items that I do
not understand.
1. When booting there are a few messages like:
acd0: TIMEOUT - READ_BIG retrying
When the system is booted off CD (like
On Wed, Feb 27, 2008 at 11:15:30PM -0800, Doug Hardie wrote:
I have just installed 7.0 on some new hardware. Have never tried earlier
versions. There are a couple of unexpected items that I do not understand.
2. I have 2 SATA drives in the system. The first is recognized as ad10
and the
42 matches
Mail list logo
