Re: SMPNG kernel on UP
Warner Losh wrote:
In message [EMAIL PROTECTED] Garrett Wollman writes:
: On Thu, 14 Sep 2000 13:46:44 -0600, Warner Losh [EMAIL PROTECTED] said:
: Hmmm, they look good to me. Maybe Mark's system doesn't have group
: operator at gid 5. That's one bad thing about the new DEVFS: it
: appears to enshrine things like this in the kernel...
:
: It would only take a small amount of Makefile magic to fix
: this... something like:
:
: PASSWD?= /etc/passwd
: GROUP?= /etc/group
:
: uidgid.h: ${PASSWD} ${GROUP}
: perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
:$_[2], "\n");' ${PASSWD} ${.TARGET}
: perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \
:$_[2], "\n");' ${GROUP} ${.TARGET}
:
: ...add this to bsd.kmod.mk and include "uidgid.h" as necessary in
: source files.
Hmmm, I like it... But it does suffer from one problem that we
already have enough of in our tree. The build on one system, install
on another problem. It would be better than the current situtation.
Add ${DESTDIR} to PASSWD and GROUP? That will help.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
[EMAIL PROTECTED] http://softweyr.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Mark Murray writ es: : I don't know either. However, it might be because of permission : problems. It will return EINVAL when it can't open the apm file for : write. Maybe a devfs related issue? : : I don't have devfs on this system yet. Odd that. That's the only place that you can get the error you reported. what does ls -l /dev/apm say? [grimreaper] ~ $ ls -al /dev/apm crw-rw-r-- 1 root operator 39, 0 Sep 14 20:03 /dev/apm (And yes, I try to suspend as root, not as a pleb). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
Warner Losh wrote: In message [EMAIL PROTECTED] Mark Murray writes: : In message [EMAIL PROTECTED] Warner Losh wri : tes: : : 2) APM is now broken. It worked after the ACPI integration, : :but after the SMPNG stuff neither apm -z nor the BIOS keys : :seems to suspend. : : Turns out this isn't the case. : : shutdown -p does not turn off the machine for me (Libretto 110ct). : : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" I noticed this with the first SMPNG kernel I tried. The newer one this problem disappeared. Don't know why it would matter, but I may have missed a commit while in new mexico. It may be a kernel/world sync problem. Although I don't know why the ioctl argument would suddenly become invalid. Maybe it passes in a struct ucred, which changed in size just before the SMPng commit? Warner -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] John Baldwin writes: : It may be a kernel/world sync problem. Although I don't know why the ioctl : argument would suddenly become invalid. Maybe it passes in a struct ucred, : which changed in size just before the SMPng commit? I don't know either. However, it might be because of permission problems. It will return EINVAL when it can't open the apm file for write. Maybe a devfs related issue? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] John Baldwin writes: : Warner Losh wrote: : In message [EMAIL PROTECTED] John Baldwin writes: : : It may be a kernel/world sync problem. Although I don't know why the ioctl : : argument would suddenly become invalid. Maybe it passes in a struct ucred, : : which changed in size just before the SMPng commit? : : I don't know either. However, it might be because of permission : problems. It will return EINVAL when it can't open the apm file for : write. Maybe a devfs related issue? : : Hmm, it may not be using the right perms during make_dev perhaps. Hmmm, they look good to me. Maybe Mark's system doesn't have group operator at gid 5. That's one bad thing about the new DEVFS: it appears to enshrine things like this in the kernel... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
On Thu, 14 Sep 2000 13:46:44 -0600, Warner Losh [EMAIL PROTECTED] said:
Hmmm, they look good to me. Maybe Mark's system doesn't have group
operator at gid 5. That's one bad thing about the new DEVFS: it
appears to enshrine things like this in the kernel...
It would only take a small amount of Makefile magic to fix
this... something like:
PASSWD?=/etc/passwd
GROUP?= /etc/group
uidgid.h: ${PASSWD} ${GROUP}
perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
$_[2], "\n");' ${PASSWD} ${.TARGET}
perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \
$_[2], "\n");' ${GROUP} ${.TARGET}
...add this to bsd.kmod.mk and include "uidgid.h" as necessary in
source files.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Garrett Wollman writes:
: On Thu, 14 Sep 2000 13:46:44 -0600, Warner Losh [EMAIL PROTECTED] said:
: Hmmm, they look good to me. Maybe Mark's system doesn't have group
: operator at gid 5. That's one bad thing about the new DEVFS: it
: appears to enshrine things like this in the kernel...
:
: It would only take a small amount of Makefile magic to fix
: this... something like:
:
: PASSWD?= /etc/passwd
: GROUP?= /etc/group
:
: uidgid.h: ${PASSWD} ${GROUP}
: perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
:$_[2], "\n");' ${PASSWD} ${.TARGET}
: perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \
:$_[2], "\n");' ${GROUP} ${.TARGET}
:
: ...add this to bsd.kmod.mk and include "uidgid.h" as necessary in
: source files.
Hmmm, I like it... But it does suffer from one problem that we
already have enough of in our tree. The build on one system, install
on another problem. It would be better than the current situtation.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
On Thu, 14 Sep 2000 16:42:00 -0400 (EDT), I wrote:
It would only take a small amount of Makefile magic to fix
this... something like:
perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
$_[2], "\n");' ${PASSWD} ${.TARGET}
Oh, I forgot to point out -- this would be easy to do in AWK as well.
(Probably easier, actually, but I don't know AWK well enough to
actually implement it.)
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED], Warner Losh writes: In message [EMAIL PROTECTED] John Baldwin writes: : Warner Losh wrote: : In message [EMAIL PROTECTED] John Baldwin writes: : : It may be a kernel/world sync problem. Although I don't know why the ioctl : : argument would suddenly become invalid. Maybe it passes in a struct ucred, : : which changed in size just before the SMPng commit? : : I don't know either. However, it might be because of permission : problems. It will return EINVAL when it can't open the apm file for : write. Maybe a devfs related issue? : : Hmm, it may not be using the right perms during make_dev perhaps. Hmmm, they look good to me. Maybe Mark's system doesn't have group operator at gid 5. That's one bad thing about the new DEVFS: it appears to enshrine things like this in the kernel... Yes, this is a bad thing, but it is the best compromise solution. You can either manually or with a future general devd(8) fix this. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: SMPNG kernel on UP
On Thu, Sep 14, 2000 at 04:53:54PM -0400, Garrett Wollman wrote:
(Probably easier, actually, but I don't know AWK well enough to
actually implement it.)
awk -F: '$0 ~/^(#|$)/ {next}
{print "#define\tUID_" toupper($1) "\t" $3}' ${PASSWD} ${.TARGET}
--
Jos Backus _/ _/_/_/"Modularity is not a hack."
_/ _/ _/-- D. J. Bernstein
_/ _/_/_/
_/ _/ _/_/
[EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
: zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" I noticed this with the first SMPNG kernel I tried. The newer one this problem disappeared. Don't know why it would matter, but I may have missed a commit while in new mexico. It may be a kernel/world sync problem. Although I don't know why the ioctl argument would suddenly become invalid. Maybe it passes in a struct ucred, which changed in size just before the SMPng commit? Not a synchronization thing. I made sure of that. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
I don't know either. However, it might be because of permission problems. It will return EINVAL when it can't open the apm file for write. Maybe a devfs related issue? I don't have devfs on this system yet. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Mark Murray writes: : I don't know either. However, it might be because of permission : problems. It will return EINVAL when it can't open the apm file for : write. Maybe a devfs related issue? : : I don't have devfs on this system yet. Odd that. That's the only place that you can get the error you reported. what does ls -l /dev/apm say? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
: I don't know either. However, it might be because of permission : problems. It will return EINVAL when it can't open the apm file for : write. Maybe a devfs related issue? : : Hmm, it may not be using the right perms during make_dev perhaps. Hmmm, they look good to me. Maybe Mark's system doesn't have group operator at gid 5. That's one bad thing about the new DEVFS: it appears to enshrine things like this in the kernel... Nope; no devfs, and the master.passwd is as close to standard as mergemaster can get. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Warner Losh writes: : 2) APM is now broken. It worked after the ACPI integration, : but after the SMPNG stuff neither apm -z nor the BIOS keys : seems to suspend. Turns out this isn't the case. : 3) Linux emuation is panics the machine in linux_open on : a normal boot. Turns out to be a bad module. : 4) Need to rebuild all libkvm things, yet again, but : make world fixed that :-) Still true. : 5) USB ethernet is more likely to hang the machine than it was : before. This hand is transient, however. I have seen : one crash removing the USB adapter that I didn't used to : see, but wasn't in a position to look at it in detail. I've not seen this crash again, but things do seem a little slow. The slowness has only been seen in X with an xterm so far, but it has been seen a few times. : 6) Switching virtual termintals from the X server to the : console is busted. This works, but may be realted to the above and below. : 7) SSH to a machine on my local network is dog slow : sometimes. I can type about one line or two lines ahead of : it in email when it happens. It feels like a network pause : of about 1-2 seconds. Local windows behave well during : these episodes. This may be realted to 5. After updating to a newer SMPNG, I'm left with seeing only the USB issue from time to time, but only inside of X. It happens less with the latest update than with the first one. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Sheldon Hearn writes: : 7) SSH to a machine on my local network is dog slow : sometimes. I can type about one line or two lines ahead of : it in email when it happens. It feels like a network pause : of about 1-2 seconds. Local windows behave well during : these episodes. : : I also haven't noticed this. Have you managed to determine that it's : SSH and not your X11 terminal emulator? No. I don't know which one this is. I just know that it happens from time to time. I'll see if I can do something about tracking this down. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Warner Losh wri tes: : 2) APM is now broken. It worked after the ACPI integration, :but after the SMPNG stuff neither apm -z nor the BIOS keys :seems to suspend. Turns out this isn't the case. shutdown -p does not turn off the machine for me (Libretto 110ct). zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
In message [EMAIL PROTECTED] Mark Murray writes: : In message [EMAIL PROTECTED] Warner Losh wri : tes: : : 2) APM is now broken. It worked after the ACPI integration, : : but after the SMPNG stuff neither apm -z nor the BIOS keys : : seems to suspend. : : Turns out this isn't the case. : : shutdown -p does not turn off the machine for me (Libretto 110ct). : : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument" I noticed this with the first SMPNG kernel I tried. The newer one this problem disappeared. Don't know why it would matter, but I may have missed a commit while in new mexico. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
Warner Losh wrote: I've noticed a few things wrong with the SMPNG code. These are mostly impressions. As I learn more about them, I'll file more formal bug reports. This is an FYI to fellow travelers along the path. 1) You can't have I386_CPU at all. This is likely bad in the long run, but OK for now. Err, this should be fixed now. Do you have the latest i386/include/smp.h? 2) APM is now broken. It worked after the ACPI integration, but after the SMPNG stuff neither apm -z nor the BIOS keys seems to suspend. Hmm. 3) Linux emuation is panics the machine in linux_open on a normal boot. Hate to ask, but are you sure it is loading the right module? With the kernel.ko change, modules don't live in the same place anymore, and I haven't seen any commits to kldload, /etc/rc, or linux.sh that takes this into account. 5) USB ethernet is more likely to hang the machine than it was before. This hand is transient, however. I have seen one crash removing the USB adapter that I didn't used to see, but wasn't in a position to look at it in detail. Hmm, ok. 7) SSH to a machine on my local network is dog slow sometimes. I can type about one line or two lines ahead of it in email when it happens. It feels like a network pause of about 1-2 seconds. Local windows behave well during these episodes. Hmm, haven't seen this. 8) The machine seems to pause more often than it used to for reasons totally unknown at this time. These pauses last for several seconds and then things are good again. This might be related to #7, but the total machine pauses happen w/o any network connections. Next time this happens, I'll hit capslock to see if the interrupts are blocked or not. Haven't seen this either. :( Here are some of the known issues that are gotchas: 1) sio is broken. It doesn't receieve any data, although Greg has just fixed this and should be committing a fix shortly. 2) There seem to be some problems with possibly the ahc controller (haven't tried ata yet) where after several hours of heavy load (-j 256 buildworlds and the like) the disk driver will hang. The machine will run fine, top still runs over ssh, for example. However, any process that accesses the disk hangs since it blocks forever waiting on the disk, thus rendering the machine useless. Note that this only happens with SMP. UP seems to be very stable. I haven't had a UP kernel panic or freeze in weeks. 3) The alpha is not entirely stable. I'm working on adding interrupt threads to the alpha right now, which will hopefully help. I think there are some areas in the kernel that are assuming we have the type of locking we have on x86 with ithreads, and am hoping that alpha ithreads will fix those assumptions. Also, there are many changes in dfr's alpha patches that I at least do not understand, and it possibly some of them are incomplete/bogus. Now is a bad time to be thinking about cuting a production machine/snapshot from the -current branch. Are there good times for this? ;-) Warner -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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: SMPNG kernel on UP
On Fri, 08 Sep 2000 00:36:12 CST, Warner Losh wrote: 6) Switching virtual termintals from the X server to the console is busted. This does not appear to be a problem here, with SMPng and XFree86-3.3.6. 7) SSH to a machine on my local network is dog slow sometimes. I can type about one line or two lines ahead of it in email when it happens. It feels like a network pause of about 1-2 seconds. Local windows behave well during these episodes. I also haven't noticed this. Have you managed to determine that it's SSH and not your X11 terminal emulator? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMPNG kernel on UP
On Fri, 08 Sep 2000 00:01:54 MST, John Baldwin wrote: 3) Linux emuation is panics the machine in linux_open on a normal boot. Hate to ask, but are you sure it is loading the right module? With the kernel.ko change, modules don't live in the same place anymore, and I haven't seen any commits to kldload, /etc/rc, or linux.sh that takes this into account. I got annoyed when I read your question, so I set out to reproduce the fatal trap. Of course, since I got the trap, I've deleted my /modules directory. So you're aboslutely right. :-) See my reply to my own message with the subject "HEADS UP: linux module breaks current" to this list. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
