Re: pci configuration

2003-08-14 Thread Scott Long
Doug White wrote:
On Tue, 12 Aug 2003, Petri Helenius wrote:


Is there way to view PCI / PCI-X configuration with bus-width and clock
values when FreeBSD has already booted?


If you know where in PCI config space to look you could use pciconf to
query it.  Can't say I've heard of PCI speed negotiation issues, though.
I'm not aware of any registers in the standard PCI config space that
will tell you the speed of the bus.  Some PCI devices will make that
information available, but not in a standard way.  The BIOS of some
higher-end systems might also tell you this information.
Scott

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


Re: usbd does not use detach

2003-08-14 Thread Daniel O'Connor
On Friday 15 August 2003 00:31, Eric Jacobs wrote:
  example: my digital photo recorder.
  i have an attach script to mount automatically the partition on the
  cooresponding umass/da device. works great, and this helps.
 
  but when detaching, the umount part should be done BEFORE detaching, not
  after. i can't find any good use for the detach hook. most of things
  should have been done before detaching, and i can't see how to do it
  without user interactivity, thus avoiding use of the detach hook.

 The problem with this is that the system will be asking the FS to
 e.g. flush buffers to a disk which it knows doesn't exist anymore, which
 is an error (and will cause errors).

It should also have a hint to indicate that this device could potentially go 
away at any time, so it shouldn't cache anything if at all possible.
(Although it would be good if the user could elect to override this in the 
interests of performance)

I suspect that would require more significant changes though :)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140  AE4B 319B 41F4 5D17 FDD5

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


Re: TESTERS WANTED for ATAng preview 1

2003-08-14 Thread Soeren Schmidt
It seems Gavin Atkinson wrote:
 On Wed, 13 Aug 2003, Soeren Schmidt wrote:
  It seems Gavin Atkinson wrote:
   With the new ATA code, the boot now hangs. I now get on a verbose bootup:
   ata1-master: FAILURE - ATAPI_IDENTIFY status=1ERROR error=0
 
  Okies, what if you make that CDROM a slave ?
 
 That seems to work fine:
 
 ata1: spurious interrupt - status=0x7f error=0x7f reason=0x7f
 ad0: 19881MB Maxtor 6E020L0 [40395/16/63] at ata0-master UDMA100
 acd0: CDROM SAMSUNG CD-ROM SC-152A at ata1-slave PIO4

OK, your CDROM doesn't like to be a sole master it appears...

-Søren
___
[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 Lukas Ertl
On Wed, 13 Aug 2003, Soeren Schmidt wrote:

  *) ata(4) - what are the supported UDMA levels for SiS 652, 751, and 752?

  { ATA_SIS652,  0x00, SIS_SOUTH, 0, ATA_UDMA6, SiS 652 }
  { ATA_SIS751,  0x00, SIS_SOUTH, 0, ATA_UDMA6, SiS 751 }
  { ATA_SIS752,  0x00, SIS_SOUTH, 0, ATA_UDMA6, SiS 752 }

 Or so it seems, it depends on the southbridge on the board, so this is
 the max, but depending on the actual HW it can be UDMA5.

Thanks, Soren.

 The ATA driver is in violent flux currently, but I will update the
 man page when I'm done with the changes..

So would you like to handle docs/55512 yourself?

regards,
le

-- 
Lukas Ertl eMail: [EMAIL PROTECTED]
UNIX Systemadministrator   Tel.:  (+43 1) 4277-14073
Vienna University Computer Center  Fax.:  (+43 1) 4277-9140
University of Vienna   http://mailbox.univie.ac.at/~le/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...

2003-08-14 Thread Stephane Raimbault
Hi Brooks,

I'm curious, what should that option be set to if one does have an SMP
kernel running on 2x 2.4Ghz Xeon Processors (Hyper thread enabled)

Mine is currently set to
machdep.hlt_logical_cpus: 1

Thanks,
Stephane.

- Original Message - 
From: Brooks Davis [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Tuesday, August 12, 2003 4:47 PM
Subject: Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...



 --ZGiS0Q5IWpPtfppv
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Tue, Aug 12, 2003 at 03:38:29PM -0700, Scott M. Likens wrote:
  Well friend of mine just landed a Dual P4 2.4Ghz Xeon with
  Hyperthreading Enabled, and yet I know there's a hyperthreading option
  in 4.8-RELEASE but I don't see one at ALL in 5.1?
 =20
  am I suddenly blind or do I need to cvsup to CURRENT to take proper
  advantage?

 There is no option in current.  Instead, you use the sysctl
 machdep.hlt_logical_cpus to indicate if you want to use the logical
 cpus.

 -- Brooks

 --=20
 Any statement of the form X is the one, true Y is FALSE.
 PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

 --ZGiS0Q5IWpPtfppv
 Content-Type: application/pgp-signature
 Content-Disposition: inline

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.2.1 (GNU/Linux)

 iD8DBQE/OW0AXY6L6fI4GtQRAoQkAKDLc4zkeRBxI1mhNpkJnXpHjEQzAgCg1Uo1
 Qq/MJ7h24hr69yLQaaJHsD4=
 =ydl2
 -END PGP SIGNATURE-

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


dell d800 hints?

2003-08-14 Thread Dr. Richard E. Hawkins
I thought I saw during my searching that a couple of other people have
dell Latitude D800 laptops.  Are there any compiled pages of hints?  or
is there a pile that I should toss together on a webpage?

I have it working, with X and network.  I don't have the modem working
(someone would need to write the glue for the linux kernel driver),
sound is erratic (sometimes works after cold boot, sometimes not), and I
don't have the acpi working (in fact, I don't even understand what the
posts are saying :)

Anyway, if people will send the bits and pieces of advice that should be
had for this model, I'll toss them into a page like the one I have for
the Thinkpad A21p.

(I'm assuming that this model still only works with -CURRENT due to the
network card).

hawk

-- 
Richard E. Hawkins, Asst. Prof. of Economics/\   ASCII ribbon campaign
[EMAIL PROTECTED]  Smeal 178  (814) 375-4700  \ /   against HTML mail
These opinions will not be those of  Xand postings. 
Penn State until it pays my retainer.   / \   
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: panic while browsing with Opera 7

2003-08-14 Thread Arjan van Leeuwen
On Wednesday 13 August 2003 14:12, Karel J. Bosschaart wrote:
 Hi,

 Using PR/55509 I installed (native) Opera 7.2B3 on my -current as
 of 2 days ago.  I had 3 panics in only a couple of hours while using
 Opera 7: 2 times with a GENERIC kernel, 1 time with a custom kernel.
 They all look similar:


snap

I can't reproduce this. Is there some special action you do in Opera to 
trigger the panic?

Arjan

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


Re: TESTERS WANTED for ATAng preview 1

2003-08-14 Thread David Leimbach
I am rather naive on the topic but don't many drives have a single 
drive jumper
which works better than a master with no slave at times?
On Wednesday, August 13, 2003, at 5:43 AM, Gavin Atkinson wrote:

On Wed, 13 Aug 2003, Soeren Schmidt wrote:
It seems Gavin Atkinson wrote:
ata1: spurious interrupt - status=0x7f error=0x7f reason=0x7f
ad0: 19881MB Maxtor 6E020L0 [40395/16/63] at ata0-master UDMA100
acd0: CDROM SAMSUNG CD-ROM SC-152A at ata1-slave PIO4
OK, your CDROM doesn't like to be a sole master it appears...
I hate it when people respond with this, but I'm going to join them and
say It works under Windows... Also, under the new code, this problem
prevents the booting of the machine, but under the old code the machine
carries on booting after giving up on the drive.
Is it possible for this failure mode to not prevent the booting of the
machine at least?
Gavin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: TESTERS WANTED for ATAng preview 1

2003-08-14 Thread Gavin Atkinson
On Fri, 8 Aug 2003, Soeren Schmidt wrote:
 ftp://ftp.deepcore.dk/pub/ATAng
 Before these rather radical changes to the ATA driver hits the
 tree, here is the opportunity to test them out, give usefull
 feedback and for the depending subsytems to adjust to the new
 ways of things (burncd  atapicam are good examples).

Hi,

I'm using ATAng-20030809-1.tgz on top-of-tree current on hardware detected
with the old ATA code as:

atapci0: Intel ICH5 UDMA100 controller port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at 
device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
atapci1: Intel ICH5 SATA150 controller port 
0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 10 at device 
31.2 on pci0
ata2: at 0xec00 on atapci1
ata3: at 0xe400 on atapci1
ata1-master: timeout waiting for interrupt
ata1-master: ATAPI identify failed
ad0: 19881MB Maxtor 6E020L0 [40395/16/63] at ata0-master UDMA100

(ata1-master is a CD-ROM drive, and freebsd has been unable to detect it
since I installed FreeBSD onto this machine about two weeks ago).

With the new ATA code, the boot now hangs. I now get on a verbose bootup:

ata1-master: FAILURE - ATAPI_IDENTIFY timeout
ata1: resetting devices ..
ata1: pre reset mask=03 ostat0=58 ostat2=00
ata1-master: ATAPI 14 EB
ata1-slave: ATAPI 7F 7F
ata1: after reset mask=03 stat0=10 stat1=00
ata1: devices=04
ata1-master: FAILURE - ATAPI_IDENTIFY status=1ERROR error=0

hang here

db tr 0
mi_switch(...)
msleep(...)
ata_queue_request(...)
ata_getparam(...)
ata_identify_devices(...)
ata_boot_attach(...)

Unplugging the CD-ROM drive allows the machine to boot normally.

Once booted, I keep seeing these messages relating to the S-ATA controller
(which has no devices plugged into it):

ata2: spurious interrupt - status=0x7f error=0xff reason=0xff
ata3: spurious interrupt - status=0x7f error=0xff reason=0xff

These are also new with the new ATA code.

Hope that all helps, I can test any patches necessary.

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


panic: ffs_freefile: freeing free inode

2003-08-14 Thread Morten Rodal
I got a panic (and of course the usual panic on sync panic) when my
machine was just sitting more or less idle in X.  The kernel is 

  FreeBSD 5.1-CURRENT (slurp) #0: Mon Aug 11 21:01:38 CEST 2003

and the machine is a dual Pentium II with only a minimal kernel (i.e.
stripped GENERIC).

-- 
Morten Rodal

User: Pretend not to be crazy.
jabberwacky: I cannot do that.
-- www.chatterboxchallenge.com
Script started on Wed Aug 13 13:53:36 2003
slurp# gdb -k kernel.8 vmcore.8
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 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-undermydesk-freebsd...
panic: ffs_freefile: freeing free inode
panic messages:
---
panic: ffs_freefile: freeing free inode
cpuid = 0; lapic.id = 0100
Stack backtrace:
boot() called on cpu#0

syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
cpuid = 0; lapic.id = 0100
boot() called on cpu#0
Uptime: 2h13m50s
Dumping 447 MB
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 
384 400 416 432
---
Reading symbols from 
/usr/obj/usr/src/sys/slurp/modules/usr/src/sys/modules/linux/linux.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/slurp/modules/usr/src/sys/modules/linux/linux.ko.debug
Reading symbols from /boot/kernel/snd_sb16.ko...done.
Loaded symbols for /boot/kernel/snd_sb16.ko
Reading symbols from /boot/kernel/snd_sbc.ko...done.
Loaded symbols for /boot/kernel/snd_sbc.ko
Reading symbols from /boot/kernel/snd_pcm.ko...done.
Loaded symbols for /boot/kernel/snd_pcm.ko
Reading symbols from /boot/kernel/nvidia.ko...done.
Loaded symbols for /boot/kernel/nvidia.ko
Reading symbols from 
/usr/obj/usr/src/sys/slurp/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/slurp/modules/usr/src/sys/modules/acpi/acpi.ko.debug
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1  0xc01e3ec6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2  0xc01e4318 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc022d541 in bremfreel (bp=0xcca759e0) at /usr/src/sys/kern/vfs_bio.c:644
#4  0xc022d44b in bremfree (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:626
#5  0xc0238938 in vop_stdfsync (ap=0xd59e1a98)
at /usr/src/sys/kern/vfs_default.c:740
#6  0xc01a8870 in spec_fsync (ap=0xd59e1a98)
at /usr/src/sys/fs/specfs/spec_vnops.c:417
#7  0xc01a7c68 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:122
#8  0xc02c1a11 in ffs_sync (mp=0xc3a2e000, waitfor=2, cred=0xc1378e80, 
td=0xc03adb20) at vnode_if.h:627
#9  0xc024686b in sync (td=0xc03adb20, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:142
#10 0xc01e39cf in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:281
#11 0xc01e4318 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#12 0xc02a9198 in ffs_freefile (fs=0xc39a9000, devvp=0xc3ad5000, ino=3, 
mode=17407) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1917
#13 0xc02ba8f4 in handle_workitem_freefile (freefile=0xc411b000)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3401
#14 0xc02b6178 in process_worklist_item (matchmnt=0x0, flags=0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:778
#15 0xc02b5e00 in softdep_process_worklist (matchmnt=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:622
#16 0xc02421c6 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1786
#17 0xc01cc8e1 in fork_exit (callout=0xc0241d90 sched_sync, arg=0x0, 
frame=0x0) at /usr/src/sys/kern/kern_fork.c:790
(kgdb) up 12
#12 0xc02a9198 in ffs_freefile (fs=0xc39a9000, devvp=0xc3ad5000, ino=3, 
mode=17407) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1917
1917panic(ffs_freefile: freeing free inode);
(kgdb) p *fs
$1 = {fs_firstfield = 0, fs_unused_1 = 0, fs_sblkno = 8, fs_cblkno = 16, 
  fs_iblkno = 24, fs_dblkno = 1496, fs_old_cgoffset = 0, fs_old_cgmask = -1, 
  fs_old_time = 1060763786, fs_old_size = 5816260, fs_old_dsize = 5723995, 
  fs_ncg = 62, fs_bsize = 16384, fs_fsize = 2048, fs_frag = 8, fs_minfree = 8, 
  fs_old_rotdelay = 0, fs_old_rps = 60, fs_bmask = -16384, fs_fmask = -2048, 
  fs_bshift = 14, fs_fshift = 11, fs_maxcontig = 8, fs_maxbpg = 2048, 
  fs_fragshift = 3, fs_fsbtodb = 2, fs_sbsize = 2048, fs_spare1 = {0, 0}, 
  fs_nindir = 4096, fs_inopb = 128, fs_old_nspf = 4, fs_optim = 0, 
  fs_old_npsect = 376192, fs_old_interleave = 1, fs_old_trackskew = 0, 
  fs_id = {1042989277, 433616384}, fs_old_csaddr = 1496, fs_cssize = 2048, 
  fs_cgsize = 16384, fs_spare2 = 0, fs_old_nsect = 376192, 
  fs_old_spc = 376192, fs_old_ncyl = 62, fs_old_cpg = 1, fs_ipg = 23552, 
  fs_fpg = 94048, fs_old_cstotal = {cs_ndir = 570, cs_nbfree = 

Re: driver maintainers, please help

2003-08-14 Thread Soeren Schmidt
It seems Lukas Ertl wrote:
 Hi there,
 
 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, and I'm currently trying to
 update those manpages.  Unfortunately, for some devices (especially older
 ones) I'd need some info that I just can't find on the web, so I hope some
 of the maintainers or authors can give me a hint (and of course anyone
 else who knows).
 
 What I would like to know so far:
 
 *) ata(4) - what are the supported UDMA levels for SiS 652, 751, and 752?

 { ATA_SIS652,  0x00, SIS_SOUTH, 0, ATA_UDMA6, SiS 652 }
 { ATA_SIS751,  0x00, SIS_SOUTH, 0, ATA_UDMA6, SiS 751 }
 { ATA_SIS752,  0x00, SIS_SOUTH, 0, ATA_UDMA6, SiS 752 }

Or so it seems, it depends on the southbridge on the board, so this is
the max, but depending on the actual HW it can be UDMA5.

 Of course, it would be very helpful here if the driver maintainers could
 have a look at their manpages and compare them to the Hardware Notes and
 catch up with what isn't in the respective man page.

The ATA driver is in violent flux currently, but I will update the
man page when I'm done with the changes..

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


Re: pci configuration

2003-08-14 Thread Petri Helenius


 On Tue, 12 Aug 2003, Petri Helenius wrote:

  Is there way to view PCI / PCI-X configuration with bus-width and clock
  values when FreeBSD has already booted?

 If you know where in PCI config space to look you could use pciconf to
 query it.  Can't say I've heard of PCI speed negotiation issues, though.

I haven´t exactly had issues but every now and then somebody puts in
a 32/33 card into a bus which is shared with motherboard components
effectively killing performance. At this time, if I understand correctly, there
is no instrumentation in the OS to figure out what´s going on, so physical
inspection is neccessary instead of just making a piece of software beep
to the IT monkey to go and pull the junk out.

Pete

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


Re: Crash in g_dev_strategy / CURRENT as of yesterday.

2003-08-14 Thread Larry Rosenman


--On Tuesday, August 12, 2003 21:39:34 +0200 Poul-Henning Kamp 
[EMAIL PROTECTED] wrote:

In message [EMAIL PROTECTED], Eivind Olsen writes:
--On 12. august 2003 21:26 +0200 Poul-Henning Kamp [EMAIL PROTECTED]
wrote:
In message [EMAIL PROTECTED], Eivind Olsen writes:
Hello. Some of you might have seen my previous mailings regarding
crashes  in g_dev_strategy under FreeBSD 5.1 (RELENG_5_1). I have now
upgraded to  CURRENT (cvsupped, compiled and installed yesterday) and I
still see  similar  crashes (but not identical crashes, I can't see any
mention of  Vinum here).
# 12 0xc030697e in spec_xstrategy (vp=0xc1fa9cc0, bp=0x0) at
/usr/src/sys/fs/specfs/spec_vnops.c:512
This is the call into the device driver.  Do you have any idea which
driver this might be ?  Can you try to print out the bp-b_dev structure
if you still have the dump ?
I still have the dump. Please tell me exactly which commands I should
use  and I'll take a look. I'm not a kernel hacker so I don't know how
to get at  that information all by myself.
I'm not of a gdb wizard either, but I think you type up or down until
you are at stack frame #12, and the simply say print *bp-b_dev
fr 12

will get to that stack frame.

FWIW.





--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Bug in nss compat code?

2003-08-14 Thread James F. Hranicky
I think I've found a few bugs in the NSS code for FreeBSD 5.1 . I'm not
sure of the best way to split them up, so I'll list them all here.

FreeBSD version:
  % uname -a
  FreeBSD myrtle 5.1-CURRENT FreeBSD 5.1-CURRENT #1: 
  Mon Aug 11 17:15:47 EDT 2003 
  [EMAIL PROTECTED]:/private/freebsd-src/obj/private/freebsd-src/src/sys/CISEKERN
  i386

 1) getnetgrent still seems to ignore the NIS netgroup maps and only uses
