Re: Please test: cluster locking patch.

[Jeff Roberson]

Found a bug.  Please update your source from the same location if you
previously applied this patch.

On Sun, 2 Mar 2003, Jeff Roberson wrote:

 I have a patch that should clear up buf locking issues and race conditions
 in vfs_cluster.c.  Since this code is so tricky I'd like to have a few
 people test it.  You should notice no difference in your system
 performance or behavior.

 Please see:  http://www.chesapeake.net/~jroberson/cluster.diff

 I will post on arch about the contents of the patch.

 Cheers,
 Jeff


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

subscribe jo@jo.co.za

[johan]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Any ideas why we can't even boot a i386 ?

[Bruce Evans]

On Sun, 2 Mar 2003, Terry Lambert wrote:

 Poul-Henning Kamp wrote:
  In message [EMAIL PROTECTED], Bruce Evans writes:
  On Sun, 2 Mar 2003, Bruce Evans wrote:
   On Fri, 28 Feb 2003, Poul-Henning Kamp wrote:
My main concern would be if the chips have the necessary umphf
to actually do a real-world job once they're done running all the
overhead of 5.0-R.  The lack of cmpxchg8 makes the locking horribly
expensive.
  
   Actually, the lack of cmpxchg8 only makes locking more expensive.  It's
  
  I.e., strictly more expensive, but not much more.
 
  Bruce, it is not a matter of the relative expensiveness of the various
  implementations of locking primitives, its a matter of the cummulative
  weight of all the locks we add to the system.

Of course.  A 400% pessimization of locking primitive turns into more
like a 100% pessimization of locking non-primitives (at the level of
mtx_lock()).  Since the kernel spends only a few percent of its time
(1% say) of its time in non-i386 locking non-primitives, pessimizing
these non-primitives by 100% costs 1%.  Since the system spends only
a few percent of its time in the kernel (10% say), pessimizing the
non-primitives costs a whole 0.1%.  (0.1% is getting near the resolution
of my benchmarkmethod (run makeworld on a fairly idle machine after
rebooting).)

 Bruce's make world benchmark gave coverage of the cumulative
 weight, in support of his point.

Indeed.  Actual testing showed costs of 3.2% (kernel) and 0.3% (real).
I made up the percentages of 1% and 0.1% by reducing these a bit
(I386_CPU pessimizes more than locking, but the exact percentages aren't
very interesting since they are so small).

Of course there are loads that use more locks than makeworld (mainly
networking with tinygrams I think -- this is why no one except networking
people and benchmarkers even notice that -current is much worse than
RELENG_4 (slowness from debugging options is irrelevant)).

I wrote:

 To get the system to run I had to unbreak panicifcpuunsupported() so
 that it doesn't gratuitously reject Athlons (CPUs that are upward
 compatible should not be rejected), and had to replace pmap.o by the
 non-386 version since the 386 version caused strange errors.  It's not
 clear why the 386 version doesn't work -- the only internal difference
 in pmap.c is that the 386 version uses invltlb() and other versions
 use invlpg().  Using invlpg() would probably make things more than
 0.3% slower.  Selecting the best inv*() was the main optimization that
 we dropped when 386 support was made incompatible with support for later
 CPUs.

Configuring DISABLE_PG_G fixed the problem with pmap.  invlpg() apparently
doesn't work with global pages, but I386_CPU doesn't stop global pages
being configured.

 world with my kernel configured for I486_CPU through I686_CPU
 %%%
 1532 MHz AthlonXP 1600 256MB 2 ATA drives
 async mounted /usr/obj (src on separate drive)
 --
  elf make world completed on Sun Mar  2 16:30:55 EST 2003
(started Sun Mar  2 15:53:15 EST 2003)
 --
  2260.31 real  1729.55 user   326.24 sys
  40208  maximum resident set size
   2248  average shared memory size
   1762  average unshared data size
127  average unshared stack size
   14959205  page reclaims
  25630  page faults
  0  swaps
  43481  block input operations
   3963  block output operations
  0  messages sent
  0  messages received
  5  signals received
 313523  voluntary context switches
 607085  involuntary context switches
 %%%

 world with my kernel configured for I386_CPU except for pmap.o
 %%%
 1532 MHz AthlonXP 1600 256MB 2 ATA drives
 async mounted /usr/obj (src on separate drive)
 --
  elf make world completed on Mon Mar  3 03:00:45 EST 2003
(started Mon Mar  3 02:22:57 EST 2003)
 --
  2267.98 real  1730.21 user   336.73 sys
  40208  maximum resident set size
   2245  average shared memory size
   1756  average unshared data size
127  average unshared stack size
   14958931  page reclaims
  26265  page faults
  0  swaps
  44148  block input operations
   3898  block output operations
  0  messages sent
  0  messages received
  6  signals received
 313986  voluntary context switches
 598687  involuntary context switches
 %%%

As might be expected, using invlpg() and not using global pages costs
more than pessimizing locking primitives.  It costs an additional 1.6%
(real) and 5.9% (sys):

world with my kernel configured for I386_CPU and DISABLE_PG_G
%%%
1532 MHz AthlonXP 1600 256MB 2 ATA drives
async mounted /usr/obj (src on separate drive)

Re: sparc64 tinderbox failure

[Ruslan Ermilov]

On Mon, Mar 03, 2003 at 12:16:39AM -0500, Mike Barcroft wrote:
[...]
 --
  Kernel build for GENERIC started on Mon Mar  3 00:15:48 EST 2003
 --
 === hme
 make: don't know how to make bsd.README. Stop
 *** Error code 2
 
Should be fixed now.


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]   FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


pgp0.pgp
Description: PGP signature

Re: -CURRENT + cvs = panic

[Philipp Mergenthaler]

On Mon, Mar 03, 2003 at 01:23:20AM +0200, Vladimir Kushnir wrote:
 Practically 100% repeatable: after some CVS updates (not sure but it
 seems after another high HD load as well) -CURRENT panics with
 bwrite: buffer is not busy
 (in the prefious message I've attached gdb trace and so on, and nothing
 has changed so far).
 It goes on for at least several days now.

In that gdb trace, I think the panic was only an aftereffect and
the trouble started here:
#15 0xc02bc1c8 in calltrap () at {standard input}:96
#16 0xc021fd79 in tcp_input (m=0xc0d49c30, off0=20)
at /usr/src/sys/netinet/tcp_input.c:2324

Do you have version 1.198 of sys/netinet/tcp_input.c?  I haven't had
that panic since then (i.e. for the last four days).

Bye, Philipp

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: -CURRENT + cvs = panic

[leafy]

On Mon, Mar 03, 2003 at 11:01:22AM +0100, Philipp Mergenthaler wrote:

 In that gdb trace, I think the panic was only an aftereffect and
 the trouble started here:
 #15 0xc02bc1c8 in calltrap () at {standard input}:96
 #16 0xc021fd79 in tcp_input (m=0xc0d49c30, off0=20)
 at /usr/src/sys/netinet/tcp_input.c:2324
 
 Do you have version 1.198 of sys/netinet/tcp_input.c?  I haven't had
 that panic since then (i.e. for the last four days).
 
 Bye, Philipp
It's the very  same line of code that caused my distributed folding clinent oto panic 
the system. I have 

 * $FreeBSD: src/sys/netinet/tcp_input.c,v 1.198 2003/02/26 18:20:41 jlemon Exp
$
 */

It still panics everytime  I start the client. cvsup is ok though.

Jiawei Ye

-- 
Without the userland, the kernel is useless.
 --inspired by The Tao of Programming

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

HEADSUP! driver megacommit in progress.

[Poul-Henning Kamp]

I've finished compiling my driver megacommit on i386, alpha and sparc64
and I will be committing the stuff shortly

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: HEADSUP! driver megacommit in progress.

[Poul-Henning Kamp]

In message [EMAIL PROTECTED], Poul-Henning Kamp writes:

I've finished compiling my driver megacommit on i386, alpha and sparc64
and I will be committing the stuff shortly

Done, you can take off your tinfoil hats now :-)

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

[Mike Barcroft]

Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html

--
 Rebuilding the temporary build tree
--
 stage 1: bootstrap tools
--
 stage 2: cleaning up the object tree
--
 stage 2: rebuilding the object tree
--
 stage 2: build tools
--
 stage 3: cross tools
--
 stage 4: populating 
 /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include
--
 stage 4: building libraries
--
 stage 4: make dependencies
--
 stage 4: building everything..
--
 Kernel build for GENERIC started on Mon Mar  3 08:17:05 EST 2003
--
=== hme
make: don't know how to make bsd.README. Stop
*** Error code 2

Stop in /tinderbox/sparc64/src.
*** Error code 1

Stop in /tinderbox/sparc64/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

hype(r)threading

[Petri Helenius]

I seem to want to quite the opposite what other people would like to happen,
we have a supermicro P4DPR board with two Xeon´s. Since lately the kernel seems to
want to launch the virtual cores regardless of BIOS setting of HyperThreading being
[Disabled].

Any ideas how to disable the cores since our workload is does not benefit from
having more than two cores in a machine.

Pete


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: TI WiFi Drivers

[Brad Knowles]

At 7:27 PM + 2003/03/01, Suneel Jhangiani wrote:

 Does anyone know if someone is working on WiFi drivers for cards based
 on the TI chipset running at 22Mbps (ie. D-link DWL-650+ pcmcia card)?
	If you can get them, please let me know.

	A friend  co-worker (Bas Vermeulen) does driver development for 
Linux, currently specializing in WiFi cards.  He has been able to get 
samples of the cards themselves, but can't get TI or any of their 
licensees to even talk to him about the specs or other sufficient 
information to allow him to write the driver.  If we can get a driver 
under the BSD license, I'm sure that'd help him write a driver for 
Linux, and he would be a very happy camper.

--
Brad Knowles, [EMAIL PROTECTED]
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

NTP server change

[Hiten Pandya]

Hi gang.

Can anyone who is into timekeeping, and lives in or near Finland let me
know if they approve of a change to sysinstall, which will allow us to
use an alternate time keeping NTP server -- the reason for doing this is
outlined in PR conf/46235.

Patch URL:
http://www.unixdaemons.com/~hiten/work/diffs/sysinstall-46235.patch

Cheers.

-- 
Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED])
http://www.unixdaemons.com/~hiten/
Index: menus.c
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/menus.c,v
retrieving revision 1.368
diff -u -r1.368 menus.c
--- menus.c 2003/02/03 16:14:33 1.368
+++ menus.c 2003/02/03 17:54:31
@@ -1754,12 +1754,12 @@
   { Spain,   slug.ctv.es,
dmenuVarsCheck, dmenuSetVariables, NULL,
ntpdate_enable=YES,ntpdate_flags=slug.ctv.es },
-  { Finland, tick.keso.fi,
+  { Finland, time1.mikes.fi,
dmenuVarsCheck, dmenuSetVariables, NULL,
-   ntpdate_enable=YES,ntpdate_flags=tick.keso.fi },
-  { Finland #2,  tock.keso.fi,
+   ntpdate_enable=YES,ntpdate_flags=time1.mikes.fi },
+  { Finland #2,  time2.mikes.fi,
dmenuVarsCheck, dmenuSetVariables, NULL,
-   ntpdate_enable=YES,ntpdate_flags=tock.keso.fi },
+   ntpdate_enable=YES,ntpdate_flags=time2.mikes.fi },
   { France,  ntp.obspm.fr,
dmenuVarsCheck, dmenuSetVariables, NULL, 
ntpdate_enable=YES,ntpdate_flags=ntp.obspm.fr },

Re: Any ideas why we can't even boot a i386 ?

[John Baldwin]

