I had some onboard (S)ATA controllers becoming unreliable in the
past. Two of them due to chipsets overheating under load which
were fixable with additional cooling. In the third one we just added
a cheap SATA card and spread the redundant disks between
onboard and add-on controller to make a tempo
Check cables and devices are in good condition. These things are usually
a connectivity issue or device failing
On 06/12/2015 03:06, Perry Hutchison wrote:
Does anyone know the condition of the ICH5 ATA support in FreeBSD 10?
In preparing to repurpose an elderly Dell Dimension 4600 from Window
On Sun, Dec 06, 2015 at 04:54:38PM +0800, Gavin Mu wrote:
> Hi, kib,
>
>
> It is really related with madvise behavior, I checked code related with
> MADV_SEQUENTIAL, and it seems there is something wrong with vm_fault() of
> FreeBSD 10.1.
> I did a simple patch:
> diff --git a/sys/vm/vm_fault.c
Does anyone know the condition of the ICH5 ATA support in FreeBSD 10?
In preparing to repurpose an elderly Dell Dimension 4600 from Windows
to FreeBSD, and needing to decide what to do about drives, I found
several mentions in the archives* of ICH5 ATA DMA timeouts -- mostly
affecting the SATA por
hiya,
+wireless, +andriy
Andriy has been working on adding lots of new things to urtwn and
tidying it up. It's possible he's introduced some regressions. Just
check in on the wireless list and join #freebsd-wireless on efnet to
ask questions.
Hopefully it was fixed a couple days ago with the TX
i pulled the recent RPI2 r291495 from ftp.freebsd.org, and i also notice that
the urtwn usb dongle
i typically use is very flakey with -CURRENT on the Raspberry Pi 2. The
symptoms sound very
similar to those described on this thread.
: mdm
> On Dec 6, 2015, at 6:44 AM, Anton Shterenlikht wrote
>From h...@selasky.org Sun Dec 6 14:41:27 2015
>
>On 12/06/15 15:14, Anton Shterenlikht wrote:
>> I posted this about a week ago:
>>
>> http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html
>>
>> The problem is that urtwn stopped
>> working in current r291431.
>>
>> I did mo
On 12/06/15 15:14, Anton Shterenlikht wrote:
I posted this about a week ago:
http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html
The problem is that urtwn stopped
working in current r291431.
I did more testing with the same revision,
and sometimes it would work, but ex
I posted this about a week ago:
http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html
The problem is that urtwn stopped
working in current r291431.
I did more testing with the same revision,
and sometimes it would work, but extremely
slowly, and sometimes seemingly associa
Hi, kib,
It is really related with madvise behavior, I checked code related with
MADV_SEQUENTIAL, and it seems there is something wrong with vm_fault() of
FreeBSD 10.1.
I did a simple patch:
diff --git a/sys/vm/vm_fault.c b/sys/vm/vm_fault.c
index b5ac58f..135fc67 100644
--- a/sys/vm/vm_fault.c
10 matches
Mail list logo