hang while installing freebsd-5.2 beta from cd-rom

[Jay Buhner]

Hi,

I just bought a new WD 160GB disk and tried to attach
it to my system which is running FreeBSD 4.5-STABLE.
The system panics during the boot process, so I
figured this would be a good opportunity to try out
FreeBSD-5.2 BETA.

I burned a cd with the freebsd 5.2 beta mini iso
image, and then tried to install.  During the boot
process, just after the disks are sensed, the system
hangs (the sysinstall screen is never reached).  I
booted the system in verbose mode, and here is the
output before the hang (I would have included the
entire output, but I'd have to type it all in by
hand):

ar: Promise check1 failed
ata3-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin
ata3-master: setting PIO4 on Promise PDC20265 chip
ata3-master: setting UDMA100 on Promise PDC20265 chip
GEOM: create disk ad6 dp=0xc31ea760
ad6: WDC WD1600JB-00FUA0/15.05R15 ATA-6 disk at
ata3-master
ad6: 152627MB (312581808 sectors), 310101 C, 16 H, 63
S, 512 B
ad6: 16 secs/int, 1 depth queue, UDMA100
GEOM: new disk ad4
GEOM: new disk ad5
GEOM: new disk ad6


Other relevant details:  The system has an AMD K7
processor, 256MB of memory, an ASUS A7V motherboard,
with a Promise Ultra100 ata controller on the
motherboard.  The other 2 disks attached to the
promise controller are recognized as
IBM-DLTA-307045/TX60A50C disks.

Any suggestions for how to debug this further?



__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

-current lockup (how to diagnose?)

[Jun Kuriyama]

I got lockups in recent -current box.  This box is my main workstation
and usually be up to date kernel.

In recent days, I usually locked up.  This is not a panic, only locks
up.  My situation is:

o KDE's clock is working.
o KDE's virtual screen switching is working.
o Apache does not reply on 80/tcp from remote.
o ssh from this box is still working.
o zsh on this box does not go next prompt when I press enter key at
  promprt.

It looks kernel is working, but fork/exec is not working when I enter
to this situation.

So, what can I diagnose with this situation?  Of course this box has
serial console.


-- 
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: -current lockup (how to diagnose?)

[Soren Schmidt]

It seems Jun Kuriyama wrote:
 
 I got lockups in recent -current box.  This box is my main workstation
 and usually be up to date kernel.
 
 In recent days, I usually locked up.  This is not a panic, only locks
 up.  My situation is:
 
 o KDE's clock is working.
 o KDE's virtual screen switching is working.
 o Apache does not reply on 80/tcp from remote.
 o ssh from this box is still working.
 o zsh on this box does not go next prompt when I press enter key at
   promprt.
 
 It looks kernel is working, but fork/exec is not working when I enter
 to this situation.

Hmm, I've been seeing something semilar a couble of times, can you do a
ps -axl and see if those processes hang around in vm ?

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

Re: 5.2-BETA boot failure

[Oliver Brandmueller]

Hi.

On Sun, Nov 30, 2003 at 08:08:37PM -0800, Jerry Keefe wrote:
 I tried upgrading a Dell Optiplex GXa from Release 5.1p10 to the 5.2
 Beta using the mini-install CD.  The system hangs in the boot loader. 
 This problem doesn't happen with the Release 5.1 CDs.
 
 I then tried upgrading from source after getting CURRENT as of
 11/29/2003, and was able to build and install the new GENERIC kernel.
 Upon reboot, the system hangs in the same way as when booting from the
 mini-install CD.
 
 The only thing unusual about this machine is that the onboard EIDE
 controller is disabled, and a PCI EIDE controller has been added.
 
 The system doesn't seem to get far enough to get a dmesg output or a
 backtrace out of this, but here's a transcript of the last few lines if
 it helps.
 
 Timecounters tick every 10.000 msec
 ata2-master: WARNING - SETFEATURES recovered from missing interrupt
 ata2-master: WARNING - SETFEATURES recovered from missing interrupt
 ata2-slave: WARNING - SETFEATURES recovered from missing interrupt
 ata2-slave: WARNING - SETFEATURES recovered from missing interrupt
 ad4: WARNING - SETFEATURES recovered from missing interrupt
 ad4: WARNING - SETFEATURES recovered from missing interrupt
 ad4: WARNING - SET_MULTI recovered from missing interrupt
 GEOM: create disk ad4 dp=0xc23ce960
 ad4: 19541MB Maxtor 52049U4 [38703/16/63] at ata2-master UDMA66
 ad5: WARNING - SETFEATURES recovered from missing interrupt
 ad5: WARNING - SETFEATURES recovered from missing interrupt
 ad5: WARNING - SET_MULTI recovered from missing interrupt
 GEOM: create disk ad5 dp=0xc23ce660
 ad5: 4121MB Maxtor 90432D2 [8374/16/63] at ata2-master UDMA33
 ata3-master: WARNING - SETFEATURES recovered from missing interrupt
 ata3: resetting devices ..
 
 machine is hung at this point.

I see a similar behaviour since somwhere shortly before 5.2-BETA on my 
HP OmniBook 500: If I try to boot with the base station attached (which 
includes an additional ATA Channel with an CDROM Drive attached), I see 
the same messages as you see for ata3-master (which is exactly where the 
CDROM resides). If I remove the CDROM from the base station, so the ATA 
channel is still there, but with no devices, I have no problems booting. 
I don't have other devices (like harddisks) to test this behaviour with.

Booting with the CDROM worked until well a few weeks ago, I cannot 
tell exactly, because I don't use it very often.

- Oliver

-- 
| Oliver Brandmueller | Offenbacher Str. 1  | Germany   D-14197 Berlin |
| Fon +49-172-3130856 | Fax +49-172-3145027 | WWW:   http://the.addict.de/ |
|   Ich bin das Internet. Sowahr ich Gott helfe.   |
| Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

bug in CD9660 path handling in libstand (effects boot code)

[Matthew Dillon]

This fixes a bug where an attempt to load a file path which contains
an intermediate path element which is a file on the CD rather then
a directory results in the file being accessed like a directory... which
can lockup the boot code.

The fix is simple.  Check to see if an intermediate path element really
represents a directory and return ENOENT if it doesn't.

This situation can occur due to searches via the module search path.

-Matt
Matthew Dillon 
[EMAIL PROTECTED]

Index: cd9660.c
===
RCS file: /cvs/src/lib/libstand/cd9660.c,v
retrieving revision 1.3
diff -u -r1.3 cd9660.c
--- cd9660.c8 Aug 2003 04:18:34 -   1.3
+++ cd9660.c1 Dec 2003 08:37:25 -
@@ -372,7 +372,13 @@
rec = *dp;
while (*path  *path != '/') /* look for next component */
path++;
-   if (*path) path++; /* skip '/' */
+   if (*path == '/') { /* skip /, make sure is dir */
+   path++;
+   if (*path  (isonum_711(dp-flags)  2) == 0) {
+   rc = ENOENT;/* not directory */
+   goto out;
+   }
+   }
}
 
/* allocate file system specific data structure */
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic on 5.2 BETA: blockable sleep lock

[Roger Hardiman]

Hi

Please can someone commit the bktr patch for me to fix 5.2-BETA
(as long as re@ approve). I don't have the resources.


 I'm not suprised that I haven't heard from him because this issue came up
at the
 start of the Thanksgiving holiday weekend.

If only it were that simple. Actually I'm English and we don't have
Thanksgiving.

I'm not doing much work on FreeBSD (or OpenH323) at the moment due to lack
of free time and
a lack of resources.
My new job does not involve FreeBSD (or any unix systems) or Video
Conferencing.
When I can find spare time at home, I only have a P350 + 56k modem.
In the New Year I'll upgrade my PC, find someone to get me ISOs and then
I'll be back in business.

Roger


   The problem is that selrecord() wants to lock a MTX_DEF mutex, which
can
   cause a context switch if the mutex is already locked by another
thread.
   This is contrary to what bktr_poll() wants to accomplish by calling
   critical_enter().
  
   Strange enough that does not seem to happen with a kernel built
without
   INVARIANTS and WITNESS. Does this make any sense or is this just by
   chance?
 
  You might try the patch below with WITNESS enabled.  I don't have the
  hardware, so I can't test it.  It compiles for me, but for all I know
it
  could delete all your files if you run it.
 
  Any chance for getting this committed?

 I've been forwarding these messages to the bktr maintainer listed in
 /usr/src/MAINTAINERS, in case he isn't subscribed to [EMAIL PROTECTED]  I'm not
 suprised that I haven't heard from him because this issue came up at the
 start of the Thanksgiving holiday weekend.  Commiting the patch will
 also require re approval because of the code freeze in preparation for
 5.2-RELEASE.



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

Re: panic on 5.2 BETA: blockable sleep lock

[Don Lewis]

On  1 Dec, Roger Hardiman wrote:
 Hi
 
 Please can someone commit the bktr patch for me to fix 5.2-BETA
 (as long as re@ approve). I don't have the resources.

If you're happy with the patch, I'll pursue re@ approval for the commit.

 I'm not suprised that I haven't heard from him because this issue came up
 at the
 start of the Thanksgiving holiday weekend.
 
 If only it were that simple. Actually I'm English and we don't have
 Thanksgiving.

Sorry, I guess I should have fired up xearth ;-)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

A page fault in subr_turnstile.c:propogate_priority()

[Igor Sysoev]

I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.


Igor Sysoev
http://sysoev.ru/en/

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

Is booting/installing from USB CDROM considered supported?

[Martin Nilsson]

I tried to install our CD/FDD-less servers from a CD-RW drive connected 
on the USB port, the bootloader complains about not ufs and wants me 
to enter a new boot device. This is 4.9-Release

On a late October current the system reboots.

I'll try with a fresh 5.2-BETA later today and see what happens with it. 
in the meantime I just want to ask:

Is booting the install CD over a USB connected CDROM supposed to be 
working?





---
Martin Nilsson, CTO  Founder, Mullet Scandinavia AB, Malmö, SWEDEN
E-mail: [EMAIL PROTECTED], Phone: +46-(0)708-606170, http://www.mullet.se
Our business is well engineered servers optimized for FreeBSD and Linux.

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

Can we get rid of kerb5 redefining macros?

