Install 6.0-BETA2 on qemu PANIC

2005-08-25 Thread prime
Hi all,
When I install 6.0-BETA2 on qemu,it PANICs.I don't know whether it is
qemu's bug or 6.0-BETA2's.Here is output of "trace":

Tracing pid 26 tid 100026 td 0xc1740300
kdb_enter(c0856274) at kdb_enter+0x2b
panic(c0870f1a,c72d4000,407ea84d,1,0) at panic+0x127
vm_fault(c146,c72d4000,2,0,c1740300) at vm_fault+0x1e0
trap_pfault(c856fc44,0,c72d4800) at trap_pfault+0x137
trap(8,28,28,c72d4800,c1703600) at trap+0x341
calltrap() at calltrap+0x5
--- trap 0xc,eip=0xc04d2c98,esp=0xc856fc84,ebp=0xc856fca4 ---
ata_pio_read(c1843c80,800,129,c17f6dc0,c1805000) at ata_pio_read+0x78
ata_end_transaction(c1843c80) at ata_end_transaction+0x8b8
ata_interrupt(c1703600) at ata_interrupt+0xdf
ithread_loop(c170f800,c856fd38,c170f800,c061f854,0) at ithread_loop+0x11c
fork_exit(c061f854,c170f800,c856fd38) at fork_exit+0xa0
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1,eip=0,esp=0xc856fd6c,ebp=0 ---
 

-- 
Three passions, simple but overwhelmingly strong, have governed my life: 
the longing for love, the search for knowledge, and unbearable pity for 
the suffering of mankind.
 -Bertrand Russell
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE:Install 6.0-BETA2 on qemu PANIC

2005-08-25 Thread prime
and more information about the panic,it said:

panic:vm_fault: fault on nofault entry, addr: c72d400

-- 
Three passions, simple but overwhelmingly strong, have governed my life: 
the longing for love, the search for knowledge, and unbearable pity for 
the suffering of mankind.
 -Bertrand Russell
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Re: nagios and freebsd threads issue : help please ...

2005-08-25 Thread Sergey Babkin
>> > This is funny, because nagios apparently runs properly on Linux, HPUX,
>> > Solaris, Irix, AIX and Tru64. To me that seems to indicate that Nagios

This does not neccessary mean that it _really_ works.
There might be a race involved that usually ends up
lucky on these systems.

>> > is very portable indeed and that the BSD fellows somehow botched it. I
>> > might be wrong, but...
>> 
>> Just because it works doesn't make it standards conforming.
>> 
>> Maybe there's some simple extension that can be implemented to help
>> the situation.
>
>It seems the main problem of the Nagios developper seems to be they
>would need to rewrite a big part of their current implementation.
>I'm not sure however this is mandatory.  I wonder if the so-told
>pthread_atfork() handler wouldn't be a quick solution to address the
>problem.  Sorry if it's dumb.

I'd even say that it's the proper correct solution. 
This probably should me made a part of "how to write thread-safe libraries":
register pthread_atfork() function that would free every possible
mutex and conditional in the library.
And clean up the other state too.

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


NFS - MNT_NOEXEC [WAS Re: MNT_NOEXEC on root filesystem with diskless PXE boot?]

2005-08-25 Thread Sten Spans

On Thu, 31 Mar 2005, Colin Percival wrote:


Tom Alsberg wrote:

Perhaps this should go to -STABLE, I just couldn't be sure.


It will get more attention on freebsd-stable@, so I'm CCing that list.


We are trying out FreeBSD 5.4-PRERELEASE on diskless clients.  I
noticed one problem, being that when setting the LD_LIBRARY_PATH
(or for that matter, LD_PRELOAD, and LD_LIBMAP_DISABLE) environment
variables, nothing will run, as /libexec/ld-elf.so.1 complains:

Cannot execute objects on /

According to the sources, this was added in 5.4, and will happen
if / is mounted noexec.


Yes, that's quite correct -- although I can't imagine how a bug which
caused / to be labelled as "noexec" managed to avoid causing major
problems until now.

I don't know anything about NFS, but hopefully someone on -stable
will be able to work out what's going on from the rest of your
email (quoted below).

Colin Percival


In this case, / is mounted by the BTX PXE loader over NFS (from a
FreeBSD 5.3 server, right now).  "mount" does not show the noexec
flag.  However, with the attached little C program I verified that
statfs really returns this flag (0x0006).

