A current kernel just built after a current make world
comes up with this and stops booting:
Programming 24 pins in IOAPIC #0
AP #1 (PHY# 12) failed!
panic y/n [y]
If I type n the kernel boots fine.
doing mptable cause a panic though
Thanks
Manfred
==
|| [
On Mon, 22 May 2000, Matthew Dillon wrote:
> :> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> :> beans, I mean PS/2 mice which fall victim to this new problem:
> :
> :> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
> :
> I got an email from Bori
On Mon, 22 May 2000, Stephen J. Roznowski wrote:
> I'm attempting to update my -current system from mid-April, and
> I'm getting the following error:
make world first, or build the new binutils.
Kris
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <
I'm attempting to update my -current system from mid-April, and
I'm getting the following error:
make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx
Warning: Object directory not changed from original /usr/src/sys/compile/ISTARI
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wr
At 15:49 22-05-2000 +0400, Valeriy E. Ushakov wrote:
>I wish this page has less FUD about Unicode. Reference to Unicode
>being controlled by Microsoft is a prominent example.
It was true when it was written. It is a very old page: I completely forgot
it was still there. The situation with Unicod
While it's nice to supposedly have narowed this down to the SMP cleanup,
that doesn't make those of us who are running single processor machines
very cofident that the bug's been found. Here's my guess: there may be
something interupt driven related to the SMP stuff, but there's also
something wr
On 22-May-00 Stephane E. Potvin wrote:
> Try applying the patches in the following PR. I'm not sure they will still
> apply
> cleanly but it should fix your problem.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=15841
I'll look at this in a bit. I'm about ready to rewrite BTX all in
.code16 a
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Samuel Tardieu
> Sent: Monday, May 22, 2000 4:02 PM
> To: Stephane E. Potvin
> Cc: [EMAIL PROTECTED]
> Subject: Re: buildworld broken in sys/boot/i386/btx/btx
>
>
> On 22/05, Stephane E. Potvin wrote:
>
> I don't know if the mouse problems are related or not, did anyone have
> jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
> kernels then two weeks old for 4.0, and four weeks old for 5.0).
I did not have jumpy-mouse problems on my SMP system (probably should
have
On 22/05, Stephane E. Potvin wrote:
| Try applying the patches in the following PR. I'm not sure they will still
| apply cleanly but it should fix your problem.
They don't apply cleanly, and I have to leave. But I would rather understand
why there is a failure in the first place, and why other p
Try applying the patches in the following PR. I'm not sure they will still
apply
cleanly but it should fix your problem.
http://www.freebsd.org/cgi/query-pr.cgi?pr=15841
--
Stephane E. Potvin
InnoMediaLogic Inc. -- http://www.multichassis.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
> Unless your mouse died of old age. The PS/2 mouse I had been using for
> quite some time started to behave exactly like yours at some point last
> year. I avoided replacing it for a long time, since I couldn't find another
> mouse with a long enough cord.
I tried several other mice. It's a s
cvsup'ed 1.5 hours ago
===> sys/boot/i386/btx/btx
(cd /usr/objsrc/src/sys/boot/i386/btx/btx; m4 btx.m4 btx.s) | as -o btx.o
{standard input}: Assembler messages:
{standard input}:136: Warning: using `%eax' instead of `%ax' due to `l' suffix
{standard input}:138: Warning: using `%eax' instead o
I saw it once or twice in the last couple of weeks, when I'm kicking the
hell out of the CPU (ie compiling something)
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 2476772
On a build of 4.0 CVSup'd today before noon Eastern time.
===> usr.bin/kdump
make: don't know how to make /usr/obj/usr/src/i386/usr/include/machine/random.h. Stop
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
To Unsubscribe: send mail to [E
I stopped using moused sometime during 4.0-current as a result of this.
It ocasionally froze, moved randomly around the screen, clicked without
being touched, and yes, got extreamly jumpy. The hardware's rock solid,
and once I ditched moused and read the device directly, life went back to
normal.
:> > kernels then two weeks old for 4.0, and four weeks old for 5.0).
:>
:> Yes. This started long before the SMP cleanup MFC. I'm running 4-stable.
:
:Let me second this. I have been unable to use moused on my laptop
:(Sony VAIO 505TR with Versapad) since syscons changes went in right
:
Matthew Dillon wrote:
> :> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
> Now, I must say, that there is no way we are going to add that hack back
> in ... it was a real mess and is simply not worth it, and when we
> move to the interrupt threading model we ca
Frank Mayhar stated:
> Matthew Dillon wrote:
> > I don't know if the mouse problems are related or not, did anyone have
> > jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
> > kernels then two weeks old for 4.0, and four weeks old for 5.0).
>
> Yes. This started l
Matthew Dillon wrote:
> I don't know if the mouse problems are related or not, did anyone have
> jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
> kernels then two weeks old for 4.0, and four weeks old for 5.0).
Yes. This started long before the SMP cleanup MFC.
:
:> No, I don't mean rodents who've nibbled on chocolate-covered expresso
:> beans, I mean PS/2 mice which fall victim to this new problem:
:
:> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
:
:I saw this happen once, during a period heavy disk and serial
:activity.
:
:-GAW
Hi all,
Im also seeing this messages in FreeBSD 3.4 Release:
> psmintr: out of sync (00c0 != ).
> psmintr: out of sync (0040 != ).
> psmintr: out of sync (0080 != ).
It doesnt even have X installed, nor APM enabled (BIOS & KERNEL) its a smtp,
pop3 & DNS dedicated server, I have
< said:
> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> beans, I mean PS/2 mice which fall victim to this new problem:
> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
I saw this happen once, during a period heavy disk and serial
activity.
-GAWoll
On Mon, 22 May 2000, Jordan K. Hubbard wrote:
> Well, in my case it happens without any such things going on. More to
> the point, it *never* works entirely right, from the moment I boot the
> machine to the moment I turn it off. The mouse is always jumpy now,
> and it's the same mouse I've bee
> On May 21/2000, Clive Lin wrote to -current&-i18n:
> > > The only way i found to link motif programs is by using
> > >
> > > http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz
> >
> >This seems the solution of wc* routines in FreeBSD.
> >
> >Could any one tell us, is this project dead ?
>Try flags 0x04 on device psm.
>
>This undocumented option fixed my PS/2 IntelliMouse clone that has a
>wheel (which is also the center button).
As you have not given details on your problem and mouse,
I don't understand why this flag solved your problem...
That flag simply sets the mouse's reso
Arun Sharma wrote:
> There is a minor nit about the permissions on /dev. It was not readable
> by others. So ps wouldn't work, because it could not open /dev/null.
I noticed this when I tried a home-built 5.0 snapshot (/dev was mode
0700), I didn't report it though because I thought it might hav
Stijn Hoop <[EMAIL PROTECTED]> wrote:
> I do have /dev/psm0 in my XF86Config. You're saying it is better to
> use /dev/sysmouse, Protocol moused?
If you have moused running, set XF86Config to /dev/sysmouse, protocol
"MouseSystems".
--
Christian "naddy" Weisgerber [EMAI
On May 21/2000, Clive Lin wrote to -current&-i18n:
> > The only way i found to link motif programs is by using
> >
> > http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz
>
>This seems the solution of wc* routines in FreeBSD.
>
>Could any one tell us, is this project dead ?
Last I knew, D
On Mon, May 22, 2000 at 13:26:22 +0200, Thomas Runge wrote:
> Look here: http://www.whizkidtech.net/i18n/wc/
I wish this page has less FUD about Unicode. Reference to Unicode
being controlled by Microsoft is a prominent example. As for the list
of problems with Unicode given on that page - all
World and kernel of approx 1100 GMT Sunday 21st May:
Console (re-typed):
ad0: 1999MB [4334/15/63] at ata0-master using UDMA33
ad1: 499MB [1083/15/63] at ata0-slave using UDMA33
Mounting root from ufs: /dev/ad0s1a
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x2a6
f
Clive Lin wrote:
> Could any one tell us, is this project dead ?
> Will this be in the src/ ?
> Or still in long-long beta (even pre-alpha ?) testing.. ?
> Or .. ?
Look here: http://www.whizkidtech.net/i18n/wc/
--
Tom
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-c
Try flags 0x04 on device psm.
This undocumented option fixed my PS/2 IntelliMouse clone that has a
wheel (which is also the center button).
Bug Kazu as to why this isn't documented in LINT.
"Jordan K. Hubbard" wrote:
>
> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> b
*
$B!!(B
$B"'"$"'"$!V(B $B?7Ce>pJs%M%C%H%o!<%/%5!<%S%9(B $B!WBh(B5/22$B9f"'"$"'"$(B
*
$BEv2q0w$NJ}!"$^$?$O2?$i$+$N7A$G%3%s%?%/%H$d$4>R2pEy$N$"$C$?J}$K!"(B
$B:G?7>pJs$r$*CN
On Sun 2000-05-21 (23:35), Arun Sharma wrote:
> I upgraded my 4.0-release laptop to 5.0-current today and my xe0 was
> recognized by the driver and everything was great.
>
> There is a minor nit about the permissions on /dev. It was not readable
> by others. So ps wouldn't work, because it could
Just one more "problem" report:
I see those messages, however I do not have any problems mousing afterwards.
I'm using a switchview, which at least resets the mouse when I switch.
On Sun, May 21, 2000 at 08:41:57PM -0700, Mike Smith wrote:
> > Um, if you don't see the above message but see errat
> > options PSM_HOOKRESUME
> > options PSM_RESETAFTERSUSPEND
>
> They compile and boot fine. I'll let you know in a day or two if this
> stops the crazy mouse syndrome. For what it's worth, I've seen this
> both before and after a suspend/resume.
I doubt that this will help me since the PS/2 m
Nope!
> >May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
> >
> >I've seen it for the last few weeks and can only think that something
> >must be stomping on the psm driver now (or the driver is missing
> >interrupts for reasons of its own). Anyone else seeing this?
>
> Do yo
> Jonathan Hanna wrote:
> > Yes, recently on 4.0-stable, though provoked by unplugging and
> > replugging in the mouse. It did not recover. This I thought
> > sounded like a PR on the mouse being dead after a wakeup
> > from sleep mode.
>
> Come to think of it, I do use a KVM switch, but this usu
39 matches
Mail list logo
