Kazutaka YOKOTA wrote:
> The PS/2 mouse generates interrupt when /dev/psm0 is open and
> the user moves the mouse.
>
> If you are running moused or X when you suspend the system, /dev/psm0
> is left open and might generate interrupts. I think modern motherboard
> BIOSes have a setup menu that l
>> OK. Probably `slept 00:00:00 - 00:00:40' problem was caused by PS/2
>> mouse, I think. Do we need something to do with psm on suspending as
>> well as resuming?
>
>Im not sure anything needs to be done for PS/2.. check out these
>results..
The PS/2 mouse generates interrupt when /dev/psm0 is
Ever since we started using binutils with the move to elf we've been
using linker scripts with library search paths. The genscripts.sh
source from binutils is giving us at least one bogus path all the
time, and the presence of a not-always-appropriate-path (/usr/lib)
the rest of the time. I'd like
Mitsuru IWASAKI wrote:
> OK. Probably `slept 00:00:00 - 00:00:40' problem was caused by PS/2
> mouse, I think. Do we need something to do with psm on suspending as
> well as resuming?
Im not sure anything needs to be done for PS/2.. check out these
results..
> > > > ed1: irq 3 at device 9.0
I've resynced the source tree and updated my big-fat patch again.
http://www.backplane.com/FreeBSD4/
This patch is the same as the last one, but:
* should patch clean to the tree as of tonight
* fixes an additional bug in swapblock management. Certain
I have some other changes planned so I'm not going to re-roll the port
yet, but between now and then I've put up a version of mergemaster that
knows about the $FreeBSD tags at
http://freebsd.simplenet.com/mergemaster-1.25.
Enjoy,
Doug
To Unsubscribe: send mail to [EMAIL PROTECTED]
wit
>Under normal Circumstances, the communication is Ok between all three
>machines, but sometimes the ethernet interface in the main machine
>(the 8139) wedges up. I cannot ping any other host. The only solution
>is taking the interface down and up again:
It hangs when it gets an rx fifo overrun.
Poul-Henning fixed (without knowing) a bug in the fd driver (that must
have sneaked in when changing something to do with dev_t's.
revision 1.156
date: 1999/08/28 08:10:13; author: phk; state: Exp; lines: +4 -1
Initialize dev->si_bsize*, the floppy driver doesn't use dsopen().
The panic is
"Mark S. Reichman" wrote:
>
> Another reason less lawsuits of this type are tried in Europe
> is because the loser pays all court costs.
> In the US a person will name everyone and anyone
> remotely associated with the supposed wrong doing in hopes of a
> big payoff. Each person must then hire a
> I haven't had much feedback on this code so would like to hear how well it
> works for people. Unfortunately I can't correct any bugs at the moment
> until I get my computer (which is at this moment being unloaded from a
> plane at the airport :-) set up and back on the net, but I tested it a
>
On Sat, 28 Aug 1999, Doug wrote:
> Something that came up recently, both for me and someone else on the list
> is the ability to have DES libs in the system and still use MD5 passwords
> as the default. I have no idea how difficult this would be to do, but if
> someone has it in mind here's
Mark Murray wrote:
>
> Hello All!
>
> I have got a $#|7load of crypto updates that I'd like to commit; they
> are all over my tree, so let me describe what they do, and anyone who
> wishes to review any part of them can get the appropriate bits.
Something that came up recently, both for
On Fri, 27 Aug 1999, Nick Hibma wrote:
>Let me guess, the kernel panic ends up in a division by zero error when
>writing to floppy in _qdivrem.
Yep, this would be it.
On Sat, 28 Aug 1999, Brian F. Feldman wrote:
>That sounds like it could have just been fixed by phk. If it's not that and
>is the
Hi,
I get some strange networking results with my RealTek 8139 card. I
don't know how long these problems exist in the kernel, because they
only showed up after some change in my network setup.
I got a third PC for testing and now needed a hub to connect all my
PCs together. I used to have an UT
> On Sat, 28 Aug 1999, Mark Murray wrote:
>
> > 3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does
> > not hurt anything else. This will go into src/crypto.
>
> You might also like to turn on the x86 assembler code (it's only for
> pentiums, I think, so would have to be a non
On Sat, 28 Aug 1999, Mark Murray wrote:
> 3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does
> not hurt anything else. This will go into src/crypto.
You might also like to turn on the x86 assembler code (it's only for
pentiums, I think, so would have to be a non-default optio
Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> schizo# make
> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
>-nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h -
schizo# make
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h -elf
../../pci/if_tl.c
../../pci/if_tl.c:226: miib
Jordan, Satoshi,
Just a reminder: I have *no* objection to the ports tree being used to
build packages of the documentation, as long as the maintenance of those
ports is assigned to individuals, and not the FDP (and, more specifically,
me).
However, I think that another mechanism, one that's w
Hello All!
I have got a $#|7load of crypto updates that I'd like to commit; they
are all over my tree, so let me describe what they do, and anyone who
wishes to review any part of them can get the appropriate bits.
1) Revisit the way libscrypt/libdescript get built. This is partially
based on Br
On Fri, 27 Aug 1999, Adam Wight wrote:
> > > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null
> > > *** Error code 1
>
> > Probably it consequences of recent dd changes...
Sorry about that! Instead of relying on the kernel being newer than the world
and haveing the new ioctl FIODTYPE, dd
Let me guess, the kernel panic ends up in a division by zero error when
writing to floppy in _qdivrem.
Haven't had time to script that panic, but will do next week.
Nick
On Fri, 27 Aug 1999, Adam Wight wrote:
> > > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null
> > > *** Error code
22 matches
Mail list logo