Re: Help with dual head configuration for Acer Ferrari 4000 wmli

[Vladimir Botka]

Dne Wed, 26 Sep 2007 08:41:38 +0300
"Maher Mohamed" <[EMAIL PROTECTED]> napsal(a):

> I need to configure my ATI X700 to be able to have a dual monitor
> since i really need it for representations, I have not have any luck
> in the last year searching around to make it work, I am asking any
> one that has an a machine like mine and has resolved this issue to
> kindly send me any information, I am attaching my xorg.conf in case
> it may help
> 
> 
> thank you in advanced.
> 
> PS: DO NOT BUY ATI PRODUCTS PEOPLE, I MADE A HUGE MISTAKE
> 
> 
> Mohamed M. Maher

To avoid the troubles it is recommended to check the "Hardware notes"
before purchase.

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

Help with dual head configuration for Acer Ferrari 4000 wmli

[Maher Mohamed]

I need to configure my ATI X700 to be able to have a dual monitor since i
really need it for representations, I have not have any luck in the last
year searching around to make it work, I am asking any one that has an a
machine like mine and has resolved this issue to kindly send me any
information, I am attaching my xorg.conf in case it may help


thank you in advaced.

PS: DO NOT BUY ATI PRODUCTS PEOPLE, I MADE A HUGE MISTAKE

-- 
Mohamed M. Maher
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Help with dual head configuration for Acer Ferrari 4000 wmli

[Maher Mohamed]

I need to configure my ATI X700 to be able to have a dual monitor since i
really need it for representations, I have not have any luck in the last
year searching around to make it work, I am asking any one that has an a
machine like mine and has resolved this issue to kindly send me any
information, I am attaching my xorg.conf in case it may help


thank you in advanced.

PS: DO NOT BUY ATI PRODUCTS PEOPLE, I MADE A HUGE MISTAKE


Mohamed M. Maher


xorg.conf
Description: Binary data
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rm(1) bug, possibly serious

[CmdLnKid]

On Tue, 25 Sep 2007 17:55 +0100, jan.grant wrote:


On Tue, 25 Sep 2007, Oliver Fromme wrote:


Note that the command "rm -rf ../" was entered twice.
The first time I got an error message (and exit code 1),
the second time it apparently succeeded.


Check the man page for rm:

  -f  Attempt to remove the files without prompting for confirma-
tion, regardless of the file's permissions.  If the file does
not exist, do not display a diagnostic message or modify the
exit status to reflect an error.

That's what's happening the second time through. The first time, your
current directory is getting removed (so ../ won't refer to a real
directory the second time around). The bug is really in rm(1)'s initial
diagnostic message.



Just wanted to point out that this actually goes all the way back as far 
as 4.6.2-RELEASE-p27. I dont have any earlier machines than that to test

on but best guess is that it most likely goes back further than that.

--

 - (2^(N-1))

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

Re: rm(1) bug, possibly serious

[Bob Johnson]

On 9/25/07, Oliver Fromme <[EMAIL PROTECTED]> wrote:
> Torfinn Ingolfsen wrote:
>  > Oliver Fromme wrote:
>  >
>  > > $ cd /tmp
>  > > $ mkdir -p foo/var
>  > > $ cd foo/bar
>  > > $ rm -rf ../
>  > > rm: ../: Invalid argument
>  > > $ rm -rf ../
>  > > $
>  > >
[...]
>  > Quick testing here:
>  > [...]
>  > Ok, I think it is a bug.
>
> Yes, I think so, too.
>
> By the way, an additional confusion is that ".." and "../"
> are handled differently.  Specifying ".." always leads to
> this message:
>
> rm: "." and ".." may not be removed
>
> and nothing is actually removed.  It is confusing that
> adding a slash leads to a different error message _and_
> removal of the contents of the parent directory.  Clearly
> a POLA violation.

Maybe. But I expect that the behavior for "rm -rf .." is there so that
things don't get REALLY astonishing when you do "rm -rf *". Having a
different behavior for "rm -rf ../" may have been intentional on
someone's part so you can override the protection if you really want
to.

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

Re: FreeBSD PseudoRAID RAID0 array broken on atapci1:

[Yarema]

--On Tuesday, September 25, 2007 8:49 AM +0200 Søren Schmidt 
<[EMAIL PROTECTED]> wrote:



Yarema wrote:

Hi, I need some help recovering from this.  First some back story.
Running 6.2-STABLE i386 from Sep 17, 2007.  My /home slice is mounted
from /dev/ar0s1e where the relevant kernel messages look like so when
all is good:

atapci1: 
ata2:  on atapci1
ata3:  on atapci1
ad4: 381554MB  at ata2-master SATA150
ad6: 381554MB  at ata3-master SATA150
ar0: 763108MB  status: READY
ar0: disk0 READY using ad4 at ata2-master
ar0: disk1 READY using ad6 at ata3-master

Today this server crashed with the following loggeed:

ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=144888320
ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=143390319
ad4: FAILURE - device detached
ar0: FAILURE - RAID0 array broken
subdisk4: detached
ad4: detached
g_vfs_done():ar0s1e[WRITE(offset=146002964480, length=2048)]error = 5
initiate_write_filepage: already started
g_vfs_done():ar0s1e[WRITE(offset=146002964480, length=2048)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6144000, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6160384, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6176768, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6193152, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6209536, length=2048)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=65536, length=2048)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=147801325568, length=12288)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=147142686720, length=2048)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=65536, length=2048)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6144000, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6160384, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6176768, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6193152, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=6209536, length=2048)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=146831867904, length=16384)]error = 5
g_vfs_done():ar0s1e[WRITE(offset=147024330752, length=16384)]error = 5
initiate_write_filepage: already started
g_vfs_done():ar0s1e[WRITE(offset=146002964480, length=2048)]error = 5
initiate_write_filepage: already started
g_vfs_done():ar0s1e[WRITE(offset=146002964480, length=2048)]error = 5
initiate_write_filepage: already started
g_vfs_done():ar0s1e[WRITE(offset=147801325568, length=12288)]error = 5
initiate_write_filepage: already started
g_vfs_done():ar0s1e[WRITE(offset=147142686720, length=2048)]error = 5

Now the kernel messages read:

ar0: FAILURE - RAID0 array broken
ar0: 763108MB  status: BROKEN
ar0: disk0 READY using ad4 at ata2-master
ar0: disk1 DOWN no device found for this subdisk
ar1: 763108MB  status: BROKEN
ar1: disk0 DOWN no device found for this subdisk
ar1: disk1 READY using ad6 at ata3-master

For some reason the second disk in the array shows up as ar1 instead
of being part of ar0.  I suspect there's gotta be some way to force
the two drives to show up as part of the same array by perhaps editing
the PseudoRAID metadata on disk without putting any of the UFS2 data
in "jeopardy".  Any pointers on where to start poking around for the
relevant metadata structures on disk or what to search for?  I figure
if I can dd the metadata off the disks, tweak a field or two and then
dd the whole mess back I stand a chance of either hosing the array
irrevocably or getting it all back. ;)  Or maybe atacontrol could be
used to re-create the metadata without destroying the UFS2 on the
array?  I have a coredump of the kernel from this crash if that helps
analyze things any.



The solution to getting the array back is to "atacontrol delete ar0"
"atacontrol delete ar1" "atacontrol create stripe 512 ad4 ad6" and
the array is reborn.
 However your filesystems might be just a bunch of bits depending
