On 07/02/2011 04:12, Daniel O'Connor wrote:
>
> On 07/02/2011, at 13:02, Ivan Voras wrote:
I'll be looking at it on Monday, I will let you know :)
>>>
>>> No luck with mlock() so it wouldn't appear to be paging is the issue :(
>>
>> I'm also interested in raw device vs file system access!
>
>
On 07/02/2011, at 21:07, Ivan Voras wrote:
>>> I'm also interested in raw device vs file system access!
>>
>> Oops, sorry.. I just tried that now but it doesn't improve things :(
>
> Meaning: you still get jitter?
Yes, well I didn't measure the read frequency but it dropped out (stopped
stream
On 7 February 2011 13:38, Daniel O'Connor wrote:
>>> I am writing directly to /dev/ad10 but stressing /dev/ad14 (sudo tar -cf
>>> /dev/null /local0)
>>
>> Can you do only one of those things? I.e. leave all the file systems
>> alone and just do something like 'diskinfo -vt /dev/ad14'?
>
> OK, I
On 07/02/2011, at 23:36, Ivan Voras wrote:
>> OK, I wrote the data to /dev/null from USB and ran diskutil in a loop and it
>> doesn't drop out.
>
> Maybe I misunderstood you and it's a different problem than what I was
> experiencing; is this a better description of your problem:
>
> 1) you hav
On 22 January 2011 00:43, Alan Cox wrote:
> On Fri, Jan 21, 2011 at 2:58 PM, Alan Cox wrote:
>>
>> On Fri, Jan 21, 2011 at 11:44 AM, John Baldwin wrote:
>>>
>>> On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
>>> > Hello.
>>> >
>>> > Some time ago I faced with a problem booting w
Does anyone know why boot0sio would wait about 1 minute before proceeding?
If this is a known issue I can't find anything about it. I know there is a bug
with boot0cfg not changing the partition to boot to. Don't know if this is
related.
FreeBSD 8.2RC2 i386. Boot blocks were compiled with s
On 01/14/2011 09:42, Warner Losh wrote:
On 01/14/2011 01:28, Kostik Belousov wrote:
On Thu, Jan 13, 2011 at 04:34:22PM -0700, Warner Losh wrote:
On 01/13/2011 13:28, Kostik Belousov wrote:
On Thu, Jan 13, 2011 at 12:19:00PM -0500, Ryan Stone wrote:
I've been trying to get an application compil
Robert writes:
Why would doing a printf(9) in a device driver (usb, firewire,
probably
others) cause an obscenely long lockout on
/usr/src/sys/kern/uipc_sockbuf.c:148 (sx:so_rcv_sx) ?
Printf(9) alone isn't the problem, adding printfs to chown(2) does
not
cause the problem, but printfs from
I received a suggestion to try witness, so I build a kernel with
WITNESS, WITNESS_KDB, KDB, DDB, KDB_TRACE, and DDB_NUMSYM.
This is my first attempt to use witness, so if I got something wrong
let me know. Didn't quite make it all the way up to a multiuser prompt:
Starting syslogd.
Starting rpcb
9 matches
Mail list logo