[David O'Brien]

Ever since kerberos5 got hooked up to the build by default I'm getting
*TONS* (758) of CPP macros.  An example is:

In file included from /usr/obj/usr/src/kerberos5/lib/libasn1/roken.h:77,
 from /usr/src/crypto/heimdal/lib/vers/print_version.c:38:
/usr/src/crypto/heimdal/lib/roken/roken-common.h:183:1: warning: EAI_NODATA re
defined
In file included from /usr/obj/usr/src/kerberos5/lib/libasn1/roken.h:59,
 from /usr/src/crypto/heimdal/lib/vers/print_version.c:38:
/usr/include/netdb.h:166:1: warning: this is the location of the previous defini
tion

Can a kerberos5 guy take a look at these?

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

Re: Can we get rid of kerb5 redefining macros?

[Hajimu UMEMOTO]

Hi,

 On Mon, 1 Dec 2003 04:11:34 -0800
 David O'Brien [EMAIL PROTECTED] said:

obrien Ever since kerberos5 got hooked up to the build by default I'm getting
obrien *TONS* (758) of CPP macros.  An example is:

obrien In file included from /usr/obj/usr/src/kerberos5/lib/libasn1/roken.h:77,
obrien  from /usr/src/crypto/heimdal/lib/vers/print_version.c:38:
obrien /usr/src/crypto/heimdal/lib/roken/roken-common.h:183:1: warning: EAI_NODATA 
re
obrien defined
obrien In file included from /usr/obj/usr/src/kerberos5/lib/libasn1/roken.h:59,
obrien  from /usr/src/crypto/heimdal/lib/vers/print_version.c:38:
obrien /usr/include/netdb.h:166:1: warning: this is the location of the previous 
defini
obrien tion

obrien Can a kerberos5 guy take a look at these?

I made a patch for this.  However, I forgot to sent it to Kerberos5
guy.

Sincerely,

Index: crypto/heimdal/lib/krb5/eai_to_heim_errno.c
diff -u crypto/heimdal/lib/krb5/eai_to_heim_errno.c.orig 
crypto/heimdal/lib/krb5/eai_to_heim_errno.c
--- crypto/heimdal/lib/krb5/eai_to_heim_errno.c.origThu Jun 21 11:11:31 2001
+++ crypto/heimdal/lib/krb5/eai_to_heim_errno.c Fri Nov  7 02:47:15 2003
@@ -47,8 +47,10 @@
 switch(eai_errno) {
 case EAI_NOERROR:
return 0;
+#ifdef EAI_ADDRFAMILY
 case EAI_ADDRFAMILY:
return HEIM_EAI_ADDRFAMILY;
+#endif
 case EAI_AGAIN:
return HEIM_EAI_AGAIN;
 case EAI_BADFLAGS:
@@ -59,8 +61,10 @@
return HEIM_EAI_FAMILY;
 case EAI_MEMORY:
return HEIM_EAI_MEMORY;
+#if defined(EAI_NODATA)  EAI_NODATA != EAI_NONAME
 case EAI_NODATA:
return HEIM_EAI_NODATA;
+#endif
 case EAI_NONAME:
return HEIM_EAI_NONAME;
 case EAI_SERVICE:
Index: crypto/heimdal/lib/krb5/verify_krb5_conf.c
diff -u crypto/heimdal/lib/krb5/verify_krb5_conf.c.orig 
crypto/heimdal/lib/krb5/verify_krb5_conf.c
--- crypto/heimdal/lib/krb5/verify_krb5_conf.c.orig Sat Oct 25 06:55:43 2003
+++ crypto/heimdal/lib/krb5/verify_krb5_conf.c  Fri Nov  7 02:42:26 2003
@@ -156,7 +156,11 @@
 hostname[strcspn(hostname, /)] = '\0';
 ret = getaddrinfo(hostname, telnet /* XXX */, NULL, ai);
 if(ret != 0) {
+#ifdef EAI_NODATA
if(ret == EAI_NODATA)
+#else
+   if(ret == EAI_NONAME)
+#endif
krb5_warnx(context, %s: host not found (%s), path, hostname);
else
krb5_warnx(context, %s: %s (%s), path, gai_strerror(ret), hostname);
Index: crypto/heimdal/lib/roken/roken-common.h
diff -u crypto/heimdal/lib/roken/roken-common.h.orig 
crypto/heimdal/lib/roken/roken-common.h
--- crypto/heimdal/lib/roken/roken-common.h.origWed Sep 18 02:36:32 2002
+++ crypto/heimdal/lib/roken/roken-common.h Fri Nov  7 01:58:38 2003
@@ -171,22 +171,26 @@
 #ifndef EAI_NOERROR
 #define EAI_NOERROR0   /* no error */
 #endif
-
 #ifndef EAI_ADDRFAMILY
-
 #define EAI_ADDRFAMILY 1   /* address family for nodename not supported */
+#endif
+
+#ifndef EAI_NONAME
+
 #define EAI_AGAIN  2   /* temporary failure in name resolution */
 #define EAI_BADFLAGS   3   /* invalid value for ai_flags */
 #define EAI_FAIL   4   /* non-recoverable failure in name resolution */
 #define EAI_FAMILY 5   /* ai_family not supported */
 #define EAI_MEMORY 6   /* memory allocation failure */
+#ifndef EAI_NODATA
 #define EAI_NODATA 7   /* no address associated with nodename */
+#endif
 #define EAI_NONAME 8   /* nodename nor servname provided, or not known */
 #define EAI_SERVICE9   /* servname not supported for ai_socktype */
 #define EAI_SOCKTYPE   10  /* ai_socktype not supported */
 #define EAI_SYSTEM 11  /* system error returned in errno */
 
-#endif /* EAI_ADDRFAMILY */
+#endif /* EAI_NONAME */
 
 /* flags for getaddrinfo() */
 
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED],jp.}FreeBSD.org
http://www.imasy.org/~ume/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: problem with kerberos startup and LDAP

[Jacques A. Vidrine]

On Sun, Nov 30, 2003 at 10:37:08PM -0800, Sean McNeil wrote:
 Hello All,
 
 I was having trouble with startup and kdc/kadmin5 failing.  Turns out
 that they were trying to access a shared library in /usr/local/lib
 (libldap.so.2).  Unfortunately, both were getting started before
 ldconfig.
 
 I added ldconfig to the REQUIRE: for kerberos and now all is well.
 
 What should be the correct solution?

Let's see:  What implementation of Kerberos?  (Heimdal, MIT?)
Installed as part of the base system, from the Ports Collection, or by
hand?

The correct solutions are:

  (a) Do not build Kerberos against OpenLDAP if you do not use
  LDAP functionality.

  (b) When building Kerberos, make certain that the linker flags
  include an appropriate setting for RPATH, e.g.
  `-rpath /usr/local/lib'.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Need example file for nsswitch.conf in /usr/share/examples

[Jacques A. Vidrine]

On Sat, Nov 29, 2003 at 04:41:11PM -0500, Richard Coleman wrote:
 There really needs to be an example file for nsswitch.conf in 
 /usr/share/example.  For people new to FreeBSD 5.X, there is no outward 
 sign that nsswitch is supported other than the nsswitch.conf(5) man page.

I won't be adding one for reasons already discussed on the list list
back in August (I think you started that thread, too, Richard)--- in
short I do not think it is needed and could even be harmful (if people
copy it to /etc/nsswitch.conf).

But, if someone has a set of *good* example configurations and they
are installed in share/examples/etc/nsswitch.conf.${description},
I certainly would not object. (e.g. nsswitch.conf.hesiod,
nsswitch.conf.ldap, and so on)

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can we get rid of kerb5 redefining macros?

[Jacques A. Vidrine]

On Mon, Dec 01, 2003 at 09:47:04PM +0900, Hajimu UMEMOTO wrote:
 I made a patch for this.  However, I forgot to sent it to Kerberos5
 guy.

Thanks!  I'll see about getting it upstream.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: -current lockup (how to diagnose?)

[Melvyn Sopacua]

On Monday 01 December 2003 09:02, Soren Schmidt wrote:

 It seems Jun Kuriyama wrote:
  I got lockups in recent -current box.  This box is my main workstation
  and usually be up to date kernel.
 
  In recent days, I usually locked up.  This is not a panic, only locks
  up.  My situation is:
 
  o KDE's clock is working.
  o KDE's virtual screen switching is working.
  o Apache does not reply on 80/tcp from remote.
  o ssh from this box is still working.

But ssh *to* the box doesn't right?

  o zsh on this box does not go next prompt when I press enter key at
promprt.
 
  It looks kernel is working, but fork/exec is not working when I enter
  to this situation.

 Hmm, I've been seeing something semilar a couble of times, can you do a
 ps -axl and see if those processes hang around in vm ?

I've had this on -STABLE as well and indeed KDE seems to be related. Also, I 
recall this to happen during the security check or rebuilding the locate 
database. I haven't seen this once I installed more memory.

A good tell-tale is:
* Switch to the console.
* Select another VT, via ALT-F2
* Type in the login name and press enter

You won't get a passwd prompt.

Most of the time I got outof it, by CTRL-ALT-F1 and CTRL-C.

I think I have a weekly run report somewhere, reporting 'vm exhaustion' 
errors. I can dig it up if it's helpful.
At the time, the box had 128Megs of RAM and 256MB swap, P-III 450.
-- 
Melvyn

===
FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #1: Sat Nov 29 
00:15:33 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/
SAREVOK_NOFW_DBG  i386
===


pgp0.pgp
Description: signature

Re: 5.2-BETA dsp.c duplicate lock

[Jesse Guardiani]

Jesse Guardiani wrote:

 I get this every time I `startx`. I didn't see it in
 the archive either:
 
 
 acquiring duplicate lock of same type: pcm channel
  1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144
  2nd pcm0:virtual:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146
 Stack backtrace:
 backtrace(c089b7e5,c3c96a54,c0a8f35a,92,200246) at backtrace+0x17
 witness_lock(c3c6aa80,8,c0a8f35a,92,2002) at witness_lock+0x672
 _mtx_lock_flags(c3c6aa80,0,c0a8f35a,92,c4) at _mtx_lock_flags+0xba
 getchns(c3d07700,e473faf0,e473faf4,3000,c3b86980) at getchns+0x1b5
 dsp_poll(c3d07700,c4,c403e640,c097fce0,0) at dsp_poll+0x46
 spec_poll(e473fb48,e473fb68,c06d600c,e473fb48,c0937ca0) at spec_poll+0x180
 spec_vnoperate(e473fb48,c0937ca0,c438db2c,c4,c4361a80) at
 spec_vnoperate+0x18 vn_poll(c4599110,c4,c4361a80,c403e640,c4361a80) at
 vn_poll+0x3c pollscan(c403e640,e473fbd8,3,3e1,18) at pollscan+0xb3
 poll(c403e640,e473fd14,c08b631d,3ee,3) at poll+0x252
 syscall(2f,2f,2f,,bfbfe748) at syscall+0x2c0
 Xint0x80_syscall() at Xint0x80_syscall+0x1d
 --- syscall (209), eip = 0x2869322f, esp = 0xbfbfe70c, ebp = 0xbfbfe768
 ---
 

I this a known LOR? Or do I need to submit a pr?

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net


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

Re: -current lockup (how to diagnose?)

[Jun Kuriyama]

At Mon, 1 Dec 2003 14:39:56 +0100,
Melvyn Sopacua wrote:
   o KDE's clock is working.
   o KDE's virtual screen switching is working.
   o Apache does not reply on 80/tcp from remote.
   o ssh from this box is still working.
 
 But ssh *to* the box doesn't right?

Yes.

 I've had this on -STABLE as well and indeed KDE seems to be related. Also, I 
 recall this to happen during the security check or rebuilding the locate 
 database. I haven't seen this once I installed more memory.
 
 A good tell-tale is:
 * Switch to the console.
 * Select another VT, via ALT-F2
 * Type in the login name and press enter
 
 You won't get a passwd prompt.

Yes, I can see the same situation.

 Most of the time I got outof it, by CTRL-ALT-F1 and CTRL-C.

Hmm, I'll try next time.

 I think I have a weekly run report somewhere, reporting 'vm exhaustion' 
 errors. I can dig it up if it's helpful.
 At the time, the box had 128Megs of RAM and 256MB swap, P-III 450.

My box has 2GB memory, so it would be enough.  My box makes world and
release nightly and it locks usually at that time.

Anyway, I'm waiting for next lock ups.  :-)


-- 
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: NSS and PAM, dynamic vs. static

[Jacques A. Vidrine]

On Sat, Nov 29, 2003 at 02:01:02PM +0100, Matthias Andree wrote:
 Jacques A. Vidrine [EMAIL PROTECTED] writes:
  NSS and PAM do not overlap.
 
 I wonder how PAM gets system authentication information for pam_pwdb
 or pam_unix or how it's called today and on the pertinent system if not
 through NSS. Reimplementation of these passwd/shadow/whatever
 mechanisms?

No, PAM uses the system directory services APIs (e.g. getpwnam(3) and
similar).  Those in turn use NSS, on NSS systems.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 5.2-BETA dsp.c duplicate lock

[Maxime Henrion]

Jesse Guardiani wrote:
 Jesse Guardiani wrote:
 
  I get this every time I `startx`. I didn't see it in
  the archive either:
  
  
  acquiring duplicate lock of same type: pcm channel
   1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144
   2nd pcm0:virtual:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146
  Stack backtrace:
  backtrace(c089b7e5,c3c96a54,c0a8f35a,92,200246) at backtrace+0x17
  witness_lock(c3c6aa80,8,c0a8f35a,92,2002) at witness_lock+0x672
  _mtx_lock_flags(c3c6aa80,0,c0a8f35a,92,c4) at _mtx_lock_flags+0xba
  getchns(c3d07700,e473faf0,e473faf4,3000,c3b86980) at getchns+0x1b5
  dsp_poll(c3d07700,c4,c403e640,c097fce0,0) at dsp_poll+0x46
  spec_poll(e473fb48,e473fb68,c06d600c,e473fb48,c0937ca0) at spec_poll+0x180
  spec_vnoperate(e473fb48,c0937ca0,c438db2c,c4,c4361a80) at
  spec_vnoperate+0x18 vn_poll(c4599110,c4,c4361a80,c403e640,c4361a80) at
  vn_poll+0x3c pollscan(c403e640,e473fbd8,3,3e1,18) at pollscan+0xb3
  poll(c403e640,e473fd14,c08b631d,3ee,3) at poll+0x252
  syscall(2f,2f,2f,,bfbfe748) at syscall+0x2c0
  Xint0x80_syscall() at Xint0x80_syscall+0x1d
  --- syscall (209), eip = 0x2869322f, esp = 0xbfbfe70c, ebp = 0xbfbfe768
  ---
  
 
 I this a known LOR? Or do I need to submit a pr?

This isn't a LOR at all.  Could you please try the attached patch?  It
should fix your problem.

To the sound guys : I believe it's expected that the pcm code will
sometimes acquire several channels lock at once, but I am not 100% sure.
If it's not, this patch isn't a fix but a workaround.

Cheers,
Maxime
Index: isa/ad1816.c
===
RCS file: /space2/ncvs/src/sys/dev/sound/isa/ad1816.c,v
retrieving revision 1.29
diff -u -p -r1.29 ad1816.c
--- isa/ad1816.c7 Sep 2003 16:28:02 -   1.29
+++ isa/ad1816.c1 Dec 2003 14:11:45 -
@@ -593,7 +593,8 @@ ad1816_attach(device_t dev)
ad1816 = (struct ad1816_info *)malloc(sizeof *ad1816, M_DEVBUF, M_NOWAIT | 
M_ZERO);
if (!ad1816) return ENXIO;
 
-   ad1816-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
+   ad1816-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc,
+   0);
ad1816-io_rid = 2;
ad1816-irq_rid = 0;
ad1816-drq1_rid = 0;
Index: isa/mss.c
===
RCS file: /space2/ncvs/src/sys/dev/sound/isa/mss.c,v
retrieving revision 1.86
diff -u -p -r1.86 mss.c
--- isa/mss.c   7 Sep 2003 16:28:02 -   1.86
+++ isa/mss.c   1 Dec 2003 14:11:53 -
@@ -1667,7 +1667,7 @@ mss_doattach(device_t dev, struct mss_in
int pdma, rdma, flags = device_get_flags(dev);
char status[SND_STATUSLEN], status2[SND_STATUSLEN];
 
-   mss-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
+   mss-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
mss-bufsize = pcm_getbuffersize(dev, 4096, MSS_DEFAULT_BUFSZ, 65536);
if (!mss_alloc_resources(mss, dev)) goto no;
mss_init(mss, dev);
Index: isa/sbc.c
===
RCS file: /space2/ncvs/src/sys/dev/sound/isa/sbc.c,v
retrieving revision 1.38
diff -u -p -r1.38 sbc.c
--- isa/sbc.c   7 Feb 2003 14:05:33 -   1.38
+++ isa/sbc.c   1 Dec 2003 14:12:03 -
@@ -116,7 +116,8 @@ static void sb_setmixer(struct resource 
 static void
 sbc_lockinit(struct sbc_softc *scp)
 {
-   scp-lock = snd_mtxcreate(device_get_nameunit(scp-dev), sound softc);
+   scp-lock = snd_mtxcreate(device_get_nameunit(scp-dev), sound softc,
+   0);
 }
 
 static void
Index: pci/cmi.c
===
RCS file: /space2/ncvs/src/sys/dev/sound/pci/cmi.c,v
retrieving revision 1.23
diff -u -p -r1.23 cmi.c
--- pci/cmi.c   2 Sep 2003 17:30:37 -   1.23
+++ pci/cmi.c   1 Dec 2003 14:12:15 -
@@ -842,7 +842,7 @@ cmi_attach(device_t dev)
return ENXIO;
}
 
-   sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
+   sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
data = pci_read_config(dev, PCIR_COMMAND, 2);
data |= (PCIM_CMD_PORTEN|PCIM_CMD_BUSMASTEREN);
pci_write_config(dev, PCIR_COMMAND, data, 2);
Index: pci/ds1.c
===
RCS file: /space2/ncvs/src/sys/dev/sound/pci/ds1.c,v
retrieving revision 1.36
diff -u -p -r1.36 ds1.c
--- pci/ds1.c   2 Sep 2003 17:30:37 -   1.36
+++ pci/ds1.c   1 Dec 2003 14:12:26 -
@@ -942,7 +945,7 @@ ds_pci_attach(device_t dev)
return ENXIO;
}
 
-   sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
+   sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
sc-dev = dev;
subdev = (pci_get_subdevice(dev)  16) | pci_get_subvendor(dev);
sc-type = ds_finddev(pci_get_devid(dev), subdev);
Index: 

Re: -current lockup (how to diagnose?)

[Melvyn Sopacua]

On Monday 01 December 2003 15:06, Jun Kuriyama wrote:

 My box has 2GB memory, so it would be enough.  My box makes world and
 release nightly and it locks usually at that time.

Which has the same characteristics as rebuilding a locate database or checking 
suid bits on the entire drive: lotsa disk io.

-- 
Melvyn

===
FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #1: Sat Nov 29 
00:15:33 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/
SAREVOK_NOFW_DBG  i386
===


pgp0.pgp
Description: signature

Re: -current lockup (how to diagnose?)

[Robert Watson]

On Mon, 1 Dec 2003, Jun Kuriyama wrote:

 I got lockups in recent -current box.  This box is my main workstation
 and usually be up to date kernel. 
 
 In recent days, I usually locked up.  This is not a panic, only locks
 up.  My situation is: 
 
 o KDE's clock is working.
 o KDE's virtual screen switching is working.
 o Apache does not reply on 80/tcp from remote.
 o ssh from this box is still working.
 o zsh on this box does not go next prompt when I press enter key at
   promprt.
 
 It looks kernel is working, but fork/exec is not working when I enter to
 this situation. 
 
 So, what can I diagnose with this situation?  Of course this box has
 serial console. 

This could be a sign of a VM or VFS lock leak or deadlock.  I'd advise
hooking up a serial console, dropping to DDB over serial line, and posting
the results of ps and show lockedvnods.  We might then ask you to use
the show locks command on various processes.  You'll need to have DDB
and WITNESS compiled in.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Senior Research Scientist, McAfee Research

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

Re: NSS and PAM

[Jacques A. Vidrine]

On Sat, Nov 29, 2003 at 02:45:24AM +0100, Dag-Erling Smørgrav wrote:
 Jacques A. Vidrine [EMAIL PROTECTED] writes:
  Interesting.  Explain, please.  (Maybe privately or in another thread;
  hate to keep this'n going.)  Perhaps you mean that it is a design flaw
  that two APIs are required.  If so, I happen to disagree; I think that
  the separation of directory services and authentication is appropriate
  and necessary.
 
 No, the two are essentially one.  We just think they aren't because
 we've been brainwashed to think of users in terms of uids and gids and
 especially struct passwd, which deserves to die.

By `the two', do you mean directory services and authentication?  They
are certainly not `essentially one'.  But I suspect you know this and
I am just misunderstanding your meaning.

 NSS itself doesn't make much sense to me; it's an elaborate hack
 designed to drag all those nice shiny directory services down in the
 mud where struct passwd has been wallowing for the past twenty years,
 instead of allowing applications to take advantage of their superior
 functionality.

I guess I think of it this way.  If NSS had not been implemented
`down in the mud' (inside getpw*, getgr*, gethostby*, etc.), then
applications that used the UNIX directory service APIs would need to
be re-written in order to utilize NSS.  That's a lot of code to change
for little benefit.

PAM is different.  Applications *had* to be re-written to utilize PAM,
because previously there was no real authentication API, just crypt()
and strcmp()--- obviously insufficient for many authentication methods
:-)

 As for PAM, a lot of what's wrong with it today could be fixed by
 redesigning it to include directory services.  If you fixed the
 conversation system (by formalizing service function execution as an
 FSM) and cleaned up the configuration syntax, you'd end up with
 something quite nice.

If I understand you correctly, you believe that it would be possible
to unite the NSS and PAM switches, so that they used the same
configuration file, dynamic loading mechanisms, cascading, and so
on.  Sure, I think that's possible.  There might even be some benefit,
though probably not enough benefit to abandon PAM/NSS and go our own
way.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: -current lockup (how to diagnose?)

[Jun Kuriyama]

At Mon, 1 Dec 2003 09:23:21 -0500 (EST),
Robert Watson wrote:
 This could be a sign of a VM or VFS lock leak or deadlock.  I'd advise
 hooking up a serial console, dropping to DDB over serial line, and posting
 the results of ps and show lockedvnods.  We might then ask you to use
 the show locks command on various processes.  You'll need to have DDB
 and WITNESS compiled in.

He he, I of course have serial console, DDB and WITNESS.  They are
good safety belf fot -current users, isn't it?  :-)

I'll post information above next time.  Thanks!


-- 
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]

5.2-RELEASE TODO

[Robert Watson]

This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:

http://www.FreeBSD.org/releases/5.2R/todo.html

Automated mailing of this list will continue through the release of
FreeBSD 5.2.


  FreeBSD 5.2 Open Issues

Open Issues

 This is a list of open issues that need to be resolved for FreeBSD 5.2. If
 you have any updates for this list, please e-mail [EMAIL PROTECTED]

Show stopper defects for 5.2-RELEASE

 ++
 |   Issue   |  Status   |Responsible |Description|
 |---+---++---|
 |Panic when |   ||   |
 |rebuilding |Not done   |--  |The panic reported in PR kern/58228|
 |ata-raid   |   ||must be fixed. |
 |arrays |   ||   |
 |---+---++---|
 |   |   ||panic: Assertion td-td_turnstile  |
 |   |   ||!= NULL failed at  |
 |   |   ||../../../kern/subr_turnstile.c:427 |
 |   |   ||has been affecting several users on|
 |   |   ||multiple platforms. Note: further  |
 |Turnstile  |   ||research indicates that these  |
 |assertion  |In progress|John Baldwin|panics tend to be double panics  |
 |failure|   ||that are a side effect of the  |
 |   |   ||turnstile code in the context of an|
 |   |   ||existing panic. Reporters of this  |
 |   |   ||panic should make sure to include a|
 |   |   ||full stack trace so that it's clear|
 |   |   ||if a second panic is also present. |
 |---+---++---|
 |   |   ||The new i386 interrupt code|
 |ACPI kernel|   ||requires that ACPI be compiled into|
 |module |In progress|John Baldwin|the kernel if it to be used. Work  |
 |   |   ||is underway to restore the ability |
 |   |   ||to load it as a module.|
 |---+---++---|
 |   |   ||There have been a number of reports|
 |Reported   |   ||of NFS clients and server hangs.   |
 |NFS|In progress||Unfortunately, these are difficult |
 |failures   |   ||to reproduce, and have not yet been|
 |   |   ||traced back to a particular change |
 |   |   ||or reliable reproduction scenario. |
 ++

