TB --- 2010-01-16 06:57:10 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-01-16 06:57:10 - starting RELENG_8 tinderbox run for amd64/amd64
TB --- 2010-01-16 06:57:10 - cleaning the object tree
TB --- 2010-01-16 06:57:36 - cvsupping the source tree
TB --- 2010-01-16 06:57:36 -
TB --- 2010-01-16 07:50:04 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-01-16 07:50:04 - starting RELENG_8 tinderbox run for i386/i386
TB --- 2010-01-16 07:50:04 - cleaning the object tree
TB --- 2010-01-16 07:50:34 - cvsupping the source tree
TB --- 2010-01-16 07:50:34 -
TB --- 2010-01-16 08:14:54 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-01-16 08:14:54 - starting RELENG_8 tinderbox run for i386/pc98
TB --- 2010-01-16 08:14:54 - cleaning the object tree
TB --- 2010-01-16 08:15:12 - cvsupping the source tree
TB --- 2010-01-16 08:15:12 -
On Fri, Jan 15, 2010 at 3:55 PM, Volodymyr Kostyrko c.kw...@gmail.com wrote:
On Fri, 15 Jan 2010 21:13:39 +0100
Romain Garbage romain.garb...@gmail.com wrote:
After setting ahci_load=YES in /boot/loader.conf, I get a root mount error.
ahci seems to attach to disk correctly (I get ada0
TB --- 2010-01-16 08:15:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-01-16 08:15:00 - starting RELENG_8 tinderbox run for ia64/ia64
TB --- 2010-01-16 08:15:00 - cleaning the object tree
TB --- 2010-01-16 08:15:18 - cvsupping the source tree
TB --- 2010-01-16 08:15:18 -
Hello,
Since moving from 6.4 to 8.0 I noticed that usage of mouse (usb) in
console has somewhat regressed:
First, as soon as I start moving my mouse interrupts increase to 15-18 %
as seen in top(1). That's way too much and seems like a bug.
Second, mouse cursor looks worse. It used to be
On Friday 15 January 2010 02:31:22 David Xu wrote:
Tijl Coosemans wrote:
Besides weird formatting of procstat -k output, I do not see
anything wrong in the state of the process. It got SIGSTOP, I am
sure. Attaching gdb helps because debugger gets signal reports
instead of target process
Dear colleagues,
after some unidenfified trouble I am no longer able to access raidz1 pool on my
home file server (8 sata disks). rebooting from outer media works fine until
`zpool import' - then process is stuck in zio-io_cv state forever (I waited
for 2+ hours) without real activity. This is
On Sat, 16 Jan 2010, Dmitry Morozovsky wrote:
DM after some unidenfified trouble I am no longer able to access raidz1 pool
on my
DM home file server (8 sata disks). rebooting from outer media works fine
until
DM `zpool import' - then process is stuck in zio-io_cv state forever (I
waited
DM
Russell Yount wrote:
It seems AP to client broadcasts/multicasts traffic is
broken when using WPA2/802.11i with multiple hostapds in 8.0.
Only the SSID associated with the last hostapd to be started has
AP to client broadcasts/multicasts being delivered correctly.
The AP and client are 8.0
Nenhum_de_Nos wrote:
On Tue, January 5, 2010 00:09, Nenhum_de_Nos wrote:
hail,
I have a Core 2 Duo 2.66 GHz as a wifi ap:
Jan 4 22:31:08 xxx kernel: cpu_reset: Stopping other CPUs
Jan 4 22:31:08 xxx kernel: Copyright (c) 1992-2010 The FreeBSD Project.
Jan 4 22:31:08 xxx kernel: Copyright
Good evening,
I am observing that doing a buildworld on stable (r202448) with
WITH_CTF=1 breaks /usr/libexec/cc1plus on my amd64. Doing so causes
cc1plus to crash with internal errors and ports like devel/popt don't
even make it through the configure stage (fails sanity check).
Is this behaviour
for about two years, i have been using the Metrix CM9 miniPCI
(http://metrix.net/cm9-p-2.html) on freebsd 8 on a 5501 and
have been happy with it
randy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
Tijl Coosemans wrote:
On Friday 15 January 2010 02:31:22 David Xu wrote:
Tijl Coosemans wrote:
Besides weird formatting of procstat -k output, I do not see
anything wrong in the state of the process. It got SIGSTOP, I am
sure. Attaching gdb helps because debugger gets signal reports
Hi,
On the weekend, I moved my 8-STABLE installation (csup'd late Dec 2009)
onto a new drive, a Seagate ST31000528AS CC3; and while the transfer was
successful, I've noticed that the drive light is solidly on all the time,
even if it boots into single-user.
# uname -a
FreeBSD osiris.chen.org.nz
15 matches
Mail list logo
