Re: GENERIC and DEFAULTS

2005-11-01 Thread Rob
Kris Kennaway wrote: > > You've clearly never spent much time on the FreeBSD > support forums, where every few days someone posts > for help > > 1) with an error caused by removing one of those > "Do not remove this!" lines, and > > 2) for help on getting X working when they forgot > to add /dev/

Re: calcru: runtime went backwards ?

2005-11-01 Thread Niki Denev
Niki Denev wrote: > Joseph Koshy wrote: > >>>dmesg and output of kern.timecounter sysctl can be found here : >> >> >>Changing your timecounter to "i8254" may help. >> >>Bug 43491 and 72338 seem to be related: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 >> http://www.freebsd.org/cgi/qu

6.x-RC1 instability with HighPoint HPT372N UDMA133 controller

2005-11-01 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just upgraded this thing to RELENG_6 and have all manner of issues when there are a lot of files to be removed; as is typical when I do the recommended "portupgrade -af" so as to remove all of the references to RELENG_5 libraries. With Soren's ata-

Re: HEADS UP! 6.0-RELEASE coming

2005-11-01 Thread Robert Watson
On Tue, 1 Nov 2005, Scott Long wrote: There is little difference between 1:1 and M:N from the application's point of view. Both will allow multiple application threads to run concurrently on multiple CPUs, and both will allow other process threads to run when the current thread blocks in the

Re: HEADS UP! 6.0-RELEASE coming

2005-11-01 Thread Scott Long
Marc Olzheim wrote: On Tue, Nov 01, 2005 at 06:33:21PM +0600, Max Khon wrote: Hi! On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote: Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb "The program no longer exists." problem for me on RELENG_6. Well, yes, but

Re: HFS/HFS+ support in 5.4 Stable

2005-11-01 Thread Michael Nottebrock
On Sunday, 30. October 2005 11:14, edward wrote: > Hi, > I need to mount an iPod mini formatted in HFS+. I don't believe this > file system is supported in 5.4 Stable, at least not on a standard > kernel. I get : > # ls /sbin/mount_* > /sbin/mount_cd9660 /sbin/mount_msdosfs /sbin/mount_std

Re: HEADS UP! 6.0-RELEASE coming

2005-11-01 Thread Marc Olzheim
On Tue, Nov 01, 2005 at 06:33:21PM +0600, Max Khon wrote: > Hi! > > On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote: > > > > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > > > "The program no longer exists." problem for me on RELENG_6. > > > > Well, yes, bu

Re: HEADS UP! 6.0-RELEASE coming

2005-11-01 Thread Max Khon
Hi! On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote: > > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > > "The program no longer exists." problem for me on RELENG_6. > > Well, yes, but that's not the same. While running on M:N KSE, all sorts > of locking ne

Re: Qualcomm modem via USB

2005-11-01 Thread Daniel O'Connor
On Tue, 1 Nov 2005 22:10, Павел Е. Черкаев wrote: > console: > ucom0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev > 1.01/0.00, addr 2, iclass 2/2 > ucom0: data interface 1, has CM over data, has break > ucom0: could not set data multiplex mode > device_attach: ucom0 attach returned 6

Qualcomm modem via USB

2005-11-01 Thread Павел Е. Черкаев
console: ucom0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev 1.01/0.00, addr 2, iclass 2/2 ucom0: data interface 1, has CM over data, has break ucom0: could not set data multiplex mode device_attach: ucom0 attach returned 6 #uname -a FreeBSD proxy.omk-kuzbass.ru 5.4-STABLE FreeBSD

Re: HEADS UP! 6.0-RELEASE coming

2005-11-01 Thread Marc Olzheim
On Tue, Nov 01, 2005 at 06:40:42AM +0600, Max Khon wrote: > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > "The program no longer exists." problem for me on RELENG_6. Well, yes, but that's not the same. While running on M:N KSE, all sorts of locking needs to be correct, w

Re: HEADS UP! 6.0-RELEASE coming

2005-11-01 Thread Marc Olzheim
On Mon, Oct 31, 2005 at 05:01:50PM +0100, Marc Olzheim wrote: > > Is the 'VM/VFS overruns' item still a problem? That was likely fixed a > > couple of months ago. If not then it's definitely something that I'll > > track for the 6.1 release. > > I'll retest that one, but it wasn't fixed yet in

Re: calcru: runtime went backwards ?

2005-11-01 Thread Niki Denev
Joseph Koshy wrote: >>dmesg and output of kern.timecounter sysctl can be found here : > > > Changing your timecounter to "i8254" may help. > > Bug 43491 and 72338 seem to be related: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 > http://www.freebsd.org/cgi/query-pr.cgi?pr=43491 > >

Re: calcru: runtime went backwards ?

2005-11-01 Thread Joseph Koshy
> dmesg and output of kern.timecounter sysctl can be found here : Changing your timecounter to "i8254" may help. Bug 43491 and 72338 seem to be related: http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 http://www.freebsd.org/cgi/query-pr.cgi?pr=43491 -- FreeBSD Volunteer, http://people.

Re: calcru: runtime went backwards ?

2005-11-01 Thread Niki Denev
Niki Denev wrote: > Hi, > > I've recently upgraded my server from 5.4-STABLE to 6.0-RC1 > and shortly after that i began to see these messages in my dmesg: > > calcru: runtime went backwards from 1488581 usec to 1488580 usec for pid > 65583 (mpsnmp) [snip] dmesg and output of kern.timecounter sy

Dual Symbios/LSI-HBA and FreeBSD 6.0 RC1

2005-11-01 Thread Juergen Dankoweit
Hello, on my Siemens Primergy 470 (dual PIII 450MHz) with two Symbios/LSI 83C895 I have great troubles: While booting FreeBSD it hangs on probing the SCSI devices. This error was in FreeBSD 5.3 STABLE 2, too! When will this bug being fixed? Here the SCSI tree and dmesg from FBSD 5.3: --

calcru: runtime went backwards ?

2005-11-01 Thread Niki Denev
Hi, I've recently upgraded my server from 5.4-STABLE to 6.0-RC1 and shortly after that i began to see these messages in my dmesg: calcru: runtime went backwards from 1488581 usec to 1488580 usec for pid 65583 (mpsnmp) calcru: runtime went backwards from 12674015 usec to 12674008 usec for pid 9818