Required features for 5.2-RELEASE

 ++
 |  Issue  |   Status| Responsible |   Description|
 |-+-+-+--|
 | | | | Kernel and userland bits |
 | KSE support for | | Jake| are implemented but  |
 | sparc64 | In progress | Burkholder  | untested and known to be |
 | | | | incomplete. Required for |
 | | | | 5.2-RELEASE. |
 |-+-+-+--|
 | | | | Userland bits|
 | KSE support for | | Marcel  | implemented, kernel bits |
 | alpha   | In progress | Moolenaar   | not implemented. |
 | | | | Required for |
 | | | | 5.2-RELEASE. |
 |-+-+-+--|
 | | | | Significant parts of the |
 | | | | network stack|
 | | | | (especially IPv4 and |
 | | | | IPv6) now have   |
 | | | | fine-grained locking of  |
 | | | | their data structures.   |
 | | | | However, it is not yet   |
 | | | | possible for the netisr  |
 | 

Re: lock order reversal

[Kris Kennaway]

On Sun, Nov 30, 2003 at 07:46:55PM -0500, [EMAIL PROTECTED] wrote:
 Is this a known issue on 5.2 beta 6 sup'ed nov 29/03?

Yes, it's reported on a daily basis and is harmless.

Kris


pgp0.pgp
Description: PGP signature

licq KSE

[Alexander Motin]

Hi!

licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping 
libc_r to libkse:

%licq -d0 -p qt-gui -- -noxim
Fatal error 'No current thread.
' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2)
And after saying this it begins eat all free CPU.
If I remove this mapping it works fine.
--
Alexander Motin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Panic booting cdboot-5.2-BETA-20031201-JPSNAP.iso

[Andreas Braukmann]

Hi there,

Hardware:   Tyan 2880 (K8S), single Opteron 240
   Adaptec 2200 or 2120, 2 Arrays (20 GB RAID-0, 20 GB RAID-5)
booting the install kernel gives:
[normal boot process]
aacd0: RAID 5 on aac0
aacd0: 20480 MB (41943040 sectors)
GEOM: create disk aacd0 dp=0xc2dc1c0c
aacd1: RAID 0 (Stripe) on aac0
aacd1: 20480MB (41943168 sectors)
GEOM: create disk aacd1 dp=0xc6fa980c
panic: mutex Giant not owned at /usr/src/sys/cam/cam_xpt.c: 4822
cpuid = 0;
Debugger(panic)
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db trace
Debugger(...)
panic(...)
_mtx_assert
xpt_done
aac_cam_complete
aac_complete
taskqueue_run
taskqueue_swi_run
ithread_loop
fork_exit
fork_trampoline
--- trap 0x1, eip = 0, esp = 0xe22b2d7c, ebp = 0 ---


I'm sorry for not having connected a serial console. If anybody needs
the full trace information I would gladly reproduce the crash and write
the complete information off.
Yesterdays (2003/11/30) snapshot yields the same result.

-Andreas

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

[no subject]

[Mark Murray]

Hi

You haven't responded to this. I'm very interested in these patches,
please.

M

--- Forwarded Message

Date:Thu, 27 Nov 2003 11:51:19 +
From:Mark Murray [EMAIL PROTECTED]
To:  Terry Lambert [EMAIL PROTECTED]
cc:  [EMAIL PROTECTED]
Subject: Re: rtld + static linking 

Terry Lambert writes:
  I've looked without much success. Could you give a timeframe, a subject
  and/or something?
 
 Note that the part you snipped indicated that the patches were
 posted by a third party, and that my own patches had been offered,
 but were not posted in their entirety to the mailing list.  In
 actuality, I only ever posted portions of my own patches, since
 they also required compiler and linker changes.

Could you please post your patches in their entirety?

M
- --
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

--- End of Forwarded Message

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

Re: NSS and PAM

[Dag-Erling Smørgrav]

Jacques A. Vidrine [EMAIL PROTECTED] writes:
 By `the two', do you mean directory services and authentication?  They
 are certainly not `essentially one'.  But I suspect you know this and
 I am just misunderstanding your meaning.

They are different issues, but in this context you can't discuss one
without the other.  Authentication doesn't work unless you have a user
to authenticate.  It makes no sense to separate them; you just end up
duplicating a lot of concepts and code.

Also, is changing your password an authentication function or a
directory function?  I don't think you can answer either without
answering both.

 I guess I think of it this way.  If NSS had not been implemented
 `down in the mud' (inside getpw*, getgr*, gethostby*, etc.), then
 applications that used the UNIX directory service APIs would need to
 be re-written in order to utilize NSS.  That's a lot of code to change
 for little benefit.

Backward compatibility is fine, but NSS does not seem to export an API
that we can use when we want to lift ourselves out of the mud, so we
are forced to keep rooting around in it.  One consequence of this (and
of the artificial separation between NSS and PAM) is that passwd(1)
doesn't work properly except in the simplest cases.

 If I understand you correctly, you believe that it would be possible
 to unite the NSS and PAM switches, so that they used the same
 configuration file, dynamic loading mechanisms, cascading, and so
 on.  Sure, I think that's possible.  There might even be some benefit,
 though probably not enough benefit to abandon PAM/NSS and go our own
 way.

Not to go our own way, no.  There's the rub.  It would have to be a
reasonably wide effort; we'd need to get at least one major Linux
distro to adopt the same infrastructure.

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

Route LOR

[Ryan]

I know this has been mentioned a few times before but I think I was able
to tie down what causes it more specifically. (Other reports of it just
mention starting programs).

For me the first time I try to set the default route I get the message.
(DHClient doesn't like to set my route the first time I invoke it for some
reason). I noticed the LOR in the syslog file but didn't know what caused
it. Then the next two times after that I noticed it right after I
explicitly set my route with route change default ... It seems to only
happen the first time I change the default route after booting.

I have 2 devices, Ethernet (xl) is static IP assigned through the rc
scripts, and Wireless (wi) isn't brought up at boot. When I use the
wirless I let dhclient bring the device up and then I usually have to tail
/var/log/messages to get the router IP. I then issue the route command and
that is when I get the LOR. However if I make subsequent calls to route,
even changing the default route, I don't get the LOR.

I've attached the LOR. If you need any other info please feel free to
request it.

-- 
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO

-= http://www.gamersimpact.com =-lock order reversal
 1st 0xc4566264 rtentry (rtentry) @ /usr/src/sys/net/rtsock.c:387
 2nd 0xc4481a7c radix node head (radix node head) @ /usr/src/sys/net/route.c:133

Stack backtrace:
backtrace(c0692e54,c4481a7c,c069830a,c069830a,c0698360) at backtrace+0x17
witness_lock(c4481a7c,8,c0698360,85,c43f68a0) at witness_lock+0x672
_mtx_lock_flags(c4481a7c,0,c0698360,85,121) at _mtx_lock_flags+0xba
rtalloc1(c474636c,1,0,436,0) at rtalloc1+0x79
rt_setgate(c4566200,c43f68a0,c474636c,184,0) at rt_setgate+0x258
route_output(c192fe00,c45c5870,80,c192fe00,1f80) at route_output+0x67f
raw_usend(c45c5870,0,c192fe00,0,0) at raw_usend+0x73
rts_send(c45c5870,0,c192fe00,0,0) at rts_send+0x35
sosend(c45c5870,0,dc926c80,c192fe00,0) at sosend+0x44d
soo_write(c456a8c4,dc926c80,c474ea80,0,c4543280) at soo_write+0x70
dofilewrite(c4543280,c456a8c4,3,804e940,80) at dofilewrite+0xfb
write(c4543280,dc926d14,c06a6081,3ee,3) at write+0x6e
syscall(2f,2f,2f,804e99c,80) at syscall+0x2c0
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (4), eip = 0x280c20af, esp = 0xbfbfecec, ebp = 0xbfbfed08 ---
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: NSS and PAM

[Robert Watson]

On Mon, 1 Dec 2003, Dag-Erling Smørgrav wrote:

 Jacques A. Vidrine [EMAIL PROTECTED] writes:
  By `the two', do you mean directory services and authentication?  They
  are certainly not `essentially one'.  But I suspect you know this and
  I am just misunderstanding your meaning.
 
 They are different issues, but in this context you can't discuss one
 without the other.  Authentication doesn't work unless you have a user
 to authenticate.  It makes no sense to separate them; you just end up
 duplicating a lot of concepts and code. 
 
 Also, is changing your password an authentication function or a
 directory function?  I don't think you can answer either without
 answering both. 

It strikes me that there are two separate issues:

(1) Whether or not there's a useful distinction between authentication
services and directory services.

(2) If there is or isn't such a distinction in (1), whether or not that
distinction should appear in the implementation.

In practice, people frequently mix and match authentication services and
directory services, and there are services that implement one but not the
other.  For example, Kerberos5 for authentication an LDAP for directory
services is a common combination: however, Kerberos doesn't provide
directory services, only principal authentication.  Likewise, even on
purely local systems, the account directory services (pwent, et al) may be
distinct from principal authentication using one-time passwords, etc.  I'm
not opposed to the fundamental idea of combining mechanism, but there are
some practical underlying differences between directory services and
authentication, even though there's clear overlap. 

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Senior Research Scientist, McAfee Research

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

Re: bash2 linked dynamically

[Leo Bicknell]

In a message written on Sun, Nov 30, 2003 at 09:48:45PM -0800, David O'Brien wrote:
 Lucky for me (who wants a static Bash), I don't have to make the
 decission -- ports are frozen and have been for a while.

This line of thinking seems a bit silly to me.  We have a long
discussion documenting the dynamic root concept, and how it was
deemed important that /bin/sh be dynamic to support NSS and other
reasons.

Now someone wants the same thing in bash, and commit-freeze is going
to stop it from happening?

Sounds like the core team, or re, or someone needs to decide which
is more important.  If NSS is so important redoing the whole root
is important, then I sure think any and all shells installed by
ports should support the same features.  If, on the other hand it's
not important for Bash then why in the heck are we doing it for the
root?

I'm done arguing for either side of this issue, but I will argue for
consistency until I'm blue in the face.

-- 
   Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - [EMAIL PROTECTED], www.tmbg.org


pgp0.pgp
Description: PGP signature

panic during shutdown from vfs_umountall()

[Robert Watson]

Running with a MAC kernel, about to try booting identical but non-MAC; I'm
not able to reproduceit , however.  bgfsck may have been running during
the shutdown.  Apparently the device vnode for /usr is vrele()'d one too
many times at some point during the run, resulting in a panic.  This is
with vfs_mount.c:1.116. 

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Senior Research Scientist, McAfee Research

Script started on Mon Dec  1 12:23:10 2003
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: vrele: negative ref cnt
panic messages:
---
panic: vrele: negative ref cnt
cpuid = 0; 
panic: from debugger
cpuid = 0; 
Uptime: 23h36m45s
Dumping 511 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 448 464 480 496
---
Reading symbols from /boot/kernel/snd_maestro3.ko...done.
Loaded symbols for /boot/kernel/snd_maestro3.ko
Reading symbols from /boot/kernel/snd_pcm.ko...done.
Loaded symbols for /boot/kernel/snd_pcm.ko
Reading symbols from 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_biba/mac_biba.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_biba/mac_biba.ko.debug
Reading symbols from 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_mls/mac_mls.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_mls/mac_mls.ko.debug
Reading symbols from /boot/kernel/r128.ko...done.
Loaded symbols for /boot/kernel/r128.ko
Reading symbols from 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linprocfs/linprocfs.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linprocfs/linprocfs.ko.debug
Reading symbols from 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linux/linux.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linux/linux.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  0xc06719f7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2  0xc0671dfd in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc048cc82 in db_panic () at /usr/src/sys/ddb/db_command.c:450
#4  0xc048cbe2 in db_command (last_cmdp=0xc094efc0, cmd_table=0x0, 
aux_cmd_tablep=0xc08d09cc, aux_cmd_tablep_end=0xc08d09e4)
at /usr/src/sys/ddb/db_command.c:346
#5  0xc048cd25 in db_command_loop () at /usr/src/sys/ddb/db_command.c:472
#6  0xc048fd25 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:73
#7  0xc082861c in kdb_trap (type=3, code=0, regs=0xd77c6b48)
at /usr/src/sys/i386/i386/db_interface.c:171
#8  0xc083e688 in trap (frame=
  {tf_fs = 24, tf_es = -1064697840, tf_ds = 16, tf_edi = -1064617494, tf_esi = 1, 
tf_ebp = -679711852, tf_isp = -679711884, tf_ebx = 0, tf_edx = 0, tf_ecx = 32, tf_eax 
= 18, tf_trapno = 3, tf_err = 0, tf_eip = -1065187035, tf_cs = 8, tf_eflags = 642, 
tf_esp = -1064532435, tf_ss = -1064643348})
at /usr/src/sys/i386/i386/trap.c:580
#9  0xc082a068 in calltrap () at {standard input}:94
#10 0xc0671d96 in panic (fmt=0xc08b39ea vrele: negative ref cnt)
at /usr/src/sys/kern/kern_shutdown.c:534
#11 0xc06cb44e in vrele () at /usr/src/sys/kern/vfs_subr.c:2221
#12 0xc07d4b18 in ffs_unmount (mp=0xc481c800, mntflags=524288, td=0xc1d29500)
at /usr/src/sys/ufs/ffs/ffs_vfsops.c:999
#13 0xc06c68f4 in dounmount (mp=0xc481c800, flags=524288, td=0xc1d29500)
at /usr/src/sys/kern/vfs_mount.c:1126
#14 0xc06cce3e in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:3176
#15 0xc06718c3 in boot (howto=16392) at /usr/src/sys/kern/kern_shutdown.c:357
#16 0xc06711d4 in reboot (td=0xc1d29500, uap=0xd77c6d14)
at /usr/src/sys/kern/kern_shutdown.c:178
#17 0xc083f050 in syscall (frame=
  {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077940488, tf_esi = -1077940488, 
tf_ebp = -1077940744, tf_isp = -679711372, tf_ebx = -1077940584, tf_edx = -1, tf_ecx = 
4, tf_eax = 55, tf_trapno = 12, tf_err = 2, tf_eip = 134547627, tf_cs = 31, tf_ef
lags = 515, tf_esp = -1077940948, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1010
#18 0xc082a0bd in Xint0x80_syscall () at {standard input}:136
---Can't read userspace from dump, or kernel process---

(kgdb) up
#1  0xc06719f7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
372 doadump();
(kgdb) up
#2  0xc0671dfd in panic () at /usr/src/sys/kern/kern_shutdown.c:550
550 boot(bootopt);
(kgdb) up
#3  0xc048cc82 in 

Re: Panic booting cdboot-5.2-BETA-20031201-JPSNAP.iso

[Andreas Braukmann]

--On Montag, 1. Dezember 2003 17:41 Uhr +0100 Andreas Braukmann [EMAIL PROTECTED] wrote:

Hardware:   Tyan 2880 (K8S), single Opteron 240
Adaptec 2200 or 2120, 2 Arrays (20 GB RAID-0, 20 GB RAID-5)
[...]
GEOM: create disk aacd1 dp=0xc6fa980c
panic: mutex Giant not owned at /usr/src/sys/cam/cam_xpt.c: 4822
cpuid = 0;


I took another K8S / Adaptec 2200S box and (to rule out any hardware
issues) was able to reproduce the panic with all -current-snapshots back
to 20031128. I don't have former kernels available.
-Andreas

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

Re: psmintr not attached w/ acpi

[Nate Lawson]

Your ASL indicates that it returns different values for present (based on
PS2F) and current resources (based on KBDI).  Please send me the URL to
the full ASL so I can see what sets those two variables.

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

Re: NSS and PAM

[Brandon S. Allbery KF8NH]

On Mon, 2003-12-01 at 11:48, Dag-Erling Smrgrav wrote:
  If I understand you correctly, you believe that it would be possible
  to unite the NSS and PAM switches, so that they used the same
  configuration file, dynamic loading mechanisms, cascading, and so
  on.  Sure, I think that's possible.  There might even be some benefit,
  though probably not enough benefit to abandon PAM/NSS and go our own
  way.
 
 Not to go our own way, no.  There's the rub.  It would have to be a
 reasonably wide effort; we'd need to get at least one major Linux
 distro to adopt the same infrastructure.

Has anyone considered the idea of hybridizing PAM with
Digital^WCompaq^WHP's SIA matrix setup?

-- 
brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED]
system administrator  [WAY too many hats][EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon univ. KF8NH

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

Re: Panic booting cdboot-5.2-BETA-20031201-JPSNAP.iso

[Scott Long]

Hi,

This is a serious mistake of mine.  I'll come up with a patch later today.

Scott

On Mon, 1 Dec 2003, Andreas Braukmann wrote:

 Hi there,

 Hardware:   Tyan 2880 (K8S), single Opteron 240
 Adaptec 2200 or 2120, 2 Arrays (20 GB RAID-0, 20 GB RAID-5)


 booting the install kernel gives:
 [normal boot process]
 aacd0: RAID 5 on aac0
 aacd0: 20480 MB (41943040 sectors)
 GEOM: create disk aacd0 dp=0xc2dc1c0c
 aacd1: RAID 0 (Stripe) on aac0
 aacd1: 20480MB (41943168 sectors)
 GEOM: create disk aacd1 dp=0xc6fa980c
 panic: mutex Giant not owned at /usr/src/sys/cam/cam_xpt.c: 4822
 cpuid = 0;
 Debugger(panic)
 Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
 db trace
 Debugger(...)
 panic(...)
 _mtx_assert
 xpt_done
 aac_cam_complete
 aac_complete
 taskqueue_run
 taskqueue_swi_run
 ithread_loop
 fork_exit
 fork_trampoline
 --- trap 0x1, eip = 0, esp = 0xe22b2d7c, ebp = 0 ---



 I'm sorry for not having connected a serial console. If anybody needs
 the full trace information I would gladly reproduce the crash and write
 the complete information off.

 Yesterdays (2003/11/30) snapshot yields the same result.


 -Andreas


 ___
 [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: NSS and PAM

[Jacques A. Vidrine]

On Mon, Dec 01, 2003 at 05:48:22PM +0100, Dag-Erling Smørgrav wrote:
 They are different issues, but in this context you can't discuss one
 without the other.  Authentication doesn't work unless you have a user
 to authenticate.  It makes no sense to separate them; you just end up
 duplicating a lot of concepts and code.

Hmm, I disagree completely.  :-)  They can be separated and should be
separated.  Systems that mix them up are flawed.  The confusion of the
two are what *causes* the problem you bring up below (passwd(1)).

Authentication simply names you.  It is quite possible to be
authenticated in some context and have absolutely no privileges or
other information (``in a vacuum'', if you will).  It is even useful
in some cases:

   = `Junk' certificates
   = `Junk' Kerberos principals
   = A disabled account
   = A newly-created account

More practically speaking, the mechanism by which you authenticate
usually has no bearing on what you are authorized to do.  This is the
power of properly separating authentication and authorization:
regardless of whether I authenticate by entering my password, inserting
my smart card and PIN, or supplying a Kerberos ticket, my privileges
will be the same [1].  

Similarly, if the IT department moved from NIS to LDAP over the
weekend, all my existing authentication tokens naturally still work.

That's not to say that you *cannot* combine authentication and
authorization, but they are naturally independent and different
protocols and semantics are required for one and the other.  RADIUS is
a good example.  It is quite difficult to properly support a variety
of authentication mechanisms in RADIUS.  Diameter addresses the issue
by supporting a separate authentication protocol, EAP, which in turn
allows for various authentication mechanisms generically.

 Also, is changing your password an authentication function or a
 directory function?  I don't think you can answer either without
 answering both.

I think it is strictly an authentication function.  The change in your
password has no affect on your UID, or your phone number, or in what
ACLs your name appears in.

  I guess I think of it this way.  If NSS had not been implemented
  `down in the mud' (inside getpw*, getgr*, gethostby*, etc.), then
  applications that used the UNIX directory service APIs would need to
  be re-written in order to utilize NSS.  That's a lot of code to change
  for little benefit.
 
 Backward compatibility is fine, but NSS does not seem to export an API
 that we can use when we want to lift ourselves out of the mud, so we
 are forced to keep rooting around in it.  

