Re: Official request: Please make GNU grep the default

2010-08-18 Thread Wilko Bulte


Op 18 aug. 2010 om 18:48 heeft Gabor Kovesdan ga...@freebsd.org het volgende 
geschreven:

 Em 2010.08.13. 10:43, Doug Barton escreveu:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 Gabor,
 
 I hope at this point it goes without saying that I have a lot of respect
 for the work you've done on BSD grep, and I've already told you that I
 think you're very courageous for taking the project on. I've been
 testing and evaluating it for some time now, and I think I've given it a
 fair trial. You've done a fairly good job of responding to bug reports,
 and I understand that the exposure BSD grep has received as the default
 in HEAD has been very valuable in exposing additional areas that need
 work. However, with all that in mind I am officially asking you to
 please change the default in HEAD to GNU grep. (Note, I am _not_ asking
 you to remove BSD grep from the tree, just to change the default.)
 
 My reason is simple, performance. [...]
 
 I've just committed a patch with the kind help of Dimitry Andric, which gives 
 BSD grep a huge performance boost. The performance is now almost comparable 
 to GNU grep. I think with this, BSD grep may remain default if no other 
 serious issues come up. Please report if you notice something weird.
 
 I know about some minor issues, which aren't fixed yet. I'll be out for 4 
 days as of tomorrow but when I come back I'll take care of these:
 - Infinite loop when reading directory on ZFS/NFS filesystem
 - Problems with context grepping
 
 When reply, please remove core@ from CC, let's not bother them with this, I 
 just wanted to let them know that I'm not neglecting this issue but if still 
 demanded for a good reason,

No worries there Gabor!

Wilko

 I'll switch back to default GNU grep.
 
 Gabor
 
 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: How to disable devices in -current / 5.2-BETA?

2003-12-02 Thread Wilko Bulte
On Tue, Dec 02, 2003 at 11:11:48AM -0700, M. Warner Losh wrote:
 In message: [EMAIL PROTECTED]
 Scott Long [EMAIL PROTECTED] writes:
 : However, having a general mechanism for disabling newbus devices would be
 : really nice.
 
 Agreed.  But today and 5.2 you lose.  However, it isn't easy.  What
 does disabled mean?  Don't attach?  Don't even probe?  If you don't

