Hi all,
I hope to use "option VIMAGE" on RaspberryPi.
So, I try to make a patch.
http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff
#There is a SD image for RaspberryPi at same place.
But, I only test it for if_smsc driver on RaspberryPi.
Hail,
I am back to desktoo and FreeBSD, but I cant pass the simple test to make X
alive. Xorg -configure detects two vga and two displays, but neither seems to
work. On 9.2rc I got to show X, but deadlock soon after. Now I installed head,
and cant even get X to work. The nvidia driver refuses
On Sun, Aug 11, 2013 at 9:20 AM, Larry Rosenman wrote:
> In the last 12 hours I've had 4 crashes related to ZFS.
>
>
> total 97
> -rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1
> -rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2
> -rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3
> The SVN rev was AWOL from the uname till this AM.
>
Oh snap you are right, I didn't even notice uname -a lost the rev #
looks like I have some compiling to do :)
--
Sam Fourman Jr.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
Le 11/08/2013 19:30, Larry Rosenman a écrit :
> On 2013-08-11 12:29, Steven Hartland wrote:
>> You seem to be getting a selection of random looking issues
>> bad hardware would be my first guess. Run a memtest and
>> see if it turns up anything.
>>
>>Regards
>>Steve
>>
>
> same hardware wa
On 2013-08-11 12:41, Sam Fourman Jr. wrote:
same hardware was ROCK STABLE till this weekend.
Larry,
it would help if you had a svn revision #, for what it is worth, I had
a machine
that was crashing all over the place, after r254141
a fresh svnlite up and new kernel r254196 seems to have f
> same hardware was ROCK STABLE till this weekend.
>
Larry,
it would help if you had a svn revision #, for what it is worth, I had a machine
that was crashing all over the place, after r254141
a fresh svnlite up and new kernel r254196 seems to have fixed my
problem atleast...
--
Sam Fourman Jr
On 2013-08-11 12:29, Steven Hartland wrote:
You seem to be getting a selection of random looking issues
bad hardware would be my first guess. Run a memtest and
see if it turns up anything.
Regards
Steve
same hardware was ROCK STABLE till this weekend.
--
Larry Rosenman
You seem to be getting a selection of random looking issues
bad hardware would be my first guess. Run a memtest and
see if it turns up anything.
Regards
Steve
- Original Message -
From: "Larry Rosenman"
To:
Sent: Sunday, August 11, 2013 5:20 PM
Subject: ZFS Crashes
In the la
On 2013-08-11 12:05, Dan Mack wrote:
I'm running zfs on a few systems with recent builds; which version of
current were you last stable on ... if you can recall?
FWIW I'm so far pretty stable on 254187 (on two systems) and also on
r253918
Dan
About 3-4 days ago (not sure of the svn rev).
I'm running zfs on a few systems with recent builds; which version of current
were you last stable on ... if you can recall?
FWIW I'm so far pretty stable on 254187 (on two systems) and also on r253918
Dan
On Sun, 11 Aug 2013, Larry Rosenman wrote:
In the last 12 hours I've had 4 crashes r
Wiadomość napisana przez Alan Cox w dniu 30 lip 2013, o godz.
19:40:
> On Jul 21, 2013, at 2:50 PM, Jeremie Le Hen wrote:
>>
>>> Also, a wired mapping can be destroyed by calling munmap(2) without
>>> first calling munlock(2), in which case, RACCT_MEMLOCK will be
>>> incorrect.
>>
>> So I think
In the last 12 hours I've had 4 crashes related to ZFS.
total 97
-rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1
-rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2
-rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3
-rw-r--r-- 1 ler ler 71718 Aug 11 11:17 core.txt.4
These are
Howdy,
Anyone looking into this?
http://software.intel.com/en-us/articles/what-is-intel-rapid-start-technology
Best,
George
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #78 r253966: Mon Aug 5
14:42:05 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64
# svn info
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/bas
Yeah, I agree with avoiding the 'cd' as well. I'll give it a try shortly.
Dan
On Sun, 11 Aug 2013, Glen Barber wrote:
On Sun, Aug 11, 2013 at 08:25:42AM -0500, Dan Mack wrote:
There's still one problem left ... the svnliteversion test fails
because you are not in the correct directory. This
On Sun, Aug 11, 2013 at 08:25:42AM -0500, Dan Mack wrote:
>
> There's still one problem left ... the svnliteversion test fails
> because you are not in the correct directory. This is the patch that
> worked for me ...
>
Yep, you are correct. Although, rather than cd(1) to the SYSDIR
directory,
There's still one problem left ... the svnliteversion test fails
because you are not in the correct directory. This is the patch that
worked for me ...
root@olive:/usr/src # svnlite diff sys/conf/newvers.sh
Index: sys/conf/newvers.sh
=
On Sun, Aug 11, 2013 at 02:15:15AM -0700, Peter Wemm wrote:
> On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev wrote:
> > Yes, please do something about our base(1) being unable to talk in anything
> > non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, and
> > was wondering w
On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev wrote:
> On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote:
>> I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
>>
>> https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1
>> https://github.com/l
On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote:
> I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
>
> https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1
> https://github.com/lichray/nvi2
>
> The goal was to update the multibyte handling
On 08/10/13 23:34, Kevin Oberman wrote:
On Fri, Aug 9, 2013 at 1:33 PM, Hans Petter Selasky wrote:
Hi,
For those of you that want to make sure your USB mass storage device
behaves correctly when using FreeBSD, typically for critical applications,
I've just added an advanced USB testing tool t
22 matches
Mail list logo