On 28-Feb-2003 Terry Lambert wrote:
 John Baldwin wrote:
 Or you can use PXE at your provisioning center and have the
 BIOS setup to boot from the hard disk first, which will fail
 for the initial boot and fall back to PXE.  Then once the box
 is installed you ship it to its destination.
 
 This is a possibility; however, there are a number of system
 failure scenarios that make this undesirable.  Specifically,
 it's desirable to support the idea of a fallback boot (e.g.
 nextboot) for a partially functional system, to downgrade
 it automatically, and make it at least something other than a
 doorstop on which one has to pay international shipping.  In
 your scenario, there's no possible reupgrade method.

We perform upgrades in the field using a different transport.
In the case of major problems it is possible to ship a new
drive out to a system.

 We just launched a closed-box appliance yesterday.  Actually,
 it's going live to actual customers in about an hour and a
 half, but I digress. :)
 
 You should shout it to the world... at least post a press release
 to -advocacy!

The real press release is coming from my company's PR department.
Not sure of an ETA though.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: can't sshd into box

[Mike Barcroft]

Wayne [EMAIL PROTECTED] writes:
 Dear Jason,
 
[Not too many people jumping onto this thread to help me.]
 
The first two non-bold lines on rebooting, are:
 hw.bus.devctl_disable: 0 - 1
 Entropy harvesting: interrupts ethernet point_to_point.
 
 So I try:
 [EMAIL PROTECTED]:/home/waynesysctl hw.bus.devctl_disable: 1 - 0
[but the result is:]
 sysctl: unknown oid 'hw.bus.devctl_disable:'
 
 So what the heck is Entropy harvesting ?  Could this
 be blocking my incoming contact attempts?