What's an example of what you mean?  The BSD nsswitch implementation
has a generic nsdispatch(3) that allows for new applications, but I'm
not sure that is what you mean.  At any rate, it is not `NSS' proper, it
is an implementation detail.

 One consequence of this (and
 of the artificial separation between NSS and PAM) is that passwd(1)
 doesn't work properly except in the simplest cases.

It seems to me that this is a direct result of passwd(1) confusing
authentication and authorization.  Other than determining the default
target user name from the current UID, passwd(1) needs only to invoke
PAM interfaces to change your password for any authentication method
that supports password changing.

Of course this won't work for certain legacy, read-mostly
`authentication methods' such as NIS or Hesiod that aren't supported
by PAM.

  If I understand you correctly, you believe that it would be possible
  to unite the NSS and PAM switches, so that they used the same
  configuration file, dynamic loading mechanisms, cascading, and so
  on.  Sure, I think that's possible.  There might even be some benefit,
  though probably not enough benefit to abandon PAM/NSS and go our own
  way.
 
 Not to go our own way, no.  There's the rub.  It would have to be a
 reasonably wide effort; we'd need to get at least one major Linux
 distro to adopt the same infrastructure.

Indeed, ``there's the rub'' :-)

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]


[1] Mostly.  An application might require that you used a strong
authentication method, to launch the nukes or something. :-)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: psmintr not attached w/ acpi

[Slawa Olhovchenkov]

On Mon, Dec 01, 2003 at 09:48:40AM -0800, Nate Lawson wrote:

 Your ASL indicates that it returns different values for present (based on
 PS2F) and current resources (based on KBDI).  Please send me the URL to
 the full ASL so I can see what sets those two variables.

http://zxy.spb.ru/acpi.dump

Do you need additional information?

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

Re: problem with kerberos startup and LDAP

[Sean McNeil]

This was with Heimdal from an installation of -CURRENT.  I am using LDAP
functionality, so option (a) below is not an option.  Option (b) below
sounds more difficult than the change I made to /etc/rc.d/kerberos :)

I hadn't thought kerberos would get linked in such a manner, but now
that you mentioned it here is what it ended up using:

/usr/libexec/kdc:
libkrb5.so.7 = /usr/lib/libkrb5.so.7 (0x2807e000)
libhdb.so.7 = /usr/lib/libhdb.so.7 (0x280ba000)
libroken.so.7 = /usr/lib/libroken.so.7 (0x280ca000)
libasn1.so.7 = /usr/lib/libasn1.so.7 (0x280d8000)
libcrypto.so.3 = /lib/libcrypto.so.3 (0x280fe000)
libcrypt.so.2 = /lib/libcrypt.so.2 (0x28208000)
libcom_err.so.2 = /usr/lib/libcom_err.so.2 (0x28221000)
libldap.so.2 = /usr/local/lib/libldap.so.2 (0x28223000)
liblber.so.2 = /usr/local/lib/liblber.so.2 (0x28254000)
libc.so.5 = /lib/libc.so.5 (0x2826)
libsasl2.so.2 = /usr/local/lib/libsasl2.so.2 (0x28337000)
libssl.so.3 = /usr/local/lib/libssl.so.3 (0x2834a000)
libcrypto.so.3 = /usr/local/lib/libcrypto.so.3 (0x2837b000)

It only complained about libldap.so.2, so I would guess kerberos is
using the -rpath for the others?

Thanks,
Sean

On Mon, 2003-12-01 at 05:25, Jacques A. Vidrine wrote:
 On Sun, Nov 30, 2003 at 10:37:08PM -0800, Sean McNeil wrote:
  Hello All,
  
  I was having trouble with startup and kdc/kadmin5 failing.  Turns out
  that they were trying to access a shared library in /usr/local/lib
  (libldap.so.2).  Unfortunately, both were getting started before
  ldconfig.
  
  I added ldconfig to the REQUIRE: for kerberos and now all is well.
  
  What should be the correct solution?
 
 Let's see:  What implementation of Kerberos?  (Heimdal, MIT?)
 Installed as part of the base system, from the Ports Collection, or by
 hand?
 
 The correct solutions are:
 
   (a) Do not build Kerberos against OpenLDAP if you do not use
   LDAP functionality.
 
   (b) When building Kerberos, make certain that the linker flags
   include an appropriate setting for RPATH, e.g.
   `-rpath /usr/local/lib'.
 
 Cheers,

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

Re: problem with kerberos startup and LDAP

[Jacques A. Vidrine]

On Mon, Dec 01, 2003 at 10:10:20AM -0800, Sean McNeil wrote:
 This was with Heimdal from an installation of -CURRENT.  I am using LDAP
 functionality, so option (a) below is not an option.  Option (b) below
 sounds more difficult than the change I made to /etc/rc.d/kerberos :)
 
 I hadn't thought kerberos would get linked in such a manner, but now
 that you mentioned it here is what it ended up using:
 
 /usr/libexec/kdc:
 libkrb5.so.7 = /usr/lib/libkrb5.so.7 (0x2807e000)
 libhdb.so.7 = /usr/lib/libhdb.so.7 (0x280ba000)
 libroken.so.7 = /usr/lib/libroken.so.7 (0x280ca000)
 libasn1.so.7 = /usr/lib/libasn1.so.7 (0x280d8000)
 libcrypto.so.3 = /lib/libcrypto.so.3 (0x280fe000)
 libcrypt.so.2 = /lib/libcrypt.so.2 (0x28208000)
 libcom_err.so.2 = /usr/lib/libcom_err.so.2 (0x28221000)
 libldap.so.2 = /usr/local/lib/libldap.so.2 (0x28223000)
 liblber.so.2 = /usr/local/lib/liblber.so.2 (0x28254000)
 libc.so.5 = /lib/libc.so.5 (0x2826)
 libsasl2.so.2 = /usr/local/lib/libsasl2.so.2 (0x28337000)
 libssl.so.3 = /usr/local/lib/libssl.so.3 (0x2834a000)
 libcrypto.so.3 = /usr/local/lib/libcrypto.so.3 (0x2837b000)
 
 It only complained about libldap.so.2, so I would guess kerberos is
 using the -rpath for the others?


Oh, you must be using `WITH_OPENLDAP'--- an option that I did not even
realize was available in the base system until I looked just now :-)

