Re: wierdness with mountd

[John]

- Ian Dowse's Original Message -
> In message <[EMAIL PROTECTED]>, John Polstra writes:
> >In article <[EMAIL PROTECTED]>,
> >Matthew Jacob  <[EMAIL PROTECTED]> wrote:
> >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /tmp
> >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /usr/obj
> >
> >I've been seeing this too, on a -current system from around May 5.
> 
> This sounds like there are stale entries in /var/db/mountdtab, but
> I'm not familiour enough with the purpose of mountdtab to know why
> this is happening. I'll look into this further over the next few
> days; for now maybe try cleaning out mountdtab manually?
> 
> Ian

Hi,

   Some info...  I've looked into a bit previously.. I have no mountdtab file:

%find /var -name 'mount*'
/var/db/mounttab
/var/log/mount.today
/var/log/mount.yesterday
/var/run/mountd.lock
/var/run/mountd.pid

   What I have mounted, though it is not a part of this issue..

%cat /var/db/mounttab
990745123   snapserv/pub
990745123   snapserv/mirror/ncvs

and then reboot the system:

/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /usr
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /tmp
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /var
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for 
/usr/obj
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for 
/snap


Looking in /usr/src/sbin/mountd/mountd.c, under line 930
shows the following:

num = getmntinfo(&fsp, MNT_NOWAIT);

and then runs through a loop 'num' times trying to
delete any export for each entry. Maybe it should check
to see if there is an export before attempting to delete it
by using the MNT_EXPORTED request? Note: These MNT_xxx definitions
appear to be only partially documented in mount(2).

   If you kill and restart mountd the logic appears correct.
Bringing mountd up on a newly booted system appears to be the
oddball case.

   Hope this helps..

-john



 

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

Re: Unrecognised CBCP packet [strange problems with ppp(8)]

[Brian Somers]

I've had reports of this in the past.  The other end is sending a 
``code 5'' packet - something that doesn't appear in the spec :(

ppp(8) just ignores these (emitting a warning), they shouldn't be 
causing any problems themselves (even if CBCP is actually being used).

Try enabling IPCP logging.  You may be having a problem at that 
level, or alternatively, perhaps the peer thinks you've already got a 
connection and is (rudely) dropping the connection because of that.

> Hi,
> 
> I'm having strange problems with one of local dial-up providers: without
> any visible reasons from time to time I can't establish PPP connection
> during 20-30 minutes. Shortly after going into `Network' mode ppp(8)
> complains about `Unrecognised CBCP packet' and drops down line.
> Restarting ppp/machine/modem etc. doesn't help and provider's technical
> people have no idea what could be wrong. Attached please find piece of
> log, please let me know if any additional information would be necessary.
> 
> -Maxim
> 
> Phase: bundle: Authenticate
> Phase: deflink: his = PAP, mine = none
> Phase: Pap Output: sobomax1 
> Ppp ON vega> Phase: Pap Input: SUCCESS ()
> Phase: deflink: lcp -> open
> Phase: bundle: Network
> PPp ON vega> Warning: Unrecognised CBCP packet (code 5, length 4)
> PPp ON vega> Phase: deflink: open -> lcp
> Phase: bundle: Terminate
> ppp ON vega> Phase: deflink: Carrier lost
> Phase: deflink: Disconnected!
> Phase: deflink: lcp -> logout
> Phase: deflink: Disconnected!
> Phase: deflink: logout -> hangup
> Phase: deflink: Connect time: 32 secs: 248 octets in, 235 octets out

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



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

Re: mount_mfs (Re: smbfs)

[Boris Popov]

On Fri, 25 May 2001, Brooks Davis wrote:

> On Fri, May 25, 2001 at 10:04:09PM +0700, Boris Popov wrote:
> > There is no any technical problems in doing that. But I'm unsure
> > if this should be done (code is not very small). On other hand, people
> > expect it in the base system... Probably we should collect more votes on
> > this topic.
> 
> I'll definatly vote for inclusion.  IMO, it makes no sense to have a
> filesystem in the base you can't mount.  If it really is so hugh that
> people complain, there's always the ugly NO_MOUNT_SMBFS make.conf option
> route.  Those who really need small systems have to strip all sorts of
> things out already anyway, one more won't hurt.

