Hi
I'm having some weird problems running an usb keyboard on my 5.x system.
The same keyboard works under 4.x.
As soon as usb0 loads both ps/2 and usb keyboards stop working.
I found out this by running the bootload in pause mode. The line it
stops at says:
usb0: Intel 82371AB/EB (PIIX4) USB
I have ever compiled kernel without console, keyboard, and VGA in
RELENG_4, it is no problem, and works fine, but I can't do so in
RELENG_5 now...:-(
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
On 4/26/05, W C [EMAIL PROTECTED] wrote:
Hi all,
I am attempting to install 5.3-R from cd (iso image download) and
sysinstall is failing
to write the chosen (Auto Layout) filesystem to disk, the Toshiba 80G on the
primary ide channel as master. The error on vty1 is (from memory) ad0:
On Tue, Apr 26, 2005 at 03:36:02PM -0400, Brian Fundakowski Feldman wrote:
I'm still guessing that for whatever reason your writes on the FreeBSD
4.x NFS client are not using NFSv3/transactions. The second method
I just now implemented; it works fine except for being slower since
all data is
Just add the following line to your /etc/rc.conf
jail_sysvipc_allow=YES
and ipc configuration will be shared with the jails
I have IPC enabled for jails already. So unfortunately this is not a
solution.
Is anybody here who do run several jailed PostgreSQL servers?
AFAIR PostgreSQL generates
On Wed, Apr 27, 2005 at 10:11:16AM +0200, Arjan Van Leeuwen wrote:
After you've installed the system, insert that line into
/boot/loader.conf, and load up atacontrol mode 0 udma33 udma33 as
early as possible during the boot (try using /etc/rc.early, for
example) to get it up to speed again.
* Bruce M Simpson [EMAIL PROTECTED] [0440 11:40]:
However, I agree, this is *annoying*; I don't know of 80 + 4 conductor cables
for 2.5 ATA drives. If anyone knows of such things then please do let me
know, as I've had significant problems with a development system at work which
is Mini-ITX
In case anyone is curious, here's the answer. The information needed to
solve this wasn't in my email. Look in the archives for the original
problem description.
The short and amusing answer: it was booting off a stale vinum drive, and
then running off the current drive once vinum got loaded.
This might be the only real advantage of a serial console. The unit you
pointed to is ~$4000.00, whereas 16-port serial console units run more
like $1000.00.
I've built a number of Dell systems lately (Windows for this client) but
I always order them with the DRAC/4 card. I think it's about $350
FreeBSD 5.4-STABLE #5: Wed Apr 6 15:16:36 CEST 2005
Slab at 0xc866cfa8, freei 0 = 12.
panic: Duplicate free of item 0xc866c000 from zone 0xc103e9a0(Mbuf)
cpuid = 2
KDB: stack backtrace:
kdb_backtrace(100,c569dd80,0,c866cfa8,c56363c0) at 0xc053f121 =
kdb_backtrace+0x29
Hello,
I have a multithreaded application ported on FreeBSD 5.3 which crashes
in a minute or less if hyperthreading in enabled. Without HT there is no
problem.
How and where should I start to investigate the problem?
The backtrace:
(gdb) bt
#0 0x2819631b in pthread_testcancel () from
Will Saxon wrote:
I recently purchased a Netgear WG311 card based on the fact that the
manpage for ath(4) says it is a supported card. As it turns out, at
least version 2 (the version I had) of this card is not supported - it
appears to be based on a Texas Instruments chipset that it not
On Wed, Apr 27, 2005 at 10:17:46AM +0200, Marc Olzheim wrote:
On Tue, Apr 26, 2005 at 03:36:02PM -0400, Brian Fundakowski Feldman wrote:
I'm still guessing that for whatever reason your writes on the FreeBSD
4.x NFS client are not using NFSv3/transactions. The second method
I just now
On Wed, Apr 27, 2005 at 12:08:57PM -0400, Brian Fundakowski Feldman wrote:
Yes, a single writev(). Just like in the kern/79207 PR.
It doesn't have to be superfast (why would I use NFS otherwise), just as
long as it's threadsafe / atomic.
Alright, this will do synchronous, instead of
On Tue, 26 Apr 2005, Sergey S. Ropchan wrote:
Hi, all
I have problem on high loaded SMP server with FreeBSD 5.3-p10+Apache
1.3.33+Mysql 4.0 reported in kern/75780 !
State still open - not fixed as i understand!
If there any possible way to find workaround of this problem !?
Maybe cvsup
The same system about which I just mailed, crashes when booting with
verbose logging enabled. With a normal boot, everything's ok...
Marc
KDB: debugger backends: ddb
KDB: current backend: ddb
131072K of memory above 4GB ignored
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979,
Hi,
I've updates my system this morning after reading about the usb mfc. The
sources used before are dated from january. I'm not sure if this error
was triggered by the update, but:
Using sysctl -a it seems to lose track after some lines.
snip
kern.ostype: FreeBSD
kern.osrelease: 4.11-STABLE
Hi,
I experienced this new fxp LOR (probably when ntpd started during boot):
hand-copied:
lock order reversal
1st 0xcc666360 inp (udpinp) @ sys/netinet/udp_usrreq.c:772
2nd 0xc14c8264 fxp0 (network driver) @
/usr/src/sys/modules/fxp/../../dev/fxp/if_fxp.c:1232
KDB: stack backtrace:
On Wed, Apr 27, 2005 at 07:46:28PM +0200, Marc Santhoff wrote:
Hi,
I've updates my system this morning after reading about the usb mfc. The
sources used before are dated from january. I'm not sure if this error
was triggered by the update, but:
Using sysctl -a it seems to lose track after
On Mon, 2005-04-25 at 12:59 +0200, Oliver Brandmueller wrote:
Hi,
I have some servers running running on 5.4-STABLE as of Apr 5th. I use
nss_ldap for a userbase of currently about 24000 accounts (will be
growing to approx 6 in the next weeks). I don't use pam_ldap
currently, because
Am Mi, den 27.04.2005 schrieb Marc Olzheim um 20:10:
On Wed, Apr 27, 2005 at 07:46:28PM +0200, Marc Santhoff wrote:
Hi,
I've updates my system this morning after reading about the usb mfc.
The
sources used before are dated from january. I'm not sure if this
error
was triggered by the
On Wed, Apr 27, 2005 at 08:24:36PM +0200, Marc Santhoff wrote:
That is 'kern.msgbuf' ;-)
Hm, I've never seen such a verbose output before.
Has anything changed in that area? And why does it still occur after a
reboot, normally buffers are only temporarily valid(at least I thought
so
On Wed, Apr 27, 2005 at 07:15:23PM +0200, Marc Olzheim wrote:
On Wed, Apr 27, 2005 at 12:08:57PM -0400, Brian Fundakowski Feldman wrote:
Yes, a single writev(). Just like in the kern/79207 PR.
It doesn't have to be superfast (why would I use NFS otherwise), just as
long as it's
On Wed, Apr 27, 2005 at 02:34:35PM -0400, Brian Fundakowski Feldman wrote:
Alright, thanks for helping with this :-) Do you think you can find
a way to tell if in 4.x you're actually using NFSv3/transactions? I
would really like to know why 4.x isn't deadlocking, and that's the
most plausible
Am Mi, den 27.04.2005 schrieb Marc Olzheim um 20:31:
On Wed, Apr 27, 2005 at 08:24:36PM +0200, Marc Santhoff wrote:
That is 'kern.msgbuf' ;-)
Hm, I've never seen such a verbose output before.
Has anything changed in that area? And why does it still occur after a
reboot, normally
Marc Olzheim wrote:
On Mon, Apr 25, 2005 at 08:06:19PM -0700, Ade Lovett wrote:
SuperMicro [...] Seagate [...]
on-board aic7902
and, from your dmesg output:
da0: SEAGATE ST373207LC 0003 Fixed Direct Access SCSI-3 device
da0: 320.000MB/s transfers [...]
At an absolute minimum, have the
On Wed, Apr 27, 2005 at 08:42:03PM +0200, Marc Olzheim wrote:
On Wed, Apr 27, 2005 at 02:34:35PM -0400, Brian Fundakowski Feldman wrote:
Alright, thanks for helping with this :-) Do you think you can find
a way to tell if in 4.x you're actually using NFSv3/transactions? I
would really like
On Wed, 27 Apr 2005, Gavin Atkinson wrote:
On Mon, 2005-04-25 at 12:59 +0200, Oliver Brandmueller wrote:
The more accounts there are in the LDAP directory, the longer the
startup of top takes. With the current userbase top takes about 3-4
seconds to start (on a mostly idle Dual Xeon 2.8GHz
On Wed, Apr 27, 2005 at 03:06:27PM -0400, Brian Fundakowski Feldman wrote:
How can I tell whether it uses transactions ?
I am not sure -- it should with NFSv3 though. Does mount -v tell
you anything more detailed? I suppose that nfsstat may also be used
-- the commit count should only
hi all
i'm fighting a little bit with a new intel server.
i bought an intel SE7210TP1-E server with integrated RAID controller (SATA)
and thought: nice, one box everything inside ,-)
but it seems that the raid controller is not supported by any freebsd
version (i would love to see it running on
On Wed, Apr 27, 2005 at 10:17:46AM +0200, Marc Olzheim wrote:
Btw. running the writev program with 20 * 100 MB on UFS on a 512MB
FreeBSD 6-CURRENT system practicly locks the filesystem down _and_
causes all processes to be swapped out in favor of the buffer cache.
'top' however,
On Wed, Apr 27, 2005 at 09:19:38PM +0200, Marc Olzheim wrote:
On Wed, Apr 27, 2005 at 03:06:27PM -0400, Brian Fundakowski Feldman wrote:
How can I tell whether it uses transactions ?
I am not sure -- it should with NFSv3 though. Does mount -v tell
you anything more detailed? I suppose
On Wed, Apr 27, 2005 at 03:41:44PM -0400, Brian Fundakowski Feldman wrote:
Alright, thanks for testing. So the same bug exists in 4.x but may
not actually deadlock the buffer cache in the same circumstances.
If you feel like playing with it anymore, I would expect a certain
write block size,
On Wed, Apr 27, 2005 at 08:53:57PM +0200, Marc Santhoff wrote:
I still don't understand completly. In the file made like this:
sysctl -a garbage.txt
there are the messages of at least three reboot cycles.
The kernel tries to preserve the message buffer if it has not been
cleared by
Have you found a solution to this? I am having the same problems on a
machine very recently updated (cvsupped + buildworld on 4/14/2005):
kernel.log:Feb 25 13:46:40 trinity kernel: rl0: discard oversize frame
(ether type 3db4 flags 3 len 8381 max 1514)
kernel.log:Apr 10 14:27:37 trinity
On Wed, Apr 27, 2005 at 08:01:28PM +0200, Rene Ladan wrote:
Hi,
I experienced this new fxp LOR (probably when ntpd started during boot):
[snip 2 LORs]
The box panics with automatic dump and reboot:
KDB: enter: witness_checkorder
panic: blockable sleep lock (sleep mutex) tty @
Should work just fine with the integrated ICH5R if you CVSUP to
-CURRENT. sos@ has done major work to the ata code recently and I have
many of this exact machine up and running right now. I had to:
Enable SATA RAID in the BIOS but define no raid
Install FreeBSD on ad4 (or the first disk)
CVSUP
be awair that often 'hardare raid' ata and sata controllers
actually just have bioses which can boot from raided disks
and then hand over to the OS. therefore their is no actual
difference between 'hardware' and software raid as your
cpu is doing the work
please see documentation relating to your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/27/05 18:36, Samuel Clements wrote:
Should work just fine with the integrated ICH5R if you CVSUP to
-CURRENT. sos@ has done major work to the ata code recently and I have
many of this exact machine up and running right now. I had to:
You'll find a diff at:
http://www.freebsd.org/~julian/usb-4.diff
This merges a lot of the USB infrastructure.
I was amazed how little changing had to be done
to allow this to work on 4.x.
The files become almost teh same as on -current.
(minus small changes here and there)
if you use USB on 4.x,
Julian Elischer wrote:
You'll find a diff at:
http://www.freebsd.org/~julian/usb-4.diff
This merges a lot of the USB infrastructure.
I was amazed how little changing had to be done
to allow this to work on 4.x.
The files become almost teh same as on -current.
(minus small changes here and there)
On 4/27/05, Gavin Atkinson [EMAIL PROTECTED] wrote:
A while back, there was talk of a FreeBSD libc name cache daemon, but I
can't seem to find any reference to it now (I seem to remember the
website was within .ru, if it helps anyone find it) - though I'm not
sure it would help in this context
I was pretty sure I saw a heads-up, and lo I did:
+++
I have just merged in most of the lowest level changes to 4.x from
6.x.
If you use USB on 4.x machines and are planning on following RELENG_4
then I suggest you test the latest sources to avoid nasty surprises
later.
I will probably merge
hello,
first of i'd like to excuse any of the hardcore unix heads here, bringing
such possibly unimportant topics :-)
to keep it quick - the idea is simple, there is some standard *bsd games
distribution, but those games are hardly even anything more amusing than
fortune /which do not get me
None wrote:
might be interested to help out? i am aware of the fact, that a main
tree merge would require some extra libs not everyone might be happy
about in the main dist, or maybe some framework, kernel/system wise?
Make it a port, and put it in ports/games.
mkb.
On Thu, Apr 28, 2005 at 05:03:55AM +0200, None wrote:
hello,
first of i'd like to excuse any of the hardcore unix heads here, bringing
such possibly unimportant topics :-)
to keep it quick - the idea is simple, there is some standard *bsd games
distribution, but those games are hardly
On Thursday, 28. April 2005 05:03, None wrote:
now this is where the plan comes in - what about some upgrade to the
default bsd world? FreeBSD seems like the BSD that could support it.
Almost all of the 44BSD-Lite games were removed from FreeBSD 5-CURRENT over
two years ago to save space and
Brooks Davis [EMAIL PROTECTED] writes:
Reproducibly, if I begin copying data to a [...] CF card [...] it
works for a while, then freezes the system.
[...]
Sounds like you should file a PR about the issue. Are you sure the file
system in question is OK? There were some msdosfs corruption
This is resurrecting an old thread, but I'd like the answer to be found
in searches, so here goes:
On Monday, 25th August 2003, Stephen McKay wrote:
On Saturday, 9th August 2003, Doug White wrote:
On Fri, 8 Aug 2003, Stephen McKay wrote:
Stephen McKay wrote:
Since I upgraded to FreeBSD 4.8
On Wed, Apr 27, 2005 at 07:42:35PM -0400, Tim Howe wrote:
Brooks Davis [EMAIL PROTECTED] writes:
Reproducibly, if I begin copying data to a [...] CF card [...] it
works for a while, then freezes the system.
[...]
Sounds like you should file a PR about the issue. Are you sure the
50 matches
Mail list logo