Yes, I believe the build is broken and I will correct it after the
code freeze.  In the meantime, you might try the following patch and
rebuild the KDC (`make clean' first).

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME  FreeBSD UNIX   Heimdal
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]


Index: kerberos5/Makefile.inc
===
RCS file: /home/ncvs/src/kerberos5/Makefile.inc,v
retrieving revision 1.19
diff -c -r1.19 Makefile.inc
*** kerberos5/Makefile.inc  18 Jul 2003 13:21:55 -  1.19
--- kerberos5/Makefile.inc  1 Dec 2003 18:21:23 -
***
*** 16,22 
  OPENLDAPBASE?=/usr/local
  LDAPLIBS=-lldap -llber
  LDAPCFLAGS=-I${OPENLDAPBASE}/include -DOPENLDAP=1
! LDAPLDADD=-L${OPENLDAPBASE}/lib ${LDAPLIBS}
  .endif
  
  .if exists(${.OBJDIR}/../../include)
--- 16,22 
  OPENLDAPBASE?=/usr/local
  LDAPLIBS=-lldap -llber
  LDAPCFLAGS=-I${OPENLDAPBASE}/include -DOPENLDAP=1
! LDAPLDADD=-L${OPENLDAPBASE}/lib -Wl,-rpath,${OPENLDAPBASE}/lib ${LDAPLIBS}
  .endif
  
  .if exists(${.OBJDIR}/../../include)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: licq KSE

[Daniel Eischen]

On Mon, 1 Dec 2003, Alexander Motin wrote:

 Hi!
 
 licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping 
 libc_r to libkse:
 
 %licq -d0 -p qt-gui -- -noxim
 Fatal error 'No current thread.
 ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2)
 
 And after saying this it begins eat all free CPU.
 If I remove this mapping it works fine.

I think the port is broken.  Are you getting static LDT warnings
from the kernel when this happens?

-- 
Dan Eischen

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

Re: problem with kerberos startup and LDAP

[Sean McNeil]

Yes, I use the following in make.conf:

WITH_LDAP=openldap2
WITH_OPENLDAP=yes

Great, I will give your patch a try. Thanks!

Sean

On Mon, 2003-12-01 at 10:23, Jacques A. Vidrine wrote:
 On Mon, Dec 01, 2003 at 10:10:20AM -0800, Sean McNeil wrote:
  This was with Heimdal from an installation of -CURRENT.  I am using LDAP
  functionality, so option (a) below is not an option.  Option (b) below
  sounds more difficult than the change I made to /etc/rc.d/kerberos :)
  
  I hadn't thought kerberos would get linked in such a manner, but now
  that you mentioned it here is what it ended up using:
  
  /usr/libexec/kdc:
  libkrb5.so.7 = /usr/lib/libkrb5.so.7 (0x2807e000)
  libhdb.so.7 = /usr/lib/libhdb.so.7 (0x280ba000)
  libroken.so.7 = /usr/lib/libroken.so.7 (0x280ca000)
  libasn1.so.7 = /usr/lib/libasn1.so.7 (0x280d8000)
  libcrypto.so.3 = /lib/libcrypto.so.3 (0x280fe000)
  libcrypt.so.2 = /lib/libcrypt.so.2 (0x28208000)
  libcom_err.so.2 = /usr/lib/libcom_err.so.2 (0x28221000)
  libldap.so.2 = /usr/local/lib/libldap.so.2 (0x28223000)
  liblber.so.2 = /usr/local/lib/liblber.so.2 (0x28254000)
  libc.so.5 = /lib/libc.so.5 (0x2826)
  libsasl2.so.2 = /usr/local/lib/libsasl2.so.2 (0x28337000)
  libssl.so.3 = /usr/local/lib/libssl.so.3 (0x2834a000)
  libcrypto.so.3 = /usr/local/lib/libcrypto.so.3 (0x2837b000)
  
  It only complained about libldap.so.2, so I would guess kerberos is
  using the -rpath for the others?
 
 
 Oh, you must be using `WITH_OPENLDAP'--- an option that I did not even
 realize was available in the base system until I looked just now :-)
 
 Yes, I believe the build is broken and I will correct it after the
 code freeze.  In the meantime, you might try the following patch and
 rebuild the KDC (`make clean' first).
 
 Cheers,

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

ACPI results Inspiron 8000

[Melvyn Sopacua]

Hi,

I've done some testing with acpi:
S1 level - does not blank the display.
S2 level - unsupported by the BIOS
S3/S4 level - reboot the machine, with at best a print_cpu debug statement[1]
s5 level - works as expected

[1] I've pressed 'pause' and copied it for anybody that wants the register 
dump

I've set the dump device and dumpdir, but no dumps are created - it's a reboot 
without a panic apparently.

Attached are:
* dmesg.boot
* Kernel config
* acpidump output
* loader.conf
* S1 run output (the only way to wake-up is to 'open the lid')
* oids.start: relevant oids

Setting of 'os_name' does not make any difference whatsoever. I've also 
disabled any firewall and usb devices, but it doesn't make a difference as 
well.

If anything else is needed, let me know.

-- 
Melvyn

===
FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #2: Mon Dec  1 
17:58:47 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/
SAREVOK_NOFW_DBG  i386
===
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.2-BETA #2: Mon Dec  1 17:58:47 CET 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOFW_DBG
Preloaded elf kernel /boot/kernel/kernel at 0xc0923000.
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) M processor 1400MHz (1398.82-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x695  Stepping = 5
  
Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE
real memory  = 536535040 (511 MB)
avail memory = 511508480 (487 MB)
Pentium Pro MTRR support enabled
acpi0: DELL   CPi R   on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 9 entries at 0xc00fc590
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
acpi_cpu0: CPU port 0x530-0x537 on acpi0
acpi_tz0: Thermal Zone port 0x530-0x537 on acpi0
acpi_acad0: AC Adapter on acpi0
acpi_cmbat0: Control Method Battery on acpi0
acpi_cmbat1: Control Method Battery on acpi0
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib0: slot 29 INTA is routed to irq 11
pcib0: slot 29 INTB is routed to irq 11
pcib0: slot 29 INTC is routed to irq 11
pcib0: slot 29 INTD is routed to irq 11
pcib0: slot 31 INTB is routed to irq 11
agp0: Intel 82855 host to AGP bridge mem 0xe800-0xefff at device 0.0 on pci0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib1: slot 0 INTA is routed to irq 11
pci1: display, VGA at device 0.0 (no driver attached)
pci0: serial bus, USB at device 29.0 (no driver attached)
pci0: serial bus, USB at device 29.1 (no driver attached)
pci0: serial bus, USB at device 29.2 (no driver attached)
pci0: serial bus, USB at device 29.7 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0
pci2: ACPI PCI bus on pcib2
pcib2: slot 0 INTA is routed to irq 11
pcib2: slot 1 INTA is routed to irq 11
bfe0: Broadcom BCM4401 Fast Ethernet mem 0xfaffe000-0xfaff irq 11 at device 0.0 
on pci2
bfe0: Ethernet address: 00:0d:56:3c:1c:37
miibus0: MII bus on bfe0
bmtphy0: BCM4401 10/100baseTX PHY on miibus0
bmtphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
cbb0: TI4510 PCI-CardBus Bridge at device 1.0 on pci2
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
pcib2: slot 1 INTA is routed to irq 11
cbb0: [MPSAFE]
pci2: serial bus, FireWire at device 1.1 (no driver attached)
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel ICH4 UDMA100 controller port 
0xbfa0-0xbfaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
pcm0: Intel ICH4 (82801DB) port 0xbc40-0xbc7f,0xb800-0xb8ff mem 
0xf4fff400-0xf4fff4ff,0xf4fff800-0xf4fff9ff irq 11 at device 31.5 on pci0
pcm0: SigmaTel STAC9750/51 AC97 Codec
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 1 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: Parallel port bus on ppc0
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
orm0: Option ROMs at iomem 0xcf800-0xc,0xc-0xcf7ff on isa0
vga0: Generic ISA VGA 

Re: psmintr not attached w/ acpi

[Nate Lawson]

On Mon, 1 Dec 2003, Slawa Olhovchenkov wrote:
 On Mon, Dec 01, 2003 at 09:48:40AM -0800, Nate Lawson wrote:
  Your ASL indicates that it returns different values for present (based on
  PS2F) and current resources (based on KBDI).  Please send me the URL to
  the full ASL so I can see what sets those two variables.

 http://zxy.spb.ru/acpi.dump

 Do you need additional information?

Try this workaround, recompile your asl, set dsdt_load in loader.conf.
See acpi(4) if you need info on this process.  I think your BIOS needs a
workaround.  I wonder if the MS interpreter ignores _STA for some devices.

--- slawa-IntelLaptop.asl.orig  Mon Dec  1 10:54:18 2003
+++ slawa-IntelLaptop.asl   Mon Dec  1 10:57:39 2003
@@ -3353,14 +3353,7 @@
 Name (_HID, EisaId (PNP0F13))
 Method (_STA, 0, NotSerialized)
 {
-If (LEqual (PS2F, 0x00))
-{
 Return (0x0F)
-}
-Else
-{
-Return (0x00)
-}
 }

 Method (_CRS, 0, NotSerialized)

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

Re: [ATAng?] ad1 disappeared again

[Chris Faulhaber]

On Wed, Nov 26, 2003 at 01:00:47PM +0900, NAKAJI Hiroyuki wrote:
 Hi,
 
 I'm preparing new machine with 5-current. First, I installed a snapshot on
 Feb 21 2003. It works well. From the beginning of this week, I started
 updating it to the latest, and found the problem.
 
...
 ad0: 38166MB ST340810A [77545/16/63] at ata0-master UDMA100
 ad1: 38166MB ST340810A [77545/16/63] at ata0-slave UDMA100

I have been seeing the same issue since August with a different,
but similiar, set of drives:

ad0: 57241MB ST360015A [116301/16/63] at ata0-master UDMA100
ad1: 57241MB ST360015A [116301/16/63] at ata0-slave UDMA100

Under -CURRENT only the first drive is seen; RELENG_4 still works
fine.

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

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


pgp0.pgp
Description: PGP signature

Re: panic on 5.2 BETA: blockable sleep lock

[Don Lewis]

On  1 Dec, Roger Hardiman wrote:
 Hi
 
 Please can someone commit the bktr patch for me to fix 5.2-BETA
 (as long as re@ approve). I don't have the resources.

The patch has been committed with re@ approval.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Is booting/installing from USB CDROM considered supported?

[Andrew P. Lentvorski, Jr.]

On Mon, 1 Dec 2003, Martin Nilsson wrote:

 Is booting the install CD over a USB connected CDROM supposed to be
 working?

USB CDROM booting for FreeBSD currently does not work for either -stable
or -current.

I see exactly the same symptoms as you do.

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

Re: 5.2-BETA panic: page fault

[Don Lewis]

On  1 Dec, Stefan Ehmann wrote:
 On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
 Can you reproduce this problem without bktr?
 
 snip
 You are getting a double panic, with the second happening during the
 file system sync.  The code seems to be be tripping over the same mount
 list entry each time.  Maybe the mount list is getting corrupted.  Are
 you using amd?  Print *lkp in the lockmgr() stack frame.
 
 
 You might want to add
  KASSERT(mp-mnt_lock.lk_interlock !=NULL, vfs_busy: NULL mount
 pointer interlock);
 at the top of vfs_busy() and right before the lockmgr() call.
 
 No, I'm not using amd.
 
 (kgdb) print *lkp
 $1 = {lk_interlock = 0x0, lk_flags = 0, lk_sharecount = 0, lk_waitcount
 = 0, 
   lk_exclusivecount = 0, lk_prio = 0, lk_wmesg = 0x0, lk_timo = 0, 
   lk_lockholder = 0x0, lk_newlock = 0x0}
 
 This is indeed just NULLs.
 
 I haven't tried without bktr yet but I hope I'll have time for that (and
 the KASSERT) tomorrow.
 
 The panic only seems to happen when accessing my read-only mounted ext2
 partition. Today I tried not to access any data there and uptime is
 14h30min now. The panic always happened after a few hours. So this is
 probably the core of the problem.

What about ther file system types, like nullfs, unionfs, cd9660?  I
created an ext2 partition, filled it with data, and mounted it
read-only.  So far I am unable to reproduce this problem.

I'm also running with the DEBUG_VFS_LOCKS and the following patch in an
attempt to catch the bug closer to its origin.  Be forwarned that
DEBUG_VFS_LOCKS sometimes gets triggered by procfs and linprocfs, but
you can just continue in DDB.

Index: sys/kern/vfs_subr.c
===
RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v
retrieving revision 1.472
diff -u -r1.472 vfs_subr.c
--- sys/kern/vfs_subr.c 9 Nov 2003 09:17:24 -   1.472
+++ sys/kern/vfs_subr.c 1 Dec 2003 13:34:23 -
@@ -282,6 +282,9 @@
 void
 assert_vop_locked(struct vnode *vp, const char *str)
 {
+   if (vp  vp-v_mount)
+   KASSERT(vp-v_mount-mnt_lock.lk_interlock != NULL,
+   (assert_vop_locked: vnode mount entry interlock is null));
if (vp  !IGNORE_LOCK(vp)  !VOP_ISLOCKED(vp, NULL))
vfs_badlock(is not locked but should be, str, vp);
 }
@@ -289,6 +292,9 @@
 void
 assert_vop_unlocked(struct vnode *vp, const char *str)
 {
+   if (vp  vp-v_mount)
+   KASSERT(vp-v_mount-mnt_lock.lk_interlock != NULL,
+   (assert_vop_unlocked: vnode mount entry interlock is null));
if (vp  !IGNORE_LOCK(vp) 
VOP_ISLOCKED(vp, curthread) == LK_EXCLUSIVE)
vfs_badlock(is locked but should not be, str, vp);



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

Re: 5.2-BETA dsp.c duplicate lock

[Mathew Kanner]

On Dec 01, Maxime Henrion wrote:
 Jesse Guardiani wrote:
  Jesse Guardiani wrote:

 Index: isa/ad1816.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/isa/ad1816.c,v
 retrieving revision 1.29
 diff -u -p -r1.29 ad1816.c
 --- isa/ad1816.c  7 Sep 2003 16:28:02 -   1.29
 +++ isa/ad1816.c  1 Dec 2003 14:11:45 -
 @@ -593,7 +593,8 @@ ad1816_attach(device_t dev)
   ad1816 = (struct ad1816_info *)malloc(sizeof *ad1816, M_DEVBUF, M_NOWAIT | 
 M_ZERO);
   if (!ad1816) return ENXIO;
  
 - ad1816-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
 + ad1816-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc,
 + 0);
   ad1816-io_rid = 2;
   ad1816-irq_rid = 0;
   ad1816-drq1_rid = 0;
 Index: isa/mss.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/isa/mss.c,v
 retrieving revision 1.86
 diff -u -p -r1.86 mss.c
 --- isa/mss.c 7 Sep 2003 16:28:02 -   1.86
 +++ isa/mss.c 1 Dec 2003 14:11:53 -
 @@ -1667,7 +1667,7 @@ mss_doattach(device_t dev, struct mss_in
   int pdma, rdma, flags = device_get_flags(dev);
   char status[SND_STATUSLEN], status2[SND_STATUSLEN];
  
 - mss-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
 + mss-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
   mss-bufsize = pcm_getbuffersize(dev, 4096, MSS_DEFAULT_BUFSZ, 65536);
   if (!mss_alloc_resources(mss, dev)) goto no;
   mss_init(mss, dev);
 Index: isa/sbc.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/isa/sbc.c,v
 retrieving revision 1.38
 diff -u -p -r1.38 sbc.c
 --- isa/sbc.c 7 Feb 2003 14:05:33 -   1.38
 +++ isa/sbc.c 1 Dec 2003 14:12:03 -
 @@ -116,7 +116,8 @@ static void sb_setmixer(struct resource 
  static void
  sbc_lockinit(struct sbc_softc *scp)
  {
 - scp-lock = snd_mtxcreate(device_get_nameunit(scp-dev), sound softc);
 + scp-lock = snd_mtxcreate(device_get_nameunit(scp-dev), sound softc,
 + 0);
  }
  
  static void
 Index: pci/cmi.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/pci/cmi.c,v
 retrieving revision 1.23
 diff -u -p -r1.23 cmi.c
 --- pci/cmi.c 2 Sep 2003 17:30:37 -   1.23
 +++ pci/cmi.c 1 Dec 2003 14:12:15 -
 @@ -842,7 +842,7 @@ cmi_attach(device_t dev)
   return ENXIO;
   }
  
 - sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
 + sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
   data = pci_read_config(dev, PCIR_COMMAND, 2);
   data |= (PCIM_CMD_PORTEN|PCIM_CMD_BUSMASTEREN);
   pci_write_config(dev, PCIR_COMMAND, data, 2);
 Index: pci/ds1.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/pci/ds1.c,v
 retrieving revision 1.36
 diff -u -p -r1.36 ds1.c
 --- pci/ds1.c 2 Sep 2003 17:30:37 -   1.36
 +++ pci/ds1.c 1 Dec 2003 14:12:26 -
 @@ -942,7 +945,7 @@ ds_pci_attach(device_t dev)
   return ENXIO;
   }
  
 - sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
 + sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
   sc-dev = dev;
   subdev = (pci_get_subdevice(dev)  16) | pci_get_subvendor(dev);
   sc-type = ds_finddev(pci_get_devid(dev), subdev);
 Index: pci/emu10k1.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/pci/emu10k1.c,v
 retrieving revision 1.41
 diff -u -p -r1.41 emu10k1.c
 --- pci/emu10k1.c 7 Sep 2003 16:28:03 -   1.41
 +++ pci/emu10k1.c 1 Dec 2003 14:12:35 -
 @@ -1468,7 +1468,7 @@ emu_pci_attach(device_t dev)
   return ENXIO;
   }
  
 - sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
 + sc-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
   sc-dev = dev;
   sc-type = pci_get_devid(dev);
   sc-rev = pci_get_revid(dev);
 Index: pci/t4dwave.c
 ===
 RCS file: /space2/ncvs/src/sys/dev/sound/pci/t4dwave.c,v
 retrieving revision 1.40
 diff -u -p -r1.40 t4dwave.c
 --- pci/t4dwave.c 7 Sep 2003 16:28:03 -   1.40
 +++ pci/t4dwave.c 1 Dec 2003 14:12:42 -
 @@ -811,7 +811,7 @@ tr_pci_attach(device_t dev)
  
   tr-type = pci_get_devid(dev);
   tr-rev = pci_get_revid(dev);
 - tr-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc);
 + tr-lock = snd_mtxcreate(device_get_nameunit(dev), sound softc, 0);
  
   data = pci_read_config(dev, PCIR_COMMAND, 2);
   data |= (PCIM_CMD_PORTEN|PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN);
 Index: pcm/ac97.c
 ===
 RCS file: 

Re: psmintr not attached w/ acpi

[Slawa Olhovchenkov]

On Mon, Dec 01, 2003 at 10:59:49AM -0800, Nate Lawson wrote:

  On Mon, Dec 01, 2003 at 09:48:40AM -0800, Nate Lawson wrote:
   Your ASL indicates that it returns different values for present (based on
   PS2F) and current resources (based on KBDI).  Please send me the URL to
   the full ASL so I can see what sets those two variables.
 
  http://zxy.spb.ru/acpi.dump
 
  Do you need additional information?
 
 Try this workaround, recompile your asl, set dsdt_load in loader.conf.
 See acpi(4) if you need info on this process.  I think your BIOS needs a
 workaround.  I wonder if the MS interpreter ignores _STA for some devices.

I try recompile asl and got some errors:

===
iasl acpi.dump

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20030619 [Nov 25 2003]
Copyright (C) 2000 - 2003 Intel Corporation
Supports ACPI Specification Revision 2.0b

acpi.dump84: And (SUSF, 0x02, STAT)
Error1037 -^ syntax error

ASL Input:  acpi.dump - 3574 lines, 113232 bytes, 12 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 9 Optimizations
===

I commented out this line and try again.

===
iasl acpi.dump

Intel ACPI Component Architecture
ASL Optimizing Compiler / AML Disassembler version 20030619 [Nov 25 2003]
Copyright (C) 2000 - 2003 Intel Corporation
Supports ACPI Specification Revision 2.0b

acpi.dump   352: Method (\_WAK, 1, NotSerialized)
Warning  2026 -  ^ Reserved method must return a value (_WAK)

acpi.dump   382: Store (Local0, Local0)
Error1013 -  ^ Method local variable is not initialized 
(Local0)

acpi.dump   387: Store (Local0, Local0)
Error1013 -  ^ Method local variable is not initialized 
(Local0)

acpi.dump  1609: ICF0,   2,
Error1051 - ^ Access width of Field Unit extends beyond 
region limit

acpi.dump  1610: ICF1,   2,
Error1051 - ^ Access width of Field Unit extends beyond 
region limit

acpi.dump  1612: WPPE,   1,
Error1051 - ^ Access width of Field Unit extends beyond 
region limit

acpi.dump  1614: FAS0,   2,
Error1051 - ^ Access width of Field Unit extends beyond 
region limit

acpi.dump  1615: FAS1,   2
Error1051 - ^ Access width of Field Unit extends beyond 
region limit

ASL Input:  acpi.dump - 3850 lines, 119353 bytes, 1690 keywords
Compilation complete. 7 Errors, 1 Warnings, 0 Remarks, 345 Optimizations
===

What is wrong?

 --- slawa-IntelLaptop.asl.origMon Dec  1 10:54:18 2003
 +++ slawa-IntelLaptop.asl Mon Dec  1 10:57:39 2003
 @@ -3353,14 +3353,7 @@
  Name (_HID, EisaId (PNP0F13))
  Method (_STA, 0, NotSerialized)
  {
 -If (LEqual (PS2F, 0x00))
 -{
  Return (0x0F)
 -}
 -Else
 -{
 -Return (0x00)
 -}
  }
 
  Method (_CRS, 0, NotSerialized)
 
 -Nate


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

Reading advice for compiler RunTime environment

[Willem Jan Withagen]

Hi,

I have a sort of working Pascal compiler up and running.
It used to be an old research project of mine, which never really made it
out since I started to play ISP. The last build was done in the COFF area,
and I've found that things have somewhat changed...

Small programs are working, because I've made the main pascal program look
like a C-main routine. Perhaps not quite needed. But for instance, debugging
is totally non existant

So I'm looking for hints to read to catch up on these matters,

Thanx,
--WjW

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

Re: boot process is too slow during installation

[Dorin H]

FWIW: I am also using an USB to boot install the
FreeBSD on my Toshiba 3480CT lap. It is a Toshiba
PA3043U-1FDD; BUT it takes no more than a couple of
minutes to load the 4.8 kern and mfsroot floppies.
/Dorin.

--- Zhang Shu [EMAIL PROTECTED] wrote:
 Hi,
 
 I am trying to install the current-FreeBSD to my
 Vaio PCG-Z1/P but found
 the installation boot process is extremely slow. It
 takes more than 10
 minutes to finish loading the disk created from
 kern.flp and another 10
 minutes for mfsroot.flp. Does anyone know what the
 problem is?
 
 The USB floppy drive I am using is sony's PCGA-UF05.
 The same thing
 happens with another USB floppy drive which I don't
 remember the model.
 
 I also tried to boot the installation disks of 4.8R,
 4.9R and 5.1R but
 the result were the same.
 
 Thanks.
 
 Zhang Shu
 ___
 [EMAIL PROTECTED] mailing list

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


__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: licq KSE

[Daniel Eischen]

On Mon, 1 Dec 2003, Alexander Motin wrote:

 Hi!
 
 licq 1.2.7 installed from ports does not works on 5.2-BETA with mapping 
 libc_r to libkse:
 
 %licq -d0 -p qt-gui -- -noxim
 Fatal error 'No current thread.
 ' at line 318 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2)

I just built and installed this under -current and it
seems to work fine.  I invoke it as you describe above.

Are you using an nvidia driver or openGL?

-- 
Dan Eischen

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

RE: ACPI results Inspiron 8000

[Thomas]

Hi

If you just looking for working acpi with your inspiron 8000 then try this patches at 
http://sandcat.nl/~stijn/freebsd/dell.php. It works for me with -current. 

regards
Thomas Vogt
Hi,

I've done some testing with acpi:
S1 level - does not blank the display.
S2 level - unsupported by the BIOS
S3/S4 level - reboot the machine, with at best a print_cpu debug statement=
[1]
s5 level - works as expected
[1] I've pressed 'pause' and copied it for anybody that wants the register=
=20
dump
I've set the dump device and dumpdir, but no dumps are created - it's a reb=
oot=20
without a panic apparently.
Attached are:
* dmesg.boot
* Kernel config
* acpidump output
* loader.conf
* S1 run output (the only way to wake-up is to 'open the lid')
* oids.start: relevant oids


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

Re: 5.2-RELEASE TODO

[Paul Murphy]

On Mon, 1 Dec 2003 10:01:23 -0500 (EST)
Robert Watson [EMAIL PROTECTED] wrote:

 This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues
 list. The live version of this list is available at:
 
 http://www.FreeBSD.org/releases/5.2R/todo.html
 
 Automated mailing of this list will continue through the release of
 FreeBSD 5.2.
 
 

 Just wondering if, when one is announced, you could include in this
messages the release date forecast.

-- 
Cogeco ergo sum


pgp0.pgp
Description: PGP signature

FreeBSD.org site down

[Nigel Weeks]

Sorry if I'm posting to the wrong place, but is anyone able to get to
www.freebsd.org?

It appears the webserver has stopped.

Again, sorry If this is the wrong place.


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

Sleep on Non-sleep lock / LOR with Radeon DRM driver

[Ryan]

I received the following when shutting X down.

If you need any other info please let me know.

PS
I wasn't able to find any reports of this in the current@ or the PR
database. Should I submit a PR as well?

-
Sleeping on itrmh with the following non-sleepable locks held:
exclusive sleep mutex drm device r = 0 (0xc43e1064) locked @
@/dev/drm/drm_irq.h:192
lock order reversal
 1st 0xc43e1064 drm device (drm device) @ @/dev/drm/drm_irq.h:192
 2nd 0xc06e3de0 Giant (Giant) @ /usr/src/sys/kern/kern_synch.c:307
Stack backtrace:
backtrace(c0692e54,c06e3de0,c068f29a,c068f29a,c0690314) at backtrace+0x17
witness_lock(c06e3de0,8,c0690314,133,c1913800) at witness_lock+0x672
_mtx_lock_flags(c06e3de0,0,c0690314,133,0) at _mtx_lock_flags+0xba
msleep(c4539c40,c1913800,a0,c068d951,0) at msleep+0x734
ithread_remove_handler(c4539c40,dc8fc9c8,c064cc91,c4539c40,dc8fc9f0) at
ithread_remove_handler+0x14c
intr_remove_handler(c4539c40,dc8fc9f0,c052cf00,c1914c80,c43edd80) at
intr_remove_handler+0x11
nexus_teardown_intr(c1914c80,c43edd80,c4539c00,c4539c40,c43edd80) at
nexus_teardown_intr+0x11
bus_generic_teardown_intr(c1914c00,c43edd80,c4539c00,c4539c40,c43edd80) at
bus_generic_teardown_intr+0x70
bus_generic_teardown_intr(c1914800,c43edd80,c4539c00,c4539c40,c43edd80) at
bus_generic_teardown_intr+0x70
bus_generic_teardown_intr(c43ec600,c43edd80,c4539c00,c4539c40,c43edd80) at
bus_generic_teardown_intr+0x70
bus_generic_teardown_intr(c43ec780,c43edd80,c4539c00,c4539c40,c43edd80) at
bus_generic_teardown_intr+0x70
bus_generic_teardown_intr(c43ede80,c43edd80,c4539c00,c4539c40,c43edd80) at
bus_generic_teardown_intr+0x70
bus_teardown_intr(c43edd80,c4539c00,c4539c40,c43e1064,c43e1064) at
bus_teardown_intr+0x75
radeon_irq_uninstall(c43e1000,0,c07c3727,c0,c07c6110) at
radeon_irq_uninstall+0x61
radeon_control(c06e2100,80086414,dc8fcc58,43,c4544000) at radeon_control+0x8b
radeon_ioctl(c06e2100,80086414,dc8fcc58,43,c4544000) at radeon_ioctl+0x1e6
spec_ioctl(dc8fcb80,dc8fcc2c,c057b341,dc8fcb80,c4544070) at spec_ioctl+0x19e
spec_vnoperate(dc8fcb80,c4544070,c06e7d20,5f5,c06d8660) at
spec_vnoperate+0x18
vn_ioctl(c456b61c,80086414,dc8fcc58,c4749000,c4544000) at vn_ioctl+0x1a1
ioctl(c4544000,dc8fcd14,c06a6081,3ee,3) at ioctl+0x481
syscall(2f,8b4002f,bfbf002f,8932c00,8736000) at syscall+0x2c0
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (54), eip = 0x28255c2f, esp = 0xbfbfeb7c, ebp = 0xbfbfeb98 ---

-- 
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO

-= http://www.gamersimpact.com =-

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

RE: ACPI results Inspiron 8000

[Ryan]

Are you able to suspend to disk? So far I haven't been able to suspend to
disk on my Inspiron 8200. I'm using the fixed DSDT table from the URL
you posted as well.

-- 
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO

-= http://www.gamersimpact.com =-

Thomas said:
 Hi

 If you just looking for working acpi with your inspiron 8000 then try this
 patches at
 http://sandcat.nl/~stijn/freebsd/dell.php. It works for me with -current.

 regards
 Thomas Vogt

Hi,

I've done some testing with acpi:
S1 level - does not blank the display.
S2 level - unsupported by the BIOS
S3/S4 level - reboot the machine, with at best a print_cpu debug
 statement=
[1]
s5 level - works as expected

[1] I've pressed 'pause' and copied it for anybody that wants the
 register=
=20
dump

I've set the dump device and dumpdir, but no dumps are created - it's a
 reb=
oot=20
without a panic apparently.

Attached are:
* dmesg.boot
* Kernel config
* acpidump output
* loader.conf
* S1 run output (the only way to wake-up is to 'open the lid')
* oids.start: relevant oids



 ___
 [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]

FreeBSD.org site down...NOT

[Nigel Weeks]

Sorry again. My Bad.


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

Re: NSS and PAM

[Dag-Erling Smørgrav]

Jacques A. Vidrine [EMAIL PROTECTED] writes:
 Hmm, I disagree completely.  :-)  [...]

You are bringing authorization into the fray...  we're talking about
directory services (retrieving information about a user) and
authentication (identifying someone as that user), not authorization.

  Also, is changing your password an authentication function or a
  directory function?  I don't think you can answer either without
  answering both.
 I think it is strictly an authentication function.  The change in your
 password has no affect on your UID, or your phone number, or in what
 ACLs your name appears in.

The problem is that the authentication information needs to be stored
somewhere, and the usual solution is to store it in the directory, so
changing the password involves both authentication and directory
services.

 Backward compatibility is fine, but NSS does not seem to export an API
 that we can use when we want to lift ourselves out of the mud, so we
 are forced to keep rooting around in it.  
 What's an example of what you mean?  The BSD nsswitch implementation
 has a generic nsdispatch(3) that allows for new applications, but I'm
 not sure that is what you mean.  At any rate, it is not `NSS' proper, it
 is an implementation detail.

Like you say, it is an implementation detail, and it is far too
low-level to be of use.  We need an API that retrieves information
about a user according to rules established by the administrator
(nsswitch.conf or pam.conf or whatever) and is flexible enough to
handle the fact that different directories store different amounts of
information about the users at different levels of detail (for
instance, LDAP stores first and last name separately while /etc/passwd
only has the one GCOS field).

 It seems to me that this is a direct result of passwd(1) confusing
 authentication and authorization.  Other than determining the default
 target user name from the current UID, passwd(1) needs only to invoke
 PAM interfaces to change your password for any authentication method
 that supports password changing.

No, because PAM doesn't control retrieval of the user information.  If
it did, it would be as simple as you say, but it doesn't - NSS does -
so it's a nightmare.  Imagine the case where different directories
contain different entries for the same user, or for different users
who happen to have the same name; this is standard practice with NIS.
Which directory do you write the modified entry into?  The obvious
answer is the one it came out of in the first place, but PAM doesn't
know which one that was.

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

Re: Ports startup scripts in /etc/rc.d (Re: 5.2-BETA and related ports issues)

[Matthias Andree]

Robert Watson [EMAIL PROTECTED] writes:

 (1) Combine / and /usr into a single file system by default, and add
 /usr/local/etc/rc.d to the search order, with appropriate hacks to
 handle old-style scripts.  The devil will be in the bikeshed, but the
 implementation is easy, except for the bit where we explain that
 NFS-mounted /usr/local won't work too well.

I'd discourage that. It's fairly intrusive and breaks existing
setups. I'm NOT going to repartition and reinstall!

 (2) Reevaluate the order at routine points in the boot where new scripts
 might now be available (due to file system mounts or whatever).
 Essentially insert the new cards into the deck, and shuffle.  This
 requires rethinking of our current approach, which assumes a static
 order is created once at the start of the boot by rcorder(8).  The
 devil will be in the big picture *and* the details of the
 implementation.

I don't think there shall be devils in the implementation details. I
admit not having looked at rcorder yet, but dependencies can be passed
on from one rcorder run to the next, through the usual process
environment.

 (3) Add /local/etc/rc.d or /local/rc.d or /etc/local/rc.d or the like, a
 new directory that third party applications are allowed to modify
 during install, and that will be present for the creation of the
 static ordering by rcorder(8) early in the boot.  The devil will be in
 the bikeshed, but the implementation is easy.

/etc/local/rc.d might work, it's quite similar to the /etc/opt approach
configuration stuff for /opt applications on Linux.

 I'm actually leaning towards (2) as being the best solution, as it's easy
 and functional.

Seconded from the user's view.

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ACPI results Inspiron 8000

[Melvyn Sopacua]

On Monday 01 December 2003 22:56, Thomas wrote:

 If you just looking for working acpi with your inspiron 8000 then try this
 patches at http://sandcat.nl/~stijn/freebsd/dell.php. It works for me with
 -current.

Thanx. It mentions the ports version of acpidump and iasl, which are already 
in my base system. Is there a difference or should the port be marked as 
BROKEN if OSREL  5.2?


-- 
Melvyn

===
FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #2: Mon Dec  1 
17:58:47 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/
SAREVOK_NOFW_DBG  i386
===


pgp0.pgp
Description: signature

Re: NSS and PAM

[Garrett Wollman]

On Mon, 01 Dec 2003 23:24:40 +0100, [EMAIL PROTECTED] (Dag-Erling 
=?iso-8859-1?q?Sm=F8rgrav?=) said:

 The problem is that the authentication information needs to be stored
 somewhere, and the usual solution is to store it in the directory, 

...which is usually the worst possible place.  Please don't penalize
those of us with sensible authentication systems.

-GAWollman

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

Re: 5.2-BETA dsp.c duplicate lock

[Maxime Henrion]

Mathew Kanner wrote:
[patch ripped]
 
   Maxime,
   I think it would be better to isolate the changes (DUP_OK flag
 and lock creation) to just the channel code, no need to touch every
 driver.

Yes, but to do this I'd need either to make the channel code use
mtx_init() directly, which would defeat the purpose of the USING_MUTEX
define, or to completely unifdef -U it.  Since I had no idea if this code
was actually used or not, I went the safe way and just changed the
snd_mtxcreate() wrapper interface to accept mutex options.  For what it's
worth, there is at least one direct invokation of mtx_init() in the sound
drivers, so it seems this define is actually already broken.

This needs to be sorted out before committing this patch if we need to,
but for now, I just wanted to see if using MTX_DUPOK solved the problem or
not.

 Also, if this is the right direction, we should back out the
 commit I did that re-ordered code that prevented duplicate channel
 locks (obviously it wasn't completen) channel.

If the code is not supposed to acquire several channel locks at once,
then yes, it's not the right direction to go.  As I said in my previous
mail, and that's why I wanted the advice of you sound guys, in that case
it's just a workaround. :-)

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

Re: NSS and PAM

[Dag-Erling Smørgrav]

Garrett Wollman [EMAIL PROTECTED] writes:
 On Mon, 01 Dec 2003 23:24:40 +0100, [EMAIL PROTECTED] (Dag-Erling 
 =?iso-8859-1?q?Sm=F8rgrav?=) said:
  The problem is that the authentication information needs to be stored
  somewhere, and the usual solution is to store it in the directory, 
 ...which is usually the worst possible place.  Please don't penalize
 those of us with sensible authentication systems.

You're the one trying to penalize other people.  A common framework
for directory and authentication services can of course store
authentication tokens separately from user information, but the
reverse isn't true.  You can't unilaterally decide to leave out
functionality that 90% of our users require just because you are in a
position to use (what you consider to be) a better solution.

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

Re: ACPI results Inspiron 8000

[Daniel O'Connor]

On Tuesday 02 December 2003 08:46, Ryan wrote:
 Are you able to suspend to disk? So far I haven't been able to suspend to
 disk on my Inspiron 8200. I'm using the fixed DSDT table from the URL
 you posted as well.

I used to suspend to disk in 4.x after creating the S2D partition with the 
floppy image from Dell, however I don't any more..

Basically it takes so long to suspend and resume with a decent amount of 
memory (256Mb+) that it's not worth it - most of my applications are smart 
enough to save state when they quit :)

I suspect the story would be different if FreeBSD did the hard work (ie it 
could use DMA, compression, throw away cache pages etc etc) but just thinking 
about how to resume makes my head hurt.

-- 
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: 5.2-RELEASE TODO

[Greg 'groggy' Lehey]

On Monday,  1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
 This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
 
 Show stopper defects for 5.2-RELEASE
 
  ++
  |   Issue   |  Status   |Responsible |Description|
  |---+---++---|
  |   |   ||The new i386 interrupt code|
  |ACPI kernel|   ||requires that ACPI be compiled into|
  |module |In progress|John Baldwin|the kernel if it to be used. Work  |
  |   |   ||is underway to restore the ability |
  |   |   ||to load it as a module.|
  |---+---++---|

I'm currently investigating ACPI problems on a dual processor Intel
motherboard (re@ knows about this).  It looks as if the new code is
much fussier than the old code about the quality of the motherboard
BIOS: this machine runs fine on 5.1, but won't finish booting on
5.2-BETA.  Yes, this is probably an ACPI bug, but users aren't going
to see it that way: if we release a 5.2 which won't boot on a lot of
machines, people are going to blame 5.2, not the machine.  I think we
should ensure that there's at least a fallback for machines with
broken ACPI.

Greg
-- 
See complete headers for address and phone numbers.


pgp0.pgp
Description: PGP signature

Update to fix 'installworld' for 5.2

[Garance A Drosihn]

Here is an update I would like to install before 5.2-release.
This fixes the problems that people will run into during
'make installworld' when doing a source-upgrade from
5.1-release or 5.1-security to (what will be) 5.2-release.
To test this, I first upgraded a system to 5.1-RELEASE-p11.
I then created a /usr/src-curr which was the current source
tree, and did a buildworld and buildkernel.
I then copied that OS to another set of partitions, booted
up into the copy, and tried the normal installkernel-reboot-
installworld sequence.  The installation was hosed, due to
programs in /bin which reference files in a not-yet-existent
/libexec.  Recovery is possible, but can be somewhat painful.
I booted back into a working system, and re-copied the
original set of partitions to the test partitions.  I booted
into the test partitions, applied this update, and tried the
same installkernel-reboot-installworld sequence.  This did
not run into any problems (as long as one follows the rest
of the instructions in /usr/src/UPDATING).
I have brought this issue up on -current, but no one has
responded with a reason why the install for /libexec should
*not* be moved up.  So, I think it should be moved up, now
that I've tested that it does seem to work OK.
As near as I can tell, the special check for libexec/rtld-elf
never did work, and in any case it will be unnecessary if we
unconditionally install all of libexec at that point.
Index: Makefile.inc1
===
RCS file: /usr/cvs/free/depot/src/Makefile.inc1,v
retrieving revision 1.397
diff -u -u -r1.397 Makefile.inc1
--- Makefile.inc1   16 Nov 2003 21:17:43 -  1.397
+++ Makefile.inc1   1 Dec 2003 23:10:45 -
@@ -49,16 +49,8 @@
 .if exists(${.CURDIR}/lib)
 SUBDIR+= lib
 .endif
-
-# When upgrading to a dynamically linked root, install the runtime
-# linker early into its new location before make(1) has a chance
-# to run the dynamically linked /bin/sh.
-.if !defined(NO_DYNAMICROOT)  !defined(NOPIC)  \
-(!defined(TARGET_ARCH) || ${TARGET_ARCH} == ${MACHINE_ARCH})  \
-!defined(DISTDIR)  \
-(!defined(DESTDIR) || empty(DESTDIR) || ${DESTDIR} == /)  \
-!exists(/libexec/ld-elf.so.1)
-SUBDIR+= libexec/rtld-elf
+.if exists(${.CURDIR}/libexec)
+SUBDIR+= libexec
 .endif
 .if exists(${.CURDIR}/bin)
@@ -73,9 +65,6 @@
 .if exists(${.CURDIR}/kerberos5)  exists(${.CURDIR}/crypto)  \
 !defined(NOCRYPT)  !defined(NO_OPENSSL)  !defined(NO_KERBEROS)
 SUBDIR+= kerberos5
-.endif
-.if exists(${.CURDIR}/libexec)
-SUBDIR+= libexec
 .endif
 .if exists(${.CURDIR}/rescue)  !defined(NO_RESCUE)
 SUBDIR+= rescue
--
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 5.2-RELEASE TODO

[Scott Long]

On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
 On Monday,  1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
  This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
 
  Show stopper defects for 5.2-RELEASE
 
   ++
   |   Issue   |  Status   |Responsible |Description|
   |---+---++---|
   |   |   ||The new i386 interrupt code|
   |ACPI kernel|   ||requires that ACPI be compiled into|
   |module |In progress|John Baldwin|the kernel if it to be used. Work  |
   |   |   ||is underway to restore the ability |
   |   |   ||to load it as a module.|
   |---+---++---|

 I'm currently investigating ACPI problems on a dual processor Intel
 motherboard (re@ knows about this).  It looks as if the new code is
 much fussier than the old code about the quality of the motherboard
 BIOS: this machine runs fine on 5.1, but won't finish booting on
 5.2-BETA.  Yes, this is probably an ACPI bug, but users aren't going
 to see it that way: if we release a 5.2 which won't boot on a lot of
 machines, people are going to blame 5.2, not the machine.  I think we
 should ensure that there's at least a fallback for machines with
 broken ACPI.

This argument is exactly why I added the 'disable acpi' option in the boot
loader menu.  Of course, we STILL need to get good debugging information
from you as to why you get a Trap 9 when ACPI is disabled.  This is the
more important issue.

Scott

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

Re: 5.2-RELEASE TODO

[Greg 'groggy' Lehey]

On Monday,  1 December 2003 at 17:12:23 -0700, Scott Long wrote:
 On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
 On Monday,  1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
 This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.

 Show stopper defects for 5.2-RELEASE

 I'm currently investigating ACPI problems on a dual processor Intel
 motherboard (re@ knows about this).  It looks as if the new code is
 much fussier than the old code about the quality of the motherboard
 BIOS: this machine runs fine on 5.1, but won't finish booting on
 5.2-BETA.  Yes, this is probably an ACPI bug, but users aren't going
 to see it that way: if we release a 5.2 which won't boot on a lot of
 machines, people are going to blame 5.2, not the machine.  I think we
 should ensure that there's at least a fallback for machines with
 broken ACPI.

 This argument is exactly why I added the 'disable acpi' option in the boot
 loader menu.  Of course, we STILL need to get good debugging information
 from you as to why you get a Trap 9 when ACPI is disabled.  This is the
 more important issue.

I've sent information, and I'm waiting for feedback about what to do
next.  The fact that the stack is completely trashed doesn't help,
admittedly.

Greg
--
See complete headers for address and phone numbers.


pgp0.pgp
Description: PGP signature

Atheros netstat error

[Marcos Biscaysaqu]

Hi there.
I running an script every 4 sec. on my Freebsd Atheros Access Point to 
log the netstat errors and I can confirm every time I have more than 3 
Ierrs per sec or Oerrs per sec.. my ping to the clients box start to be 
very high and the connection work very slow until the error go down 
again, please someone has a similar problem or someone can help me  any 
aditional information?
thanks a lot

Ierrs Errors 27
Oerrs Errores 2
Ierrs Errors 21
Oerrs Errores 0
Ierrs Errors 23
Oerrs Errores 7
Ierrs Errors 26
Oerrs Errores 1
Ierrs Errors 35
Oerrs Errores 3
Ierrs Errors 22
Oerrs Errores 5
Ierrs Errors 21
Oerrs Errores 3
Ierrs Errors 0
Oerrs Errores 5
Ierrs Errors 2
Oerrs Errores 6
Ierrs Errors 6-- 

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

ATAPI CD still not detected, verbose boot logs available

[Christoph Sold]

Hi All, 
 
FreeBSD 5.2-B still does not detect my ATAPI DVD-ROM drive. This used to  
work until Søren's ATAng commits. Other OSes (Win, Linux, Solaris)  
detect the drive appropriately. 
 
# uname -a 
FreeBSD kiste.local 5.2-BETA FreeBSD 5.2-BETA #14: Sun Nov 30 18:51:31  
CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386 
# atacontrol list 
ATA channel 0: 
Master:  ad0 ST340823A/3.39 ATA/ATAPI rev 4 
Slave:   no device present 
ATA channel 1: 
Master:  ad2 SAMSUNG SP1203N/TL100-23 ATA/ATAPI rev 7 
Slave:  acd0 SONY CD-RW CRX140E/1.0s ATA/ATAPI rev 0 
 
should read (sometimes the drive _is_ detected): 
 
# atacontrol list 
ATA channel 0: 
Master:  ad0 ST340823A/3.39 ATA/ATAPI rev 4 
Slave:  acd0 _NEC DVD_RW ND-1300A/1.07 ATA/ATAPI rev 0 
ATA channel 1: 
Master:  ad2 SAMSUNG SP1203N/TL100-23 ATA/ATAPI rev 7 
Slave:  acd1 SONY CD-RW CRX140E/1.0s ATA/ATAPI rev 0 
 
Verbose boot logs, both with and without detecting the DVD burner on  
ATA-0 slave, are available at 
 
   http://cheasy.dyndns.org/bootlogs/ 
 
Remote access to the box may be possible for debugging purposes. Other  
help may be available on request. 
 
Thanks for all the good work so far. 
Christoph Sold 
__
WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130

smime.p7s
Description: S/MIME Cryptographic Signature

Re: Atheros netstat error

[Leo Bicknell]

In an effort to cut down on Sam's load...

This is a known issue.  Evidently there are some low level radio
counters that are incorrectly being reported as input errors.
Basically they should be ignored until the driver can be changed
to not report them.


-- 
   Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - [EMAIL PROTECTED], www.tmbg.org


pgp0.pgp
Description: PGP signature

Re: Atheros netstat error

[Marcos Biscaysaqu]

Hi there.
I running an script every 4 sec. on my Freebsd Atheros Access Point to 
log the netstat errors and I can confirm every time I have more than 3 
Ierrs per sec or Oerrs per sec.. my ping to the clients box start to 
be very high and the connection work very slow until the error go down 
again, please someone has a similar problem or someone can help me  
any aditional information?
logs aditional info:
Atheros# tail /var/log/messages
Dec  1 18:00:00 Atheros newsyslog[2014]: logfile turned over due to 
size100K
Dec  2 11:16:13 Atheros kernel: ath0: bogus xmit rate 0x0

thanks a lot

Ierrs Errors 27
Oerrs Errores 2
Ierrs Errors 21
Oerrs Errores 0
Ierrs Errors 23
Oerrs Errores 7
Ierrs Errors 26
Oerrs Errores 1
Ierrs Errors 35
Oerrs Errores 3
Ierrs Errors 22
Oerrs Errores 5
Ierrs Errors 21
Oerrs Errores 3
Ierrs Errors 0
Oerrs Errores 5
Ierrs Errors 2
Oerrs Errores 6
Ierrs Errors 6--
Marcos Biscaysaqu
Systems Administrator
ThePacific.Net Ltd.


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


--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: Atheros netstat error

[Marcos Biscaysaqu]

Hi Leo.
   Thanks for the information, but do you know if is some thing to do 
to fix this? or simply I need wait for another driver version, because 
the driver looks so much better than a couple a week ago, the only bad 
thing is this problem and when happen  kill all the wireless network
Thanks

Leo Bicknell wrote:

In an effort to cut down on Sam's load...

This is a known issue.  Evidently there are some low level radio
counters that are incorrectly being reported as input errors.
Basically they should be ignored until the driver can be changed
to not report them.
 

--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: Atheros netstat error

[Sam Leffler]

On Monday 01 December 2003 05:25 pm, Leo Bicknell wrote:
 In an effort to cut down on Sam's load...

 This is a known issue.  Evidently there are some low level radio
 counters that are incorrectly being reported as input errors.
 Basically they should be ignored until the driver can be changed
 to not report them.

I changed this a while ago; phy errors are no longer counted as input errors.

Sam

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

Re: NSS and PAM

[Tim Kientzle]

Garrett Wollman wrote:
On Mon, 01 Dec 2003 23:24:40 +0100, [EMAIL PROTECTED] (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) said:

The problem is that the authentication information needs to be stored
somewhere, and the usual solution is to store it in the directory, 
...which is usually the worst possible place.  Please don't penalize
those of us with sensible authentication systems.
Care to elaborate, Garrett?  I've been following this discussion
with some interest, and would like to see people elucidate their
positions and concerns.  Both DES and Jacques have made some
interesting points so far.
What exactly is your sensible authentication system?

Why is the directory usually the worst for storing
authentication information?
What do you think are the correct fracture points and
how do they relate to the existing PAM/NSS frameworks?
Tim

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

Re: [Fwd: re: ath0 lost connection]

[Eric Anderson]

Marcos Biscaysaqu wrote:

On a simpler yet related config, I have a linksys ag520 pci card 
running with a linksys a/b/g AP. IT occasionally just loses 
connectivity, but simply re-execing the ifconfig line brings it back. 
Haven't found a rhyme or reason yet.

I'd send this to the FBSD list, but I just moved server IP blocks and 
the reverse DNS stuff hasn't propagated yet.
I'm having the same problem - Sam knows about it (I've been annoying him 
for about a week and a half with info - sorry Sam!)..  I think he may be 
working on it, but he may want more details from you. 

One question - does it drop when in A, B, and G modes?  Or just one 
mode?  It seemed to me that my connection was better when using 11b mode 
(to a B/G ap).  Just curious.

Also - is shared mode authentication ever going to work in FreeBSD?  
Does anyone know what the problem with it is?

Eric



--
--
Eric Anderson  Systems Administrator  Centaur Technology
All generalizations are false, including this one.
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

[PATCH] fixes of tcp_hostcache.c

[Taku YAMAMOTO]

Greetings,

I found two calls of bcopy() in tcp_hostcache.c got the source and the
destination pointer wrongly.
# Perhaps the author got confused with memcpy(), I guess.

The fix is attached as a patch against tcp_hostcache.c as of revision 1.2.

Please review and incorporate the patch to the tree because the bug makes
hostcache useless with TCPv6 and/or brings TTCP (RFC1644) meaningless.
Especially the bug renders it unusable to use TCPv6 and TTCP together.
# To confirm this: sysctl net.inet.tcp.rfc1644=1; telnet ::1

Best regards,
Taku
-- 
-|-__YAMAMOTO, Taku  [EMAIL PROTECTED]
 | __ 
--- sys/netinet/tcp_hostcache.c.origSat Nov 29 01:33:03 2003
+++ sys/netinet/tcp_hostcache.c Tue Dec  2 10:17:57 2003
@@ -377,7 +377,7 @@
 */
bzero(hc_entry, sizeof(*hc_entry));
if (inc-inc_isipv6)
-   bcopy(hc_entry-ip6, inc-inc6_faddr, sizeof(hc_entry-ip6));
+   bcopy(inc-inc6_faddr, hc_entry-ip6, sizeof(hc_entry-ip6));
else
hc_entry-ip4 = inc-inc_faddr;
hc_entry-rmx_head = hc_head;
@@ -474,7 +474,7 @@
hc_entry-rmx_hits++;
hc_entry-rmx_expire = tcp_hostcache.expire; /* start over again */
 
-   bcopy(tao, hc_entry-rmx_tao, sizeof(*tao));
+   bcopy(hc_entry-rmx_tao, tao, sizeof(*tao));
THC_UNLOCK(hc_entry-rmx_head-hch_mtx);
 }
 

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

