Re: network deamons starting before network!

2010-06-22 Thread Randy Bush
# grep REQUIRE /etc/rc.d/ppp # REQUIRE: netif ldconfig ^ i had to add this ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubs

Re: FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e

2010-06-22 Thread Andriy Gapon
on 23/06/2010 05:58 Mario Sergio Fujikawa Ferreira said the following: > Hi, > > I am getting more than 4 thousand of the following messages a day: > > WARNING pid 24509 (python2.6): ioctl sign-extension ioctl 8004667e This ioctl is FIONBIO. I believe that I saw another report abou

Re: The mouse appears on screen but doesn't move.

2010-06-22 Thread Warren Block
On Tue, 22 Jun 2010, Nathan Maier wrote: Hi, Just updated to 8.0-Release via freebsd-update from 8.0-rc1. My mouse worked well enough in the first 8.0 release after adding "Option "AllowEmptyInput" "off" from the UPDATING file. Here's Xorg.log: X.Org X Server 1.7.5 Release Date: 201

FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e

2010-06-22 Thread Mario Sergio Fujikawa Ferreira
Hi, I am getting more than 4 thousand of the following messages a day: WARNING pid 24509 (python2.6): ioctl sign-extension ioctl 8004667e I've already recompiled all my python ports and dependencies. I am running up to date ports (today). $ uname -a FreeBSD exxodus.feday

Re: The mouse appears on screen but doesn't move.

2010-06-22 Thread Adam Vande More
On Tue, Jun 22, 2010 at 7:14 PM, Nathan Maier wrote: > Hi, > Just updated to 8.0-Release via freebsd-update from 8.0-rc1. My mouse > worked well enough in the first 8.0 release after adding "Option > "AllowEmptyInput" "off" from the UPDATING file. > Here's Xorg.log: > (II) LoadModule: "

The mouse appears on screen but doesn't move.

2010-06-22 Thread Nathan Maier
Hi, Just updated to 8.0-Release via freebsd-update from 8.0-rc1. My mouse worked well enough in the first 8.0 release after adding "Option "AllowEmptyInput" "off" from the UPDATING file. Here's Xorg.log: X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0

panic during boot on 8.0-RELEASE

2010-06-22 Thread Nicholas Mills
Oops, sent this to the wrong list. --Nick -- Forwarded message -- From: Nicholas Mills Date: Tue, Jun 22, 2010 at 7:41 PM Subject: panic during boot on 8.0-RELEASE To: freebsd-curr...@freebsd.org Hey all, Screenshot of panic message is attached. Machine is a VM running under P

Re: bwn(4) on 8.1-RC1: connection problems

2010-06-22 Thread Quentin Stievenart
On Tue, Jun 22, 2010 at 11:18:04AM +, Paul B Mahol wrote: > Where is weptxkey. Read manual again. Oh sorry, I missed that. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, sen

Re: 7.2-RELEASE-p4, IO errors & RAID1 failure

2010-06-22 Thread Bob Bishop
Hi, On 22 Jun 2010, at 08:45, Jeremy Chadwick wrote: > On Mon, Jun 21, 2010 at 10:33:12PM +0100, Matthew Lear wrote: >> [tale of woe elided] > > I don't really have any other thoughts on the matter, sadly. > [helpful suggestions elided] > > Anyone else have ideas/recommendations? The disks sur

[stable 7]config -g -ppp + kgmon causes deadlock

2010-06-22 Thread Sean Bruno
Not sure where to start poking about, but I'm seeing a dead lock on my boxes when the kernel is configured with -g -ppp. The dead lock occurs when I start profiling via kgmon -p. Any one else seeing this on 7? Sean ___ freebsd-stable@freebsd.org maili

Re: bwn(4) on 8.1-RC1: connection problems

2010-06-22 Thread Paul B Mahol
On Sun, Jun 20, 2010 at 2:23 PM, Quentin Stievenart wrote: > Hi, > > I've some broadcom wireless cards to test here (two BCM4318 and a > BCM4312). This week I tried the BCM4318 one (the 4312 is on a netbook, > I'll try it later, if the 4318 works some day). > > First of all, I was able to use it w

Re: 7.2-RELEASE-p4, IO errors & RAID1 failure

2010-06-22 Thread Jeremy Chadwick
On Mon, Jun 21, 2010 at 10:33:12PM +0100, Matthew Lear wrote: > Hello Jeremy. I just wondered if you had any further thoughts on the > info below. Two new disks arrived over the weekend and I'm still unsure > if I'm best to replace ad0 or not... > Much appreciated indeed. > -- Matt > > On Fri, 20