Re: 7.1 and wireless with ural
And in my rc.conf I have this defined: ifconfig_ural0=wpa DHCP hostname=my.home.server You must create a virtual interface (i.e. wlan0) and then configure it. # ifconfig wlan0 create wlandev ural0 Read man(5) rc.conf and the handbook for more information. You are using FreeBSD 8, don't you? Regards Alberto Mijares ___ 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: 7.1 and wireless with ural
On Mon, Apr 19, 2010 at 08:43:18PM -0400, Bobby Walker wrote: Hey list, I've searched and searched for a solution to this problem and I can't find one. I've got the wireless nic setup, its a Linksys WUSB54G v2. I have a Linksys WUSB54GC, and use the rum driver, check out the man page, man rum..., the WUSB54G is mentioned here as well.. ..it works like a dream on my 8.0-STABLE system -- Mvh/Brgds Harry FreeBSD 8.0-STABLE #23: Compiled at Mon Apr 19 18:55:29 CEST 2010 i386 ___ 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: 7.1 and wireless with ural
No I only had 7.1 on CD, but I've burned 8 onto disc and will upgrade when I get home tonight. Thanks Sent from my iPhone On Apr 20, 2010, at 7:27 AM, Alberto Mijares amijar...@gmail.com wrote: And in my rc.conf I have this defined: ifconfig_ural0=wpa DHCP hostname=my.home.server You must create a virtual interface (i.e. wlan0) and then configure it. # ifconfig wlan0 create wlandev ural0 Read man(5) rc.conf and the handbook for more information. You are using FreeBSD 8, don't you? Regards Alberto Mijares ___ 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: 7.1 and wireless with ural
FYI, I upgraded to 8.0 and built the virtual interface, but still had the same problems. I finally stumbled upon the solution to my problem. I added to rc.conf wpa_supplicant_flags=-s -Dbsd It will now get online, I'm rebuilding my kernel before cvsup'ing. Thanks! From: bobbyjwal...@live.com To: freebsd-questions@freebsd.org Date: Tue, 20 Apr 2010 17:06:02 -0500 Subject: Re: 7.1 and wireless with ural No I only had 7.1 on CD, but I've burned 8 onto disc and will upgrade when I get home tonight. Thanks Sent from my iPhone On Apr 20, 2010, at 7:27 AM, Alberto Mijares amijar...@gmail.com wrote: And in my rc.conf I have this defined: ifconfig_ural0=wpa DHCP hostname=my.home.server You must create a virtual interface (i.e. wlan0) and then configure it. # ifconfig wlan0 create wlandev ural0 Read man(5) rc.conf and the handbook for more information. You are using FreeBSD 8, don't you? Regards Alberto Mijares ___ 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 _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5___ 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: 7.1 System Crashing
On Tue, Apr 14, 2009 at 8:49 PM, Fbsd1 fb...@a1poweruser.com wrote: APseudoUtopia wrote: My FreeBSD 7.1-RELEASE-p3 system has gone down a few times in the last two days. I'm trying to figure out why, but there is nothing in /var/log/messages or dmesg about the incident. Here's the output from the `last` command: User ttyp0 1.2.3.4 Tue Apr 14 19:02 still logged in User ttyp0 1.2.3.4 Tue Apr 14 18:52 - 19:02 (00:09) reboot ~ Tue Apr 14 18:52 User ttyp0 1.2.3.4 Tue Apr 14 18:42 - crash (00:09) User ttyp0 1.2.3.4 Tue Apr 14 16:06 - 18:42 (02:36) User ttyp0 1.2.3.4 Tue Apr 14 11:23 - 12:53 (01:29) reboot ~ Tue Apr 14 07:44 User ttyp0 1.2.3.4 Mon Apr 13 20:01 - 22:58 (02:57) User ttyp0 1.2.3.4 Mon Apr 13 19:56 - 20:01 (00:04) User ttyp0 1.2.3.4 Mon Apr 13 19:31 - 19:56 (00:25) User ttyp0 1.2.3.4 Sun Apr 12 15:02 - 16:15 (01:12) User ttyp0 1.2.3.4 Sun Apr 12 14:48 - 15:02 (00:14) reboot ~ Sun Apr 12 14:48 shutdown ~ Sun Apr 12 14:45 User ttyp0 1.2.3.4 Sun Apr 12 14:24 - shutdown (00:21) User ttyp0 1.2.3.4 Sat Apr 11 13:03 - 17:00 (03:56) wtmp begins Wed Apr 1 21:21:28 UTC 2009 As you can see, the system reboot several times, and crashed the most recent time. Only one of the shutdown/reboots listed is valid - the furthest one. I have no idea why it is rebooting/crashing. It has been completely stable until about 1-2 days ago. If anyone can direct me to post the output to any commands or any log messages, I'd be more than willing to do so in order to help anyone diagnose my problem. Thank you for your time. What you are experiencing are the early warning signs of disk drive failure or over heating problems. Before doing any thing else make backup of your user data if you have not done so already. Then open your box and use a small brush and a can of compressed air to blow the dust off the motherboard and the fans. Give special attention to the fan in the power supply. If PC is older than 3 years or has over 1 year of continues use then replace the power supply. IF problem still happens replace hard drive. The system is in a colocation center which I don't have access to. The HDD crashed several months ago and was replaced by a brand new drive (or so I was told). So I'm leaning towards a heat or PSU problem. I installed Healthd on the system to monitor such things, however it didn't detect the hardware properly. Apparently the voltage in my CPU core was 0.00, as was the temperature. Is there any other way to monitor these things? Everyone: Thanks for all the help. I'll open up a ticket with my host to get them to look at it. ___ 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: 7.1 System Crashing
-Original Message- From: APseudoUtopia [mailto:apseudouto...@gmail.com] Sent: 14 April 2009 20:23 To: FreeBSD Questions Subject: 7.1 System Crashing My FreeBSD 7.1-RELEASE-p3 system has gone down a few times in the last two days. I'm trying to figure out why, but there is nothing in /var/log/messages or dmesg about the incident. Here's the output from the `last` command: User ttyp01.2.3.4Tue Apr 14 19:02 still logged in User ttyp01.2.3.4Tue Apr 14 18:52 - 19:02 (00:09) reboot ~ Tue Apr 14 18:52 User ttyp01.2.3.4Tue Apr 14 18:42 - crash (00:09) User ttyp01.2.3.4Tue Apr 14 16:06 - 18:42 (02:36) User ttyp01.2.3.4Tue Apr 14 11:23 - 12:53 (01:29) reboot ~ Tue Apr 14 07:44 User ttyp01.2.3.4Mon Apr 13 20:01 - 22:58 (02:57) User ttyp01.2.3.4Mon Apr 13 19:56 - 20:01 (00:04) User ttyp01.2.3.4Mon Apr 13 19:31 - 19:56 (00:25) User ttyp01.2.3.4Sun Apr 12 15:02 - 16:15 (01:12) User ttyp01.2.3.4Sun Apr 12 14:48 - 15:02 (00:14) reboot ~ Sun Apr 12 14:48 shutdown ~ Sun Apr 12 14:45 User ttyp01.2.3.4Sun Apr 12 14:24 - shutdown (00:21) User ttyp01.2.3.4Sat Apr 11 13:03 - 17:00 (03:56) wtmp begins Wed Apr 1 21:21:28 UTC 2009 As you can see, the system reboot several times, and crashed the most recent time. Only one of the shutdown/reboots listed is valid - the furthest one. I have no idea why it is rebooting/crashing. It has been completely stable until about 1-2 days ago. If anyone can direct me to post the output to any commands or any log messages, I'd be more than willing to do so in order to help anyone diagnose my problem. Thank you for your time. ___ 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 If you are able to I would check the cpu heat sink and fan are clean and in good working order, or if the machine is remote to you install something like healthd and have a look at the temperatures. Regards Graeme ___ 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: 7.1 System Crashing
APseudoUtopia wrote: My FreeBSD 7.1-RELEASE-p3 system has gone down a few times in the last two days. I'm trying to figure out why, but there is nothing in /var/log/messages or dmesg about the incident. Here's the output from the `last` command: User ttyp01.2.3.4Tue Apr 14 19:02 still logged in User ttyp01.2.3.4Tue Apr 14 18:52 - 19:02 (00:09) reboot ~ Tue Apr 14 18:52 User ttyp01.2.3.4Tue Apr 14 18:42 - crash (00:09) User ttyp01.2.3.4Tue Apr 14 16:06 - 18:42 (02:36) User ttyp01.2.3.4Tue Apr 14 11:23 - 12:53 (01:29) reboot ~ Tue Apr 14 07:44 User ttyp01.2.3.4Mon Apr 13 20:01 - 22:58 (02:57) User ttyp01.2.3.4Mon Apr 13 19:56 - 20:01 (00:04) User ttyp01.2.3.4Mon Apr 13 19:31 - 19:56 (00:25) User ttyp01.2.3.4Sun Apr 12 15:02 - 16:15 (01:12) User ttyp01.2.3.4Sun Apr 12 14:48 - 15:02 (00:14) reboot ~ Sun Apr 12 14:48 shutdown ~ Sun Apr 12 14:45 User ttyp01.2.3.4Sun Apr 12 14:24 - shutdown (00:21) User ttyp01.2.3.4Sat Apr 11 13:03 - 17:00 (03:56) wtmp begins Wed Apr 1 21:21:28 UTC 2009 As you can see, the system reboot several times, and crashed the most recent time. Only one of the shutdown/reboots listed is valid - the furthest one. I have no idea why it is rebooting/crashing. It has been completely stable until about 1-2 days ago. If anyone can direct me to post the output to any commands or any log messages, I'd be more than willing to do so in order to help anyone diagnose my problem. Thank you for your time. ___ 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 What you are experiencing are the early warning signs of disk drive failure or over heating problems. Before doing any thing else make backup of your user data if you have not done so already. Then open your box and use a small brush and a can of compressed air to blow the dust off the motherboard and the fans. Give special attention to the fan in the power supply. If PC is older than 3 years or has over 1 year of continues use then replace the power supply. IF problem still happens replace hard drive. ___ 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: 7.1 System Crashing
Could also be a PSU going out - unable to maintain the correct voltages. On Tue, Apr 14, 2009 at 3:23 PM, APseudoUtopia apseudouto...@gmail.com wrote: My FreeBSD 7.1-RELEASE-p3 system has gone down a few times in the last two days. I'm trying to figure out why, but there is nothing in /var/log/messages or dmesg about the incident. Here's the output from the `last` command: User ttyp0 1.2.3.4 Tue Apr 14 19:02 still logged in User ttyp0 1.2.3.4 Tue Apr 14 18:52 - 19:02 (00:09) reboot ~ Tue Apr 14 18:52 User ttyp0 1.2.3.4 Tue Apr 14 18:42 - crash (00:09) User ttyp0 1.2.3.4 Tue Apr 14 16:06 - 18:42 (02:36) User ttyp0 1.2.3.4 Tue Apr 14 11:23 - 12:53 (01:29) reboot ~ Tue Apr 14 07:44 User ttyp0 1.2.3.4 Mon Apr 13 20:01 - 22:58 (02:57) User ttyp0 1.2.3.4 Mon Apr 13 19:56 - 20:01 (00:04) User ttyp0 1.2.3.4 Mon Apr 13 19:31 - 19:56 (00:25) User ttyp0 1.2.3.4 Sun Apr 12 15:02 - 16:15 (01:12) User ttyp0 1.2.3.4 Sun Apr 12 14:48 - 15:02 (00:14) reboot ~ Sun Apr 12 14:48 shutdown ~ Sun Apr 12 14:45 User ttyp0 1.2.3.4 Sun Apr 12 14:24 - shutdown (00:21) User ttyp0 1.2.3.4 Sat Apr 11 13:03 - 17:00 (03:56) wtmp begins Wed Apr 1 21:21:28 UTC 2009 As you can see, the system reboot several times, and crashed the most recent time. Only one of the shutdown/reboots listed is valid - the furthest one. I have no idea why it is rebooting/crashing. It has been completely stable until about 1-2 days ago. If anyone can direct me to post the output to any commands or any log messages, I'd be more than willing to do so in order to help anyone diagnose my problem. Thank you for your time. ___ 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 ___ 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: 7.1 64 bit
Hi everyone, I have a mixed update: I was able to get it running, but once it starts, it gets stuck. Here are the last two lines: isab0: pci-isa bridge. at device 31.0 on pci0 isa0: isa bus on isab0 Please let me know if you need more info, or you have any advice on what this could be. On Wed, Mar 18, 2009 at 12:47 PM, Gal Lis galg...@gmail.com wrote: Thanks for that, I'm sorry I didn't mention what version I downloaded earlier. I will reply once I test it out. On Wed, Mar 18, 2009 at 12:31 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: ia64 is for Itanium processor . Therefore ia64 can NOT work on Intel Pentium series processors . Their architectures are different . You should download amd64 ISO . amd64 is for both Intel 64 bits and AMD 64 bits pocessors compatible to each other . On Wed, Mar 18, 2009 at 2:58 PM, Gal Lis galg...@gmail.com wrote: They should definitely support it. My workstation has an Intel E5320 quad core, and the M600 has a 5400 series chip, but I can't remember which one exactly. They should definitely be able to handle it. I downloaded the 7.1 ia64, maybe there is something else I should be downloading? On Wed, Mar 18, 2009 at 11:53 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: You said 32-bits 6.4 could be loaded . A question coming to mind is Can your processor handle 64-bits ? Please check this issue . Thank you very much . Mehmet Erol sanliturk On Wed, Mar 18, 2009 at 2:29 PM, Gal Lis galg...@gmail.com wrote: I guess that shows just how unexperienced I am with all of this. ___ 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: 7.1 64 bit
On Fri, Mar 20, 2009 at 1:51 PM, Gal Lis galg...@gmail.com wrote: Hi everyone, I have a mixed update: I was able to get it running, but once it starts, it gets stuck. Here are the last two lines: isab0: pci-isa bridge. at device 31.0 on pci0 isa0: isa bus on isab0 Please let me know if you need more info, or you have any advice on what this could be. I do not know exact reason of that problem , but i can say the following : Another approach may be to install 7.1 i386 ISO . If 32-bits works . but 64-bits does not work . it may mean that a hardware part is not usable by the 64-bits operating system . If 32-bits even does not work ( we know that 6.4 32-bits is working ) this may mean that in your PC there is an older hardware which its support is or has been removed from the operating system . Another approach would be removal of components from ISA slots and then try to boot the 64-bits operating system . If it can boot , then add the ISA components one-by-one to isolate which component is causing the lock up . If even this does not work : Then best action may be to use 6.4 or if it is possible to replace the older hardware by a newer ( or compatible ) hardware . In new main boards there is no ISA bus slots . ISA slots components approximately can NOT be auto-detected easily because they do not have such a related circuitry . There is another point : Some manufacturers are producing parts which can only work by a famous widely used operating system by cutting some electronic circuitry parts . Such components can NOT work under Unix or Linux . During selection of parts it may be useful to check whether at least it can work under Linux if BSD is not mentioned at all . Thank you very much . Mehmet Erol Sanliturk ___ 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: 7.1 mysql-server-60 stalls
In the last episode (Mar 20), Christoph Kukulies said: I did a pkg_add -r mysql60-server and then # mysql_install_db --user=mysql Installing MySQL system tables... 090320 17:11:24 [Note] Falcon: unable to open system data files. 090320 17:11:24 [Note] Falcon: creating new system data files. ^T ^T load: 0.01 cmd: mysqld 1028 [uwait] 0.01u 0.01s 0% 11420k load: 0.01 cmd: mysqld 1028 [uwait] 0.01u 0.01s 0% 11420k and it hangs forever. I have seen this too, and it's intermittent. I haven't tried very hard to track it down, but adding skip-falcon to your my.cfg file works around the problem by disabling falcon. -- Dan Nelson dnel...@allantgroup.com ___ 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: 7.1 phpmyadmin skip logon screen?
Fbsd1 wrote: Matthew Seaman wrote: Fbsd1 wrote: In 7.1 phpmyadmin now drops you into a logon screen. How do I stop this function and always go to main menu screen? That's nothing to do with the FreeBSD version -- phpMyAdmin works the same on any platform. To make phpMyAdmin auto-login to a DB, you need to use 'config' authentication mode. http://www.phpmyadmin.net/documentation/#authentication_modes It's probably the least secure authentication mode provided, so you should take further steps in your Apache config to stop the world gaining access to your database. Cheers, Matthew Read the user id info on mysql and phpmyadmin. It's so much overkill. Don't need to secure then at all. I have inhouse development box on private lan and mysql has always worked just fine with superuser mysql id of root without password. In the previous version of phpmyadmin no login id was required and I was able to see my DB definitions. Tried to setup config.inc.php by adding statement $cfg['Servers'][$i]['user'] = 'root'; but no joy. What is needed in config.inc.php to allow the default mysql superuser user id root full access in phpmyadmin? For the archives. Figured it out for myself after much testing. This is the contents of my working config.inc.php file. ?php $i=0; $i++; $cfg['Servers'][$i]['auth_type']= 'config'; $cfg['Servers'][$i]['user'] = 'root'; $cfg['Servers'][$i]['AllowNoPasswordRoot'] = 'true'; ? ___ 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: 7.1 64 bit
Hi Frank, Thanks for the reply, I see what to compare the checksums to on the site, but I have a Windows machine. Any hints on how to check? Sorry to ask these mundane questions, but I'm a linux novice. Thank you! From: Frank Shute fr...@shute.org.uk To: Gal Lis gal_...@yahoo.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Sent: Tuesday, March 17, 2009 6:23:52 PM Subject: Re: 7.1 64 bit On Tue, Mar 17, 2009 at 04:08:25PM -0700, Gal Lis wrote: Hi Frank and Glen, I tried both disks on my workstation, and 6.4 started up, but there was nothing from 7.1, so maybe my copy is bad. I burned it using imgburn, and i also have magiciso. How can I check to make sure the file is correct? I've never checksumed anything, and haven't been able to find any help online on how to do so. Look here: http://www.freebsd.org/releases/7.1R/announce.html The checksums are listed there. For you to checksum your iso, you do this on a unix/linux machine: $ md5 7.1-RELEASE-amd64-disc1.iso and compare the checksum printed to that published on that page. If the checksum is different, then you got some corruption and need to download the image again. My guess is that the software you used didn't burn the iso correctly. Load up 6.4 and burn your CD from there, something like the following should do it: # burncd -f /dev/acd0 data 7.1-RELEASE-amd64-disc1.iso fixate Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ 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: 7.1 64 bit
In response to Gal Lis gal_...@yahoo.com: Hi Frank, Thanks for the reply, I see what to compare the checksums to on the site, but I have a Windows machine. Any hints on how to check? http://www.pc-tools.net/win32/md5sums/ -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: 7.1 64 bit
Thank you! I got have another ISO that matches, I'm going to burn and test it. From: Bill Moran wmo...@potentialtech.com To: Gal Lis gal_...@yahoo.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Sent: Wednesday, March 18, 2009 9:30:09 AM Subject: Re: 7.1 64 bit In response to Gal Lis gal_...@yahoo.com: Hi Frank, Thanks for the reply, I see what to compare the checksums to on the site, but I have a Windows machine. Any hints on how to check? http://www.pc-tools.net/win32/md5sums/ -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: 7.1 64 bit
I burned another copy, using another ISO whose checksum comes out ok, and it still isn't loading. What else can I be doing wrong? From: Bill Moran wmo...@potentialtech.com To: Gal Lis gal_...@yahoo.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Sent: Wednesday, March 18, 2009 9:30:09 AM Subject: Re: 7.1 64 bit In response to Gal Lis gal_...@yahoo.com: Hi Frank, Thanks for the reply, I see what to compare the checksums to on the site, but I have a Windows machine. Any hints on how to check? http://www.pc-tools.net/win32/md5sums/ -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: 7.1 64 bit
Gal Lis wrote: I burned another copy, using another ISO whose checksum comes out ok, and it still isn't loading. What else can I be doing wrong? From: Bill Moran wmo...@potentialtech.com To: Gal Lis gal_...@yahoo.com Cc: FreeBSD Questions freebsd-questions@freebsd.org Sent: Wednesday, March 18, 2009 9:30:09 AM Subject: Re: 7.1 64 bit In response to Gal Lis gal_...@yahoo.com: Hi Frank, Thanks for the reply, I see what to compare the checksums to on the site, but I have a Windows machine. Any hints on how to check? http://www.pc-tools.net/win32/md5sums/ First you need to isolate the problem. As someone else suggested, try booting another computer with the disk. Check BIOS boot order to make sure it checks cd drive first. Try another bootable disk in system. I've seen lockups in booting off install disc, but the only situations in which a system would fail to attempt to boot off of it is when either media or drive is bad. If all else fails I believe there is a process to boot from flash drive and install via that method. -- Adam Vandemore Systems Administrator IMED Mobility (605) 498-1610 ___ 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: 7.1 64 bit
On Wed, Mar 18, 2009 at 6:22 PM, Gal Lis gal_...@yahoo.com wrote: Sorry to ask these mundane questions, but I'm a linux novice. Linux != FreeBSD ___ 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: 7.1 64 bit
On Wed, Mar 18, 2009 at 08:28:22PM +0200, Ross Cameron wrote: On Wed, Mar 18, 2009 at 6:22 PM, Gal Lis gal_...@yahoo.com wrote: Sorry to ask these mundane questions, but I'm a linux novice. Linux != FreeBSD But, the OP will still probably get better information on the FreeBSD lists than over there. If it is a UNIX question, it might be relevant anyway. jerry ___ 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 ___ 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: 7.1 64 bit
I guess that shows just how unexperienced I am with all of this. On Wed, Mar 18, 2009 at 11:28 AM, Ross Cameron abal...@gmail.com wrote: On Wed, Mar 18, 2009 at 6:22 PM, Gal Lis gal_...@yahoo.com wrote: Sorry to ask these mundane questions, but I'm a linux novice. Linux != FreeBSD ___ 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: 7.1 64 bit
anyway - you SOMEHOW got into that list and not linux one. So you must know something about FreeBSD anyway :) On Wed, 18 Mar 2009, Gal Lis wrote: I guess that shows just how unexperienced I am with all of this. On Wed, Mar 18, 2009 at 11:28 AM, Ross Cameron abal...@gmail.com wrote: On Wed, Mar 18, 2009 at 6:22 PM, Gal Lis gal_...@yahoo.com wrote: Sorry to ask these mundane questions, but I'm a linux novice. Linux != FreeBSD ___ 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 ___ 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: 7.1 64 bit
You said 32-bits 6.4 could be loaded . A question coming to mind is Can your processor handle 64-bits ? Please check this issue . Thank you very much . Mehmet Erol sanliturk On Wed, Mar 18, 2009 at 2:29 PM, Gal Lis galg...@gmail.com wrote: I guess that shows just how unexperienced I am with all of this. ___ 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: 7.1 64 bit
They should definitely support it. My workstation has an Intel E5320 quad core, and the M600 has a 5400 series chip, but I can't remember which one exactly. They should definitely be able to handle it. I downloaded the 7.1 ia64, maybe there is something else I should be downloading? On Wed, Mar 18, 2009 at 11:53 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: You said 32-bits 6.4 could be loaded . A question coming to mind is Can your processor handle 64-bits ? Please check this issue . Thank you very much . Mehmet Erol sanliturk On Wed, Mar 18, 2009 at 2:29 PM, Gal Lis galg...@gmail.com wrote: I guess that shows just how unexperienced I am with all of this. ___ 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: 7.1 64 bit
Gal Lis wrote: They should definitely support it. My workstation has an Intel E5320 quad core, and the M600 has a 5400 series chip, but I can't remember which one exactly. They should definitely be able to handle it. I downloaded the 7.1 ia64, maybe there is something else I should be downloading? You should be going for the AMD64 unless that's an itanium based instruction set. I believe your CPU is not, so try w/ AMD64. -- Adam Vandemore Systems Administrator IMED Mobility (605) 498-1610 ___ 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: 7.1 64 bit
Well that explains a lot. I will try it and report back. Thanks to everyone for your help so far! On Wed, Mar 18, 2009 at 12:12 PM, Adam Vandemore amvandem...@gmail.comwrote: Gal Lis wrote: They should definitely support it. My workstation has an Intel E5320 quad core, and the M600 has a 5400 series chip, but I can't remember which one exactly. They should definitely be able to handle it. I downloaded the 7.1 ia64, maybe there is something else I should be downloading? You should be going for the AMD64 unless that's an itanium based instruction set. I believe your CPU is not, so try w/ AMD64. -- Adam Vandemore Systems Administrator IMED Mobility (605) 498-1610 ___ 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: 7.1 64 bit
ia64 is for Itanium processor . Therefore ia64 can NOT work on Intel Pentium series processors . Their architectures are different . You should download amd64 ISO . amd64 is for both Intel 64 bits and AMD 64 bits pocessors compatible to each other . On Wed, Mar 18, 2009 at 2:58 PM, Gal Lis galg...@gmail.com wrote: They should definitely support it. My workstation has an Intel E5320 quad core, and the M600 has a 5400 series chip, but I can't remember which one exactly. They should definitely be able to handle it. I downloaded the 7.1 ia64, maybe there is something else I should be downloading? On Wed, Mar 18, 2009 at 11:53 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: You said 32-bits 6.4 could be loaded . A question coming to mind is Can your processor handle 64-bits ? Please check this issue . Thank you very much . Mehmet Erol sanliturk On Wed, Mar 18, 2009 at 2:29 PM, Gal Lis galg...@gmail.com wrote: I guess that shows just how unexperienced I am with all of this. ___ 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: 7.1 64 bit
Thanks for that, I'm sorry I didn't mention what version I downloaded earlier. I will reply once I test it out. On Wed, Mar 18, 2009 at 12:31 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: ia64 is for Itanium processor . Therefore ia64 can NOT work on Intel Pentium series processors . Their architectures are different . You should download amd64 ISO . amd64 is for both Intel 64 bits and AMD 64 bits pocessors compatible to each other . On Wed, Mar 18, 2009 at 2:58 PM, Gal Lis galg...@gmail.com wrote: They should definitely support it. My workstation has an Intel E5320 quad core, and the M600 has a 5400 series chip, but I can't remember which one exactly. They should definitely be able to handle it. I downloaded the 7.1 ia64, maybe there is something else I should be downloading? On Wed, Mar 18, 2009 at 11:53 AM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: You said 32-bits 6.4 could be loaded . A question coming to mind is Can your processor handle 64-bits ? Please check this issue . Thank you very much . Mehmet Erol sanliturk On Wed, Mar 18, 2009 at 2:29 PM, Gal Lis galg...@gmail.com wrote: I guess that shows just how unexperienced I am with all of this. ___ 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: 7.1 phpmyadmin skip logon screen?
Matthew Seaman wrote: Fbsd1 wrote: In 7.1 phpmyadmin now drops you into a logon screen. How do I stop this function and always go to main menu screen? That's nothing to do with the FreeBSD version -- phpMyAdmin works the same on any platform. To make phpMyAdmin auto-login to a DB, you need to use 'config' authentication mode. http://www.phpmyadmin.net/documentation/#authentication_modes It's probably the least secure authentication mode provided, so you should take further steps in your Apache config to stop the world gaining access to your database. Cheers, Matthew Read the user id info on mysql and phpmyadmin. It's so much overkill. Don't need to secure then at all. I have inhouse development box on private lan and mysql has always worked just fine with superuser mysql id of root without password. In the previous version of phpmyadmin no login id was required and I was able to see my DB definitions. Tried to setup config.inc.php by adding statement $cfg['Servers'][$i]['user'] = 'root'; but no joy. What is needed in config.inc.php to allow the default mysql superuser user id root full access in phpmyadmin? ___ 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: 7.1 64 bit
On Tue, Mar 17, 2009 at 10:25:34AM -0700, Gal Lis wrote: Hello, I have tried installing 7.1 64 bit onto a Dell M600 in an M1000E enclosure for a client, and the 7.1 disk does not boot. Is there anything you can recommend? I have installed 6.4 32 bit onto it with no issues. Thank you. I'd investigate why your 7.1 AMD64 disk doesn't boot. How did you burn it? Did you checksum the image before burning? Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ 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: 7.1 64 bit
On Tue, Mar 17, 2009 at 1:25 PM, Gal Lis gal_...@yahoo.com wrote: Hello, I have tried installing 7.1 64 bit onto a Dell M600 in an M1000E enclosure for a client, and the 7.1 disk does not boot. Is there anything you can recommend? I have installed 6.4 32 bit onto it with no issues. Can you try to boot the disc on a different machine? -- Glen Barber ___ 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: 7.1 64 bit
On Tue, Mar 17, 2009 at 04:08:25PM -0700, Gal Lis wrote: Hi Frank and Glen, I tried both disks on my workstation, and 6.4 started up, but there was nothing from 7.1, so maybe my copy is bad. I burned it using imgburn, and i also have magiciso. How can I check to make sure the file is correct? I've never checksumed anything, and haven't been able to find any help online on how to do so. Look here: http://www.freebsd.org/releases/7.1R/announce.html The checksums are listed there. For you to checksum your iso, you do this on a unix/linux machine: $ md5 7.1-RELEASE-amd64-disc1.iso and compare the checksum printed to that published on that page. If the checksum is different, then you got some corruption and need to download the image again. My guess is that the software you used didn't burn the iso correctly. Load up 6.4 and burn your CD from there, something like the following should do it: # burncd -f /dev/acd0 data 7.1-RELEASE-amd64-disc1.iso fixate Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ 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: 7.1 phpmyadmin skip logon screen?
Fbsd1 wrote: In 7.1 phpmyadmin now drops you into a logon screen. How do I stop this function and always go to main menu screen? That's nothing to do with the FreeBSD version -- phpMyAdmin works the same on any platform. To make phpMyAdmin auto-login to a DB, you need to use 'config' authentication mode. http://www.phpmyadmin.net/documentation/#authentication_modes It's probably the least secure authentication mode provided, so you should take further steps in your Apache config to stop the world gaining access to your database. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: 7.1-release and KDE4
On Thu, Mar 5, 2009 at 4:08 PM, joel perry finnd...@gmail.com wrote: Attempting to pkg_add kde4 fails because the lame3.97_1.tgz is not located in the latest ftp location. I and many others would appreciate it if you would add lame to latest folder so that this package will install. It was previously available in the 7.0 release. -- Joel Perry SBSC Registered Microsoft Partner 803.800.5650 Lame was available on the ftp site? Are you sure? I thought lame was one of the packages that couldn't be distributed in binary form due to license restrictions. Andrew ___ 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: 7.1-release and KDE4
On Thu, 5 Mar 2009 18:43:42 -0600, Andrew Gould andrewlylego...@gmail.com wrote: I thought lame was one of the packages that couldn't be distributed in binary form due to license restrictions. In the past, it really was. But I think it was possible to add it via pkg_add. It's some time ago, but memory serves me right, I did pkg_add -r lame because it was possible... if there was a way to find out if some software has been installed via port OR package, I could find this out. :-) Because of the few dependencies, it's no problem to use the port to install it first, then pkg_add -r the KDE 4 packages. Maybe install nasm prior to make. The Makefile of lame still states: RESTRICTED= patent issues, see http://www.mp3licensing.com/ If licensing problems are still present, there may be no way to put a precompiled package onto the FTP server. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
Hi Mel, Sorry for not getting back to you earlier, I have been out of the office for some time... Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab The UP message came more or less at the same time. Marking it late fixed the problem, still leaving me puzzled why the NFS mounts work without problem on identical machines but not in this one. Anyhow, since it's not a critical fs, the late option works fine. Thanks. -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78 Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
On Tuesday 10 February 2009 01:34:47 Arjan van der Oest wrote: Hi Mel, Sorry for not getting back to you earlier, I have been out of the office for some time... Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab The UP message came more or less at the same time. Marking it late fixed the problem, still leaving me puzzled why the NFS mounts work without problem on identical machines but not in this one. Anyhow, since it's not a critical fs, the late option works fine. There's 2 scenarios for late NFS mounting: - local named: named gets started after mountcritremote, fixable with resolv.conf that has an additional nameserver or populate /etc/hosts. - slow network card and/or DHCP server causing the network card to be down or without IP address / invalid resolv.conf at mountcritremote. Not really fixable. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ 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: 7.1 release / apache22 / php5
LS, I hav e the same problem with 7.0 release. The libphp5.so is placed by the php5 port. When you deinstall php5, make clean, make config (check apache module), make install,...the libphp5.so is placed in the libexec directory. Or with clean installation, first install apache22 then php5. Danny van der Schaft - Original Message - From: Glen Barber glen.j.bar...@gmail.com To: Jim Pazarena fqu...@ccstores.com; freebsd-questions@freebsd.org Sent: Tuesday, January 06, 2009 3:33 AM Subject: Re: 7.1 release / apache22 / php5 stan wrote: On Mon, Jan 05, 2009 at 04:52:10PM -0800, Jim Pazarena wrote: for some odd reason, with this latest install (7.1), apache22 complains that it cannot find libphp5.so I usually compile php5 from ports and apache22 from ports after I think about it, I have never actually placed libphp5.so anywhere. I am not even sure who/what causes php5 module to be added to /usr/local/libexec/apache22/libphp5.so it's present on my 7.0 system, and missing on my 7.1 system. advice would be much appreciated. I don't know if it's a change, but on the 7.1 machine I just built. the lang/php5 port was not configured by default to build the Apache module. It's been that way as far as I can remember (at least since 6.2-RELEASE). -- Glen Barber ___ 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.2/1874 - Release Date: 4-1-2009 16:32 ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
Mel wrote: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. Yes, but I am not. I'm using the default kernel option which I believe is enabled with the mentioned rc.conf switch, or am I wrong here? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Looks more like the server is not sending a success message or it got lost in transit. If this is 100% reproducable, look into compatibility issues, by scaling down the NFS version for the mount and check firewall rules on both ends. Firewall has been disabled and seems not the problem, since (even with the firewall enabled) the manual mount works fine. In case of fw problems this would be a problem too. Also what puzzles me is the fact that a new identical setup box has no problem. As I wrote earlier the only difference is that I did not select the 'enable nfs client' from the sysinstall this time. I have not used any of the mentioned flags on the second box too, so why does it work on that machine? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution
I've done some further investigation and this is what happens: The mountcritremote script executes mount -a -t nfs and times out. If this script is aborted, the NFS export is mounted later by the mountlate script with mount -a -l, this succeeds. This is the reason that the export is mounted after sending ctrl-d, the initial mount never succeeds. From what I can see now this is neither a firewall nor a NFS-version issue, else it would not succeed in the mountlate script. I'm still puzzled why on other boxes this is not a problem, while it is at this box. -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78 -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Arjan van der Oest Sent: vrijdag 30 januari 2009 14:36 To: Mel; freebsd-questions@freebsd.org Subject: RE: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution Mel wrote: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. Yes, but I am not. I'm using the default kernel option which I believe is enabled with the mentioned rc.conf switch, or am I wrong here? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Looks more like the server is not sending a success message or it got lost in transit. If this is 100% reproducable, look into compatibility issues, by scaling down the NFS version for the mount and check firewall rules on both ends. Firewall has been disabled and seems not the problem, since (even with the firewall enabled) the manual mount works fine. In case of fw problems this would be a problem too. Also what puzzles me is the fact that a new identical setup box has no problem. As I wrote earlier the only difference is that I did not select the 'enable nfs client' from the sysinstall this time. I have not used any of the mentioned flags on the second box too, so why does it work on that machine? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.15/1924 - Release Date: 1/29/2009 5:57 PM Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
On Friday 30 January 2009 04:36:04 Arjan van der Oest wrote: Mel wrote: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. Yes, but I am not. I'm using the default kernel option which I believe is enabled with the mentioned rc.conf switch, or am I wrong here? Yes, but why should mount(8) check /etc/rc.conf? The relation is reverse, rc(8) should give services the right(tm) arguments. And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it Also what puzzles me is the fact that a new identical setup box has no problem. As I wrote earlier the only difference is that I did not select the 'enable nfs client' from the sysinstall this time. I have not used any of the mentioned flags on the second box too, so why does it work on that machine? Does this one also have a link UP message after nfs mounting? If not, then there's your culprit: network isn't up at mountcritremote time. You should mark it 'late' in fstab. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution
To make it even stranger, a new fresh installed box has no problems with this configuration. The difference between these two : on the problem box I enabled NFS client during installation with sysinstall, on the working box I've just added the nfs_client_enable=YES flag manually to rc.conf. I would suspect that the sysinstall approach would do the same (as it looks like it) but now I suspect sysinstall does something else too that breaks the config. -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 E.: arjan.van.der.o...@worldmax.nl W.:www.worldmax.nl W.:www.aerea.nl GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78 -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Arjan van der Oest Sent: donderdag 29 januari 2009 10:48 To: freebsd-questions@freebsd.org Subject: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution Hi, I’m puzzled and either I don’t understand the boot rc.d process or there is something wrong with it ☺ I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so NFS support is baked right into the kernel by default. In fsstab I have this entry: nfs server ip:/data/nfs-shares/S1018SR18 /nfs-mounts/backupsrv nfs rw00 Further, as per the handbook, I’ve set nfs_client_enable to “YES” in the rc.conf. During boottime the machine hangs on the console after stating “Mounting NFS filesystems:”. I notice that _immediately_ after that line there is a console message saying “em0: link state changed to UP”. Then the system repeats this line until eternity (well, the max I’ve been waiting has been 30 minutes), no . appears indicating the system has not yet completed the 'mount -a 't nfs' command from the mountcritremote script. [udp] nfs server ip:/data/nfs-shares/S1018SR18: RPGPROC_MNT: RPC: Timed out Hitting CTRL-C forces the machine to continue the boot process, aborting the mountcritremote script. What strikes me is that the actual NFS share has been mounted, although the boot-process seems to indicate otherwise... After doing a umount and mount –a –t nfs again the machine has no problem whatsoever. Something else that puzzles me, when I set the nfs_client_enable=”NO” line in the rc.conf, the same happens : console hangs on the mountcritremote script until I hit CTRL-C and after that the share has been mounted anyway? Shouldn’t the machine ignore nfs filesystems with this rc.conf config? I’ve removed the entry in fstab and set a line in rc.local and then the boot-process works fine without interruption. So I'm currently lost with these questions: - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? - why does the system seems to hang on the mountcritremote script although there seems no valid reason for that. I can imagine the network has not been fully configured yet when executing (indicated by the link UP message right after the mouning NFS filesystems line) but why will the script not continue after a few timeouts? And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Any fingerpoints? -- Met vriendelijke groet / Kind Regards, Worldmax Operations B.V. Arjan van der Oest Network Design Engineer T.: +31 (0) 88 001 7912 F.: +31 (0) 88 001 7902 M.: +31 (0) 6 10 62 58 46 GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F 3AE2 0A8B 7579 75A9 169F 5D9E 5312 0728 6F78) No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.15/1921 - Release Date: 1/28/2009 6:37 AM Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail. ___ 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: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during mountcritremote execution
On Thursday 29 January 2009 00:47:49 Arjan van der Oest wrote: Hi, I’m puzzled and either I don’t understand the boot rc.d process or there is something wrong with it ☺ I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so NFS support is baked right into the kernel by default. In fsstab I have this entry: nfs server ip:/data/nfs-shares/S1018SR18 /nfs-mounts/backupsrv nfs rw00 - why does the system tries to mount the nfs filesystem from the fstab while nfs_client_enable has been set to no in rc.conf? Because there is no relation between the two. You could be using a 3rd party nfs kernel module. - why does the system seems to hang on the mountcritremote script although there seems no valid reason for that. I can imagine the network has not been fully configured yet when executing (indicated by the link UP message right after the mouning NFS filesystems line) but why will the script not continue after a few timeouts? Because you are not aware of the following mount_nfs flags, you can put in /etc/fstab: -b If an initial attempt to contact the server fails, fork off a child to keep trying the mount in the background. Useful for fstab(5), where the file system mount is not critical to multi- user operation. -R Set the mount retry count to the specified value. The default is a retry count of zero, which means to keep retrying forever. There is a 60 second delay between each attempt. -i Make the mount interruptible, which implies that file system calls that are delayed due to an unresponsive server will fail with EINTR when a termination signal is posted for the process. -s A soft mount, which implies that file system calls will fail after retrycnt round trip timeout intervals. And more bizarre: when interrupting the mountcritremote script the share has been actually mounted, so it seems the 'mount -a -t nfs' command has actually been executed successfully. Looks more like the server is not sending a success message or it got lost in transit. If this is 100% reproducable, look into compatibility issues, by scaling down the NFS version for the mount and check firewall rules on both ends. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ 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: 7.1 : watchdog bge0 timeout ?
I'm gonna retry installing 7.1 today on a different hardware machine ( an older one ) let's see what happen then. Frank Bonnet wrote: Jos Chrispijn wrote: [Lowell Gilbert] Uit een eerder bericht van 10-1-2009 15:51 :: Could be hardware trouble, I suppose. I know FreeBSD can detect hardware probs better than other OS'es; but why didn't 6.x detect this malfunction then? I believe Murphy and his law, but for mee it seems a little bit too accidentally L-) regards, Jos Chrispijn Well I have re-install the machine at 6.4 and it runs WITHOUT any trouble with exactly same softwares ( OS + Postfix + Postgrey ) At 7.1 the machine hanged after running few hours ( ~2 ) At 6.4 it runs since 3 days without problem. ___ 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 -- Cordialement Frank Bonnet ESIEE Paris ___ 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: 7.1 : watchdog bge0 timeout ?
Jos Chrispijn wrote: [Lowell Gilbert] Uit een eerder bericht van 10-1-2009 15:51 :: Could be hardware trouble, I suppose. I know FreeBSD can detect hardware probs better than other OS'es; but why didn't 6.x detect this malfunction then? I believe Murphy and his law, but for mee it seems a little bit too accidentally L-) regards, Jos Chrispijn Well I have re-install the machine at 6.4 and it runs WITHOUT any trouble with exactly same softwares ( OS + Postfix + Postgrey ) At 7.1 the machine hanged after running few hours ( ~2 ) At 6.4 it runs since 3 days without problem. ___ 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: 7.1 : watchdog bge0 timeout ?
[Lowell Gilbert] Uit een eerder bericht van 10-1-2009 15:51 :: Could be hardware trouble, I suppose. I know FreeBSD can detect hardware probs better than other OS'es; but why didn't 6.x detect this malfunction then? I believe Murphy and his law, but for mee it seems a little bit too accidentally L-) regards, Jos Chrispijn ___ 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: 7.1 : watchdog bge0 timeout ?
Frank Bonnet f.bon...@esiee.fr writes: I've installed 7.1 onto our mail exchager (MX) then it suddendly stopped to work last night with the following message watchdog bge0 timeout The machine is a HP pc which was doing the same service at 6.3 without that kind of trouble Could be hardware trouble, I suppose. The whole point of a watchdog is to let the driver recover after the hardware has locked up. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: 7.1 release / apache22 / php5
On Mon, Jan 5, 2009 at 7:52 PM, Jim Pazarena fqu...@ccstores.com wrote: for some odd reason, with this latest install (7.1), apache22 complains that it cannot find libphp5.so I usually compile php5 from ports and apache22 from ports after I think about it, I have never actually placed libphp5.so anywhere. I am not even sure who/what causes php5 module to be added to /usr/local/libexec/apache22/libphp5.so it's present on my 7.0 system, and missing on my 7.1 system. advice would be much appreciated. Do you have something like: LoadModule php5_modulelibexec/apache22/libphp5.so in /usr/local/etc/apache22/httpd.conf ? If not, that's the likely culprit. You'd also need the IfModule mod_php5.c ... /IfModule block in there as well (or in an included file). Regards, Josh ___ 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: 7.1 release / apache22 / php5
Josh Carroll wrote: On Mon, Jan 5, 2009 at 7:52 PM, Jim Pazarena fqu...@ccstores.com wrote: for some odd reason, with this latest install (7.1), apache22 complains that it cannot find libphp5.so I usually compile php5 from ports and apache22 from ports after I think about it, I have never actually placed libphp5.so anywhere. I am not even sure who/what causes php5 module to be added to /usr/local/libexec/apache22/libphp5.so it's present on my 7.0 system, and missing on my 7.1 system. advice would be much appreciated. Do you have something like: LoadModule php5_modulelibexec/apache22/libphp5.so in /usr/local/etc/apache22/httpd.conf ? If not, that's the likely culprit. You'd also need the IfModule mod_php5.c ... /IfModule block in there as well (or in an included file). Regards, Josh the httpd config file isn't the issue. it hasn't changed in a few years. yes, I do have the correct entries. what I do NOT have is the actual libphp5.so library file! it doesn't exist on my system, so apache complains that it can't open it. -- Jim Pazarena fqu...@ccstores.com ___ 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: 7.1 release / apache22 / php5
On Mon, Jan 5, 2009 at 7:52 PM, Jim Pazarena fqu...@ccstores.com wrote: for some odd reason, with this latest install (7.1), apache22 complains that it cannot find libphp5.so I usually compile php5 from ports and apache22 from ports after I think about it, I have never actually placed libphp5.so anywhere. I am not even sure who/what causes php5 module to be added to /usr/local/libexec/apache22/libphp5.so it's present on my 7.0 system, and missing on my 7.1 system. advice would be much appreciated. Did you remember to build the apache module when compiling php5? -- Glen Barber Tell me and I forget. Teach me and I remember. Involve me and I learn. - Benjamin Franklin ___ 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: 7.1 release / apache22 / php5
the httpd config file isn't the issue. it hasn't changed in a few years. yes, I do have the correct entries. what I do NOT have is the actual libphp5.so library file! it doesn't exist on my system, so apache complains that it can't open it. Did you build the lang/php5 port with the Build Apache module option checked via make config? make -C /usr/ports/lang/php5 showconfig | grep APACHE Should return: APACHE=on Build Apache module If not, make config in there, check that option, then rebuild and reinstall the port. Josh ___ 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: 7.1 release / apache22 / php5
On Mon, Jan 05, 2009 at 04:52:10PM -0800, Jim Pazarena wrote: for some odd reason, with this latest install (7.1), apache22 complains that it cannot find libphp5.so I usually compile php5 from ports and apache22 from ports after I think about it, I have never actually placed libphp5.so anywhere. I am not even sure who/what causes php5 module to be added to /usr/local/libexec/apache22/libphp5.so it's present on my 7.0 system, and missing on my 7.1 system. advice would be much appreciated. I don't know if it's a change, but on the 7.1 machine I just built. the lang/php5 port was not configured by default to build the Apache module. -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs. ___ 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: 7.1 release / apache22 / php5
stan wrote: On Mon, Jan 05, 2009 at 04:52:10PM -0800, Jim Pazarena wrote: for some odd reason, with this latest install (7.1), apache22 complains that it cannot find libphp5.so I usually compile php5 from ports and apache22 from ports after I think about it, I have never actually placed libphp5.so anywhere. I am not even sure who/what causes php5 module to be added to /usr/local/libexec/apache22/libphp5.so it's present on my 7.0 system, and missing on my 7.1 system. advice would be much appreciated. I don't know if it's a change, but on the 7.1 machine I just built. the lang/php5 port was not configured by default to build the Apache module. It's been that way as far as I can remember (at least since 6.2-RELEASE). -- Glen Barber ___ 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: 7.1 RC1 - problems with Intel Pro/1000 NIC (em0)?
Ewald Jenisch wrote: Hi, After installing FreeBSD 7.1 RC1 from the DVD-image I found that the PC in question has no LAN connectivity upon reboot. The PC has an Intel GE builtin NIC showing up as Intel PRO/1000 Network Connection 6.9.6 in dmesg. For the problem: Though IP-Adress, default-GW etc. are correctly set the box can't e.g. ping anything on the net; neither on the local lan nor across the default-gw. Same the other way round: machine can't be ping-ed, not even from the local subnet. What's interesting though is that on both the LAN-Switch and the PC (ifconfig) the interface shows up as connected. Even more interesting: the MAC-address of the PC-nic shows up on the corresponding LAN-Switch. So there definitely is some form of connectivity. When starting a tcpdump there's no output - so obviously nothing is coming into the machine form the network. To cross-check I've a) swapped the patch-cable for another one - no change b) tried Ubuntu (Linux) from the Live-CD - under Ubuntu I've got full LAN-connectivity without any problems so it must be something FreeBSD related... Has anybody out there had problems with an Intel GE-Nic (em0) under 7.1? Thanks in advance for any clue, -ewald ___ There was a note on the intel em chipset. most of them are being renamed to igb, that could be part of the problem. You may need to check the hardware notes. ___ 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: 7.1 - with x.org 7.4?
On Tue, Dec 09, 2008 at 02:17:27PM +0100, Ewald Jenisch wrote: Hi, Does anybody out there know if FreeBSD 7.1 will come out with X.org 7.4 (or still 7.3)? Thanks much in advance for any clue, -ewald X.org 7.4 has not been imported into the ports system yet, and this far into the release process it is too late to update such an important port - too much risk of something going wrong. The X.org port(s) will probably be updated to 7.4 not too long after FreeBSD 7.1 has been released and the dust has settled. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! (Re: 7.1)
Ott Köstner wrote: I had my workstation running 7.0-STABLE. Perfectly well till today. Now I compiled and installed the latest 7.1-PRERELEASE and now Thunderbird and Firefox got really SLOW. Everything works, but Xorg is consuming time constatnly. Scrolling inbox is especially slow. Asked the question and... answering it by my self... ;) Seems that rebuiding Nvidia 'Quadro4 380 XGL' driver solved the problem. Could it be? Anyway, it's OK now. I also rebuilt the Thunderbird. Greetings, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
Frank Bonnet wrote: Hello I don't want appears as an impatient and I KNOW people that support FreeBSD are volunteers, I am a long time user of our prefered OS I just would like to have an estimation for the release of 7.1. I have two new production servers that will come tomorrow - If the release is a matter of days I'll wait a bit before installing them, - If it is a matter of monthes I'll install them with another release. Thanks a lot I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
Ott Köstner wrote: Manolis Kiagias wrote: I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Is it better to reinstall 7.0 before something really bad happens, or can I just let it run? What are the most serious bugs to expect? Greetings, O.K. It all depends on the programs you run, your configuration, system load and so on. Bugs that may be present in the system, may simply not be applicable to you, if you are not using the specific part or feature that has the problem. While it is difficult to assess without knowing specific details, I think 7.1 is generally stable at the moment. Maybe people using it in production servers (if any) can step in and share their experiences. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
On Monday 17 November 2008 13:01:53 Ott Köstner wrote: Manolis Kiagias wrote: I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Not very. The -stable branches really are stable, 99% of the time. Just glance through /usr/src/UPDATING. The difference between RELENG_7 now and 7.1 when it comes out, is: - fixing of bugs that you would've noticed already (hardware issues, installer / boot code) - polishing (dotting i's and crossing t's) - even more testing then has been done already - 2 week long security review by the security team - the packages on the cdroms - output of uname -r The release is merely a snapshot of the source tree, that has had more eyes looking at it then normal. There are no guarantees. If your company policy requires you to run releases (+ their updates) on production servers, that would be the only good reason to install 7.0-p5. Otherwise, keep RELENG_7 and once 7.1 comes out, change csup tag to RELENG_7_1, recompile and you're done. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
Manolis Kiagias wrote: I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Is it better to reinstall 7.0 before something really bad happens, or can I just let it run? What are the most serious bugs to expect? Greetings, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
Manolis Kiagias wrote: Ott Köstner wrote: Manolis Kiagias wrote: I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Is it better to reinstall 7.0 before something really bad happens, or can I just let it run? What are the most serious bugs to expect? Greetings, O.K. It all depends on the programs you run, your configuration, system load and so on. Bugs that may be present in the system, may simply not be applicable to you, if you are not using the specific part or feature that has the problem. While it is difficult to assess without knowing specific details, I think 7.1 is generally stable at the moment. Maybe people using it in production servers (if any) can step in and share their experiences. I have just regular internet things running: apache22, mysql5, bind94, php5, postfix, dovecot, proftpd, clamav, spamassasin, snmpd... ...plus ipfw and pf Actually there is one strange thing what I described here before -- 'top' reporting incorrect process times. But this appeared already when I upgraded from FreBSD 6.3 to 7.0. The bug appears on all 7.++ machines, i386 and amd64. Everything is OK with single-threaded processes, but processes with multiple threades are reported incorrectly by top. Anybody else has experienced this? Also, there was a strange phenomenon with FreeBSD router with pf. the rule in question is: 'scrub in all' I do not knw, if this has anything to do with 7.1 issue. Maybe it is not just a good idea to have a 'scrub' rule on router... Greetings, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
On Mon, Nov 17, 2008 at 02:49:26PM +0200, Ott Köstner wrote: Manolis Kiagias wrote: Ott Köstner wrote: Manolis Kiagias wrote: I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Is it better to reinstall 7.0 before something really bad happens, or can I just let it run? What are the most serious bugs to expect? Greetings, O.K. It all depends on the programs you run, your configuration, system load and so on. Bugs that may be present in the system, may simply not be applicable to you, if you are not using the specific part or feature that has the problem. While it is difficult to assess without knowing specific details, I think 7.1 is generally stable at the moment. Maybe people using it in production servers (if any) can step in and share their experiences. I have just regular internet things running: apache22, mysql5, bind94, php5, postfix, dovecot, proftpd, clamav, spamassasin, snmpd... ...plus ipfw and pf I'm not sure why you're paranoid of 7.1-PRERELEASE (RELENG_7 at the present time). It seems like you installed it or upgraded to it, then became greatly concerned for strange reasons. I really don't think you have anything to worry about. The only gigantic difference, as I see it, is that the ULE scheduler is now the default (while in 7.0, 4BSD was default). I personally run all of the above services (minus bind94, clamav, and snmpd; I use the base system bind, do not care for AV software, and use bsnmpd where applicable), and I also run all of those services on servers in my co-location. We have a RELENG_7 box which is working fine doing all of the above, on a dual-core processor to boot. Actually there is one strange thing what I described here before -- 'top' reporting incorrect process times. But this appeared already when I upgraded from FreBSD 6.3 to 7.0. The bug appears on all 7.++ machines, i386 and amd64. Everything is OK with single-threaded processes, but processes with multiple threades are reported incorrectly by top. Anybody else has experienced this? Sounds familiar (not personally). There are efforts underway in CURRENT to improve top. I would recommend posting your top problem to -stable or -hackers. Also, there was a strange phenomenon with FreeBSD router with pf. the rule in question is: 'scrub in all' I do not knw, if this has anything to do with 7.1 issue. Maybe it is not just a good idea to have a 'scrub' rule on router... No, it's perfectly fine. But your description of the problem is too terse, and the issue should be discussed on freebsd-pf not here. There *are* other problems with pf which have been fixed in RELENG_7 (7.1), and you can review my Wiki to see what those are. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 02:49:26PM +0200, Ott Köstner wrote: Also, there was a strange phenomenon with FreeBSD router with pf. the rule in question is: 'scrub in all' I do not knw, if this has anything to do with 7.1 issue. Maybe it is not just a good idea to have a 'scrub' rule on router... No, it's perfectly fine. But your description of the problem is too terse, and the issue should be discussed on freebsd-pf not here. OK. Thank you! Will subscribe to pf list. Just to finish this talk, the problem was with 'pop3s' protocol. Removing 'scrub' rule from firewall made it work perfectly well... There *are* other problems with pf which have been fixed in RELENG_7 (7.1), and you can review my Wiki to see what those are. ...and what is the address of this Wiki? Greetings, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
On Mon, Nov 17, 2008 at 04:09:15PM +0200, Ott Köstner wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 02:49:26PM +0200, Ott Köstner wrote: Also, there was a strange phenomenon with FreeBSD router with pf. the rule in question is: 'scrub in all' I do not knw, if this has anything to do with 7.1 issue. Maybe it is not just a good idea to have a 'scrub' rule on router... No, it's perfectly fine. But your description of the problem is too terse, and the issue should be discussed on freebsd-pf not here. OK. Thank you! Will subscribe to pf list. Just to finish this talk, the problem was with 'pop3s' protocol. Removing 'scrub' rule from firewall made it work perfectly well... There *are* other problems with pf which have been fixed in RELENG_7 (7.1), and you can review my Wiki to see what those are. ...and what is the address of this Wiki? Wow, I figured by now everyone had it. That's what I get for assuming. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help! (Re: 7.1)
Manolis Kiagias wrote: You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. Hi! I had my workstation running 7.0-STABLE. Perfectly well till today. Now I compiled and installed the latest 7.1-PRERELEASE and now Thunderbird and Firefox got really SLOW. Everything works, but Xorg is consuming time constatnly. Scrolling inbox is especially slow. Recompile Xorg, Thunderbird??? Any help available? CPU: 6.8% user, 0.0% nice, 10.9% system, 0.4% interrupt, 82.0% idle Mem: 329M Active, 310M Inact, 139M Wired, 2696K Cache, 112M Buf, 1214M Free Swap: 2000M Total, 2000M Free PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 998 root 1 610 239M 160M select 0 5:42 16.36% Xorg 11866 ott 3 960 75596K 66008K ucond 0 0:00 8.40% opera 9280 ott 7 440 76156K 62604K ucond 0 0:00 0.98% thunderbird-bin Greetings, O.K. -- Testi oma Interneti kiirust / Test Your Internet speed: http://speedtest.zzz.ee/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
Ott Köstner [EMAIL PROTECTED] writes: I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Is it better to reinstall 7.0 before something really bad happens, or can I just let it run? What are the most serious bugs to expect? In addition to what others have said, note that there are numerous issues that have been fixed since 7.0. The most serious issues have been fixed for 7.0 (in the security branch), but there is still a good chance that you will have *fewer* problems with what you installed. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1
On Mon, Nov 17, 2008 at 02:01:53PM +0200, Ott Köstner wrote: Manolis Kiagias wrote: I don't think it is a matter of days, we have not even reached RC status yet on 7.1 On a production server you will probably wish to go with 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of freebsd-update(8) when it is released. You probably don't want to risk 7.1-PRERELEASE on a server, but for anyone running workstations, desktops, laptops I think it is worth trying at this moment. I am a person, who made a mistake, installing 7.1 on my production server (actually RELENG_7 stable, which shows up as 7.1). My question is, how stupid is that mistake? Is it better to reinstall 7.0 before something really bad happens, or can I just let it run? What are the most serious bugs to expect? It is not that big of a problem. I've been tracking -STABLE on my destkop since 5.4 without major problems. Every once in a while you see a failure report for RELENG_7 from the tinderbox build cluster, which can mean that you shouldn't csup at that moment. And rarely there is a report on the stable mailing list that something's broken and you need to wait with updating until it's fixed. The most effort IMHO is switching between major versions because you then need to delete and rebuild all your installed ports. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp6XHpPKYunw.pgp Description: PGP signature
Re: 7.1
Manolis Kiagias wrote: It all depends on the programs you run, your configuration, system load and so on. Bugs that may be present in the system, may simply not be applicable to you, if you are not using the specific part or feature that has the problem. While it is difficult to assess without knowing specific details, I think 7.1 is generally stable at the moment. Maybe people using it in production servers (if any) can step in and share their experiences. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I'm running a 7.1 prerelease from 10-31 on a dual core amd AM2 for mail with spamassassin, postfix, and procmail with a few virtual domains. So far, the only issue I've had is that some new device support was added causing the drive number to change, that was an easy fix once I saw what the issue was. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Final remark: I changed the motherboard in the end but actually I suspect that the reason the install got hung was not the READ BIG MEDIUM ERROR (I got this error also with the new motherboard and the install got past this error and continued), the reason was, that I had an ASUS ST-200 SCSI card (NCR Symbios chipset?) sticking in the system that could have caused all the trouble. Either it was the fact that this card had trouble with FreeBSD anyway (I remember something in this vein) or the card was defective or it was a problem with card and motherboard. Anyway, the problem has resolved. Thanks a lot for the good advice, explanations, tips etc. -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation from floppies - has anyone tried lately?
In the vein of getting a way to install FreeBSD 7.1-BETA2 onto my SATA IDE drive (otherwise still running 5.2.1. from IDE drives) I found in the seek of other methods to bootstrap myself, that the boot floppy hangs after asking for kern1 floppy. Could that be just bad media or could it have another cause. In other words: Has anyone tried to boot from a 7.1-BETA2 floppy set recently? Other suggestion of how to bootstrap me from 5.2.1 to 7.1 are welcome: Doing a cvs-sup ? (Is there still this method of updating FreeBSD? - I've been a while off from the front) Making my SATA drive (/dev/ar0) bootable and putting the contents of the distribution into it? -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. Back at the problem: I chose 3. safe mode to no avail. Still get this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config I even changed the CDROM drive to a very old slow one. I changes IDE busses (first vs. second IDE) to no avail. I'm now gonna burn another medium. No luck yet installing 7.1 BETA2. I'm also a long time FreeBSD user btw, from times where it was called 386bsd :-) -- Christoph -- Christoph Al Plant schrieb: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 This makes the HD and CD to work for me after the install. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Christoph Kukulies schrieb: Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. Back at the problem: I chose 3. safe mode to no avail. Still get this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 I now tried with a 7.0 BETA Boot CD (which I had laying around from possibly another fruitless attempt in the past to update that system from 5.1 or something to 7.x). Same picture. Hangs on this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x21 ascq=0x00 (asc=0x21 at this time FWIW). Please help me in getting FreeBSD onto this machine iin whatever way. -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
On Wed, Nov 05, 2008 at 05:26:38PM +0100, Christoph Kukulies wrote: Christoph Kukulies schrieb: Christoph Kukulies schrieb: Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. Back at the problem: I chose 3. safe mode to no avail. Still get this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 I now tried with a 7.0 BETA Boot CD (which I had laying around from possibly another fruitless attempt in the past to update that system from 5.1 or something to 7.x). Same picture. Hangs on this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x21 ascq=0x00 (asc=0x21 at this time FWIW). This won't help you get FreeBSD installed any quicker, but it will give you some insight to what the error messages mean. ATAPI essentially uses SCSI commands but over an ATA bus, which is why atapicam(4) exists (which is what's giving you the xpt_* errors). The problem is that not all drives are created equal, so some behave differently to certain commands than others. ASC and ASCQ are, in layman's terms, error codes with added degrees of granularity. ASC = Additional Sense Code, ASCQ = Additional Sense Code Qualifier. These are fairly well-documented all over the web, and per T10 specifications. Looking at a chart, specifically noting errors that are for CD (MMC) devices, we find: ASC 0x11, ASCQ 0x00 == Unrecovered Read Error ASC 0x21, ASCQ 0x00 == Logical Block Address (LBA) Out of Range Your first reaction will be So does this mean I have a bad CD?, and the answer is not necessarily. It could be that the drive does not support the commands FreeBSD expects available to read a CD in this particular fashion. But it could also be a badly burned CD, or a CD burned with buggy software. If at all possible, try another CD drive of some kind. Get one from a friend, borrow one, or buy one. People have had good experiences with Plextor and Pioneer drives, while recent Samsung drives have been hit-or-miss. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Jeremy Chadwick schrieb: acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x21 ascq=0x00 (asc=0x21 at this time FWIW). This won't help you get FreeBSD installed any quicker, but it will give you some insight to what the error messages mean. ATAPI essentially uses SCSI commands but over an ATA bus, which is why atapicam(4) exists (which is what's giving you the xpt_* errors). The problem is that not all drives are created equal, so some behave differently to certain commands than others. ASC and ASCQ are, in layman's terms, error codes with added degrees of granularity. ASC = Additional Sense Code, ASCQ = Additional Sense Code Qualifier. These are fairly well-documented all over the web, and per T10 specifications. Looking at a chart, specifically noting errors that are for CD (MMC) devices, we find: ASC 0x11, ASCQ 0x00 == Unrecovered Read Error ASC 0x21, ASCQ 0x00 == Logical Block Address (LBA) Out of Range Your first reaction will be So does this mean I have a bad CD?, and the answer is not necessarily. It could be that the drive does not support the commands FreeBSD expects available to read a CD in this particular fashion. But it could also be a badly burned CD, or a CD burned with buggy software. If at all possible, try another CD drive of some kind. Get one from a friend, borrow one, or buy one. People have had good experiences with Plextor and Pioneer drives, while recent Samsung drives have been hit-or-miss. I'm now at home at a different burner but I probably don't have a different CD recording software other than cdrecord available. that's Windows XP BTW, under which I burnt that CDs. I could prbably boot an older (4.x) FreeBSD on that machine but that would be CD record, too. Medium is also a 80 min 700 MB CD. Weren't they 650 MB in earlier times actually? Earlier times I mean, when I still had my FreeBSD subscription and got each release in a neat CD set :-) Oh well, I will give it another try and see how it works out. Later -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Julien Cigar Belgian Biodiversity Platform http://www.biodiversity.be Université Libre de Bruxelles (ULB) Campus de la Plaine CP 257 Bâtiment NO, Bureau 4 N4 115C (Niveau 4) Boulevard du Triomphe, entrée ULB 2 B-1050 Bruxelles Mail: [EMAIL PROTECTED] @biobel: http://biobel.biodiversity.be/person/show/471 Tel : 02 650 57 52 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Julien Cigar schrieb: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor What I've found is enable/disable IDE Master in the BIOS settings. I disabled it to no avail. Just bought a SATA CD/DVD burner hoping to get along with this. -- Christoph Kukulies (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Julien Cigar schrieb: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor What I've found is enable/disable IDE Master in the BIOS settings. I disabled it to no avail. Just bought a SATA CD/DVD burner hoping to get along with this. Pitfall - SATA CDROM drive is not seen by the BIOS so I cannot boot from it or is there a way to get around this? Any other method to boot from? This motherboard isn't one of the newest, in contrary, quite old. Doesn't seem to support boot from USB device, so I depend on getting the system booted from CDROM. -- Christoph Kukulies -- Christoph Kukulies (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 This makes the HD and CD to work for me after the install. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. -- Christoph Al Plant schrieb: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 This makes the HD and CD to work for me after the install. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that ATA DMA is for hard disks, and ATAPI DMA is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. The READ BIG MEDIUM ERROR often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that ATA DMA is for hard disks, and ATAPI DMA is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. The READ BIG MEDIUM ERROR often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. Aloha Jeremy, Thanks for catching the - vs _ . I hear you, but I have to do the hw settings like above or the servers wont boot they stick at a db or mountroot error I think the 7 and 8 series OS are looking for SATA and dont like the IDE drives I use. I know the atapi setting is for CD's and These are brand new DVD/CD RW burners fwiw. A month or so back there were several people on line complaining about this. Maybe one of the FreeBSD comitters will have a look and see if something is wrong. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
On Tue, Nov 04, 2008 at 12:46:43PM -1000, Al Plant wrote: Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that ATA DMA is for hard disks, and ATAPI DMA is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. The READ BIG MEDIUM ERROR often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. Aloha Jeremy, Thanks for catching the - vs _ . I hear you, but I have to do the hw settings like above or the servers wont boot they stick at a db or mountroot Those are two very different things. A db prompt indicates you're hitting a kernel panic, while a mountroot prompt indicates the OS can't find your root filesystem. I think the 7 and 8 series OS are looking for SATA and dont like the IDE drives I use. I understand, but what I'm saying is that hw.ata.ata-dma=0 (note the hyphen) is not fixing/solving anything, because it contains a typo. I know the atapi setting is for CD's and These are brand new DVD/CD RW burners fwiw. A month or so back there were several people on line complaining about this. Maybe one of the FreeBSD comitters will have a look and see if something is wrong. The I get dropped to a mountroot prompt problem has been reported many times, and so far there haven't been any indications what causes it to happen for people. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 12:46:43PM -1000, Al Plant wrote: Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that ATA DMA is for hard disks, and ATAPI DMA is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. The READ BIG MEDIUM ERROR often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. Aloha Jeremy, Thanks for catching the - vs _ . I hear you, but I have to do the hw settings like above or the servers wont boot they stick at a db or mountroot Those are two very different things. A db prompt indicates you're hitting a kernel panic, while a mountroot prompt indicates the OS can't find your root filesystem. I think the 7 and 8 series OS are looking for SATA and dont like the IDE drives I use. I understand, but what I'm saying is that hw.ata.ata-dma=0 (note the hyphen) is not fixing/solving anything, because it contains a typo. I know the atapi setting is for CD's and These are brand new DVD/CD RW burners fwiw. A month or so back there were several people on line complaining about this. Maybe one of the FreeBSD comitters will have a look and see if something is wrong. The I get dropped to a mountroot prompt problem has been reported many times, and so far there haven't been any indications what causes it to happen for people. _ Aloha Jeremy, The - was not in the installs. I typed it correctly in the several cases where it was used. It will be interesting to see if anybody can find a solution to these issues. I am not a coder just a long time user of FreeBSD, (since 3.*) I think it was. It is such a rock solid system that most of us are curious when something like this happens and its hard to find out why. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1 hangs, shutdown terminated
Johan Hendriks írta: If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem: # sysctl -a | grep dirhash shopzeus# sysctl -a | grep dirhash vfs.ufs.dirhash_docheck: 0 vfs.ufs.dirhash_mem: 2095818 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_minsize: 2560 Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem: All right. It is close to it. Which one should I increase? I put this into /etc/sysctl.conf: vfs.ufs.dirhash_maxmem=8228608 Would it be scufficient? Thanks, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 7.1 hangs, shutdown terminated
Johan Hendriks írta: If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem: # sysctl -a | grep dirhash shopzeus# sysctl -a | grep dirhash vfs.ufs.dirhash_docheck: 0 vfs.ufs.dirhash_mem: 2095818 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_minsize: 2560 Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem: All right. It is close to it. Which one should I increase? I put this into /etc/sysctl.conf: vfs.ufs.dirhash_maxmem=8228608 Would it be scufficient? Thanks, Laszlo vfs.ufs.dirhash_maxmem= is the value to adjust. Mine is at 12582912. this happens on Mailservers 'which has a lot of directorys for the mail. The value depends on how many directory's there are on your system. Keep track on the value and when it hits the limit again increase the limit until it stays under the limit. It can take a while to reach the limit again. Regards, Johan Hendriks Double L Automatisering No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.8.0/1717 - Release Date: 9-10-2008 16:56 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1 hangs, shutdown terminated
On Fri, Oct 10, 2008 at 10:40:01AM +0200, Laszlo Nagy wrote: Hi, A computer hangs every day in the morning at a specific time, between 8 AM and 9 AM. We can ping it. Apparently the console works, also gdm works on it, but we are not able to login at all. ssh accepts connections, but the authentication does not continue (e.g. ssh client waits for the server forever...) I even cannot login on the console as root because it accepts the user name, but does not ask for the password! Pressing Ctrl+Alt+Del on the console waits for about one or two minutes, then I see this on the screen: http://www.imghype.com/viewer.php?imgdata=9d95ee9d1fstrange_shutdown.jpg Here is /var/log/messages just before the crash: Oct 10 01:52:47 shopzeus postgres[81114]: [5-1] WARNING: nonstandard use of escape in a string literal at character 193 Oct 10 01:52:47 shopzeus postgres[81114]: [5-2] HINT: Use the escape string syntax for escapes, e.g., E'\r\n'. Oct 10 01:57:11 shopzeus postgres[84132]: [5-1] WARNING: nonstandard use of escape in a string literal at character 188 Oct 10 01:57:11 shopzeus postgres[84132]: [5-2] HINT: Use the escape string syntax for escapes, e.g., E'\r\n'. Oct 10 02:00:01 shopzeus postfix/postfix-script[86167]: fatal: the Postfix mail system is already running Oct 10 02:30:00 shopzeus postfix/postfix-script[7240]: fatal: the Postfix mail system is already running Oct 10 03:00:00 shopzeus postfix/postfix-script[27437]: fatal: the Postfix mail system is already running Oct 10 04:07:54 shopzeus rc.shutdown: 30 second watchdog timeout expired. Shutdown terminated. Oct 10 04:09:16 shopzeus postgres[30455]: [5-1] FATAL: terminating connection due to administrator command Oct 10 04:09:17 shopzeus syslogd: exiting on signal 15 Oct 10 04:11:31 shopzeus syslogd: kernel boot file is /boot/kernel/kernel Oct 10 04:11:31 shopzeus kernel: Copyright (c) 1992-2008 The FreeBSD Project. Oct 10 04:11:31 shopzeus kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 After rebooting the machine, nothing happens until the next day. Here are some possible problems I can think of: #1. We are using gjournal. It might be that the journal size is too small. Although I do not think this is the case, because we have 40GB journal space for each journaled partition below (except for /home, it has 10GB only, but /home is rarely used) Filesystem 1G-blocks Used Avail Capacity Mounted on /dev/da0s1a 91 714%/ devfs 00 0 100%/dev /dev/da0s1f.journal 140 12 117 9%/home /dev/da0s2d.journal 106889 8%/pgdata0 /dev/da0s1d29026 0%/tmp /dev/da0s2e.journal 585 74 46414%/usr /dev/da0s1e.journal 145 17 11613%/var /dev/da1s1d.journal 4160 383 0%/data Is it possible that gjournal is hanging up the machine? #2. Yesterday when I logged in in the morning, I saw a process running under root, it was something like find / -sx ... and then something. I don't remember but it was scanning the whole filesystem. It was using 100% cpu and 100% disk I/O. I wonder if that might be freezing the computer. I do not know how to disable this maintenance process but I should. After killing this process, the system worked fine. (We have zillions of files on the disks, running find / ... is a bad idea.) This could be a periodic job (since you said this happens daily) which runs early in the morning (2-3am?) and for some reason isn't finishing in a timely manner. You haven't provided any actual ps -auxwww data, so we can't easily discern if it's a periodic job or something amiss on your system (for all we know the system could be compromised). I'm also curious what controller your SCSI disks are attached to. Can you provide that information? dmesg would be useful. I remember hearing some reports about 3Ware controllers locking up due to firmware problems which were later fixed via a f/w upgrade. #3. In the screenshot above, you can see that the IMAP server dovecot was terminated on signal 11. Can it be the problem? I can't believe that dovecot could freeze the whole system. #4. Hardware error. I don't think this is the case since the computer freezes at the same time, every day, so it is more likely a software problem. My vote is on a hardware problem. The watchdog timeout you see indicates a portion of the system is locking up hard. The sig 11 would indicate a sudden segfault, which if unexpected, often indicates bad memory or motherboard. I would recommend you start down the hardware path. Replace the RAM and the mainboard, and see what happens. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | |
Re: 7.1 hangs, shutdown terminated
On Fri, Oct 10, 2008 at 11:13:00AM +0200, Laszlo Nagy wrote: Johan Hendriks írta: If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem: # sysctl -a | grep dirhash shopzeus# sysctl -a | grep dirhash vfs.ufs.dirhash_docheck: 0 vfs.ufs.dirhash_mem: 2095818 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_minsize: 2560 Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem: All right. It is close to it. Which one should I increase? I put this into /etc/sysctl.conf: vfs.ufs.dirhash_maxmem=8228608 Would it be scufficient? We don't know, and can't tell you. You'll have to monitor vfs.ufs.dirhash_mem occasionally to see if you start to reach vfs.ufs.dirhash_maxmem. I have a tendency to use vfs.ufs.dirhash_maxmem=16777216, which is 16384*1024 (16MBytes). I'm not fully confident this is what's causing your problem, but it's definitely a recommendation by Johan. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1 hangs, shutdown terminated
This could be a periodic job (since you said this happens daily) which runs early in the morning (2-3am?) and for some reason isn't finishing in a timely manner. You haven't provided any actual ps -auxwww data, so we can't easily discern if it's a periodic job or something amiss on your system (for all we know the system could be compromised). I wanted to, but since I could not log in... I'm also curious what controller your SCSI disks are attached to. Can you provide that information? ARECA 1680 ix 12 dmesg would be useful. Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #3: Mon Oct 6 07:50:31 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHOPZEUS module_register: module g_journal already exists! Module g_journal failed to register: 17 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2508.72-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 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=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 usable memory = 8571047936 (8173 MB) avail memory = 8260050944 (7877 MB) ACPI APIC Table: INTEL S5000PSL FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: INTEL S5000PSL on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 acpi_button0: Sleep Button on acpi0 acpi_button1: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xca2,0xca3,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge irq 18 at device 2.0 on pci2 pci4: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection 6.9.5 port 0x2020-0x203f mem 0xb882-0xb883,0xb840-0xb87f irq 18 at device 0.0 on pci4 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:81:99:d0 em1: Intel(R) PRO/1000 Network Connection 6.9.5 port 0x2000-0x201f mem 0xb880-0xb881,0xb800-0xb83f irq 19 at device 0.1 on pci4 em1: Using MSI interrupt em1: [FILTER] em1: Ethernet address: 00:15:17:81:99:d1 pcib5: ACPI PCI-PCI bridge at device 0.3 on pci1 pci5: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 3.0 on pci0 pci6: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 4.0 on pci0 pci7: ACPI PCI bus on pcib7 pcib8: ACPI PCI-PCI bridge at device 5.0 on pci0 pci8: ACPI PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 6.0 on pci0 pci9: ACPI PCI bus on pcib9 pcib10: PCI-PCI bridge at device 7.0 on pci0 pci10: PCI bus on pcib10 pci0: base peripheral at device 8.0 (no driver attached) pcib11: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci11: ACPI PCI bus on pcib11 arcmsr0: Areca SAS Host Adapter RAID Controller (RAID6 capable) mem 0xb8b0-0xb8b01fff irq 16 at device 0.0 on pci11 ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.45 2008-04-29 arcmsr0: [ITHREAD] uhci0: Intel 631XESB/632XESB/3100 USB controller USB-1 port 0x3080-0x309f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: Intel 631XESB/632XESB/3100 USB controller USB-1 on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 631XESB/632XESB/3100 USB controller USB-2 port 0x3060-0x307f irq 22 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: Intel 631XESB/632XESB/3100 USB controller USB-2 on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 631XESB/632XESB/3100 USB controller USB-3 port 0x3040-0x305f irq 23 at
Re: [SOLVED] Re: 7.1 hangs, shutdown terminated
On Fri, Oct 10, 2008 at 11:43:39AM +0200, Laszlo Nagy wrote: If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem: # sysctl -a | grep dirhash shopzeus# sysctl -a | grep dirhash vfs.ufs.dirhash_docheck: 0 vfs.ufs.dirhash_mem: 2095818 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_minsize: 2560 Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem: All right. It is close to it. Which one should I increase? I put this into /etc/sysctl.conf: vfs.ufs.dirhash_maxmem=8228608 Would it be scufficient? We don't know, and can't tell you. You'll have to monitor vfs.ufs.dirhash_mem occasionally to see if you start to reach vfs.ufs.dirhash_maxmem. I have a tendency to use vfs.ufs.dirhash_maxmem=16777216, which is 16384*1024 (16MBytes). I'm not fully confident this is what's causing your problem, but it's definitely a recommendation by Johan. Thank you very much! Probably you are right. Our users use shared IMAP folders and sometimes they keep ten thousands of messages in one folder. I have increased dirhash_maxmem to 64MB and see what happens. Unfortunately, I cannot play with the hardware because it is in a server park, and it must be up 99.99% on workdays. I hope dirhash will solve the problem. I'm setting this to [SOLVED] and come back if it happens again. (Maybe on monday?) By the way, there is nothing in /etc/periodic that would execute find / -sx. Can somebody explain what is this for, and why it was started by root? Is it being used instead for enumerating files in a directory, when dir hash is full? Firstly, I see a periodic(8) job that DOES use find -sx, which means your attempt to track it down was faulty, and your syntax should have been find -sx / not find / -sx. See here: /etc/periodic/security/100.chksetuid: find -sx $MP /dev/null -type f \ $MP == mountpoint, e.g. /, /var, or any other mounted filesystem. So, what you saw was the periodic check looking for setuid-root binaries. Secondly, the kernel does not spawn userland processes like find(1). Thirdly, dirmem and dirmem_max are *pure* kernel things. What they do is control the amount of memory used for directory structure caching; rather than continually hit the disk every time and spend all that time handling directory contents, the kernel can cache previously-fetched contents in memory. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: 7.1 hangs, shutdown terminated
On Fri, Oct 10, 2008 at 01:07:43PM +0200, Laszlo Nagy wrote: Firstly, I see a periodic(8) job that DOES use find -sx, which means your attempt to track it down was faulty, and your syntax should have been find -sx / not find / -sx. See here: /etc/periodic/security/100.chksetuid: find -sx $MP /dev/null -type f \ Thanks for clearing that out. :-) I did not remember what it was and failed to find it. I believe the reason you saw this process still running at 8-9 in the morning was because of the slowdown induced by lack of dirhash memory. The periodic job runs every day, usually between 0130 and 0200, so the process had been sitting there processing its heart out for 6-7 hours. Since you've tuned the dirhash stuff, I'm betting this periodic job will run much more quickly. $MP == mountpoint, e.g. /, /var, or any other mounted filesystem. So, what you saw was the periodic check looking for setuid-root binaries. Secondly, the kernel does not spawn userland processes like find(1). Thirdly, dirmem and dirmem_max are *pure* kernel things. What they do is control the amount of memory used for directory structure caching; rather than continually hit the disk every time and spend all that time handling directory contents, the kernel can cache previously-fetched contents in memory Now it stays this value constantly: vfs.ufs.dirhash_mem: 44306131 I think it is now caching everything. Thank you again, and sorry for the dumb questions. You asked absolutely *no* dumb questions, especially given the circumstances! Do not be ashamed, you did the right thing. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: 7.1 hangs, shutdown terminated
Firstly, I see a periodic(8) job that DOES use find -sx, which means your attempt to track it down was faulty, and your syntax should have been find -sx / not find / -sx. See here: /etc/periodic/security/100.chksetuid: find -sx $MP /dev/null -type f \ Thanks for clearing that out. :-) I did not remember what it was and failed to find it. $MP == mountpoint, e.g. /, /var, or any other mounted filesystem. So, what you saw was the periodic check looking for setuid-root binaries. Secondly, the kernel does not spawn userland processes like find(1). Thirdly, dirmem and dirmem_max are *pure* kernel things. What they do is control the amount of memory used for directory structure caching; rather than continually hit the disk every time and spend all that time handling directory contents, the kernel can cache previously-fetched contents in memory Now it stays this value constantly: vfs.ufs.dirhash_mem: 44306131 I think it is now caching everything. Thank you again, and sorry for the dumb questions. Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: 7.1 hangs, shutdown terminated
Thank you very much! Probably you are right. Our users use shared IMAP folders and sometimes they keep ten thousands of messages in one folder. I have increased dirhash_maxmem to 64MB and see what happens. Unfortunately, I cannot play with the hardware because it is in a server park, and it must be up 99.99% on workdays. I hope dirhash will solve the problem. I'm setting this to [SOLVED] and come back if it happens again. (Maybe on monday?) By the way, there is nothing in /etc/periodic that would execute find / -sx. Can somebody explain what is this for, and why it was started by root? Is it being used instead for enumerating files in a directory, when dir hash is full? I'm starting to believe that this was the problem. Within an hour, I see this: shopzeus# sysctl vfs.ufs vfs.ufs.dirhash_docheck: 0 vfs.ufs.dirhash_mem: 33708867 vfs.ufs.dirhash_maxmem: 134217728 vfs.ufs.dirhash_minsize: 2560 Went up to 32MB! L ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 7.1 hangs, shutdown terminated
If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem: # sysctl -a | grep dirhash Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem: Regards, Johan Hendriks Double -L Automatisering No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.8.0/1717 - Release Date: 9-10-2008 16:56 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED] Re: 7.1 hangs, shutdown terminated
If find / -sx is running and is consuming all CPU, what is the value of vfs.ufs.dirhash_mem: # sysctl -a | grep dirhash shopzeus# sysctl -a | grep dirhash vfs.ufs.dirhash_docheck: 0 vfs.ufs.dirhash_mem: 2095818 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_minsize: 2560 Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem: All right. It is close to it. Which one should I increase? I put this into /etc/sysctl.conf: vfs.ufs.dirhash_maxmem=8228608 Would it be scufficient? We don't know, and can't tell you. You'll have to monitor vfs.ufs.dirhash_mem occasionally to see if you start to reach vfs.ufs.dirhash_maxmem. I have a tendency to use vfs.ufs.dirhash_maxmem=16777216, which is 16384*1024 (16MBytes). I'm not fully confident this is what's causing your problem, but it's definitely a recommendation by Johan. Thank you very much! Probably you are right. Our users use shared IMAP folders and sometimes they keep ten thousands of messages in one folder. I have increased dirhash_maxmem to 64MB and see what happens. Unfortunately, I cannot play with the hardware because it is in a server park, and it must be up 99.99% on workdays. I hope dirhash will solve the problem. I'm setting this to [SOLVED] and come back if it happens again. (Maybe on monday?) By the way, there is nothing in /etc/periodic that would execute find / -sx. Can somebody explain what is this for, and why it was started by root? Is it being used instead for enumerating files in a directory, when dir hash is full? Thanks, Laszo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.1-PRELEASE sporadically panicking with fatal trap 12
John L. Templer wrote: I'm running 7.1-PRERELEASE, with /usr/src and /usr/ports last csup-ed just a few days ago. After being up for about a day or so the system will panic because of a page fault. I'm not completely sure, but it seems that the system is more stable when gdm and gnome are disabled in rc.conf. At least it stayed up for several days when I did that. I've run memtest several times, so I'm pretty confident it's not a memory problem. Also the stack trace is always the same, so I'm thinking it's not hardware related. I've attached a stack trace from kgdb, and the output from dmesg. I'd appreciate any help you could give me with this. Please re-send to stable@ and CC [EMAIL PROTECTED] It looks like a locking problem in an error case that you are hitting (note ATA driver message prior to panic). Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