Re: [Fwd: re: ath0 lost connection]

[Marcos Biscaysaqu]

Marcos Biscaysaqu wrote:

Hi Eric.
   I have no loss connection  on 11b only on 11g, so for the moment im 
keep working with a Athreos Wireless card on hostap in 11b connecting 
34 clients, and really is working VERY well until I have lot of Ierrs 
and Oerrs and the ping to the client go from 2 ms to 1000 ms and all 
work very slow until the errors go down and is fast again.
I tried different AP and different wireless card and the Atheros 
wireless card even in 11b is faster than any comecial 11b AP,  fixing 
the errors problem will be a very fast and strong AP.
I wish to know fix it, but Im don't know how, Im only can help 
testing.  :(

thanks

Eric Anderson wrote:

Marcos Biscaysaqu wrote:

On a simpler yet related config, I have a linksys ag520 pci card 
running with a linksys a/b/g AP. IT occasionally just loses 
connectivity, but simply re-execing the ifconfig line brings it 
back. Haven't found a rhyme or reason yet.

I'd send this to the FBSD list, but I just moved server IP blocks 
and the reverse DNS stuff hasn't propagated yet.


I'm having the same problem - Sam knows about it (I've been annoying 
him for about a week and a half with info - sorry Sam!)..  I think he 
may be working on it, but he may want more details from you.
One question - does it drop when in A, B, and G modes?  Or just one 
mode?  It seemed to me that my connection was better when using 11b 
mode (to a B/G ap).  Just curious.