on how much of the failed write that made it in there, you get the
(missing) protection you asked for using RAID0


Søren,

Thank you for your prompt and helpful reply.  I'm running into an new 
situation with atacontrol:


% atacontrol create RAID0 512 ad4 ad6
ar0: 763108MB  status: READY
ar0: disk0 READY using ad4 at ata2-master
ar0: disk1 READY using ad6 at ata3-master

Note that the original RAID0 which broke was
ar0: 763108MB  status: READY

Now atacontrol will not create FreeBSD PseudoRAID metadata with a 256KB 
stripe, but insists on creating Intel MatrixRAID metadata with a 128KB 
stripe.  This is on a non-R version of the ICH5 southbridge.  So there's no 
way to enable/disable the Intel MatrixRAID from the BIOS.  Nor is there any 
way to change the stripe size in the BIOS since there is no Intel 
MatrixRAID BIOS on this motherboard.  The computer in question is a Dell 
SC400 with an Intel OEM motherboard which has a very limited BIOS Setup 
interface typical of Intel/Dell.


Is there any way to force atacontrol to create FreeBSD PseudoRAID metadata? 
Perhaps using an older FreeSBIE release based on FreeBSD 6.0 since IIRC

Re: rm(1) bug, possibly serious

[Patrick M. Hausen]

Hello!

On Tue, Sep 25, 2007 at 11:54:14PM +0200, Oliver Brandmueller wrote:

> In sh:
> 
> $ which rm
> /bin/rm
> $ cd /tmp
> $ mkdir -p foo/bar
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument

$ pwd
/tmp
$ ktrace -i /bin/sh
$ which rm
/bin/rm
$ mkdir -p foo/bar
$ cd foo/bar
$ rm -rf ../
rm: ../: Invalid argument
$ rm -rf ../
$ ktrace -C

 ...
 35356 rm   NAMI  "../"
 35356 rm   RET   rmdir -1 errno 22 Invalid argument
 ...
 35488 rm   NAMI  "../"
 35488 rm   RET   lstat -1 errno 2 No such file or directory
 ...

HTH,
Patrick
-- 
punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
[EMAIL PROTECTED]   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rm(1) bug, possibly serious

[Oliver Brandmueller]

Hi,

On Tue, Sep 25, 2007 at 11:25:34AM -0400, Maxim Khitrov wrote:
> On 9/25/07, Oliver Fromme <[EMAIL PROTECTED]> wrote:
> > To add further confusion, another "rm -rf ../" does
> > not print an error message and seemingly succeeds,
> > even though ".." does not exist anymore in the current
> > directory (which has been removed).
> 
> Confirmed on CURRENT as well. Note that if you run rf -rf .. as the
> first command, the command does fail with 'rm: "." and ".." may not be
> removed'. Adding a / at the end does seem to get around this check.

May I add some more confusion?

In tcsh:

(23:49) [EMAIL PROTECTED]:ttyp2 [~] which rm
/bin/rm
(23:49) [EMAIL PROTECTED]:ttyp2 [~] cd /tmp
(23:49) [EMAIL PROTECTED]:ttyp2 [/tmp] mkdir -p foo/bar
(23:49) [EMAIL PROTECTED]:ttyp2 [/tmp] cd foo/bar
(23:49) [EMAIL PROTECTED]:ttyp2 [foo/bar] rm -rf ../
(23:49) [EMAIL PROTECTED]:ttyp2 [foo/bar] pwd
pwd: .: No such file or directory
(23:52) [EMAIL PROTECTED]:ttyp2 [foo/bar] cd /tmp
(23:52) [EMAIL PROTECTED]:ttyp2 [/tmp] ls
(23:52) [EMAIL PROTECTED]:ttyp2 [/tmp] 


In sh:

$ which rm
/bin/rm
$ cd /tmp
$ mkdir -p foo/bar
$ cd foo/bar
$ rm -rf ../
rm: ../: Invalid argument
$ pwd
/tmp/foo/bar
$ rm -rf ../
$ pwd
/tmp/foo/bar
$ cd /tmp
$ ls
foo
$ cd foo
$ ls


(23:53) [EMAIL PROTECTED]:ttyp2 [~] uname -a
FreeBSD nowhere.ob-home.lan 6.2-STABLE FreeBSD 6.2-STABLE #17: Sun Aug  5 
19:03:13 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOWHERE  i386


- Olli


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


pgpR1kZ5k8oxV.pgp
Description: PGP signature

Re: rm(1) bug, possibly serious

[LI Xin]

Oliver Fromme wrote:
> Nicolas Rachinsky wrote:
>  > Oliver Fromme wrote:
>  > > By the way, an additional confusion is that ".." and "../"
>  > > are handled differently.  Specifying ".." always leads to
>  > > this message:
>  > > 
>  > > rm: "." and ".." may not be removed
>  > > 
>  > > and nothing is actually removed.  It is confusing that
>  > > adding a slash leads to a different error message _and_
>  > > removal of the contents of the parent directory.  Clearly
>  > > a POLA violation.
>  > 
>  > Adding a slash often leads to different behaviour.
> 
> Yes, I'm aware of that.  I often make use of the feature
> that "find /sys/" expands the symlink, while "find /sys"
> does not.  The same holds true for ls(1).
> 
> However, I would still argue that there is no sane reason
> for "rm -rf ../" behaving differently from "rm -rf ..",
> especially because it behaves differently in a destructive
> way.  That's why I call it a POLA violation.

Also a POSIX violation IMHO :-)

Cheers,
-- 
Xin LI <[EMAIL PROTECTED]>  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature

Re: rm(1) bug, possibly serious

[Oliver Fromme]

Nicolas Rachinsky wrote:
 > Oliver Fromme wrote:
 > > By the way, an additional confusion is that ".." and "../"
 > > are handled differently.  Specifying ".." always leads to
 > > this message:
 > > 
 > > rm: "." and ".." may not be removed
 > > 
 > > and nothing is actually removed.  It is confusing that
 > > adding a slash leads to a different error message _and_
 > > removal of the contents of the parent directory.  Clearly
 > > a POLA violation.
 > 
 > Adding a slash often leads to different behaviour.

Yes, I'm aware of that.  I often make use of the feature
that "find /sys/" expands the symlink, while "find /sys"
does not.  The same holds true for ls(1).

However, I would still argue that there is no sane reason
for "rm -rf ../" behaving differently from "rm -rf ..",
especially because it behaves differently in a destructive
way.  That's why I call it a POLA violation.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

Python is executable pseudocode.  Perl is executable line noise.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rm(1) bug, possibly serious

[Nicolas Rachinsky]

* Oliver Fromme <[EMAIL PROTECTED]> [2007-09-25 19:43 +0200]:
> By the way, an additional confusion is that ".." and "../"
> are handled differently.  Specifying ".." always leads to
> this message:
> 
> rm: "." and ".." may not be removed
> 
> and nothing is actually removed.  It is confusing that
> adding a slash leads to a different error message _and_
> removal of the contents of the parent directory.  Clearly
> a POLA violation.

Adding a slash often leads to different behaviour.