You could disable the driver altogether. Assuming that is what
is desired.

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Alpha too.. (was: Re: buildworld failure on sparc64?

2003-11-13 Thread Wilko Bulte
On Wed, Nov 12, 2003 at 11:37:18PM +0100, Wilko Bulte wrote:

And on Alpha as well:

=== lib/libpam/modules/pam_radius^M
cc -O -pipe -mcpu=ev6 -mieee
-I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/inc
lude -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers
-Werror -Wall -Wno-format
-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wreturn-type -Wcast-qual -Wwrite-st
rings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized  -c
/usr/src/lib/libpam/modules/pam_radius/pa
m_radius.c^M
/usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function
`build_access_request':^M
/usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast
increases required alignment o
f target type^M
*** Error code 1^M
^M
Stop in /usr/src/lib/libpam/modules/pam_radius.^M
*** Error code 1^M
^M
Stop in /usr/src/lib/libpam/modules.^M
*** Error code 1^M
^M
Stop in /usr/src/lib/libpam.^M
*** Error code 1^M



 === lib/libpam/modules/pam_radius
 cc -O -pipe
 -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include
 -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers
 -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes
 -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
 -Wcast-align -Wno-uninitialized  -c
 /usr/src/lib/libpam/modules/pam_radius/pam_radius.c
 /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function
 `build_access_request':
 /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast
 increases required alignment of target type
 *** Error code 1
 
 Stop in /usr/src/lib/libpam/modules/pam_radius.
 *** Error code 1
 
 Stop in /usr/src/lib/libpam/modules.
 *** Error code 1
 
 
 ?
 
 -- 
 |   / o / /_  _   
 |/|/ / / /(  (_)  Bulte   [EMAIL PROTECTED]
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
---end of quoted text---

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


buildworld failure on sparc64?

2003-11-12 Thread Wilko Bulte
=== lib/libpam/modules/pam_radius
cc -O -pipe
-I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include
-I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers
-Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
-Wcast-align -Wno-uninitialized  -c
/usr/src/lib/libpam/modules/pam_radius/pam_radius.c
/usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function
`build_access_request':
/usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast
increases required alignment of target type
*** Error code 1

Stop in /usr/src/lib/libpam/modules/pam_radius.
*** Error code 1

Stop in /usr/src/lib/libpam/modules.
*** Error code 1


?

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-11-08 Thread Wilko Bulte
On Thu, Nov 06, 2003 at 09:52:27PM -0800, Matthew Dillon wrote:
 :I just tried Jung-uk Kim's driver on -stable and sofar it works OK:
 :
 
 ... and I just ported it to DragonFly and it works fine there too
 with an ASUS K8V Motherboard.  Kudos!

Good to hear that ;)

Jung-uk has provided me with some more patches to fix some issues
with promiscuous mode. I have not had time to look at those yet.

[EMAIL PROTECTED] committed some extra PCI-IDs to sk(4) yesterday,
you might want to fold those into DragonFly as well.

cheers,
Wilko

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


buildworld fails on Alpha?

2003-10-24 Thread Wilko Bulte
ll -Wno-format-y2k -Wno-uninitialized  -c /usr/src/lib/libfetch/fetch.c
cc -O -pipe -mcpu=ev6 -mieee -I. -DINET6 -DWITH_SSL -Wsystem-headers -Werror
-Wa
ll -Wno-format-y2k -Wno-uninitialized  -c /usr/src/lib/libfetch/common.c
/usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (not
in a 
function)
/usr/src/lib/libfetch/common.c:58: error: initializer element is not
constant
/usr/src/lib/libfetch/common.c:58: error: (near initialization for
`_netdb_errli
st[0].num')
/usr/src/lib/libfetch/common.c:58: error: initializer element is not
constant
/usr/src/lib/libfetch/common.c:58: error: (near initialization for
`_netdb_errli
st[0]')
/usr/src/lib/libfetch/common.c:60: error: initializer element is not
constant
/usr/src/lib/libfetch/common.c:60: error: (near initialization for
`_netdb_errli
st[1]')
/usr/src/lib/libfetch/common.c:61: error: initializer element is not
constant
/usr/src/lib/libfetch/common.c:61: error: (near initialization for
`_netdb_errli
st[2]')
/usr/src/lib/libfetch/common.c:62: error: initializer element is not
constant
/usr/src/lib/libfetch/common.c:62: error: (near initialization for
`_netdb_errli
st[3]')
/usr/src/lib/libfetch/common.c:63: error: initializer element is not
constant
/usr/src/lib/libfetch/common.c:63: error: (near initialization for
`_netdb_errli
st[4]')
*** Error code 1

Stop in /usr/src/lib/libfetch.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Seen before? Or just me?

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildworld fails on Alpha?

2003-10-24 Thread Wilko Bulte
On Sat, Oct 25, 2003 at 06:06:24AM +0900, Hajimu UMEMOTO wrote:
 Hi,
 
  On Fri, 24 Oct 2003 23:03:31 +0200
  Wilko Bulte [EMAIL PROTECTED] said:
 
 wkb ll -Wno-format-y2k -Wno-uninitialized  -c /usr/src/lib/libfetch/common.c
 wkb /usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (not
 
 It was fixed already.  Please re-cvsup.
 Sorry for the mess.

No problem, I'll re-cvsup

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: GEOM Gate.

2003-10-15 Thread Wilko Bulte
On Wed, Oct 15, 2003 at 12:28:12AM -0700, Terry Lambert wrote:
 Wilko Bulte wrote:
  On Tue, Oct 14, 2003 at 10:44:14PM +0200, Oldach, Helge wrote:
   From: Richard Tobin [mailto:[EMAIL PROTECTED]
 Ok, GEOM Gate is ready for testing.
 For those who don't know what it is, they can read README:
   
Aaargh!  It's the return of nd(4) from SunOS.
  
   Excuse me?
  
   # uname -a
   SunOS galaxy 4.1.4 18 sun4m
  
  Too new..
 
 Yeah... Think Sun2 systems
 
 http://www.netbsd.org/Documentation/network/netboot/nd.html

/me fondly remembers the hacked-up backplane in the Sun2/170
to allow it to use 7 1MB RAM cards..

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: hiding e-mail adresses needed badly

2003-10-15 Thread Wilko Bulte
On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote:


I fail to see why this is relevant to -current but OK.. I think that
the opportunity to do this has long since passed. Just type your name
in Google and see what happens..

Wilko

 Due to increased activity of SPAM harvesters what are our plans to hide 
 our addresses from public WWW? I mean all browseable mailing lists, 
 FreeBSD site, CVS via WWW, PRs, ports and docs.
 
 As I think, simple user [at] domain.com form will be enough to stop 
 them.
 
 -- 
 Andrey Chernov | http://ache.pp.ru/
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: GEOM Gate.

2003-10-14 Thread Wilko Bulte
On Tue, Oct 14, 2003 at 10:44:14PM +0200, Oldach, Helge wrote:
 From: Richard Tobin [mailto:[EMAIL PROTECTED]
   Ok, GEOM Gate is ready for testing.
   For those who don't know what it is, they can read README:
  
  Aaargh!  It's the return of nd(4) from SunOS.
 
 Excuse me?
 
 # uname -a
 SunOS galaxy 4.1.4 18 sun4m

Too new..

 # man nd
 No manual entry for nd.
 #

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2-RELEASE TODO

2003-09-29 Thread Wilko Bulte
On Mon, Sep 29, 2003 at 02:05:16PM -0400, Daniel Eischen wrote:
 On Mon, 29 Sep 2003, Robert Watson wrote:
 
   |-+---+-+|
   | |   | | Userland bits  |
   | |   | | implemented,   |
   | KSE support for | In| Marcel  | kernel bits not|
   | alpha   | progress. | Moolenaar   | implemented.   |
   | |   | | Required for   |
   | |   | | 5.2-RELEASE.   |
 
 You should probably remove Marcel from this item.  This task needs
 another volunteer.

Recently Marcel noted to me he was planning to engage on this one. I have
offered him help for testing.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2-RELEASE TODO

2003-09-29 Thread Wilko Bulte
On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote:
 On Mon, Sep 29, 2003 at 08:07:32PM +0200, Wilko Bulte wrote:
   
   You should probably remove Marcel from this item.  This task needs
   another volunteer.
  
  Recently Marcel noted to me he was planning to engage on this one. I have
  offered him help for testing.
 
 The deal is this (if you find your way between the parenthesis):
 
...

 At the DevSummit we failed to reach agreement that alpha should be
 dropped to a tier 2 platform, but we did acknowledge that alpha needs
 developers pronto. There it was also agreed that I would enter a
 holding pattern (which roughly boils down to me circling between home,
 work and Starbucks) until either someone fixes KSE or my weakness
 shows and I do it anyway (the fact that I looked at it this weekend
 means that I was pretty close to folding -- I made it to Starbucks
 just in time).

You get red hair from too much coffee anyway :-) :-)

 I also mentioned recently (in the last couple of days) that we should
 worry more about sparc64 than alpha. Simply because I think alpha is
 on it's way down and should already be a tier 2 platform and sparc64
 is still on its way up ... sort of.

In my book sparc64 is also with one foot in the grave. As is Sun
itself. 

If we want to be future proof ia64 and amd64 are the only viable 
architectures. The rest are just interesting passtimes..

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Gcc 3.2.2 vs gcc 3.2.3

2003-09-22 Thread Wilko Bulte
On Mon, Sep 22, 2003 at 02:25:27PM +, Holger Kipp wrote:
 
 
 Justin Smith ([EMAIL PROTECTED]) wrote: 
 I'm running a P4 2.4 Ghz processor with 512meg of ram.
 
 I've had the problem of getting signal 11 and signal 4 when I make
 buildworld and buildkernel.
 
 I tested my system with memtest86 (for several hours) and it says
 everything is OK.
 
 We had similar problems once. It turned out to be a 'lucky' combination of good
 mainboard and good memory that were slightly incompatible.
 
 memtest86 might not detect this, but make buildworld will. If you don't get the
 errors at the same location every time, it might be the same issue. We found
 out after contacting both the mainboard and the memory chip vendors.

Same experience here, also on P4, with DDR400 memory. Asus mainboard,
with memory from the Asus qualified memory list. Did not work worth sh*,
at least not with memory at DDR400 speeds. Other memory fixed is perfectly.

Go figure..

-- 
Wilko   [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-09-14 Thread Wilko Bulte
On Sat, Sep 13, 2003 at 03:37:51PM +0100, Stuart Walsh wrote:
 On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote:
  I have my own *working* driver, which is for 4-STABLE.  It works with 
  SK-9521 V2.0 (for me, at least) and it should work with 3C940.
  
  Note: This driver is ported from Nathan L. Binkert's OpenBSD driver.
  Note: This is completely independent from Stuart Walsh's work. ;-)
  Note: You must recompile MII driver and dependent network drivers.
  
 
 It's worth noting my patch was a port of Natan's patch also(which is actually
 Bill's driver technically speaking ;), so I'd be interested to see where i
 went wrong.  But if it works then great, I'll get on with something else :)
 It's somewhat difficult to fine tune a driver when you dont actually own 
 the hardware in question.

I just tried Jung-uk Kim's driver on -stable and sofar it works OK:

pcib2: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0
pci2: PCI bus on pcib2
skc0: 3Com 3C940 Gigabit Ethernet port 0xd400-0xd4ff mem
0xfeaf8000-0xfeafbfff irq 11 at device 5.0 on pci2
skc0: 3Com Gigabit LOM (3C940)
sk0: Marvell Semiconductor, Inc. Yukon on skc0
sk0: Ethernet address: 00:0c:6e:4f:77:0c
miibus0: MII bus on sk0
e1000phy0: Marvell Semiconductor 88E1000* gigabit PHY on miibus0
e1000phy0:  1000baseTX-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX,
10baseTX, auto
isp0: Qlogic ISP 1020/1040 PCI SCSI Adapter port 0xd800-0xd8ff mem
0xfeaff000-0xfeaf irq 10 at device 9.0 on pci2

This is with the LOM found on Asus P4P800 btw.

Curious minds obviously wonder about the difference with Stuart's driver ;)

ENOTIME to check right now. Sleep first.

Wilko
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-09-05 Thread Wilko Bulte
On Fri, Sep 05, 2003 at 07:50:24PM +0100, Stuart Walsh wrote:
 On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote:
 
 Hi again chaps,
 
 I've been working on other things lately, including getting ready to
 move house and looking after my 3 month old daughter :) but recently I've 

Changing nappies? ;)

 took up trying to get this driver working again.  If anyone is interested in
 helping out, could they give http://stu.bash.sh/if_sk.c and
 http://stu.bash.sh/if_skreg.h a try and let me know what output you get.
 I'm only really interested in what happens after the MAC gets printed so
 don't go to too much trouble to get the exact info.
 
 Just plonk the files in /usr/src/sys/pci over the top of the old ones.
 Thanks to anyone who helps out.

OK.. what it does is as follows:

- print ethernet address
- then it prints:

Yukon chip detected
Phy type 4 adr 0
initialising yukon device
phy reset set
mac reset set
mac reset clear
mac reset set
hang

This all on an Asus P4P800. Obviously a copper based NIC, without cable
connected in this case.

hth
Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cvs commit: src/gnu/usr.bin Makefile src/lib Makefile src/sbinMakefile src/usr.bin Makefile src/usr.sbin Makefile

2003-08-30 Thread Wilko Bulte
On Sat, Aug 30, 2003 at 02:55:32PM +0200, Andreas Klemm wrote:
 On Sat, Aug 30, 2003 at 03:46:53AM -0700, Doug Barton wrote:
  On Sat, 30 Aug 2003, Poul-Henning Kamp wrote:
  
   In message [EMAIL PROTECTED], Doug Barton writes:
   Poul-Henning,
   
   Please don't forget to update src/share/examples/etc/make.conf
   accordingly.
  
   Hmm, so this stuff is documented both in make.conf(5) and an examples
   file ?  Sounds like one place too many to me.
  
  Well, there's always been an example make.conf file. In previous
  incarnations it's lived in /etc, then /etc/defaults. I also agree with
  the previous poster that it's useful to have such an example, and
  mergemaster uses it for the -p option.
 
 In former times the make.conf file has been installed in /etc
 when doing a fresh FreeBSD installation. It contained useful
 commented out options.
 
 If memory serves me right, the file isn't installed anymore
 by default. Is there a reason ? I regarded this as useful
 tro have it around under /etc, so to say ready for use.

See /etc/defaults/make.conf

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-08-24 Thread Wilko Bulte
On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote:
 Hi,
 
 I ported the openbsd additions to the sk driver to support the 3c940
 gigabit network card which is commonly found in the above asus
 motherboard.  Testers/comments/commits welcome, but please don't blame
 me if it burns your house down or something :)

Hi Stuart,

I tried this patch instead of the earlier ones you pointed me to on IRC.

Unfortunately my Asus P4P800 still locks up solid (reset button required)
after printing the 3c940's ethernet address.

I'm interested to know if other P4P800 owners have the same issue.

Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-08-24 Thread Wilko Bulte
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote:
 On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote:
  On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote:
   Hi,
   
   I ported the openbsd additions to the sk driver to support the 3c940
   gigabit network card which is commonly found in the above asus
   motherboard.  Testers/comments/commits welcome, but please don't blame
   me if it burns your house down or something :)
  
  Hi Stuart,
  
  I tried this patch instead of the earlier ones you pointed me to on IRC.
  
  Unfortunately my Asus P4P800 still locks up solid (reset button required)
  after printing the 3c940's ethernet address.
  
  I'm interested to know if other P4P800 owners have the same issue.
  
  Wilko
  
 Hi Wilko,
 
 Sorry to hear you are still having trouble.  Thus far I have only been
 able to find one other person to test the driver and for him it works
 perfectly(also a P4P800).

Right, that is a valuable datapoint.

 Are you running up do date -current, or is there anything strange about
 your setup at all?

Not that I know, but given that it works for another P4P800 I can find out
what is special locally.

W/

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-08-24 Thread Wilko Bulte
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote:
 On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote:
  On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote:

...

  Unfortunately my Asus P4P800 still locks up solid (reset button required)
  after printing the 3c940's ethernet address.
  
  I'm interested to know if other P4P800 owners have the same issue.
  
  Wilko
  
 Hi Wilko,
 
 Sorry to hear you are still having trouble.  Thus far I have only been
 able to find one other person to test the driver and for him it works
 perfectly(also a P4P800).
 
 Are you running up do date -current, or is there anything strange about
 your setup at all?

I just did a buildworld on a freshly checked out tree, applied the patches
and tried again.

Unfortunately that did not help. I continue my investigation.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-08-24 Thread Wilko Bulte
On Sun, Aug 24, 2003 at 12:17:52PM +, Jens Rehsack wrote:
 Stuart Walsh wrote:
 On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote:
 
 On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote:
 
 Hi,
 
 I ported the openbsd additions to the sk driver to support the 3c940
 gigabit network card which is commonly found in the above asus
 motherboard.  Testers/comments/commits welcome, but please don't blame
 me if it burns your house down or something :)
 
 Hi Stuart,
 
 I tried this patch instead of the earlier ones you pointed me to on IRC.
 
 Unfortunately my Asus P4P800 still locks up solid (reset button required)
 after printing the 3c940's ethernet address.
 
 I'm interested to know if other P4P800 owners have the same issue.
 
 Wilko
 
 
 Hi Wilko,
 
 Sorry to hear you are still having trouble.  Thus far I have only been
 able to find one other person to test the driver and for him it works
 perfectly(also a P4P800).
 
 Hi Guys,
 
 I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix
 the swap-issue, so that I can reboot easily, I would test your patches,
 too.

Que? What swap issue? I can dual boot stable and current just fine on
the P4P800. 

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3C940 / Asus P4P800 gigabit LAN driver

2003-08-24 Thread Wilko Bulte
On Sun, Aug 24, 2003 at 03:13:18PM +0200, Wilko Bulte wrote:
 On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote:
  On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote:
   On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote:
 
 ...
 
   Unfortunately my Asus P4P800 still locks up solid (reset button required)
   after printing the 3c940's ethernet address.
   
   I'm interested to know if other P4P800 owners have the same issue.
   
   Wilko
   
  Hi Wilko,
  
  Sorry to hear you are still having trouble.  Thus far I have only been
  able to find one other person to test the driver and for him it works
  perfectly(also a P4P800).
  
  Are you running up do date -current, or is there anything strange about
  your setup at all?
 
 I just did a buildworld on a freshly checked out tree, applied the patches
 and tried again.
 
 Unfortunately that did not help. I continue my investigation.

Going to the latest BIOS also did not make any difference (long shot, I
know).

Can someone with a P4P800 who has gotten it to work please post their
dmesg?

Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [current tinderbox] failure on alpha/alpha

2003-08-20 Thread Wilko Bulte
On Wed, Aug 20, 2003 at 01:59:42PM -0400, Andrew Gallatin wrote:
 
 Tinderbox writes:
 
   cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DIN_GCC -DHAVE_CONFIG_H 
 -DPREFIX=\/usr\ 
 -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../cc_tools
  
 -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../cc_tools
  
 -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc
  
 -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/config
  
 -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f
  -I. -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/contrib/gcc/f/stc.c
   cc1: error: invalid option `tune=ev5'
   cc1: error: invalid option `ieee'
   cc1: error: bad value (ev4) for -mcpu= switch
 
 I assume that this is a crossbuild problem?

FWIW on a true alpha buildworld ran fine last night.
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


mergemaster b0rked?

2003-08-18 Thread Wilko Bulte
for i in answer  isdntel.sh  record
  tell tell-record unknown_incoming ; do
install -o  -g  -m 700 $i  /var/tmp/temproot/etc/isdn ;  done ;  for i in
holidays.Disdnd.rates.Aisdnd.rates.D   isdnd.rates.F
 isdnd.rates.L   isdnd.rates.UK.BT   isdnd.rc.sample
   isdntel.alias.sample ; do  install -o  -g  -m 600 $i
/var/tmp/temproot/etc/isdn ;  done
install: -g: Invalid argument
*** Error code 67

Stop in /usr/src/etc/isdn.
*** Error code 1

Stop in /usr/src/etc.

  *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
  the temproot environment

#

??

This is on Alpha btw.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: mergemaster b0rked?

2003-08-18 Thread Wilko Bulte
On Mon, Aug 18, 2003 at 04:19:22PM -0400, Craig Rodrigues wrote:
 On Mon, Aug 18, 2003 at 07:05:54PM +0200, Wilko Bulte wrote:
  for i in answer  isdntel.sh  record
tell tell-record unknown_incoming ; do
  install -o  -g  -m 700 $i  /var/tmp/temproot/etc/isdn ;  done ;  for i in
   ^^  
 
 Why doesn't the -g flag have a GID as an argument? 

Because it seems that BINGRP and BINOWNER are undefined.

  install: -g: Invalid argument
  *** Error code 67
 
 -- 
 Craig Rodrigues
 http://crodrigues.org
 [EMAIL PROTECTED]
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SAN disk with freebsd?

2003-08-14 Thread Wilko Bulte
On Sun, Aug 10, 2003 at 06:53:09AM +0200, Poul-Henning Kamp wrote:
 In message [EMAIL PROTECTED], Aaron Wohl writes:
 Anyone using a storage area network with freebsd (or linux)?  Anything to
 recommend as working well or to stay way from?  
 
 I have a customer doing that.

Is this your customer running the DEC^WCompaq^WHP HSG80 raid array?

 Works ok.
 
 You need qlogic 2300 cards and the isp driver which Matt Jacob maintains.

Qlogic 2200 should also work (but is 1Gbit only)

Wilko
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: GEOM/vinum compatibility (was: vinum lock panic at startup-current)

2003-08-14 Thread Wilko Bulte
On Sat, Aug 09, 2003 at 06:38:51AM +0200, Poul-Henning Kamp wrote:
 In message [EMAIL PROTECTED], Greg 'groggy' Lehey 
 writes:
 
  and it seems that vinum does not respect the D_NOGIANT flag which
  GEOM recently started setting.
 
 Probably because it didn't know about it.  As I've said before, it
 would be nice to be informed about the changes you're making,
 particularly given your stated intention of doing no work on Vinum.
 
 I had the choice between supporting sos@ effort to de-Giantize ATA
 or wait for the non-maintainer of vinum to possibly react to his email

Come on.. a bit of politeness goes a long way..

 so I chose the former as being more beneficial to the project.

W/
-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: driver maintainers, please help

2003-08-14 Thread Wilko Bulte
On Thu, Aug 14, 2003 at 09:45:27AM -0700, David O'Brien wrote:
 On Wed, Aug 13, 2003 at 03:11:35PM +0200, Lukas Ertl wrote:
  this is a call for help from the various driver maintainers.  In a recent
  discussion on -doc it has come out that several manpages are not in sync
  with what's listed in the 5.1 Hardware Notes,
 
 We also have several drivers in 5.1 that don't even have man pages. :-(

Reference to documentation is the hallmark of the coward 

;)

But you are right of course...

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Best Known Methods for dual booting WinXP + -current

2003-08-14 Thread Wilko Bulte
On Thu, Aug 07, 2003 at 06:49:55PM -0700, David O'Brien wrote:
 On Thu, Aug 07, 2003 at 03:40:27PM -0500, Cagle, John (ISS-Houston) wrote:
  Had to use FFS filesystem since Grub doesn't support UFS.
  ^^^
  UFS1
 ^^^
 UFS2
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


crash when bringing up fddi interface

2003-08-01 Thread Wilko Bulte
I added a DEC DEFPA PCI FDDI card to my Alpha.

When ifconfig fpa0 foo I am greeted by the following
panic:

fatal kernel trap:

trap entry = 0x2 (memory management fault)
cpuid  = 2
faulting va= 0x53c443f891b8
type   = access violation
cause  = load instructon
pc = 0xfc4addc8
ra = 0xfc4ad3ac
sp = 0xfe0039dfd970
usp= 0x11fffa70
curthread  = 0xfc0006acba20
pid = 571, comm = ifconfig

Stopped at  rt_maskedcopy+0x18: ldq_u   t0,0(a2)
0x53c443f891b8   
t0=0x0,a2=0x53c443f891b8
db tb
No such command
db bt
No such command
db tsa^H ^H^H ^Hrace
rt_maskedcopy() at rt_maskedcopy+0x18
rtrequest1() at rtrequest1+0x39c
rtinit() at rtinit+0x250
in_ifinit() at in_ifinit+0x6d4
in_control() at in_control+0x918
ifioctl() at ifioctl+0x2b4
soo_ioctl() at soo_ioctl+0x290
ioctl() at ioctl+0x750
syscall() at syscall+0x3b8
XentSys() at XentSys+0x64
--- syscall (54, FreeBSD ELF64, ioctl) ---
--- user mode ---
db 

So, something appears to go wrong in:

static void
rt_maskedcopy(src, dst, netmask)
struct sockaddr *src, *dst, *netmask;
{
register u_char *cp1 = (u_char *)src;
register u_char *cp2 = (u_char *)dst;
register u_char *cp3 = (u_char *)netmask;
u_char *cplim = cp2 + *cp3;
u_char *cplim2 = cp2 + *cp1;
   
*cp2++ = *cp1++; *cp2++ = *cp1++; /* copies sa_len  sa_family */
cp3 += 2;
if (cplim  cplim2)
cplim = cplim2;
while (cp2  cplim)
*cp2++ = *cp1++  *cp3++;
if (cp2  cplim2)
bzero((caddr_t)cp2, (unsigned)(cplim2 - cp2));
}

My other DEFPA lives in a BP6 x86 box and is not panicing.

Suggestions?

W/

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Alpha/EISA broken?

2003-07-31 Thread Wilko Bulte
On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote:
 Wilko Bulte writes:
   Sounds like an SRM problem or EISA configuration problem.
   Normaly the bus and then system board should be probed at this point.
   We never used EISA on alpha before - EISA bridge support was only
   conditionalisized on pci.
  
  Which triggers me: did you run the ECU?
  
  A copy is at:
  
  ftp://ftp.tcja.nl/pub/wilko/alpha
 
 I have this now. It looks like something I dd(1) onto a floppy?

yessir

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Alpha/EISA broken?

2003-07-31 Thread Wilko Bulte
On Thu, Jul 31, 2003 at 02:03:12PM +0100, Mark Murray wrote:
 Wilko Bulte writes:
  On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote:
   Wilko Bulte writes:
 Sounds like an SRM problem or EISA configuration problem.
 Normaly the bus and then system board should be probed at this point.
 We never used EISA on alpha before - EISA bridge support was only
 conditionalisized on pci.

Which triggers me: did you run the ECU?

A copy is at:

ftp://ftp.tcja.nl/pub/wilko/alpha
   
   I have this now. It looks like something I dd(1) onto a floppy?
  
  yessir
 
 :-)
 
 And then do what with? Boot off it? run it from the bios?

 runecu 

from SRM. Better have a VGA card installed. Serial console is 
possible to but is a bit (hum..) of a challenge.

-- 
|   / o / /_  _ FreeBSD core team secretary
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Alpha/EISA broken?

2003-07-25 Thread Wilko Bulte
On Fri, Jul 25, 2003 at 01:07:46PM +0100, Mark Murray wrote:
 Hi
 
 Latest boot on my Alpha breaks thus:
 

 real memory  = 266371072 (254 MB)
 avail memory = 250863616 (239 MB)
 cia0: 2117x Core Logic chipset
 cia0: ALCOR/ALCOR2, pass 3
 cia0: extended capabilities: 21DWEN,BWEN
 pcib0: 2117x PCI host bus adapter on cia0
 pci0: PCI bus on pcib0
 eisab0: PCI-EISA bridge at device 7.0 on pci0
 
 halted CPU 0
 
 halt code = 7
 machine check while in PAL mode
 PC = 18100
 
 
 Any idea what gives?

Not really, but as a datapoint today's -current 
does work OK on a EISA-less machine. 

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Alpha/EISA broken?

2003-07-25 Thread Wilko Bulte
On Fri, Jul 25, 2003 at 05:31:27PM +0100, Mark Murray wrote:
 Wilko Bulte writes:
   halt code = 7
   machine check while in PAL mode
   PC = 18100
   
   
   Any idea what gives?
  
  Not really, but as a datapoint today's -current 
  does work OK on a EISA-less machine. 
 
 GENERIC kernel also has above error.
 
 Remove eisa, and the boot goes straight to panic (no clock).

That is because your clock sits behind eisa I think. ticso recently
posted some days ago that eisa is now mandatory on alpha.
I did not follow in detail to be honest. Check the archives.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Alpha/EISA broken?

2003-07-25 Thread Wilko Bulte
On Fri, Jul 25, 2003 at 07:02:09PM +0200, Bernd Walter wrote:

  eisab0: PCI-EISA bridge at device 7.0 on pci0
  
  halted CPU 0
  
  halt code = 7
  machine check while in PAL mode
  PC = 18100
  
  
  Any idea what gives?
 
 Sounds like an SRM problem or EISA configuration problem.
 Normaly the bus and then system board should be probed at this point.
 We never used EISA on alpha before - EISA bridge support was only
 conditionalisized on pci.

Which triggers me: did you run the ECU?

A copy is at:

ftp://ftp.tcja.nl/pub/wilko/alpha

 In case something is wrong with your eisa setup.
 Eisa configuration has to be done via alphabios.

Do 'runecu' from the SRM console and it should work.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 3Com 3C9340 (3C200) support

2003-07-25 Thread Wilko Bulte
On Thu, Jul 24, 2003 at 02:23:01AM -0400, Nathan Binkert wrote:
  I own an Abit IS7-G which includes an intergrated 3Com 3C940 card
  currently not supported in any FreeBSD branch to my knowledge. Some
  people said that the nic could world with the Tigon III driver but I
  haven't been able to get it to work with it during install. Are there
  any plans or projects to get this card supported in the near future? A
  Linux driver is provided by 3Com. Thanks in advance for your time.
 
 In the next few days, I will be committing support for this chip to the
 OpenBSD sk driver.  Our sk driver was based on the freebsd, so it will be 
 simple to backport.

Can you please be so kind to send a short headsup when you are done?
I'm planning on getting your work integrated once you have the OpenBSD
driver updated. (I'm lazy, I admit ;)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: We have ath, now what about Broadcom?

2003-07-23 Thread Wilko Bulte
On Wed, Jul 23, 2003 at 06:21:23PM -0400, Matthew Emmerton wrote:
   Folks,

...

   Can anyone provide some pointers or links that would bring me
   up-to-date on the current state of affairs on this subject,
   especially as it related to FreeBSD or *BSD in general?
 
  The folks at Broadcom have not been willing to release any information
  on their 800.11g chips for fear of violating FCC regs. The required
  NDA would prohibit the release of the source. You can program
  both the transmit power and frequency if you have this. (I make no
  claim as to whether their concerns have any validity.)
 
  For that reason there has been no open-source support for these chips.
 
 Why would Broadcom be scared?  Obviously it's the _driver_ that controls the
 power/freq output of the chip, so the responsibility of staying within FCC
 regs is that of the driver authors.  Of course, the no warranty aspects of
 open source drivers turns a blind eye to liability, but would things really
 come back to Broadcom?

Simple: ETOOMANYCORPORATELAWYERS is most likely the culprit.. 

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HTT on single CPU?

2003-07-17 Thread Wilko Bulte
On Thu, Jul 10, 2003 at 02:01:55AM -0700, Terry Lambert wrote:
 Wilko Bulte wrote:
  On Wed, Jul 09, 2003 at 10:14:47AM -0500, Thomas T. Veldhouse wrote:
  
  I can confirm my 2.4G P4 does have HTT:
 
 This is unfortunately not definitive for CPUs other than your
 own.  The Intel Extends... announcement that was quoted really
 means two things:

In my case it was a retail-boxed CPU, and it had the whole HTT
story on it ;-)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Call for testers: patch to convert dc(4) to busdma

2003-07-06 Thread Wilko Bulte
On Sat, Jul 05, 2003 at 04:07:26PM +0200, Maxime Henrion wrote:
 Wilko Bulte wrote:
  
  Could it be there is something fishy with mbuf handling?
 
 Could you please try the attached patch?  It's absolutely untested
 except for compilation because I have to leave right now, but I believe
 it should fix the mbuf leaks you've been reporting.

I ran netperf and bonnie via nfs in both directions. Everything ran fine,
no mbuf issues or whatever.

Anything specific you want tested in addition?

Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Call for testers: patch to convert dc(4) to busdma

2003-07-05 Thread Wilko Bulte

Could it be there is something fishy with mbuf handling?

I ran netperf from my DS10 Alpha box towards a 4-stable
netperf-receiver (called freebie)

As in:

ds10#ls
netperf tcp_range_scriptudp_rr_script
netserver   tcp_rr_script   udp_stream_script
snapshot_script tcp_stream_script
ds10#./tcp_range_script freebie


Testing with the following command line:
/usr/local/netperf/netperf -l 60 -H freebie -t TCP_STREAM -i 10,2 -I 99,3 --
-m 1 -s 32768 -S 32768

TCP STREAM TEST to freebie : +/-1.5% @ 99% conf. : histogram

After some time one gets:

Out of mbuf address space!
Consider increasing NMBCLUSTERS
All mbufs or mbuf clusters exhausted, please see tuning(7).
Out of mbuf address space!
Consider increasing NMBCLUSTERS
All mbufs or mbuf clusters exhausted, please see tuning(7).

Initially things were like:

ds10#netstat -m
mbuf usage:
GEN cache:  0/0 (in use/in pool)
CPU #0 cache:   2195/2240 (in use/in pool)
Total:  2195/2240 (in use/in pool)
Mbuf cache high watermark: 512
Maximum possible: 18176
Allocated mbuf types:
  2195 mbufs allocated to data
12% of mbuf map consumed
mbuf cluster usage:
GEN cache:  0/0 (in use/in pool)
CPU #0 cache:   2189/2192 (in use/in pool)
Total:  2189/2192 (in use/in pool)
Cluster cache high watermark: 128
Maximum possible: 9088
24% of cluster map consumed
4944 KBytes of wired memory reserved (99% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

and after the machine ran out of buffers it displayed:

ds10#netstat -m
mbuf usage:
GEN cache:  0/0 (in use/in pool)
CPU #0 cache:   9061/9088 (in use/in pool)
Total:  9061/9088 (in use/in pool)
Mbuf cache high watermark: 512
Maximum possible: 18176
Allocated mbuf types:
  9061 mbufs allocated to data
50% of mbuf map consumed
mbuf cluster usage:
GEN cache:  0/0 (in use/in pool)
CPU #0 cache:   9058/9072 (in use/in pool)
Total:  9058/9072 (in use/in pool)
Cluster cache high watermark: 128
Maximum possible: 9088
99% of cluster map consumed
20416 KBytes of wired memory reserved (99% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
ds10#

During the test run there was a steady increase in the % for the cluster
map.

Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Heads up: checking in change to ata-card.c

2003-06-26 Thread Wilko Bulte
On Fri, Jun 27, 2003 at 06:30:17AM +0800, David Xu wrote:

I'm sure Soeren will be be glad to investigate, I don't think
it is very worthwhile for you to piggyback your problem
on top of Bill's controversial email..

Make code, not war ;-)

Wilko


 I have another problem different with Bill Paul's.
 I have a Tyan Tiger 230T dual CPU MB. On second IDE,
 there are MITSUBISHI 52X CDROM as master and a SONY
 CD-RW CRX140E 8X/4X/32X as slave. FreeBSD never got
 them to work, while MS Windows and Linux and NetBSD and
 OpenBSD all work well with these devices. FreeBSD always
 stuck at MODE SENSE BIG, this sucks, I must disable
 second IDE in BIOS before booting into FreeBSD and
 reenable it before booting into another OS. I changed
 configuration several times, both DMA and PIO mode don't
 work, it works only when CR-RW is pulled.
 
 David Xu
 
 - Original Message - 
 From: Soeren Schmidt [EMAIL PROTECTED]
 To: Bill Paul [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Sent: Friday, June 27, 2003 3:03 AM
 Subject: Re: Heads up: checking in change to ata-card.c
 
 
  
  I do have problems with the wording you use in the comments
  in that patch mentioned below, I will even say that I will remove
  that as soon as it appears *and* shoot the committer so it doesn't
  happen again to use your choice of wording..
  
  Now, I dont think this way is productive at all, and would appreciate
  if we could have a civilized way of doing this instead...
  
  This is exactly the crap that makes one wonder if the time used on
  the project is well spent...
  
  -Søren
  

... [snip snip ]
---end of quoted text---

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Heads up: checking in change to ata-card.c

2003-06-26 Thread Wilko Bulte
On Thu, Jun 26, 2003 at 05:04:10PM -0700, David O'Brien wrote:
 On Thu, Jun 26, 2003 at 01:20:04PM -0600, M. Warner Losh wrote:
  In message: [EMAIL PROTECTED]
  [EMAIL PROTECTED] (Bill Paul) writes:
  : P.S.: Be sure to join us next time when I ream out whoever it was that
  :   broke support for my 3Com 3c575C cardbus ethernet NIC.
  
  It looks like my 3ccfe575ct is working well as of lasts week's
  current.
  
  Any public reamings likely will result in some sanction from core.
  Control your temper, or else.
 
 Here comes the Great Core FreeBSD Censor Police!!!
 I can't believe Bill's email, elected this threat from Core.  Become a
 committer and loose rights others on this mailing list have.
 Feh, is a group hug next?

Come on...

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 8MB install

2003-06-25 Thread Wilko Bulte
On Wed, Jun 25, 2003 at 12:45:19PM +0200, Simon L. Nielsen wrote:
 On 2003.06.25 12:10:42 +0200, Michael Nottebrock wrote:
  On Wednesday 25 June 2003 11:44, Terry Lambert wrote:
  
   Alternately, you could find a FreeBSD 1.1.5.1 distribution on the
   net somewhere, and install that, instead; I have personally run
   that version of FreeBSD on a 4M 386SX, to use it as an X Terminal.
   8-).
  
  FWIW, the last FreeBSD release I managed to install on an 8mb machine from 
  CD-ROM+bootfloppies was 4.1.1.
 
 Can anybody else confirm this ?  It seems like the documetation need to
 be updated to state this.
 
 Have anybody made any recent tests on CURRENT (and STABLE for that
 matter) with regards to minimum RAM requirements, install and normal
 runtime?

CURRENT in 8MB is a joke.

For 4.x the minimum to get an installer running was something like 12MB
for years now.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: matcd rises from the ashes!

2003-06-24 Thread Wilko Bulte
On Tue, Jun 24, 2003 at 08:31:44AM -0400, Paul Mather wrote:

 licensing problems have been fixed.  (I notice the original 10-point
 license has shrunk to only 3 in the latest version.)  So, could we
 please (pretty please) have matcd also magically reappear in 4-STABLE?

Frank Durda is back, and has re-written the driver to work in 5.x


 nice (but not essential) if I could upgrade it to 4.8-STABLE so it was
 at the same level as my other FreeBSD 4 box.  (I notice from the edit
 history in matcd.c that the original author of the driver is actively
 developing it for FreeBSD 5, so maybe he could MFC his license changes
 [re: edit 40 in the change log] back to 4-STABLE??)

I don't know what his plans are for 4.x, why not ask him directly?

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ReiserFS

2003-06-22 Thread Wilko Bulte
On Sun, Jun 22, 2003 at 07:00:26PM +0200, Brad Knowles wrote:
 At 9:50 AM -0700 2003/06/22, Lars Eggert wrote:
 
  Make the ReiserFS box an NFS server and mount it on FreeBSD to copy the
  data over.
 
   What if it's the same machine?  What if they have only the one 
 machine, so they can't even copy it over to another one, just to copy 
 it back?

Borrow a tape unit, or a second disk, or a CDRW / DVDRW. 
Something along those lines, lacking Reiserfs in FreeBSD that 
leaves you little other option.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Proof of concept patch for device rearrangement

2003-06-19 Thread Wilko Bulte
On Thu, Jun 19, 2003 at 01:16:56AM +0200, Maxime Henrion wrote:
 walt wrote:
  Poul-Henning Kamp wrote:
  
  I have uploaded a proof of concept patch:
  
 http://phk.freebsd.dk/patch/fd_dev.patch
  
  
  ...And with this code enabled, it is possible to go from userland to
  device driver without touching Giant underway.
  
  I'm sorry, I can't parse that last sentence.  Could you explain in
  25 words or less (or 3 lines of code) what it means?
  
  'Giant' is the lock that Alan is trying to get rid of?
 
 Giant is the big lock that protects the whole kernel that everyone is
 trying to get rid of :-).

Get rid of the lock that is ;-)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cvs commit: src/share/man/man4 axe.4 mac_portacl.4 my.4rndtest.4 rue.4 sbsh.4 src/share/man/man4/man4.i386 pae.4 sbni.4vpd.4

2003-05-30 Thread Wilko Bulte
On Fri, May 30, 2003 at 12:31:05AM +0300, Ruslan Ermilov wrote:
 On Thu, May 29, 2003 at 02:28:36PM -0700, Ruslan Ermilov wrote:
  ru  2003/05/29 14:28:36 PDT
  
FreeBSD src repository
  
Modified files:
  share/man/man4   axe.4 mac_portacl.4 my.4 rndtest.4 rue.4 
   sbsh.4 
  share/man/man4/man4.i386 pae.4 sbni.4 vpd.4 
Log:
Assorted mdoc(7) fixes.

Approved by:re (blanket)

 Now this is real funny: the sbsh(4) manpage says the driver
 first appeared in FreeBSD 4.9, but 5.1 will be released
 before 4.9.  Something wrong with our release model?  ;)

Virtualised time?

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: policy on GPL'd drivers?

2003-05-27 Thread Wilko Bulte
On Tue, May 27, 2003 at 10:23:04AM -0400, Alexander Kabaev wrote:
 On Tue, 27 May 2003 07:20:17 -0700
 Steve Kargl [EMAIL PROTECTED] wrote:
 
  On Tue, May 27, 2003 at 08:45:29AM -0400, Alexander Kabaev wrote:
   On Tue, 27 May 2003 14:36:26 +0200
  
   I and no doubt many others will insist on keeping GPLed drivers out
   of the tree. I have no objections for this drivers to be confined in
   ports though.
  
  kargl[205] ls /sys/gnu/dev/sound/pci
  csaimg.h*  emu10k1-ac97.h  emu10k1.h  maestro3_dsp.h  maestro3_reg.h
  
  The maestro3 driver is in the tree and is covered by the GPL
  for the same reasons that David will need to GPL the FreeBSD
  version of the nForce driver.
  
  -- 
  Steve
 This doesn't mean it is an open season for contaminating the tree with
 GPL. 

Nobody said so. But this is a policy set by core..

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Removing Sendmail

2003-04-02 Thread Wilko Bulte
On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote:

...

  [stepping back a bit ]
 
 I find an odd situation here whenever this topic comes up.  One the
 one hand, people are always wanting to split the entire base system
 up into small packages for each little piece of the base.  On the
 other hand, one of FreeBSD's selling points in real-world environments
 is that it doesn't have a bunch of little packages for the base system
 like Linux distros.  Do people really prefer something like having
 rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin,
 etc.?

BarfPuke One of the worst mis-features of Linux in my book.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Removing Sendmail

2003-04-02 Thread Wilko Bulte
On Wed, Apr 02, 2003 at 11:28:53PM +0300, Dan Naumov wrote:
 On Wed, 2 Apr 2003 21:56:40 +0200
 Wilko Bulte [EMAIL PROTECTED] wrote:
 
  On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote:
   
   I find an odd situation here whenever this topic comes up.  One the
   one hand, people are always wanting to split the entire base system
   up into small packages for each little piece of the base.  On the
   other hand, one of FreeBSD's selling points in real-world
   environments is that it doesn't have a bunch of little packages for
   the base system like Linux distros.  Do people really prefer
   something like having rpm's for /bin/ps to having one lump base dist
   for all of /bin, /sbin, etc.?
  
  BarfPuke One of the worst mis-features of Linux in my book.
 
 I think being able to update just about ANYTHING, except the kernel
 without the need for a reboot is one of the best features of Linux and
 actual advantages it has over FreeBSD.

Then go and run Linux. I like my FreeBSD bikeshed better ;)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Clock running double time

2003-03-18 Thread Wilko Bulte
On Tue, Mar 18, 2003 at 07:23:48PM +0100, Poul-Henning Kamp wrote:
 In message [EMAIL PROTECTED], Kevin Oberman writes:
 
  kern.timecounter.hardware=TSC
 
 Can someone explain why TSC is preferred to i8254 (or why not)?
 
 Cheaper access  better resolution.

Which brings me to the question if there is a comprehensive story
on timekeeping in FreeBSD in the docs? Like the EuroBSDcon2002
one, but with answers to questions like the one above added.

[I did not hunt in the doc tree for it btw]

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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


Re: HEADS UP: Don't upgrade your Alphas!

2003-03-17 Thread Wilko Bulte
On Mon, Mar 17, 2003 at 02:12:31PM -0800, David Schultz wrote:
 Thus spake Ruslan Ermilov [EMAIL PROTECTED]:
  Hold off upgrading your Alphas for a moment.
  Something broke libc recently that results in
  (at least) floating point exceptions from
  awk(1) (this is not related to today's awk
  upgrade).
  
  I've been able to reproduce this on beast.freebsd.org
  by building the fresh libc.a and linking awk with
  it, and running a test case.
  
  I haven't been able to reproduce this with 8th
  March libc, so the time window for the breakage
  is low.
  
  I suspect the recent gtdoa commit to libc; we
  will know that is less than an hour.
 
 Whups.  You're probably using a locale in which the decimal point
 is not a period.  In that case, please use the patches I just
 posted to the following thread, which I just CC'd you.

Ruslan has been using my Alphas to test this and there
is no locale set on those.

 If it really is an Alpha issue and not a locale issue, awk is
 probably dying on one of the scripts used by the kernel build.
 If you could send me the command line that causes awk to die,
 that would be helpful.  I'm running a kernel build on beast
 right now to see if I can reproduce a problem.  I have a meeting
 in a few minutes, but I'll be back in five hours or so to follow
 up on this.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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


Re: Time drift.

2003-03-12 Thread Wilko Bulte
On Wed, Mar 12, 2003 at 07:14:38AM +0100, Poul-Henning Kamp wrote:
 In message [EMAIL PROTECTED], Andrew
  P. Lentvorski, Jr. writes:
 
 An $8.00 wristwatch has much better time accuracy that your multi-$100 PC.
 
 That's because the crystal in your wristwatch is cut specially so that it
 has a flat temp-co at about 23-16 C, whereas the xtal in your computer
 is has a gradient all the way from 0 to 70 C.

And this is easily verifiable too: just leave your wristwatch in an unheated
(cold) bedroom and watch the drift. 

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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


Re: IP over IEEE1394?

2003-03-05 Thread Wilko Bulte
On Wed, Mar 05, 2003 at 07:25:20AM -0600, David Leimbach wrote:
 Interesting... I didn't even know we had Ethernet over firewire :).
 
 Mac OS X and Windows XP both have IP over firewire either working or
 in the works and somewhat usable.  The only one I can claim any  
 experience
 with is Mac OS X.  It's somewhat flaky though and you get unreliable  
 spikes
 in some basic performance tests I have done with it.
 
 It would be a really interesting value added feature for FreeBSD 5.x
 and could potentially open FBSD up even more to the cluster market
 which is somewhere its not as proliferated as linux.
 
 With the advent of firewire2  on the horizon it may be even more  
 impressive.

The interconnect is just 10% of the whole cluster story. Firewire
is one possibility, but Fibrechannel you could do today if you wanted
to. We have Fibrechannel support in the Qlogic isp(4) driver (thanks
Matt!) today.

W/

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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


Re: Removal of netns

2003-03-04 Thread Wilko Bulte
On Tue, Mar 04, 2003 at 07:56:27AM -0800, Terry Lambert wrote:
 Tim Robbins wrote:
  Is there a compelling reason why I shouldn't remove netns? That is, does
  it serve a purpose now that it could not serve if it was moved to the
  Attic?
 
 Might as well move /sys/i386/conf/GENERIC to the attic while
 you are at it.  It can serve it's purpose from there, too.
 
 Is there a compelling reason for doing this, other than I
 want to make some API/locking change, but I don't want to
 have to keep this code working at the same time?  Maximizing

Is there a compelling reason for you to moan about the removal
of things constantly?

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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


Re: wi0 - need help

2003-03-01 Thread Wilko Bulte
On Sat, Mar 01, 2003 at 08:08:36PM +0100, Christoph P. Kukulies wrote:
 On Sat, Mar 01, 2003 at 11:35:37AM -0700, M. Warner Losh wrote:
 

 
 It works!
 Packets started flowing right after I typed in the above line.
 
  
  and
  
  ifconfig wi0 192.168.254.2 netmask 255.255.255.0 ssid kuku stationname \
   kukulap media DS/11Mbps mediaopt adhoc[*]
  
  [*] adhoc is spelled ibss-create on 4.x
  
  Warner
 
 How can I find out whether I can run the interface in hostap mode?
 At the moment it runs in adhoc mode.

If you try ifconfig bla hostap and the card is not capable of doing that
(wrong chipset e.g) it will give you an error.

Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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


Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

2003-02-15 Thread Wilko Bulte
On Sat, Feb 15, 2003 at 10:37:26PM +0100, [EMAIL PROTECTED] wrote:
 In message [EMAIL PROTECTED], Makoto Matsushita writes:
 
 I've tried to do make release of FreeBSD/alpha on FreeBSD/i386 box
 last night, and found that follow error while generating drivers.flp:
 
 If my understandings are correct, this is because disklabel(8) kicked
 is FreeBSD/i386 native binary which doesn't know about FreeBSD/alpha
 disklabel structure or whatever.
 
 Are there any workaround/fix?
 
 Not yet.  I think adding a -m architecture flag to disklabel is the
 way around this problem, but have not had time to do so.

But now that you have an alpha machine... ;-)
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: Force 1 CPU on SMP kernel?

2003-01-28 Thread Wilko Bulte
On Tue, Jan 28, 2003 at 12:33:32PM -0500, Andre Guibert de Bruet wrote:
 
 
 On Tue, 28 Jan 2003, Adam Migus wrote:
 
  Yes, just to be more explicit.  What I want to do is get the
  'real' difference a second processor makes.  ie. If I run
  GENERIC I'm not incurring the overhead associated with SMP/APIC.
   I want to use the same kernel making as small a change as
  nessessary to have the machine start/use just one CPU.
 
 I'm not aware of any hacks to disable APs through loader.conf. If you're
 trying to benchmark the system's performance with 1 vs N CPUs, you're best
 off pulling all but the BSP CPU out of the machine. For such a benchmark
 to be accurate, you shouldn't make any software changes (kernel, daemons
 or startup configs).

VOlunteers to implement psradm maybe?

W/

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: HEADSUP: disklabel(8): men at work.

2003-01-26 Thread Wilko Bulte
On Sun, Jan 26, 2003 at 03:47:11PM +0100, Poul-Henning Kamp wrote:
 
 I'm still not done with disklabel(8), and I have not run it through
 all the tests I want (I'm waiting for my glacial 233MHz EV45 alpha
 to compile a world) so be careful what you do with disklabel and in
 particular the -B option.

Time to put a DS10 on wantlist.sgml I suppose? ;)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: unexpected machine check on 5.0 alpha

2003-01-15 Thread Wilko Bulte
On Wed, Jan 15, 2003 at 02:19:19PM -0800, Kris Kennaway wrote:
 On Wed, Jan 15, 2003 at 05:15:56PM -0500, Andrew Gallatin wrote:
  
  Kris Kennaway writes:
I just got this on one of the axp machines [*]:

unexpected machine check:

mces= 0x1
vector  = 0x670
  
  670 is a cpu machine check -- thats most likely an uncorretable
  memory parity error or some other (intermittent) hardware failure
  caused by overheating, etc.
  
  This is what?  A miata?
 
 Yes.

Time to check the fan for the CPU, and the air'tunnel' feeding the
air to the heatsink. I had one come loose after servicing the machine.
Impractical..

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: 5.0 Freezes under high load with SMP.

2003-01-14 Thread Wilko Bulte
On Tue, Jan 14, 2003 at 11:12:30AM -0800, Nate Lawson wrote:
 On Tue, 14 Jan 2003, wade wrote:
  Although GENERIC functions perfectly, when I enable SMP in GENERIC, the box
  freezes during big build jobs ( i.e. buildworld. ).  This box functioned
  well in SMP mode und 4.7-STABLE.  The big problem is that freezing does not
  leave core files or any other debugging information.
  
  Hardware: 
ASUS CUV4X-D
2 X PIII 600 MHz Coppermine.
512 MB 133MHz RAM.
 
 Hit ctl-alt-esc on console to enter DDB (enable this kernel option if you
 haven't already).  Type trace to find out what is hung.  If this doesn't
 work, attach a serial console and do a break there and trace.

Interesting, as I have been trying the last 3 days to reproduce freezes 
that people reported on 5.0 on (specifically) the ASUS BP6 mainboard.

I ran continuous make -j16 buildworlds to see if I could break it, but 
no luck (or very good luck, depends on your perspective ;-)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: 5.0 Freezes under high load with SMP.

2003-01-14 Thread Wilko Bulte
On Tue, Jan 14, 2003 at 11:51:36AM -0800, Nate Lawson wrote:
 On Tue, 14 Jan 2003, Wilko Bulte wrote:
  On Tue, Jan 14, 2003 at 11:12:30AM -0800, Nate Lawson wrote:
   On Tue, 14 Jan 2003, wade wrote:
Although GENERIC functions perfectly, when I enable SMP in GENERIC, the box
freezes during big build jobs ( i.e. buildworld. ).  This box functioned
well in SMP mode und 4.7-STABLE.  The big problem is that freezing does not
leave core files or any other debugging information.

Hardware: 
  ASUS CUV4X-D
  2 X PIII 600 MHz Coppermine.
  512 MB 133MHz RAM.
   
   Hit ctl-alt-esc on console to enter DDB (enable this kernel option if you
   haven't already).  Type trace to find out what is hung.  If this doesn't
   work, attach a serial console and do a break there and trace.
  
  Interesting, as I have been trying the last 3 days to reproduce freezes 
  that people reported on 5.0 on (specifically) the ASUS BP6 mainboard.
  
  I ran continuous make -j16 buildworlds to see if I could break it, but 
  no luck (or very good luck, depends on your perspective ;-)
 
 That's an Abit BP6, different from this Asus mobo.  :)

Yes, I know ;)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: weird serial console issue

2002-12-11 Thread Wilko Bulte
On Tue, Dec 10, 2002 at 11:41:35PM +0100, Wilko Bulte wrote:

Well, I think my DS10 does not have that problem as in:

ppi0: Parallel I/O on ppbus0
ppc0: interrupting at ISA irq 7
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x0
sc0: fb0, kbd0, terminal emulator: sc (syscons terminal)
sio0: irq maps: 0x81 0x91 0x81 0x81
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A, console
sio0: interrupting at ISA irq 4
sio1: reserved for low-level i/o
sio1 failed to probe at port 0x2f8-0x2ff irq 3 flags 0x50 on isa0
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xb8000 size:32k gran:32k, buf:0 size:32k
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39 
3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff 
VGA parameters in BIOS for mode 24
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
EGA/VGA parameters to be used for mode 24
50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39 
3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff 
isa_probe_children: probing PnP devices
procfs registered
Timecounter i8254  frequency 1193182 Hz
Timecounter alpha  frequency 462387140 Hz
Timecounters tick every 0.976 msec

Taken from the serial console.

Wilko


 On Tue, Dec 10, 2002 at 02:01:16PM -0500, Andrew Gallatin wrote:
 
 I will bring my DS10 to the latest  greatest -current and see what it
 does for me. Stay tuned (till tomorrow at least ;)
 
 W/
 
 
  I just upgraded my UP1000 from 4.7-stable to 5.0.
  
  Only weird thing left is the console seems to drop a lot of characters
  just after syscons takes over.
  
  I see this on console:
  
  ...
  ppc0: interrupting at ISA irq 7
  sc0: System console on isa0
  sc0: VGA 16 virtual consoles, flags=0x0
  net.inet.udp.blackhole: 0 - 1
  Doing initial network setup: host.conf hostname domain.
  ...
  
  
  And this (correct output) in dmesg:
  
  ppc0: interrupting at ISA irq 7
  sc0: System console on isa0
  sc0: VGA 16 virtual consoles, flags=0x0
  sio0 at port 0x3f8-0x3ff irq 4 on isa0
  sio0: type 16550A, console
  sio0: interrupting at ISA irq 4
  sio1 at port 0x2f8-0x2ff irq 3 on isa0
  sio1: type 16550A
  sio1: interrupting at ISA irq 3
  vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
  Timecounters tick every 0.976 msec
  Timecounter i8254  frequency 1193182 Hz
  Timecounter alpha  frequency 598976859 Hz
  ad2: DMA limited to UDMA33, non-ATA66 cable or device
  ad2: 39266MB IC35L040AVER07-0 [79780/16/63] at ata1-master UDMA33
  acd0: CDROM CD-ROM CDU4011 at ata1-slave PIO4
  Mounting root from ufs:/dev/ad2a
  
  
  Note that everything past sc0 seems to have disappeared until it
  re-appears partway through multi-user startup.  Its not a sysctl
  on a comcontrol thing, because booting single-user is similar.
  The output stops after sc0, and starts again when I hit return.
  
  This is a serial console, connected to a 5.0 x86 running conserver 8.5
  on an 8-port comtrol rocketport card.  The speed is only 9600 baud,
  and the console server seems to be able to handle it, so I think the
  problem is at the alpha end..
  
  
  Drew
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message
 ---end of quoted text---
 
 -- 
 |   / o / /_  _   FreeBSD core team secretary
 |/|/ / / /(  (_)  Bulte   [EMAIL PROTECTED]
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

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



Re: weird serial console issue

2002-12-11 Thread Wilko Bulte
On Wed, Dec 11, 2002 at 02:22:12PM -0500, Andrew Gallatin wrote:
 
 Wilko Bulte writes:
   On Tue, Dec 10, 2002 at 11:41:35PM +0100, Wilko Bulte wrote:
   
   Well, I think my DS10 does not have that problem as in:
 ..
   50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 
 ..
 
 Try booting without verbose..

...
lpt0: Polled port
ppi0: Parallel I/O on ppbus0
ppc0: interrupting at ISA irq 7
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x0
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A, console
sio0: interrupting at ISA irq 4
sio1: reserved for low-level i/o
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter i8254  frequency 1193182 Hz
Timecounter alpha  frequency 462383710 Hz
Timecounters tick every 0.976 msec
acd0: CDROM TOSHIBA CD-ROM XM-6302B at ata0-master PIO4
Waiting 15 seconds for SCSI devices to settle
da0 at isp0 bus 0 target 0 lun 0
...

-- 
Wilko

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



Re: weird serial console issue

2002-12-10 Thread Wilko Bulte
On Tue, Dec 10, 2002 at 02:01:16PM -0500, Andrew Gallatin wrote:

I will bring my DS10 to the latest  greatest -current and see what it
does for me. Stay tuned (till tomorrow at least ;)

W/


 I just upgraded my UP1000 from 4.7-stable to 5.0.
 
 Only weird thing left is the console seems to drop a lot of characters
 just after syscons takes over.
 
 I see this on console:
 
 ...
 ppc0: interrupting at ISA irq 7
 sc0: System console on isa0
 sc0: VGA 16 virtual consoles, flags=0x0
 net.inet.udp.blackhole: 0 - 1
 Doing initial network setup: host.conf hostname domain.
 ...
 
 
 And this (correct output) in dmesg:
 
 ppc0: interrupting at ISA irq 7
 sc0: System console on isa0
 sc0: VGA 16 virtual consoles, flags=0x0
 sio0 at port 0x3f8-0x3ff irq 4 on isa0
 sio0: type 16550A, console
 sio0: interrupting at ISA irq 4
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 sio1: interrupting at ISA irq 3
 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
 Timecounters tick every 0.976 msec
 Timecounter i8254  frequency 1193182 Hz
 Timecounter alpha  frequency 598976859 Hz
 ad2: DMA limited to UDMA33, non-ATA66 cable or device
 ad2: 39266MB IC35L040AVER07-0 [79780/16/63] at ata1-master UDMA33
 acd0: CDROM CD-ROM CDU4011 at ata1-slave PIO4
 Mounting root from ufs:/dev/ad2a
 
 
 Note that everything past sc0 seems to have disappeared until it
 re-appears partway through multi-user startup.  Its not a sysctl
 on a comcontrol thing, because booting single-user is similar.
 The output stops after sc0, and starts again when I hit return.
 
 This is a serial console, connected to a 5.0 x86 running conserver 8.5
 on an 8-port comtrol rocketport card.  The speed is only 9600 baud,
 and the console server seems to be able to handle it, so I think the
 problem is at the alpha end..
 
 
 Drew
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ FreeBSD core team secretary
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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



Re: mozilla busted?

2002-09-20 Thread Wilko Bulte

On Fri, Sep 20, 2002 at 10:43:13AM -0400, John Baldwin wrote:
 
 On 20-Sep-2002 M. Warner Losh wrote:
  In message: [EMAIL PROTECTED]
  Joe Marcus Clarke [EMAIL PROTECTED] writes:
 : On Thu, 2002-09-19 at 23:22, M. Warner Losh wrote:
 :  In message: [EMAIL PROTECTED]
 :  Julian Elischer [EMAIL PROTECTED] writes:
 :  : Is it statically linked?
 :  
 :  Yup.
 : 
 : You'll need to rebuild against the new libc_r, then.
  
  Yuck.  I'd rather nail jello to a tree than try to update a port that
  complicated.
 
 * BigKnife hands bsdimp a hammer and some nails

* Bigknife should preserve nature (trees) and properly recycle jello.

;-)

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: current buildworld failure on Alpha?

2002-08-25 Thread Wilko Bulte

On Wed, Aug 21, 2002 at 11:38:00AM +, Christian Weisgerber wrote:
 Wilko Bulte [EMAIL PROTECTED] wrote:
 
  ds10#make
  Segmentation fault (core dumped)
  /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m
  /usr/src/share/mk  CPUTYPE=ev56 -V CPUTYPE returned non-zero status
 
 There was a time window when make -V ... was broken on 64-bit
 archs, i.e. it would segfault after printing the result.  This has
 been fixed in revision 1.69 of make/main.c.
 
  FreeBSD ds10.wbnet 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Sat Aug 10 19:51:27
 
 make was fixed on August 11.

Thanks! A manual make/make install of 'make' ;) fixed it

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



current buildworld failure on Alpha?

2002-08-20 Thread Wilko Bulte

What did I miss this time?

ds10#make
Segmentation fault (core dumped)
/usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m
/usr/src/share/mk  CPUTYPE=ev56 -V CPUTYPE returned non-zero status
/usr/src/Makefile.inc1, line 142: CPUTYPE global should be set with ?=.
*** Error code 1

Stop in /usr/src.
ds10#
ds10#
ds10#uname -a 
FreeBSD ds10.wbnet 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Sat Aug 10 19:51:27
CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DS10  alpha
ds10#date
Tue Aug 20 22:44:41 CEST 2002
ds10#


-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: About GEOM...

2002-07-03 Thread Wilko Bulte

On Wed, Jul 03, 2002 at 11:59:47AM +0200, Poul-Henning Kamp wrote:
 In message [EMAIL PROTECTED], Jul
 ian Elischer writes:
 
 aren't you suppost to be honeymooning from yesterday?
 
 I am, I'm not working, only doing things I do for fun :-)

Like reading Linux source code? 

ducks for cover 8-)

-- 
|   / o / /_  _ FreeBSD core team secretary
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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



Re: XFree86-4-libraries build error

2002-05-29 Thread Wilko Bulte

On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:

FWIW: same here yesterday. I have not yet investigated what's up

Wilko

 I'm getting the following error on a just built -current, which was a 
 fresh install of 5.0-CURRENT-20020519-JPSNAP:
 
 installing in lib/XThrStub...
 rm -f UIThrStubs.o
 LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe-ansi -pedantic 
 -Dasm=__asm
 -Wall -Wpointer-arith -I../.. -I../../exports/include   -DCSRG_BASED 
   -DFUNC
 PROTO=15 -DNARROWPROTO -DXTHREADS   -DXUSE_MTSAFE_API 
 -DXNO_MTSAFE_PWDAPI-DM
 ALLOC_0_RETURNS_NULL-ansi -pedantic -Dasm=__asm -Wall 
 -Wpointer-arith-I.
 ./.. -I../../exports/include   -DCSRG_BASED  -DFUNCPROTO=15 
 -DNARROWPROTO -DXTHR
 EADS   -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL 
  -fPI
 C UIThrStubs.c
 UIThrStubs.c:102: alias arg not a string
 UIThrStubs.c:103: alias arg not a string
 UIThrStubs.c:104: alias arg not a string
 UIThrStubs.c:105: alias arg not a string
 UIThrStubs.c:106: alias arg not a string
 UIThrStubs.c:107: alias arg not a string
 UIThrStubs.c:108: alias arg not a string
 UIThrStubs.c:109: alias arg not a string
 UIThrStubs.c:110: alias arg not a string
 UIThrStubs.c:111: alias arg not a string
 UIThrStubs.c:113: alias arg not a string
 UIThrStubs.c:114: alias arg not a string
 UIThrStubs.c:115: alias arg not a string
 UIThrStubs.c:131: warning: `_Xthr_self_stub_' defined but not used
 UIThrStubs.c:139: warning: `_Xthr_zero_stub_' defined but not used
 *** Error code 1
 
 Stop in /usr/ports/x11/XFree86-4-libraries/work/xc/lib/XThrStub.
 
 Pete...
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: MAKEDEV in current

2002-05-21 Thread Wilko Bulte

On Tue, May 21, 2002 at 10:41:05AM -0700, Rob wrote:
 I've tried to copy MAKEDEV to /dev in current.  But get the error-
 operation not supported.  I must be missing some very basic concept. 
 Rob.

Rather basic ;-) : -current uses the devfs filesystem 

man devfs tells you more about the idea behind this

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Special fx with disklabel(8)?

2002-05-12 Thread Wilko Bulte

On Sun, May 12, 2002 at 10:19:45PM -0700, Terry Lambert wrote:
 Poul-Henning Kamp wrote:
   Please do not follow Terrys advice, unless and until you have
   independent confirmation that his 10 year old knowledge is still
   current.
  
  Poul: I will say that advice is bad, but I will not provide advice
 of my own, because it might be bad, too, and open me to the
 same type of attack I like to make on others.  It's just so
 much easier to criticize someone than it is to help solve a
 problem and risk being attacked by someone else like me.
  
  Terry: I would appreciate if you would ensure that your knowledge
  is up to date before you mislead people with it.
 
 Poul: Of course, *my* knowledge is up to date because *I'm* Poul; but
I'll be damned if I'll share it, because then I can't beat people
over the head for not having it, and beating people over the head
is ever so much more fun, isn't it?  Meanwhile, I'm still not
going to answer the original poster's question

Gentlemen.. does this discussion on a public list serve any useful purpose?

-- 
|   / o / /_  _ FreeBSD core team secretary
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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



Re: PAM doesn't allow to log-in when /var mounted ro

2002-05-02 Thread Wilko Bulte

On Thu, May 02, 2002 at 04:24:16PM +0300, Maxim Sobolev wrote:

/var mounted ro sounds like a truly bad idea to me BTW. 

 Hi,
 
 Subject says it all. I'm getting the following from the syslog:
 
 login: cannot open /var/log/lastlog: Read-only file system
 login: pam_open_session(): error in service module
 
 This violates POLA, therefore please fix ASAP.
 
 -Maxim
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Alpha Build

2002-03-26 Thread Wilko Bulte

On Tue, Mar 26, 2002 at 07:56:39AM -0500, Michael Lucas wrote:
 Either would work.
 
 I have an Alpha Multia-166 that I use to play with -current on.  As it
 has a TGA card, it's running via serial console.  This machine feels
 like the equivalent of, say, a 50MHz 486.
 
 Each day, I try to build -current.  (Hey, it's good for a laugh.  :-)

You will gain saint-like patience as a bonus..

;)
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Alpha Build

2002-03-26 Thread Wilko Bulte

On Wed, Mar 27, 2002 at 03:15:14AM +0200, Giorgos Keramidas wrote:
 On 2002-03-26 12:00, Terry Lambert wrote:
  Wilko Bulte wrote:
   On Tue, Mar 26, 2002 at 07:56:39AM -0500, Michael Lucas wrote:
Each day, I try to build -current.  (Hey, it's good for a laugh.  :-)
  
   You will gain saint-like patience as a bonus..
  
   ;)
 
  Remind me again of the value of saint-like patience, in the larger
  scheme of things...
 
 It's the extra warmth and fuzziness one feels, as the horns on top of one's
 head start turning into a brilliant, blazing circle of light...  at least
 this is what happens for i386 users.  The Alpha users are less easy to turn
 into saints.  They tend to twist and shout that's not a 64-bit wing, get
 it away from me when one tries to remove their devil horns and tail :)))

Right.

And that is not evening mentioning those who want MI fine-grained wings :-P

Hmm, come to think of it, saint-like is Not Done(TM) in their neighbourhood.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands
   We are FreeBSD.  Resistance is futile.  Prepare to be committed.

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



Re: witness panic on Alpha

2002-03-25 Thread Wilko Bulte

On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote:

  lstat() at lstat+0x50
  syscall() at syscall+0x318
  XentSys() at XentSys+0x64
  --- syscall (190, FreeBSD ELF, lstat) ---
  --- user mode ---
  db 
 
 Is this reproducible?  If so, can you do a 'show locks'? 

Sofar it happened once. But I'll try to catch it again.

-- 
|   / o / /_  _ 
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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



Re: witness panic on Alpha

2002-03-25 Thread Wilko Bulte

On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote:

Looks like a different one:

db trace
siointr1() at siointr1+0x17c
siointr() at siointr+0x40
isa_handle_fast_intr() at isa_handle_fast_intr+0x28
alpha_dispatch_intr() at alpha_dispatch_intr+0xdc
interrupt() at interrupt+0x108
XentInt() at XentInt+0x28
--- interrupt (from ipl 0) ---
--- user mode ---
db 

and

db show locks
exclusive (spin mutex) sio (0xfc648d20) locked @
/usr/src/sys/dev/sio/sio.c:1634
db 

This is a serial console

Wilko

  No such command
  db trace
  Debugger() at Debugger+0x3c
  panic() at panic+0x100
  witness_lock() at witness_lock+0xb4
  _mtx_lock_flags() at _mtx_lock_flags+0xd8
  vfree() at vfree+0x30
  vm_page_free_toq() at vm_page_free_toq+0x200
  vm_page_free() at vm_page_free+0x2c
  vm_page_alloc() at vm_page_alloc+0x1ac
  pmap_growkernel() at pmap_growkernel+0x3e8
  vm_map_findspace() at vm_map_findspace+0x144
  kmem_alloc() at kmem_alloc+0x9c
  _zget() at _zget+0x244
  zalloc() at zalloc+0x78
  getnewvnode() at getnewvnode+0x470
  ffs_vget() at ffs_vget+0x168
  ufs_lookup() at ufs_lookup+0xf78
  ufs_vnoperate() at ufs_vnoperate+0x2c
  vfs_cache_lookup() at vfs_cache_lookup+0x3cc
  ufs_vnoperate() at ufs_vnoperate+0x2c
  lookup() at lookup+0x4d0
  namei() at namei+0x308
  lstat() at lstat+0x50
  syscall() at syscall+0x318
  XentSys() at XentSys+0x64
  --- syscall (190, FreeBSD ELF, lstat) ---
  --- user mode ---
  db 
 
 Is this reproducible?  If so, can you do a 'show locks'? 

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: witness panic on Alpha

2002-03-25 Thread Wilko Bulte

On Mon, Mar 25, 2002 at 04:21:23PM -0500, John Baldwin wrote:

 On 25-Mar-2002 Wilko Bulte wrote:
  On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote:
  
  Looks like a different one:
  
  db trace
  siointr1() at siointr1+0x17c
  siointr() at siointr+0x40
  isa_handle_fast_intr() at isa_handle_fast_intr+0x28
  alpha_dispatch_intr() at alpha_dispatch_intr+0xdc
  interrupt() at interrupt+0x108
  XentInt() at XentInt+0x28
  --- interrupt (from ipl 0) ---
  --- user mode ---
  db 
  
  and
  
  db show locks
  exclusive (spin mutex) sio (0xfc648d20) locked @
  /usr/src/sys/dev/sio/sio.c:1634
  db 
  
  This is a serial console
 
 Hummm, and you got a blockable lock panic here?

Well.. I lost the system for a reboot that served as the console display
so I cannot tell unfortunately what the panic message said.

W/

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: can't build world on alpha

2002-03-24 Thread Wilko Bulte

On Sat, Mar 23, 2002 at 11:02:26AM -0800, Matthew Dillon wrote:

As a datapoint, this does work when starting from a 4.5-RELEASE
I just did a build yesterday on the AS500 

Wilko


 Anyone have any ideas?  I'm trying to build the latest -current
 (from cvs) on an alpha running 4.3-RELEASE, using 'make buildworld'.
 
   -Matt
   Matthew Dillon 
   [EMAIL PROTECTED]
 
 cc -O -pipe -mcpu=ev4 -D_open=open -DIN_GCC -DHAVE_CONFIG_H 
-DPREFIX=\/usr/obj/FreeBSD/FreeBSD-current/src/alpha/usr\ -DHAIFA 
-I/usr/obj/FreeBSD/FreeBSD-current/src/alpha/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../cc_tools
 -I/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../cc_tools 
-I/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../contrib/gcc.295 
-I/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../contrib/gcc.295/config
  -c 
/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../lib/libc/stdio/mktemp.c
 -o mktemp.o
 
/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../lib/libc/stdio/mktemp.c:38:
 syntax error before string constant
 
/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../lib/libc/stdio/mktemp.c:38:
 warning: data definition has no type or storage class
 *** Error code 1
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



witness panic on Alpha

2002-03-23 Thread Wilko Bulte

Fri Mar 22 19:06:37 CET 2002

FreeBSD/alpha (ds10.wbnet) (ttyd0)

login:   syslogd: /var/log/auth.log: No such file or directory
  syslogd: /var/log/auth.log: No such file or directory
Mar 22 21:55:23 ds10 kernel: pid 27885 (telnetd), uid 0: exited on signal 11
(co
re dumped)
Mar 22 21:55:30 ds10 kernel: pid 28342 (telnetd), uid 0: exited on signal 11
(co
re dumped)
  syslogd: /var/log/auth.log: No such file or directory
  syslogd: /var/log/auth.log: No such file or directory
panic: blockable sleep lock (sleep mutex) vnode_free_list @
/usr/src/sys/kern/vf
s_subr.c:2678
panic
Stopped at  Debugger+0x34:  zapnot  v0,#0xf,a0  v0=0x7,a0=0x6
db 
db tb
No such command
db bt
No such command
db st
Stopped at  Debugger+0x38:  call_pal osf1_swpipl
db stack
No such command
db trace
Debugger() at Debugger+0x3c
panic() at panic+0x100
witness_lock() at witness_lock+0xb4
_mtx_lock_flags() at _mtx_lock_flags+0xd8
vfree() at vfree+0x30
vm_page_free_toq() at vm_page_free_toq+0x200
vm_page_free() at vm_page_free+0x2c
vm_page_alloc() at vm_page_alloc+0x1ac
pmap_growkernel() at pmap_growkernel+0x3e8
vm_map_findspace() at vm_map_findspace+0x144
kmem_alloc() at kmem_alloc+0x9c
_zget() at _zget+0x244
zalloc() at zalloc+0x78
getnewvnode() at getnewvnode+0x470
ffs_vget() at ffs_vget+0x168
ufs_lookup() at ufs_lookup+0xf78
ufs_vnoperate() at ufs_vnoperate+0x2c
vfs_cache_lookup() at vfs_cache_lookup+0x3cc
ufs_vnoperate() at ufs_vnoperate+0x2c
lookup() at lookup+0x4d0
namei() at namei+0x308
lstat() at lstat+0x50
syscall() at syscall+0x318
XentSys() at XentSys+0x64
--- syscall (190, FreeBSD ELF, lstat) ---
--- user mode ---
db 


-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: strange apm/acpi message on CPQ Armada E700

2002-03-17 Thread Wilko Bulte

On Fri, Mar 15, 2002 at 11:11:45PM +0100, Wilko Bulte wrote:

Never mind.. this was due to the fact that device.hints had APM
disabled.

Looks a lot better now:

APM version: 1.2
APM Managment: Enabled
AC Line status: on-line
Battery status: charging
Remaining battery life: 62%
Remaining battery time: unknown
Number of batteries: 4
Battery 0:
Battery status: charging
Remaining battery life: 62%
Remaining battery time:  0:01:27
Battery 1:
Battery status: not present
Battery 2:
Battery status: not present
Battery 3:
Battery status: not present
APM Capacities:
global standby state
global suspend state
resume timer from standby
resume timer from suspend



 Hi
 
 I just went -current with my Compaq Armada E700 laptop.
 Coming from -stable.
 
 I'm a bit puzzled by:
 
 WKB ~: apm
 APM version: 1.2
 APM Managment: Enabled
 AC Line status: off-line
 Battery status: charging
 Remaining battery life: invalid value (0x)
 Remaining battery time: unknown
 Number of batteries: 0
 APM Capacities:
 unknown
 
 dmesg also has some strange things it appears
 
 
 Rebooting...
 Copyright (c) 1992-2002 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 #2: Fri Mar 15 22:48:40 CET 2002
 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WILKLT
 Preloaded elf kernel /boot/kernel/kernel at 0xc0436000.
 Preloaded elf module /boot/kernel/acpi.ko at 0xc04360a8.
 Timecounter i8254  frequency 1193182 Hz
 Timecounter TSC  frequency 498669634 Hz
 CPU: Pentium III/Pentium III Xeon/Celeron (498.67-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x681  Stepping = 1
   
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
 real memory  = 268369920 (262080K bytes)
 avail memory = 256614400 (250600K bytes)
 Pentium Pro MTRR support enabled
 Using $PIR table, 268435454 entries at 0xc00f0970
 npx0: math processor on motherboard
 npx0: INT 16 interface
 acpi0: COMPAQ RSDTBL   on motherboard
 ACPI-1305: *** Error: Method execution failed, AE_AML_REGION_LIMIT
 acpi0: power button is handled as a fixed feature programming model.
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 ACPI timer looks BAD  min = 2, max = 6, width = 5
 Timecounter ACPI-safe  frequency 3579545 Hz
 acpi_timer0: 24-bit timer at 3.579545MHz port 0x5008-0x500b on acpi0
 acpi_cpu0: CPU on acpi0
 acpi_tz0: thermal zone on acpi0
 acpi_acad0: AC adapter on acpi0
 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard
 pci0: PCI bus on pcib0
 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)
 pcic0: TI PCI-1450 PCI-CardBus Bridge mem 0x4110-0x41100fff irq 11 at device 
4.0 on pci0
 pcic0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq]
 pccard0: PC Card bus (classic) on pcic0
 pcic1: TI PCI-1450 PCI-CardBus Bridge mem 0x4118-0x41180fff irq 11 at device 
4.1 on pci0
 pcic1: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq]
 pccard1: PC Card bus (classic) on pcic1
 isab0: PCI-ISA bridge at device 7.0 on pci0
 isa0: ISA bus on isab0
 atapci0: Intel PIIX4 ATA33 controller port 0x3420-0x342f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x3400-0x341f irq 11 at device 
7.2 on pci0
 usb0: Intel 82371AB/EB (PIIX4) USB controller 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
 pci0: bridge, PCI-unknown at device 7.3 (no driver attached)
 pcm0: ESS Technology Maestro-2E port 0x3000-0x30ff irq 11 at device 8.0 on pci0
 fxp0: Intel Pro 10/100B/100+ Ethernet port 0x3440-0x347f mem 
0x4120-0x4121,0x4128-0x41280fff irq 11 at device 9.0 on pci0
 fxp0: Ethernet address 00:d0:59:0b:f3:c2
 inphy0: i82555 10/100 media interface on miibus0
 inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 pci0: simple comms, UART at device 9.1 (no driver attached)
 orm0: Option ROMs at iomem 0xd-0xd17ff,0xc-0xc on isa0
 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: PS/2 Mouse irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 fdc0: enhanced floppy controller (i82077, NE72065

strange apm/acpi message on CPQ Armada E700

2002-03-15 Thread Wilko Bulte

Hi

I just went -current with my Compaq Armada E700 laptop.
Coming from -stable.

I'm a bit puzzled by:

WKB ~: apm
APM version: 1.2
APM Managment: Enabled
AC Line status: off-line
Battery status: charging
Remaining battery life: invalid value (0x)
Remaining battery time: unknown
Number of batteries: 0
APM Capacities:
unknown

dmesg also has some strange things it appears


Rebooting...
Copyright (c) 1992-2002 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 #2: Fri Mar 15 22:48:40 CET 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/WILKLT
Preloaded elf kernel /boot/kernel/kernel at 0xc0436000.
Preloaded elf module /boot/kernel/acpi.ko at 0xc04360a8.
Timecounter i8254  frequency 1193182 Hz
Timecounter TSC  frequency 498669634 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (498.67-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x681  Stepping = 1
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 268369920 (262080K bytes)
avail memory = 256614400 (250600K bytes)
Pentium Pro MTRR support enabled
Using $PIR table, 268435454 entries at 0xc00f0970
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: COMPAQ RSDTBL   on motherboard
ACPI-1305: *** Error: Method execution failed, AE_AML_REGION_LIMIT
acpi0: power button is handled as a fixed feature programming model.
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
ACPI timer looks BAD  min = 2, max = 6, width = 5
Timecounter ACPI-safe  frequency 3579545 Hz
acpi_timer0: 24-bit timer at 3.579545MHz port 0x5008-0x500b on acpi0
acpi_cpu0: CPU on acpi0
acpi_tz0: thermal zone on acpi0
acpi_acad0: AC adapter on acpi0
pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
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)
pcic0: TI PCI-1450 PCI-CardBus Bridge mem 0x4110-0x41100fff irq 11 at device 4.0 
on pci0
pcic0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq]
pccard0: PC Card bus (classic) on pcic0
pcic1: TI PCI-1450 PCI-CardBus Bridge mem 0x4118-0x41180fff irq 11 at device 4.1 
on pci0
pcic1: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq]
pccard1: PC Card bus (classic) on pcic1
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0x3420-0x342f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x3400-0x341f irq 11 at device 
7.2 on pci0
usb0: Intel 82371AB/EB (PIIX4) USB controller 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
pci0: bridge, PCI-unknown at device 7.3 (no driver attached)
pcm0: ESS Technology Maestro-2E port 0x3000-0x30ff irq 11 at device 8.0 on pci0
fxp0: Intel Pro 10/100B/100+ Ethernet port 0x3440-0x347f mem 
0x4120-0x4121,0x4128-0x41280fff irq 11 at device 9.0 on pci0
fxp0: Ethernet address 00:d0:59:0b:f3:c2
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: simple comms, UART at device 9.1 (no driver attached)
orm0: Option ROMs at iomem 0xd-0xd17ff,0xc-0xc on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0: enhanced floppy controller (i82077, NE72065 or clone) at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
IPsec: Initialized Security Association Processing.
acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5%
system power profile changed to 'economy'
ad0: 17301MB IBM-DARA-218000 [35152/16/63] at ata0-master UDMA33
acd0: 

Re: Serial break into debugger broken from 'cu' on -CURRENT?

2002-03-11 Thread Wilko Bulte

On Mon, Mar 11, 2002 at 10:43:22PM +0100, Joerg Wunsch wrote:
 Bruce Evans [EMAIL PROTECTED] wrote:

 used to have two alternatives, cu and tip.  Now we only have tip and
 tip. :(  (I doubt tip has actually less security bugs than Taylor cu.
 If we threw out all the BSD-originating programs that once experienced
 a security problem, we would rather quickly end up with a skeleton
 that could hardly be named `Unix' anymore...)
 
  This is bug for bug compatible with the V7 cu except
  for the unusably slow speed of 9600.  For perfect brokenness, the
  default speed should be 300.
 
 *ROTFL*

Duh... goes hunting for the ASR33 to verify this. Strange that it
isn't 110baud :-P


-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Serial break into debugger broken from 'cu' on -CURRENT?

2002-03-10 Thread Wilko Bulte

On Sun, Mar 10, 2002 at 10:07:07AM -0500, Robert Watson wrote:
 
 For the past couple of months, I've been working with a set of identical
 test boxes from SGI which, for some reason, stopped responding to serial
 break on the serial console.  I switched to the 'alternative break' option
 in LINT, and things work fine.  I assumed it was actually some issue with
 that particular batch of machines, since no one else had had a problem,
 and I didn't really have time to follow up.  Yesterday, I brought online
 two more crash boxes via serial console, both older TeleNet servers, and
 noticed that neither of them respond to serial break over the serial
 console using cu.  This leads me to wonder two things: 
 
 (1) Is serial break currently broken in -CURRENT
 (2) Is serial break currently broken in 'cu'?

I had similar experiences with tip trying to break into ddb on the 
AlphaStation DS10 with -current. I thought it was just me ;-)


-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Serial break into debugger broken from 'cu' on -CURRENT?

2002-03-10 Thread Wilko Bulte

On Sun, Mar 10, 2002 at 08:49:16AM -0800, Mark Peek wrote:
 At 4:11 PM +0100 3/10/02, Wilko Bulte wrote:
 On Sun, Mar 10, 2002 at 10:07:07AM -0500, Robert Watson wrote:
 
   For the past couple of months, I've been working with a set of identical
   test boxes from SGI which, for some reason, stopped responding to serial
   break on the serial console.  I switched to the 'alternative break' option
   in LINT, and things work fine.  I assumed it was actually some issue with
   that particular batch of machines, since no one else had had a problem,
   and I didn't really have time to follow up.  Yesterday, I brought online
   two more crash boxes via serial console, both older TeleNet servers, and
   noticed that neither of them respond to serial break over the serial
   console using cu.  This leads me to wonder two things:
 
   (1) Is serial break currently broken in -CURRENT
   (2) Is serial break currently broken in 'cu'?
 
 I had similar experiences with tip trying to break into ddb on the
 AlphaStation DS10 with -current. I thought it was just me ;-)
 
 Hitting ~# in tip worked fine for me with a -current CVSup'd from 
 yesterday. However, it did stump me for a second until I realized I 
 was initially escaping into SSH and not tip.

Let me clarify: the DS10 is running -current, the x86 that has tip running 
is on -stable. 

It could be that the DS10 was sufficiently catatonic to not react to
a break (how likely is that in the first place? I was looking at a hard
lockup). Now that I followed Drew's suggestion to

quote

I suggest reverting rev 1.61 of alpha/alpha/interrupt.c (eg, disable
interrupt thread preemption).  I'm on the west coast right now, away
from my alphas, but I had several buildworlds complete last week with
ithread preemption disabled.

Drew
/quote

I have not seen a lockup anymore. I also had to take out options SMP
in order to get the kernel link.

W/

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Serial break into debugger broken from 'cu' on -CURRENT?

2002-03-10 Thread Wilko Bulte

On Sun, Mar 10, 2002 at 06:15:53PM +, Christian Weisgerber wrote:
 Wilko Bulte [EMAIL PROTECTED] wrote:
 
  It could be that the DS10 was sufficiently catatonic to not react to
  a break (how likely is that in the first place? I was looking at a hard
  lockup).
 
 If you experience one of the lockups that currently plague
 -CURRENT/alpha, the machine won't react to break, ctrl-alt-esc, or
 anything else except HALT and RESET.
 
  Now that I followed Drew's suggestion to
  
  quote
  I suggest reverting rev 1.61 of alpha/alpha/interrupt.c (eg, disable
  interrupt thread preemption).
  /quote
  
  I have not seen a lockup anymore.
 
 Neither have I, but I have only been running with it for a day, and
 it has previously managed to survive for up to two days without
 locking up.

Well, I had a close to 100% lockup or panic chance when I ran a make
release. I just completed a succesful buildworld, and will subsequently
run a make release.

W/

-- 
|   / o / /_  _ FreeBSD core team secretary
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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



Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )

2002-03-08 Thread Wilko Bulte

On Fri, Mar 08, 2002 at 01:35:47PM -0800, Matthew Jacob wrote:
 
 And FWIW, alpha kernels on some Uniprocessor boxes freeze up.

Yes. Or panic. See my posts earlier this week. I managed to get 
2 buildworlds without accidents, but all make release attempts either
paniced or froze.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: blockable sleep panic on Alpha / current

2002-03-05 Thread Wilko Bulte

On Tue, Mar 05, 2002 at 10:51:53AM -0500, John Baldwin wrote:
 
 On 04-Mar-02 Wilko Bulte wrote:
  During a make release I just got a panic. The build progressed until:
  
  gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxabs.3  imaxabs.3.gz
  gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxdiv.3  imaxdiv.3.gz
  gzip -cn /usr/src/lib/libc/../libc/stdlib/labs.3  labs.3.gz
  
  The running system is a -current as of today.
  
  The panic:
  
  login: 
  FreeBSD/alpha (ds10.wbnet) (ttyd0)
  
  login: panic: blockable sleep lock (sleep mutex) Giant @
  ../../../alpha/alpha/tr
  ap.c:482
  cpuid = 0; panic
  Stopped at  Debugger+0x34:  zapnot  v0,#0xf,a0  v0=0x7,a0=0x6
  db 
  db trace
  Debugger() at Debugger+0x34
  panic() at panic+0x188
  witness_lock() at witness_lock+0xb4
  _mtx_lock_flags() at _mtx_lock_flags+0xd8
  trap() at trap+0x4c8
  XentMM() at XentMM+0x2c
  --- memory management fault (from ipl 7) ---
  statclock_process() at statclock_process+0x1d4
 
 We did something stupid like dereference a NULL pointer here.  Can you pull up
 gdb on kernel.debug and do 'l *statclock_process+0x1d4'?


Is gdb broken on Alpha, or is it just me?

ds10#gdb
^C
ds10#gdb -k

^C
ds10#

In short, gdb just sits there (??).

On x86/stable I get:

wb ~: gdb
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i386-unknown-freebsd.
(gdb) wb ~: 
wb ~: 

etc

I'll to reproduce the problem again.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: blockable sleep panic on Alpha / current

2002-03-05 Thread Wilko Bulte

On Tue, Mar 05, 2002 at 10:51:53AM -0500, John Baldwin wrote:

Hi John,

 On 04-Mar-02 Wilko Bulte wrote:
  During a make release I just got a panic. The build progressed until:
  
  gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxabs.3  imaxabs.3.gz
  gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxdiv.3  imaxdiv.3.gz
  gzip -cn /usr/src/lib/libc/../libc/stdlib/labs.3  labs.3.gz
  
  The running system is a -current as of today.
  
  The panic:
  
  login: 
  FreeBSD/alpha (ds10.wbnet) (ttyd0)
  
  login: panic: blockable sleep lock (sleep mutex) Giant @
  ../../../alpha/alpha/tr
  ap.c:482
  cpuid = 0; panic
  Stopped at  Debugger+0x34:  zapnot  v0,#0xf,a0  v0=0x7,a0=0x6
  db 
  db trace
  Debugger() at Debugger+0x34
  panic() at panic+0x188
  witness_lock() at witness_lock+0xb4
  _mtx_lock_flags() at _mtx_lock_flags+0xd8
  trap() at trap+0x4c8
  XentMM() at XentMM+0x2c
  --- memory management fault (from ipl 7) ---
  statclock_process() at statclock_process+0x1d4
 
 We did something stupid like dereference a NULL pointer here.  Can you pull up
 gdb on kernel.debug and do 'l *statclock_process+0x1d4'?

Thanks to Drew for confirming that -current's gdb is hosed. Using the
-stable gdb I get better results.

Anyway:

(kgdb) l *statclock_process+0x1d4
0xfc3d1ed4 is in statclock_process (../../../kern/kern_clock.c:447).
442
443 /* Update resource usage integrals and maximums. */
444 if ((pstats = p-p_stats) != NULL 
445 (ru = pstats-p_ru) != NULL 
446 (vm = p-p_vmspace) != NULL) {
447 ru-ru_ixrss += pgtok(vm-vm_tsize);
448 ru-ru_idrss += pgtok(vm-vm_dsize);
449 ru-ru_isrss += pgtok(vm-vm_ssize);
450 rss = pgtok(vmspace_resident_count(vm));
451 if (ru-ru_maxrss  rss)
(kgdb) 

 
  XentMM() at XentMM+0x2c
  --- memory management fault ---
  ithread_schedule() at ithread_schedule+0xa4
 
 Eww, we have another one here.

(kgdb) l *ithread_schedule+0xa4
0xfc3e2924 is in ithread_schedule (../../../kern/kern_intr.c:375).
370 random_harvest(entropy, sizeof(entropy), 2, 0,
371 RANDOM_INTERRUPT);
372 }
373
374 td = ithread-it_td;
375 p = td-td_proc;
376 KASSERT(p != NULL, (ithread %s has no process,
ithread-it_name));
377 CTR4(KTR_INTR, %s: pid %d: (%s) need = %d, __func__,
p-p_pid, p-p_comm,
378 ithread-it_need);
379
(kgdb) 


  alpha_dispatch_intr() at alpha_dispatch_intr+0x130
  interrupt() at interrupt+0x138
  XentInt() at XentInt+0x28
  --- interrupt (from ipl 0) ---
  critical_exit() at critical_exit+0x1c
  _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0xd4
  vm_fault1() at vm_fault1+0x110c
  vm_fault() at vm_fault+0x64
  trap() at trap+0x6d8
  XentMM() at XentMM+0x2c
  --- memory management fault ---
  pmap_enter_quick() at pmap_enter_quick+0x1d4
 
 Ugh, this is probably the real bug. :(  Can you do a list on this address?

(kgdb) l *pmap_enter_quick+0x1d4
0xfc52c314 is in pmap_enter_quick
(../../../alpha/alpha/pmap.c:2422).
2417pmap_insert_entry(pmap, va, mpte, m);
2418
2419/*
2420 * Increment counters
2421 */
2422pmap-pm_stats.resident_count++;
2423
2424/*
2425 * Now validate mapping with RO protection
2426 */
(kgdb) 

I hope this makes sense. I still hope to catch a dump. Or
alternatively I hope it get's caught by ddb.

W/
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



blockable sleep panic on Alpha / current

2002-03-04 Thread Wilko Bulte

During a make release I just got a panic. The build progressed until:

gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxabs.3  imaxabs.3.gz
gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxdiv.3  imaxdiv.3.gz
gzip -cn /usr/src/lib/libc/../libc/stdlib/labs.3  labs.3.gz

The running system is a -current as of today.

The panic:

login: 
FreeBSD/alpha (ds10.wbnet) (ttyd0)

login: panic: blockable sleep lock (sleep mutex) Giant @
../../../alpha/alpha/tr
ap.c:482
cpuid = 0; panic
Stopped at  Debugger+0x34:  zapnot  v0,#0xf,a0  v0=0x7,a0=0x6
db 
db trace
Debugger() at Debugger+0x34
panic() at panic+0x188
witness_lock() at witness_lock+0xb4
_mtx_lock_flags() at _mtx_lock_flags+0xd8
trap() at trap+0x4c8
XentMM() at XentMM+0x2c
--- memory management fault (from ipl 7) ---
statclock_process() at statclock_process+0x1d4
statclock() at statclock+0x78
alpha_clock_interrupt() at alpha_clock_interrupt+0xac
interrupt() at interrupt+0xb8
XentInt() at XentInt+0x28
--- interrupt (from ipl 4) ---
critical_exit() at critical_exit+0x1c
_mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0xd4
witness_lock() at witness_lock+0x408
_mtx_lock_flags() at _mtx_lock_flags+0xd8
lockmgr() at lockmgr+0x70
vm_map_lock_read() at vm_map_lock_read+0x28
vm_map_lookup() at vm_map_lookup+0x78
vm_fault1() at vm_fault1+0xa8
vm_fault() at vm_fault+0x64
trap() at trap+0x6d8
XentMM() at XentMM+0x2c
--- memory management fault ---
ithread_schedule() at ithread_schedule+0xa4
alpha_dispatch_intr() at alpha_dispatch_intr+0x130
interrupt() at interrupt+0x138
XentInt() at XentInt+0x28
--- interrupt (from ipl 0) ---
critical_exit() at critical_exit+0x1c
_mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0xd4
vm_fault1() at vm_fault1+0x110c
vm_fault() at vm_fault+0x64
trap() at trap+0x6d8
XentMM() at XentMM+0x2c
--- memory management fault ---
pmap_enter_quick() at pmap_enter_quick+0x1d4
pmap_object_init_pt() at pmap_object_init_pt+0x1a4
vm_map_insert() at vm_map_insert+0x35c
elf_load_section() at elf_load_section+0x190
exec_elf_imgact() at exec_elf_imgact+0x278
execve() at execve+0x324
syscall() at syscall+0x338
XentSys() at XentSys+0x64
--- syscall (59, FreeBSD ELF, execve) ---
--- user mode ---
db 


-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: blockable sleep panic on Alpha / current

2002-03-04 Thread Wilko Bulte

On Mon, Mar 04, 2002 at 07:13:03PM +0100, Wilko Bulte wrote:

Another one, appears to be identical. No dump, no kernel debugger
unfortunately. The kernel has WITNESS enabled too. I'll try to catch a dump
if that is helpful to someone?

Wilko



FreeBSD/alpha (ds10.wbnet) (ttyd0)

login: panic: blockable sleep lock (sleep mutex) Giant @
../../../alpha/alpha/tr
ap.c:482
cpuid = 0; panic
Stopped at
fatal kernel trap:

trap entry = 0x2 (memory management fault)
cpuid  = 0
faulting va= 0x60
type   = access violation
cause  = load instructon
pc = 0xfc50b220
ra = 0xfc50b218
sp = 0xfe000e22c450
usp= 0x11fff0a8
curthread  = 0xfe000e107d00
pid = 44138, comm = cc

  Stopped at
fatal kernel trap:

trap entry = 0x2 (memory management fault)
cpuid  = 0
faulting va= 0x60
type   = access violation
cause  = load instructon
pc = 0xfc50b220
ra = 0xfc50b218
sp = 0xfe000e22b9c8
usp= 0x11fff0a8
curthread  = 0xfe000e107d00
pid = 44138, comm = cc

  Stopped at
fatal kernel trap:

trap entry = 0x2 (memory management fault)
cpuid  = 0
faulting va= 0x60
type   = access violation
cause  = load instructon
pc = 0xfc50b220
ra = 0xfc50b218
sp = 0xfe000e22af40
usp= 0x11fff0a8
curthread  = 0xfe000e107d00
pid = 44138, comm = cc

  Stopped at
halted CPU 0

halt code = 2
kernel stack not valid halt
PC = fc4231ec




 During a make release I just got a panic. The build progressed until:
 
 gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxabs.3  imaxabs.3.gz
 gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxdiv.3  imaxdiv.3.gz
 gzip -cn /usr/src/lib/libc/../libc/stdlib/labs.3  labs.3.gz
 
 The running system is a -current as of today.
 
 The panic:
 
 login: 
 FreeBSD/alpha (ds10.wbnet) (ttyd0)
 
 login: panic: blockable sleep lock (sleep mutex) Giant @
 ../../../alpha/alpha/tr
 ap.c:482
 cpuid = 0; panic
 Stopped at  Debugger+0x34:  zapnot  v0,#0xf,a0  v0=0x7,a0=0x6
 db 
 db trace
 Debugger() at Debugger+0x34
 panic() at panic+0x188
 witness_lock() at witness_lock+0xb4
 _mtx_lock_flags() at _mtx_lock_flags+0xd8
 trap() at trap+0x4c8
 XentMM() at XentMM+0x2c
 --- memory management fault (from ipl 7) ---
 statclock_process() at statclock_process+0x1d4
 statclock() at statclock+0x78
 alpha_clock_interrupt() at alpha_clock_interrupt+0xac
 interrupt() at interrupt+0xb8
 XentInt() at XentInt+0x28
 --- interrupt (from ipl 4) ---
 critical_exit() at critical_exit+0x1c
 _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0xd4
 witness_lock() at witness_lock+0x408
 _mtx_lock_flags() at _mtx_lock_flags+0xd8
 lockmgr() at lockmgr+0x70
 vm_map_lock_read() at vm_map_lock_read+0x28
 vm_map_lookup() at vm_map_lookup+0x78
 vm_fault1() at vm_fault1+0xa8
 vm_fault() at vm_fault+0x64
 trap() at trap+0x6d8
 XentMM() at XentMM+0x2c
 --- memory management fault ---
 ithread_schedule() at ithread_schedule+0xa4
 alpha_dispatch_intr() at alpha_dispatch_intr+0x130
 interrupt() at interrupt+0x138
 XentInt() at XentInt+0x28
 --- interrupt (from ipl 0) ---
 critical_exit() at critical_exit+0x1c
 _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0xd4
 vm_fault1() at vm_fault1+0x110c
 vm_fault() at vm_fault+0x64
 trap() at trap+0x6d8
 XentMM() at XentMM+0x2c
 --- memory management fault ---
 pmap_enter_quick() at pmap_enter_quick+0x1d4
 pmap_object_init_pt() at pmap_object_init_pt+0x1a4
 vm_map_insert() at vm_map_insert+0x35c
 elf_load_section() at elf_load_section+0x190
 exec_elf_imgact() at exec_elf_imgact+0x278
 execve() at execve+0x324
 syscall() at syscall+0x338
 XentSys() at XentSys+0x64
 --- syscall (59, FreeBSD ELF, execve) ---
 --- user mode ---
 db 
 
 
 -- 
 |   / o / /_  _   [EMAIL PROTECTED]
 |/|/ / / /(  (_)  Bulte   Arnhem, the Netherlands
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ FreeBSD core team secretary
|/|/ / / /(  (_)  Bulte [EMAIL PROTECTED]

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



Re: Performance of -current vs -stable

2002-02-11 Thread Wilko Bulte

On Thu, Feb 07, 2002 at 10:15:02AM +0100, Cejka Rudolf wrote:
 Garance A Drosihn wrote (2002/02/06):
  Anything else I should check?  I realize there's about a million
  differences between the two branches, and there might also be
  something about my machine's setup which is a major culprit here.
  I'm just looking for a basic idea of what other people have been
  seeing for performance when they run current.
 
 There is another common source of confusion: If anybody has IDE
 disks, write-caching is enabled by default in -stable, but disabled
 in -current.

I don't think that is true anymore. -stable has WC enabled as well.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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: How about gcj? (Re: Not committing WARNS settings...)

2002-02-11 Thread Wilko Bulte

On Thu, Feb 07, 2002 at 10:35:41AM -0800, David O'Brien wrote:
 On Thu, Feb 07, 2002 at 07:29:57PM +0100, Wilko Bulte wrote:
  - is GCC3 also better on Alpha as far as correctness of the generated
code goes? Or is that what you mean by bad optimised code ?
 
 We shall see.

OK. 8-)

  - The gcc 2.95 compiler is quite a bit slower (it appears) on Alpha than
on x86. Do you have any idea how gcc3 does in this respect?
 
 3.1 will also be slower on the Alpha.  It is really an issue of the code
 generator.  Generating x86 code on an Alpha is faster than generating
 [native] Alpha code.  The Alpha code generator is slow.  It may be that
 all 64 bit or RISC GCC code generation is slow -- we will see soon for
 the sparc64.

Thanks. So it is the code generator itself, I always thought it would be
the optimiser that needs more time to do a decent job on a RISC.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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: Non 386 testers REALLY NEEDED

2002-02-11 Thread Wilko Bulte

On Wed, Feb 06, 2002 at 12:32:18PM -0800, Alfred Perlstein wrote:
 * Julian Elischer [EMAIL PROTECTED] [020206 12:20] wrote:
  
  for the set of patches at:
  http://www.freebsd.org/~julian/adiff
  
  these patches SHOULD NOT EFFECT your system except to do some
  slight re-aranging of stuff in the kernel.
  
  THe aim is to get this committed to 'clarify' the upcoming
  KSE commit in http://www.freebsd.org/~julian/thediff
  
  which includes adiff as a subset.
  
  when adiff is committed thediff will become a lot easier for people to 
  read and check. I'd like to get adiff in relatively soon.
 
 I commend you on your wait for testers, but I find that after a couple
 of days of waiting for them to appear and give decent feedback usually
 just committing the code will bring out a horde of involentary testers
 which actually gets the code stabilized.
 
 This is current, we're allowed some breakage.  Cross your I's and dot
 your T's first though. :-)

C'mon guys: it is not so long ago (days..) that the Alpha started
buildworlding -current again. Alpha builds tend to take much
longer (on most people's hardware that is) so a bit of patience
would be nice.

FWIW: I'm trying to get 2 of my Alphas to go to -current again.

W/
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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: Performance of -current vs -stable

2002-02-07 Thread Wilko Bulte

On Thu, Feb 07, 2002 at 10:15:02AM +0100, Cejka Rudolf wrote:
 Garance A Drosihn wrote (2002/02/06):
  Anything else I should check?  I realize there's about a million
  differences between the two branches, and there might also be
  something about my machine's setup which is a major culprit here.
  I'm just looking for a basic idea of what other people have been
  seeing for performance when they run current.
 
 There is another common source of confusion: If anybody has IDE
 disks, write-caching is enabled by default in -stable, but disabled
 in -current.

I don't think that is true anymore. -stable has WC enabled as well.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: How about gcj? (Re: Not committing WARNS settings...)

2002-02-07 Thread Wilko Bulte

On Thu, Feb 07, 2002 at 10:11:33AM -0800, David O'Brien wrote:
 On Thu, Feb 07, 2002 at 12:39:35AM -0500, Mikhail Teterin wrote:
  I believe,  what I see.  And that is, FreeBSD  includes both --  gdb and
  gcc, but only one libbfd, thankfully. And  I want to be able to use that
  same libbfd  for my own development  and for porting of  other compilers
  and tools.

...
 
 Sure some things are a problem.  GCC 2.95 generates bad optimized code on
 the Alpha.  Upgrading to 3.1 will fix [some of] this.  We cannot do a

To satisfy a bit of my curiosity:

- is GCC3 also better on Alpha as far as correctness of the generated
  code goes? Or is that what you mean by bad optimised code ?

- The gcc 2.95 compiler is quite a bit slower (it appears) on Alpha than
  on x86. Do you have any idea how gcc3 does in this respect?

Thanks!
Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: How about gcj? (Re: Not committing WARNS settings...)

2002-02-07 Thread Wilko Bulte

On Thu, Feb 07, 2002 at 10:35:41AM -0800, David O'Brien wrote:
 On Thu, Feb 07, 2002 at 07:29:57PM +0100, Wilko Bulte wrote:
  - is GCC3 also better on Alpha as far as correctness of the generated
code goes? Or is that what you mean by bad optimised code ?
 
 We shall see.

OK. 8-)

  - The gcc 2.95 compiler is quite a bit slower (it appears) on Alpha than
on x86. Do you have any idea how gcc3 does in this respect?
 
 3.1 will also be slower on the Alpha.  It is really an issue of the code
 generator.  Generating x86 code on an Alpha is faster than generating
 [native] Alpha code.  The Alpha code generator is slow.  It may be that
 all 64 bit or RISC GCC code generation is slow -- we will see soon for
 the sparc64.

Thanks. So it is the code generator itself, I always thought it would be
the optimiser that needs more time to do a decent job on a RISC.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Non 386 testers REALLY NEEDED

2002-02-07 Thread Wilko Bulte

On Thu, Feb 07, 2002 at 04:28:03PM -0500, Andrew Gallatin wrote:
 
 Julian Elischer writes:
   
   
   I've committed both the kernel diff and a libkvm diff that seems to work
   for me here.
   
   can you check it with the new -current  again ?
   
 
 I'll build a kernel  I'll be happy to try a buildworld under it.
 But from what I understand, the new binutils is broken and alpha
 binaries built with it segv, so I don't really want to install
 whatever I build :-(

No you don't. I did accidentally. Don't :(

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Non 386 testers REALLY NEEDED

2002-02-06 Thread Wilko Bulte

On Wed, Feb 06, 2002 at 12:32:18PM -0800, Alfred Perlstein wrote:
 * Julian Elischer [EMAIL PROTECTED] [020206 12:20] wrote:
  
  for the set of patches at:
  http://www.freebsd.org/~julian/adiff
  
  these patches SHOULD NOT EFFECT your system except to do some
  slight re-aranging of stuff in the kernel.
  
  THe aim is to get this committed to 'clarify' the upcoming
  KSE commit in http://www.freebsd.org/~julian/thediff
  
  which includes adiff as a subset.
  
  when adiff is committed thediff will become a lot easier for people to 
  read and check. I'd like to get adiff in relatively soon.
 
 I commend you on your wait for testers, but I find that after a couple
 of days of waiting for them to appear and give decent feedback usually
 just committing the code will bring out a horde of involentary testers
 which actually gets the code stabilized.
 
 This is current, we're allowed some breakage.  Cross your I's and dot
 your T's first though. :-)

C'mon guys: it is not so long ago (days..) that the Alpha started
buildworlding -current again. Alpha builds tend to take much
longer (on most people's hardware that is) so a bit of patience
would be nice.

FWIW: I'm trying to get 2 of my Alphas to go to -current again.

W/
-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Non 386 testers REALLY NEEDED

2002-02-06 Thread Wilko Bulte

On Wed, Feb 06, 2002 at 06:20:16PM -0500, Mike Barcroft wrote:
 Wilko Bulte [EMAIL PROTECTED] writes:
  C'mon guys: it is not so long ago (days..) that the Alpha started
  buildworlding -current again. Alpha builds tend to take much
  longer (on most people's hardware that is) so a bit of patience
  would be nice.
  
  FWIW: I'm trying to get 2 of my Alphas to go to -current again.
 
 Running most things compiled with the new binutils on Alpha causes
 segfaults.  Be very careful not to install anything compiled with it.

Thanks... it apparantly wasn't my cockpit error then yesterday
nite.. I had to reinstall one of the Alphas to get anything running again.

 To test KSE on Alpha I recommend locally backing out the new binutils
 until David or another developer resolves the issues with it.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: Latest binutils import breaks Alpha cross compiles

2002-02-04 Thread Wilko Bulte

On Mon, Feb 04, 2002 at 09:06:56AM -0800, David O'Brien wrote:
 On Mon, Feb 04, 2002 at 06:43:23PM +0200, Ruslan Ermilov wrote:
  The fix was as simple as this:
 
 Thanks!!  Committed.

Great! /me fires up the DS10..

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



  1   2   3   4   >