Also - is shared mode authentication ever going to work in 
FreeBSD?  Does anyone know what the problem with it is?

Eric




--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: [Fwd: re: ath0 lost connection]

[Eric Anderson]

Marcos Biscaysaqu wrote:

Hi Eric.
   I have no loss connection  on 11b only on 11g, so for the moment im 
keep working with a Athreos Wireless card on hostap in 11b connecting 
34 clients, and really is working VERY well until I have lot of Ierrs 
and Oerrs and the ping to the client go from 2 ms to 1000 ms and all 
work very slow until the errors go down and is fast again.
I tried different AP and different wireless card and the Atheros 
wireless card even in 11b is faster than any comecial 11b AP,  fixing 
the errors problem will be a very fast and strong AP.
I wish to know fix it, but Im don't know how, Im only can help 
testing.  :( 
Hmm - I wonder if you are losing packets when the device thinks the 
signal is weak, and it attempts to lower the connection speed to 
increase reliability.  Maybe try forcing it down to a low speed (like 
1mb/s or something?) and seeing if it continues to happen..

Maybe also try setting:
sysctl hw.ath.debug=1
and watch your dmesg/messages for hints..
Eric

Eric Anderson wrote:

Marcos Biscaysaqu wrote:

On a simpler yet related config, I have a linksys ag520 pci card 
running with a linksys a/b/g AP. IT occasionally just loses 
connectivity, but simply re-execing the ifconfig line brings it 
back. Haven't found a rhyme or reason yet.

I'd send this to the FBSD list, but I just moved server IP blocks 
and the reverse DNS stuff hasn't propagated yet.


I'm having the same problem - Sam knows about it (I've been annoying 
him for about a week and a half with info - sorry Sam!)..  I think he 
may be working on it, but he may want more details from you.
One question - does it drop when in A, B, and G modes?  Or just one 
mode?  It seemed to me that my connection was better when using 11b 
mode (to a B/G ap).  Just curious.

Also - is shared mode authentication ever going to work in 
FreeBSD?  Does anyone know what the problem with it is?

Eric

--
--
Eric Anderson  Systems Administrator  Centaur Technology
All generalizations are false, including this one.
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: [Fwd: re: ath0 lost connection]

[Marcos Biscaysaqu]

Hi there
   This may help:
Im turn the debug on Im I recive lot of this:
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure


Eric Anderson wrote:

Marcos Biscaysaqu wrote:

Hi Eric.
   I have no loss connection  on 11b only on 11g, so for the moment 
im keep working with a Athreos Wireless card on hostap in 11b 
connecting 34 clients, and really is working VERY well until I have 
lot of Ierrs and Oerrs and the ping to the client go from 2 ms to 
1000 ms and all work very slow until the errors go down and is fast 
again.
I tried different AP and different wireless card and the Atheros 
wireless card even in 11b is faster than any comecial 11b AP,  fixing 
the errors problem will be a very fast and strong AP.
I wish to know fix it, but Im don't know how, Im only can help 
testing.  :( 


Hmm - I wonder if you are losing packets when the device thinks the 
signal is weak, and it attempts to lower the connection speed to 
increase reliability.  Maybe try forcing it down to a low speed (like 
1mb/s or something?) and seeing if it continues to happen..

Maybe also try setting:
sysctl hw.ath.debug=1
and watch your dmesg/messages for hints..
Eric

Eric Anderson wrote:

Marcos Biscaysaqu wrote:

On a simpler yet related config, I have a linksys ag520 pci card 
running with a linksys a/b/g AP. IT occasionally just loses 
connectivity, but simply re-execing the ifconfig line brings it 
back. Haven't found a rhyme or reason yet.

I'd send this to the FBSD list, but I just moved server IP blocks 
and the reverse DNS stuff hasn't propagated yet.




I'm having the same problem - Sam knows about it (I've been annoying 
him for about a week and a half with info - sorry Sam!)..  I think 
he may be working on it, but he may want more details from you.
One question - does it drop when in A, B, and G modes?  Or just one 
mode?  It seemed to me that my connection was better when using 11b 
mode (to a B/G ap).  Just curious.

Also - is shared mode authentication ever going to work in 
FreeBSD?  Does anyone know what the problem with it is?

Eric



--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: [Fwd: re: ath0 lost connection]

[Marcos Biscaysaqu]

Also I have

in dmsg:
ath_calibrate: channel 2437/e0
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_calibrate: channel 2437/e0
ath_rate_ctl: 1M - 2M (14 ok, 0 err, 0 retr)
Eric Anderson wrote:

Marcos Biscaysaqu wrote:

Hi Eric.
   I have no loss connection  on 11b only on 11g, so for the moment 
