jason wrote:
At some point in the last couple of weeks postfix on my 5.4-RELEASE
system stopped logging to /var/log/maillog. The only thing in there
now (and for all of the saved maillog files) is the turnover
timestamp. Any suggestions where to look?
Short answer - check:
a) syslogd
On Sun, Apr 23, 2006 at 12:04:33PM -0700, Bradley W. Dutton wrote:
+ Hi,
+
+ I'm experiencing a sort of livelock on a 6.1 prerelease box. It appears
+ all of the IO related activity hangs but the box continues to do
+ routing/NAT/etc for internet access from my other boxes. I can usually
+ get
On Wed, 2006-04-26 at 10:30 -0700, Sam Leffler wrote:
There are known locking bottlenecks in the crypto subsystem that fast
ipsec depends on. This is consistent with idle time going up.
Not sure when they'll be fixed but I know they're important to at least
one person.
Sorry to correct
... to at least three persons :)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hello!
I've done simple (yet, I hope, reality-reflecting) performance benchmarking
different STABLE branches (4 vs 5 vs 6) using the following hardware:
CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU)
Origin = GenuineIntel Id = 0x665 Stepping = 5
This card is based on a Silicon Image chip. You might as well
chuck the card I have never got a machine stable with one of these
controllers, I tried three cards all based on this chip, including an
Adaptec 1210SA. All the same, completely unstable.
I suggest you acquire one of these
Colleagues,
what should I do to drift serial console from sio0 to sio4 on puc (alas, com1
is broken on given motherboard, and there is no com2)? Quick googling and
looking through the Handbook does not help much.
Thanks in advance.
Sincerely,
D.Marck
On Thu, Apr 27, 2006 at 08:16:42PM +0400, Dmitry Morozovsky wrote:
Colleagues,
what should I do to drift serial console from sio0 to sio4 on puc (alas, com1
is broken on given motherboard, and there is no com2)? Quick googling and
looking through the Handbook does not help much.
look like
On Thu, 27 Apr 2006, Dmitriy Kirhlarov wrote:
DK what should I do to drift serial console from sio0 to sio4 on puc (alas,
com1
DK is broken on given motherboard, and there is no com2)? Quick googling and
DK looking through the Handbook does not help much.
DK
DK look like impossible.
DK
DK
On Thu, Apr 27, 2006 at 08:16:42PM +0400, Dmitry Morozovsky wrote:
Colleagues,
what should I do to drift serial console from sio0 to sio4 on puc (alas, com1
is broken on given motherboard, and there is no com2)? Quick googling and
looking through the Handbook does not help much.
Thanks
On Thu, Apr 27, 2006 at 08:55:35AM +0200, Pawel Jakub Dawidek wrote:
+ On Sun, Apr 23, 2006 at 12:04:33PM -0700, Bradley W. Dutton wrote:
+ + Hi,
+ +
+ + I'm experiencing a sort of livelock on a 6.1 prerelease box. It appears
+ + all of the IO related activity hangs but the box continues to do
+
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:
makeoptions CONF_CFLAGS=-fno-builtin
Non-default option; this may conceivably affect performance.
options INVARIANTS
options INVARIANT_SUPPORT
These definitely effect performance, much more in 5.x and 6.x
Pawel Jakub Dawidek wrote:
Flags field suggest that you were giving the passphrase on boot, before
root file system was mounted. Is that right?
Yes. That's correct.
Can you enter DDB, look for g_event and g_eli_worker processes PIDs in
'ps' output and send me the output of 'trace pid' for
Kris Kennaway a écrit :
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:
options QUOTA
This definitely effects performance on 6.x since it makes your
filesystem giant-locked, which may also interfere with your network
processing.
Why would QUOTA affect
On Thu, Apr 27, 2006 at 08:26:06PM +0200, [EMAIL PROTECTED] wrote:
Kris Kennaway a ?crit :
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:
options QUOTA
This definitely effects performance on 6.x since it makes your
filesystem giant-locked, which may also
Hi,
first of all a big thanks for your reply.
* Bruno Ducrot [EMAIL PROTECTED] wrote:
On Fri, Apr 21, 2006 at 04:11:00PM +, Stefan 'Steve' Tell wrote:
powernow0: PowerNow! K7 on cpu0
powernow0: ACPI MAX frequency not found
powernow0: no match for extended cpuid 780
Maybe
On Thu, Apr 27, 2006 at 08:22:08PM +0200, Martin wrote:
+ Pawel Jakub Dawidek wrote:
+ Flags field suggest that you were giving the passphrase on boot, before
+ root file system was mounted. Is that right?
+
+ Yes. That's correct.
+
+ Can you enter DDB, look for g_event and g_eli_worker
Kris Kennaway a écrit :
On Thu, Apr 27, 2006 at 08:26:06PM +0200, [EMAIL PROTECTED] wrote:
Kris Kennaway a ?crit :
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:
options QUOTA
This definitely effects performance on 6.x since it makes your
filesystem
You wrote that Giant is needed in 6.0 and now you write it has been
removed.
In 4.x, every UFS write requires the Giant lock. In 6.x, Giant is not
normally required, making file system operations faster. When you enable
QUOTA, you basically get back to the 4.x behavior where Giant is needed
Bartosz Fabianowski wrote:
You wrote that Giant is needed in 6.0 and now you write it has been
removed.
In 4.x, every UFS write requires the Giant lock. In 6.x, Giant is not
normally required, making file system operations faster. When you
enable QUOTA, you basically get back to the 4.x
On Thu, Apr 27, 2006 at 03:47:37PM -0400, Mike Jakubik wrote:
Bartosz Fabianowski wrote:
You wrote that Giant is needed in 6.0 and now you write it has been
removed.
In 4.x, every UFS write requires the Giant lock. In 6.x, Giant is not
normally required, making file system operations
Kris Kennaway wrote:
On Thu, Apr 27, 2006 at 03:47:37PM -0400, Mike Jakubik wrote:
Why isn't QUOTA mpsafe then?
Because code doesn't grow on trees. There are uncommitted patches
though - perhaps you can test them and get back to the author with
your feedback.
What? There is a
On Thu, Apr 27, 2006 at 04:43:07PM -0400, Mike Jakubik wrote:
Kris Kennaway wrote:
On Thu, Apr 27, 2006 at 03:47:37PM -0400, Mike Jakubik wrote:
Why isn't QUOTA mpsafe then?
Because code doesn't grow on trees. There are uncommitted patches
though - perhaps you can test them and
On Apr 27, 2006, at 11:12, Kris Kennaway wrote:
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:
options QUOTA
This definitely effects performance on 6.x since it makes your
filesystem giant-locked, which may also interfere with your network
processing.
Any
Hi List,
To get the above to work I had to add
#define NFORCE_MCPNET12_DEVICEID 0x0269
if_nvereg.h
and
{NVIDIA_VENDORID, NFORCE_MCPNET12_DEVICEID,
NVIDIA nForce MCP51 Networking Adapter},
if_nve.c
For anyone that cares.
Regards,
Steve
--
They that give up essential liberty
Ok, I had already installed and booted the first patch. I then rebuilt the
kernel with the second patch. Trying to reboot from the first patch to the
second resulted in a crash/panic on shutdown. I didn't capture the output
from this. Once I booted the second patch the machine panics in the boot
On Thu, Apr 27, 2006 at 01:57:02PM -0700, Doug Hardie wrote:
On Apr 27, 2006, at 11:12, Kris Kennaway wrote:
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:
options QUOTA
This definitely effects performance on 6.x since it makes your
filesystem giant-locked,
Hello,
I'm trying to upgrade from 5-stable to 6-stable; after rebooting to the
new kernel, the amr(4) module (amr.ko) refuses to load with this message:
link_elf: symbol cam_simq_alloc undefined
However, a quick nm(1) on /boot/kernel/cam.ko does show:
...
f0ac T
Eugene M. Kim wrote this message on Thu, Apr 27, 2006 at 19:55 -0700:
I'm trying to upgrade from 5-stable to 6-stable; after rebooting to the
new kernel, the amr(4) module (amr.ko) refuses to load with this message:
link_elf: symbol cam_simq_alloc undefined
However, a quick nm(1) on
Well I don't know what was going on earlier but I reverted to good kernel,
synced my raid arrays (no longer degraded from the panics), then booted a
kernel with the second patch applied, this time no problems so far. I'll
let you know how things go after the box is running for a while.
Thanks,
Thanks, that fixed it! : )
scottl: Could you commit (and MFC) the fix? It's as simple as adding a
MODULE_DEPEND line:
MODULE_DEPEND(amr, cam, 1, 1, 1);
after the DRIVER_MODULE line in src/sys/dev/amr/amr_pci.c
I'm not sure about amr_linux though; it seems that there's no CAM
Hi,
I broke the amr_cam interface several months ago when I locked the
driver. I've been neglecting it ever since due to lack of time, and due
to the amr_cam interface not being terribly useful. If you do in fact
have a use for it, let me know and I'll add it to my TODO list.
Scott
Eugene
Oh, I see. The fix was just to make it work as a KLD, because as it
stands now I can't load the module even though I don't use the CAM
portion of it.
Separating the amr_cam interface into a compatibility layer (like
atapicam) would probably be better... I'll see if I can do it whenever
I find
If anyone was using a bfe card and seeing interrupt storms when you
attempted to bring the card up, this is the fix for you. The driver
wasn't previously taking into account the fact that the chipset doesn't
like addresses over the 1GB mark.
If you'd like an even quicker fix, just add
34 matches
Mail list logo
