On 5/18/2010 1:39 AM, Garrett Cooper wrote:
> On Mon, May 17, 2010 at 10:35 PM, Rob Farmer wrote:
>> Hi,
>>
>> make release is broken on current. Seems to be related to the lzma
>> import. This is on i386:
>>
>> cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo
>> test.lo camc
Rob Farmer wrote:
> Hi,
>
> make release is broken on current. Seems to be related to the lzma
> import. This is on i386:
..
> : undefined reference to `lzma_end'
> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567):
> In function `xz_filter_read'
On Sat, May 15, 2010 at 01:04:01PM +0300, Kostik Belousov wrote:
> Hello,
>
> please find at http://people.freebsd.org/~kib/misc/aesni.1.patch the
> combined patch, containing the fpu_kern KPI and Intel AESNI crypto(9)
> driver. I did development and some testing on the hardware generously
> prov
On Tue, May 18, 2010 at 05:30:19PM +0200, Pawel Jakub Dawidek wrote:
> On Sat, May 15, 2010 at 01:04:01PM +0300, Kostik Belousov wrote:
> > Hello,
> >
> > please find at http://people.freebsd.org/~kib/misc/aesni.1.patch the
> > combined patch, containing the fpu_kern KPI and Intel AESNI crypto(9)
Hi,
I've been using -CURRENT last update in February for quite a long time
and few weeks ago decided to finally update it. The update was quite
unfortunate as system became very unstable: it just hangs few times a
day and panics sometimes.
Some things can be reproduced, some cannot. Reproducible
>
>>
>> - Unfortunately the driver in its current version can't be used with
>> IPsec and with GELI where authentication is enabled. This is because
>> the driver doesn't support sessions where both encryption and
>> authentication is defined. Do you have plans to change it?
>> I saw that you
Roman Bogorodskiy wrote:
> I've been using -CURRENT last update in February for quite a long time
> and few weeks ago decided to finally update it. The update was quite
> unfortunate as system became very unstable: it just hangs few times a
> day and panics sometimes.
>
> Some things can be repr
I'm trying to bring up a new board based on Intel's Jasper Forest x86
processor. I can boot a kernel without SMP without any problems, but
FreeBSD is not able to start up the Application Processors if I enable
SMP. The error message that I get is:
AP #2 (PHY# 2) failed!
panic y/n? [y]
This was
What if you use amd64, have you tried that? Low level code is different.
Interesting however, maybe I can get access to one around here, will see.
Jack
On Tue, May 18, 2010 at 2:32 PM, Ryan Stone wrote:
> I'm trying to bring up a new board based on Intel's Jasper Forest x86
> processor. I ca
amd64 exhibits the same problem, except that it's not even polite and
panics without even asking.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsu
LOL, ok, I'm beating the bushes here Ryan, and I think I can get a system
although it may be a day or two. Will let you know.
Jack
On Tue, May 18, 2010 at 4:40 PM, Ryan Stone wrote:
> amd64 exhibits the same problem, except that it's not even polite and
> panics without even asking.
>
On Tue, 18 May 2010 19:40:13 -0400
Ryan Stone wrote:
> amd64 exhibits the same problem, except that it's not even polite and
> panics without even asking.
Could you please try disabling legacy USB device support in BIOS if
such an option is provided in your BIOS setup and see if that changes
any
12 matches
Mail list logo
