on 14/05/2010 03:25 Giovanni Trematerra said the following:
Attilio and I came up with this patch. It seems ready for stress
testing and review
Please test and report back.
It seems that there is inconsistent indentation for some of new lines.
Original style seems to be softtabstop=4 tabstop=8
Postfix will re-write this as part of sanitization, so I had to revert
to creating mbox files by hand. Anyway, could you please test the
following patch with a wider variety of mails?
I've been testing your patch for a few weeks now as my main email
client, and I havent encountered any
Hi,
I'm trying to set ipv6 aliases for my jails in my rc.conf but it
doesn't seem to work as advertised. I have a /48 range assigned to me
(for this example 2001:dead:beef) and am trying to assign ipv6
addresses to a jail. The jails will all have ipv6 addresses in the
2001:dead:beef:1 range.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/2010 10:07:23, Spil Oss wrote:
I'm trying to set ipv6 aliases for my jails in my rc.conf but it
doesn't seem to work as advertised. I have a /48 range assigned to me
(for this example 2001:dead:beef) and am trying to assign ipv6
Thanks for the hints Matthew!
Cleaning up my config I found the culprit. Copied
ipv6_network_interfaces=gif0
from some guide which off course defeated all my efforts to configure
ipv6 on the other interfaces.
The ipv6_addrs_interface knob doesn't seem to work (this is 8.0-p2),
can't find
rihad wrote:
On 05/14/2010 04:13 AM, Doug Ambrisko wrote:
rihad writes:
| Hi, I'm thinking of enabling the watchdog on our Dell PowerEdge 2950 /
| FreeBSD 8.0 amd64, so that it reboots the machine in case of lockups.
| Right now it doesn't work:
|
| # watchdog
| watchdog: patting the dog:
Terry Kennedy wrote:
I'm reposting this over here at the suggestion of the Forums moderator.
The original post is at http://forums.freebsd.org/showthread.php?t=14163
Got an interesting crash just now (well, as interesting as a crash on a
soon-to-be production system can be).
This is
The crash was a page fault while in kernel mode with the current process
being the interrupt service routine for the bce0 GigE. Things progressed
reasonably until partway through the dump, when the system locked up with a
Sleeping thread (tid 100028, pid 12) owns a non-sleepable lock. That's
on 14/05/2010 09:42 Chris Buechler said the following:
one of our users has reported a regression in dc(4) on RELENG_8, the
cards work fine on 7.2 and previous versions, but no longer function at
all with RELENG_8 as of about a week ago.
On Fri, May 14, 2010 at 00:32, Fred Souza f...@storming.org wrote:
Good to know, I never really paid much attention to those details (I
will from now on). Thank you a lot for the help, Jeremy. I will try
your suggestions in the morning and post back to tell what did I find
out.
Like I said,
The crash was a page fault while in kernel mode with the current process
being the interrupt service routine for the bce0 GigE. Things progressed
reasonably until partway through the dump, when the system locked up with a
Sleeping thread (tid 100028, pid 12) owns a non-sleepable lock.
rihad writes:
| On 05/14/2010 04:13 AM, Doug Ambrisko wrote:
| rihad writes:
| | Hi, I'm thinking of enabling the watchdog on our Dell PowerEdge 2950 /
| | FreeBSD 8.0 amd64, so that it reboots the machine in case of lockups.
| | Right now it doesn't work:
| |
| | # watchdog
| | watchdog:
On Fri, May 14, 2010 at 07:16:28AM -0700, Doug Ambrisko wrote:
rihad writes:
| On 05/14/2010 04:13 AM, Doug Ambrisko wrote:
| rihad writes:
| | Hi, I'm thinking of enabling the watchdog on our Dell PowerEdge 2950 /
| | FreeBSD 8.0 amd64, so that it reboots the machine in case of lockups.
Hmm. You could try changing the code to not do a nested panic in that
case. You would update subr_turnstile.c to just return if panicstr is
not NULL rather than calling panic. However, there is still a good
chance you will end up deadlocking in that case. I have another patch I
can
On Fri, May 14, 2010 at 09:56:47AM -0400, Terry Kennedy wrote:
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular,
Tom Evans writes:
| On Fri, May 14, 2010 at 3:15 PM, Jeremy Chadwick
| free...@jdc.parodius.com wrote:
|
| I'm a bit confused at this point, Doug. ?At what point did the OP state
| he has IPMI support or IPMI cards in his system?
|
| He said he had a Dell PowerEdge 2950 - iirc these all have
On Fri, May 14, 2010 at 03:21:42PM +0100, Tom Evans wrote:
On Fri, May 14, 2010 at 3:15 PM, Jeremy Chadwick
free...@jdc.parodius.com wrote:
I'm a bit confused at this point, Doug. At what point did the OP state
he has IPMI support or IPMI cards in his system?
He said he had a Dell
On Fri, 14.05.2010 at 10:17:23 +0100, Pete French wrote:
Postfix will re-write this as part of sanitization, so I had to revert
to creating mbox files by hand. Anyway, could you please test the
following patch with a wider variety of mails?
I've been testing your patch for a few weeks
On Fri, May 14, 2010 at 3:15 PM, Jeremy Chadwick
free...@jdc.parodius.com wrote:
I'm a bit confused at this point, Doug. At what point did the OP state
he has IPMI support or IPMI cards in his system?
He said he had a Dell PowerEdge 2950 - iirc these all have IPMI.
Cheers
Tom
Do you feel strongly about merging the fix to 8 or 7 or both?
Not really - it;s such a small change that it would seem a shame
not to commit it to earlier releases, but then I used 7 thoughout
it;s lifetime with the bug only being a minor annoyance.
-pete.
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular, the shutdown makes a bunch of the behind the scenes man-
Matthew Fleming wrote:
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular, the shutdown makes a bunch of the
Hi list,
I'm running FreeBSD 8.0-RELEASE-p1 on a Dell R300 which has a ICH9 SATA
controller on-board (do not have the RAID controller).
The system has 2 disks in a gmirror setup. Every now and then, probably
under some load, one of the disks gets read or write timeouts like:
May 5 03:01:37
On Fri, May 14, 2010 at 12:42 PM, Pieter de Boer pie...@os3.nl wrote:
I'm running FreeBSD 8.0-RELEASE-p1 on a Dell R300 which has a ICH9 SATA
controller on-board (do not have the RAID controller).
The system has 2 disks in a gmirror setup. Every now and then, probably
under some load, one of
Adam Vande More wrote:
May 5 03:01:37 aberdeen kernel: ad4: timeout waiting to issue command
May 5 03:01:37 aberdeen kernel: ad4: error issuing WRITE_DMA48 command
May 5 03:01:37 aberdeen kernel: GEOM_MIRROR: Request failed (error=5).
ad4[WRITE(offset=200404975104, length=16384)]
May 5
Oops, youre right that other CPUs are running.
The stop_cpus() call is only made if kdb is entered. doadump() is called
out of boot() which comes later. At Isilon weve been running with a patch
that does stop_cpus() pretty close to the front of panic(9).
This is interesting, and
On Fri, May 14, 2010 at 07:42:33PM +0200, Pieter de Boer wrote:
Hi list,
I'm running FreeBSD 8.0-RELEASE-p1 on a Dell R300 which has a ICH9
SATA controller on-board (do not have the RAID controller).
The system has 2 disks in a gmirror setup. Every now and then,
probably under some load,
My question: does anyone have experience with FreeBSD on a Dell R300
or can anyone give me some help in trying to fix the timeouts?
Could you please do the following:
- Provide output from vmstat -i
- Provide output from dmesg | grep -i ata
- Install ports/sysutils/smartmontools (5.40 or
On Fri, May 14, 2010 at 11:09:28PM +0200, Pieter de Boer wrote:
The ad4 SMART output is showing errors, as this disk is indeed
broken now. It wasn't before and it is a replacement of another disk
that wasn't broken either. Grmbl, I now see reallocated sectors on
ad6 as well, in the smartctl
On Fri May 14 22:42:38 UTC 2010, Jeremy Chadwick wrote:
Finally, your vmstat -i output:
# vmstat -i
interrupt total rate
irq23: atapci0 371021299 10423
Good to know there's no IRQ sharing going on, but what does worry me is
the
TB --- 2010-05-15 02:06:57 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2010-05-15 02:06:57 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2010-05-15 02:06:57 - cleaning the object tree
TB --- 2010-05-15 02:07:27 - cvsupping the source tree
TB --- 2010-05-15 02:07:27 -
TB --- 2010-05-15 03:21:53 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2010-05-15 03:21:53 - starting RELENG_7 tinderbox run for i386/i386
TB --- 2010-05-15 03:21:53 - cleaning the object tree
TB --- 2010-05-15 03:22:18 - cvsupping the source tree
TB --- 2010-05-15 03:22:18 -
TB --- 2010-05-15 03:40:23 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2010-05-15 03:40:23 - starting RELENG_7 tinderbox run for i386/pc98
TB --- 2010-05-15 03:40:23 - cleaning the object tree
TB --- 2010-05-15 03:40:43 - cvsupping the source tree
TB --- 2010-05-15 03:40:43 -
On Fri, May 14, 2010 at 11:40:23PM -0400, FreeBSD Tinderbox wrote:
=== em (depend)
@ - /src/sys
machine - /src/sys/amd64/include
awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
ln -sf
TB --- 2010-05-15 04:29:04 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2010-05-15 04:29:04 - starting RELENG_7 tinderbox run for ia64/ia64
TB --- 2010-05-15 04:29:04 - cleaning the object tree
TB --- 2010-05-15 04:29:28 - cvsupping the source tree
TB --- 2010-05-15 04:29:28 -
35 matches
Mail list logo