[EMAIL PROTECTED] ~/rd> mkdir foo; ln -s foo bar
[EMAIL PROTECTED] ~/rd> rm -r bar
[EMAIL PROTECTED] ~/rd> ls -l
total 2
drwxr-xr-x  2 nicolas  wheel  512 Sep 25 20:55 foo/
[EMAIL PROTECTED] ~/rd> 

[EMAIL PROTECTED] ~/rd> mkdir foo; ln -s foo bar
[EMAIL PROTECTED] ~/rd> rm -r bar/
[EMAIL PROTECTED] ~/rd> ls -l
total 0
lrwxr-xr-x  1 nicolas  wheel  3 Sep 25 20:56 bar@ -> foo
[EMAIL PROTECTED] ~/rd> 

And cp -R behaves differently for dir and dir/, too, but it is
explicitly documented there.

Nicolas

-- 
http://www.rachinsky.de/nicolas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rm(1) bug, possibly serious

[LI Xin]

I think this is a bug, here is a fix obtained from NetBSD.

The reasoning (from NetBSD's rm.c,v 1.16):

Strip trailing slashes of operands in checkdot().

POSIX.2 requires that if "." or ".." are specified as the basename
portion of an operand, a diagnostic message be written to standard
error, etc.  We strip the slashes because POSIX.2 defines basename
as the final portion of a pathname after trailing slashes have been
removed.

This also makes rm "perform actions equivalent to" the POSIX.1
rmdir() and unlink() functions when removing directories and files,
even when they do not follow POSIX.1's pathname resolution semantics
(which require trailing slashes be ignored).

If nobody complains about this I will request for commit approval from [EMAIL 
PROTECTED]

Cheers,
-- 
Xin LI <[EMAIL PROTECTED]>  http://www.delphij.net/
FreeBSD - The Power to Serve!
Index: rm.c
===
RCS file: /home/ncvs/src/bin/rm/rm.c,v
retrieving revision 1.58
diff -u -p -r1.58 rm.c
--- rm.c31 Oct 2006 02:22:36 -  1.58
+++ rm.c25 Sep 2007 18:26:52 -
@@ -558,6 +558,14 @@ check2(char **argv)
return (first == 'y' || first == 'Y');
 }
 
+/*
+ * POSIX.2 requires that if "." or ".." are specified as the basename
+ * portion of an operand, a diagnostic message be written to standard
+ * error and nothing more be done with such operands.
+ *
+ * Since POSIX.2 defines basename as the final portion of a path after
+ * trailing slashes have been removed, we'll remove them here.
+ */
 #define ISDOT(a)   ((a)[0] == '.' && (!(a)[1] || ((a)[1] == '.' && 
!(a)[2])))
 void
 checkdot(char **argv)
@@ -567,10 +575,17 @@ checkdot(char **argv)
 
