Re: CURRENT instability
My old K6-2 laptop has this problem and the patch seemed to fix the crashes that
I was experiencing under almost minimal load. The down side is that it also
brought me a pccard or DEVFS problem so no network. Of course that could have
been caused by out-of-sync kernel and sources due to all the crashes and the
fact that I had to build the patched kernel on an up-to-date Current desktop and
install it on the laptop, but of course with the laptop KERNCONF.
Has this or another fix been committed?
Thanks,
ed
Quoting Dag-Erling Smorgrav [EMAIL PROTECTED]:
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Try this workaround (apply with 'patch -l'):
Here's a better workaround. Revert the previous patch and apply this
one:
Index: npx.c
===
RCS file: /home/ncvs/src/sys/i386/isa/npx.c,v
retrieving revision 1.93
diff -u -r1.93 npx.c
--- npx.c 2001/03/19 00:28:04 1.93
+++ npx.c 2001/03/19 20:28:55
@@ -456,7 +456,7 @@
}
npxinit(__INITIAL_NPXCW__);
-#ifdef I586_CPU
+#ifdef I586_CPU_DOES_NOT_WORK
if (cpu_class == CPUCLASS_586 npx_ex16 npx_exists
timezero("i586_bzero()", i586_bzero)
timezero("bzero()", bzero) * 4 / 5) {
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
---
The illiterate of the 21st century will not be
those who cannot read and write,
but those who cannot learn, unlearn and relearn.
--Alvin Toffler
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
"Edwin L. Culp" [EMAIL PROTECTED] writes: My old K6-2 laptop has this problem and the patch seemed to fix the crashes that I was experiencing under almost minimal load. The down side is that it also brought me a pccard or DEVFS problem so no network. Uh, no. There's no way this patch can affect the functionality of your network adapter, and network interfaces don't care about DEVFS. Has this or another fix been committed? No, Certain People [tm] are opposed to it, though it's not clear why. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
Quoting Dag-Erling Smorgrav [EMAIL PROTECTED]: "Edwin L. Culp" [EMAIL PROTECTED] writes: My old K6-2 laptop has this problem and the patch seemed to fix the crashes that I was experiencing under almost minimal load. The down side is that it also brought me a pccard or DEVFS problem so no network. Uh, no. There's no way this patch can affect the functionality of your network adapter, and network interfaces don't care about DEVFS. One of the error messages was that card0 didn't exist in /dev I'm going to patch the kernel again and try to sync everything with a new world and see what happens. Thanks, ed Has this or another fix been committed? No, Certain People [tm] are opposed to it, though it's not clear why. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
"Edwin L. Culp" [EMAIL PROTECTED] writes: One of the error messages was that card0 didn't exist in /dev That's pccard stuff, not your network driver. Did you check to see that the pccard bridge was probed and attached? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
Quoting Dag-Erling Smorgrav [EMAIL PROTECTED]: "Edwin L. Culp" [EMAIL PROTECTED] writes: My old K6-2 laptop has this problem and the patch seemed to fix the crashes that I was experiencing under almost minimal load. The down side is that it also brought me a pccard or DEVFS problem so no network. Uh, no. There's no way this patch can affect the functionality of your network adapter, and network interfaces don't care about DEVFS. Has this or another fix been committed? No, Certain People [tm] are opposed to it, though it's not clear why. I managed to get things in sync enough to get the network working. Now I'm making world, runing X and doing several port updates that have been on hold since the begining of February, all at the same time. Without your patch it would have crashed within the first couple of minutes but with it, it's just chugging along like a happy little K6-2 300, slow but maybe on its way to being sure again. Thanks for coming up with such a simple and effective solution. I was almost ready to retire this for a Dell 4000e that everyone is talking about. But as someone else said, first I would prefer to have a little more consulting money coming in:-) It would really be nice to have this committed, if it doesn't break anything, to not have to be patching every time. Thanks again, ed DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On Mon, 19 Mar 2001, Pierre Beyssac wrote: On Mon, Mar 19, 2001 at 08:30:12AM +0100, Pascal Hofstee wrote: AMD K6-2 350 I noticed the vague stack smashes posting earlier ... and i think it's very likely this is the same bug Same here, random crashes -- AMD K6-2 300; no panic, no crash dump, just a complete system freeze if you happen to use too much CPU. I had to temporarily revert to an older kernel. Another "data point". It was happening here as well on a Pentium 200/MMX. The crash occurred, almost everytime, in a bcopy called from vm_fault according to the kernel debugger (on the rare occassions I could still use it). Whenever I couldn't use the debugger, the Instruction pointer was usually 08:. I stuck an old P-III 800MHz/PC133 machine in its place and everything has worked flawlessly since. - brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On Tue, Mar 20, 2001 at 03:23:55PM -0800, Edwin L. Culp wrote: It would really be nice to have this committed, if it doesn't break anything, to not have to be patching every time. It will be. I am waiting a responce back from someone. But one way or another it will be fixed -- I run two K6-2's myself, including my main desktop. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
Quoting David O'Brien [EMAIL PROTECTED]: On Tue, Mar 20, 2001 at 03:23:55PM -0800, Edwin L. Culp wrote: It would really be nice to have this committed, if it doesn't break anything, to not have to be patching every time. It will be. I am waiting a responce back from someone. But one way or another it will be fixed -- I run two K6-2's myself, including my main desktop. That is good news, David. Thanks a lot. It's working great for me. I haven't been able to load my laptop for over a month. ed -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On Mon, Mar 19, 2001 at 08:30:12AM +0100, Pascal Hofstee wrote: AMD K6-2 350 I noticed the vague stack smashes posting earlier ... and i think it's very likely this is the same bug Same here, random crashes -- AMD K6-2 300; no panic, no crash dump, just a complete system freeze if you happen to use too much CPU. I had to temporarily revert to an older kernel. -- Pierre Beyssac [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
Pierre Beyssac [EMAIL PROTECTED] writes: On Mon, Mar 19, 2001 at 08:30:12AM +0100, Pascal Hofstee wrote: I noticed the vague stack smashes posting earlier ... and i think it's very likely this is the same bug Same here, random crashes -- AMD K6-2 300; no panic, no crash dump, just a complete system freeze if you happen to use too much CPU. I had to temporarily revert to an older kernel. Try this workaround (apply with 'patch -l'): Index: pmap.c === RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v retrieving revision 1.277 diff -u -r1.277 pmap.c --- pmap.c 2001/03/15 05:10:06 1.277 +++ pmap.c 2001/03/18 21:21:19 @@ -2664,7 +2664,7 @@ i686_pagezero(CADDR2); else #endif - bzero(CADDR2, PAGE_SIZE); + generic_bzero(CADDR2, PAGE_SIZE); *(int *) CMAP2 = 0; } DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Try this workaround (apply with 'patch -l'):
Here's a better workaround. Revert the previous patch and apply this
one:
Index: npx.c
===
RCS file: /home/ncvs/src/sys/i386/isa/npx.c,v
retrieving revision 1.93
diff -u -r1.93 npx.c
--- npx.c 2001/03/19 00:28:04 1.93
+++ npx.c 2001/03/19 20:28:55
@@ -456,7 +456,7 @@
}
npxinit(__INITIAL_NPXCW__);
-#ifdef I586_CPU
+#ifdef I586_CPU_DOES_NOT_WORK
if (cpu_class == CPUCLASS_586 npx_ex16 npx_exists
timezero("i586_bzero()", i586_bzero)
timezero("bzero()", bzero) * 4 / 5) {
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On Mon, Mar 19, 2001 at 11:19:02PM +0100, Pierre Beyssac wrote: Ok, thanks, note that your previous patch works fine, at least my make world is still running :-) Famous last words; I had a freeze soon afterwards. Though it seems to have improved the situation quite a bit. Now running another make world with the new patch... -- Pierre Beyssac [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On 19-Mar-01 Pierre Beyssac wrote: On Mon, Mar 19, 2001 at 10:16:00PM +0100, Dag-Erling Smorgrav wrote: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Try this workaround (apply with 'patch -l'): Here's a better workaround. Revert the previous patch and apply this one: Ok, thanks, note that your previous patch works fine, at least my make world is still running :-) The previous patch is not sufficient. It only fixes one instance of bzero, but currently all instances of bzero, bcopy, copyin, and copyout are broken on the 586 and his second patch fixes all of them. I'll try this one ASAP. +#ifdef I586_CPU_DOES_NOT_WORK -- Pierre Beyssac[EMAIL PROTECTED] -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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: CURRENT instability
Pascal Hofstee [EMAIL PROTECTED] writes: With a CURRENT build/installworld from yesterday ... i get a VERY unstable system that page faults under the slightest CPU load (e.g. playing MP3's) What kind of CPU? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On Mon, Mar 19, 2001 at 01:00:08AM +0100, Dag-Erling Smorgrav wrote: Pascal Hofstee [EMAIL PROTECTED] writes: With a CURRENT build/installworld from yesterday ... i get a VERY unstable system that page faults under the slightest CPU load (e.g. playing MP3's) What kind of CPU? AMD K6-2 350 I noticed the vague stack smashes posting earlier ... and i think it's very likely this is the same bug -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