Now, I see that on FreeBSD 5.3 diskless clients this flag is also
returned on / - just it happened that nobody looked at it until
the change in rtld.c of FreeBSD 5.4:

if (fs.f_flags & MNT_NOEXEC) {
_rtld_error("Cannot execute objects on %s\n", fs.f_mntonname);
close(fd);
return NULL;
}

I didn't yet understand (didn't check much) - why does statfs report
the MNT_NOEXEC flag on the / filesystem (and only the / filesystem,
when it's mounted from NFS by the bootloader - not any other
NFS filesystems)?  BTW, this happens also with NetApp as the NFS
server - just to rule out any possibility of relation here.

  Ideas appreciated,
  -- Tom





#include 
#include 
#include 
#include 


int main(int argc, char *argv[])
{
if (argc != 2) {
fprintf(stderr, "invalid number of arguments");
return -1;
}

struct statfs stbuf;

if (statfs(argv[1], &stbuf) != 0) {
perror("fstatfs");
return -1;
}

printf("FLAGS: 0x%08X\n", stbuf.f_flags);
if (stbuf.f_flags & MNT_NOEXEC)
printf("MNT_NOEXEC\n");

return 0;
}


I've managed to reproduce this with a simple:

www1# gcc -o noexec noexec.c
www1# umount /buildroot/
www1# mount nfs3:/export/vol1/build/BUILDROOT-WWW /buildroot
www1# ./noexec /buildroot/
exec
www1# umount /buildroot/
www1# mount -o -r=32768 nfs3:/export/vol1/build/BUILDROOT-WWW /buildroot
www1# ./noexec /buildroot/
noexec
www1#

Pretty funky shit this :).

PR: 85268
http://www.freebsd.org/cgi/query-pr.cgi?pr=85268

Anybody care to take a deeper look ?

--
Sten Spans

"There is a crack in everything, that's how the light gets in."
Leonard Cohen - Anthem
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Vertikal and Horizontal Scroll of (mighty) mice

2005-08-25 Thread Arne Schwabe
Hi,

I just got myself myself a shiny white Mighty Mouse from Apple.

I now have the Problem that Wheel if the scrolling to left and right.
I fixed this by teaching ums.c to prefer WHEEL over Z but it would be
nice to support both wheel and z axis scrolling. I checked the mouse(4)
but the dataformat there does not even support a forth axis. Hacking
ums.c to map z axis to buttons 7 and 8 would be possible, but not a
clean solution. Another Option would be to add a z2 axis or something
tothe SYSMOUSE format.

What are your opinion?

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


Re: Vertikal and Horizontal Scroll of (mighty) mice

2005-08-25 Thread Seán C . Farley

On Thu, 25 Aug 2005, Arne Schwabe wrote:


Hi,

I just got myself myself a shiny white Mighty Mouse from Apple.

I now have the Problem that Wheel if the scrolling to left and right.
I fixed this by teaching ums.c to prefer WHEEL over Z but it would be
nice to support both wheel and z axis scrolling. I checked the
mouse(4) but the dataformat there does not even support a forth axis.
Hacking ums.c to map z axis to buttons 7 and 8 would be possible, but
not a clean solution. Another Option would be to add a z2 axis or
something tothe SYSMOUSE format.

What are your opinion?


I have an MX1000[1] from Logitech with many buttons and a wheel.  The
wheel can scroll up and down and "click" left and right.  The PS/2
driver did not support enough of its buttons which caused moused to not
see all of the buttons.  I recommend looking at this first link since it
details one way of setting up a mouse with many buttons.

I used the ums driver, but I had to enable more buttons in the
driver[2].  You may need that patch to use it fully, but I do not know
how many logical buttons you have.

In X, you will need to configure the mouse with xmodmap.  Here is my
line to my mouse to do most of what I want.  It moves the paste action
to the button above the wheel instead of the click of the wheel.

xmodmap -e "pointer = 1 7 3 9 10 6 2 8 4 5 11 12"

Here is the mouse in xorg.conf:
Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/ums0"
Option  "Buttons" "12"
Option  "Emulate3Buttons" "false"
Option  "ZAxisMapping" "9 10"
EndSection

Seán
  1. http://floam.sh.nu/index.xhtml?page=guides§ion=mx1000
  2. http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/83353
--
[EMAIL PROTECTED]___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"