im keep working with a Athreos Wireless card on hostap in 11b 
connecting 34 clients, and really is working VERY well until I have 
lot of Ierrs and Oerrs and the ping to the client go from 2 ms to 
1000 ms and all work very slow until the errors go down and is fast 
again.
I tried different AP and different wireless card and the Atheros 
wireless card even in 11b is faster than any comecial 11b AP,  fixing 
the errors problem will be a very fast and strong AP.
I wish to know fix it, but Im don't know how, Im only can help 
testing.  :( 


Hmm - I wonder if you are losing packets when the device thinks the 
signal is weak, and it attempts to lower the connection speed to 
increase reliability.  Maybe try forcing it down to a low speed (like 
1mb/s or something?) and seeing if it continues to happen..

Maybe also try setting:
sysctl hw.ath.debug=1
and watch your dmesg/messages for hints..
Eric

Eric Anderson wrote:

Marcos Biscaysaqu wrote:

On a simpler yet related config, I have a linksys ag520 pci card 
running with a linksys a/b/g AP. IT occasionally just loses 
connectivity, but simply re-execing the ifconfig line brings it 
back. Haven't found a rhyme or reason yet.

I'd send this to the FBSD list, but I just moved server IP blocks 
and the reverse DNS stuff hasn't propagated yet.




I'm having the same problem - Sam knows about it (I've been annoying 
him for about a week and a half with info - sorry Sam!)..  I think 
he may be working on it, but he may want more details from you.
One question - does it drop when in A, B, and G modes?  Or just one 
mode?  It seemed to me that my connection was better when using 11b 
mode (to a B/G ap).  Just curious.

Also - is shared mode authentication ever going to work in 
FreeBSD?  Does anyone know what the problem with it is?

Eric



--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: [Fwd: re: ath0 lost connection]

[Marcos Biscaysaqu]

After this I loss the connection and I have to restart the box:
this is getting worse :(
ath_start: encapsulation failure
ath_rate_ctl: 5M - 2M (0 ok, 1 err, 1 retr)
ath_beacon_proc: beacon queue 9 did not stop?ath_beacon_proc: beacon 
queue 9 did not stop?ath_beacon_proc: beacon queue 9 did not 
stop?ath_start: encapsulation failure
ath_start: encapsulation failure
ath_calibrate: channel 2437/e0
ath_start: encapsulation failure
ath_rate_ctl: 5M - 11M (10 ok, 0 err, 0 retr)
ath_beacon_proc: beacon queue 9 did not stop?ath_beacon_proc: beacon 
queue 9 did not stop?ath_beacon_proc: beacon queue 9 did not 
stop?ath_beacon_proc: beacon queue 9 did not stop?ath_beacon_proc: 
beacon queue 9 did not stop?ath_beacon_proc: beacon queue 9 did not 
stop?ath_beacon_proc: beacon queue 9 did not stop?ath_start: 
encapsulation failure
ath_beacon_proc: beacon queue 9 did not stop?ath_start: encapsulation 
failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_rate_ctl: 2M - 1M (0 ok, 1 err, 1 retr)
ath_start: encapsulation failure
ath_start: encapsulation failure

Eric Anderson wrote:

Marcos Biscaysaqu wrote:

Hi Eric.
   I have no loss connection  on 11b only on 11g, so for the moment 
im keep working with a Athreos Wireless card on hostap in 11b 
connecting 34 clients, and really is working VERY well until I have 
lot of Ierrs and Oerrs and the ping to the client go from 2 ms to 
1000 ms and all work very slow until the errors go down and is fast 
again.
I tried different AP and different wireless card and the Atheros 
wireless card even in 11b is faster than any comecial 11b AP,  fixing 
the errors problem will be a very fast and strong AP.
I wish to know fix it, but Im don't know how, Im only can help 
testing.  :( 


Hmm - I wonder if you are losing packets when the device thinks the 
signal is weak, and it attempts to lower the connection speed to 
increase reliability.  Maybe try forcing it down to a low speed (like 
1mb/s or something?) and seeing if it continues to happen..

Maybe also try setting:
sysctl hw.ath.debug=1
and watch your dmesg/messages for hints..
Eric

Eric Anderson wrote:

Marcos Biscaysaqu wrote:

On a simpler yet related config, I have a linksys ag520 pci card 
running with a linksys a/b/g AP. IT occasionally just loses 
connectivity, but simply re-execing the ifconfig line brings it 
back. Haven't found a rhyme or reason yet.

I'd send this to the FBSD list, but I just moved server IP blocks 
and the reverse DNS stuff hasn't propagated yet.




I'm having the same problem - Sam knows about it (I've been annoying 
him for about a week and a half with info - sorry Sam!)..  I think 
he may be working on it, but he may want more details from you.
One question - does it drop when in A, B, and G modes?  Or just one 
mode?  It seemed to me that my connection was better when using 11b 
mode (to a B/G ap).  Just curious.

Also - is shared mode authentication ever going to work in 
FreeBSD?  Does anyone know what the problem with it is?

Eric



--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: [Fwd: re: ath0 lost connection]

[Eric Anderson]

Marcos Biscaysaqu wrote:

After this I loss the connection and I have to restart the box:
this is getting worse :( 
I haven't seen the debug mode kill my box, but anything can happen on 
-current :)

ath_start: encapsulation failure
ath_rate_ctl: 5M - 2M (0 ok, 1 err, 1 retr) 
These ^^ are what I am talking about - I think when 
the signal is low or the connection is lossy (dropping packets or 
something) it auto drops the rate to a lower number (as it should) - and 
this is when you are  seeing the delays, dropped packets, whatever.  If 
you set the rate to a static number (say, 2M), then possibly it won't 
attempt any changes, and you can at least know what is causing the 
packet loss.

[..snip..]

ath_rate_ctl: 5M - 11M (10 ok, 0 err, 0 retr) 
Now the signal got better, so it bumped it up to 11M..

ath_start: encapsulation failure 
I have no idea what that is trying to tell you .. (besides the obvious)

ath_rate_ctl: 2M - 1M (0 ok, 1 err, 1 retr) 
If you are down to 1M, I think you may need to check signal strength and 
such.  I'd start with my testing near the AP (in sight of it at least). 

Eric

--
--
Eric Anderson  Systems Administrator  Centaur Technology
All generalizations are false, including this one.
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: [Fwd: re: ath0 lost connection]

[Eric Anderson]

Eric Anderson wrote:

[..snip..]

ath_rate_ctl: 2M - 1M (0 ok, 1 err, 1 retr) 


If you are down to 1M, I think you may need to check signal strength 
and such.  I'd start with my testing near the AP (in sight of it at 
least). 


Ok - I don't usually talk to myself (not in public anyway) - but here 
are my findings.  When in 11b mode, everything works fine (I didn't try 
going to the edge of my coverage area though - too comfortable on my 
couch).  When in 11g mode, I see the rate flap up and down between 48M 
and 24M, and each time it switches, it loses some packets in between 
modes.   I just now manually set my client (FreeBSD of course) to 36M, 
and it seems to be holding up for now.  Here's all I did:

ifconfig ath0 media OFDM/36Mbps mode 11g

Give that a try on the FreeBSD AP, and see if that helps at all (you may 
want to try the 11b modes, like:
ifconfig ath0 media DS/2Mbps mode 11b
or something..

Eric



--
--
Eric Anderson  Systems Administrator  Centaur Technology
All generalizations are false, including this one.
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: NSS and PAM

[Brandon S. Allbery KF8NH]

On Mon, 2003-12-01 at 21:24, Tim Kientzle wrote:
 Why is the directory usually the worst for storing
 authentication information?

This one's fairly easy to answer:  you want to stick authentication data
into a potentially public/exposed directory?  Even traditional Unix uses
/etc/shadow (or more complex solutions on some commercial systems) these
days, so the password isn't in the directory (/etc/passwd).

However, I have to agree with des's argument:  a combined matrix for
directory and authentication services doesn't mean the *data* must be
combined.  Using (for example) SIA, one could specify Kerberos 5 (my
guess as to wollman's better answer) and LDAP, and simply not specify
entry points for the parts that each doesn't handle (Kerberos doesn't
support directory services, and LDAP isn't being used for
authentication), with later entries falling back to NIS or traditional
files.  But this arrangement allows traditional APIs to work reasonably
--- and you can layer PAM and NSS on top of it as compatibility APIs.

-- 
brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED]
system administrator  [WAY too many hats][EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon univ. KF8NH

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

ATAPI CD still not detected, verbose boot logs available

[Christoph Sold]

Hi All,

FreeBSD 5.2-B still does not detect my ATAPI DVD-ROM drive. This used to 
work until Søren's ATAng commits. Other OSes (Win, Linux, Solaris) 
detect the drive appropriately.

# uname -a
FreeBSD kiste.local 5.2-BETA FreeBSD 5.2-BETA #14: Sun Nov 30 18:51:31 
CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
# atacontrol list
ATA channel 0:
Master:  ad0 ST340823A/3.39 ATA/ATAPI rev 4
Slave:   no device present
ATA channel 1:
Master:  ad2 SAMSUNG SP1203N/TL100-23 ATA/ATAPI rev 7
Slave:  acd0 SONY CD-RW CRX140E/1.0s ATA/ATAPI rev 0

should read (sometimes the drive _is_ detected):

# atacontrol list
ATA channel 0:
Master:  ad0 ST340823A/3.39 ATA/ATAPI rev 4
Slave:  acd0 _NEC DVD_RW ND-1300A/1.07 ATA/ATAPI rev 0
ATA channel 1:
Master:  ad2 SAMSUNG SP1203N/TL100-23 ATA/ATAPI rev 7
Slave:  acd1 SONY CD-RW CRX140E/1.0s ATA/ATAPI rev 0

Verbose boot logs, both with and without detecting the DVD burner on 
ATA-0 slave, are available at

   http://cheasy.dyndns.org/bootlogs/

Remote access to the box may be possible for debugging purposes. Other 
help may be available on request.

Thanks for all the good work so far.
Christoph Sold

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

Re: [Fwd: re: ath0 lost connection]

[Marcos Biscaysaqu]

Hi There
Fixing the speed on DS/11Mbps corrected one of the debug errors 
(ath_rate_ctl: 2M - 1M (0 ok, 1 err, 1 retr)) but I still with this 2 :
I think this error (ath_start: encapsulation failure) its cousing Ierrs 
and the Oerrs on the netstat, becouse is doing it all the time same with 
the  Ierrs and Oerrs

ath_calibrate: channel 2437/e0
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
ath_start: encapsulation failure
thnaks
Eric Anderson wrote:
Eric Anderson wrote:

[..snip..]

ath_rate_ctl: 2M - 1M (0 ok, 1 err, 1 retr) 


If you are down to 1M, I think you may need to check signal strength 
and such.  I'd start with my testing near the AP (in sight of it at 
least). 


Ok - I don't usually talk to myself (not in public anyway) - but here 
are my findings.  When in 11b mode, everything works fine (I didn't 
try going to the edge of my coverage area though - too comfortable on 
my couch).  When in 11g mode, I see the rate flap up and down between 
48M and 24M, and each time it switches, it loses some packets in 
between modes.   I just now manually set my client (FreeBSD of course) 
to 36M, and it seems to be holding up for now.  Here's all I did:

ifconfig ath0 media OFDM/36Mbps mode 11g

Give that a try on the FreeBSD AP, and see if that helps at all (you 
may want to try the 11b modes, like:
ifconfig ath0 media DS/2Mbps mode 11b
or something..

Eric



--

Marcos Biscaysaqu

Systems Administrator
ThePacific.Net Ltd.


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

Re: 40% slowdown with dynamic /bin/sh

[Jonathan Mini]

I have found that the cost of printing the spew often
slows down compiles measurably, especially when spewing
to an xterm running on a local XFree86 process.  Even
with syscons, this is noticeable.
I generally tend to run my builds behind the screen
port these days, which  helps (screen implements a
virtual display buffer that disconnects screen updates
from the display client and the slave pty).  Another
optimization worth noting is running make -q, which
silences a lot of that spam (urban legend has it that
the synchronization in parallel makes to write the build
messages causes noticeable amounts of contention).
On Nov 29, 2003, at 3:22 PM, Garance A Drosihn wrote:

I also had some benchmarks of doing 'buildworld' over an
ssh connection vs doing it at the console.  Oddly enough,
the ssh connection was faster in some ways and slower in
others.  I wonder if there is a speed-up by writing to a
file instead of the console?
--
Jonathan Mini
[EMAIL PROTECTED]
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: 40% slowdown with dynamic /bin/sh

[Scott Long]

Jonathan Mini wrote:
I have found that the cost of printing the spew often
slows down compiles measurably, especially when spewing
to an xterm running on a local XFree86 process.  Even
with syscons, this is noticeable.
I generally tend to run my builds behind the screen
port these days, which  helps (screen implements a
virtual display buffer that disconnects screen updates
from the display client and the slave pty).  Another
optimization worth noting is running make -q, which
silences a lot of that spam (urban legend has it that
the synchronization in parallel makes to write the build
messages causes noticeable amounts of contention).
I regularly use -s.  With the pipe code being completely
Giant-free, I don't see a significant performance difference
anymore on an SMP machine when the output is not supressed.
Scott

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

Re: 40% slowdown with dynamic /bin/sh

[Jonathan Mini]

On Dec 1, 2003, at 10:15 PM, Scott Long wrote:

Jonathan Mini wrote:
I have found that the cost of printing the spew often
slows down compiles measurably, especially when spewing
to an xterm running on a local XFree86 process.  Even
with syscons, this is noticeable.
I generally tend to run my builds behind the screen
port these days, which  helps (screen implements a
virtual display buffer that disconnects screen updates
from the display client and the slave pty).  Another
optimization worth noting is running make -q, which
silences a lot of that spam (urban legend has it that
the synchronization in parallel makes to write the build
messages causes noticeable amounts of contention).
I regularly use -s.  With the pipe code being completely
Giant-free, I don't see a significant performance difference
anymore on an SMP machine when the output is not supressed.
Ah, I meant -s.  And, that is good news.  I am still running
on a 4.x system most of the time, and (sigh) Linux 2.4.x the
rest of the time.
--
Jonathan Mini
[EMAIL PROTECTED]
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: -current lockup (how to diagnose?)

[Jun Kuriyama]

At Mon, 1 Dec 2003 09:23:21 -0500 (EST),
Robert Watson wrote:
 This could be a sign of a VM or VFS lock leak or deadlock.  I'd advise
 hooking up a serial console, dropping to DDB over serial line, and posting
 the results of ps and show lockedvnods.  We might then ask you to use
 the show locks command on various processes.  You'll need to have DDB
 and WITNESS compiled in.

I got it.

http://www.imgsrc.co.jp/~kuriyama/BSD/lock-20031202.log


-- 
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: -current lockup (how to diagnose?)

[Robert Watson]

On Tue, 2 Dec 2003, Jun Kuriyama wrote:

 At Mon, 1 Dec 2003 09:23:21 -0500 (EST),
 Robert Watson wrote:
  This could be a sign of a VM or VFS lock leak or deadlock.  I'd advise
  hooking up a serial console, dropping to DDB over serial line, and posting
  the results of ps and show lockedvnods.  We might then ask you to use
  the show locks command on various processes.  You'll need to have DDB
  and WITNESS compiled in.
 
 I got it.
 
 http://www.imgsrc.co.jp/~kuriyama/BSD/lock-20031202.log

ouch

Could you try compiling in DEBUG_LOCKS into your kernel and doing show
lockedvnods with that?  Unfortunately, someone removed the pid from the
output of that command, but didn't add the thread pointer to the DDB ps
output, so you'll probably need to modify the lockmgr_printinfo() function
in vfs_subr.c to print out lkp-lk_lockholder-td_proc-p_pid as well for
exclusive locks.  It looks like maybe something isn't releasing a vnode
lock before returning to userspace.  I have some patches to assert that no
lockmgr locks are held on the return to userspace, but I'll have to dig
them up tomorrow and send them to you.  Basically, it adds a per-thread
lockmgr lock count in a thread-local variable, incrementing for each lock,
and decrementing for each release, and then KASSERT()'s in userret that
the variable is 0.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Senior Research Scientist, McAfee Research

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

Re: named (bind) in jail does not start

[Axel S. Gruner]

On Sat, 29 Nov 2003 15:39:50 +
Matthew Seaman [EMAIL PROTECTED] wrote something
special:

 On Sat, Nov 29, 2003 at 03:23:48PM +0100, Axel S. Gruner wrote:
  /usr/sbin/named
  
  i get this error message:

  opensocket_f: bind([0.0.0.0].53): Address already in use
  
  Ok, Port 53 is not in use in the jail nor the hostsystem.
  I think the problem is 0.0.0.0, and i have to bind named on the IP
  of the jail. 
  
  I tested same named configuration on the hostsystem, i thought about
  some misconfigration, but on the hostsystem named starts perfectly.
  
  I also tried to start named with -g and -u in the jail, same error.
  
  So, my short question is, how can i run named in the jail?
  Any ideas?
 
 [...]
 In bind9 you need to add something like the following to named.conf --
 bind8 will be similar:
 
 options {
 
 [...]
 
 listen-on {
 192.168.1.1;
 };
 query-source address 192.168.1.1 port 53;
 transfer-source  192.168.1.1 port 53;
 notify-source192.168.1.1 port 53;
 };

Yes. Thats it. Thanks a lot. 


-- 
asg

Die Antwort auf alle Fragen ist 42.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]