Hardware migration and upgrade from 6.3 to 8.0 advice
Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). My current system is alive since 2005, so is full of code, scripts, configurations,lookfeel,ssh keys etc.. that i would like to keep handy in my new system. Also, currently i run gmirror, i am mentioning it, in case it affects something. Since 2005, dealing with programming/support/etc.. i haven't done any upgrade task in FreeBSD, so i dont feel that confident in this regard. I could: a) install a brand new 8.0-RELEASE in the new hardware and then a1) just mount the old disks to the new system or a2) migrate /home user data directly to the new home dirs b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) So, its a trade-off between pain, correctness, effectiveness, and ease of use. What would you guys recommend? Which way to go? Any other options? Thanx in advance! Please include me in your CC, as i am not subscribed to the list. Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware migration and upgrade from 6.3 to 8.0 advice
Thanx to all. I will keep the old machine for development/maintenance/support, while bulding/testing/migrating the newest versions of software in the new hardware. Up to now, i got the base system/kernel working ok on the new beast, and currently installing additional distributions. All seem fine. Achilleas Mantzios --- On Fri, 12/4/09, Adam Vande More amvandem...@gmail.com wrote: From: Adam Vande More amvandem...@gmail.com Subject: Re: Hardware migration and upgrade from 6.3 to 8.0 advice To: Achilleas Mantzios mantzios.ach...@yahoo.com Cc: freebsd-questions@freebsd.org Date: Friday, December 4, 2009, 1:36 PM On Fri, Dec 4, 2009 at 2:57 AM, Achilleas Mantzios mantzios.ach...@yahoo.com wrote: Hello, i am facing this situation, where i need to upgrade from my 6.3 i386 system, used as my main workstation, to a new hardware based on amd64 (phenom II x4). My current system is alive since 2005, so is full of code, scripts, configurations,lookfeel,ssh keys etc.. that i would like to keep handy in my new system. Also, currently i run gmirror, i am mentioning it, in case it affects something. Since 2005, dealing with programming/support/etc.. i haven't done any upgrade task in FreeBSD, so i dont feel that confident in this regard. I could: a) install a brand new 8.0-RELEASE in the new hardware and then a1) just mount the old disks to the new system or a2) migrate /home user data directly to the new home dirs b) migrate all current data to the new hardware, kernel/system included, and then try to upgrade to 8.0 (by sysinstall or makeworld/makekernel) So, its a trade-off between pain, correctness, effectiveness, and ease of use. What would you guys recommend? Which way to go? Any other options? Thanx in advance! Please include me in your CC, as i am not subscribed to the list. Achilleas Mantzios You may want to consider installing from scratch and migrating over. This would allow you setup zfs and make the move easier. Also may want to explore run ahci(4) as that can seriously increase disk speed although I believe many more improvements live in STABLE, not RELEASE. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online
Στις Monday 18 May 2009 22:07:24 ο/η Miroslav Lachman έγραψε: Achilleas Mantzios wrote: Hello, I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: Intel i865G GMCH on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 The correct order of commands is: atacontrol list gmirror list gmirror forget gm0 gmirror clear -v ad4 gmirror insert -v gm0 ad4 Thanx. Miroslav Lachman -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online
Στις Monday 18 May 2009 13:27:58 ο/η Manolis Kiagias έγραψε: It looks to me you got a bad disk now. Manoli, thanx i replaced the bad disk and the system looks ok, rebulding gm0. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online
Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: Intel i865G GMCH on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22). Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status NameStatus Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online
Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: Intel i865G GMCH on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22). Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status NameStatus Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online
Hey Manoli! glad to see you again, Στις Monday 18 May 2009 13:27:58 ο/η Manolis Kiagias έγραψε: Achilleas Mantzios wrote: Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: Intel i865G GMCH on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. It looks to me you got a bad disk now. I certainly hope so, since there is nothing else i can do I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22). Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status NameStatus Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? I'd recommend attaching the bad disk on its own to a system and perform tests on it. Is the BIOS recognizing this properly? I would run hardware Yes, the BIOS recognizes it ok i suppose. tests on it - either manufacturer ones, or stuff like sysutils/smartmontools. You could also try installing FreeBSD on it and see if it works. And probably use dd to clean all the contents, esp. the partition table and the last sector where geom information is stored. Thanx, lacking time i think i will try to use a brand new identical disk. Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? The bad disk may be sending confusing signals to the bus / IDE interface. I've had this once (although it was due to a bad cable). The entire mirror would disappear suddenly. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online
Hello, I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: Intel i865G GMCH on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22). Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status NameStatus Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Just to summarize (after 5.5 days of uptime), i'd like to recap on what happened next. I burned the SiS 651 based motherboard, while memtesting, and i replaced it with a new Asrock, Intel 82865G based motherboard. All run fine, no panics, no unexpected segfaults. It seems that the old SiS was fine until i fitted the kodicom4400 on the PCI bus, when all the problems started. Now at idle i can get CPU temps as low as 35 deg Celsious, altho it turned out that was not my problem in the first place. Thank you all for your help. Manoli Euxaristw! -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Στις Tuesday 22 July 2008 00:25:46 ο/η Tore Lund έγραψε: Achilleas Mantzios wrote: ... Having said that, the issue with the temperature must not be my thing :( after kldload coretemp, i get [EMAIL PROTECTED] ~]% sysctl -a | grep tempera hw.acpi.thermal.tz0.temperature: 40,0C dev.cpu.0.temperature: -1 [EMAIL PROTECTED] ~]% The first always is stuck to 40 and dev.cpu.0.temperature to -1. Achillea, have you told us what CPU you have? Manolis presumes you have an Intel, but I do not see this information anywhere in your posts. If you have a recent AMD, try the port k8temp. Sorry, i have a CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2672.74-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNXT-ID,xTPR So coretemp is not for me. While experimenting, i noticed the 1st and 3rd temperatures from mbmon to be updated in a fashion that seems natural. [EMAIL PROTECTED] ~]% mbmon Temp.= 41.0, 201.0, 42.0; Rot.= 3443,0,0 Vcore = 1.50, 1.81; Volt. = 3.30, 5.08, 11.43, -11.74, -1.69 I started to trust mbmon, and i think the 1st temp must be motherboard, while the 3rd CPU, and indeed the first value varies betaeen 41-42 degrees, and the third value from 39, (~ 100% idle) to 45 (0% idle). So i assume the above must be right. Yesterday i had mbmon -t mbmon.out running all night and the highest CPU temp was at 46 deg C, while highest MB temp was at 43 deg Celsius (if the previous assumptions about the interpretation of the output of mbmon are correct). Both high temps happened while running periodic daily at 03:00 (which increased my trust in those). All that, was after i blew the box/case inside and closed the case. If i trust those numbers and their interpretation then i must not have a temperature problem (anymore). Lets see how the machine behaves. There is always the other usual suspect from the memory department :) -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Στις Tuesday 22 July 2008 10:16:02 ο/η Manolis Kiagias έγραψε: Achilleas Mantzios wrote: Στις Tuesday 22 July 2008 00:25:46 ο/η Tore Lund έγραψε: Achilleas Mantzios wrote: ... Having said that, the issue with the temperature must not be my thing :( after kldload coretemp, i get [EMAIL PROTECTED] ~]% sysctl -a | grep tempera hw.acpi.thermal.tz0.temperature: 40,0C dev.cpu.0.temperature: -1 [EMAIL PROTECTED] ~]% The first always is stuck to 40 and dev.cpu.0.temperature to -1. Achillea, have you told us what CPU you have? Manolis presumes you have an Intel, but I do not see this information anywhere in your posts. If you have a recent AMD, try the port k8temp. Sorry, i have a CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2672.74-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNXT-ID,xTPR So coretemp is not for me. Definitely. While experimenting, i noticed the 1st and 3rd temperatures from mbmon to be updated in a fashion that seems natural. [EMAIL PROTECTED] ~]% mbmon Temp.= 41.0, 201.0, 42.0; Rot.= 3443,0,0 Vcore = 1.50, 1.81; Volt. = 3.30, 5.08, 11.43, -11.74, -1.69 What chipset is the mobo based on? mbmon runs fine on my 865G and a 3Ghz P4 CPU. You are probably correct, the middle temp may represent a sensor that is not recognized, but the other readings seem normal. i'll let you know next time i open the case. Is there any reading from dmesg or sysctl that can reveal that info? I started to trust mbmon, and i think the 1st temp must be motherboard, while the 3rd CPU, and indeed the first value varies betaeen 41-42 degrees, and the third value from 39, (~ 100% idle) to 45 (0% idle). So i assume the above must be right. Yesterday i had mbmon -t mbmon.out running all night and the highest CPU temp was at 46 deg C, while highest MB temp was at 43 deg Celsius (if the previous assumptions about the interpretation of the output of mbmon are correct). Both high temps happened while running periodic daily at 03:00 (which increased my trust in those). All that, was after i blew the box/case inside and closed the case. If i trust those numbers and their interpretation then i must not have a temperature problem (anymore). Lets see how the machine behaves. There is always the other usual suspect from the memory department :) For memory, I would suggest memtest86. For stressing the machine, try math/mprime in torture mode. Watch the temperatures and make sure you leave it running for a couple of hours and you don't get any errors. Usually, if you have a termperature problem it will bail out in half an hour or less. Memtest86 is good enough, i have used it on other machines. Thx for the math/mprime hint. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Στις Tuesday 22 July 2008 14:27:28 ο/η Manolis Kiagias έγραψε: Achilleas Mantzios wrote: While experimenting, i noticed the 1st and 3rd temperatures from mbmon to be updated in a fashion that seems natural. [EMAIL PROTECTED] ~]% mbmon Temp.= 41.0, 201.0, 42.0; Rot.= 3443,0,0 Vcore = 1.50, 1.81; Volt. = 3.30, 5.08, 11.43, -11.74, -1.69 What chipset is the mobo based on? mbmon runs fine on my 865G and a 3Ghz P4 CPU. You are probably correct, the middle temp may represent a sensor that is not recognized, but the other readings seem normal. i'll let you know next time i open the case. Is there any reading from dmesg or sysctl that can reveal that info? Sure. There are various places to get this info. Sometimes the BIOS startup messages contain a hint on the chipset (like 865, 915 and so on). My dmesg also shows: agp0: Intel 82865 host to AGP bridge on hostb0 And you can also use pciconf -v -l hdr=0x00 vendor = 'Intel Corporation' device = '82865G/PE/P, 82848P DRAM Controller / Host-Hub Interface' class = bridge subclass = HOST-PCI Considering that you are running an older P4, probably socket 478, chances are you are using an 845 or 848 or 865 chipset. Then by all evidence, % dmesg | grep -i agp agp0: SiS 651 host to AGP bridge on hostb0 [EMAIL PROTECTED]:0:0:0: class=0x06 card=0x1801147b chip=0x06511039 rev=0x02 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS651 Host-to-PCI Bridge' class = bridge subclass = HOST-PCI it must be the SiS 651 chipset http://www.sis.com/products/sis651.htm -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Monitoring CPU temperature: mbmon shows 201 degrees C
Hi, i have had various crashes and segfaults in the last hot days (room temp about 30 deg C). I tried to monitor CPU temp with mbmon, which shows a very big value in COU temperature: [EMAIL PROTECTED]:~# mbmon -c 1 Temp.= 42.0, 201.0, 39.0; Rot.= 3245,0,0 Vcore = 1.50, 1.81; Volt. = 3.30, 5.08, 11.31, -11.74, -1.66 Also, healthdc shows: localhost 186.00.0 0.0531417307 1.492.49 1.625.42 0.00 -10.84 0.00 and lmmon -i shows: Motherboard Temp Voltages 186C / 366F / 459KVcore1: +1.469V Vcore2: +1.766V Fan Speeds + 3.3V: +3.219V + 5.0V: +4.932V 1: 10629rpm+12.0V: +11.750V 2: 33750rpm-12.0V: -13.188V 3: 16071rpm- 5.0V: -1.800V So i dont have any idea how to assess the real CPU temperature. I am thinking of tuning down the BIOS to fail-safe settings, just as an extra measure. Apart from that, i have no clue how to solve the random crashes/segfaults problem. I also opened the case in order to get ventilated with fresh air from the room. Any hints would be welcome. P.S. Please include me in the reply, i am not subscribed to -questions. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Στις Monday 21 July 2008 14:59:09 ο/η Kemian Dang έγραψε: Achilleas Mantzios wrote: Hi, i have had various crashes and segfaults in the last hot days (room temp about 30 deg C). I tried to monitor CPU temp with mbmon, which shows a very big value in COU temperature: [EMAIL PROTECTED]:~# mbmon -c 1 Temp.= 42.0, 201.0, 39.0; Rot.= 3245,0,0 Vcore = 1.50, 1.81; Volt. = 3.30, 5.08, 11.31, -11.74, -1.66 Also, healthdc shows: localhost 186.00.0 0.0531417307 1.49 2.491.625.42 0.00 -10.84 0.00 and lmmon -i shows: Motherboard Temp Voltages 186C / 366F / 459KVcore1: +1.469V Vcore2: +1.766V Fan Speeds + 3.3V: +3.219V + 5.0V: +4.932V 1: 10629rpm+12.0V: +11.750V 2: 33750rpm-12.0V: -13.188V 3: 16071rpm- 5.0V: -1.800V So i dont have any idea how to assess the real CPU temperature. I am thinking of tuning down the BIOS to fail-safe settings, just as an extra measure. Apart from that, i have no clue how to solve the random crashes/segfaults problem. I also opened the case in order to get ventilated with fresh air from the room. Any hints would be welcome. P.S. Please include me in the reply, i am not subscribed to -questions. I use sysctl -a |grep tepmerature to get the temperature, tough to say the truth, I am not sure about their exactly meaning... Yes thx, the problem is that hw.acpi.thermal.tz0.temperature always return 40.0C, and i read about others noticing that. Best wishes, Kemian -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Στις Monday 21 July 2008 15:41:01 ο/η DA Forsyth έγραψε: From: Achilleas Mantzios [EMAIL PROTECTED] Hi, i have had various crashes and segfaults in the last hot days (room temp about 30 deg C). I tried to monitor CPU temp with mbmon, which shows a very big value in COU temperature: I also opened the case in order to get ventilated with fresh air from the room. Actually, that doesn't work, your components will get hotter. This is because the case provides a through flow environment where air is forced to flow over most of the components most of the time. By opening the case you remove the force, and now have to rely on convection. What you want to do is make sure all the fans are running freely. Especially the processor fan. It may have stopped silently an dthat would definitely cause crashes. A fan at the front of the case blowing IN is more effective than one on the back blowing out, so if there isn't one on the front, add one. The 80 to 120mm ones can be very quiet and some can control their own speed if your motherboard cannot do it. If one can blow in the front and directly on the harddrives then that is a bonus, cool harddrives last longer. The basic idea of a case is to have air coming in the front and exiting at the rear. So make sure all your fans are blowing in the right direction. My office goes to 38C in summer, and all 5 computers just keep on going, using the principles above. I fitted a fan to the UPS as well (-: My box has 3 fans, one on the case blowing from outside=inside, one in the power supply and one on the CPU. In the evening, i will have the case/board inside blown/cleaned with air, i am gonna close the case, and i am gonna tune BIOS to fail-safe settings. Apart from that, i would like to have a reliable tool to monitor temperature. Is there anything in mind? -- DA Fo rsythNetwork Supervisor Principal Technical Officer -- Institute for Water Research http://www.ru.ac.za/institutes/iwr/ -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring CPU temperature: mbmon shows 201 degrees C
Στις Monday 21 July 2008 18:17:59 ο/η Manolis Kiagias έγραψε: Achilleas Mantzios wrote: My office goes to 38C in summer, and all 5 computers just keep on going, using the principles above. I fitted a fan to the UPS as well (-: My box has 3 fans, one on the case blowing from outside=inside, one in the power supply and one on the CPU. In the evening, i will have the case/board inside blown/cleaned with air, i am gonna close the case, and i am gonna tune BIOS to fail-safe settings. Apart from that, i would like to have a reliable tool to monitor temperature. Is there anything in mind? As you already noticed, mbmon is no good in recent hardware. It works successfully in my 865-based systems though. As others have said, I would recommend adding a rear out-take fan. Do not rely on the PSU's fan to take all the warm air out. The PSU generates heat on its own, and the fan may not be sufficient. A rear out-take fan should be located rather high - at CPU height - since warm air always goes up. This is where most cases have a place for the fan anyway. It is indeed as you say. The fans on my case are: the PSU fan, one takeout fan just below the PSU and the CPU fan. It is a medium tower size case. The thing is on the bottom PCI slot i have installed a Kodicom 4400 for video capture for use with zoneminder, (the FreeBSD port is available from the zoneminder site) and right above that a LML video capture card. and then while capturing 5 full frame-rate (25fps) cameras in zoneminder a) the load never falls below 0.4 even while no users use it (it is our family workstation as well:) b) all the heat from the kodicom flows higher to the CPU/memory area of the case Having said that, the issue with the temperature must not be my thing :( after kldload coretemp, i get [EMAIL PROTECTED] ~]% sysctl -a | grep tempera hw.acpi.thermal.tz0.temperature: 40,0C dev.cpu.0.temperature: -1 [EMAIL PROTECTED] ~]% The first always is stuck to 40 and dev.cpu.0.temperature to -1. A note for monitoring: If you are using FreeBSD 7.0 and you have an Intel Core CPU, there is a new coretemp(4) driver that can actually read the on-die digital thermal sensor. Have a look at man coretemp -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Script Automated voice dialout to normal human voice phones?
Hi, i intend to implement a home security system based on zoneminder. Upon certain conditions i'd like to trigger various alarms depending on the various criteria met/sensors values, etc... like trigger an external siren or call my mobile phone. Now what i'd like to do is to write a script that is going to be called from inside zoneminder, that will call my mobile and will play a pre-recorded wav or mp3 message like: your house is being at risk, call the police now. I searched a lot, and could not find anything close. Results from google are saturated with answering machine and vgetty, which in my case i dont think they fit. Anyone with experience with dialing out human phones? Is that possible? Pls, include my address to your replies, since i am not subscribed on -questions. Thanx for any clues. -- Achilleas Mantzios ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