I missed most of this thread, but to set the sysctl you want to:
`sysctl hw.bus.devctl_disable=0'.  See random(4) for details on
entropy harvesting.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: can't sshd into box

[Andre Guibert de Bruet]

On Sun, 2 Mar 2003, Terry Lambert wrote:

 Andre Guibert de Bruet wrote:
  On Mon, 3 Mar 2003, Wayne Barnes wrote:
   Immediately after rebooting, I get this:
  
   [EMAIL PROTECTED]:/home/waynetelnetd -debug
 ^^^
   telnetd: bind: Address already in use
  
   This doesn't happen on my other (working) system.
   Could this be a clue to my problem?
 
  Telnetd is telling you that something else is listening on port 23. This
  is most probably inetd. Do a 'killall inetd' then try that command.

 That's not only going to stop inetd from sitting on the port,
 it will probably also make telnet into the box start working,
 if it's related to the TCP wrappers (if he had modified his
 hosts.allow with the advice from a previous poster, he would
 not be having this problem, if that happens, so rather than
 posting his problem over and over again, maybe he should read
 the responses, and at least tell us if they worked?).

 Otherwise, another common culprit is ipfw; if he has the
 firewall enabled, the default is to block everything.

 Given that he got a connection, and that it was subsequently
 closed, though, rather than not getting a connection at all,
 it's a safe bet that it's the TCP wrappers, not the ipfw, that
 is causing the trouble.

 In which case, he should take the advice on the hosts.allow
 file contents that he was given earlier, and it will fix his
 problem...

Terry,

Part of the original message said the following:
quote
I have installed 5.0 into a new Dell.  I have not set up anything
special yet (no firewall, no natd, etc.).
...
Is there a new default connecton protection that I must turn off, or
something?  [/etc/hosts.allow  is the default setting, I see no answer
there.]
/quote

If I recall correctly, we don't ship GENERIC with any firewalling options
enabled, so like you said, this is not likely to be a firewalling issue.

5.0R's /etc/hosts.allow shipped with something like the following at the
top of the file:
# Start by allowing everything (this prevents the rest of the file
# from working, so remove it when you need protection).
# The rules here work on a First match wins basis.
ALL : ALL : allow

If Wayne was trying to run 'telnetd -debug', would it not make sense for
him to kill inetd first (or at least reconfigure inetd.conf then hup it)
before running the daemon in debug mode at the command line?

Wayne: Can you successfully login using telnet over the loopback
interface?

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Hyperactive ICH2 sound (with workaround)

[Kevin Oberman]

 From: Jun Su [EMAIL PROTECTED]
 Date: Sat, 1 Mar 2003 10:44:57 +0800
 
 Soory for my English. there is a time delay in playback. Thanks. If you need 
 me do any test, I am glad to do.

Please don't apologize for your English. I assure you that my (German,
French, Chinese, Korean, Spanish, etc.) is far worse.

Thanks for the added information. I have an ICH3 in my ThinkPad and it
shows the same behavior, but running Stable. It is not clear to me if
this is intentional or not, but it's not unique to Current.

I use the system for GnomeMeeting (H.323 conferencing) and it does not
seem to cause problems there, nor does it do so when using mplayer or
ogle to play DVDs. But it is easy to demonstrate with 'cat /dev/dsp 
/dev/dsp'. It seems likely to me that this is an issue only when running
in full-duplex (simultaneous input and output).

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

[tlambert2@mindspring.com: Re: can't sshd into box]

[Wayne Barnes]

Dear FreeBSD,

   1.  My /etc/hosts.allow is the untouched default, with the first 
uncommented line being 
ALL : ALL : allow

   Also, I am still running the default GENERIC kernel, so
there is no ipfw capability:
FreeBSD etaq3 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 
2003
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386


   2.  If I kill inetd, indeed 'telnet -debug' does not give an error.
It seems to be running and waiting for something ...
Going back to the other box etaq and trying to 'telnet etaq3' in, however, 
still results in:
Connection closed by foreign host.

 Looking back at the waiting telnet job, it has no message or 
anything.

 Trying it with 'telnetd -debug -D report'
doesn't give any messages, either

   3.  If you missed my response (maybe not copied to the list correctly)
about ALL:ALL:allow, maybe you missed that 'portscanner etaq3' from etaq
(the 4.7) reports that etaq3 (the new 5.0 system) has open ports 22, 23,
25, and 110.  They all result in immediate 'Connection closed by foreign
host.', even while ps reports that 'telnet -debug' is running.
Actually, 'telnet etaq3 110' has a slightly different rejection:
[EMAIL PROTECTED]:/home/waynetelnet etaq3 110
Trying 192.168.0.12...
telnet: connect to address 192.168.0.12: Connection refused
telnet: Unable to connect to remote host

   4.  There is one possibly relevant fact that I have not mentioned,
yet:
sysinstall cannot see the (motherboard?) ethernet port on this Dell
2350.  As FTP connection, it only offered dialup ppp or serial, etc. So I
put in a years-old SMC1211TX ethernet PCI card, and that was recognized
easily as rl0.

On bootup, of the FTP-installed 5.0 system, only one NIC is
recognized, as rl0, and I only plugged the old PCI card with an ethernet
cord; so I don't think this is really causing my problem.

I can connect and conduct ssh sessions outward (that's how I am typing
now), so this machine can receive packets at all.

I just can't telnet or ssh into it.  I haven't tried to install
apache, yet, but I wouldn't expect much until an ssh or telnet probe
works.  It does ping just fine, both ways.

  - Wayne

- Forwarded message from Terry Lambert [EMAIL PROTECTED] -

Andre Guibert de Bruet wrote:
 On Mon, 3 Mar 2003, Wayne Barnes wrote:
  Immediately after rebooting, I get this:
 
  [EMAIL PROTECTED]:/home/waynetelnetd -debug
  telnetd: bind: Address already in use
 
  This doesn't happen on my other (working) system.
  Could this be a clue to my problem?
 
 Telnetd is telling you that something else is listening on port 23. This
 is most probably inetd. Do a 'killall inetd' then try that command.

That's not only going to stop inetd from sitting on the port,
it will probably also make telnet into the box start working,
if it's related to the TCP wrappers (if he had modified his
hosts.allow with the advice from a previous poster, he would
not be having this problem, if that happens, so rather than
posting his problem over and over again, maybe he should read
the responses, and at least tell us if they worked?).

Otherwise, another common culprit is ipfw; if he has the
firewall enabled, the default is to block everything.

Given that he got a connection, and that it was subsequently
closed, though, rather than not getting a connection at all,
it's a safe bet that it's the TCP wrappers, not the ipfw, that
is causing the trouble.

In which case, he should take the advice on the hosts.allow
file contents that he was given earlier, and it will fix his
problem...

-- Terry


   --  Wayne M Barnes, [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

install via serial console

[James E. Flemer]

I've read the recent discussion[1] about why the install
media cannot use /boot/loader -P (broken K7 mobo's).  Is
this still the case?  Perhaps there could be a second
'miniinst' that had /boot/loader -h in the /boot.config
to facilitate install on headless machines.  I am aware of
how trivial it is to fix the standard kern.flp to use
serial console.  However, fixing an iso or building a new
one for serial console is not quite so quick.  (Nor is
finding the necessary combination of working floppy drives
and disks in my case.)

[1] Message Id: [EMAIL PROTECTED]
on freebsd-current.

-James


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: can't sshd into box

[Wayne Barnes]

Dear Andre,

Yes, I can telnet and ssh on loopback.  Boy, that debug setting
on the telnetd sure dumps a lot of output on the telnet side (but
is still silent on the screen where I started it).

  - Wayne

On Mon, Mar 03, 2003 at 10:48:15AM -0500, Andre Guibert de Bruet wrote:
 
 On Sun, 2 Mar 2003, Terry Lambert wrote:
 
  Andre Guibert de Bruet wrote:
   On Mon, 3 Mar 2003, Wayne Barnes wrote:
Immediately after rebooting, I get this:
   
[EMAIL PROTECTED]:/home/waynetelnetd -debug
  ^^^
telnetd: bind: Address already in use
   
This doesn't happen on my other (working) system.
Could this be a clue to my problem?
  
   Telnetd is telling you that something else is listening on port 23. This
   is most probably inetd. Do a 'killall inetd' then try that command.
 
  That's not only going to stop inetd from sitting on the port,
  it will probably also make telnet into the box start working,
  if it's related to the TCP wrappers (if he had modified his
  hosts.allow with the advice from a previous poster, he would
  not be having this problem, if that happens, so rather than
  posting his problem over and over again, maybe he should read
  the responses, and at least tell us if they worked?).
 
  Otherwise, another common culprit is ipfw; if he has the
  firewall enabled, the default is to block everything.
 
  Given that he got a connection, and that it was subsequently
  closed, though, rather than not getting a connection at all,
  it's a safe bet that it's the TCP wrappers, not the ipfw, that
  is causing the trouble.
 
  In which case, he should take the advice on the hosts.allow
  file contents that he was given earlier, and it will fix his
  problem...
 
 Terry,
 
 Part of the original message said the following:
 quote
 I have installed 5.0 into a new Dell.  I have not set up anything
 special yet (no firewall, no natd, etc.).
 ...
 Is there a new default connecton protection that I must turn off, or
 something?  [/etc/hosts.allow  is the default setting, I see no answer
 there.]
 /quote
 
 If I recall correctly, we don't ship GENERIC with any firewalling options
 enabled, so like you said, this is not likely to be a firewalling issue.
 
 5.0R's /etc/hosts.allow shipped with something like the following at the
 top of the file:
 # Start by allowing everything (this prevents the rest of the file
 # from working, so remove it when you need protection).
 # The rules here work on a First match wins basis.
 ALL : ALL : allow
 
 If Wayne was trying to run 'telnetd -debug', would it not make sense for
 him to kill inetd first (or at least reconfigure inetd.conf then hup it)
 before running the daemon in debug mode at the command line?
 
 Wayne: Can you successfully login using telnet over the loopback
 interface?
 
 Regards,
 
  Andre Guibert de Bruet | Enterprise Software Consultant 
  Silicon Landmark, LLC. | http://siliconlandmark.com/
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

-- 

   --  Wayne M Barnes, [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Volunteer with genuine i386 cpu lots of time wanted.

[John Baldwin]

On 01-Mar-2003 Ruslan Ermilov wrote:
 On Thu, Feb 27, 2003 at 05:05:43PM -0500, John Baldwin wrote:
 
 On 27-Feb-2003 Mike Barcroft wrote:
  John Baldwin [EMAIL PROTECTED] writes:
  Fixed.  Apparently people don't compile kernels for 80386's very often.
  
  Maybe LINT should be building I386 instead of more modern processors.
 
 That would turn off a lot of the CPU options that LINT covers.  You would
 lose more than you gain.
 
 Should I add the nocpu option to config(8)?  :-)

No.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

¦³¾÷·|§AÄ@·N¥h¹Á¸Õ¶Ü??

[star]

Title: ¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿


¥D¦®: ³o©Î³\¬O±z¥¿¦b´M§äªº¾÷·|³á 
 
 
 
   
   
³o©Î³\¬O±z¥¿¦b§äªº¾÷·|[EMAIL PROTECTED] 
   
¹ï¤£°_¡I¥´ÂZ¤F¡A¦pªG¦]¦¹³y¦¨±zªº§xÂZ¡A½Ðª½±µ§R°£¥»«H¤ÎÂI¿ï¤U¤è¡u¤£·Q¦A¦¬«H¡v¡A§Ú­Ì·|±N±zªº¸ê®Æ§R°£¡I 
   
 
   
 
   
¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿¡A¦¬¤J¦h100­¿¡B¬Æ¦Ü¦h1000­¿¡AÃø¹D¥L¦³¤ñ§A¦hÁo©ú³o»ò¦h¶Ü¡H 
   
µª®×ªÖ©w¤£¬Oªº¡I 
   
[EMAIL PROTECTED] 
   
¥L­Ì¨ì©³°µ¤F¤°»ò¬O§Ú­Ì©Ò¤£ª¾¹Dªº¨Æ¡H 
   
¦Ó§Ú­Ì¨ì©³°µ¿ù¤F¤°»ò¡B¤S¿ù¹L¤F¤°»ò¡H 
   
·Q¤£·Qª¾¹D¤H®a«ç»ò°µ­Ëªº¡I
  
§A¬Û«H¡u®É¶¡¡×ª÷¿ú¡v¡BÁÙ¬O¡u®É¶¡¡Öª÷¿ú¡v
  

  Á|¨Ò¡G
  
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@®É¼Æ¡H
  
¢·¤p®É¡¯¢²¢µ¢´¤Ñ¡¯¢²¢¯¦~¡×¢·¢¶,¢µ¢¯¢¯¤p®É
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]
  
³o¼Ëªº¦¬¤J¡A¨¬°÷¤TÀ\·Å¹¡¡F¶R¨®¤l¡B©Ð¤l«j±j°÷¥Î¡F§O§Ñ¤F¡AÁÙ¦³¤l¤kªº±Ð¨|¶O¡B¦Û¤vªº¾i¦Ñª÷¡BÁÙ¦³¡y¹Ú·Q¡zµ¥«Ý¹ê²{¡I
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@¥Í¡H
  

  

  
¤£·Q¦A¦¬«H(Unsubscribe) 


¡@




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Panic running mozilla when doing bg fsck

[Ollivier Robert]

Hello everyone,

I'm having panic fairly regularely at the moment and I've seen that trying
to run mozilla when fsck_ffs is doing its work in the background is a Bad
Thing[tm].

While I'm here, am I the only one to notice that stack traces are not very
complete right now?

initial pcb at physical address 0x00321080
panicstr: bremfree: bp 0xc7797a70 not locked
panic messages:
---
panic: Most recently used by none


syncing disks, buffers remaining... panic: bremfree: bp 0xc7797a70 not locked
Uptime: 7m37s
Dumping 255 MB
ata0: resetting devices ..
done
[CTRL-C to abort] [CTRL-C to abort]  16[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to 
abort]  32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
#0  doadump () at ../../../kern/kern_shutdown.c:239
239 dumping++;
(kgdb) where
#0  doadump () at ../../../kern/kern_shutdown.c:239
#1  0xc019d6a5 in boot (howto=260) at ../../../kern/kern_shutdown.c:371
#2  0xc019d8e3 in panic () at ../../../kern/kern_shutdown.c:542
#3  0xc01d7c47 in bremfreel (bp=0xc02d9d6d) at ../../../kern/vfs_bio.c:672
#4  0xc01d7bb5 in bremfree (bp=0x0) at ../../../kern/vfs_bio.c:659
#5  0xc01d9cdb in vfs_bio_awrite (bp=0xc264f000)
at ../../../kern/vfs_bio.c:1714
#6  0xc01e0def in vop_stdfsync (ap=0xcdd8eaf4)
at ../../../kern/vfs_default.c:755
#7  0xc016ad40 in spec_fsync (ap=0xcdd8eaf4)
at ../../../fs/specfs/spec_vnops.c:422
#8  0xc016a2f8 in spec_vnoperate (ap=0x0)
at ../../../fs/specfs/spec_vnops.c:123
#9  0xc02513a7 in ffs_sync (mp=0xc25a5200, waitfor=2, cred=0xc0eb5e80, 
td=0xc02fa620) at vnode_if.h:612
#10 0xc01eca6b in sync (td=0xc02fa620, uap=0x0)
at ../../../kern/vfs_syscalls.c:138
#11 0xc019d2f2 in boot (howto=256) at ../../../kern/kern_shutdown.c:280
#12 0xc019d8e3 in panic () at ../../../kern/kern_shutdown.c:542
#13 0xc027895d in mtrash_ctor (mem=0xc264f000, size=0, arg=0x0)
at ../../../vm/uma_dbg.c:138
#14 0xc0278a00 in mtrash_fini (mem=0x0, size=0) at ../../../vm/uma_dbg.c:189
#15 0xc02762a9 in zone_drain (zone=0x100) at ../../../vm/uma_core.c:630
#16 0xc0276ee5 in zone_foreach (zfunc=0xc0276070 zone_drain)
at ../../../vm/uma_core.c:1166
#17 0xc0278277 in uma_reclaim () at ../../../vm/uma_core.c:1997
#18 0xc0272ef9 in vm_pageout_scan (pass=0) at ../../../vm/vm_pageout.c:691
#19 0xc0273fae in vm_pageout () at ../../../vm/vm_pageout.c:1480
#20 0xc018a6d4 in fork_exit (callout=0xc0273ce0 vm_pageout, arg=0x0, 
frame=0x0) at ../../../kern/kern_fork.c:871

[there must be something here after frame #20, right?]
-- 
Ollivier ROBERT  -=-  Eurocontrol EEC/AMI  -=-  [EMAIL PROTECTED]
FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Tue Jan 21 16:05:16 CET 2003

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: [tlambert2@mindspring.com: Re: can't sshd into box]

[Barney Wolff]

On Mon, Mar 03, 2003 at 10:22:21AM -0600, Wayne Barnes wrote:
  Looking back at the waiting telnet job, it has no message or 
 anything.
 
  Trying it with 'telnetd -debug -D report'
 doesn't give any messages, either

Use tcpdump to make sure your machine is actually receiving the telnet
connection.  It sounds as though something else is getting it.

-- 
Barney Wolff http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

¦³¾÷·|§AÄ@·N¥h¹Á¸Õ¶Ü??

[star]

Title: ¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿


¥D¦®: ³o©Î³\¬O±z¥¿¦b´M§äªº¾÷·|³á 
 
 
 
   
   
³o©Î³\¬O±z¥¿¦b§äªº¾÷·|[EMAIL PROTECTED] 
   
¹ï¤£°_¡I¥´ÂZ¤F¡A¦pªG¦]¦¹³y¦¨±zªº§xÂZ¡A½Ðª½±µ§R°£¥»«H¤ÎÂI¿ï¤U¤è¡u¤£·Q¦A¦¬«H¡v¡A§Ú­Ì·|±N±zªº¸ê®Æ§R°£¡I 
   
 
   
 
   
¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿¡A¦¬¤J¦h100­¿¡B¬Æ¦Ü¦h1000­¿¡AÃø¹D¥L¦³¤ñ§A¦hÁo©ú³o»ò¦h¶Ü¡H 
   
µª®×ªÖ©w¤£¬Oªº¡I 
   
[EMAIL PROTECTED] 
   
¥L­Ì¨ì©³°µ¤F¤°»ò¬O§Ú­Ì©Ò¤£ª¾¹Dªº¨Æ¡H 
   
¦Ó§Ú­Ì¨ì©³°µ¿ù¤F¤°»ò¡B¤S¿ù¹L¤F¤°»ò¡H 
   
·Q¤£·Qª¾¹D¤H®a«ç»ò°µ­Ëªº¡I
  
§A¬Û«H¡u®É¶¡¡×ª÷¿ú¡v¡BÁÙ¬O¡u®É¶¡¡Öª÷¿ú¡v
  

  Á|¨Ò¡G
  
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@®É¼Æ¡H
  
¢·¤p®É¡¯¢²¢µ¢´¤Ñ¡¯¢²¢¯¦~¡×¢·¢¶,¢µ¢¯¢¯¤p®É
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]
  
³o¼Ëªº¦¬¤J¡A¨¬°÷¤TÀ\·Å¹¡¡F¶R¨®¤l¡B©Ð¤l«j±j°÷¥Î¡F§O§Ñ¤F¡AÁÙ¦³¤l¤kªº±Ð¨|¶O¡B¦Û¤vªº¾i¦Ñª÷¡BÁÙ¦³¡y¹Ú·Q¡zµ¥«Ý¹ê²{¡I
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@¥Í¡H
  

  

  
¤£·Q¦A¦¬«H(Unsubscribe) 


¡@




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: can't sshd into box]

[Terry Lambert]

Wayne Barnes wrote:
4.  There is one possibly relevant fact that I have not mentioned,
 yet:
 sysinstall cannot see the (motherboard?) ethernet port on this Dell
 2350.  As FTP connection, it only offered dialup ppp or serial, etc. So I
 put in a years-old SMC1211TX ethernet PCI card, and that was recognized
 easily as rl0.
 
 On bootup, of the FTP-installed 5.0 system, only one NIC is
 recognized, as rl0, and I only plugged the old PCI card with an ethernet
 cord; so I don't think this is really causing my problem.
 
 I can connect and conduct ssh sessions outward (that's how I am typing
 now), so this machine can receive packets at all.
 
 I just can't telnet or ssh into it.  I haven't tried to install
 apache, yet, but I wouldn't expect much until an ssh or telnet probe
 works.  It does ping just fine, both ways.

ifconfig
netstat -af inet

We would also like the output of ifconfig or ifconfig -a,
whichever one dumps out all configured interfaces, from one of
the working hosts on your network.

At this point, it's likely either netmask or a bad ethernet card.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: FreeBSD Bluetooth stuff

[Maksim Yevmenkin]

Hello Dustin,

1) compile and install hcidump from the snapshot's ports/ directory
Recompiled and reinstalled.  All went fine.
good

2) make sure you have clean setup, i.e.
  - run # rc.bluetooth stop device
  - disconnect the device from the PC
  - reset mouse
  - connect device back to PC
  - run # rc.bluetooth start device
  - in separate window run # hcidump -x
  - run # hccontrol -n devicehci inquiry
  - run # sdptool browse BD_ADDR_of_your_mouse
I followed this sequence.  One thing to note is that the mouse tries it's
best to conserve power, so it only responds to any initial queries for a
few seconds after pressing the reset button.  I don't know exactly how
long, but it's pretty short.  Klausler makes a note of this on his site,
so it must have caused him a hiccup or two.
hmmm... if your mouse drains batteries so fast for how you long
can you use it?
Okay, here it is.  Turns out I think my batteries ran out of juice, which
was causing some of the problems.  I wasn't getting any response at all
after all sorts of resets so I tried seeing if I could find the keyboard
and it 'just worked'.  I replaced the batteries and got a response from
hccontrol inquiry.  Just in case replacing the batteries turned out to
reset it more than pressing the button I put the old batteries back in and
still got nothing.  When the batteries 'die' the mouse still lights up
(it's optical), and apparently the radio connection goes first.  Anyway,
without further adue here is the hcidump output:

# hcidump -x
[ inquiry part skipped ]

 HCI Command: Create Connection(0x01|0x0005) plen 13
  A8 D6 7E F2 50 00 18 CC 02 00 C3 4B 01
HCI Event: Command Status(0x0f) plen 4
  00 01 05 04

HCI Event: Connect Complete(0x03) plen 11
  00 29 00 A8 D6 7E F2 50 00 01 00
baseband connection is now open

 HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
  29 00 0F 00
 ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
HCI Event: Number of Completed Packets(0x13) plen 5
  01 29 00 01 00
HCI Event: Command Complete(0x0e) plen 6
  01 0D 08 00 29 00
ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 2
this is you PC adjusts link policy settings and request L2CAP
connection on PSM 1 (which is SDP)
ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
 ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x clen 0
HCI Event: Number of Completed Packets(0x13) plen 5
  01 29 00 01 00
ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x result 0 clen 0
ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x clen 4
MTU 48
here your PC tries to configure L2CAP channel (incoming path)
and mouse agrees. after that mouse tries to configure incoming
L2CAP channel and sets incoming MTU to 48 bytes. so far no
problems.
HCI Event: QoS Setup Complete(0x0d) plen 21
  00 29 00 00 01 00 00 00 00 00 00 00 00 F2 2B 00 00 FF FF FF
  FF
oh! i have never seen any device using this :) your mouse
actually wants to set QoS (Quality Of Service). anyway the
status is 00 - success, so no problem here.
 ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x result 0 clen 0
and this is your PC agress to use proposed L2CAP configuration.
So L2CAP connection is open and there was no problem.
 ACL data: handle 0x0029 flags 0x02 dlen 24
L2CAP(d): cid 0x40 len 20 [psm 1]
SDP SSA Req: tid 0x0 len 0xf
  pat uuid-16 0x1002 (PubBrwsGrp)
  max 0x
  aid(s) 0x - 0x
  cont 00
HCI Event: Number of Completed Packets(0x13) plen 5
  01 29 00 01 00
HCI Event: Number of Completed Packets(0x13) plen 5
  01 29 00 01 00
now sdptool sends SDP browse request to your mouse to figure
out which services are available.
ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x40 len 10 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x5
  cnt 0x2
 len 0x2 frm-len 0x1 n 0x0
  cont 00
... and the mouse returns nothing back to us :(

 ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
HCI Event: Number of Completed Packets(0x13) plen 5
  01 29 00 01 00
ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
and at this point sdptool is done and closes the L2CAP
connection.
bottom line: baseband + L2CAP works. you can talk to your
mouse. SDP does not return anything. possible problems:
1) mouse does not fully implement SDP. it is assumed that you have
   to know magic PSM for interrupt and control channel on the mouse.
2) SDP interoperability problem

one thing you could try is to ask mouse for the specific service,
rather then for all services. you can do it by
# sdptool search --bdaddr BD_ADDR HID

Note: HID is the service you looking 

Re: hype(r)threading

[Trish Lynch]

On Mon, 3 Mar 2003, Petri Helenius wrote:


 I seem to want to quite the opposite what other people would like to happen,
 we have a supermicro P4DPR board with two Xeon´s. Since lately the kernel seems to
 want to launch the virtual cores regardless of BIOS setting of HyperThreading being
 [Disabled].

 Any ideas how to disable the cores since our workload is does not benefit from
 having more than two cores in a machine.

 Pete


Currently, AFAIK, there is no way to do this.

Depending on what you are doing you can increase performance slightly by
setting machdep.cpu_idle_hlt=1

-Trish

--
Trish Lynch[EMAIL PROTECTED]
Ecartis Core Team [EMAIL PROTECTED]
EFNet IRC Operator @ efnet.demon.co.uk[EMAIL PROTECTED]
EFNet IRC Operator/SysAdmin @ irc.dkom.at [EMAIL PROTECTED]
Key fingerprint = 781D 2B47 AA4B FC88 B919  0CD6 26B2 1D62 6FC1 FF16


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: hype(r)threading

[Petri Helenius]

After some reading around I ended up putting a return; on top of
the mptable_hyperthread_fixup function and my performance is back.
Setting the sysctl helps some but it does not really fix the performance issues.

I would like to make the suggestion of making the HT fixup maybe a default
but allow disabling with a kernel variable?

Pete

On Mon, 3 Mar 2003, Petri Helenius wrote:


 I seem to want to quite the opposite what other people would like to happen,
 we have a supermicro P4DPR board with two Xeon´s. Since lately the kernel seems to
 want to launch the virtual cores regardless of BIOS setting of HyperThreading being
 [Disabled].

 Any ideas how to disable the cores since our workload is does not benefit from
 having more than two cores in a machine.

 Pete


Currently, AFAIK, there is no way to do this.

Depending on what you are doing you can increase performance slightly by
setting machdep.cpu_idle_hlt=1

-Trish

--
Trish Lynch[EMAIL PROTECTED]
Ecartis Core Team   [EMAIL PROTECTED]
EFNet IRC Operator @ efnet.demon.co.uk   [EMAIL PROTECTED]
EFNet IRC Operator/SysAdmin @ irc.dkom.at [EMAIL PROTECTED]
Key fingerprint = 781D 2B47 AA4B FC88 B919  0CD6 26B2 1D62 6FC1 FF16



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Possible patch for limiting APs at startup

[John Baldwin]

On 02-Mar-2003 Juli Mallett wrote:
 * De: Hiten Pandya [EMAIL PROTECTED] [ Data: 2003-03-01 ]
   [ Subjecte: Possible patch for limiting APs at startup ]
 Hello.
 
 Just as the topic says, do you think this patch is good enough, or gets
 even close to it?  I have tested the patch, and it seems to do it's job
 in the right way.  Some might call it hackery, but it's better than
 nothing I would suppose.
 
 I think your use of cpus to refer to APs only is silly, and also that
 overriding mp_naps instead of using a real cpus value and using it as
 a bounds check akin to MAXCPU, is a bit of the wrong direction.  As you
 know, the following is my patch, and it does not work, but I think,
 personally, the behaviour is saner, in theory at least :)

You should set mp_maxcpus prior to the mp_naps test so it isn't left
invalid in the common case.  Also, this patch doesn't limit HT cpu's
at all.  I could have a 4 cpu system with HTT and maxcpus=2, and I
will end up with 4 CPU's due to 2 logical CPU's per processor.  Perhaps
this is intentional?

 %%%
 Index: mp_machdep.c
 ===
 RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v
 retrieving revision 1.203
 diff -d -c -r1.203 mp_machdep.c
 *** mp_machdep.c  24 Feb 2003 14:36:03 -  1.203
 --- mp_machdep.c  2 Mar 2003 00:22:58 -
 ***
 *** 249,254 
 --- 249,259 
   /** XXX FIXME: what system files declare these??? */
   extern struct region_descriptor r_gdt, r_idt;
   
 + int mp_maxcpus = 0; /* max CPUs; not in BSS so it can be hacked. */
 + TUNABLE_INT(machdep.smp_max_cpus, mp_maxcpus);
 + SYSCTL_INT(_machdep, OID_AUTO, smp_max_cpus, CTLFLAG_RD,
 +mp_maxcpus, 1, Maximum number of CPUs to use.);
 + 
   int bsp_apic_ready = 0; /* flags useability of BSP apic */
   int mp_naps;/* # of Applications processors */
   int mp_nbusses; /* # of busses */
 ***
 *** 864,874 
   }
   }
   
 ! /* qualify the numbers */
 ! if (mp_naps  MAXCPU) {
   printf(Warning: only using %d of %d available CPUs!\n,
 ! MAXCPU, mp_naps);
 ! mp_naps = MAXCPU;
   }
   
   /* See if we need to fixup HT logical CPUs. */
 --- 869,881 
   }
   }
   
 ! /* use the smallest number of requested CPUs or CPUs we support. */
 ! if ((mp_maxcpus  0  mp_naps  mp_maxcpus) || mp_naps  MAXCPU) {
 ! if (mp_maxcpus = 0)
 ! mp_maxcpus = MAXCPU;
   printf(Warning: only using %d of %d available CPUs!\n,
 ! mp_maxcpus, mp_naps);
 ! mp_naps = mp_maxcpus;
   }
   
   /* See if we need to fixup HT logical CPUs. */
 %%%
 
 Thanx,
 juli.
 -- 
 Juli Mallett [EMAIL PROTECTED] - AIM: BSDFlata -- IRC: juli on EFnet
 OpenDarwin, Mono, FreeBSD Developer - ircd-hybrid Developer, EFnet addict
 FreeBSD on MIPS-Anything on FreeBSD - /* XXX Nothing to see here, now. */
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: hype(r)threading

[John Baldwin]

On 03-Mar-2003 Petri Helenius wrote:
 After some reading around I ended up putting a return; on top of
 the mptable_hyperthread_fixup function and my performance is back.
 Setting the sysctl helps some but it does not really fix the performance issues.
 
 I would like to make the suggestion of making the HT fixup maybe a default
 but allow disabling with a kernel variable?

I'm going to add a 'HTT' kernel option that I'll backport prior to 4.8.

 Pete
 
 On Mon, 3 Mar 2003, Petri Helenius wrote:
 

 I seem to want to quite the opposite what other people would like to happen,
 we have a supermicro P4DPR board with two Xeon´s. Since lately the kernel seems to
 want to launch the virtual cores regardless of BIOS setting of HyperThreading being
 [Disabled].

 Any ideas how to disable the cores since our workload is does not benefit from
 having more than two cores in a machine.

 Pete

 
 Currently, AFAIK, there is no way to do this.
 
 Depending on what you are doing you can increase performance slightly by
 setting machdep.cpu_idle_hlt=1
 
 -Trish
 
 --
 Trish Lynch[EMAIL PROTECTED]
 Ecartis Core Team   [EMAIL PROTECTED]
 EFNet IRC Operator @ efnet.demon.co.uk   [EMAIL PROTECTED]
 EFNet IRC Operator/SysAdmin @ irc.dkom.at [EMAIL PROTECTED]
 Key fingerprint = 781D 2B47 AA4B FC88 B919  0CD6 26B2 1D62 6FC1 FF16
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: potential for foot-shooting with KLD's

[Giorgos Keramidas]

On 2003-03-02 17:34, Michal Mertl [EMAIL PROTECTED] wrote:
 Imagine you decided to go with modular kernel. You comment out 'device
 random' in your kernel-config and place 'random_load=YES' in
 /boot/loader.conf. When you reboot and don't rebuild the kernel first, you
 have your machine unbootable - at least in case you previously had acpi in
 your kernel and acpi doesn't work without OS supplied dsdt (as in my
 case) or you need acpi as a module or any other module.

 The way out is to boot from install CDROM, have fixit floppy, mount the
 old root and remove the random.ko module. Which is pretty inconvenient,
 when you don't have the medias handy.

 The problem is that I can't ask loader not to load some module. It doesn't
 understand 'unset XX_load'. It doesn't work to say 'set XX_load=NO'
 either. The only way I found to make it not load the modules is to 'load
 /boot/kernel/kernel;set module_path=;boot'. Unfortunately it doesn't
 help me either because I need to load special acpi_dsdt.aml which isn't
 then loaded either.

How about `unset XX_load' ?

