Freddie,
On Wed, Mar 27, 2013 at 04:10:03PM -0700, Freddie Cash wrote:
F> Just curious if anyone has any scripts for managing fail-over of multiple
F> interfaces using the new CARP setup in 10-CURRENT.
F>
F> Fail-over of all CARP vhids associated with a single interface is working
F> correctly.
TB --- 2013-04-02 07:42:29 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-04-02 07:42:29 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Hi all,
On behalf of monthly@, I would like to inform you that the next
submission date for the January to March quarterly status reports is
April 21st, 2013 - less than a month away.
They don't have to be very long - anything that lets people know what
is going on inside FreeBSD is useful. Note
El día Monday, April 01, 2013 a las 10:25:46PM -0700, Kevin Oberman escribió:
> Good luck. I suspect a successful update of ptlib will be the real tricky
> part. At least it gave me headaches back when I was using Ekiga.
PTlib and opal are compiling fine directly from their SVN repositories;
> A
Hi Adrian,
Please find a patch which does two things:
>
>
patch was lost, apparently :)
thanks
max
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-
Hi Konstantin,
Am 2013-03-27 15:33, schrieb m...@kernel32.de:
Am 2013-03-27 14:32, schrieb Konstantin Belousov:
Do you use preload md(4) ? If yes, try the following patch:
Not sure whether time permits that today, but I'm starting right
away.
Had no time before easter, but I tried it n
Am 31.03.2013 23:02, schrieb Scott Long:
> So what I hear you and Matthias saying, I believe, is that it should be
> easier to
> force disks to fall back to non-NCQ mode, and/or have a more responsive
> black-list for problematic controllers. Would this help the situation? It's
> hard to
> jus
On Tue, Apr 02, 2013 at 08:23:20PM +0200, m...@kernel32.de wrote:
> Hi Konstantin,
>
> Am 2013-03-27 15:33, schrieb m...@kernel32.de:
> > Am 2013-03-27 14:32, schrieb Konstantin Belousov:
> >>
> >> Do you use preload md(4) ? If yes, try the following patch:
> >>
> >
> >
> > Not sure whether time p
On 2 April 2013 10:21, Maksim Yevmenkin wrote:
> Hi Adrian,
>
>> Please find a patch which does two things:
>>
>
> patch was lost, apparently :)
Oh for gods sake. God damned mailing list setup.
I'll upload the patch soon.
adrian
___
freebsd-current@
Am 2013-04-02 21:52, schrieb Konstantin Belousov:
On Tue, Apr 02, 2013 at 08:23:20PM +0200, m...@kernel32.de wrote:
Root mount waiting for: usbus2
uhub5: 2 ports with 1 removable, self powered
Trying to mount root from ufs:/dev/md0 []...
start_init: trying /sbin/init
Good, thank you for testing
Hi again,
Am 2013-04-02 21:52, schrieb Konstantin Belousov:
On Tue, Apr 02, 2013 at 08:23:20PM +0200, m...@kernel32.de wrote:
Try breaking into the debugger and see where it progresses. To do
this,
you would need to boot with the 'boot -d' command from the loader
prompt,
then do 'w kbd_break_
On 1. 4. 2013 22:33, Martin Matuska wrote:
> This error seems to be limited to sending deduplicated streams. Does
> sending without "-D" work ok? This might be a vendor error as well.
>
> On 1.4.2013 20:05, Larry Rosenman wrote:
>> Re-Sending. Any ideas, guys/gals?
>>
>> This really gets in my way
As of r248872, my system, when ordered to power off, stalls at the "Uptime: [...]" message. Before
that revision, the "Uptime" message would be followed by several additional messages -- something
related to "usb controllers" -- before powering off.
__
My kernel configuration file:
cpu I686_CPU
options SCHED_ULE
options PREEMPTION
options INET
options FFS
options SOFTUPDATES
options UFS_DIRHASH
options MD_ROOT
options MSDOSFS
options CD9660
options GEOM_PART_GPT
options GEOM_LABEL
options COMPAT_FREEBSD4
options COMPAT_FREEBSD5
options COMPAT_F
On Wed, Apr 03, 2013 at 01:15:03AM +0200, deeptech71 wrote:
> As of r248872, my system, when ordered to power off, stalls at the "Uptime:
> [...]" message. Before that revision, the "Uptime" message would be followed
> by several additional messages -- something related to "usb controllers" --
>
On 4/2/13, m...@kernel32.de wrote:
> Hi again,
>
> Am 2013-04-02 21:52, schrieb Konstantin Belousov:
>> On Tue, Apr 02, 2013 at 08:23:20PM +0200, m...@kernel32.de wrote:
>>
>> Try breaking into the debugger and see where it progresses. To do
>> this,
>> you would need to boot with the 'boot -d' co
On 2013-04-02 1:52 AM, "Gleb Smirnoff" wrote:
>
> Freddie,
>
> On Wed, Mar 27, 2013 at 04:10:03PM -0700, Freddie Cash wrote:
> F> Just curious if anyone has any scripts for managing fail-over of
multiple
> F> interfaces using the new CARP setup in 10-CURRENT.
> F>
> F> Fail-over of all CARP vhid
On 2013-04-02 16:26, Martin Matuska wrote:
On 1. 4. 2013 22:33, Martin Matuska wrote:
This error seems to be limited to sending deduplicated streams. Does
sending without "-D" work ok? This might be a vendor error as well.
On 1.4.2013 20:05, Larry Rosenman wrote:
Re-Sending. Any ideas, guys/g
on 03/04/2013 02:15 deeptech71 said the following:
> As of r248872, my system, when ordered to power off, stalls at the "Uptime:
> [...]" message. Before that revision, the "Uptime" message would be followed
> by
> several additional messages -- something related to "usb controllers" --
> before
19 matches
Mail list logo
