Hi,
it's been a while since this topic was touched, see
http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013129.html.
I coulnd't find anything more recent than the following commit, which
prints a warning message, if a suspectible CPU model is detected:
http://svn.freebsd.or
On Mon, 03 Jan 2011 22:21:51 +0300 Anonymous wrote:
> Bakul Shah writes:
>
> > On Mon, 03 Jan 2011 21:20:42 +0300 Anonymous wrote:
> >>=20
> >> Do you mean perror(1)?
> >>=20
> >> $ perror 5
> >> Input/output error
> >
> > I prefer mine:
> >
> > $ errno () { grep "^#.*\\<$*\\>" /usr/inclu
Bakul Shah writes:
> On Mon, 03 Jan 2011 21:20:42 +0300 Anonymous wrote:
>>
>> Do you mean perror(1)?
>>
>> $ perror 5
>> Input/output error
>
> I prefer mine:
>
> $ errno () { grep "^#.*\\<$*\\>" /usr/include/sys/errno.h }
> $ errno 5
> #define EIO 5 /* Input/ou
On Mon, 03 Jan 2011 21:20:42 +0300 Anonymous wrote:
>
> Do you mean perror(1)?
>
> $ perror 5
> Input/output error
I prefer mine:
$ errno () { grep "^#.*\\<$*\\>" /usr/include/sys/errno.h }
$ errno 5
#define EIO 5 /* Input/output error */
$ errno EIO
#define EIO
On Jan 3, 2011, at 10:20 AM, Anonymous wrote:
> Garrett Cooper writes:
>
>> On Jan 3, 2011, at 8:33 AM, Edward Tomasz Napierała
>> wrote:
>>
>>> Wiadomość napisana przez Kostik Belousov w dniu 2011-01-03, o godz. 15:18:
On Mon, Jan 03, 2011 at 02:16:37PM +0100, Matthias Andree wrote:
>>>
Garrett Cooper writes:
> On Jan 3, 2011, at 8:33 AM, Edward Tomasz Napierała wrote:
>
>> Wiadomość napisana przez Kostik Belousov w dniu 2011-01-03, o godz. 15:18:
>>> On Mon, Jan 03, 2011 at 02:16:37PM +0100, Matthias Andree wrote:
Am 03.01.2011 14:14, schrieb Ivan Voras:
> On 12/29/10
On Jan 3, 2011, at 8:33 AM, Edward Tomasz Napierała wrote:
> Wiadomość napisana przez Kostik Belousov w dniu 2011-01-03, o godz. 15:18:
>> On Mon, Jan 03, 2011 at 02:16:37PM +0100, Matthias Andree wrote:
>>> Am 03.01.2011 14:14, schrieb Ivan Voras:
On 12/29/10 11:32, David Demelier wrote:
>>
Wiadomość napisana przez Kostik Belousov w dniu 2011-01-03, o godz. 15:18:
> On Mon, Jan 03, 2011 at 02:16:37PM +0100, Matthias Andree wrote:
>> Am 03.01.2011 14:14, schrieb Ivan Voras:
>>> On 12/29/10 11:32, David Demelier wrote:
/var/log/messages.5.bz2:Nov 29 16:36:52 Abricot kernel:
g_
deliver better performance than h/w emulation.
http://ysr.jp/~hasegaw/virtio-20110103-2316.tar.gz
I'm sorry for very nasty code; I am newbie in both of C and
kernel-space code. ;)
Now I am suffering with performance problem with virtio-blk driver.
I've heard some people said FreeBSD's di
On Mon, Jan 03, 2011 at 02:16:37PM +0100, Matthias Andree wrote:
> Am 03.01.2011 14:14, schrieb Ivan Voras:
> > On 12/29/10 11:32, David Demelier wrote:
> >> /var/log/messages.5.bz2:Nov 29 16:36:52 Abricot kernel:
> >> g_vfs_done():ufs/public[READ(offset=232718991360, length=131072)]error
> >> = 5
Am 03.01.2011 14:14, schrieb Ivan Voras:
> On 12/29/10 11:32, David Demelier wrote:
>> Hello,
>>
>> Sometimes when I use my external harddrive I get these awful message :
>>
>> g_vfs_done():da1[WRITE(offset=34590720, length=65536)]error = 5
>> /var/log/messages.1.bz2:Dec 21 18:36:07 Abricot kernel:
Hello,
SOLVED ! But the problem was in another place.
Host world and kernel were build with src r215329 (patched with
head-v28-v2.patch from Martin Matuska), but ezjail buildworld was made using
more recent sources with no patch (in fact I was trying to apply the same
patch to more recent sources
On 12/29/10 11:32, David Demelier wrote:
Hello,
Sometimes when I use my external harddrive I get these awful message :
g_vfs_done():da1[WRITE(offset=34590720, length=65536)]error = 5
/var/log/messages.1.bz2:Dec 21 18:36:07 Abricot kernel:
g_vfs_done():da1[WRITE(offset=34656256, length=65536)]er
On Mon, Jan 03, 2011 at 01:21:10PM +0200 I heard the voice of
Alexander Motin, and lo! it spake thus:
>
> Symptoms look very alike to ones fixed at r214597 on 2010-10-31:
Shoot, I missed that going by. Sorry for the noise; I guess I've got
a good excuse to go upgrade now 8-}
--
Matthew Full
On 03.01.2011 12:28, Matthew D. Fuller wrote:
OK, this has happened a couple times now. I'm running a mid-Oct
-CURRENT, and at around 25 days uptime (not exact but consistently in
that vicinity), things start getting very choppy. It's easily visible
in playing videos; things get very jerky and
OK, this has happened a couple times now. I'm running a mid-Oct
-CURRENT, and at around 25 days uptime (not exact but consistently in
that vicinity), things start getting very choppy. It's easily visible
in playing videos; things get very jerky and slow, but all sorts of
things start acting like
16 matches
Mail list logo