/etc/netgroup. A '+' as the only entry in /etc/netgroup does not force
an NIS netgroup map lookup. This bug has been reported in the 4.x tree
as well.

 2) There's an odd bug in sshd/nss when the following are configured:

- nsswitch.conf
passwd: compat

- sshd_config
ChallengeResponseAuthentication yes (default)
HostbasedAuthentication yes

When /etc/netgroup doesn't exist, the sshd hangs when logging in with
HostbasedAuthentication:

[EMAIL PROTECTED]:~ # gdb /usr/sbin/sshd
GNU gdb 5.2.1 (FreeBSD)
(gdb) run -d -p 987

[ some debugging output deleted for readability]

debug1: KEX done
debug1: userauth-request for user jfh service ssh-connection method none
debug1: attempt 0 failures 0
debug1: PAM: initializing for jfh
debug1: PAM: setting PAM_RHOST to waterspout.cise.ufl.edu
Failed none for jfh from 128.227.205.52 port 47962 ssh2
Failed none for jfh from 128.227.205.52 port 47962 ssh2
debug1: userauth-request for user jfh service ssh-connection method hostbased
debug1: attempt 1 failures 1
debug1: userauth_hostbased: cuser jfh chost waterspout.cise.ufl.edu. pkalg 
ssh-dss slen 55
Failed hostbased for jfh from 128.227.205.52 port 47962 ssh2
debug1: userauth-request for user jfh service ssh-connection method hostbased
debug1: attempt 2 failures 2
debug1: userauth_hostbased: cuser jfh chost waterspout.cise.ufl.edu. pkalg 
ssh-rsa slen 143
Failed hostbased for jfh from 128.227.205.52 port 47962 ssh2
debug1: userauth-request for user jfh service ssh-connection method 
keyboard-interactive
debug1: attempt 3 failures 3
debug1: keyboard-interactive devs 
debug1: auth2_challenge: user=jfh devs=
debug1: kbdint_alloc: devices 'pam'
debug1: auth2_challenge_start: trying authentication method 'pam'
^C
Program received signal SIGINT, Interrupt.
0x282e987f in read () at {standard input}:15
15  {standard input}: No such file or directory.
in {standard input}
Current language:  auto; currently asm
(gdb) Quit
(gdb) where
#0  0x282e987f in read () at {standard input}:15
#1  0x281409ab in atomicio (f=0x5, fd=-1077940208, _s=0xbfbff038, n=674583073)
at /private/freebsd-src/src/crypto/openssh/atomicio.c:45
#2  0x281286a9 in ssh_msg_recv (fd=5, m=0xbfbff010) at 
/private/freebsd-src/src/crypto/openssh/msg.c:58
#3  0x08062bb5 in pam_query (ctx=0x807a870, name=0x7, info=0x7, 
num=0xbfbff064, prompts=0xbfbff068, 
echo_on=0xbfbff06c) at 
/private/freebsd-src/src/crypto/openssh/auth2-pam-freebsd.c:397
#4  0x0805ef2a in mm_answer_pam_query (socket=3, m=0xbfbff0a0)
at /private/freebsd-src/src/crypto/openssh/monitor.c:799
#5  0x0805e51a in monitor_read (pmonitor=0x8075580, ent=0x8070320, 
pent=0xbfbff0ec)
at /private/freebsd-src/src/crypto/openssh/monitor.c:388
#6  0x0805e208 in monitor_child_preauth (pmonitor=0x8075580)
at /private/freebsd-src/src/crypto/openssh/monitor.c:301
#7  0x0804ed1f in privsep_preauth () at 
/private/freebsd-src/src/crypto/openssh/sshd.c:605
#8  0x0805087a in main (ac=47962, av=0x807a7b0) at 
/private/freebsd-src/src/crypto/openssh/sshd.c:1523
#9  0x0804e1a2 in _start (ap=0xbfbffb24 /usr/sbin/sshd)
at /private/freebsd-src/src/lib/csu/i386-elf/crt1.c:104

With either ChallengeResponseAuthentication or HostbasedAuthentication
disabled, I'm prompted for a password. With both enabled, sshd hangs
here, and I'm never prompted for a password on the client side.

However, if /etc/netgroup does exist and is populated with netgroup info, I 
get a core dump in sshd:

(gdb) run -d -p 987
[ ... ] 
debug1: KEX done
debug1: userauth-request for user jfh service ssh-connection method none
debug1: attempt 0 failures 0
debug1: PAM: initializing for jfh
debug1: PAM: setting PAM_RHOST to waterspout.cise.ufl.edu
Failed none for jfh from 128.227.205.52 port 47968 ssh2
Failed none for jfh from 128.227.205.52 port 47968 ssh2
debug1: userauth-request for user jfh service ssh-connection method hostbased
debug1: attempt 1 failures 1
debug1: userauth_hostbased: cuser jfh chost waterspout.cise.ufl.edu. pkalg 
ssh-dss slen 

XFree86 on FreeBSD 5.1 w/ATI M9

2003-08-14 Thread Sukhjeet Singh Batth
I have an HP Compaq Presario X1000 (Model X1018CL) with an ATI Mobility
Radeon 9200 (M9 / RV250?) and a 15.4 widescreen WSXGA+ capable of
1280x800.  I installed XFree86 4.3.0 on FreeBSD 5.1 and it seems like the
only odd message I'm getting before aborting the startx is a warning about
a bad v_bios checksum.  Any ideas on how to get this to work?  I searched
around and found a post similar to mine at
http://lists.freebsd.org/pipermail/freebsd-stable/2003-April/000542.html ,
but there was no associated answer.  I had X running with Mandrake 9.1 on
the same computer, so I'm not sure what the problem may be.  Also, at
first there was a problem with not loading a certain library module.  I
just added a Load ddc in the module section of my XF86Config to fix
that unresolved symbol.

Thanks,
Sukhjeet

Attachment(s)
XFree86.0.log

XFree86.0.log
Description: Binary data
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


host/domain name verification, and valid top level domains (fwd)

2003-08-14 Thread Doug Barton
Folks,