- Giorgos


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: hype(r)threading

[Petri Helenius]

Thanks, that´s greatly appreciated.

Pete



 On 03-Mar-2003 Petri Helenius wrote:
  After some reading around I ended up putting a return; on top of
  the mptable_hyperthread_fixup function and my performance is back.
  Setting the sysctl helps some but it does not really fix the performance issues.
 
  I would like to make the suggestion of making the HT fixup maybe a default
  but allow disabling with a kernel variable?

 I'm going to add a 'HTT' kernel option that I'll backport prior to 4.8.

  Pete
 
  On Mon, 3 Mar 2003, Petri Helenius wrote:
 
 
  I seem to want to quite the opposite what other people would like to happen,
  we have a supermicro P4DPR board with two Xeon´s. Since lately the kernel seems to
  want to launch the virtual cores regardless of BIOS setting of HyperThreading 
  being
  [Disabled].
 
  Any ideas how to disable the cores since our workload is does not benefit from
  having more than two cores in a machine.
 
  Pete
 
 
  Currently, AFAIK, there is no way to do this.
 
  Depending on what you are doing you can increase performance slightly by
  setting machdep.cpu_idle_hlt=1
 
  -Trish
 
  --
  Trish Lynch[EMAIL PROTECTED]
  Ecartis Core Team   [EMAIL PROTECTED]
  EFNet IRC Operator @ efnet.demon.co.uk   [EMAIL PROTECTED]
  EFNet IRC Operator/SysAdmin @ irc.dkom.at [EMAIL PROTECTED]
  Key fingerprint = 781D 2B47 AA4B FC88 B919  0CD6 26B2 1D62 6FC1 FF16
 
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message

 --

 John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
 Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: FreeBSD Bluetooth stuff