Ok, now I've received about fifty votes for inclusion of userland
part in the base tree and zero objections. Import process will be done in
the -current first and then MFCed to -stable.

--
Boris Popov
http://www.butya.kz/~bp/


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

Re: wierdness with mountd

[Ian Dowse]

In message <[EMAIL PROTECTED]>, John writes:

>Looking in /usr/src/sbin/mountd/mountd.c, under line 930
>shows the following:
>
>num = getmntinfo(&fsp, MNT_NOWAIT);
>
>and then runs through a loop 'num' times trying to
>delete any export for each entry.

Thanks, you're right - this has nothing to do with mountdtab or
mounttab. The commit that caused these messages to appear is
phk's centralisation of the kernel netexport structure:

REV:1.149   ffs_vfsops.c2001/04/25 07:07:50   phk

   Move the netexport structure from the fs-specific mountstructure
   to struct mount.
   ...

Doing a MNT_DELEXPORT mount used to be a no-op if there were no
exports, but now it returns EINVAL. Maybe that should be changed
to ENOENT or something, so that mountd can detect it as a 'normal'
error? (untested patch below). 

Ian


Index: sys/kern/vfs_export.c
===
RCS file: /dump/FreeBSD-CVS/src/sys/kern/vfs_export.c,v
retrieving revision 1.310
diff -u -r1.310 vfs_export.c
--- sys/kern/vfs_export.c   2001/04/26 20:47:14 1.310
+++ sys/kern/vfs_export.c   2001/05/29 09:28:43
@@ -207,7 +207,7 @@
nep = mp->mnt_export;
if (argp->ex_flags & MNT_DELEXPORT) {
if (nep == NULL)
-   return (EINVAL);
+   return (ENOENT);
if (mp->mnt_flag & MNT_EXPUBLIC) {
vfs_setpublicfs(NULL, NULL, NULL);
mp->mnt_flag &= ~MNT_EXPUBLIC;
Index: sbin/mountd/mountd.c
===
RCS file: /dump/FreeBSD-CVS/src/sbin/mountd/mountd.c,v
retrieving revision 1.51
diff -u -r1.51 mountd.c
--- sbin/mountd/mountd.c2001/05/25 08:14:02 1.51
+++ sbin/mountd/mountd.c2001/05/29 09:31:43
@@ -903,6 +903,7 @@
struct xucred anon;
char *cp, *endcp, *dirp, *hst, *usr, *dom, savedc;
int len, has_host, exflags, got_nondir, dirplen, num, i, netgrp;
+   int error;
 
dirp = NULL;
dirplen = 0;
@@ -949,10 +950,11 @@
!strcmp(fsp->f_fstypename, "cd9660")) {
targs.ua.fspec = NULL;
targs.ua.export.ex_flags = MNT_DELEXPORT;
-   if (mount(fsp->f_fstypename, fsp->f_mntonname,
- fsp->f_flags | MNT_UPDATE,
- (caddr_t)&targs) < 0)
-   syslog(LOG_ERR, "can't delete exports for %s",
+   error = mount(fsp->f_fstypename, fsp->f_mntonname,
+   fsp->f_flags | MNT_UPDATE, (caddr_t)&targs);
+   if (error && error != ENOENT)
+   syslog(LOG_ERR,
+   "can't delete exports for %s: %m",
fsp->f_mntonname);
}
fsp++;

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

Re: softupdates related problem in -current

[Brian Somers]

> On Sun, May 27, 2001 at 10:18:43PM -0700, Doug Barton wrote:
> > Another problem I'm having in -current right now is with softupdates. Wh=
> en
> > the system panic'ed the first time, it came up ok and fsck'ed fine with no
> > apparent loss of data. However, during the fsck it complained bitterly
> > about my superblocks, and when it was done and the system booted, the
> > softupdates attribute was missing from the filesystems that had it set.=
> =20
> 
> Yep, I've seen this too.

I think this is related to the bogus ``corrupt first superblock'' 
message that forces a manual fsck (-b32 doesn't work, -Tufs:-b32 is 
required) two times out of three.
-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



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

Re: 'make includes' ownership patch

[Bruce Evans]

On Mon, 28 May 2001, Kris Kennaway wrote:

> On Mon, May 28, 2001 at 10:31:58AM -0700, Rodney W. Grimes wrote:
> > > [Someone wrote]
> > > What was the reasoning for a serperate owner specification from BIN*?
> > 
> > Simple orthagonality.  Ie, each bsd.*.mk file typically has a seperate
> > set of *{DIR/OWN/GRP/MODE} specs.  bsd.inc.mk was cloned from another
> > bsd.*.mk file.
> 
> Well, I don't mind how it gets fixed, but it's very unorthogonal at
> the moment having to set two sets of OWN/GRP variables in order to
> make includes as non-root.

This shouldn't be a problem, because "includes" is an undocumented private
target in src/Makefile.inc1.  Running it independently of buildworld
is usually wrong.  You would have to set the two sets to run buildworld.
You would also have to set the other set that doesn't default to the BIN
set, i.e., the SHARE set.  To set all the sets to different values, you
would also have to set the following sets:

KMOD, LIB (these mostly default to the BIN set)
DOC, INFO, MAN, NLS (these mostly default to the SHARE set)

There is a little too much orthogonality here.

Bruce


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

Re: cvs commit: src UPDATING

[Warner Losh]

In message  Michael Reifenberger writes:
: Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using
: whine?

Nope.

Warner

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

Re: cvs commit: src UPDATING

[Brian Somers]

> In message  Michael Reifenberger 
>writes:
> : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using
> : whine?
> 
> Nope.

vmware does the job too, and I believe star-office.

> Warner

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



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

Re: wierdness with mountd

[Thomas Quinot]

Le 2001-05-28, Matthew Jacob écrivait :

> On startup:
> May 28 10:16:04 farrago mountd[216]: can't delete exports for /

Same here with -CURRENT as of today.

-- 
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
  ENST   //   46 rue Barrault   //   75634 PARIS CEDEX 13 

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

rpc.lockd: kernel trap 12 with interrupts disabled

[Thomas Quinot]

In the hope to check for any recent improvements with lockd,
I cvsupped this morning and remade world. I now have a very
strange behaviour of lockd:
  * rc.conf has nfs_server_enable, rpc_lockd_enable and rpc_statd_enable
set to YES.
  * the system seems to boot correclty; rpc.lockd and rpc.statd are
mentioned in the 'Starting final network daemons' phase.

BUT:
  * ps ax shows no trace of rpc.lockd
  * an attempt to manually launch rpc.lockd immediately results in
a hard freeze with message 'Kernel trap 12 with interrupts
disabled (repeated twice).
  * launching rpc.lockd with truss shows that the crash occurs (shortly)
after it has forked.

Thomas.

-- 
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
  ENST   //   46 rue Barrault   //   75634 PARIS CEDEX 13 

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

Re: Supported ATAPI cdr/cdrw drives

[Ken Wills]

* Søren Schmidt <[EMAIL PROTECTED]> [010528 09:01]:
> 
> As promised I've made up a list of reports I've received so far go to
> http://freebsd.dk/ and follow the link.
> 
> I also have a patch for the Yamaha's (yamaha-cdr.p1) which also
> can be found via the above URL. Let me know if that make things
> work...

This patch (well, yamaha-cdr.p2), allows my Yamaha 2100E to fixate disks now!
Thanks Soren and others!

Ken

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

Re: cvs commit: src UPDATING

[Brian F. Feldman]

Brian Somers <[EMAIL PROTECTED]> wrote:
> > In message  Michael Reifenberger 
>writes:
> > : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using
> > : whine?
> > 
> > Nope.
> 
> vmware does the job too, and I believe star-office.

I've noticed it, and after backing out locally the commits recently made to 
"lock" LDT access, things work (at least, as well as they used to).  I 
didn't do this hastily;  I spent hours looking at what could possibly be 
wrong with the new locking added, and couldn't find anything :(  I know that 
sched_lock is being held too long, which means (I think) that either somehow 
the code is sleeping with it held or just not releasing it at all.


-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'



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

Re: -current is _definitely_ not stable right now

[John Baldwin]

On 28-May-01 Doug Barton wrote:
> I forgot something:
> 
> IdlePTD 4734976
> initial pcb at 3b5f80
> panicstr: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858
> panic messages:

I would need a traceback from here.  It looks like someone called msleep or
tsleep with sched lock held.

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

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

RE: vm_pager_(de)allocate and vm_mtx

[John Baldwin]

On 26-May-01 Dima Dorfman wrote:
> Is there a reason vm_pager_allocate acquires vm_mtx itself if
> necessary but vm_pager_deallocate does not?  At the moment, detaching
> an md(4) disk will panic the system with a failed mtx_assert in
> vm_pager_deallocate.  This can be fixed one of two ways:
> vm_pager_deallocate could be made to deal with vm_mtx itself like
> vm_pager_allocate does, or md(4) and any other drivers which call
> vm_pager_deallocate can be fixed to acquire vm_mtx.  So which will it
> be?  I'll supply patches for either case.
> 
> Thanks,

I think I have it the same in the patches on my laptop, but I've not finished
those yet, so they aren't safe to be committed but are still a WIP.  I would
grab the lock around vm_pager_deallocate() for now.

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

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

RE: Panic: spin lock shed lock hold by ... for >5 seconds

[John Baldwin]

On 26-May-01 Michael Reifenberger wrote:
> Hi,
> I get the above panic when just running aviplay (/usr/ports/graphics/avifile)
> or wine.
> Since both programs use USER_LDT functions I suspect a problem there in the
> kernel.
> The kernel is the latest -current.
> I get no kernel-dump because the panic seems to loop (in conjunction with
> some
> lockmgr: panics...)
> But it's too easy to reproduce anyway...

I'll try and look at this in a bit.  I did make some changes to the LDT stuff
to use the sched_lock, it is quite possible I forgot to unlock it somewhere.

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

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

RE: Q) lock order reversal

[John Baldwin]

On 27-May-01 Takeshi Ken Yamada wrote:
>   Hi!
>   With recent -current kernel, I get message below with P3@800Mhz X 2
> when booting up.
> 
>   What is wrong?
> 
>   lock order reversal
> 1st 0xc04d4ac0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c  1007
> 2nd 0xdb3001ac vnode interlock @ ../../ufs/ffs/ffs_vfsops.c  1016

This is a FAQ.  These reversals have been around for a long time, we just
haven't had the tools to find them before.

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

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

Correctness of UIO_MAXIOV definition?

[Garrett Wollman]

< said:

>The second question I have is more standards based.
> Should we consider changing UIO_MAXIOV to IOV_MAX or
> _XOPEN_IOV_MAX and deprecating the 1st? I am unclear
> on what the standard is for this.

UIO_MAXIOV is what the kernel is willing to do.  IOV_MAX being
standardized is what should be used by user code.

-GAWollman


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

Re: make release failure

[Bruce A. Mah]

If memory serves me right, John Hay wrote:
> Yes, this patch fix it for me. I had to convert the spaces back to tabs
> though. :-)

