Re: if_bge driver problem. - SOLVED

2006-02-01 Thread husnu demir
On Wed, Feb 01, 2006 at 10:27:43AM +0300, Gleb Smirnoff wrote: > On Wed, Feb 01, 2006 at 09:11:22AM +0200, husnu demir wrote: > h> No I am not tired. We would like to be part of that, even like testers. I > did try to compile but gave these error messages. I did not make CVSUP > because of the pc

Re: dhclient wedged

2006-02-01 Thread Peter Jeremy
On Tue, 2006-Jan-31 15:38:53 -0500, Lodewijk Vge wrote: >On 31-jan-2006, at 14:13, Brooks Davis wrote: > >>At the very least I need a coredump and your executable so I can >>look at variables >>in receive_packet. > >I accidentally killed it with my attempts to make it dump a core >file. so, wha

Re: Change in Promise controllers

2006-02-01 Thread Christian Baer
On Wed, 01 Feb 2006 16:33:24 +1300 Mark Kirkwood wrote: > Not of much help to you I'm afraid :-( , but a couple of us see a very > similar error with the SX4060 (PDC20621) - same chip as the SX4000 which > works perfectly for Søren, so I'll be very interested to find out what > is going on with

Re: SCSI device timeout

2006-02-01 Thread Holm Tiffe
Derkjan de Haan wrote: > All, > > Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my > system no longer boots. It hangs on > > Waiting 5 seconds for SCSI devices to settle > > Booting from the previous kernel allows my system to boot again. Please let > me know if I can do

Re: SCSI device timeout

2006-02-01 Thread Holm Tiffe
Johan Ström wrote: > On 1 feb 2006, at 10.57, Holm Tiffe wrote: > > >Derkjan de Haan wrote: > > > >>All, > >> > >>Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my > >>system no longer boots. It hangs on > >> > >>Waiting 5 seconds for SCSI devices to settle > >> > >>Booting fr

Re: SCSI device timeout

2006-02-01 Thread Johan Ström
On 1 feb 2006, at 11.42, Holm Tiffe wrote: Johan Ström wrote: On 1 feb 2006, at 10.57, Holm Tiffe wrote: Derkjan de Haan wrote: All, Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my system no longer boots. It hangs on Waiting 5 seconds for SCSI devices to settle

Quota deadlocks.

2006-02-01 Thread Jeff Roberson
I'm not able to reproduce the quota deadlocks that were reported. Can anyone reproduce them on 7.0? I need more specific instructions on how to reproduce, or more detailed debugging info from someone who can. If you can reproduce, please add 'options DEBUG_LOCKS' to your kernel. Then get me

Restartable system call behaviour

2006-02-01 Thread Pete French
I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. The reason it puzzles me is that I am explicitly catching every signal that could possibly be causing this, with the SA_RESTART flag set. So surely I sh

Re: 6-stable and HTT P4

2006-02-01 Thread Pete French
> > Just got it to work though... Had to add > > machdep.hyperthreading_allowed=1 to loader.conf in addition to > > hlt_logical_cpus=0 > > Great. FYI, HTT will give you little or even negative performance benefits. Heh - I still cant persuade my 6.0-RELEASE to *not* use hyperthreading! have got

Re: top doesn't show any Process in idle-Mode

2006-02-01 Thread Michael Schuh
Hello, sorry for the time ago, i haven't an FreeBSD-Box on my Work. The CLI-Optin -S doesn't really help me. I will test the patch from Stefan Esser, but i think my Problem are not alone SRUN-Proc's. if i run TOP with the CLI-Options -I -S so i should see Processes with status RUN and SRUN, if

Update: Change in Promise controllers (is the source-code broken?)

2006-02-01 Thread Christian Baer
I mounted ad8 as ro and tried to copy files off that drive. Didn't do much good, the system still hung up. Because of the -ro I thought it might be possible to shutdown the system cleanly, but that didn't work this time either. During shutdown the fushing of the cache fails. Strangely, this time t

Re: Quota deadlocks.

2006-02-01 Thread Oliver Brandmueller
Hi. On Wed, Feb 01, 2006 at 03:36:19AM -0800, Jeff Roberson wrote: > I'm not able to reproduce the quota deadlocks that were reported. Can > anyone reproduce them on 7.0? I need more specific instructions on how to > reproduce, or more detailed debugging info from someone who can. If you > c

Re: SCSI device timeout

2006-02-01 Thread Derkjan de Haan
> Derkjan de Haan wrote: >> >> Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my >> system no longer boots. It hangs on >> >> Waiting 5 seconds for SCSI devices to settle >> >> Booting from the previous kernel allows my system to boot again. Please >> let >> me know if I can do

KDE 3.5

2006-02-01 Thread Roger Grosswiler
Hey, where can i get it from with pkg_add ?? thx, roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0

2006-02-01 Thread Paulo Fragoso
There is a problem with country code in DWL-AG530, you can solve setting country code, we can find instructions for this in: http://madwifi.org/wiki/Compatibility Our newest DWL-AG530 are working now on FreeBSD 5.4 and FreeBSD 6.0: FreeBSD 5.4 before load contry code: Jan 4 19:39:04 dl2 kerne