[Dustin Boontheekul]

Max,

This is probably where I'm going to have to stop for the week to make sure
I get my classwork done, you've been a wonderful guide.  I can't wait to
get started working on this some more.

 hmmm... if your mouse drains batteries so fast for how you long
 can you use it?

Actually, the battery life sucks for a wireless mouse.  I guess both the
RF part and the Bluetooth protocol eat up a lot of power.  It's my
understanding that RF mice tend to have shorter battery life than IR mice
anyway, and that adding the Bluetooth chip must use more.  I can get about
a month out of a set of batteries.  During extra high use this drops as
low as 2 weeks.  I read a review on activewin.com and the editor got a
month out of it (and he's an editor, so I magine he uses his machine a
lot).  The keyboard batteries last quite a bit longer (1.5 months
minimum).  A friend of mine has an IR keyboard and mouse that have had the
same batteries for 6 months, so going bluetooth isn't just more costly up
front, but also in maintanence costs.

 ACL data: handle 0x0029 flags 0x02 dlen 14
  L2CAP(d): cid 0x40 len 10 [psm 1]
  SDP SSA Rsp: tid 0x0 len 0x5
cnt 0x2
   len 0x2 frm-len 0x1 n 0x0
cont 00

 ... and the mouse returns nothing back to us :(

That sucks.  Well, as long as we can get it working in the end, no big
deal.

 bottom line: baseband + L2CAP works. you can talk to your
 mouse. SDP does not return anything. possible problems:

Good.

 1) mouse does not fully implement SDP. it is assumed that you have
 to know magic PSM for interrupt and control channel on the mouse.

 2) SDP interoperability problem

Either way at least we know somebody has gotten it working.

 one thing you could try is to ask mouse for the specific service,
 rather then for all services. you can do it by

 # sdptool search --bdaddr BD_ADDR HID

Bingo.  Nice response from the mouse.

# sdptool search --bdaddr $BT_ADDR HID
Searching for HID on 00:50:F2:7E:D6:A8 ...
Service Name: Wireless IntelliMouse Explorer for Bluetooth
Service Description: Five Button Mouse
Service Provider: Microsoft
Service RecHandle: 0x1
Service Class ID List:
   (0x1124)
Protocol Descriptor List:
  L2CAP (0x0100)
PSM: 17
   (0x0011)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:0x6a
  base_offset: 0x100
Profile Descriptor List:
   (0x1124)
Version: 0x0100

 well, you have to read Bluetooth spec :) but i can tell you right now
 that in this case it is safe to use 0 for all of them :)

Yup.  I've downloaded it from the bluetooth SIG's website, just haven't
extracted it for a look yet.

Also, my bluetooth enabled phone came in today (Ericsson R520m).  I'm
gonna check out which firmware revision it is and (if needed) send it off
for an update.  Then I can start playing around with a more conventional
Bluetooth device to learn the ins and outs better.

Thanks again,

Dustin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

strace and CURRENT?

[Atte Peltomaki]

Installed from ports, I get 

strace: open(/proc/..., ...): No such file or directory
trouble opening proc file

Clues?


Atte Peltomäki
http://kameli.org

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: strace and CURRENT?

[Chris Faulhaber]

On Mon, Mar 03, 2003 at 11:27:09PM +0200, Atte Peltomaki wrote:
 Installed from ports, I get 
 
 strace: open(/proc/..., ...): No such file or directory
 trouble opening proc file
 

Try mounting the /proc fs.

-- 
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

FreeBSD: The Power To Serve   -   http://www.FreeBSD.org


pgp0.pgp
Description: PGP signature

Re: FreeBSD Bluetooth stuff

[Maksim Yevmenkin]

Dustin,

This is probably where I'm going to have to stop for the week to make sure
I get my classwork done, you've been a wonderful guide.  I can't wait to
get started working on this some more.
no problem. thanks for your time :)

[...]

bottom line: baseband + L2CAP works. you can talk to your
mouse. SDP does not return anything. possible problems:
Good.

1) mouse does not fully implement SDP. it is assumed that you have
   to know magic PSM for interrupt and control channel on the mouse.
2) SDP interoperability problem
Either way at least we know somebody has gotten it working.
well, then we will get it working too :)

one thing you could try is to ask mouse for the specific service,
rather then for all services. you can do it by
# sdptool search --bdaddr BD_ADDR HID
Bingo.  Nice response from the mouse.
errr... those M$ bastards :)

# sdptool search --bdaddr $BT_ADDR HID
Searching for HID on 00:50:F2:7E:D6:A8 ...
Service Name: Wireless IntelliMouse Explorer for Bluetooth
Service Description: Five Button Mouse
Service Provider: Microsoft
Service RecHandle: 0x1
Service Class ID List:
   (0x1124)
Protocol Descriptor List:
  L2CAP (0x0100)
PSM: 17
   (0x0011)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:0x6a
  base_offset: 0x100
Profile Descriptor List:
   (0x1124)
Version: 0x0100
fine. we now see PSM 17. i guess it is a control channel. but where
another (interrupt) one? well, its spec reading time again :)
Also, my bluetooth enabled phone came in today (Ericsson R520m).  I'm
gonna check out which firmware revision it is and (if needed) send it off
for an update.  Then I can start playing around with a more conventional
Bluetooth device to learn the ins and outs better.
cool :)

thanks
max
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: -CURRENT + cvs = panic

[Vladimir Kushnir]

On Mon, 3 Mar 2003, Philipp Mergenthaler wrote:

 On Mon, Mar 03, 2003 at 01:23:20AM +0200, Vladimir Kushnir wrote:
  Practically 100% repeatable: after some CVS updates (not sure but it
  seems after another high HD load as well) -CURRENT panics with
  bwrite: buffer is not busy
  (in the prefious message I've attached gdb trace and so on, and nothing
  has changed so far).
  It goes on for at least several days now.

 In that gdb trace, I think the panic was only an aftereffect and
 the trouble started here:
 #15 0xc02bc1c8 in calltrap () at {standard input}:96
 #16 0xc021fd79 in tcp_input (m=0xc0d49c30, off0=20)
 at /usr/src/sys/netinet/tcp_input.c:2324

 Do you have version 1.198 of sys/netinet/tcp_input.c?  I haven't had
 that panic since then (i.e. for the last four days).

 Bye, Philipp