complained = 0;
for (t = argv; *t;) {
+   /* strip trailing slashes */
+   p = strrchr(*t, '\0');
+   while (--p > *t && *p == '/')
+   *p = '\0';
+
+   /* extract basename */
if ((p = strrchr(*t, '/')) != NULL)
++p;
else
p = *t;
+
if (ISDOT(p)) {
if (!complained++)
warnx("\".\" and \"..\" may not be removed");


signature.asc
Description: OpenPGP digital signature

Re: device polling and weird timer interrupt count from vmstat

[Michael Proto]

Artem Kuchin wrote:
> Oliver Fromme wrote:
>> Artem Kuchin wrote:
>>> Oliver Fromme wrote:
 Artem Kuchin wrote:
> 3) Is timer int really generated on each cpu? Am i really wasting
> cpu time on ~4000 ints per second?

 4000 ints per second is rather nothing on any modern CPU.
 Have a look at the top(1) display of an otherwise idle
 system.  The "%interrupt" column should be zero, even if
 it's processing 4000 timer interrupts per second.  As far
 as I know, the cpu timer interrupt handler is very light-
 weight.
>>>
>>> Thank you for the answer. My convern is that with 4 CPUs i get 8000
>>> ints/second.  While em generates only about 200 ints/second. As i
>>> undertand not all int handlers are the same. Some are heavy and some
>>> are light on CPU. So, the question is what is better (better=less CPU
>>> time): 8000 ints/sec from timer or 200 ints/sec from NIC?
>>
>> There's no simple answer to the question.  The best way is
>> to just try it.  As I wrote, run top(1) while the system is
>> idle, so only the cpu timer interrupts are active.  If the
>> "%interrupt" column is zero most of the time, then there
>> is nothing to worry about at all.
>>
>> However, if you have a constant non-zero %interrupt value,
>> you might consider lowering HZ, and you might reconsider
>> whether polling really has advantages in your situation.
>> Do you have reasons to believe so?  Remember that the main
>> purpose of polling is to improve interactivity under very
>> high network load.  If you're not in such a situation, then
>> polling probably doesn't buy you much.
> 
> Well, problem with top is that on dual 3GHZ box it alsway s
> shows 0% load when not loaded with real traffic (web traffic) no matter
> if it is polling of int handling. And when loaded with real traffic
> web server eat a lot more cpu power then traffic handling, so, no
> separate measurement of traffic cpu load is possible.
> But i think it is possible to simulate this kind of load, need to think
> about
> it.
> 
> Also, when it comes to public web server i can never be secure enough and
> crazy load of traffic can come any time from DDOS attack which can bring
> down any box. So, for public web server it is a matter of security and
> managebility to have server interactive even on high traffic load. So,
> even from
> this poing of view polling can be usefull.
> 

Would it not be advisable then to simply limit the maximum number of
allowed connections, ala sysctl kern.ipc.somaxconn, rather then to
enable polling? I can see using polling on a router or some device that
funnels traffic through multiple interfaces, but rarely have I seen it
useful on a single-homed box where sysctls might be better used to limit
connections. May be old news, but I've read that polling on a SMP
machine is questionable anyway (http://info.iet.unipi.it/~luigi/polling/).


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

Re: in openpam_load_module(): no pam_unix.so found

[Victor Star]

Hi Mike,

Now, before I got a chance to try it out it suddenly works again.
As good of a new as it is, I don't really like things fixing themselves without 
my knowledge of
what's going on... Looks like a good time to start learning about rootkits. Of 
course there is a
possibility of some resource-related issue, but I would expect at least to see 
something in
messages, or other log files

I'll keep this email for future in case it happens again.

Thank you for your help!

Victor

> On Mon, Sep 24, 2007 at 09:29:08AM -0400, Victor Star wrote:
>> ==- 8< 
>> -
>> fireball# ldd /usr/lib/pam_unix.so
>> /usr/lib/pam_unix.so:
>> libutil.so.5 => /lib/libutil.so.5 (0x28167000)
>> libcrypt.so.3 => /lib/libcrypt.so.3 (0x28173000)
>> libypclnt.so.2 => /usr/lib/libypclnt.so.2 (0x2818b000)
>> libpam.so.3 => /usr/lib/libpam.so.3 (0x2818f000)
>> fireball# ldd /usr/lib/pam_unix.so.3
>> /usr/lib/pam_unix.so.3:
>> libutil.so.5 => /lib/libutil.so.5 (0x28167000)
>> libcrypt.so.3 => /lib/libcrypt.so.3 (0x28173000)
>> libypclnt.so.2 => /usr/lib/libypclnt.so.2 (0x2818b000)
>> libpam.so.3 => /usr/lib/libpam.so.3 (0x2818f000)

> Hmm. That all looks ok.   

> The relevant code inside openpam[1] does something like

> dlopen(OPENPAM_MODULES_DIR . "/pam_unix.so.3", RTLD_NOW)

> and if that fails, tries

> dlopen(OPENPAM_MODULES_DIR . "/pam_unix.so", RTLD_NOW)

> Both of these must have failed when su ran.  

> It may be worth compiling the following:

> : [EMAIL PROTECTED]:~ ; cat dlopentest.c 
> #include 
> #include 

> int
> main (int argc, char **argv) {

> void *dlh;

> dlh = dlopen(argv[1], RTLD_NOW);
> if (dlh) {
> printf("dlopen %s worked\n", argv[1]);
> } else {
> printf("dlopen %s failed: %s\n", argv[1], dlerror());
> }
> return 0;
> }
> : [EMAIL PROTECTED]:~ ; make dlopentest
> cc -O2 -fno-strict-aliasing -pipe -march="pentium3"  dlopentest.c  -o 
> dlopentest
> : [EMAIL PROTECTED]:~ ; ./dlopentest /usr/lib/pam_unix.so
> dlopen /usr/lib/pam_unix.so worked
> : [EMAIL PROTECTED]:~ ; ./dlopentest /usr/lib/pam_unix.so.3
> dlopen /usr/lib/pam_unix.so.3 worked
> : [EMAIL PROTECTED]:~ ; ./dlopentest /usr/lib/pam_kasjajsk.so
> dlopen /usr/lib/pam_kasjajsk.so failed: Cannot open "/usr/lib/pam_kasjajsk.so"
> : [EMAIL PROTECTED]:~ ;

> this may give you a clue as to why the dlopen failed.  If that
> doesn't point at a problem, then recompile su with _openpam_debug
> = 1, and setup syslog to log LOG_DEBUG messages somewhere and see
> what happens.


> [1] assuming a version of FreeBSD suitably similar to the one I
> have here, of course.



>> 
>> ==- 8< 
>> -
>> 
>> As for when it stopped working - the first thing I did is trying to recall 
>> if I updated any ports.
>> I've even went so far as looking for all files in /usr/ modified within the 
>> date range, but no,
>> nothing.
>> 
>> I did update php5 couple days before that. But it still worked for about two 
>> days after that.
>> And I don't have apache/php opened to outside anyway. Just mail ports and 
>> ssh on high port (closed
>> it for now for just in case anyway).
>> 
>> Victor
>> 
>> >> - 8< -===
>> >> su: in openpam_load_module(): no pam_unix.so found
>> >> su: pam_start: system error
>> >> - 8< -===
>> >> 
>> >> pam_unix.so is in /usr/lib:
>> >> - 8< -===
>> >> # ls -l /usr/lib/pam_unix*
>> >> lrwxr-xr-x  1 root  wheel 13 Sep 25  2006 /usr/lib/pam_unix.so -> 
>> >> pam_unix.so.3
>> >> -r--r--r--  1 root  wheel  10240 Feb 19  2007 /usr/lib/pam_unix.so.3
>> >> # file /usr/lib/pam_unix.so
>> >> /usr/lib/pam_unix.so: symbolic link to `pam_unix.so.3'
>> >> - 8< -===
>> 
>> > First, this is how a problem should be described, great work.
>> 
>> > When openpam can't load a module, it also print's the 'not found' message.
>> > With 'ldd /usr/lib/pam_unix.so.3' you can see if all the libraries that
>> > it needs are in place. On my systems it give's the following output:
>> 
>> > $ ldd /usr/lib/pam_unix.so.3 
>> > /usr/lib/pam_unix.so.3:
>> > libutil.so.5 => /lib/libutil.so.5 (0x28169000)
>> > libcrypt.so.3 => /lib/libcrypt.so.3 (0x28175000)
>> > libypclnt.so.2 => /usr/lib/libypclnt.so.2 (0x2818d000)
>> > libpam.so.3 => /usr/lib/libpam.so.3 (0x28191000)
>> 
>> >> - 8< -===
>> >> Sep 18 11:11:37 xx su: BAD SU  to root on /dev/ttyp3
>> >> Sep 18 11:13:46 xx sshd[45047]: Bad protocol version identification 
>> >> '\377\364\377\375\006quit' from 
>> >> Sep 18 11:15:08 xx sshd[45056]: Receiv

Re: rm(1) bug, possibly serious

[Oliver Fromme]

Torfinn Ingolfsen wrote:
 > Oliver Fromme wrote:
 > 
 > > $ cd /tmp
 > > $ mkdir -p foo/var
 > > $ cd foo/bar
 > > $ rm -rf ../
 > > rm: ../: Invalid argument
 > > $ rm -rf ../
 > > $ 
 > > 
 > > Note that the command "rm -rf ../" was entered twice.
 > > The first time I got an error message (and exit code 1),
 > > the second time it apparently succeeded.  The very same
 > > command.
 > 
 > What happens if you issue a 'pwd' command after each 'rm -rf ../'?
 > We want to see the output.

It's /tmp/foo/bar every time.

 > IMHO, the only way the second rm command *should* succeed, is if it
 > invalidates the current working directory, thus releasing the last lock
 > on the directory.
 > 
 > Quick testing here:
 > [...]
 > Ok, I think it is a bug.

Yes, I think so, too.

By the way, an additional confusion is that ".." and "../"
are handled differently.  Specifying ".." always leads to
this message:

rm: "." and ".." may not be removed

and nothing is actually removed.  It is confusing that
adding a slash leads to a different error message _and_
removal of the contents of the parent directory.  Clearly
a POLA violation.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"Perl will consistently give you what you want,
unless what you want is consistency."
-- Larry Wall
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: device polling and weird timer interrupt count from vmstat

[Artem Kuchin]

Oliver Fromme wrote:

Artem Kuchin wrote:

Oliver Fromme wrote:

Artem Kuchin wrote:

3) Is timer int really generated on each cpu? Am i really wasting
cpu time on ~4000 ints per second?


4000 ints per second is rather nothing on any modern CPU.
Have a look at the top(1) display of an otherwise idle
system.  The "%interrupt" column should be zero, even if
it's processing 4000 timer interrupts per second.  As far
as I know, the cpu timer interrupt handler is very light-
weight.


Thank you for the answer. My convern is that with 4 CPUs i get 8000
ints/second.  While em generates only about 200 ints/second. As i
undertand not all int handlers are the same. Some are heavy and some
are light on CPU. So, the question is what is better (better=less CPU
time): 8000 ints/sec from timer or 200 ints/sec from NIC?


There's no simple answer to the question.  The best way is
to just try it.  As I wrote, run top(1) while the system is
idle, so only the cpu timer interrupts are active.  If the
"%interrupt" column is zero most of the time, then there
is nothing to worry about at all.

However, if you have a constant non-zero %interrupt value,
you might consider lowering HZ, and you might reconsider
whether polling really has advantages in your situation.
Do you have reasons to believe so?  Remember that the main
purpose of polling is to improve interactivity under very
high network load.  If you're not in such a situation, then
polling probably doesn't buy you much.


Well, problem with top is that on dual 3GHZ box it alsway s
shows 0% load when not loaded with real traffic (web traffic) no matter
if it is polling of int handling. And when loaded with real traffic
web server eat a lot more cpu power then traffic handling, so, no
separate measurement of traffic cpu load is possible.
But i think it is possible to simulate this kind of load, need to think about
it.

Also, when it comes to public web server i can never be secure enough and
crazy load of traffic can come any time from DDOS attack which can bring
down any box. So, for public web server it is a matter of security and
managebility to have server interactive even on high traffic load. So, even from
this poing of view polling can be usefull.

--
Regards,
Artem

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

Re: rm(1) bug, possibly serious

[Jan Grant]

On Tue, 25 Sep 2007, Oliver Fromme wrote:

> Note that the command "rm -rf ../" was entered twice.
> The first time I got an error message (and exit code 1),
> the second time it apparently succeeded.

Check the man page for rm:

   -f  Attempt to remove the files without prompting for confirma-
 tion, regardless of the file's permissions.  If the file does
 not exist, do not display a diagnostic message or modify the
 exit status to reflect an error.

That's what's happening the second time through. The first time, your 
current directory is getting removed (so ../ won't refer to a real 
directory the second time around). The bug is really in rm(1)'s initial 
diagnostic message.



-- 
jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/
Tel +44 (0)117 3317661   http://ioctl.org/jan/
We thought time travel was impossible. But that was now and this is then.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

cvs questions

[Stefan Lambrev]

Hello,

Sorry if this is off-topic here, but I want to ask few questions about 
the cvs that is in FreeBSD base system.


We have project that is in cvs and we uses different branches.
I want to separate permitions for different developers, and to allow all 
of them to commit
changes in HEAD, but only few of them to be able to make changes in 
STABLE branch for example.


From what I found I should use commitinfo for this, but I have the 
feeling, that I cannot provide the name of the branch

in this file as variable to the script that is run.

Any ideas how to accomplish this? Is it possible without additional patches?

--

Best Wishes,
Stefan Lambrev
ICQ# 24134177

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

Re: rm(1) bug, possibly serious

[Torfinn Ingolfsen]

On Tue, 25 Sep 2007 17:12:50 +0200 (CEST)
Oliver Fromme <[EMAIL PROTECTED]> wrote:

> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
> $ rm -rf ../
> $ 
> 
> Note that the command "rm -rf ../" was entered twice.
> The first time I got an error message (and exit code 1),
> the second time it apparently succeeded.  The very same
> command.

What happens if you issue a 'pwd' command after each 'rm -rf ../'?
We want to see the output.

IMHO, the only way the second rm command *should* succeed, is if it
invalidates the current working directory, thus releasing the last lock
on the directory.

Quick testing here:
[EMAIL PROTECTED] mkdir -p foo/bar
[EMAIL PROTECTED] cd foo/bar
[EMAIL PROTECTED] ll
total 4
drwxr-xr-x  2 tingo  wheel  - 512 Sep 25 17:31 ./
drwxr-xr-x  3 tingo  wheel  - 512 Sep 25 17:31 ../
[EMAIL PROTECTED] pwd
/tmp/foo/bar
[EMAIL PROTECTED] rm -rf ../
rm: ../: Invalid argument
[EMAIL PROTECTED] pwd
/tmp/foo/bar
[EMAIL PROTECTED] rm -rf ../
[EMAIL PROTECTED] pwd
/tmp/foo/bar
[EMAIL PROTECTED] ls -al
total 0
[EMAIL PROTECTED] ll
total 0
[EMAIL PROTECTED] pwd
/tmp/foo/bar
[EMAIL PROTECTED] ls -al ..
ls: ..: No such file or directory
[EMAIL PROTECTED] ls -al /tmp/foo/bar
ls: /tmp/foo/bar: No such file or directory
[EMAIL PROTECTED] ls -al /tmp/foo
total 8
drwxr-xr-x   2 tingo  wheel   512 Sep 25 17:32 .
drwxrwxrwt  35 root   wheel  5632 Sep 25 17:31 ..


Ok, I think it is a bug.
-- 
Regards,
Torfinn Ingolfsen

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

Re: rm(1) bug, possibly serious

[Oleg Nauman]

On Tue, Sep 25, 2007 at 05:12:50PM +0200, Oliver Fromme wrote:
> Hi,
> 
> Today I noticed the following behaviour on a 6-stable
> machine:
> 
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar

 Looks like you have mistyped 'mkdir' argument :)

> $ rm -rf ../
> rm: ../: Invalid argument

 Please type 'pwd' here

> $ rm -rf ../
> $ 
> 
> Note that the command "rm -rf ../" was entered twice.
> The first time I got an error message (and exit code 1),
> the second time it apparently succeeded.  The very same
> command.
> 
> Further investigation:
> 
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
> $ ls -al ..
> ls: ..: No such file or directory
> $ ls /tmp/foo/bar
> ls: /tmp/foo/bar: No such file or directory
> 
> That means:  Even though "rm -rf ../" prints an error
> message, indicating that the argument is invalid, it
> *DOES* remove the contents of the parent directory!
> 
> To add further confusion, another "rm -rf ../" does
> not print an error message and seemingly succeeds,
> even though ".." does not exist anymore in the current
> directory (which has been removed).
> 
> Shall I file a PR?  Or is rm working correctly, and
> my assumptions are wrong?
> 
> Best regards
>Oliver
> 
> -- 
> Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
> Handelsregister: Registergericht Muenchen, HRA 74606,  GeschДftsfuehrung:
> secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht MЭn-
> chen, HRB 125758,  GeschДftsfЭhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart
> 
> FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd
> 
> "The scanf() function is a large and complex beast that often does
> something almost but not quite entirely unlike what you desired."
> -- Chris Torek

-- 
The ultimate artifact may be found in the driven snow... 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

"ioapicx" warnings at boot

[Mike Lempriere]

I just did a firmware upgrade on my Dell 2850 FreeBSD server.  I'm seeing the 
following warnings at boot time.  (I am not sure that they weren't there before 
the firmware upgrade.)

Should I be worried about this?  And if so, what do I need to do...

Thanks!


Copyright (c) 1992-2006 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.5-STABLE #1: Thu Aug 23 07:53:36 PDT 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/VINIFERA
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.02-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf43  Stepping = 3
  
Features=0xbfebfbff
  Hyperthreading: 2 logical CPUs
real memory  = 2147221504 (2047 MB)
avail memory = 2095742976 (1998 MB)
ioapic0: Changing APIC ID to 2
ioapic1: Changing APIC ID to 3
ioapic1: WARNING: intbase 32 != expected base 24
ioapic2: Changing APIC ID to 4
ioapic2: WARNING: intbase 64 != expected base 56
ioapic3: Changing APIC ID to 5
ioapic3: WARNING: intbase 96 != expected base 88
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 32-55 on motherboard


--
Mike Lempriere- Home: [EMAIL PROTECTED]  Phone: 206-780-2146
Cellphone: 206-200-5902;  text pager: [EMAIL PROTECTED]


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

Re: rm(1) bug, possibly serious

[Maxim Khitrov]

On 9/25/07, Oliver Fromme <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Today I noticed the following behaviour on a 6-stable
> machine:
>
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
> $ rm -rf ../
> $
>
> Note that the command "rm -rf ../" was entered twice.
> The first time I got an error message (and exit code 1),
> the second time it apparently succeeded.  The very same
> command.
>
> Further investigation:
>
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
> $ ls -al ..
> ls: ..: No such file or directory
> $ ls /tmp/foo/bar
> ls: /tmp/foo/bar: No such file or directory
>
> That means:  Even though "rm -rf ../" prints an error
> message, indicating that the argument is invalid, it
> *DOES* remove the contents of the parent directory!
>
> To add further confusion, another "rm -rf ../" does
> not print an error message and seemingly succeeds,
> even though ".." does not exist anymore in the current
> directory (which has been removed).
>
> Shall I file a PR?  Or is rm working correctly, and
> my assumptions are wrong?
>
> Best regards
>Oliver

Confirmed on CURRENT as well. Note that if you run rf -rf .. as the
first command, the command does fail with 'rm: "." and ".." may not be
removed'. Adding a / at the end does seem to get around this check.

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

rm(1) bug, possibly serious

[Oliver Fromme]

Hi,

Today I noticed the following behaviour on a 6-stable
machine:

$ cd /tmp
$ mkdir -p foo/var
$ cd foo/bar
$ rm -rf ../
rm: ../: Invalid argument
$ rm -rf ../
$ 

Note that the command "rm -rf ../" was entered twice.
The first time I got an error message (and exit code 1),
the second time it apparently succeeded.  The very same
command.

Further investigation:

$ cd /tmp
$ mkdir -p foo/var
$ cd foo/bar
$ rm -rf ../
rm: ../: Invalid argument
$ ls -al ..
ls: ..: No such file or directory
$ ls /tmp/foo/bar
ls: /tmp/foo/bar: No such file or directory

That means:  Even though "rm -rf ../" prints an error
message, indicating that the argument is invalid, it
*DOES* remove the contents of the parent directory!

To add further confusion, another "rm -rf ../" does
not print an error message and seemingly succeeds,
even though ".." does not exist anymore in the current
directory (which has been removed).

Shall I file a PR?  Or is rm working correctly, and
my assumptions are wrong?

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"The scanf() function is a large and complex beast that often does
something almost but not quite entirely unlike what you desired."
-- Chris Torek
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: device polling and weird timer interrupt count from vmstat

[Oliver Fromme]

Artem Kuchin wrote:
 > Oliver Fromme wrote:
 > > Artem Kuchin wrote:
 > > > 3) Is timer int really generated on each cpu? Am i really wasting
 > > > cpu time on ~4000 ints per second?
 > > 
 > > 4000 ints per second is rather nothing on any modern CPU.
 > > Have a look at the top(1) display of an otherwise idle
 > > system.  The "%interrupt" column should be zero, even if
 > > it's processing 4000 timer interrupts per second.  As far
 > > as I know, the cpu timer interrupt handler is very light-
 > > weight.
 > 
 > Thank you for the answer. My convern is that with 4 CPUs i get 8000
 > ints/second.  While em generates only about 200 ints/second. As i
 > undertand not all int handlers are the same. Some are heavy and some
 > are light on CPU. So, the question is what is better (better=less CPU
 > time): 8000 ints/sec from timer or 200 ints/sec from NIC?

There's no simple answer to the question.  The best way is
to just try it.  As I wrote, run top(1) while the system is
idle, so only the cpu timer interrupts are active.  If the
"%interrupt" column is zero most of the time, then there
is nothing to worry about at all.

However, if you have a constant non-zero %interrupt value,
you might consider lowering HZ, and you might reconsider
whether polling really has advantages in your situation.
Do you have reasons to believe so?  Remember that the main
purpose of polling is to improve interactivity under very
high network load.  If you're not in such a situation, then
polling probably doesn't buy you much.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"Documentation is like sex; when it's good, it's very, very good,
and when it's bad, it's better than nothing."
-- Dick Brandon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: device polling and weird timer interrupt count from vmstat

[Artem Kuchin]

3) Is timer int really generated on each cpu? Am i really wasting cpu
time on ~4000 ints per second?


4000 ints per second is rather nothing on any modern CPU.
Have a look at the top(1) display of an otherwise idle
system.  The "%interrupt" column should be zero, even if
it's processing 4000 timer interrupts per second.  As far
as I know, the cpu timer interrupt handler is very light-
weight.



Thank you for the answer. My convern is that with 4 CPUs i get 8000 ints/second.
While em generates only about 200 ints/second. As i undertand not all int 
handlers
are the same. Some are heavy and some are light on CPU. So, the question is
what is better (better=less CPU time): 8000 ints/sec from timer or 200 ints/sec 
from NIC?

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

Re: 6.2-STABLE does not lauch 2nd core of Pentium e2160 CPU

[Oliver Fromme]

vermaden <[EMAIL PROTECTED]> wrote:
 > FreeBSD 6.2-STABLE (GENERIC SMP kernel rebuild from today sources) does
 > not launch second core of Pentium Dual Core e2160 CPU, it detects the
 > cores [Cores per package: 2] but it does not launch the second CPU
 > [SMP: AP CPU #1 Launched! <-- this should pop in dmesg but it doesnt]

My guess is that you forgot to include "options SMP" in
your kernel config.  Otherwise, what's the output from
"sysctl kern.smp" on that machine?

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"C++ is to C as Lung Cancer is to Lung."
-- Thomas Funke
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: device polling and weird timer interrupt count from vmstat

[Oliver Fromme]

Artem Kuchin wrote:
 > I enabled device polling in the kernel, in nics and
 > set HZ=1000.

HZ=1000 is the default anyway.  You only need to set it
if you want a value other than 1000.

For example, on my notebook I have set HZ=600 because that
machine often used for various media playback (video).
600 is a multiple of 24, 25 and 30, which are common frame
rates of video files.  Aligning the kernel's scheduling
quantum with the frame rate improves video playback.
On a very fast processor I would probably use HZ=1200,
but mine is only an older single-core.

 > How, when i do
 > 
 > omni2# vmstat -i
 > 
 > i see
 > 
 > interrupt  total   rate
 > irq14: ata0   47  0
 > irq15: ata1   41  0
 > irq28: em0  2268  4
 > irq72: twe058380120
 > cpu0: timer   965994   1995
 > cpu3: timer1  0
 > cpu1: timer1  0
 > cpu2: timer   965857   1995
 > Total1992589   4116

Looks perfectly normal.

 > What i don't understand is why timer rate on each cpu is 1995? I have
 > set it to 1000, not 1995 or 2000. I have seen it showing 2000 on
 > another box.

The timer frequencies are not necessarily the same as the
HZ setting.  They are related, but don't have to be the
same.  It depends on several things, in particular the type
of your processor and sysctl kern.timecounter settings.

There are several formulas, dependencies and requirements
for time counters.  For example, the frequency must be
set so the counter does not roll over in less than about
max(2 msec, 2/HZ sec), which depends on the bit width of
the counter (see src/sys/sys/timetc.h).  On the other
hand, you want a counter which runs as fast as possible,
so you get better precision for time keeping.  For those
reasons the cpu timer can be set to a multiple of HZ.

I've made a quick survery on a few machines around me
(unless otherwise noted, all of these run FreeBSD/i386
6-stable and have the default of HZ=1000):

Pentium III, 800 MHz:
cpu0: timer   1893955760   1999

Xeon 5160, 3000 MHz:
cpu0: timer   243483   1996

Athlon64, 2200 MHz:
cpu0: timer   3964659397960

Athlon64 X2, 2x 2000 MHz, 7-current:
cpu0: timer847083650   2000
cpu1: timer847081624   2000

VIA C3 Nehemiah, 1000 MHz, HZ=250:
irq0: clk  167288669249

 > 3) Is timer int really generated on each cpu? Am i really wasting cpu
 > time on ~4000 ints per second?

4000 ints per second is rather nothing on any modern CPU.
Have a look at the top(1) display of an otherwise idle
system.  The "%interrupt" column should be zero, even if
it's processing 4000 timer interrupts per second.  As far
as I know, the cpu timer interrupt handler is very light-
weight.

 > 4) does twe driver use polling? whay about twa?

No, they don't.  They aren't even NIC drivers.  Currently
polling is only implemented for (some of) the NIC drivers.

 > how to check it in the sources? 

The polling(4) manual page lists all supported devices.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"When your hammer is C++, everything begins to look like a thumb."
-- Steve Haflich, in comp.lang.c++
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: in openpam_load_module(): no pam_unix.so found

[Mike Bristow]

On Mon, Sep 24, 2007 at 09:29:08AM -0400, Victor Star wrote:
> ==- 8< 
> -
> fireball# ldd /usr/lib/pam_unix.so
> /usr/lib/pam_unix.so:
> libutil.so.5 => /lib/libutil.so.5 (0x28167000)
> libcrypt.so.3 => /lib/libcrypt.so.3 (0x28173000)
> libypclnt.so.2 => /usr/lib/libypclnt.so.2 (0x2818b000)
> libpam.so.3 => /usr/lib/libpam.so.3 (0x2818f000)
> fireball# ldd /usr/lib/pam_unix.so.3
> /usr/lib/pam_unix.so.3:
> libutil.so.5 => /lib/libutil.so.5 (0x28167000)
> libcrypt.so.3 => /lib/libcrypt.so.3 (0x28173000)
> libypclnt.so.2 => /usr/lib/libypclnt.so.2 (0x2818b000)
> libpam.so.3 => /usr/lib/libpam.so.3 (0x2818f000)

Hmm. That all looks ok. 

The relevant code inside openpam[1] does something like

dlopen(OPENPAM_MODULES_DIR . "/pam_unix.so.3", RTLD_NOW)

and if that fails, tries

dlopen(OPENPAM_MODULES_DIR . "/pam_unix.so", RTLD_NOW)

Both of these must have failed when su ran.  

It may be worth compiling the following:

: [EMAIL PROTECTED]:~ ; cat dlopentest.c 
#include 
#include 

int
main (int argc, char **argv) {

void *dlh;

dlh = dlopen(argv[1], RTLD_NOW);
if (dlh) {
printf("dlopen %s worked\n", argv[1]);
} else {
printf("dlopen %s failed: %s\n", argv[1], dlerror());
}
return 0;
}
: [EMAIL PROTECTED]:~ ; make dlopentest
cc -O2 -fno-strict-aliasing -pipe -march="pentium3"  dlopentest.c  -o dlopentest
: [EMAIL PROTECTED]:~ ; ./dlopentest /usr/lib/pam_unix.so
dlopen /usr/lib/pam_unix.so worked
: [EMAIL PROTECTED]:~ ; ./dlopentest /usr/lib/pam_unix.so.3
dlopen /usr/lib/pam_unix.so.3 worked
: [EMAIL PROTECTED]:~ ; ./dlopentest /usr/lib/pam_kasjajsk.so
dlopen /usr/lib/pam_kasjajsk.so failed: Cannot open "/usr/lib/pam_kasjajsk.so"
: [EMAIL PROTECTED]:~ ;

this may give you a clue as to why the dlopen failed.  If that
doesn't point at a problem, then recompile su with _openpam_debug
= 1, and setup syslog to log LOG_DEBUG messages somewhere and see
what happens.


[1] assuming a version of FreeBSD suitably similar to the one I
have here, of course.



> 
> ==- 8< 
> -
> 
> As for when it stopped working - the first thing I did is trying to recall if 
> I updated any ports.
> I've even went so far as looking for all files in /usr/ modified within the 
> date range, but no,
> nothing.
> 
> I did update php5 couple days before that. But it still worked for about two 
> days after that.
> And I don't have apache/php opened to outside anyway. Just mail ports and ssh 
> on high port (closed
> it for now for just in case anyway).
> 
> Victor
> 
> >> - 8< -===
> >> su: in openpam_load_module(): no pam_unix.so found
> >> su: pam_start: system error
> >> - 8< -===
> >> 
> >> pam_unix.so is in /usr/lib:
> >> - 8< -===
> >> # ls -l /usr/lib/pam_unix*
> >> lrwxr-xr-x  1 root  wheel 13 Sep 25  2006 /usr/lib/pam_unix.so -> 
> >> pam_unix.so.3
> >> -r--r--r--  1 root  wheel  10240 Feb 19  2007 /usr/lib/pam_unix.so.3
> >> # file /usr/lib/pam_unix.so
> >> /usr/lib/pam_unix.so: symbolic link to `pam_unix.so.3'
> >> - 8< -===
> 
> > First, this is how a problem should be described, great work.
> 
> > When openpam can't load a module, it also print's the 'not found' message.
> > With 'ldd /usr/lib/pam_unix.so.3' you can see if all the libraries that
> > it needs are in place. On my systems it give's the following output:
> 
> > $ ldd /usr/lib/pam_unix.so.3 
> > /usr/lib/pam_unix.so.3:
> > libutil.so.5 => /lib/libutil.so.5 (0x28169000)
> > libcrypt.so.3 => /lib/libcrypt.so.3 (0x28175000)
> > libypclnt.so.2 => /usr/lib/libypclnt.so.2 (0x2818d000)
> > libpam.so.3 => /usr/lib/libpam.so.3 (0x28191000)
> 
> >> - 8< -===
> >> Sep 18 11:11:37 xx su: BAD SU  to root on /dev/ttyp3
> >> Sep 18 11:13:46 xx sshd[45047]: Bad protocol version identification 
> >> '\377\364\377\375\006quit' from 
> >> Sep 18 11:15:08 xx sshd[45056]: Received disconnect from  >> here>: 2: Bad packet length 710099706.
> >> - 8< -===
> 
> > The first line is probably the result of the broken pam_unix.so, the
> > other two lines look to me as ssh bruteforce attacks.
> 
> > But, when did it stopped working. Did you tried to update the world or 
> > something like that?
> 
> 
> 
> -- 
> Best regards,
>  Victor  
> 
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTE

Re: device polling and weird timer interrupt count from vmstat

[Artem Kuchin]

Nikos Vassiliadis wrote:

On Tuesday 25 September 2007 12:13, Artem Kuchin wrote:

I have dual CPU with HT. If i turn on HT (and it does help in my
case) it shoud 2000 int x4 = 8000 ints per second. SO, i have saved
200 int/second from NIC and got myself 8000 ints/second from timer.


This kind of load(200intrs/s) earns nothing from polling.


Did i
really win anything? I wish there were some good explanation on this.


It would make a difference for let's say 8000 - 1 interrupts/sec.
You should read polling(4). It explains a lot:)


Yes, i have read the man for polling. However, it does not contain 
info on when it worth enabling. From this point of view it seems like
if i have 8CPU server an a NIC with 8000 ints/sec when i enable polling 
with HZ=1000 i get


about 30 ints/sec from NIC
about 16000 ints from NIC

So, we were at 8000 ints a second and now we are at 16000 ints/second.
Is it worth in this case? It seems  like enabling polling on really multi
cpu computers never worth it. I think there is a mistake in my logic
here. It just canot be like this.

any thoughts?

--
Regards,
Artem

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

Re: device polling and weird timer interrupt count from vmstat

[Nikos Vassiliadis]

On Tuesday 25 September 2007 12:13, Artem Kuchin wrote:
> I have dual CPU with HT. If i turn on HT (and it does help in my case)
> it shoud 2000 int x4 = 8000 ints per second. SO, i have saved 200
> int/second from NIC and got myself 8000 ints/second from timer. 

This kind of load(200intrs/s) earns nothing from polling.

> Did i 
> really win anything? I wish there were some good explanation on this.

It would make a difference for let's say 8000 - 1 interrupts/sec.
You should read polling(4). It explains a lot:)