One of the topics at the recent ICANN conference was the issue of
functionality for the new generic top level domains (gTLD's). Seven new
gTLD's were adopted by ICANN in November of 2000, but many users with
domains in those TLD's are still having problems using them.

One of the areas that is particularly relevant to us is the issue of web
forms, and other locations where user data like URL's or e-mail
addresses are verified and stored (especially C/C++ code that allocates
memory for names, etc.). In the past, all domain names ended in 2, 3, or
4 letter labels. However, now the list of valid gTLD's also contains one
with 6. The list of currently valid gTLD's is:

.aero, .biz, .com, .coop, .edu, .gov, .info, .int, .mil, .museum, .name,
.net, .org, and .pro

If you are responsible for code that deals with domain names in any way,
please run some tests to be sure that hostnames from all of these gTLD's
work with your code, and please fix anything that doesn't.

If you have any questions, please shoot them my way. If you are tempted
to reply to all, please trim your cc: list appropriately, and keep me in
there somewhere.

Hope this helps,

Doug


References:
http://www.iana.org/domain-names.htm
http://www.iana.org/cctld/cctld-whois.htm
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...

2003-08-14 Thread Brooks Davis
On Tue, Aug 12, 2003 at 05:26:42PM -0600, Stephane Raimbault wrote:
 Hi Brooks,
 
 Thanks for responding...
 
 However I'm confused by the terms used.  Are you saying if I set it to 0, I
 would be using the processing power of all CPU's?  I'm not sure how this
 halted comes in to play, cuz the only thing that comes to mind is to halt
 the machine as in shutdown  I'm probably confusing terms here... can you
 expand and clarify?  I just want to make sure what this all means.  Also is
 this an option that can be modified via sysctl -w and the /etc/sysctl.conf
 file ?  Or is this going to have to be set in a boot option?

When halted, the logical CPUs are rendered unavailable.  This is the
default.  If you want the logical CPUs to work, you see the boolean
sysctl to 0 telling the kernel to let them work.  You can set the option
any time you want.

-- Brooks


pgp0.pgp
Description: PGP signature


Re: make buildkernel hang with SCHED_ULE

2003-08-14 Thread Andrew Gallatin

Adam Migus writes:
  Folks,
  While doing some performance analysis (doing make -j5 buildkernel)
  on a set of 14 kernels I've hit one using the SCHED_ULE scheduler
  that hangs.   It happens every time but not necessarily in the same
  place in the make.
  

...

  The hardware is a dual Xeon box.  The kernel is SMP w/ SCHED_ULE
  instead of SCHED_4BSD, the options required for diskless and the
  following two options:

You have machdep.hlt_logical_cpus: 1 in your sysctl output.  [BTW,
lots of people read this mail via the web archives at
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1073654+0+current/freebsd-current,
where its impossible to view mime; it would be MUCH better for us if
appended things like stack traces and sysctl output rather then
scrambling them for no reason]

SCHED_ULE is incompatible with halting logical CPUs.  Something about
it does't know the core isn't running, so it schedules a job there
which never runs, and then it gets confused.  When I boot a 1 CPU P4
with an SMP kernel and machdep.hlt_logical_cpus=1, it hangs before
making it to multiuser mode..

Try setting machdep.hlt_logical_cpus=0 (via sysctl now, and in
/boot/loader.conf so it doesn't happen again).


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


RE: pci configuration

2003-08-14 Thread Cagle, John (ISS-Houston)
If you're using a server with the Compaq PCI-X Hot Plug controller, you
can read the maximum bus speed and current device speed from the hot
plug controller.  For details, take a look at the
drivers/pci/hotplug/cpqphp.h and drivers/pci/hotplug/cpqphp_core.c files
in the latest Linux 2.6 kernel.  Here are a couple links:

http://lxr.linux.no/source/drivers/pci/hotplug/cpqphp_core.c?v=2.6.0-tes
t2
http://lxr.linux.no/source/drivers/pci/hotplug/cpqphp.h?v=2.6.0-test2

Regards,
John


John Cagle [EMAIL PROTECTED]
Principal Member Technical Staff
   Industry Standard Servers
Hewlett-Packard Company

 -Original Message-
 From: Scott Long [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, August 12, 2003 8:55 PM
 To: Doug White
 Cc: [EMAIL PROTECTED]; Petri Helenius
 Subject: Re: pci configuration
 
 
 Doug White wrote:
  On Tue, 12 Aug 2003, Petri Helenius wrote:
  
  
 Is there way to view PCI / PCI-X configuration with 
 bus-width and clock
 values when FreeBSD has already booted?
  
  
  If you know where in PCI config space to look you could use 
 pciconf to
  query it.  Can't say I've heard of PCI speed negotiation 
 issues, though.
  
 
 I'm not aware of any registers in the standard PCI config space that
 will tell you the speed of the bus.  Some PCI devices will make that
 information available, but not in a standard way.  The BIOS of some
 higher-end systems might also tell you this information.
 
 Scott
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to 
 [EMAIL PROTECTED]
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Invalid partition table error when creating more than oneslice during install?

2003-08-14 Thread Darren Pilgrim
On 2003-08-11, at 00:41:57, Doug White [EMAIL PROTECTED] wrote:

On Sun, 10 Aug 2003, Darren Pilgrim wrote:

 On 2003-08-10, at 15:29:32, Doug White [EMAIL PROTECTED] wrote:

 On Sat, 9 Aug 2003, Darren Pilgrim wrote:
 
  I'm trying to get 5.1-R installed, but I've run into a problem I don't
  understand.  The disk layout I want should look like this:
 
  s1: 20gb, FreeBSD
  s2: 10gb, Windows
  s3: ~83gb (the rest of the disk), data
 
 with what tool are you creating s2 and s3?  It sounds like the last thing
 that touches it is not creating a proper partition table and your BIOS is
 unhappy.

 Sysinstall, as part of the installation process.

Hm. sysinstall is famously bad at making slice tables.  The usual solution
is to make the Windows partitions first using DOS FDISK on a zeroed disk
-- it can usually get the geometry right.

I used fdisk(8) from my existing 5.0 install and it worked great!  It even dealt
with my being lazy and not taking the time to calculate boundary-aligned sizes.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Crash in g_dev_strategy / CURRENT as of yesterday.

2003-08-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Eivind Olsen writes:
Hello. Some of you might have seen my previous mailings regarding crashes 
in g_dev_strategy under FreeBSD 5.1 (RELENG_5_1). I have now upgraded to 
CURRENT (cvsupped, compiled and installed yesterday) and I still see 
similar  crashes (but not identical crashes, I can't see any mention of 
Vinum here).

#12 0xc030697e in spec_xstrategy (vp=0xc1fa9cc0, bp=0x0) at 
/usr/src/sys/fs/specfs/spec_vnops.c:512

This is the call into the device driver.  Do you have any idea which
driver this might be ?  Can you try to print out the bp-b_dev structure
if you still have the dump ?

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem using USB 2.0 device under -CURRENT

2003-08-14 Thread Craig Boston
On Monday 11 August 2003 11:04 am, Joe Marcus Clarke wrote:
 [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x015f1028 chip=0x24cd8086
 rev=0x03
 hdr=0x00
 vendor   = 'Intel Corporation'
 device   = '82801DB (ICH4) USB EHCI Controller'
 class= serial bus
 subclass = USB

I have the same hardware (0x24cd8086) on a Dell-branded board with the same 
results.  I think so far only the NEC-based EHCI controllers are verified to 
work -- I don't know of anyone who has had success with the Intel ones.

 I haven't tried applying the patch to get it detected as an actual Intel
 controller, but I'm not sure that would help.

It doesn't.  It makes the probe message prettier but I get the same problem 
(unrecoverable error).  If you have time, could you try compiling with 
options USB_DEBUG and setting the sysctl hw.usb.debug=3 and 
hw.usb.ehci.debug=6 ?  Be warned that that will generate a LOT of debug 
output.

Craig

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


Re: Crash in g_dev_strategy / CURRENT as of yesterday.

2003-08-14 Thread Eivind Olsen
--On 12. august 2003 21:39 +0200 Poul-Henning Kamp [EMAIL PROTECTED] 
wrote:
I'm not of a gdb wizard either, but I think you type up or down until
you are at stack frame #12, and the simply say print *bp-b_dev
[EMAIL PROTECTED]:~/tmp/debug/CURRENT-2003-08-11  gdb -k kernel.debug vmcore.1
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 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-undermydesk-freebsd...
panic: from debugger
panic messages:
---
Syntax error: Unterminated quoted string
---
Reading symbols from 
/usr/obj/usr/src/sys/VIMES/modules/usr/src/sys/modules/vinum/vinum.ko.debug
...done.
Loaded symbols for 
/usr/obj/usr/src/sys/VIMES/modules/usr/src/sys/modules/vinum/vinum.ko.debug
Reading symbols from 
/usr/obj/usr/src/sys/VIMES/modules/usr/src/sys/modules/ipfw/ipfw.ko.debug..
.done.
Loaded symbols for 
/usr/obj/usr/src/sys/VIMES/modules/usr/src/sys/modules/ipfw/ipfw.ko.debug
Reading symbols from /boot/kernel/dragon_saver.ko...done.
Loaded symbols for /boot/kernel/dragon_saver.ko
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) fr 12
#12 0xc030697e in spec_xstrategy (vp=0xc1fa9cc0, bp=0x0) at 
/usr/src/sys/fs/specfs/spec_vnops.c:512
512 DEV_STRATEGY(bp);
(kgdb) print *bp-b_dev
There is no member named b_dev.
(kgdb)

I can give you SSH access to the server if it's any help / easier for you 
to  look at this yourself without telling me one command at a time.

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


Re: PCM freezes the box

2003-08-14 Thread root
 Is anything printed on the console (or the first vty)?
 
  Andre Guibert de Bruet | Enterprise Software Consultant 
  Silicon Landmark, LLC. | http://siliconlandmark.com/
Nope. I get complete blackout - I'm unable to switch vtys, move mouse,
start a new process, etc. Just like a crash in Windows - only reset button works.

 



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


Re: got bad cookie warnings/errors?

2003-08-14 Thread Terry Lambert
Lars Eggert wrote:
 David Malone wrote:
  I have a vague feeling they are related to a directory changing while it
  is being read, and might mean that the NFS client sees an inconsistent
  version of the directory. It's been a long time since I looked at it
  though.
 
 Sounds reasonable, but I'm not sure if is the case for me:
 
 My home directory is NFS mounted from a Solaris box, and gets modified
 only from a single client (my desktop) at a time. I get these cookie
 messages whenever I log out of X, when a lot of things get read and
 written to that mount. Since all those reads and writes originate on my
 FreeBSD desktop, I would expect its NFS client to keep its cache
 consitent in that case.
 
 But maybe not.

The problem is that the next iteration in the directory hits a bad
cookie error because a delete ocurred during an iteration.  If the
program that's doing the iteration to do the deletes (which is what
is likely happening) snapshotted the directory *then* did them, it
would all work fine.

Note that deleting from a shell doesn't have this problem, since
the globbing occurs in the shell, and the arguments are all
expanded before being passed to the rm, so it doesn't have this
issue.

Basically, you have some badly behaved (for NFS) software.  You
can't really safely assume the server disk block size for the
back-off (not to mention duplicate suppression for a double rename
operation).

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


Re: Crash in g_dev_strategy / CURRENT as of yesterday.

2003-08-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Eivind Olsen writes:
--On 12. august 2003 21:26 +0200 Poul-Henning Kamp [EMAIL PROTECTED] 
wrote:
 In message [EMAIL PROTECTED], Eivind Olsen writes:
 Hello. Some of you might have seen my previous mailings regarding
 crashes  in g_dev_strategy under FreeBSD 5.1 (RELENG_5_1). I have now
 upgraded to  CURRENT (cvsupped, compiled and installed yesterday) and I
 still see  similar  crashes (but not identical crashes, I can't see any
 mention of  Vinum here).
# 12 0xc030697e in spec_xstrategy (vp=0xc1fa9cc0, bp=0x0) at
 /usr/src/sys/fs/specfs/spec_vnops.c:512
 This is the call into the device driver.  Do you have any idea which
 driver this might be ?  Can you try to print out the bp-b_dev structure
 if you still have the dump ?

I still have the dump. Please tell me exactly which commands I should use 
and I'll take a look. I'm not a kernel hacker so I don't know how to get at 
that information all by myself.

I'm not of a gdb wizard either, but I think you type up or down until
you are at stack frame #12, and the simply say print *bp-b_dev

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.1, Data Corruption, Intel, Oh my! [patch] - Fatal trap 12

2003-08-14 Thread Terry Lambert
Bosko Milekic wrote:
  db trace
  _mtx_lock_flags(0,0,c07aa287,11e,c0c21aaa) at _mtx_lock_flags+0x43
  vm_fault(c102f000,c000,2,0,c08205c0) at vm_fault+0x2b4
  trap_pfault(c0c21b9e,0,c4d8,10,c4d8) at trap_pfault+0x152
  trap(6c200018,10,1bc40060,1c,0) at trap+0x30d
  calltrap() at calltrap+0x5
  --- trap 0xc, eip = 0x5949, esp = 0xc0c21bde, dbp = 0xc0c21be4 ---
  (null)(1bf80058,0,530e0102,80202,505a61) at 0x5949
  db

FWIW: This is a NULL function pointer that's trying to call a
function that hasn't been initialized, or has been explicitly
NULL'ed out.  Decoding the pointer values to find out what the
object are would probably go a long way toward knowing what's
going on.  Last time I saw one of these, it was the NFS lease
function.  He might also want to look for any function pointer
that takes 5 arguments; Linux threads is a likely suspect, in
that the thread mailboxes are at a fixed location, so he should
make sure to recompile any kernel modules when he compiles his
new kernel.

BTW: Good work on the patch, both you and Peter!

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


Re: Problem with dhclient wi0 on resume.

2003-08-14 Thread Martin Blapp

Hi,

 Unfortunately this system hasn't worked for me. As it is I have a script

Have you tested it and included theses commands in rc.resume and rc.suspend ?

 which lives in rc.d which starts up dhclient with the appropriate
 wireless options. Unfortunately after each suspend and resume this is
 what I have to use.

 If anyone comes up with a solution to this it'd be much appreciated.

Which script do you use ? The dhclient script in /etc/rc.d ?

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


pci configuration

2003-08-14 Thread Petri Helenius
Is there way to view PCI / PCI-X configuration with bus-width and clock values 
when FreeBSD has already booted?

Pete

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


[current tinderbox] failure on sparc64/sparc64

2003-08-14 Thread Tinderbox
TB --- 2003-08-10 23:07:20 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-08-10 23:07:20 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-10 23:10:05 - building world
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 stage 1: bootstrap tools
 stage 2: cleaning up the object tree
 stage 2: rebuilding the object tree
 stage 2: build tools
 stage 3: cross tools
 stage 4: populating 
 /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
TB --- 2003-08-11 00:06:18 - building generic kernel
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make buildkernel KERNCONF=GENERIC
 Kernel build for GENERIC started on Mon Aug 11 00:06:18 GMT 2003
 Kernel build for GENERIC completed on Mon Aug 11 00:15:11 GMT 2003
TB --- 2003-08-11 00:15:11 - generating LINT kernel config
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/conf
TB --- /usr/bin/make -B LINT
TB --- 2003-08-11 00:15:11 - building LINT kernel
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make buildkernel KERNCONF=LINT
 Kernel build for LINT started on Mon Aug 11 00:15:11 GMT 2003
[...]
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99  -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd
 -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing 
-fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/in_cksum.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99  -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd
 -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing 
-fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/intr_machdep.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99  -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd
 -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing 
-fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/sparc64/iommu.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99  -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd
 -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing 

Re: Invalid partition table error when creating more than oneslice during install?

2003-08-14 Thread Doug White
On Sat, 9 Aug 2003, Darren Pilgrim wrote:

 I'm trying to get 5.1-R installed, but I've run into a problem I don't
 understand.  The disk layout I want should look like this:

 s1: 20gb, FreeBSD
 s2: 10gb, Windows
 s3: ~83gb (the rest of the disk), data

with what tool are you creating s2 and s3?  It sounds like the last thing
that touches it is not creating a proper partition table and your BIOS is
unhappy.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Panic at _mtx_lock_flags+0x43 on VMware 3.x

2003-08-14 Thread Jun Kuriyama
At Fri, 08 Aug 2003 15:47:31 -0400 (EDT),
John Baldwin wrote:
 The passed in mutex to mtx_lock is NULL, so likely a bio or
 some such in spec_getpages() is zero'd and not initialized
 yet or something.

Yes, vp-v_object in spec_getpages() is NULL and then,
VTOI(ap-a_vp)-i_devvp-v_object in ffs_getpages() (the caller of
spec_getpages() via VOP_GETPAGES()) is also NULL.

I don't know where this should be initialized...


-- 
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
 [EMAIL PROTECTED] // FreeBSD Project
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: got bad cookie warnings/errors?

2003-08-14 Thread Lars Eggert
Emiel Kollof wrote:
I've been seeing lots of these lately:

got bad cookie vp 0xc2f40b68 bp 0xc929a1e8
got bad cookie vp 0xc318d124 bp 0xc91d4240
...
I grepped around, and it seems it has something to do with NFS (well, I found 
this being printf'ed in src/sys/nfsclient/nfs_bio.c

I have two NFS machines from which I mount, a 4.8-STABLE machine and a NetBSD 
1.6.1 box. I haven't seen any dataloss or panics. But still, should I be 
worried? How serious is this message?
I can only say that (1) I've been getting these forever, on both -stable 
and -current, and (2) I personally have never lost any data.

However, I have no clue as to why you and I get them, or what they signify.

Lars
--
Lars Eggert [EMAIL PROTECTED]   USC Information Sciences Institute


smime.p7s
Description: S/MIME Cryptographic Signature


Re: PLIP transmit timeouts -- any solutions?

2003-08-14 Thread Ian Dowse
In message [EMAIL PROTECTED], Christopher Nehren writes:

--=-7MVWKH2AJ0lqXf3q30++
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I currently have a PLIP link to an old laptop running Linux (I tried to
install FreeBSD, but it freezes at the USB detection -- yes, I tried

Try the following patch. I can't remember if all the changes in
this are necessary, but I think I found it fixed problems when
interoperating with a Linux-like PLIP implementation.

If I remember correctly, the PLIP implementation I saw used the
data bits that came in the very first read that had the correct
handshake signal, whereas FreeBSD readers do one extra read after
the handshake to ensure that the signal is stable (i.e. that
implementation used an unsafe read and a safe write, whereas
FreeBSD's uses a safe read and an unsafe write). This patch
causes both read and write to be safe. The removal of the use of
ctxmitl[] seems to be unnecessary.

Ian

Index: if_plip.c
===
RCS file: /dump/FreeBSD-CVS/src/sys/dev/ppbus/if_plip.c,v
retrieving revision 1.28
diff -u -r1.28 if_plip.c
--- if_plip.c   4 Mar 2003 23:19:54 -   1.28
+++ if_plip.c   12 Mar 2003 07:09:43 -
@@ -409,12 +409,14 @@
 static __inline int
 clpoutbyte (u_char byte, int spin, device_t ppbus)
 {
-   ppb_wdtr(ppbus, ctxmitl[byte]);
+   ppb_wdtr(ppbus, byte  0xf);
+   ppb_wdtr(ppbus, (byte  0xf) | 0x10);
while (ppb_rstr(ppbus)  CLPIP_SHAKE)
if (--spin == 0) {
return 1;
}
-   ppb_wdtr(ppbus, ctxmith[byte]);
+   ppb_wdtr(ppbus, ((byte  0xf0)  4) | 0x10);
+   ppb_wdtr(ppbus, ((byte  0xf0)  4));
while (!(ppb_rstr(ppbus)  CLPIP_SHAKE))
if (--spin == 0) {
return 1;
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ACPI battery state and resume not working on Inspiron 5150

2003-08-14 Thread Scott Lambert
On Sat, Aug 09, 2003 at 08:53:54PM -0400, David Gilbert wrote:
  Kevin == Kevin Oberman [EMAIL PROTECTED] writes:

 Kevin Sorry, Joe. By the way, are you suspending with acpiconf -s3?
 Kevin Have you tried creating a hibernation partition (slice) and
 Kevin using -s4? That appears to work better than suspend on most
 Kevin platforms that support it at all.
 Kevin
 Kevin -- R. Kevin Oberman, Network Engineer

 What does a hibernation partition look like?

 My dell has a 31 meg partition that I havn't touched and my FreeBSD
 partition.

And can you determine what the hibernation partition should look like
from an acpidump?  I have a toshiba that only lists :

hw.acpi.supported_sleep_state: S1 S4 S5 

And I wiped the disk so fast after I bought it, that I've never seen the
hibernation setup that originally came with it.

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


Re: 5.1-R acl problem (again)

2003-08-14 Thread Robert Watson

On Sun, 10 Aug 2003, Branko F. Gracnar wrote:

 Thanks for quick and very informative answer. 
 
 You're right about getfacl -d (i used linux + acl patch before, where
 default acls are displayed without any arguments and i didn't read
 getfacl man page). 

Yeah -- the Linux tool implementation is based more on Solaris than on
POSIX.1e.  That has some upsides, and some downsides.  I believe there's
an environmental variable you can set on Linux to cause the
getfacl/setfacl to behave in strict accordance with the spec
(POSIXLY_CORRECT or the like). 

 Thanks alot again.

Sure.

 But there is one thing, i don't understand. 
 
 if i issue the following command:
 
 setfacl -dm u::rwx,g::rx,o::---,u:branko:rwx,m::rwx  directory
 
 and then create file under that directory, why getfacl reports:
 
 #file:a/c
 #owner:0
 #group:0
 user::rw-
 user:branko:rwx # effective: r--
 group::r-x  # effective: r--
 mask::r--
 other::r--
 
 why is mask just 'r' ?!

One of the contentious issues in the design of POSIX.1e was how to set the
protections on a new object.  There are three variables of interest: the
creation mode requested by a process, the umask of that process, and the
default ACL on the parent directory where the object is being created.  In
5.0-R and 5.1-R, we combine them as follows: we mask all elements of the
creation mode using the umask; we then combine the ACL and combined mode
by converting the default ACL to the access ACL on the new object and
overwriting the access ACL fields with the equivilent fields in the mode.
So in the above example, a mask of r-- is likely a result of the creation
mode and umask having a group mode of 4.

In 5.1-CURRENT, we recently switched these semantics to perform a further
intersection of rights in the ACL, rather than a replacement of rights. 
The result is that if the mask in your default ACL is --- and the
combination of creation mode and umask is r--, you get a mask of --- in
the final access ACL.  This implements the algorithm in the POSIX.1e spec
to the letter: at some point, these semantics got changed during a
retrofit of the ACL code, and it wasn't picked up (this might actually
have been after 5.0 but I haven't checked the logs).

I'm currently in the throes of implementing a mode of operation which uses
the Solaris/Linux algorithm, which works in the following manner: if an
default ACL is being used to create a new object, the default ACL replaces
the umask, rather than combining with it.  This allows directory default
ACLs to override the umask locally, producing more liberal rights, which
may be what you're expecting.  This is a violation of the spec, but it's a
common violation due to its utility (POSIX.1e doesn't allow the create
more liberal protections because it was deemed unsafe).  I hope to finish
prototyping this and get a patch out to the current@ list in the next
couple of weeks.  The complication is that currently, the umask and
requested creation mode are combined at the system call layer, above VFS,
so we need to expose them separately on the entry to the file system.  The
result is that all file systems would now have to combine the two
elements, and it touches a lot of code. 

Hope this information is useful, and gives you a good picture of where
we're going. 

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

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


Re: distcc and freebsd

2003-08-14 Thread Emiel Kollof
Op maandag 11 augustus 2003 19:26, schreef Christer Gundersen:
 anyone gotten this to work?

Yes, I have.

 It seems like I cant. I followed the howto on their page, but it seems
 like distccd dont startup right. ('ps aux' shows distccd running)
 Like, distccd runs but it dont open the port that it needs. I even tried
 using 'distccd --daemon -p 80' , but nmap did not find it, nor does a
 'telnet localhost 80' seem to find anything.
 The monitor does not seem to respond either.

Distcc wants to drop down it's privs (it doesn't like runnig as root). And 
seeming that you are trying to bind distcc to a priviledged port, no wonder 
it won't listen. Best is to create a locked distcc user without a shell that 
can't log in. Then just run distccd, and edit the distcc hosts file so you 
can distribute complies across machines. Don't forget to use -j flags with 
make.

To see if distccd is doing compile jobs, you can always attach a strace(1) (or 
maybe even truss) to it's pid and watch if it's doing someting.

HTH

Cheers,
Emiel
-- 
If everything is coming your way then you're in the wrong lane.

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


Re: Problem with PS/2 mouse driver in XFree86 4.3.0

2003-08-14 Thread Mike Bohan
Not to undermine what you guys said, but this is unrelated to the
original post I think.  The problem I was having related to acpi, which
Shizuka pointed out.  I'm not trying to play nanny here, just don't want
people to get confused =)

On Sun, 2003-08-10 at 21:16, Daniel Flickinger wrote:

   Sent: Sun, 10 Aug 2003 15:32:28 -0700 (PDT) by Doug White
 
   + On Sun, 10 Aug 2003, Daniel Flickinger wrote:
   +
   +  I had the same problem starting about a year ago when I
   +  finally gave up and upgraded to X4. The problem appears
   +  to be that the X4 driver does not disable the console
   +  mouse and the two of them fight over the interrupts.
   +
   + Well yeah moused and X can't both use the mouse at once. You
   + should get a 'device busy' error.  If you want to use moused
   + then have X gets its events from moused (/dev/sysmouse) and
   + not psm0.
 
 That's what I did, as I had done in the past with X3
 --upgrading to X4 is when the problem came up, and yes,
 you get a mouse busy when you move it to /dev/psm0.
 However, if you do not start the mouse for the virtual
 screens (which I had no need for anyway), /dev/psm0 can
 be opened for X4.
 
 Secondly, at the time, Xconfig would not accept
 /dev/sysmouse as a ps2 style mouse and would not track
 if I called it a generic mouse... that may have changed.
 
 CAVEAT: I admit that I have not revisted the problem
 since then which was at least a year ago --it works, I
 leave it alone despite several X4 upgrades. The remedy
 at the time was to use /dev/psm0, not /dev/sysmouse.
 Maybe in the next upgrade I'll revisit the aggravation
 since I would prefer to be able to use virtual X
 sessions on separate logins.
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


LOR in pcm

2003-08-14 Thread Dmitry Sivachenko
Hello!

I have Chaintech Apogee 7VGL motherboard with on-board CMedia 8738 audio chip.
Kernel identifies it as follows:
pcm0: CMedia CMI8738 port 0xe400-0xe4ff irq 10 at device 19.0 on pci0

I am running very recent -current.

When I am watching movies in mplayer, I get on the console from time to time:

lock order reversal
 1st 0xc4021c40 pcm0 (sound softc) @ /usr/src/sys/dev/sound/pci/cmi.c:520
 2nd 0xc402c4c0 pcm0:play:0 (pcm channel) @ /usr/src/sys/dev/sound/pcm/channel.c
:440
Stack backtrace:
backtrace(c03503c2,c402c4c0,c4045154,c03420f5,c03421cf) at backtrace+0x17
witness_lock(c402c4c0,8,c03421cf,1b8,c) at witness_lock+0x672
_mtx_lock_flags(c402c4c0,0,c03421cf,1b8,80c1) at _mtx_lock_flags+0xba
chn_intr(c4045100,c,1,208,c4021b80) at chn_intr+0x2f
cmi_intr(c4045280,0,c034b2ba,215,c405f1e4) at cmi_intr+0xa0
ithread_loop(c4045200,d6947d48,c034b12c,30e,0) at ithread_loop+0x182
fork_exit(c01ef870,c4045200,d6947d48) at fork_exit+0xcf
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd6947d7c, ebp = 0 ---

I could provide additional information if needed.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ACPI battery state and resume not working on Inspiron 5150

2003-08-14 Thread David Gilbert
 Kevin == Kevin Oberman [EMAIL PROTECTED] writes:

Kevin I don't know if all laptops support both, but every one I have
Kevin used does. IBM has a stand-alone tool on it's web site that
Kevin creates a hibernation partition on ThinkPads (which I use). You
Kevin probably need to check with the manufacturer of your system to
Kevin see what is available.

I'm working on tracking that down for my Dell.  What's been
frustrating me ... is that the S1 is not very useful and the S3
suspend shuts the machine off.  I tried putting a value in the sleep
timeout as as suggested here recently... but it didn't help.

My only hope at this point is that S4 will do something useful.

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem with PS/2 mouse driver in XFree86 4.3.0

2003-08-14 Thread Doug White
On Sun, 10 Aug 2003, Daniel Flickinger wrote:

 I had the same problem starting about a year ago when I
 finally gave up and upgraded to X4. The problem appears
 to be that the X4 driver does not disable the console
 mouse and the two of them fight over the interrupts.

Well yeah moused and X can't both use the mouse at once. You should get a
'device busy' error.  If you want to use moused then have X gets its
events from moused (/dev/sysmouse) and not psm0.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: TESTERS WANTED for ATAng preview 1

2003-08-14 Thread Jason Dambrosio
On Fri, Aug 08, 2003 at 09:55:11PM +0200, Soeren Schmidt wrote:
 
 The first preview release of ATAng is now available on:
 
 ftp://ftp.deepcore.dk/pub/ATAng

I cvsup'd to HEAD and applied the conf-patch and put in your
new ATA source, but when I recompiled my kernel and rebooted, the
server just locked up with the following dmesg:

Console: serial port
BIOS drive C: is disk0
BIOS 639kB/523264kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Mon Jun  9 08:51:01 HST 2003)
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x23b4b4 data=0x2700c+0x4cfd0 syms=[0x4+0x2f0a0+0x4+0x3a9c7]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #1: Fri Aug  8 13:41:50 HST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LEET
Preloaded elf kernel /boot/kernel/kernel at 0xc041b000.
Timecounter i8254  frequency 1193182 Hz
CPU: AMD Athlon(tm) XP 2100+ (1733.41-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x681  Stepping = 1
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
  AMD Features=0xc040AMIE,DSP,3DNow!
real memory  = 536870912 (512 MB)
avail memory = 517066752 (493 MB)
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 14 entries at 0xc00f8030
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
pci_cfgintr: 0:13 INTA BIOS irq 11
pci_cfgintr: 0:15 INTA BIOS irq 10
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
atapci0: Promise PDC20376 SATA150 controller port 
0xe400-0xe47f,0xe800-0xe80f,0xec00-0xec3f mem 
0xdffa-0xdffb,0xdffdf000-0xdffd irq 11 at device 13.0 on pci0
ata2: at 0xdffdf000 on atapci0
ata3: at 0xdffdf000 on atapci0
ata4: at 0xdffdf000 on atapci0
bge0: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xdffc-0xdffc 
irq 10 at device 15.0 on pci0
bge0: Ethernet address: 00:10:dc:d6:05:a2
miibus0: MII bus on bge0
brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, 
auto
isab0: PCI-ISA bridge at device 17.0 on pci0
isa0: ISA bus on isab0
orm0: Option ROM at iomem 0xc8000-0xc on isa0
ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0
ata1 at port 0x376,0x170-0x177 irq 15 on isa0
atkbdc0: Keyboard cller (i8042) at port 0x64,0x60 on isa0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown: PNP0c02 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
RTC BIOS diagnostic error 20config_unit
Timecounter TSC  frequency 1733405338 Hz
Timecounters tick every 10.000 msec
IPv6 packet filtering initialized, default to accept, unlimited logging
DUMMYNET initialized (011031)
ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, 
logging unlimited
IPsec: Initialized Security Association Processing.
ad6: 114473MB WDC WD1200JB-00CRA1 [232581/16/63] at ata3-master UDMA100

(locked up at that point)

Thanks,

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


help me out please : contigmalloc1: size must not be 0

2003-08-14 Thread S. Koers
I am receiving this error while booting from the 5.0 miniinst.iso CD: contigmalloc1: 
size must not be 0
My pc is a IBM a30 notebook.

Please help me, so I can install FreeBSD on that machine,

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


Re: GEOM/vinum compatibility

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
Wilko Bulte [EMAIL PROTECTED] writes:
: 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..

As would a little technical information.  It does no harm to send off
a message that tells of API breakage/introduction.

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


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


Re: dhclient problem with xl0

2003-08-14 Thread Martin Blapp

Hi,

 Here is the output of dhclient -v -d xl0

I I checked. Dhclient still initializes the
interface and brings it up itself. So there
is only one possibility:

You don't have a working link. Maybe it helps
if you add a interface define in /etc/dhclient.conf
wit the possible media.

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


Re: make buildkernel hang with SCHED_ULE

2003-08-14 Thread Adam Migus
Andrew Gallatin wrote:

Adam Migus writes:
 Folks,
 While doing some performance analysis (doing make -j5 buildkernel)
 on a set of 14 kernels I've hit one using the SCHED_ULE scheduler
 that hangs.   It happens every time but not necessarily in the same
 place in the make.
 

...

 The hardware is a dual Xeon box.  The kernel is SMP w/ SCHED_ULE
 instead of SCHED_4BSD, the options required for diskless and the
 following two options:
You have machdep.hlt_logical_cpus: 1 in your sysctl output.  [BTW,
lots of people read this mail via the web archives at
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1073654+0+current/freebsd-current,
where its impossible to view mime; it would be MUCH better for us if
appended things like stack traces and sysctl output rather then
scrambling them for no reason]
SCHED_ULE is incompatible with halting logical CPUs.  Something about
it does't know the core isn't running, so it schedules a job there
which never runs, and then it gets confused.  When I boot a 1 CPU P4
with an SMP kernel and machdep.hlt_logical_cpus=1, it hangs before
making it to multiuser mode..
Try setting machdep.hlt_logical_cpus=0 (via sysctl now, and in
/boot/loader.conf so it doesn't happen again).
Drew
 

Andrew,
WRT the mime thing.  My apologies.  It never occured to me as everyone I 
know personally uses a real mail reader.  I'd attached them simply to 
keep the scrolling down and allow order independant viewing.  Thanks for 
the tip.  I'll just read them in as plain text in the future.

WRT the sysctl value.  Thanks for the tip.  Is this to be considered a 
bug in SCHED_ULE?  If the default is hlt_logical_cpus=1 I would think 
the scheduler should be able to handle it or deal with it 
appropriately.  Perhaps ignoring the value, setting it to 0 internally 
or even just putting a warning message on boot?  After all, not everyone 
RTFM's.  :-)

Thanks again,

--
Adam - Migus Dot Org (http://www.migus.org)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ipfw feature request

2003-08-14 Thread The Anarcat
You're looking for the me keyword. See the manpage for details.

A.

On Fri Aug 08, 2003 at 08:52:07AM -0400, David Hill wrote:
 Hello -
 I apologize in advance if this feature is already implemented.
 
 Is there anyway for ipfw to automatically get the IP from the interface?  In 
 OpenBSD's PF, putting ()'s around the interface name will cause that rule to be 
 refreshed on an IP change, such as DHCP, making reloading the rules manually 
 unnecessary.
 
 Thanks
 David
 
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 


-- 
Lorsque l'on range des objets dans des tiroirs, et que l'on a plus
d'objets que de tiroirs, alors un tiroir au moins contient deux
objets.
- Lejeune-Dirichlet, Peter Gustav


pgp0.pgp
Description: PGP signature


Re: make buildkernel hang with SCHED_ULE

2003-08-14 Thread Jeff Roberson

On Thu, 14 Aug 2003, Adam Migus wrote:

 Andrew Gallatin wrote:

 Adam Migus writes:
   Folks,
   While doing some performance analysis (doing make -j5 buildkernel)
   on a set of 14 kernels I've hit one using the SCHED_ULE scheduler
   that hangs.   It happens every time but not necessarily in the same
   place in the make.
  
 
 ...
 
   The hardware is a dual Xeon box.  The kernel is SMP w/ SCHED_ULE
   instead of SCHED_4BSD, the options required for diskless and the
   following two options:
 
 You have machdep.hlt_logical_cpus: 1 in your sysctl output.  [BTW,
 lots of people read this mail via the web archives at
 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1073654+0+current/freebsd-current,
 where its impossible to view mime; it would be MUCH better for us if
 appended things like stack traces and sysctl output rather then
 scrambling them for no reason]
 
 SCHED_ULE is incompatible with halting logical CPUs.  Something about
 it does't know the core isn't running, so it schedules a job there
 which never runs, and then it gets confused.  When I boot a 1 CPU P4
 with an SMP kernel and machdep.hlt_logical_cpus=1, it hangs before
 making it to multiuser mode..
 
 Try setting machdep.hlt_logical_cpus=0 (via sysctl now, and in
 /boot/loader.conf so it doesn't happen again).
 
 
 Drew
 
 

 Andrew,
 WRT the mime thing.  My apologies.  It never occured to me as everyone I
 know personally uses a real mail reader.  I'd attached them simply to
 keep the scrolling down and allow order independant viewing.  Thanks for
 the tip.  I'll just read them in as plain text in the future.

 WRT the sysctl value.  Thanks for the tip.  Is this to be considered a
 bug in SCHED_ULE?  If the default is hlt_logical_cpus=1 I would think
 the scheduler should be able to handle it or deal with it
 appropriately.  Perhaps ignoring the value, setting it to 0 internally
 or even just putting a warning message on boot?  After all, not everyone
 RTFM's.  :-)


The MD code does not currently export the status of the CPUs in any
reliable way.  ULE attempts to recognize halted CPUs but it is not able to
due to other issues.  I think john baldwin might be solving this for x86.
If not I can take a stab at it again.

 Thanks again,

 --
 Adam - Migus Dot Org (http://www.migus.org)


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


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


Re: dhclient problem with xl0

2003-08-14 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Martin Blapp wrote:
 Isn't there a way to see that the card doesn't support reporting
 media status ? If the card does report this, I could add code
 to dhclient and all would be fine.

Yes; check the media status word for IFM_AVALID.

(whitespace damaged)
%%%
--- dhclient.c  28 Jul 2003 13:25:04 -  1.27
+++ dhclient.c  9 Aug 2003 13:07:16 -
@@ -3221,13 +3221,11 @@
if (ifmr.ifm_status  IFM_ACTIVE)
return (1);
}
+   return (0);
}

-   return (0);
-#else /* ifdef __FreeBSD__ */
-
-   return (1);
 #endif /* Other OSs */
+   return (1);
 }

 #ifdef __FreeBSD__
%%%


-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


LOR with filedesc structure and Giant

2003-08-14 Thread Kris Kennaway
Aug  9 11:29:50 dosirak kernel: lock order reversal
Aug  9 11:29:50 dosirak kernel: 1st 0xcf3fa334 filedesc structure (filedesc structure) 
@ kern/sys_generic.c:895
Aug  9 11:29:50 dosirak kernel: 2nd 0xc070a8e0 Giant (Giant) @ 
fs/specfs/spec_vnops.c:372
Aug  9 11:29:50 dosirak kernel: Stack backtrace:

And that's it (i.e. no backtrace is recorded).

Kris

pgp0.pgp
Description: PGP signature


Re: ipfw - default to accept + bootp = confusion.

2003-08-14 Thread James Quick
On Thursday, August 7, 2003, at 02:23  AM, Juli Mallett wrote:

* James Quick [EMAIL PROTECTED] [ Date: 2003-08-07 ]
[ w.r.t. Re: ipfw - default to accept + bootp = confusion. ]
On Thursday, August 7, 2003, at 12:22  AM, Juli Mallett wrote:

Does someone have any idea what approach to take for the following
scenario?  I'm leaning towards a compile time failure, or an
informative
panic at the beginning of bootp...
You have IPFIREWALL, but not the default to accept option, and you 
have
BOOTP.  The BOOTP stuff will fail in sosend with EACCESS 
(informatively
printed as 13), because of IPFW, and this may be slightly 
non-obvious
to people who haven't dealt with early ipfw interference before.

If not compile time failure / panic, I'd say probably we want some 
way
to notify a user in general of ipfw stopping pre-init operation, but 
I
don't want to add the concept of runlevels, and don't know if there's
anything there currently to do detection of if we've hit that point
yet.
If the default rule controlled by IPFIREWALL_DEFAULT_TO_ACCEPT,
default_rule.cmd[0].opcode, were made accessible via a sysctl.
then bootp could check it and produce an informative message.
Or, if possible try to insert a rule into the kernel restrictive 
enough
to
be safe.  On the one hand it's a firewall, and you don't want to be
It's entirely easy/possible to add such, but I'd rather not have a
dumb sysadmin blame me for their firewall supposedly getting
punctured.  If you have BOOTP on a box, defaulting to DENY is insane.
Does that mean I want to just *change* things at runtime?  No.  I'd
rather prevent any foot-shooting of any form.
Given the current implementation, the situation is insane.  However,
In a wider context, it might be worth looking at the configuration 
decisions
in terms of allowable site policy, rather than dismissing the 
combination
as worthless.  Regarding foot-shooting, I agree that bypassing the deny
rule to finish booting needs to be analyzed carefully and made explicit 
to
the user, through a combination of documentation and/or user 
intervention.
and/or documentation.  I believe however, that the point is largely 
moot.
A foot is already bloody at this point, isn't it?

Given the current behavior, the critical path is the conjunction of 
three
or four events.  Only one of which is compilation.  Complaining or 
halting
during compilation, or requiring additional action to get  a quiet 
compile
seem ill-advised.  They add complexity to the common path in order to
flag a possible error which could only occur in the context of several 
other
independent (and uncommon) events.  To reach this point the kernel has 
to be:
	1. Installed as a resource on a bootpd or tftpd server.
	2. Loaded by a system configured to boot it, because:
		a. They are diskless
		b. They suffered a loader failure from local disk and are
		attempting a more graceful failure by booting from the network.

The insanity of the configuration, is thus dependent both, on a
number of configuration choices outside of the kernel, and the
current implementation, which has no choice but to fail.
I think this is best viewed as a matter of defining allowable policy.
Making a decision about how to handle this situation, has direct impact 
on
the choices available to the end-user in defining site-wide 
architecture.

In the default configuration, sites have the choice of either using 
diskless
workstations, or configuring hosts with local disk to perform a network
boot after an initial failure.  Also, in the default configuration, 
sites have the
choice of using ip_fw as a mechanism for reporting on, and/or enforcing,
their network policy.  Finally, it seems good policy for any large site 
to reduce
complexity by using the same kernel for a network boot, as is normally 
used
from disk.  Thus providing the option to remotely boot a kernel which 
now
makes sense only locally, is not as insane as it appears initially.

Each of these site policies in isolation make eminent sense. The 
questions for
you become: Do want to provide additional support for sites who wish 
to implement
net booting as a response to end-user hardware failure, and whose 
security
policy defines the use of default deny rules for it's workstations?.

If the answer is no, then fine.  Report as much detail as you can 
before halting.
If the answer is yes, then, documenting that the client host will 
accept
the following packets, during a network boot, until later configuration 
overrides
it., does not seem out of line.  In either case, it makes the 
allowable policy
explicit.

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


RE: Panic at _mtx_lock_flags+0x43 on VMware 3.x

2003-08-14 Thread John Baldwin

On 08-Aug-2003 Jun Kuriyama wrote:
 
 I got a reproducable panic when installing current snapshot on VMware
 3.x on Windows XP.
 
 Sorry, panic message and trace is PNG image captured on Windows:
 
 http://www.imgsrc.co.jp/~kuriyama/tmp/20030808.png
 
 If more information is needed, please let me know.

The passed in mutex to mtx_lock is NULL, so likely a bio or
some such in spec_getpages() is zero'd and not initialized
yet or something.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: TESTERS WANTED for ATAng preview 1

2003-08-14 Thread Soeren Schmidt
It seems Jason Dambrosio wrote:
 On Fri, Aug 08, 2003 at 09:55:11PM +0200, Soeren Schmidt wrote:
  
  The first preview release of ATAng is now available on:
  
  ftp://ftp.deepcore.dk/pub/ATAng
 
 I cvsup'd to HEAD and applied the conf-patch and put in your
 new ATA source, but when I recompiled my kernel and rebooted, the
 server just locked up with the following dmesg:

 atapci0: Promise PDC20376 SATA150 controller port 
 0xe400-0xe47f,0xe800-0xe80f,0xec00-0xec3f mem 
 0xdffa-0xdffb,0xdffdf000-0xdffd irq 11 at device 13.0 on pci0
 ata2: at 0xdffdf000 on atapci0
 ata3: at 0xdffdf000 on atapci0
 ata4: at 0xdffdf000 on atapci0

OK, Try the new .tgz I just uploaded, I'm pretty sure that solves the
problem for you..

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


5.1-R acl problem (again)

2003-08-14 Thread Branko F . Granar
Hi

Today i added new disk partition to my 5.1-release box. I want to use ACLs, which are 
enabled in kernel, they work partialy. They work on a single directory or file, but 
they don't even apply to file/directory, when i try to set so called default ACL entry.

I attached my kernel config file. Additionally, i've got loaded openbsd pf module 
(firewall).

Any help would be very appreciated.

Brane

Command sequence was:

# newfs -O 2 -L export -U -m 0 -o space /dev/ad0s2d
... lots of numbers ...

# tunefs -a enable /dev/ad0s2d
tunefs: ACLs set

# mount /dev/ad0s2d /export

# mount | grep /export
/dev/ad0s2d on /export (ufs, local, soft-updates, acls)


Now i create directory /export/a. I want to be owned by root:wheel, others will no 
have any access at all and i want that user branko will have rw access to it.

# mkdir a

# getfacl a
#file:a
#owner:0
#group:0
user::rwx
group::r-x
other::r-x

# setfacl -m u::rwx,g::rx,o::---,u:branko:rwx a

# getfacl a
#file:a
#owner:0
#group:0
user::rwx
user:branko:rwx
group::r-x
mask::rwx
other::---

(testing as branko - works okay)

Now, if root creates some files (od dirs) in 'a', owner of that file will be root and 
only standard unix triple acl will be assigned, so that user branko will not be able 
to access that file read/write. 

Well, it seems, that default directory acl need to be set to achive above goal.

# setfacl -b a

# setfacl -dm u::rwx,g::rwx,o::--,u:branko:rwx a

# getfacl a
#file:a
#owner:0
#group:0
user::rwx
group::r-x
mask::r-x
other::---

WHOOPS, where is user branko?! Why group's acls was not altered from 'r-x' to 'rwx' ?!

Ofcourse, trying to access directory 'a' as branko doesn't succeed.machine i386
cpu I686_CPU
ident   FROST

options SCHED_4BSD  #4BSD scheduler
options INET#InterNETworking
options INET6   #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options UFS_ACL #Support for access control lists
options UFS_DIRHASH #Improve performance on big directories
options NFSCLIENT   #Network Filesystem Client
options NFSSERVER   #Network Filesystem Server
options NULLFS
options PROCFS  #Process filesystem (requires PSEUDOFS)
options PSEUDOFS#Pseudo-filesystem framework
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions

device  isa
device  pci

# Floppy drives
device  fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
options ATA_STATIC_ID   #Static device numbering

# atkbdc0 controls both the keyboard and the PS/2 mouse
device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse


device  vga # VGA video card driver

device  splash  # Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device  sc

# Floating point support - do not disable.
device  npx

# Power management support (see NOTES for more options)
device  apm
device  acpi
# Add suspend/resume support for the i8254.
device  pmtimer

# Serial (COM) ports
device  sio # 8250, 16[45]50 based serial ports

# Parallel port
device  ppc
device  ppbus   # Parallel port bus (required)
device  lpt # Printer
device  ppi # Parallel port interface device


# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device  miibus  # MII bus support
device  dc  # DEC/Intel 21143 and various workalikes
device  ed  # NE[12]000, SMC Ultra, 3c503, DS8390 cards
device  rl  # RealTek

# Pseudo devices - the number indicates how many units to allocate.
device  random  # Entropy device
device  loop# Network loopback
device  ether   # Ethernet support
device  ppp # Kernel PPP
device  pty # Pseudo-ttys (telnet etc)
device  md   

Re: busdma/scsi trm(4) related panic

2003-08-14 Thread Scott Long
Ruslan Ermilov wrote:
On Wed, Aug 06, 2003 at 07:42:06AM -0600, Scott Long wrote:

I know what the problem is and I'm working on a patch right now.

I have the same problem with amd(4) and this commit to busdma_machdep.c.

Cheers,
Attached is an untested patch for amd(4).  Please let me know if it
fixes your problem.
Scott
Index: amd.c
===
RCS file: /home/ncvs/src/sys/dev/amd/amd.c,v
retrieving revision 1.22
diff -u -r1.22 amd.c
--- amd.c   31 Jul 2003 16:55:44 -  1.22
+++ amd.c   9 Aug 2003 06:44:28 -
@@ -2115,12 +2115,26 @@
 {
u_int16_t  count, i;
struct amd_srb *psrb;
+   int error;
 
count = amd-SRBCount;
 
for (i = 0; i  count; i++) {
psrb = (struct amd_srb *)amd-SRB_array[i];
psrb-TagNumber = i;
+
+   /*
+* Create the dmamap.  This is no longer optional!
+*
+* XXX Since there is no detach method in this driver,
+* this does not get freed!
+*/
+   if ((error = bus_dmamap_create(amd-buffer_dmat, 0,
+  psrb-dmamap)) != 0) {
+   device_printf(amd-dev, Error %d creating buffer 
+ dmamap!\n, error);
+   return;
+   }
TAILQ_INSERT_TAIL(amd-free_srbs, psrb, links);
}
 }
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Troubles while mounting ext2 from 5.1-RELEASE

2003-08-14 Thread Christian Laursen
Vincent Caron [EMAIL PROTECTED] writes:

 Bruce Evans said:
  
   # mount -t ext2fs /dev/ad0s2 /mnt/linux
   ext2fs: /dev/ad0s2: No such file or directory
 
  Did you compile EXT2FS support into your kernel?
 
 Awful shame on a FreeBSD newbie, I didn't. I naively thought it was in the GENERIC
 kernel, but I just saw he note about the 'risky' use of the ext2 module. Apologies.
 Building now bleeding edge kernel ...

Actually I think the main reason for not shipping it in binary form is that the
code is licensed under the GPL.

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


Re: ntop broken?

2003-08-14 Thread Charlie Schluting
On Thu, 7 Aug 2003, Kris Kennaway wrote:
   On Wed, Aug 06, 2003 at 08:57:53AM -0700, Charlie Schluting wrote:
Running 5.0.
  
   cvsup to 5.1 and retry.  The package currently builds on a clean 5.1 system.
 
  Ok, done, and still:
  *  crypt() in -lc...no -lcrypt...no
  makes it fail.
  I cvsuped the ports with tag=.
  Any ideas?

 It's likely you have stale files lying around that are confusing the
 build.  ntop builds successfully on a clean 5.x system.

 Kris

Ok, sorry for being a PITA, but..

I try to install mcrypt, and it is marked broken. I'm kinda stuck. Any
idea what files those would be? It seems that it can't find crypt.h and
stuff like that, so it sounds to me like files are missing?

Is there any particular approach you'd take in solving this?

Thanks  :)

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


Re: another buildworld -j4 panic

2003-08-14 Thread Bosko Milekic

On Thu, Aug 07, 2003 at 05:36:38PM -0500, Mike Silbersack wrote:
 
 ok, here goes:
 
 duplicate free from zone FFS1 dinode
 
 traceback:
 Debugger
 panic
 uma_dbg_free
 uma_zfree_arg
 ffs_ifree
 ufs_reclaim
 ufs_vnoperate
 vclean
 gdonel
 getnewvnode
 ffs_vget
 ufs_lookup
 ufs_vnoperate
 vfs_cache_lookup
 ufs_vnoperate
 lookup
 namei
 stat
 syscall
 Xint0x80_syscall
 
 Whee!

  geez, you're really hitting a lot of double frees.  Can the other
  people running -current under high load turn on INVARIANTS and see if
  they start hitting the double free problems, too?  I'd like some more
  evidence.

  Judging from the things we've seen from your traces I would guess at
  this point that there is a path somewhere that ends up in the ffs code
  without Giant, and that code fails to assert Giant requirements most
  of the time.  Maybe it's time we start sprinkling the GIANT_REQUIREDs
  where we know they belong...  that one we talked about adding the
  other day, did it catch anything?

-- 
Bosko Milekic  *  [EMAIL PROTECTED]  *  [EMAIL PROTECTED]
TECHNOkRATIS Consulting Services  *  http://www.technokratis.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ACPI battery state and resume not working on Inspiron 5150

2003-08-14 Thread Joe Marcus Clarke
On Wed, 2003-08-06 at 16:01, Joe Marcus Clarke wrote:
 On Wed, 2003-08-06 at 15:56, Barney Wolff wrote:
  On Wed, Aug 06, 2003 at 03:31:01PM -0400, Joe Marcus Clarke wrote:
   ACPI-1287: *** Error: Method execution failed
   [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST
  
  I would not expect BAT1 to exist unless you have 2 batteries installed.
 
 Ah, good point.  However, I don't see any battery sysctls, and I do have
 at least one battery installed.
 
  As to resume, on my I5000 it takes almost a minute to come back from
  S3, but does eventually come back on a -current from 7/30.
 
 Thanks for the suggestion.  I'll wait a bit longer.

Well, I waited for 10 minutes, but the laptop never came back.  The USB
wasn't reactivated, the network didn't come back, and the display stayed
black.  The only indication that it was no longer asleep was the power
light came back on.  Thanks anyway for the suggestion.

Joe

 
 Joe
-- 
PGP Key : http://www.marcuscom.com/pgp.asc




signature.asc
Description: This is a digitally signed message part


Re: bootstrapping network (bcm) on Dell D800

2003-08-14 Thread Dr. Richard E. Hawkins
On Wed, Aug 06, 2003 at 11:40:18AM -0400, Andre Guibert de Bruet wrote:

 On Wed, 6 Aug 2003, Dr. Richard E. Hawkins wrote:

  I finally figureed out that the removable floppy (which works both as an
  external usb and internall) is treated as a scsi device, not /dev/fd0.
  So I tried moving the drivers from the up to date machine.  No dice;
  they depend on another changed function.

  So I borrowed a usb zip drive, and found that a bzip2'd source tree is
  only 83M.  I've moved that, and have a new kernel compiling from a
  source tree updated this morning.  Am I going to have to do anything
  else to get the bge device detected, or will it just kernel installation
  and reboot take care of this?

 If you've compiled the driver into the kernel, all you'll have to do is
 configure the IP settings for the device. If you intend on using the
 kernel loadable module, you'll have to kldload it before you configure
 the network settings.

All is now well, and I have my regular programs building.  DHCP network
configuration even worked flawlessly.  I have a permanent IP for the
thing, but this (should) let me plug into the sockets at our main
library as well (and I assume it will give me less hassle with ppp,
too!)

thanks

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

-- 
Richard E. Hawkins, Asst. Prof. of Economics/\   ASCII ribbon campaign
[EMAIL PROTECTED]  Smeal 178  (814) 375-4700  \ /   against HTML mail
These opinions will not be those of  Xand postings. 
Penn State until it pays my retainer.   / \   
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ath0 driver

2003-08-14 Thread Sam Leffler
On Wed, 6 Aug 2003, Sam Leffler wrote:

 Shouldn't that be 0.9.5.2?  I run the latest current, and
 hw.ath.hal.version is 0.9.5.2.

You're right; I committed a slightly older version to FreeBSD than to
Linux.
Any chance that you could commit the newer version?  Or are the
differences too marginal?
There are no substantive differences.  The later version was created to 
identify some fixes specific to Linux.

	Sam

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


Re: vinum problems with todays current

2003-08-14 Thread Rob
Greg 'groggy' Lehey wrote:
On Tuesday,  5 August 2003 at 22:21:41 +0200, Rob wrote:

Poul-Henning Kamp wrote:

In message [EMAIL PROTECTED], Rob writes:


Hi all,

After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:

...
I noticed I had an older version of spec_vnops.c (1.205), so I
cvsupped again and build kernel, this gave me the same msgbuf error,
but with different values. Then I applied your patch and the error
messgae disapeared, but still my vinum doesn't come up.


Can I assume that this is related to GEOM, and not to Vinum?

Greg
--
See complete headers for address and phone numbers


After investigating a little further today, I found the config info on 
the drives to be mangled.

--
# rm -f log
# for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
(dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo)  log
done
# cat log
IN VINOx-server.debank.tvbCc3??Z${m5?
IN VINOx-server.debank.tvaC3?WPZ${m5?
--
I guess the drives can't be started again unless I have the parameters 
which I used during install (please say I'm wrong).

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


Re: dhclient problem with xl0

2003-08-14 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Martin Blapp wrote:
  dhclient is still relying on behavior from the kernel that isn't
  guaranteed.

 I know. But I'd consider that as a kernel bug, not dhclient fault.
 Would it help the set the card into promisc. mode anyway, even
 if we don't have link ?

Except that you've added code to dhclient that makes poor assumptions
about the ifmedia status word.  Its optional; for hardware that you can
detect media status it can be used to display the status.  For other
hardware, we shouldn't have to lie about media status; if the hardware
doesn't support reporting media status then we shouldn't do anything with
the status word.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: help! 5.1 doesn't do the rc thing?

2003-08-14 Thread Charlie Schluting

On Thu, 7 Aug 2003, Arjan van Leeuwen wrote:

 On Thursday 07 August 2003 20:05, Charlie Schluting wrote:
  On Thu, 7 Aug 2003, Scot W. Hetzel wrote:
   From: Charlie Schluting [EMAIL PROTECTED]
 
 Have you ran mergemaster already? It will take care of your /etc files (or at
 least it's supposed to).

 Arjan

Yes, of course :)
That's why I'm perplexed. I let it install the files it wanted to,
except for obvious things I didn't want overwritten: passwd file,
sendmail config, etc.

Just to verify: my old rc.conf should be read (and honored) right?

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


Re: ACPI battery state and resume not working on Inspiron 5150

2003-08-14 Thread Kevin Oberman
 From: Joe Marcus Clarke [EMAIL PROTECTED]
 Date: Thu, 07 Aug 2003 12:06:30 -0400
 
 
 --=-IkHq9Jbph/9SXjiWOYnQ
 Content-Type: text/plain
 Content-Transfer-Encoding: quoted-printable
 
 On Thu, 2003-08-07 at 10:31, Kevin Oberman wrote:
   From: Joe Marcus Clarke [EMAIL PROTECTED]
   Date: Wed, 06 Aug 2003 16:01:37 -0400
   Sender: [EMAIL PROTECTED]
  =20
  =20
   --=3D-MHp9eSkqmbnyoWl+2a1w
   Content-Type: text/plain
   Content-Transfer-Encoding: quoted-printable
  =20
   On Wed, 2003-08-06 at 15:56, Barney Wolff wrote:
On Wed, Aug 06, 2003 at 03:31:01PM -0400, Joe Marcus Clarke wrote:
 ACPI-1287: *** Error: Method execution failed
 [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST
   =3D20
I would not expect BAT1 to exist unless you have 2 batteries installe=
 d.
  =20
   Ah, good point.  However, I don't see any battery sysctls, and I do hav=
 e
   at least one battery installed.
  =20
As to resume, on my I5000 it takes almost a minute to come back from
S3, but does eventually come back on a -current from 7/30.
  =20
   Thanks for the suggestion.  I'll wait a bit longer.
 =20
  Well, I did some experimenting yesterday with the ACPI code on my IBM
  T30 and learned one thing...if you plan on suspending, you need to set
  a sleep delay. Before I set the delay I had some nasty problems
  because power went away immediately and the disk cache did not have a
  chance to flush (ouch!) and left the display where it should not be.
 =20
  I noticed that Windows XP has a delay of about 5 seconds. I set the
  sysctl and tried again and things went MUCH better. The suspend didn't
  leave the disk corrupt (whew!) and the display dropped to low
  resolution before the graphics was shut down and switched back on
  resume! My Radeon M7 even retained sync.
 =20
  Of course, the USB driver simply does not recover from a suspend on
  ACPI and this should be fixed before too long. Also, the backlight
  stays on making the suspend NVU (not very useful). But it is a huge
  improvement and adding a delay MAY help a lot of other laptop
  suspend/resume areas.=20
 =20
  Whether this will help th I5000 problems, I can't say, but it seems
  like suspend/resume is the most common show-stopper for ACPI on
  laptops, so it's worth a shot. If there is a trend that indicates that
  a short delay in suspending fixes a number of problems, the default
  delay should probably be modified from 0 to 4 or 5.
 
 I tried your suggestion, but this just prolonged the inevitable for 5
 seconds.  The laptop still remained dead to all input and no video after
 resume.

Sorry, Joe. By the way, are you suspending with acpiconf -s3? Have
you tried creating a hibernation partition (slice) and using -s4? That
appears to work better than suspend on most platforms that support
it at all.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Bootstrap: Machine keeps booting ? (boot0/mbr) ?

2003-08-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], [EMAIL PROTECTED]
 writes:

I have exactly the same problem.  I'm assuming that this was caused by
the changes committed by PHK.  See the [HEADSDOWN] swap_pager.c calming down
and the Weird reboots from bootmgr or loader threads.  He is looking at
it now and will probably be committing a fix.

Already committed.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


buildworld breaks

2003-08-14 Thread Lukas Ertl
Hi,

buildworld is current broken:

=== sys/boot/i386/libi386
cc -O -pipe -mcpu=pentiumpro -ffreestanding -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU 
-I/usr/src/sys/boot/i386/libi386/../../common 
-I/usr/src/sys/boot/i386/libi386/../btx/lib  
-I/usr/src/sys/boot/i386/libi386/../../../contrib/dev/acpica  
-I/usr/src/sys/boot/i386/libi386/../../.. -I. 
-I/usr/src/sys/boot/i386/libi386/../../../../lib/libstand/ -ffreestanding 
-mpreferred-stack-boundary=2   -c /usr/src/sys/boot/i386/libi386/biosacpi.c
In file included from /usr/src/sys/contrib/dev/acpica/acfreebsd.h:165,
 from /usr/src/sys/boot/i386/libi386/biosacpi.c:33:
/usr/obj/usr/src/i386/usr/include/ctype.h:88: error: syntax error before int
*** Error code 1

Stop in /usr/src/sys/boot/i386/libi386.
*** Error code 1

regards,
le

-- 
Lukas Ertl eMail: [EMAIL PROTECTED]
UNIX Systemadministrator   Tel.:  (+43 1) 4277-14073
Vienna University Computer Center  Fax.:  (+43 1) 4277-9140
University of Vienna   http://mailbox.univie.ac.at/~le/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ath0 driver

2003-08-14 Thread Sam Leffler
Ive got a Dlink DWL-G520 that Ive installed into a Freebsd system. Ive
set up  the card with the following
ifconfig_ath0=inet 10.0.0.1 netmask 255.255.255.0 ssid daves channel 10
media  DS11 mediaopt hostap
This system was cvsuped and buildworld about 3 days ago. The card appears
to  be working because when I try to connect with my PDA it shows full
Link and  quality, and when I ifconfig ath0 down , the link and quality
go down to  nothing.
However it doesn't give out dhcp addresses over this interface. Im sure 
my
dhcpd.conf is fine because I've used a similar one on a laptop = aka
wireless access point that worked very well. So I tried to use dstumbler
to  see if it could detect the PDA, however it gives me the following
error
 error: unable to ioctl device socket: Operation now in progress

and it stays that way.

Has anyone had this issue as well or now what it means?

Verify you have the latest HAL using

sysctl hw.ath

The version should be 0.9.5.3 or better (can't remember if I committed .4 
or .3).  If you have an old version update.  Otherwise you might try 
tapping 802.11 frames with tcpdump on the AP to see what's going on:

tcpdump -i ath0 -y IEEE802_11

As to dstumbler, it is intimately tied to the wi driver at the moment.  I 
have a version that works w/ wi and ath drivers but it's a major rewrite 
and incomplete.  If someone wants to pick it up I'd be happy to pass the 
(incomplete) work on...

	Sam

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


Re: busdma/scsi trm(4) related panic

2003-08-14 Thread Scott Long
I know what the problem is and I'm working on a patch right now.

Scott

Jon Kuster wrote:
On Wed, 2003-08-06 at 05:00, Craig Rodrigues wrote:

On Tue, Aug 05, 2003 at 11:08:33PM -0700, Jon Kuster wrote:

If there's anything you'd like me to type at the db prompt, just ask
and I'll send the output.
Send the backtrace, with the 't' command.


Here you go.  Once again, this was hand transcribed, so sorry for any
typos.
-Jon
db t
_bus_dmamap_load_buffer(c3fd3c40,c044660,c4193e84,24,0) at
_bus_dmamap_load_buffer+0x3ff
bus_dmamap_load(c3fd3c40,0,c4193e84,24,c01c9760) at bus_dmamap_load+0x6c
trm_action(c406c200,c418dc00,c0130cc4,c4193e00,c4193e00) at
trm_action+0x27a
xpt_run_dev_sendq(c406c1c0,c4193e18,1,7,4) at xpt_run_dev_sendq+0x192
xpt_release_devq_device(c4193e00,1,1,d68fbcec,c0243b5e) at
xpt_release_devq_device+0xe2
xpt_release_devq_timeout(c4193e00,c1521974,10,f8c6020d,c0131dd0) at
xpt_release_devq_timeout+0x21
softclock (0,0,0,0,c1521974) at softclock+0x24e
ithread_loop(c1520280,d68fbd48,0,0,c1520280) at ithread_loop+0x1c8
fork_exit(c021d770,c1520280,d68fbd48 at fork_exit+0xb1
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd68fbd7c, ebp = 0 ---
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


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


Re: ath0 driver

2003-08-14 Thread David Gilbert
 M == M Warner Losh [EMAIL PROTECTED] writes:

M The ath driver doesn't work with broadcom hardware.  You will need
M to write your own driver, or find someone else that can write a
M broadcom one for you.

OK ... so slap me down... Geez.  It certainly has been discussed that
the PCI vendor doesn't necessarily have anything to do with the
chipset.  Simple question ... so many snarky answers.

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


vinum problems with todays current

2003-08-14 Thread Rob
Hi all,

After cvs'upping (about 12 hours ago) and building world/kernel vinum 
stopped working. It does show my two disks but nothing more. I also 
get an error message right after the bootloader:

msgbuf cksum mismatch (read a5886, calc a5efb)
--
The output of vinum:
vinum - list
2 drives:
D b State: up   /dev/ad6s1e A: 
77903/77903 MB (100%)
D a State: up   /dev/ad4s1e A: 77903/77903 
MB (100%)

0 volumes:
0 plexes:
0 subdisks:
---
slopuh# uname -a
FreeBSD slopuh.debank.tv 5.1-CURRENT FreeBSD 5.1-CURRENT #20: Tue Aug 
 5 20:13:13 CEST 2003 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLOPUH  i386

I don't have debugging configured in the kernel, but can recompile if 
usefull.
Anyone with the same problems and/or ideas ?

Rob Evers

--
It is a book about a Spanish guy called Manual. You should read it.
   -- Dilbert
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: INET6 in world

2003-08-14 Thread David O'Brien
On Mon, Aug 04, 2003 at 04:08:23PM +0200, Bernd Walter wrote:
 That's chicken/egg - IPv6 never will be widely used if everyone thinks
 that way.
 The sense is to break this dependency loop by ecouraging everyone to
 use it and not to make it easier to completely disable the support.
 As I said: you -always- have an IPv6 connection to the outside world
 as long as you have a single official IPv4 address.
 Not using it because it doesn't fit in your current network is one
 point, but disabling it in a way to make a future step to IPv6
 harder is another.
 The number of IPv4 only systems is already big enough - we don't need
 to build new ones.

Machanism, not policy.  I would also like to run with NO_INET6.  IPv6
support has done nothing for me other than cause me problems.  I still
strongly disagree with our ordering of localhost in /etc/hosts.  My
system worked worlds better when I put the IPv4 localhost first.

We don't want to kill IPv6 support in FreeBSD -- we both fully know there
are areas of the world where is it a very useful if not mandatory thing.
However that isn't the case for the USA yet, and I'm guessing Germany
also.

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


Re: HEADSUP: pca driver being retired.

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
: In message [EMAIL PROTECTED], Mark Murray wr
: ites:
: 
: Would it be a useful exercise for the minority(?) of users who use this
: driver to either see if it can be effectively newbussed or turned into
: a port or both?
: 
: The main problem is the code which hi-jacks the i8254 and kicks off
: up to 2 interrupts per second.

That sounds lame, even as a port

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


Re: usbd does not use detach

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
Eric Jacobs [EMAIL PROTECTED] writes:
: #DETACH_FORCE: Clients using the device must be disconnected,
: #typically by revoking open file descriptors. May not
: #return EBUSY due to client activitiy, but may return
: #that or other errors due to hardware problems or
: #limitations.
: #
: #DETACH_EJECTED: This call is made from a lower-level bus   
: #driver when the device has been physically removed from
: #the system. Like DETACH_FORCE, except that drivers can
: #avoid attemping (and failing) to reset the hardware
: #state. This request must succeed.

These two are redundant.  Devices can already ask the bridge driver if
the device is still present on the bus.  Smart drivers already do
this, but most of the drivers in the tree are dumb.  You also have to
deal with device disappearance in ISRs since it is possible for the
device to go away while the device is in the middle of the ISR.  Some
bus technologies also allow interrupt entry when a card/device is
ejected.

: In addition, the DETACH_FORCE and DETACH_EJECTED flags could
: be mapped to appropriate flag values for the other subsystems, such
: as MNT_FORCE and (a new) MNT_EJECTED flag for VFS.

The problem is that when you are detaching a device, it is gone when
you return from the detach routine.  It can be hard to know what
buffers (disk, network, etc) in the system refer a given newbus device
because there's not a one to one mapping for the device_t to dev_t
that the rest of the system uses.  Devices may or may not know about
buffers that are outstanding.  Work would be needed in the buf/bio
system to reference cound the dev_t so that when the driver destroys
it, it doesn't go completely away until the reference count goes to
zero.  However, doing that may have unfavorable performance impacts.

:  i manually umount the device before unpluging it.
: 
: That is the only safe way to do it for now.

Agreed.

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


Re: Change to kernel+modules build approach

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
John Baldwin [EMAIL PROTECTED] writes:
: 
: On 14-Aug-2003 Ruslan Ermilov wrote:
:  On Thu, Aug 14, 2003 at 02:10:19AM -0600, Scott Long wrote:
:  Luoqi Chen wrote:
:  [...]
:  On the other hand, all modules should create all the opt_*.h files
:  it needs when built individually. Add opt_ddb.h to nullfs's Makefile
:  should fix the breakage.
:  
:  Our kernel build system isn't set up to handle passing config options
:  to modules.  Various solutions to this have been proposed, but nothing
:  has appeared yet.  In 5.x, we document that modules will not work with
:  PAE.
:  
:  How does the below look?  This is basically a more generic implementation
:  of Luoqi's idea, but for -CURRENT:
: 
: I would prefer something far more radical that would involve moving
: all the module metadata to sys/conf (i.e. removing sys/modules) and
: building all the modules based on a single kernel config file.

Does that mean that we're abandoning the idea that modules will work
with all kernels?  I don't disagree with the metadata move, since it
is duplicated in two places now and allows for some more interesting
subsettting, but I'm concerned that our third party ISVs will need to
generate N different modules for the system...

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


Re: usbd does not use detach

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
Daniel O'Connor [EMAIL PROTECTED] writes:
: It should also have a hint to indicate that this device could potentially go 
: away at any time, so it shouldn't cache anything if at all possible.
: (Although it would be good if the user could elect to override this in the 
: interests of performance)
: 
: I suspect that would require more significant changes though :)

I suspect that this would be as hard to implement as dealing with
things going away, and produce a system that is less desirable to
use.

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


Re: Change to kernel+modules build approach

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
John Baldwin [EMAIL PROTECTED] writes:
: 
: On 14-Aug-2003 Andrew Gallatin wrote:
:  
:  John Baldwin writes:
:
:On 14-Aug-2003 Ruslan Ermilov wrote:
: On Thu, Aug 14, 2003 at 02:10:19AM -0600, Scott Long wrote:
: Luoqi Chen wrote:
: [...]
: On the other hand, all modules should create all the opt_*.h files
: it needs when built individually. Add opt_ddb.h to nullfs's Makefile
: should fix the breakage.
: 
: Our kernel build system isn't set up to handle passing config options
: to modules.  Various solutions to this have been proposed, but nothing
: has appeared yet.  In 5.x, we document that modules will not work with
: PAE.
: 
: How does the below look?  This is basically a more generic implementation
: of Luoqi's idea, but for -CURRENT:
:
:I would prefer something far more radical that would involve moving
:all the module metadata to sys/conf (i.e. removing sys/modules) and
:building all the modules based on a single kernel config file.
:  
:  Would this tie modules to that kernel config?  If so, would it mean
:  the end of the ability of 3rd party developers to ship binary drivers
:  and expect them to work with any kernel?
: 
: Well, yes, but, one could always build generic modules by using
: a kernel config containing 'options KLD_MODULE' or some such.
: This would allow one to compile optimized modules if they wanted to,
: but still provide the ability to build fully generic modules.

This sounds like an either or choice.  I don't care too much if the
third party drivers aren't hyper optimzied for my kernel.  But to
force users of them to use some generic kernel would be a big support
nightmare.

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


Re: Change in application of default ACLs in UFS

2003-08-14 Thread Robert Watson

On Wed, 6 Aug 2003, Daniel C. Sobral wrote:

Note: this change contains a semantic bugfix for new file creation:
we now intersect the ACL-generated mode and the cmode requested by
the user process.  This means permissions on newly created file
objects will now be more conservative.  In the future, we may want
to provide alternative semantics (similar to Solaris and Linux) in
which the ACL mask overrides the umask, permitting ACLs to broaden
the rights beyond the requested umask.
 
 FWIW, I don't like it. This means I'll have to change my umask to o+rw
 for my ACLs to work correctly, since I use ACLs to _give_ rights in ways
 that umask cannot. 

I'm in the throes of implementing changes that push umask processing down
into individual file systems, permitting UFS ACLs to override the umask
using the ACL mask, which would reproduce the Solaris/Linux model
(non-POSIX.1e).  However, there are some interesting implementation
question shtere, so it will probably be a bit (perhaps a couple of weeks)
before I have a useful prototype worth reviewing.  I agree that those
semantics are useful, however :-).

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

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


Re: Change to kernel+modules build approach

2003-08-14 Thread Scott Long
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
John Baldwin [EMAIL PROTECTED] writes:
: 
: On 14-Aug-2003 Ruslan Ermilov wrote:
:  On Thu, Aug 14, 2003 at 02:10:19AM -0600, Scott Long wrote:
:  Luoqi Chen wrote:
:  [...]
:  On the other hand, all modules should create all the opt_*.h files
:  it needs when built individually. Add opt_ddb.h to nullfs's Makefile
:  should fix the breakage.
:  
:  Our kernel build system isn't set up to handle passing config options
:  to modules.  Various solutions to this have been proposed, but nothing
:  has appeared yet.  In 5.x, we document that modules will not work with
:  PAE.
:  
:  How does the below look?  This is basically a more generic implementation
:  of Luoqi's idea, but for -CURRENT:
: 
: I would prefer something far more radical that would involve moving
: all the module metadata to sys/conf (i.e. removing sys/modules) and
: building all the modules based on a single kernel config file.

Does that mean that we're abandoning the idea that modules will work
with all kernels?  I don't disagree with the metadata move, since it
is duplicated in two places now and allows for some more interesting
subsettting, but I'm concerned that our third party ISVs will need to
generate N different modules for the system...
Warner
I can tell you first hand that this is painful.  However, in the case of
PAE, it's somewhat neccessary since certain fundamental types change
size.  I can envision solutions for this, but I'm not sure if they are
less painful than just dealing with multiple module builds.
Scott

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


Re: problems with wi driver.

2003-08-14 Thread M. Warner Losh
: Is there a better way to toggle the start address  for 16 bit and 32 bit
: cards with sysctl??

u_long cbb_start_16_io = CBB_START_16_IO;
TUNABLE_INT(hw.cbb.start_16_io, (int *)cbb_start_16_io);
SYSCTL_ULONG(_hw_cbb, OID_AUTO, start_16_io, CTLFLAG_RW,
cbb_start_16_io, CBB_START_16_IO,
Starting ioport for 16-bit cards);


so hw.cbb.start_16_io

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


Re: Change to kernel+modules build approach

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
Scott Long [EMAIL PROTECTED] writes:
: I can tell you first hand that this is painful.  However, in the case of
: PAE, it's somewhat neccessary since certain fundamental types change
: size.  I can envision solutions for this, but I'm not sure if they are
: less painful than just dealing with multiple module builds.

Personally I think that pae should be its own port, much like pc98 is
its own port, although much smaller in scope.  It has a few,
fundamental differences from the stock i386 port.  Since the data
type sizes are different with PAE there's no way around that.

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


Re: Dhclient fix for systems with media settings

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED]
Martin Blapp [EMAIL PROTECTED] writes:
:  Is this going to cure the cases where using DHCP results in my network
:  link going dead about ~30 minutes after getting a lease? At that point
:  it starts spitting out timeout errors and stuff, and i have to
:  unplug/replug the card and re-start dhclient to get connectivity again..
: 
: Unless the lease time was ~30 minutes and you've changed networks, I doubt it.
: 
: This sounds like a if_wi driver problem. Warner should be able to tell you
: more.

I still don't have a clear problem statement.

Warner
___
[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-08-14 Thread John Birrell
On Mon, Aug 04, 2003 at 10:45:39PM -0700, Stephen Casner wrote:
 I tried what I thought might be the equivalent patch (eliminating an
 else clause), but it did not solve the problem.  In 4.8-RELEASE I
 sometimes get a system hang and sometimes not, but even when it does
 not hang, I just get Device not configured when I try to mount
 /dev/acd0c.  The output I get is:
 
  /kernel: pccard: card inserted, slot 0
  pccardd[49]: Card  (NinjaATA-) [V1.0] [AP00 ] matched   (NinjaATA-) 
 [(null)] [(null)]
  /kernel: ata2 at port 0x180-0x187,0x386 iomem 0xd4000-0xd4fff irq 9 slot 0 on 
 pccard0
  pccardd[49]: ata2: NinjaATA inserted.

I saw similar behaviour with STABLE when trying to use a CompactFlash card
on a CPU board that didn't support the default range of I/O ports. This might
not be the case you have, but I saw output just like that quoted above. The
ata device gets reported, but there is no 'ad' device following it like there
normally is.

In my case the solution was to use the I/O port range hidden in the manufacturer's
notes on their web site. Once I set the port range in /etc/pccard.conf to
override the default, the CompactFlash card worked fine.

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


Re: problem with nvidia graphics card and -current

2003-08-14 Thread Glenn Johnson
On Tue, Aug 05, 2003 at 02:38:05PM +1000, Alastair G. Hogge wrote:

 On Tuesday, 05 August 2003 14:34, Matthew N. Dodd wrote:

  On Mon, 4 Aug 2003, Glenn Johnson wrote:
 
   Question for the developers: Is there someway to avoid having
   the combination of vesa and nvidia cause a total lockup of the
   machine?  I have a feeling I may not be the last person to try the
   nvidia driver with vesa enabled, either as a module, or compiled
   in the kernel.
 
  I'm running a system with the VESA stuff compiled in; the nvidia
  drivers work just fine.
 
  IIRC you're running with ACPI; try not doing that.

 I'm also running a system with the vesa module loaded. I'm also
 running ACPI.

Hmm, the only other thing I can offer here is that I had the console
screen set to -g 100x37 VESA_800x600.  How does that fit into the
picture?  Perhaps I could have left vesa in but just set the resolution
to something else.

Perhaps the machine just has quirky hardware.  It is a VIA KT-133
chipset, Athlon-tbird processor.

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


Re: Weird reboots from bootmgr or loader

2003-08-14 Thread Lukas Ertl
On Tue, 5 Aug 2003, Florian Smeets wrote:

 I got a really anoying Problem today. 3 different boxes started to reboot
 when i hit enter at the bootmgr, or when i don't hit enter and wait for it
 to boot FreeBSD it reboots when the loader should apear. I can see that it
 prints out some numbers but its to fast to recognise anything. I did not
 mess with the disk configuration on any of the boxes. I only rebuild world
 and kernel as usual every few days. They all had sources from 3rd or 4th
 of august. I don't have my serial cable handy i'll try to get it back this

I saw _exactly_ the same problem on one of my boxes today: it was
shutdowned correctly yesterday, and today it wouldn't boot, but panic
right after boot0. The only thing I could see were some hex numbers and
BTX halted for a split second, then immediately reboot. It's a -current
box from Sunday evening CEST.

I managed to fix it by booting from floppies and running the Fixit floppy,
writing a new disklabel, which seems to have become corrupted somehow.

HTH,
regards,
le

-- 
Lukas Ertl eMail: [EMAIL PROTECTED]
UNIX Systemadministrator   Tel.:  (+43 1) 4277-14073
Vienna University Computer Center  Fax.:  (+43 1) 4277-9140
University of Vienna   http://mailbox.univie.ac.at/~le/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Crash in g_dev_strategy / CURRENT as of yesterday.

2003-08-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Eivind Olsen writes:
--On 12. august 2003 20:39 +0100 Peter Edwards 
[EMAIL PROTECTED] wrote:
 # 10 0xc04f3c65 in trap (frame=
   {tf_fs = -1059913704, tf_es = -890109936, tf_ds = -1070268400,
 tf_edi
 = -1040540480, tf_esi = -978597456, tf_ebp = -890095148, tf_isp =
 -890095220, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 16343040,
 tf_trapno = 12, tf_err = 2, tf_eip = -1070560519, tf_cs = 8, tf_eflags
 =
 66054, tf_esp = -978597456, tf_ss = -1067143852}) at
 /usr/src/sys/i386/i386/trap.c:420
 Look at tf_eip: -1070560519 = 0xc0308af9
 What does list *0xc0308af9 show in gdb?

(kgdb) list *0xc0308af9
0xc0308af9 is in g_dev_strategy (/usr/src/sys/geom/geom_dev.c:401).
396 KASSERT(cp-acr || cp-acw,
397 (Consumer with zero access count in g_dev_strategy));
398
399 bp2 = g_clone_bio(bp);
400 KASSERT(bp2 != NULL, (XXX: ENOMEM in a bad place));
401 bp2-bio_offset = (off_t)bp-bio_blkno  DEV_BSHIFT;
402 KASSERT(bp2-bio_offset = 0,
403 (Negative bio_offset (%jd) on bio %p,
404 (intmax_t)bp2-bio_offset, bp));
405 bp2-bio_length = (off_t)bp-bio_bcount;
(kgdb)

Ohh, damn, I still have that stuff uncommitted.  Will fix!

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [acpi-jp 2583] ACPI sleep_delay caused reboot

2003-08-14 Thread Nate Lawson
On Mon, 11 Aug 2003, Anish Mistry wrote:
 I cvsup'd over the weekend and my laptop started to reboot after the second
 resume.  I checked the hw.acpi.sleep_delay and the default value seems to be
 changed to 5.  This would happen with earlier ACPI imports, but the default
 was zero, so it would be fine.  Can't seem to get and crash dumps since it
 just restarts.  I'll send the dmesg and acpidump info when I'm back at home.
 - --
 Anish Mistry

For a workaround, do:
  echo hw.acpi.sleep_delay=0  /etc/sysctl.conf

Unfortunately, we can't have it both ways and the delay helps some users
so you'll have to use this until we find what's wrong.

-Nate
___
[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 Garrett Wollman
On Mon, 11 Aug 2003 11:24:13 -0500, Jonathan Fosburgh [EMAIL PROTECTED] said:

 - Windows on the same loop as anything else
 Liberal use of zoning should help that.  Each Windows HBA should be in a 
 seperate zone.  This is from personal experience and also assumes you are 
 using a switched fabric.

I said ``loop'' for a reason.

The configuration that we were sold is pure FC-AL.  No fabrics.  Don't
do that, it's bad for your sanity.  If you can't afford a switch, you
can't afford Fibre Channel.

-GAWollman

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


Re: Weird reboots from bootmgr or loader

2003-08-14 Thread haro
Hi,

I also got the same BTX error during boot up. :(
I used 4.8-RELEASE CD to boot till loader starts up,
changed currdev/loaddev/kernel etc to the -CURRENT setting
and let system boot.

From: Florian Smeets [EMAIL PROTECTED]
Date: Wed, 6 Aug 2003 09:43:18 +0200 (CEST)
::quote who=Lukas Ertl
:: On Tue, 5 Aug 2003, John-Mark Gurney wrote:
::
:: Are you running -current w/ a kernel from the last 24 hrs?  (After
:: phk's mass swap check in?)  If so, make sure your swap isn't at the
:: start of your disk.  If it is, phk was nice enough to only blow away
:: your boot blocks instead of your disk label too. :)  Swap currently
:: uses all but the first page (4k on i386).
::
:: Argl, YES, swap _is_ the first partition:
::
::Yes same here!

Same here, as well. :(

::
:: Does that mean I have to rearranged or never build world again?
::
::Yeah good question, what can we do ?

May be, we have to run 'bsdlabel -B' just before shutting down
system, everytime, until it gets fixed. :(

Regards,
 Haro
=---
   _ _Munehiro (haro) Matsuda
 -|- /_\  |_|_|   Kubota Graphics Technology Inc.
 /|\ |_|  |_|_|   2-8-8 Shinjuku, Shinjuku-ku Tokyo 160-0022, Japan
  Tel: +81-3-3225-0767  Fax: +81-3-3225-0740
  Email: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...

2003-08-14 Thread David R. Colyer
No doubt this has been answered before, but I have an asus p4pe with a 3.06 
p4.  Naturally, it is enabled in the bios.  To enable hyperthreading do I 
need to recompile my kernel with smp support, and if so...does this apply to 
freebsd 5.1 release as well?  (my friend wants to know).  Additionally does 
changing the machdep.cpu_idle_hlt to zero make it faster?  Thanks in advance.

David R. Colyer


On Wednesday 13 August 2003 10:52 am, John Baldwin wrote:
 On 13-Aug-2003 Dr. Richard E. Hawkins wrote:
  On Wed, Aug 13, 2003 at 11:35:14AM -0400, John Baldwin wrote:
  On 13-Aug-2003 Dr. Richard E. Hawkins wrote:
   On Tue, Aug 12, 2003 at 08:33:57PM -0500, Cagle, John (ISS-Houston) 
wrote:
   I think the valid settings are only 0 or 1, with the default being 1
   which will disable all logical CPUs.  If you want to enable the extra
   logical CPUS, then set it to 0 (zero).  They will come online
   immediately.
  
   That can't be right.  I've never done anything to configure the
   logical cpus on mine; they just showed up unexpectedly when i switched
   from stable to current.  Now I have:
  
   slytherin ttyp1:hawksysctl -a |  grep cpu
   kern.threads.virtual_cpu: 4
   kern.ccpu: 1948
   kern.smp.cpus: 4
   hw.ncpu: 4
   machdep.cpu_idle_hlt: 1
   machdep.hlt_cpus: 10
   machdep.hlt_logical_cpus: 1
   machdep.logical_cpus_mask: 10
  
   It launches four logical cpus all on it's own.  It did panic during
   shutdown yesterday; If I read the messages right as it flashed by, it
   was because cpu#2 got the shutdown order.
 
  Your logical CPU's aren't doing anything though, even though they are
  started up.  John's explanation is correct.
 
  I've also got the report in dmesg,
 
  SMP: AP CPU #1 Launched!
  SMP: AP CPU #2 Launched!
  SMP: AP CPU #3 Launched!
 
 
  Doesn't this mean that they *are* active?

 No, it means the kernel has started them up.  CPU's whose bits are set
 in machdep.hlt_cpus don't execute any user tasks.  Instead, they just
 sit in a loop executing the 'hlt' instruction doing nothing but servicing
 interrupts.

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


Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...

2003-08-14 Thread Brooks Davis
On Thu, Aug 14, 2003 at 09:59:58AM -0600, David R. Colyer wrote:
 No doubt this has been answered before, but I have an asus p4pe with a 3.06 
 p4.  Naturally, it is enabled in the bios.  To enable hyperthreading do I 
 need to recompile my kernel with smp support, and if so...does this apply to 
 freebsd 5.1 release as well?  (my friend wants to know).  Additionally does 
 changing the machdep.cpu_idle_hlt to zero make it faster?  Thanks in advance.

Yes, you need SMP support in all releases.  As to your second question,
define faster.  It depends heavily on your appliction mix.  My guess is
that on a UP system which is doing something other then running a single
compute bound process it's going to be a minor win, but only measurement
will tell you anything.

-- Brooks


pgp0.pgp
Description: PGP signature


Re: HEADSUP: pca driver being retired.

2003-08-14 Thread Julian Elischer
Well I'm not too happy about this..

It's the only audio I have on my TI-810 laptop.
That is however not running -current yet.

I'm also not pleased from the perspective that this is the only 
major example in the tree of how to use the clock-speedup 
code in i386/isa/clock.c. A very nice piece of functionality I use quite
often.

What is youir reason for shooting a working piece of code?
(well it works in 4.x.. I haven't tried it in 5.x?)
(other than it offends you in some way)


On Wed, 13 Aug 2003, Poul-Henning Kamp wrote:

 
 I plan to remove the pca driver in about a week.
 
 Protest only from actual users respected.
 
 If you don't know what pca is or what it does, do not even send email.
 
 Thank you!
 
 -- 
 Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
 [EMAIL PROTECTED] | TCP/IP since RFC 956
 FreeBSD committer   | BSD since 4.3-tahoe
 Never attribute to malice what can adequately be explained by incompetence.
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

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


Re: [PATCH] jail NG schript patch for mounting devfs andprocfsautomatically

2003-08-14 Thread Scot W. Hetzel
I just noticed a problem with periodic scripts inside a jail.  I'm getting:

Local system status:
tee: /dev/stderr: Operation not supported

Mail in local queue:
tee: /dev/stderr: Operation not supported

Mail in submit queue:
tee: /dev/stderr: Operation not supported

in the periodic daily, weekly, monthly and security reports.  But if I mount
the fdescfs on the jail, then these errors go away.

So we need to add the following to the new jail script

jail_start()
{
:
eval jail_devfs=\\$jail_${_jail}_devfs\
[ -z ${jail_devfs} ]  jail_devfs=NO:

eval jail_fdescfs=\\$jail_${_jail}_fdescfs\
[ -z ${jail_fdescfs} ]  jail_fdescfs=NO
:
if checkyesno jail_devfs ; then
mount -t devfs dev ${jail_devdir}
if checkyesno jail_fdescfs ; then
mount -t fdescfs fdesc ${jail_devdir}/fd
fi
:
fi
:
}

jail_stop()
{
:
eval jail_devfs=\\$jail_${_jail}_devfs\
[ -z ${jail_devfs} ]  jail_devfs=NO:

eval jail_fdescfs=\\$jail_${_jail}_fdescfs\
[ -z ${jail_fdescfs} ]  jail_fdescfs=NO
:
if checkyesno jail_devfs ; then
if [ -d ${jail_devdir} ] ; then
if checkyesno jail_fdescfs; then
umount -f ${jail_devdir}/fd /dev/null 21
fi
umount -f ${jail_devdir} /dev/null 21
fi
fi
:
}

The only decsion we need to make is wheter to always mount the fdescfs when
devfs is mounted on the jail, or have a variable to enable mounting of the
fdescfs (jail_*_fdescfs).

Scot

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


Re: ffsinfo missing in 5.1-RELEASE

2003-08-14 Thread Lukas Ertl
On Wed, 13 Aug 2003, Robert Watson wrote:

 The only problem with this patch is that we lose the ability to do the
 START BLOCK SUMMARY AND POSITION TABLE display for UFS1.  I'm not sure
 this is a big issue; I will go ahead and commit it with those #ifdef'd
 out (rather than removed as is the case in the patch) and look for advice
 on reintroducing them from someone with more UFS expertise than me.

Robert,

I'll have a look at it once it's back in the tree, maybe I find out what
to do about it.

regards,
le

-- 
Lukas Ertl eMail: [EMAIL PROTECTED]
UNIX Systemadministrator   Tel.:  (+43 1) 4277-14073
Vienna University Computer Center  Fax.:  (+43 1) 4277-9140
University of Vienna   http://mailbox.univie.ac.at/~le/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: kernel hangs at serial port during boot (solved)

2003-08-14 Thread walt
walt wrote:

 sio0: configured irq 4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 boot hangs forever at this point
I changed the Plug-n-Play BIOS setting and now it works
normally again.
I also changed the ACPI-aware-OS BIOS setting to YES
and I notice that the acpi.ko module is now loading
at boot, which it didn't before.  I think this is an
old thing that I didn't notice until today, however.
What surprised me is that the machine has been working
for years with the 'wrong' BIOS setting and just now
stopped working.
Were there some kernel changes recently which would
account for this?


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


clock works slowly when I change CPU speed

2003-08-14 Thread MATOBA Hirozumi
I have a problem about clock when I change CPU speed (hw.acpi.cpu). 

The default hw.acpi.cpu status of my ThinkPad A22e is

# sysctl hw.acpi.cpu

hw.acpi.cpu.max_speed: 8
hw.acpi.cpu.current_speed: 8
hw.acpi.cpu.performance_speed: 8
hw.acpi.cpu.economy_speed: 4

and, the clock value of top tool updates per 2 seconds normally, 
like as 01:21:45, 01:21:47, 01:21:49,...
(because the default delay between updates is 2 seconds)

When I change CPU speed as

sysctl -w hw.acpi.cpu.performance_speed=4

the clock value of top tool updates by 1, per 2 seconds, 
like as 01:22:45, 01:22:46, 01:22:47,..., but per 2 seconds. 
So, the clock of top tool works on half speed of the real world. 
(I compare the clock value of top tool
 and the clock value of my video recorder. 
 The problem also occur when I restart top tool after changing CPU speed)

This problem occurs not only to using top tool, 
but to executing while :; do date; sleep 1; done on bash prompt, 
(When CPU speed is 4, the time value updates by 1 per 2 seconds)
and to executing kldload snd_ich by hand after booting.
(When CPU speed is not 8, the result of link rate is wrong. 
 The normal value is about 48000 Hz, 
 but when CPU speed is 4, it gets double value of normal link rate)

This problem did not exist when I did cvsup on Aug 2. 
This problem exists since when I did cvsup on Aug 9. 
I did cvsup on Aug 13 again, but this problem still exists. 

And, when I use backuped kernel of Aug 2, 
by changing value of module_path on boot prompt, 
this problem does not occur. 
(So I do not think my ThinkPad A22e has broken)

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


Re: TESTERS WANTED for ATAng preview 1

2003-08-14 Thread Eirik Oeverby
Hi,

I've just compiled ATAng into my kernel, and I'm currently running it -
but I had to rip out my CD-ROM to make it work. I wasn't able to grab
the exact wording of the error, but it was something along the lines of
a failure to identify ata1-slave - which I suppose is my CD-ROM player.
It then retries and gets an error (error=0), then freezes.

This is a IBM ThinkPad T21, so taking out the CD-ROM is a trivial task,
but at some point I'm gonna need it again (it's actually a DVD/CD-RW
combodrive)...

Otherwise the driver seems to work with the 60gb IBM drive I have in my
laptop. No funny behaviour so far. ;)

Best regards,
/Eirik


pgp0.pgp
Description: PGP signature


Re: FreeBSD 5.1-R kernel panic

2003-08-14 Thread Bosko Milekic

On Thu, Aug 14, 2003 at 10:57:07AM -0600, Stephane Raimbault wrote:
 Hi Bosko,
 
 This is the output of sysctl vm.zone about 2 minutes before the crash
 occured.  let me know if there is anything else I can provide you for this
 crashing problem.

  H.  I don't know, maybe you really do have a machine too loaded
  for the KVA you have configured...

  I have to re-iterate that it's extremely important that you
  double-check that you are in fact in sync with the latest -current and
  _NOT_ RELENG_5_1.  Make sure you're building at least version 1.73 of
  src/sys/vm/uma_core.c (grep FBSDID src/sys/vm/uma_core.c).

  With that said, you can try the following:

  options KVA_PAGES=400

  in your kernel configuration file.

  Following that, you can do this:

  kern.vm.kmem.size=4

  In your /boot/loader.conf

  Make sure to not set NMBCLUSTERS too high.  Around 8K is probably more
  than enough, but you should look at how much you're using on average
  with `netstat -m' and then set the number to roughly 3 times that.

  If following this your crash persists, even if after a longer time,
  then I would suspect (another?) race.  Again, I have to re-iterate
  that you really need to make sure you're supping to HEAD:

  *default release=cvs tag=.

Regards,
-- 
Bosko Milekic  *  [EMAIL PROTECTED]  *  [EMAIL PROTECTED]
TECHNOkRATIS Consulting Services  *  http://www.technokratis.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ffsinfo missing in 5.1-RELEASE

2003-08-14 Thread Robert Watson

On Thu, 14 Aug 2003, Lukas Ertl wrote:

 On Wed, 13 Aug 2003, Robert Watson wrote:
 
  The only problem with this patch is that we lose the ability to do the
  START BLOCK SUMMARY AND POSITION TABLE display for UFS1.  I'm not sure
  this is a big issue; I will go ahead and commit it with those #ifdef'd
  out (rather than removed as is the case in the patch) and look for advice
  on reintroducing them from someone with more UFS expertise than me.
 
 I'll have a look at it once it's back in the tree, maybe I find out what
 to do about it. 

It's in my commit queue for today, so hopefully that opportunity will come
quickly :-).  I haven't managed to track down much about cg_blks() yet --
it disappeared with UFS2 coming in, so it will probably just take checking
out an older tree and pushing it forward again for UFS1 dumping.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


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


Re: M_NOTIFICATION in sys/mbuf.h?

2003-08-14 Thread Sam Leffler
While trying to port the SCTP-KAME code to CURRENT,
I noticed that M_NOTIFICATION is missing from sys/mbuf.h
in CURRENT, but it is present in the KAME version of this
file.
Any reason not to apply this patch?

--- sys/sys/mbuf.h.orig Sat Sep 13 19:34:07 2003
+++ sys/sys/mbuf.h  Sat Sep 13 19:34:14 2003
@@ -164,6 +164,8 @@
 #defineM_FIRSTFRAG 0x1000  /* packet is first fragment */
 #defineM_LASTFRAG  0x2000  /* packet is last fragment */
+#define M_NOTIFICATION 0x8000  /* notification event */
+
 /*
  * External buffer types: identify ext_buf type.
  */
I don't know what M_NOTIFICATION is used for but if it's applied sparingly 
it might be better to use an m_tag instead.

	Sam

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


  1   2   3   4   >