I have a system running
FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386
I have updated the source tree to CURRENT r273542.
If I build "make buildworld" for the GENERIC kernel and no
make.conf or src.conf, it succeeds.
If I use an empty make.conf
Do what (is it safe to retry the install?)?
log:
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching public key from update5.freebsd.org... done.
Fetching metadata signature for 10.0-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
John Baldwin wrote:
> On Thursday, October 23, 2014 2:57:26 pm Rick Macklem wrote:
> > Someone just pinged me on this and I figured I should
> > bring it up.
> >
> > 1 - Is anyone out there still using oldnfs due to unresolved
> > problems with the new one? (I am not aware of any outstanding
>
On Thursday, October 23, 2014 2:57:26 pm Rick Macklem wrote:
> Someone just pinged me on this and I figured I should
> bring it up.
>
> 1 - Is anyone out there still using oldnfs due to unresolved
> problems with the new one? (I am not aware of any outstanding
> issues in the new nfs that
On 10/23/2014 15:03, Konstantin Belousov wrote:
> Use https://www.kib.kiev.ua/kib/drm/i915.6.patch. I already have one
> private report of the patch worked from person who got the same panic
> in iicbb.
Yes, this one works (does not panic) and X works! I kldloaded it after
boot as I usually do.
On Wed, Oct 22, 2014 at 03:59:23PM -0400, Adam McDougall wrote:
> On 10/22/2014 08:26, Konstantin Belousov wrote:
> > On Wed, Oct 08, 2014 at 03:12:08PM -0400, Adam McDougall wrote:
> >> On 10/08/2014 13:05, Konstantin Belousov wrote:
> >>> There are more occurences of the bug I fixed once in patch
Someone just pinged me on this and I figured I should
bring it up.
1 - Is anyone out there still using oldnfs due to unresolved
problems with the new one? (I am not aware of any outstanding
issues in the new nfs that don't exist in the oldnfs.)
2 - Does anyone see a problem with getting ri
On Thu, 23 Oct 2014, Mason Loring Bliss wrote:
> On Thu, Oct 23, 2014 at 10:20:20AM +0200, Lars Engels wrote:
>
> > Please register with your realname and I can give you the needed rights.
>
> A snag...
>
> When I click 'Logic' at the top of the page it brings me to the login form,
> which has a l
On Thu, Oct 23, 2014 at 10:20:20AM +0200, Lars Engels wrote:
> Please register with your realname and I can give you the needed rights.
A snag...
When I click 'Logic' at the top of the page it brings me to the login form,
which has a link to
https://wiki.freebsd.org/action/newaccount/FrontP
On 10/23/14 16:28, Fabian Keil wrote:
A few days ago a couple of usbconfig processed did not exit:
fk@r500 ~ $sudo procstat -kk $(pgrep usbconfig)
PIDTID COMM TDNAME KSTACK
1624 100781 usbconfig-mi_switch+0xe1 sleepq_wait+0x3a
_sx_xlock_har
A few days ago a couple of usbconfig processed did not exit:
fk@r500 ~ $sudo procstat -kk $(pgrep usbconfig)
PIDTID COMM TDNAME KSTACK
1624 100781 usbconfig-mi_switch+0xe1 sleepq_wait+0x3a
_sx_xlock_hard+0x522 _sx_xlock+0
You might want to try from the mfsbsd.iso environment,
1. Import and mount the zpool you want to boot from
2. Copy /boot/zfs/zpool.cache to /mnt/boot/zfs/ (over-write existing
zpool.cache file)
3. Edit /mnt/boot/loader.conf and add any of these that you don't already
have:
zfs_load="YES"
opensolar
In old post about same issue on 8.x tree, from 2009, I saw the patch that fixed
some integer overflows for large disk sizes/ datasets for raidz.. maybe it’s
something similar here, but for huge stripes?
Also, if it might be “bootloader launching too fast, before BIOS actually see
all the drives
On Tue, Oct 21, 2014 at 02:34:13PM -0400, Mason Loring Bliss wrote:
> On Tue, Oct 21, 2014 at 09:14:07AM +0100, David Chisnall wrote:
>
> > I agree that this would be useful, but it requires someone familiar with
> > both systems to write.
>
> Doing this stuff professionally, I could probably com
14 matches
Mail list logo