HTH

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

Re: device polling and weird timer interrupt count from vmstat

[Artem Kuchin]

Nikos Vassiliadis wrote:

On Monday 24 September 2007 20:58, Artem Kuchin wrote:

What i don't understand is why timer rate on each cpu is 1995? I
have set it to 1000, not 1995 or 2000. I have seen it showing 2000
on another box.
So
1) why not 1000?



I can only make assumptions about the doubling, and I don't want to.
FreeBSD is not a RTOS and some milliseconds variation is
understandable. 


2) if it is supposed to be doubled (why?) when why not 2000?


I can only make assumptions about the doubling, and I don't want to.
FreeBSD is not a RTOS and some milliseconds variation is
understandable. 


3) Is timer int really generated on each cpu?


Apparently, why do you doubt it?


Am i really wasting cpu
time on ~4000 ints per second?


You can lower it you know, if you feel that you are waisting
that much resources. Ofcourse you'll break your traffic flow
that way, since latency will increase.

You seem very upset about it, are you sure you want to use
polling(4)? it uses much more resources than interrupts.


I am not upset about all this. But i want to understand why is it
doubled. Because when i turn on polling i think that timer freq supposed
to be just like i set HZ. However, actually, i am now 
thinking about another issue.


I have dual CPU with HT. If i turn on HT (and it does help in my case)
it shoud 2000 int x4 = 8000 ints per second. SO, i have saved 200 int/second 
from
NIC and got myself 8000 ints/second from timer. Did i really win anything?
I wish there were some good explanation on this.