Hi John--

I was trying to test out another patch, which (in addition to fixing 
the problem you found) also folds the functionality of NORELNOTES into 
NODOC.  Unfortunately, my -CURRENT test box is having some difficulties 
(probably VM-related) and it's going to take a little while before I 
can do a "make release" again to do any testing.  :-(

I'll see what I can do about getting my first patch committed to at 
least unbreak "make release".

Thanks for testing my patch, BTW!

Bruce.




 PGP signature

Re: wierdness with mountd

[Ian Dowse]

In message <[EMAIL PROTECTED]>, Ian Dowse writes:
>error? (untested patch below). 

I braino'd that patch (error vs. errno), but I have just committed
a working version that should stop the mountd warnings.

Ian

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

Re: wierdness with mountd

[Matthew Jacob]

Thanks, Ian!



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

Re: wierdness with mountd

[John]

Yes, with the error vs errno fix, I've got the patch up and running
on my system. It seems to be doing the trick.

Thanks,
-john

- Ian Dowse's Original Message -
> In message <[EMAIL PROTECTED]>, Ian Dowse writes:
> >error? (untested patch below). 
> 
> I braino'd that patch (error vs. errno), but I have just committed
> a working version that should stop the mountd warnings.
> 
> Ian

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

Re: rpc.lockd: kernel trap 12 with interrupts disabled

[Andrew Gallatin]

Thomas Quinot [[EMAIL PROTECTED]] wrote:
> In the hope to check for any recent improvements with lockd,
> I cvsupped this morning and remade world. I now have a very

Did you also rebuild your kernel?

In order for a bug report like this to be useful, you need to supply a
backtrace from ddb or gdb.  See the Kernel Debugging section of the
FreeBSD handbook for instructions on how to obtain such information.

-- 
--
Andrew Gallatin, Sr Systems Programmer  http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science  Phone: (919) 660-6590

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

HEADS UP, ACPI CA updated.

[Mike Smith]

The ACPI core code in -current has been updated to the 20010518 drop from 
Intel.  You can read more about APCI CA at

   http://developer.intel.com/technology/ial/acpi

This update doesn't add any new, visible functionality, but it should 
resolve a number of bugs and problems in the core interpreter.  Bringing 
ACPI CA up to date will let other developers work more actively on adding 
new functionality (like me, for example).

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E



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

Re: cvs commit: src/sbin/fsck_ffs setup.c

[Ian Dowse]

In message <[EMAIL PROTECTED]>, Ian Dowse writes:
>iedowse 2001/05/29 13:45:09 PDT
>
>  Modified files:
>sbin/fsck_ffssetup.c 
>  Log:
>  Ignore the new superblock fields fs_pendingblocks and fs_pendinginodes
>  when comparing with the alternate superblock. These fields are used
>  for temporary in-core information only. This should fix the "VALUES
>  IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE" error from
>  fsck_ffs that has been seen a lot recently.

Note that this will not fix the softupdates freelist corruption
problem that people have been reporting. It seems that Kirk is away
for at least another week, so if Tor's suggested fix for that works,
then it should probably be committed in the meantime.

Ian

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

MFS gone...

[Poul-Henning Kamp]

MFS is gone now except from the newfs(8) manpage.

If anybody better at mdoc than me would take on the surgical
task of censoring that page I would be most happy.

The command name "mount_mfs" is now available for use for other
purposes like a md(4) based facility, I'm not happy about "stealing"
a name from the mount_*(8) api for doing something which isn't
really that.

The opposite argument could be made successfully though, that by
stealing the name we allow people to write something sensible in
their /etc/fstab and then later when we get a _real_ memory
filesystem, they will not have to fiddle it again.

As usual I revert to the safety of "whoever writes the code make
decisions as well..."

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

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

Re: rpc.lockd: kernel trap 12 with interrupts disabled

[Thomas Quinot]

Le 2001-05-29, Andrew Gallatin écrivait :

> Did you also rebuild your kernel?

Yep, I did buildworld buildkenrnel installkernel installworld,
then mergemaster and reboot.

> In order for a bug report like this to be useful, you need to supply a
> backtrace from ddb or gdb.  See the Kernel Debugging section of the
> FreeBSD handbook for instructions on how to obtain such information.

Will try that, thanks.
Thomas.

-- 
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
  ENST   //   46 rue Barrault   //   75634 PARIS CEDEX 13 

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

Re: HEADS UP, ACPI CA updated.

[Mike Smith]

> 
> The ACPI core code in -current has been updated to the 20010518 drop from 
> Intel.  You can read more about APCI CA at
> 
>http://developer.intel.com/technology/ial/acpi

Sorry, that should be 

http://developer.intel.com/technology/iapc/acpi

Regards,
Mike
-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E



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

Re: -current is _definitely_ not stable right now

[Thomas Moestl]

On Tue, 2001/05/29 at 09:39:42 -0700, John Baldwin wrote:
> 
> On 28-May-01 Doug Barton wrote:
> > I forgot something:
> > 
> > IdlePTD 4734976
> > initial pcb at 3b5f80
> > panicstr: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858
> > panic messages:
> 
> I would need a traceback from here.  It looks like someone called msleep or
> tsleep with sched lock held.

OK, I think I've found the problem, patch attached. set_user_ldt is
called from cpu_switch on i386, where the sched lock is already held
by the process that is just being scheduled away, and curproc has
already been changed, so this isn't treated like a recursed mutex, but
rather like the new process (dead-) locking against the old one.

The solution taken in the attached patch create a
set_user_ldt_nolock. This way, we have a more or less consistent
enviroment (of the new process) there.
The (pcb != PCPU_GET(curpcb)) check is in the outer locking
set_user_ldt wrapper (it seems only to be needed in the smp rendezvous
case and is a "can't happen" when called from cpu_switch).

This works for me; Doug, could you please test it too? I'd be thankful
for any review.

- thomas


Index: i386/swtch.s
===
RCS file: /home/ncvs/src/sys/i386/i386/swtch.s,v
retrieving revision 1.114
diff -u -r1.114 swtch.s
--- i386/swtch.s2001/05/20 16:51:08 1.114
+++ i386/swtch.s2001/05/29 22:09:14
@@ -248,7 +248,7 @@
movl%eax,PCPU(CURRENTLDT)
jmp 2f
 1: pushl   %edx
-   callset_user_ldt
+   callset_user_ldt_nolock
popl%edx
 2:
 
Index: i386/sys_machdep.c
===
RCS file: /home/ncvs/src/sys/i386/i386/sys_machdep.c,v
retrieving revision 1.57
diff -u -r1.57 sys_machdep.c
--- i386/sys_machdep.c  2001/05/15 23:22:20 1.57
+++ i386/sys_machdep.c  2001/05/29 22:24:04
@@ -239,17 +239,16 @@
 
 /*
  * Update the GDT entry pointing to the LDT to point to the LDT of the
- * current process.
+ * current process. Assumes that sched_lock is held. This is needed
+ * in cpu_switch because sched_lock is held by the process that has
+ * just been scheduled away and we would deadlock if we would try to
+ * acquire sched_lock.
  */   
 void
-set_user_ldt(struct pcb *pcb)
+set_user_ldt_nolock(struct pcb *pcb)
 {
struct pcb_ldt *pcb_ldt;
 
-   if (pcb != PCPU_GET(curpcb))
-   return;
-
-   mtx_lock_spin(&sched_lock);
pcb_ldt = pcb->pcb_ldt;
 #ifdef SMP
gdt[PCPU_GET(cpuid) * NGDT + GUSERLDT_SEL].sd = pcb_ldt->ldt_sd;
@@ -258,6 +257,17 @@
 #endif
lldt(GSEL(GUSERLDT_SEL, SEL_KPL));
PCPU_SET(currentldt, GSEL(GUSERLDT_SEL, SEL_KPL));
+}
+
+/* Locking wrapper of the above */
+void
+set_user_ldt(struct pcb *pcb)
+{
+   if (pcb != PCPU_GET(curpcb))
+   return;
+
+   mtx_lock_spin(&sched_lock);
+   set_user_ldt_nolock(pcb);
mtx_unlock_spin(&sched_lock);
 }
 
Index: include/pcb_ext.h
===
RCS file: /home/ncvs/src/sys/i386/include/pcb_ext.h,v
retrieving revision 1.6
diff -u -r1.6 pcb_ext.h
--- include/pcb_ext.h   2001/05/10 17:03:03 1.6
+++ include/pcb_ext.h   2001/05/29 22:06:37
@@ -55,6 +55,7 @@
 
 int i386_extend_pcb __P((struct proc *));
 void set_user_ldt __P((struct pcb *));
+void set_user_ldt_nolock __P((struct pcb *));
 struct pcb_ldt *user_ldt_alloc __P((struct pcb *, int));
 void user_ldt_free __P((struct pcb *));
 

RE: -current is _definitely_ not stable right now

[John Baldwin]

On 28-May-01 Doug Barton wrote:
> Gang,
> 
>   On the avi front, typing 'aviplay' with or without an argument is
> guaranteed to instantly wedge the box. I attached a lot of running aviplay
> through truss, but I have no way to know if it stopped at or before the
> offending instruction. As for the general wonkiness of the system, I have
> finally gotten a dump. The backtrace is below, let me know if there is
> anything else I can do to help debug. 

Please try http://www.FreeBSD.org/~jhb/patches/ldt.patch.

> Doug

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

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

world broken at acpi

[walt]

===> usr.sbin/acpi
===> usr.sbin/acpi/acpiconf
rm -f .depend
mkdep -f .depend -a-I/usr/src/usr.sbin/acpi/acpiconf/../../../sys 
-I/usr/obj/usr/src/i386/usr/include  /usr/src/usr.sbin/acpi/acpiconf/acpiconf.c
/usr/src/usr.sbin/acpi/acpiconf/acpiconf.c:40: 
contrib/dev/acpica/Subsystem/Include/acgcc.h: No such file or directory
/usr/src/usr.sbin/acpi/acpiconf/acpiconf.c:41: 
contrib/dev/acpica/Subsystem/Include/actypes.h: No such file or directory
mkdep: compile failed

cvsup'd about 16.30 on 29 May 2001


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

Re: Correctness of UIO_MAXIOV definition?

[John W. De Boskey]

- Garrett Wollman's Original Message -
> < said:
> 
> >The second question I have is more standards based.
> > Should we consider changing UIO_MAXIOV to IOV_MAX or
> > _XOPEN_IOV_MAX and deprecating the 1st? I am unclear
> > on what the standard is for this.
> 
> UIO_MAXIOV is what the kernel is willing to do.  IOV_MAX being
> standardized is what should be used by user code.
> 
> -GAWollman

Hi,

   That seems reasonable, but I can only find UIO_MAXIOV referenced
in 5 files and defined in 1. Thus, I was thinking about simply
updating those references, but still leaving UIO_MAXIOV defined,
though depricated. 

   If the above is simply not the direction we want to go, then
I beleive that UIO_MAXIOV should atleast be defined in terms
of IOV_MAX in sys/uio.h:

#include  # bring in IOV_MAX
#ifdef _KERNEL
#define UIO_MAXIOV IOV_MAX
#endif


   Question: does anyone know the appropriate #define to use
 for IEEE Std. 1003.1-200x,  or should _SC_IOV_MAX
 simply be put behind the non-expansion controlled
  comment (in /usr/src/lib/libc/gen/sysconf.c) 

 switch (name) {
 /* 1003.1 */


   Comments?

Thanks,
-John

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

USB Ethernet hang on "eject"

[Warner Losh]

I'm getting a hang on eject of the USB Ethernet card that I have.

aue0: SMC, Inc EZ USB/Ethernet Converter, rev 1.10/1.01, addr 2
aue0: Ethernet address: 00:e0:29:59:fe:11
miibus0:  on aue0

When I remote the card, I get USB errors.  I also have an interrupt
storm from the USB controller.  I set a breakpoint on the interrupt
handler and get over and over again

Anything that I can do to help track down the problem here?

This is current as of May 18th, 12:00:00 MDT.

Warner

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

Re: HEADS UP, ACPI CA updated.

[nnd]

As a result 'make buildkernel' is broken in
'sys/dev/acpica/Osd'. The next patch permits me to finish
kernel building.

N.Dudorov


Index: sys/dev/acpica/Osd/OsdSchedule.c
===
RCS file: /scratch/CVS/src/sys/dev/acpica/Osd/OsdSchedule.c,v
retrieving revision 1.8
diff -b -u -r1.8 OsdSchedule.c
--- sys/dev/acpica/Osd/OsdSchedule.c2001/05/29 20:13:42 1.8
+++ sys/dev/acpica/Osd/OsdSchedule.c2001/05/30 04:29:39
@@ -37,6 +37,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #define _COMPONENT ACPI_OS_SERVICES
 MODULE_NAME("SCHEDULE")

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