Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
At Fri, 8 Nov 2002 00:58:10 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I got same result on my box. Only solution I have is deinstall dnetc. :-) ... What motherboard/CPU is this on? Have you tried a nonSMP kernel? It's SuperMicro's P3TDDE with dual P-III (1.13GHz). Yes, it works fine when I removed options SMP and options apic from kernel configuration. -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
From [EMAIL PROTECTED] Thu Nov 7 18:00:10 2002 Date: Thu, 07 Nov 2002 14:47:03 -0800 From: Joel M. Baldwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. So the questions now are. 1.) What is dnet doing that is Hard Locking the system? 2.) Is the dnet problem the same as what has been causing my Hard Locks all along? Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my-current system Hard Locking?' )
--On Thursday, November 07, 2002 6:07 PM -0500 Ray Kohler [EMAIL PROTECTED] wrote: From [EMAIL PROTECTED] Thu Nov 7 18:00:10 2002 Date: Thu, 07 Nov 2002 14:47:03 -0800 From: Joel M. Baldwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. So the questions now are. 1.) What is dnet doing that is Hard Locking the system? 2.) Is the dnet problem the same as what has been causing my Hard Locks all along? Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) - @ I've run dnet reliably before. I'm assuming the Hard Lock problem is threads related, but at this point who knows. A more heavily load system seems to increase the chances of a Hard Lock. But it HAS happened with nothing going on. Well, relatively nothing, this system does real work so its never completely idle. The important thing is I can now force a Hard Lock simply by running a program. This is something that shouldn't happen and needs to be solved. With any luck this will also solve my stability problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. I got same result on my box. Only solution I have is deinstall dnetc. :-) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my-current system Hard Locking?' )
--On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama [EMAIL PROTECTED] wrote: At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. I got same result on my box. Only solution I have is deinstall dnetc. :-) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. What motherboard/CPU is this on? Have you tried a nonSMP kernel? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
On 07-Nov-2002, Joel M. Baldwin wrote: --On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama [EMAIL PROTECTED] wrote: At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. I got same result on my box. Only solution I have is deinstall dnetc. :-) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. What motherboard/CPU is this on? Have you tried a nonSMP kernel? I noticed my machine started locking up almost a month ago and ended up removing all services on startup. Starting dnetc back up and the machine locks hard. Sorry for lack of info, but this appears to be just over a month old. The info I wrote down previously pointed to kern_fork.c and proctree function call. -- Scott DodsonPGP KEY id 0x5F9A9E5E [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