Re: KDE 3.5

2006-02-01 Thread Irvin Piraman
Follow the instructions at http://freebsd.kde.org/ On 2/1/06, Roger Grosswiler <[EMAIL PROTECTED]> wrote: > > Hey, > > where can i get it from with pkg_add ?? > > thx, > roger > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/

Re: KDE 3.5

2006-02-01 Thread Michael Nottebrock
Roger Grosswiler schrieb: > Hey, > > where can i get it from with pkg_add ?? http://www.freebsd.org/doc/en/books/handbook/packages-using.html Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/

Re: KDE 3.5

2006-02-01 Thread Kris Kennaway
On Wed, Feb 01, 2006 at 02:52:56PM +0100, Michael Nottebrock wrote: > Roger Grosswiler schrieb: > > Hey, > > > > where can i get it from with pkg_add ?? > > http://www.freebsd.org/doc/en/books/handbook/packages-using.html Unfortunately we're still playing catch-up with the official packages, tho

Re: KDE 3.5

2006-02-01 Thread Michael Nottebrock
Kris Kennaway schrieb: > Unfortunately, now we are back to square 1, since you just committed > KDE 3.5.1 :-) 'S okay - patience is a virtue and package users are the most virtuous bunch of them all. And as for square one, expat2 got bumped. :O Cheers, -- ,_, | Michael Nottebrock

Re: SCSI device timeout

2006-02-01 Thread Vivek Khera
On Feb 1, 2006, at 4:57 AM, Holm Tiffe wrote: The problem seems to be in the acpi interrupt routing, I've updated the mainboard Bios to the last available version in the meantime (1018.004 Beta) with no luck. Disabling acpi completly helps booting the machine again.. I'm suspecting I have the

[releng_6 tinderbox] failure on sparc64/sparc64

2006-02-01 Thread FreeBSD Tinderbox
TB --- 2006-02-01 15:43:51 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-02-01 15:43:51 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2006-02-01 15:43:51 - cleaning the object tree TB --- 2006-02-01 15:44:16 - checking out the source tree TB --- 2006-02-01 15:44:16

Re: [releng_6 tinderbox] failure on sparc64/sparc64

2006-02-01 Thread Harti Brandt
This is failing since January 26. Shouldn't RELENG_6 build, especially while we're preparing a release? harti On Wed, 1 Feb 2006, FreeBSD Tinderbox wrote: FT>TB --- 2006-02-01 15:43:51 - tinderbox 2.3 running on freebsd-current.sentex.ca FT>TB --- 2006-02-01 15:43:51 - starting RELENG_6 tinde

Re: [releng_6 tinderbox] failure on sparc64/sparc64

2006-02-01 Thread Scott Long
I've been trying to reproduce this on my local hardware, but I can't trigger it. Scott Harti Brandt wrote: This is failing since January 26. Shouldn't RELENG_6 build, especially while we're preparing a release? harti On Wed, 1 Feb 2006, FreeBSD Tinderbox wrote: FT>TB --- 2006-02-01 15:43:

Re: Restartable system call behaviour

2006-02-01 Thread Peter Jeremy
On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote: >I have a piece of coode which does some networking, in which I see read >and write calls failing with 'Interrupted system call' from time to time. You will get EINTR if the interrupt occurs before any data is read or written. -- Peter Jerem

Re: Restartable system call behaviour

2006-02-01 Thread Ivan Voras
Peter Jeremy wrote: On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote: I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. You will get EINTR if the interrupt occurs before any data is read or wr

Re: Restartable system call behaviour

2006-02-01 Thread Pete French
> >>I have a piece of coode which does some networking, in which I see read > >>and write calls failing with 'Interrupted system call' from time to time. > > > > You will get EINTR if the interrupt occurs before any data is read > > or written. > > Will it also happen with recv() with MSG_WAITALL

Re: X.org 6.9 - Greek Keyboard Layout - FreeBSD 6.0

2006-02-01 Thread Dimitris Tsamis
Giorgos Kapetanakis wrote: > On Tue, January 31, 2006 12:01 am, Laganakos Vassilis wrote: > >> Hello, >> >> I use two layouts on X, English and Greek. I use the following lines in >> xorg.conf to switch between those two: >> >> Option "XkbRules" "xorg" >> Option "XkbModel" "acpi" >

Re: Restartable system call behaviour

2006-02-01 Thread Yar Tikhiy
On Wed, Feb 01, 2006 at 08:48:30PM +, Pete French wrote: > > >>I have a piece of coode which does some networking, in which I see read > > >>and write calls failing with 'Interrupted system call' from time to time. > > > > > > You will get EINTR if the interrupt occurs before any data is read

Re: [releng_6 tinderbox] failure on sparc64/sparc64

2006-02-01 Thread Dag-Erling Smørgrav
Scott Long <[EMAIL PROTECTED]> writes: > I've been trying to reproduce this on my local hardware, but I can't > trigger it. The ISP driver abuses the inline keyword. As I told mjacob earlier, the extensive inlining not only breaks the build, but probably hurts performance as well. (what gcc is c