4) does twe driver use polling? whay about twa? how to check it in
the sources?


Polling is only used on some network interface drivers. Polling(4)
does not offer generic device-polling facilities.

By the way, you know your post has an aggressive sense, don't you?
Please don't do this when asking questions and want replies.


Hmm.. Really? I didn't mean it, i was just trying to me as short and as
technical as possible. Alright, i'll give a though on how to be more..
polite, i guess.

--
Regards,
Artem

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

6.2-STABLE does not lauch 2nd core of Pentium e2160 CPU

[vermaden]

FreeBSD 6.2-STABLE (GENERIC SMP kernel rebuild from today sources) does
not launch second core of Pentium Dual Core e2160 CPU, it detects the
cores [Cores per package: 2] but it does not launch the second CPU
[SMP: AP CPU #1 Launched! <-- this should pop in dmesg but it doesnt]

How can I help you to make this work?

# uname -a
FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Sep 24 12:58:17 CEST 2007   
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM  i386

# dmesg
Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-STABLE #0: Mon Sep 24 12:58:17 CEST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Genuine Intel(R) CPU2160  @ 1.80GHz (1800.01-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6f2  Stepping = 2
  
Features=0xbfebfbff
  Features2=0xe39d,CX16,,>
  AMD Features=0x2010
  AMD Features2=0x1
  Cores per package: 2
real memory  = 106496 (1015 MB)
avail memory = 1028931584 (981 MB)
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pci0:  at device 2.0 (no driver attached)
pci0:  at device 27.0 (no driver attached)
uhci0:  port 0xd400-0xd41f irq 23 at device 29.0 
on pci0
uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xd480-0xd49f irq 19 at device 29.1 
on pci0
uhci1: [GIANT-LOCKED]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xd800-0xd81f irq 18 at device 29.2 
on pci0
uhci2: [GIANT-LOCKED]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3:  port 0xd880-0xd89f irq 16 at device 29.3 
on pci0
uhci3: [GIANT-LOCKED]
usb3:  on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0:  mem 0xfe9f7c00-0xfe9f7fff 
irq 23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4:  on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib1:  at device 30.0 on pci0
pci1:  on pcib1
rl0:  port 0xe800-0xe8ff mem 0xfebffc00-0xfebffcff 
irq 19 at device 0.0 on pci1
miibus0:  on rl0
rlphy0:  on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:90:cc:de:5e:0c
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0xc480-0xc487,0xc400-0xc403,0x8f0-0x8f7,0x8f8-0x8fb,0xbc00-0xbc0f irq 18 at 
device 31.1 on pci0
ata2:  on atapci0
ata3:  on atapci0
atapci1:  port 
0xd080-0xd087,0xd000-0xd003,0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at 
device 31.2 on pci0
ata4:  on atapci1
ata5:  on atapci1
pci0:  at device 31.3 (no driver attached)
acpi_button0:  on acpi0
ppc0:  port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on 
acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
pmtimer0 on isa0
orm0:  at iomem 0xc-0xcafff on isa0
ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata1 at port 0x170-0x177,0x376 irq 15 on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 1800011043 Hz quality 800
Timecounters tick every 1.000 msec
acd0: CDROM  at ata2-slave PIO4
ad8: 152627MB  at ata4-master SATA150
Trying to mount root from ufs:/dev/ad8s1a

Regards
vermaden

--
Fajne i smieszne. Zobacz najlepsze filmiki!

>>> http://link.interia.pl/f1bbb

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-sta

Re: device polling and weird timer interrupt count from vmstat

[Nikos Vassiliadis]

On Monday 24 September 2007 20:58, Artem Kuchin wrote:
> > What i don't understand is why timer rate on each cpu is 1995? I have
> > set it to 1000, not 1995 or 2000. I have seen it showing 2000 on
> > another box.
> > So
> > 1) why not 1000?


I can only make assumptions about the doubling, and I don't want to.
FreeBSD is not a RTOS and some milliseconds variation is understandable.

> > 2) if it is supposed to be doubled (why?) when why not 2000?

I can only make assumptions about the doubling, and I don't want to.
FreeBSD is not a RTOS and some milliseconds variation is understandable.


> > 3) Is timer int really generated on each cpu?

Apparently, why do you doubt it?

> > Am i really wasting cpu 
> > time on ~4000 ints per second?

You can lower it you know, if you feel that you are waisting
that much resources. Ofcourse you'll break your traffic flow
that way, since latency will increase.

You seem very upset about it, are you sure you want to use
polling(4)? it uses much more resources than interrupts.

> > 4) does twe driver use polling? whay about twa? how to check it in
> > the sources?

Polling is only used on some network interface drivers. Polling(4)
does not offer generic device-polling facilities.

By the way, you know your post has an aggressive sense, don't you?
Please don't do this when asking questions and want replies.
Such technical comments are not useful to anybody.

HTH

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