Yes:
src/sys/netinet/tcp_input.c,v 1.198 2003/02/26 18:20:41
Doesn't help, though. Of all cvs up ... or cvsup ... there was 1 or 2
that did not panic :-(

Regards,
Vladimir

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

current and vmware2

[James Satterfield]

I'm trying to run vmware2 on a recent -current. I'm getting these when trying to load 
the vmmon_up module.
kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko: No such file or 
directory
Also making an appearance in dmesg is link_elf: symbol cdevsw_add undefined.
Current from today. Using linux_base-7.1_2.
Linux module is loaded.

Any suggestions would be appreciated.

James.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: -CURRENT + cvs = panic

[Mikko Työläjärvi]

On Tue, 4 Mar 2003, Vladimir Kushnir wrote:

 On Mon, 3 Mar 2003, Philipp Mergenthaler wrote:

  On Mon, Mar 03, 2003 at 01:23:20AM +0200, Vladimir Kushnir wrote:
   Practically 100% repeatable: after some CVS updates (not sure but it
   seems after another high HD load as well) -CURRENT panics with
   bwrite: buffer is not busy
   (in the prefious message I've attached gdb trace and so on, and nothing
   has changed so far).
   It goes on for at least several days now.
 
  In that gdb trace, I think the panic was only an aftereffect and
  the trouble started here:
  #15 0xc02bc1c8 in calltrap () at {standard input}:96
  #16 0xc021fd79 in tcp_input (m=0xc0d49c30, off0=20)
  at /usr/src/sys/netinet/tcp_input.c:2324
 
  Do you have version 1.198 of sys/netinet/tcp_input.c?  I haven't had
  that panic since then (i.e. for the last four days).
 
  Bye, Philipp
 
 Yes:
 src/sys/netinet/tcp_input.c,v 1.198 2003/02/26 18:20:41
 Doesn't help, though. Of all cvs up ... or cvsup ... there was 1 or 2
 that did not panic :-(

Just to chime in: I get these panics almost daily on my laptop since
the last update (including tcp_input.c 1.198).  They used to happen
before as well, but less frequently.  Sadly, I no longer seem to get
crashdumps, but back when I did get them, the code path looked the
same (trap somewhere in tcp_input).

The crashes can happen at any time, even under very light load and are
invariably preceeded by the mouse freezing up, then a flurry of
error messages like:

  psmintr: delay too long; resetting byte count
  psmintr: out of sync ( != 0080).
  psmintr: discard a byte (1).
  psmintr: delay too long; resetting byte count
  psmintr: out of sync ( != 0080).
  psmintr: discard a byte (1).

Then the mouse recovers, but after that it looks like almost any
network activity will trigger a panic.  WITNESS does not print
anything.

  $.02,
  /Mikko

(Since the d*mn ACPI does not work anyway, I predict a downgrade to
 4.8 in the near future...)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: current and vmware2

[James Satterfield]

By the way... /usr/local/lib/vmware/lib/modules/vmmon_up.ko does exist.

James.


On Mon, 3 Mar 2003 14:57:12 -0800
James Satterfield [EMAIL PROTECTED] wrote:

 I'm trying to run vmware2 on a recent -current. I'm getting these when trying to 
 load the vmmon_up module.
 kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko: No such file or 
 directory
 Also making an appearance in dmesg is link_elf: symbol cdevsw_add undefined.
 Current from today. Using linux_base-7.1_2.
 Linux module is loaded.
 
 Any suggestions would be appreciated.
 
 James.
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

witness_get: witness exhausted?

[Andrew Gallatin]

I'm developing a character driver which tracks a lot of state on a
per-open basis.  I've got several mutexes in there which are
initialzed at open, and destroyed at close.  After a few
dozen opens, witness seems to croak with:

witness_get: witness exhausted

Am I leaking something?  Or is the witness code?  I looked at
subr_witness.c, and I don't see witness_free() being called from
witness_destroy().  There's probably some design constraint that
I don't understand.  

If the fault is with the witness code, can it be fixed?

FWIW, Witness (and the FreeBSD debugging environment in general) is
why I've gotten approval to co-develop this driver on FreeBSD (in
addition to linux).  Its already caught several locking bugs.

Thanks,

Drew



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: potential for foot-shooting with KLD's

[Michal Mertl]

 How about `unset XX_load' ?

It works only for acpi.

-- 
Michal Mertl
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

ATA unable to map interrupt

[Huang wen hui]

hi,
I can't boot recent CURRENT on PCM-5823. Is this the problem of ATA driver?

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD SBOX #0: Sun Mar 2 12:21:09 GMT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel /boot/kernel/kernel at 0xc0ab2000.
Preloaded mfs_root /boot/mfsroot at 0xc0ab20a8.
Timecounter i8254 frequency 1193182 Hz
Timecounter TSC frequency 299237489 Hz
CPU: Cyrix GXm (299.24-MHz 586-class CPU)
Origin = CyrixInstead Id = 0x540 DIR=0x8244 Stepping=8 Revision=2
real memory = 131596288 (125 MB)
avail memory = 116523008 (111 MB)
Allocating major#253 to net
Allocating major#252 to pci
md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc0678210
npx0: math processor on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 3 entries at 0xc00fd9b0
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
fxp0: Intel Embedded 10/100 Ethernet port 0xe000-0xe03f mem
0xe202-0xe203,0xe204-0xe2040fff irq 15 at device 11.0 on pci0
fxp0: Ethernet address 00:d0:c9:53:47:17
inphy0: i82555 10/100 media interface on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Intel Embedded 10/100 Ethernet port 0xe400-0xe43f mem
0xe200-0xe201,0xe2041000-0xe2041fff irq 11 at device 12.0 on pci0
fxp1: Ethernet address 00:d0:c9:53:47:18
inphy1: i82555 10/100 media interface on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: PCI-ISA bridge at device 18.0 on pci0
isa0: ISA bus on isab0
pci0: bridge, PCI-unknown at device 18.1 (no driver attached)
atapci0: Cyrix 5530 ATA33 controller port 0xf000-0xf00f at device 18.2
on pci0
atapci0: unable to map interrupt

pci0: multimedia, audio at device 18.3 (no driver attached)
pci0: display, VGA at device 18.4 (no driver attached)
ohci0: OHCI (generic) USB controller mem 0xe2045000-0xe2045fff irq 15
at device 19.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0: OHCI (generic) USB controller on ohci0
usb0: USB revision 1.0
uhub0: (0x0e11) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
orm0: Option ROM at iomem 0xc-0xc7fff on isa0
pmtimer0 on isa0
ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0
ata1 at port 0x376,0x170-0x177 irq 15 on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x100
db trace


Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc046a380
stack pointer = 0x10:0xc0ad49f8
frame pointer = 0x10:0xc0ad49fc
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 0 (swapper)
kernel: type 12 trap, code=0



--hwh



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: current and vmware2

[Garance A Drosihn]

At 2:57 PM -0800 3/3/03, James Satterfield wrote:
I'm trying to run vmware2 on a recent -current. I'm getting these
when trying to load the vmmon_up module.
   kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko:
   No such file or directory
Also making an appearance in dmesg is

   link_elf: symbol cdevsw_add undefined.

Current from today. Using linux_base-7.1_2.
Linux module is loaded.
This is a problem that came up in the past week or two.  I don't
know exactly what causes it, or how to fix it.  I suspect that it
is some recent kernel/device change, and it might very well be
easy to update the vmware2 port to work again.
I haven't had any time to look into it, but I did try doing a
force-rebuild of the rtc and vmware2 ports, and that did not seem
to fix it.
--
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: current and vmware2

[Franz Klammer]

Am Di, 2003-03-04 um 01.42 schrieb Garance A Drosihn:
 At 2:57 PM -0800 3/3/03, James Satterfield wrote:
 I'm trying to run vmware2 on a recent -current. I'm getting these
 when trying to load the vmmon_up module.
 
 kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko:
 No such file or directory
 
 Also making an appearance in dmesg is
 
 link_elf: symbol cdevsw_add undefined.
 
 Current from today. Using linux_base-7.1_2.
 Linux module is loaded.
 
 This is a problem that came up in the past week or two.  I don't
 know exactly what causes it, or how to fix it.  I suspect that it
 is some recent kernel/device change, and it might very well be
 easy to update the vmware2 port to work again.
 
 I haven't had any time to look into it, but I did try doing a
 force-rebuild of the rtc and vmware2 ports, and that did not seem
 to fix it.


no that doesn't help. i did an update of my kernel and userland
just one hour beforeTue (Mar  4 00:42:46 CET 2003) and since 
this time vmware2 didn't run.

i've recompiled vmware2 and rtc.

franz.

-- 
WEBONAUT.com
http://webonaut.com
mailto:[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Disaster strikes...

[walt]

After cvsup'ing just now I cannot reboot -CURRENT either with the new
kernel or the old kernel.
The new kernel panics instantly on boot, and the old kernel halts
with multiple messages about ACPI, so I'm stuck with an unbootable
machine.
What is the command to disable acpi at the boot prompt?  I tried
'toggle-module acpi' with no luck.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: potential for foot-shooting with KLD's

[Giorgos Keramidas]

On 2003-03-02 17:34, Michal Mertl [EMAIL PROTECTED] wrote:
: Imagine you decided to go with modular kernel. You comment out 'device
: random' in your kernel-config and place 'random_load=YES' in
: /boot/loader.conf. When you reboot and don't rebuild the kernel first, you
: have your machine unbootable - at least in case you previously had acpi in
: your kernel and acpi doesn't work without OS supplied dsdt (as in my
: case) or you need acpi as a module or any other module.
:
: The way out is to boot from install CDROM, have fixit floppy, mount the
: old root and remove the random.ko module. Which is pretty inconvenient,
: when you don't have the medias handy.
:
: The problem is that I can't ask loader not to load some module. It doesn't
: understand 'unset XX_load'. It doesn't work to say 'set XX_load=NO'
: either. The only way I found to make it not load the modules is to 'load
: /boot/kernel/kernel;set module_path=;boot'. Unfortunately it doesn't
: help me either because I need to load special acpi_dsdt.aml which isn't
: then loaded either.

On 2003-03-03 17:19:05, Giorgos Keramidas [EMAIL PROTECTED] wrote:
:
: How about `unset XX_load' ?
:
: - Giorgos

On 2003-03-04 00:41, Michal Mertl [EMAIL PROTECTED] wrote:
:  How about `unset XX_load' ?
:
: It works only for acpi.

I just tried editing my /boot/loader.conf to make sure you haven't hit
upon a bug.  I added this line:

ipfw_load=YES

and rebooted.  The loader loaded both /boot/kernel/kernel and ipfw.ko
as you'd expect.  I then used the `unload' command and loaded only my
kernel afterwards:

OK unload
OK load /boot/kernel/kernel
OK boot -s

Voila!  Only my kernel and acpi.ko were loaded.  Then, without editing
my /boot/loader.conf I rebooted and inteerrupted the loader after
ipfw.ko and the kernel were loaded.  I disabled ACPI with:

OK unset acpi_load
OK boot -s

Only the kernel and ipfw.ko were loaded.  Then, I tried yet another
way of disabling ipfw.ko at load time, and set ipfw_load to NO in
my loader.conf.  Only the kernel and acpi.ko were loaded.

What is it that troubles you?  I'm not sure I can reproduce it.

- Giorgos

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Disaster strikes...

[Andre Guibert de Bruet]

On Mon, 3 Mar 2003, walt wrote:

 After cvsup'ing just now I cannot reboot -CURRENT either with the new
 kernel or the old kernel.

 The new kernel panics instantly on boot, and the old kernel halts
 with multiple messages about ACPI, so I'm stuck with an unbootable
 machine.

 What is the command to disable acpi at the boot prompt?  I tried
 'toggle-module acpi' with no luck.

unset acpi_load

If you're still having problems, Make sure that you do
set module_path=/boot/kernel.old
at the loader prompt. This will ensure that you're not loading the new
modules with your old kernel.

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ATA problems

[Scotty]

I am getting the same

ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
error messages, and disk io pauses when it resets the devices for around 
3 seconds (estimated from mpg123 pause in play),
a brief description of my system until i reboot and submit a verbose 
dmesg later tonight:
Abit BP6 with 2 processors, Highpoint366 in dma mode, Western digital 80 gig
running -current from mid february sources

I am very willing to test patches to solve this problem

- Scott MacPhee

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Disaster strikes...

[walt]

Andre Guibert de Bruet wrote:
On Mon, 3 Mar 2003, walt wrote:


After cvsup'ing just now I cannot reboot -CURRENT either with the new
kernel or the old kernel.
The new kernel panics instantly on boot, and the old kernel halts
with multiple messages about ACPI, so I'm stuck with an unbootable
machine.


...set module_path=/boot/kernel.old
at the loader prompt. This will ensure that you're not loading the new
modules with your old kernel...


Yes!  This is exactly what I needed, thank you!  The old kernel
boots normally now.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

ATA MODE_SENSE_BIG timeout

[David Xu]

For those want to fix ATA code, I have another problem
with CURRENT.  I have a Tyan Tiger 230T which is based
on VIA Apollo 133T, south bridge is VIA 686B.
On second IDE,  I have a Mitsubishi 52X cdrom as master,
and a Sony 16X CD R/W as slave, when startup, kernel
is always stuck at MODE_SENSE_BIG timeout.
I fortunately catched the dmesg text since ATA code past the 
probing stage. In most case,  it will be stuck there forever.
BTW, both Linux (2.2.14, Redhat) and MS Windows can probe
these devices in few seconds without any problem.

Here is the dmesg:

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #4: Fri Feb 28 23:55:50 CST 2003
[EMAIL PROTECTED]:/home/davidxu/src/sys/i386/compile/xu2
Preloaded elf kernel /boot/kernel/kernel at 0xc04cc000.
Preloaded elf module /boot/kernel/vesa.ko at 0xc04cc0a8.
Preloaded elf module /boot/kernel/acpi.ko at 0xc04cc154.
Timecounter i8254  frequency 1193182 Hz
CPU: Intel Pentium III (999.67-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x68a  Stepping = 10
  
Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE
real memory  = 268369920 (255 MB)
avail memory = 255410176 (243 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00178011, at 0xfec0
Pentium Pro MTRR support enabled
VESA: v3.0, 32768k memory, flags:0x1, mode table:0xc047fca2 (122)
VESA: NVidia
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: VIA694 AWRDACPI on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00fdd20
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI-fast  frequency 3579545 Hz
acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0
acpi_cpu0: CPU on acpi0
acpi_cpu1: CPU on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 
0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
IOAPIC #0 intpin 5 - irq 2
IOAPIC #0 intpin 10 - irq 5
IOAPIC #0 intpin 11 - irq 10
agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xf000-0xf3ff at device 
0.0 on pci0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device 0.0 (no driver attached)
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: VIA 82C686b UDMA100 controller port 0xd000-0xd00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 2 at device 7.2 on pci0
usb0: VIA 83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub0: port error, restarting port 1
uhub0: port error, giving up port 1
uhub0: port error, restarting port 2
uhub0: port error, giving up port 2
uhci1: VIA 83C572 USB controller port 0xd800-0xd81f irq 2 at device 7.3 on pci0
usb1: VIA 83C572 USB controller on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub1: port error, restarting port 1
uhub1: port error, giving up port 1
uhub1: port error, restarting port 2
uhub1: port error, giving up port 2
pci0: bridge, PCI-unknown at device 7.4 (no driver attached)
pci0: multimedia, audio at device 9.0 (no driver attached)
ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xe400-0xe41f irq 10 at device 11.0 on 
pci0
ed0: address 52:54:ab:52:53:8f, type NE2000 (16 bit) 
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 
irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0 port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
pmtimer0 on isa0
orm0: Option ROM at iomem 0xc-0xcb7ff on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
Timecounters tick every 10.000 msec
acpi_cpu: throttling enabled, 2 steps 

nvidia module panics today's kernel [03-03-03]

[walt]

My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel panic even after re-compiling
the module.
Maxime, it looks like the nvidia module will need to be sculpted one
more time.   :-(
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Double fault with IBM microdrives and CompactFlash (LONG)

[Andre Guibert de Bruet]

Latest update:

pccard0: Allocation failed for cfe 0
ata2 at port 0x140-0x14f irq 10 function 0 config 1 on pccard0
ad4: 342MB IBM-DMDM-10340 [695/16/63] at ata2-master PIO1

# atacontrol cap 2 0 # Microdrive

ATA/ATAPI revision4
device model  IBM-DMDM-10340
serial number XHAF1669
firmware revision MD2IC501

# atacontrol cap 2 0 # Compactflash

ATA/ATAPI revision0
device model  TOSHIBA THNCF128MBA
serial number STCB21M82005E93599A5
firmware revision 2.00

It works! :-)

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: nvidia module panics today's kernel [03-03-03]

[Andre Guibert de Bruet]

On Mon, 3 Mar 2003, walt wrote:

 My mini 'disaster' of earlier today was caused by the nvidia kernel
 module being autoloaded at boot, which causes an immediate kernel panic.

 The newest kernel seems fine until I try to load the module manually,
 at which time I still get the kernel panic even after re-compiling
 the module.

 Maxime, it looks like the nvidia module will need to be sculpted one
 more time.   :-(

If you really need to use your workstation, you can try the open source nv
XFree86 driver. It's not as fast as the nVidia detonator driver and it's
not accelerated, but you can at least use X11 at a reasonable resolution
and color depth.

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

ltmdm is broken now... and the disaster is coming!

[Rossam Souza Silva]

I got CURRENT sources from some hours ago and made the same ritual:

buildworld, buidlkernel, installkernel, installworld, mergemaster.

I know, the mega-commit was made, so ltmdm is broken now:

[EMAIL PROTECTED]:/usr/ports/comms/ltmdm sudo make
*
If your ISP supports K56flex protocol only and
 doesn't support V90, define USE_595_OBJ.
Otheriwse your modem will not connect
*
===  Extracting for ltmdm-1.4_3
 Checksum OK for ltmdm-1.4.tgz.
===  Patching for ltmdm-1.4_3
===  Applying FreeBSD patches for ltmdm-1.4_3
===  Configuring for ltmdm-1.4_3
===  Building for ltmdm-1.4_3
Warning: Object directory not changed from original
/usr/ports/comms/ltmdm/work/sys/modules/ltmdm
@ - /usr/src/sys
machine - /usr/src/sys/i386/include
awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
uudecode -p
/usr/ports/comms/ltmdm/work/sys/modules/ltmdm/../../dev/ltmdm/ltmdmobj-600.o.uu
ltmdmobj.o
cc -O -pipe -march=athlon-xp -DLTMDMOBJ_VERSION=600 -DCDEV_MAJOR=228
-D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-   -I. -I@ -I@/dev
-I@/../include -I/usr/include -fno-common  -mno-align-long-strings
-mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -fformat-extensions -ansi -c
/usr/ports/comms/ltmdm/work/sys/modules/ltmdm/../../dev/ltmdm/ltmdmsio.c
In file included from
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:63:
@/sys/dkstat.h:45:2: warning: #warning sys/dkstat.h is deprecated and
should not be #include'd
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:363: warning:
initialization makes integer from pointer without a cast
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:364: warning:
initialization makes integer from pointer without a cast
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:365: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:366: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:367: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:368: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:369: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:370: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:371: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:372: warning:
initialization makes pointer from integer without a cast
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:373: warning:
initialization from incompatible pointer type
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:384: `D_KQFILTER'
undeclared here (not in a function)
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:384: initializer
element is not constant
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:384: (near
initialization for `sio_cdevsw.d_kqfilter')
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:385: warning: excess
elements in struct initializer
/usr/ports/comms/ltmdm/work/sys/dev/ltmdm/ltmdmsio.c:385: warning: (near
initialization for `sio_cdevsw')
*** Error code 1

Stop in /usr/ports/comms/ltmdm/work/sys/modules/ltmdm.
*** Error code 1

Stop in /usr/ports/comms/ltmdm.

I can stay online because not booted yet, and I have another problem:
a nForce based motherboard w/ Integrated GeForce2. This system don't work
with X Window's nv driver, only with nVIDIA's one. I saw that nvidia
module is broken again. My hope now is on Maxime, the hero of nVIDIA
users! :)

--
(_ )   Contrary to popular belief, UNIX is user friendly. It just happens
 \\\'',) ^  to be very selective about who it decides to make friends with.
   \/  \(
   .\._/_)  Rossam Souza Silva ([EMAIL PROTECTED])
--





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

SCHED_ULE ok again. feedback please?

[Jeff Roberson]

I'm using SCHED_ULE on my laptop now.  My recent round of fixes seems to
have helped out.  I'm getting good interactive performance.  I'm doing the
following:

nice -5'd for (;;) {} process.
make -j4 buildworld

Mozilla, pine, irc, screen, vi, etc.

All interactive tasks are very responsive.  My nice -5'd looping process
is getting 70% of the cpu and my compile is taking the rest.  nice +20 may
not behave as well as in sched_4bsd right now.  I'm going to work on that.

This is on a 2ghz laptop though so your mileage may vary.  Use reports are
welcome.

Interactivity suffered so much over the last few weeks because I changed
the mechanism that determines interactivity and that impacts slice
assignment and priorities.  It took me a while to get it right but it
solved a major drawback with the old scheme.  I do not anticipate any
major rework on this part of the scheduler now.  It should only be tuning.

One thing that I'm looking for feedback on specifically is expensive but
interactive applications.  I'm thinking of office programs or mozilla on a
slow machine.  Do this while running a compile or a compute bound task.

Thanks,
Jeff


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: nvidia module panics today's kernel [03-03-03]

[Rossam Souza Silva]

 If you really need to use your workstation, you can try the open source nv
 XFree86 driver. It's not as fast as the nVidia detonator driver and it's
 not accelerated, but you can at least use X11 at a reasonable resolution
 and color depth.

 Regards,

With nForce based motherboards, it seems to not help. My machine locks
up with nv driver, X don't start, locks hard. I tried before with FreeBSD
4.x/CURRENT and OpenBSD 3.2-beta/3.2, only works with NetBSD.

Rossam.

  Andre Guibert de Bruet | Enterprise Software Consultant 
  Silicon Landmark, LLC. | http://siliconlandmark.com/

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: nvidia module panics today's kernel [03-03-03]

[Rossam Souza Silva]

 If you really need to use your workstation, you can try the open source nv
 XFree86 driver. It's not as fast as the nVidia detonator driver and it's
 not accelerated, but you can at least use X11 at a reasonable resolution
 and color depth.

 Regards,

If you have a nForce based machine that locks up with nv driver, you can
use the VESA driver... no big performance, but you can even watch DVDs!

PS: Slow in fullscreen mode, my machine has a AMD Athlon XP 1800+. YMMV.

Rossam.

  Andre Guibert de Bruet | Enterprise Software Consultant 
  Silicon Landmark, LLC. | http://siliconlandmark.com/

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

smp-kernel panics while booting

[Till Plewe]

I have 2 Xeon processors on a PDPEA (Rioworks) motherboard 
(http://www.rioworks.co.jp/products/pdpea.html).

The generic kernel boots without problems (see output of dmesg below).

When I use the SMP kernel I invariably (5.0 release, various CURRENTs,
the latest cvsuped yesterday, various BIOS settings) get:

CPU ...
real memory ...
avail memory ...

Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
Programming 24 pins in IOAPIC #1
Programming 24 pins in IOAPIC #2
AP #1 (PHY# 1) failed!
panic y/n [y] Uptime: 1s
panic: Assertion mtx_unowned(m)  failed at /usr/src/sys/kern/kern_mutex.c:966
cpuid = 0; lapic.id = 
Debugger(panic)
Stopped at  Debugger+0x4f:  xchgl   %ebx,in_Debugger.0

I would be grateful for any suggestions.

- Till

PS Linux 2.4.18-14smp seems to work.


OUTPUT OF DMESG
===
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #3: Mon Mar  3 20:51:39 JST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel /boot/kernel.gen/kernel at 0xc069f000.
Preloaded elf module /boot/kernel.gen/acpi.ko at 0xc069f0ac.
Timecounter i8254  frequency 1193182 Hz
Timecounter TSC  frequency 2392042856 Hz
CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2392.04-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf27  Stepping = 7
  
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Hyperthreading: 2 logical CPUs
real memory  = 2146893824 (2047 MB)
avail memory = 2082635776 (1986 MB)
Allocating major#253 to net
Allocating major#252 to pci
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: PTLTDRSDT   on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
pcibios: BIOS version 2.10
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI-fast  frequency 3579545 Hz
can't fetch resources for \\_SB_.PCI0.LPC0.SIO_.LPT_ - AE_AML_INVALID_RESOURCE_TYPE
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
acpi_cpu0: CPU on acpi0
acpi_cpu1: CPU on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: Intel Generic host to PCI bridge mem 0xf400-0xf7ff at device 0.0 on 
pci0
pci0: unknown at device 0.1 (no driver attached)
pcib1: ACPI PCI-PCI bridge mem 0xf800-0xfbff at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge at device 2.0 on pci0
pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ - AE_NOT_FOUND
pci2: ACPI PCI bus on pcib2
pci2: base peripheral, interrupt controller at device 28.0 (no driver attached)
pcib3: ACPI PCI-PCI bridge at device 29.0 on pci2
pci3: ACPI PCI bus on pcib3
pci2: base peripheral, interrupt controller at device 30.0 (no driver attached)
pcib4: ACPI PCI-PCI bridge at device 31.0 on pci2
pci4: ACPI PCI bus on pcib4
bge0: Broadcom BCM5702X Gigabit Ethernet, ASIC rev. 0x1002 mem 0xf020-0xf020 
irq 5 at device 4.0 on pci4
bge0: Ethernet address: 00:50:45:00:96:f7
miibus0: MII bus on bge0
brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, 
auto
uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0x1400-0x141f irq 11 at device 
29.0 on pci0
usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0x1420-0x143f irq 10 at device 
29.1 on pci0
usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0x1440-0x145f irq 5 at device 
29.2 on pci0
usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pci0: serial bus, USB at device 29.7 (no driver attached)
pcib5: ACPI PCI-PCI bridge at device 30.0 on pci0
pci5: ACPI PCI bus on pcib5
pci5: serial bus, FireWire at device 0.0 (no driver attached)
pci5: display, VGA at device 1.0 (no driver attached)
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel ICH4 UDMA100 controller port 0x1460-0x146f,0-0x3,0-0x7,0-0x3,0-0x7 at 
device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: serial bus, SMBus at device 31.3 (no driver attached)
acpi_button0: Power Button on acpi0
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 
irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 

Problems compiling KDE after mega-commit

[Rossam Souza Silva]

I upgraded my machine while compiling KDE, some sys header files
are problematic now:

In file included from ksimcpu.cpp:45:
/usr/include/sys/dkstat.h:45:2: warning: #warning sys/dkstat.h is
deprecated and should not be #include'd
ksimcpu.cpp:244:2: warning: #warning is a GCC extension
ksimcpu.cpp:244:2: warning: #warning add support for SMP on FreeBSD
ksimcpu.cpp: In member function `void
CpuView::updateCpu(CpuView::CpuData,
   int)':
ksimcpu.cpp:248: `CPUSTATES' undeclared (first use this function)
ksimcpu.cpp:248: (Each undeclared identifier is reported only once for
each
   function it appears in.)
ksimcpu.cpp:249: `cpuTime' undeclared (first use this function)
ksimcpu.cpp:250: warning: deprecated conversion from string constant to
`char*'
ksimcpu.cpp:266: `CP_USER' undeclared (first use this function)
ksimcpu.cpp:267: `CP_NICE' undeclared (first use this function)
ksimcpu.cpp:268: `CP_SYS' undeclared (first use this function)
ksimcpu.cpp:269: `CP_IDLE' undeclared (first use this function)
ksimcpu.cpp:209: warning: unused parameter `int cpuNumber'
gmake[4]: *** [ksimcpu.lo] Error 1
gmake[4]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors/cpu'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.1'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/misc/kdeutils3.
*** Error code 1

Stop in /usr/ports/x11/kde3.


CPUSTATES  cia. are defined in sys/resource.h, including this header in
ksimcpu.cpp, I have this:


In file included from ksimcpu.cpp:45:
/usr/include/sys/dkstat.h:45:2: warning: #warning sys/dkstat.h is
deprecated and should not be #include'd
In file included from ksimcpu.cpp:46:
/usr/include/sys/resource.h:61: field `ru_utime' has incomplete type
/usr/include/sys/resource.h:62: field `ru_stime' has incomplete type
/usr/include/sys/resource.h:122: 'int32_t' is used as a type, but is not
   defined as a type.
/usr/include/sys/resource.h:123: 'int32_t' is used as a type, but is not
   defined as a type.
/usr/include/sys/resource.h:127: 'rlim_t' is used as a type, but is not
defined
   as a type.
/usr/include/sys/resource.h:128: 'rlim_t' is used as a type, but is not
defined
   as a type.
/usr/include/sys/resource.h:133: syntax error before `[' token
ksimcpu.cpp:245:2: warning: #warning is a GCC extension
ksimcpu.cpp:245:2: warning: #warning add support for SMP on FreeBSD
ksimcpu.cpp: In member function `void
CpuView::updateCpu(CpuView::CpuData,
   int)':
ksimcpu.cpp:251: warning: deprecated conversion from string constant to
`char*'
ksimcpu.cpp:210: warning: unused parameter `int cpuNumber'
gmake[4]: *** [ksimcpu.lo] Error 1
gmake[4]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors/cpu'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.1'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/misc/kdeutils3.
*** Error code 1

Stop in /usr/ports/x11/kde3.

--
(_ )   Contrary to popular belief, UNIX is user friendly. It just happens
 \\\'',) ^  to be very selective about who it decides to make friends with.
   \/  \(
   .\._/_)  Rossam Souza Silva ([EMAIL PROTECTED])
-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Problems compiling KDE after mega-commit

[leafy]

On Tue, Mar 04, 2003 at 02:19:39AM -0300, Rossam Souza Silva wrote:

Please cvsup with the latest ports, it's already fixed.

Jiawei 
-- 
Without the userland, the kernel is useless.
 --inspired by The Tao of Programming

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Problems compiling KDE after mega-commit

[Andre Guibert de Bruet]

Hi,

You need to upgrade your ports skeleton. There's a couple of fixes that
were committed within the last 24 hours which fix these issues.

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/

On Tue, 4 Mar 2003, Rossam Souza Silva wrote:


 I upgraded my machine while compiling KDE, some sys header files
 are problematic now:

 In file included from ksimcpu.cpp:45:
 /usr/include/sys/dkstat.h:45:2: warning: #warning sys/dkstat.h is
 deprecated and should not be #include'd
 ksimcpu.cpp:244:2: warning: #warning is a GCC extension
 ksimcpu.cpp:244:2: warning: #warning add support for SMP on FreeBSD
 ksimcpu.cpp: In member function `void
 CpuView::updateCpu(CpuView::CpuData,
int)':
 ksimcpu.cpp:248: `CPUSTATES' undeclared (first use this function)
 ksimcpu.cpp:248: (Each undeclared identifier is reported only once for
 each
function it appears in.)
 ksimcpu.cpp:249: `cpuTime' undeclared (first use this function)
 ksimcpu.cpp:250: warning: deprecated conversion from string constant to
 `char*'
 ksimcpu.cpp:266: `CP_USER' undeclared (first use this function)
 ksimcpu.cpp:267: `CP_NICE' undeclared (first use this function)
 ksimcpu.cpp:268: `CP_SYS' undeclared (first use this function)
 ksimcpu.cpp:269: `CP_IDLE' undeclared (first use this function)
 ksimcpu.cpp:209: warning: unused parameter `int cpuNumber'
 gmake[4]: *** [ksimcpu.lo] Error 1
 gmake[4]: Leaving directory
 `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors/cpu'
 gmake[3]: *** [all-recursive] Error 1
 gmake[3]: Leaving directory
 `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors'
 gmake[2]: *** [all-recursive] Error 1
 gmake[2]: Leaving directory
 `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim'
 gmake[1]: *** [all-recursive] Error 1
 gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.1'
 gmake: *** [all] Error 2
 *** Error code 2

 Stop in /usr/ports/misc/kdeutils3.
 *** Error code 1

 Stop in /usr/ports/x11/kde3.


 CPUSTATES  cia. are defined in sys/resource.h, including this header in
 ksimcpu.cpp, I have this:


 In file included from ksimcpu.cpp:45:
 /usr/include/sys/dkstat.h:45:2: warning: #warning sys/dkstat.h is
 deprecated and should not be #include'd
 In file included from ksimcpu.cpp:46:
 /usr/include/sys/resource.h:61: field `ru_utime' has incomplete type
 /usr/include/sys/resource.h:62: field `ru_stime' has incomplete type
 /usr/include/sys/resource.h:122: 'int32_t' is used as a type, but is not
defined as a type.
 /usr/include/sys/resource.h:123: 'int32_t' is used as a type, but is not
defined as a type.
 /usr/include/sys/resource.h:127: 'rlim_t' is used as a type, but is not
 defined
as a type.
 /usr/include/sys/resource.h:128: 'rlim_t' is used as a type, but is not
 defined
as a type.
 /usr/include/sys/resource.h:133: syntax error before `[' token
 ksimcpu.cpp:245:2: warning: #warning is a GCC extension
 ksimcpu.cpp:245:2: warning: #warning add support for SMP on FreeBSD
 ksimcpu.cpp: In member function `void
 CpuView::updateCpu(CpuView::CpuData,
int)':
 ksimcpu.cpp:251: warning: deprecated conversion from string constant to
 `char*'
 ksimcpu.cpp:210: warning: unused parameter `int cpuNumber'
 gmake[4]: *** [ksimcpu.lo] Error 1
 gmake[4]: Leaving directory
 `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors/cpu'
 gmake[3]: *** [all-recursive] Error 1
 gmake[3]: Leaving directory
 `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors'
 gmake[2]: *** [all-recursive] Error 1
 gmake[2]: Leaving directory
 `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim'
 gmake[1]: *** [all-recursive] Error 1
 gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.1'
 gmake: *** [all] Error 2
 *** Error code 2

 Stop in /usr/ports/misc/kdeutils3.
 *** Error code 1

 Stop in /usr/ports/x11/kde3.

 --
 (_ )   Contrary to popular belief, UNIX is user friendly. It just happens
  \\\'',) ^  to be very selective about who it decides to make friends with.
\/  \(
.\._/_)  Rossam Souza Silva ([EMAIL PROTECTED])
 -


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Problems compiling KDE after mega-commit

[Kris Kennaway]

On Tue, Mar 04, 2003 at 01:57:46AM -0500, Andre Guibert de Bruet wrote:
 Hi,
 
 You need to upgrade your ports skeleton. There's a couple of fixes that
 were committed within the last 24 hours which fix these issues.

Hmm..I've seen this on another port already (icewm, I think).  It
looks like phk might have some additional patching to do when I get
him the full list.

Kris


pgp0.pgp
Description: PGP signature

Re: ATA MODE_SENSE_BIG timeout

[Soeren Schmidt]

It seems David Xu wrote:

(snip snap)
 acd1: read data overrun 34/0
 acd1: MODE_SENSE_BIG command timeout - resetting
 ata1: resetting devices ..
 done
 acd1: CD-RW SONY CD-RW CRX140E at ata1-slave PIO4

Hmm, can you use the acd1 device normally or does it fail (how) ?

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Possible patch for limiting APs at startup

[Hiten Pandya]

John Baldwin (Mon, Mar 03, 2003 at 02:49:21PM -0500) wrote:
 
 On 02-Mar-2003 Juli Mallett wrote:
  * De: Hiten Pandya [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Possible patch for limiting APs at startup ]
  Hello.
  
  Just as the topic says, do you think this patch is good enough, or gets
  even close to it?  I have tested the patch, and it seems to do it's job
  in the right way.  Some might call it hackery, but it's better than
  nothing I would suppose.
  
  I think your use of cpus to refer to APs only is silly, and also that
  overriding mp_naps instead of using a real cpus value and using it as
  a bounds check akin to MAXCPU, is a bit of the wrong direction.  As you
  know, the following is my patch, and it does not work, but I think,
  personally, the behaviour is saner, in theory at least :)
 
 You should set mp_maxcpus prior to the mp_naps test so it isn't left
 invalid in the common case.  Also, this patch doesn't limit HT cpu's
 at all.  I could have a 4 cpu system with HTT and maxcpus=2, and I
 will end up with 4 CPU's due to 2 logical CPU's per processor.  Perhaps
 this is intentional?

Yes. It was intentional, in the sense that we only want to limit the
number of Application Processors, and not the HTT cores inside it,
because that does not make much sense, IMHO.

Do you think that patch will be committed, or does it need improving?
(http://www.unixdaemons.com/~hiten/work/diffs/mp_machdep.c.patch)

Cheers.

-- 
Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED])
http://www.unixdaemons.com/~hiten/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Changes to libfetch in 5.0 break proxy support?

[Brian J. McGovern]

I'm having a problem with fetch and libfetch in 5.0, and (given that I 
currently have a bad cold), I'm hoping to get a cheap answer before I have
to start crawling through code.

In the 4.x days, I was able to set up an apache web proxy, and then export
FTP_PASSIVE_MODE=YES and HTTP_PROXY=thehostoftheproxy:80, and then go to
/usr/ports, and say, for instance make all.

Everything would then download correctly, and go on happily.

Now, however, it appears that when I do this, the connection either times out,
or I get a file with the right name, but the contents are an HTML document
(wrapped to fit in 80 cols).

HTMLHEADMETA HTTP-EQUIV=REFRESH CONTENT=0 
URL=ftp://space.mit.edu/pub/davis/jed/v0.99/jed-B0.99-15.tar.gz;
/HEADBODY/BODY/HTML

I know the proxy is working, as my 4.x boxes still go through it happily.

Anyone have any ideas if something has broken, or whether its pilot error?

-Brian

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message