Re: a wireless network freezes the machine?
Victor Sudakov wrote: [dd] Is it possible that wpa_supplicant or some other part of the WiFi setup causes the hangs? Nothing else has changed in the system besides its role from the access point to a WiFi client. Actually, kern/170066 may be related, but it's different hardware and in my case, the box does not freeze immediately at wpa_supplicant's start, though it does freeze eventually, especially if there is some load on the video subsystem (Intel SandyBridge with the recent x11-drivers/xf86-video-intel) like watching a movie. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: Port update hosed entire system
On Mon, 1 Oct 2012 20:08:29 -0400, Rod Person wrote: Hi All, I was attempting to update ports that used libogg with the command portmaster -d -y -r libogg I went away and came back some hours later and some updates had failed. Now my shell segfaults on any command such as ls, clear or su I tried to login on another console as root and after giving the password it just goes back to login. I am at a loss as to what to do to fix this one. That sounds like a really weird problem. FreeBSD and the ports (which portmaster deals with) are separated systems, so even if you totally hose your ports, the OS should not be affected. You're mentioning the shell: Which one is it? In case it's a shell from ports, _maybe_ that is a problem. In case of root, it should have the system's default shell /bin/csh; the system's scripting and emergency shell /bin/sh should also work. You can get into a state for tests under mostly defined circumstances by entering the single user mode and check things, then continue to boot, and finally install what was lost. In worst case, reinstall everything (see EXAMPLES section in man portmaster). In ultra-worst case, remove the /usr/local subtree (copy everything you might need afterwards, e. g. config files and your scripts!), repopulate it using the mtree file, and reinstall what you need. That will pull in any dependencies you may not have thought of in the first place. -- Polytropon 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: Port update hosed entire system
On Mon, 1 Oct 2012 09:47:51 +0700 Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: Can you run /bin/sh? That would be a start to try reinstalling what was lost. Good luck, Olivier Nope. $ /bin/sh Segmentation fault (core dumped) -- Rod Person http://www.rodperson.com First we got population. The world today has 6.8 billion people. That's headed up to about 9 billion. Now if we do a really great job on new vaccines, health care, reproductive health services, we lower that by perhaps 10 or 15 percent. - Bill Gates ___ 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: Port update hosed entire system
On Mon, 1 Oct 2012 09:57:05 +0700 Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Any help or ideas would be appreciated. did you try to boot into single user mode? What shells do you have installed? Erich This is the default shell. I didn't try that yet, because I don't want to be left with no way to login at all if something is really messed up. Since I could not even switch to a no console (ctrl+alt+f2...) and login I'm not really wanting to reboot at this point. -- Rod Person http://www.rodperson.com First we got population. The world today has 6.8 billion people. That's headed up to about 9 billion. Now if we do a really great job on new vaccines, health care, reproductive health services, we lower that by perhaps 10 or 15 percent. - Bill Gates ___ 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: Port update hosed entire system
On Mon, 1 Oct 2012 08:02:54 +0200 Polytropon free...@edvax.de wrote: On Mon, 1 Oct 2012 20:08:29 -0400, Rod Person wrote: Hi All, I was attempting to update ports that used libogg with the command portmaster -d -y -r libogg I went away and came back some hours later and some updates had failed. Now my shell segfaults on any command such as ls, clear or su I tried to login on another console as root and after giving the password it just goes back to login. I am at a loss as to what to do to fix this one. That sounds like a really weird problem. FreeBSD and the ports (which portmaster deals with) are separated systems, so even if you totally hose your ports, the OS should not be affected. I'm well aware of this, and is also why I no clue what could have happened. It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. I did discover that my / file system had run out of space -131MB. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. -- Rod Person http://www.rodperson.com First we got population. The world today has 6.8 billion people. That's headed up to about 9 billion. Now if we do a really great job on new vaccines, health care, reproductive health services, we lower that by perhaps 10 or 15 percent. - Bill Gates ___ 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: Port update hosed entire system
Rod Person rodperson at rodperson.com writes: ... I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. Well, in emergency: - add /rescue/sh to /etc/shells Anything in /rescue/ is statically compiled. - change root shell to /rescue/sh vipw jb ___ 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: Port update hosed entire system
Hi, On Tue, 2 Oct 2012 06:20:45 -0400 Rod Person rodper...@rodperson.com wrote: On Mon, 1 Oct 2012 08:02:54 +0200 Polytropon free...@edvax.de wrote: On Mon, 1 Oct 2012 20:08:29 -0400, Rod Person wrote: Hi All, I was attempting to update ports that used libogg with the command portmaster -d -y -r libogg I went away and came back some hours later and some updates had failed. Now my shell segfaults on any command such as ls, clear or su I tried to login on another console as root and after giving the password it just goes back to login. I am at a loss as to what to do to fix this one. That sounds like a really weird problem. FreeBSD and the ports (which portmaster deals with) are separated systems, so even if you totally hose your ports, the OS should not be affected. I'm well aware of this, and is also why I no clue what could have happened. It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. the ports did nothing of this sort. I did discover that my / file system had run out of space -131MB. Ah, all red lights are on now. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. You ave now 25GB free on /? More red lights are on now. I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. What partitioning schema do you have? Could it be that you simply filled the file system and FreeBSD does not find any space even just for a restart? Erich ___ 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: Port update hosed entire system
On 02/10/2012 11:10, Rod Person wrote: On Mon, 1 Oct 2012 09:47:51 +0700 Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: Can you run /bin/sh? That would be a start to try reinstalling what was lost. Nope. $ /bin/sh Segmentation fault (core dumped) How about /rescue/sh ? It's statically linked so should continue working no matter the state of the shared libraries on the system. Failing that, booting from the install media into a livefs is your best bet. You should be able to mount your system disks or import a ZFS pool and fix their contents. Also, wondering how exactly your original command managed to hose the base system. Did it fill up the disks? Is it possible that the problem is actually hardware failure? Cheers, Matthew ___ 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: Port update hosed entire system
On 10/02/12 11:20, Rod Person wrote: On Mon, 1 Oct 2012 08:02:54 +0200 Polytropon free...@edvax.de wrote: On Mon, 1 Oct 2012 20:08:29 -0400, Rod Person wrote: Hi All, I was attempting to update ports that used libogg with the command portmaster -d -y -r libogg I went away and came back some hours later and some updates had failed. Now my shell segfaults on any command such as ls, clear or su I tried to login on another console as root and after giving the password it just goes back to login. I am at a loss as to what to do to fix this one. That sounds like a really weird problem. FreeBSD and the ports (which portmaster deals with) are separated systems, so even if you totally hose your ports, the OS should not be affected. I'm well aware of this, and is also why I no clue what could have happened. It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. I did discover that my / file system had run out of space -131MB. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. Have you tried /rescue/sh? If that fails as well I'd start worrying about hardware problems. ___ 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: Port update hosed entire system
jb jb.1234abcd at gmail.com writes: Rod Person rodperson at rodperson.com writes: ... I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. Well, in emergency: - add /rescue/sh to /etc/shells Anything in /rescue/ is statically compiled. - change root shell to /rescue/sh vipw jb I forgot to mention that you may want to do this: Save /bin/sh. mv /bin/sh /bin/sh-saved Softlink /bin/sh: ln -s /rescue/sh /bin/sh jb ___ 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: find slot number and number of ports for each card
[ Devin Teske wrote on Sat 29.Sep'12 at 12:32:04 -0700 ] On Sep 29, 2012, at 7:37 AM, saeedeh motlagh wrote: hello all i want to have statistics about my hardware specially the type of card that are installed on my system, Card characteristics are provided by pciconf -l. (pciconf -lv for verbose listing). Two important notes about pciconf -l… 1. It lists more than just cards 2. The type can't always be determined by FreeBSD When looking at the output of pciconf -l, each line represents a component (this can be an integrated component on the mother- board, such as USB port, not necessarily a PCI add-in card). If the line begins with none@ then a driver has not attached to this device (and FreeBSD therefore doesn't know what type it is). In this case, you'll want to look at the chip= portion of the line. The chip= portion of the line gives you two very important pieces of information when it comes to identifying your hardware: a. The 4-digit hexadecimal identifier for the Model of the device b. The 4-digit hexadecimal identifier for the Vendor of the device (in that order from left-to-right) Let's look at a sample line: vgapci0@pci0:2:9:0: class=0x03 card=0x00081002 chip=0x47521002 rev=0x27 hdr=0x00 NOTE: That's my graphics card on an ASUSTek P4B533 motherboard In the above line, see chip=0x47521002. In this case, 4752 is the Model identifier and 1002 is the Vendor identifier. If you're a human and you want to know what these numbers are, you hop on over to pcidatabase.com and punch in the numbers to find out that this is a [particularly ancient] ATI Rage XL graphics card. If you're not a human (i.e., a script), you'll instead reference a local copy of the pci.ids (/usr/local/share/pciids/pci.ids for example): $ grep '1002 4752' /usr/local/share/pciids/pci.ids 1002 4752 Proliant Rage XL the number of ports that each card has That one is near impossible. Since every add-in card is going function differently, you really need a device-specific enumeration method to (for example) count things like PHYs provided by a single NIC. Imagine if you will, the case of the card for which there is no driver loaded in the kernel (where pciconf -l shows a none@ prefix). There really is no way to enumerate the number of ports a card offers in that circumstance. However! You can build logic into your code (if you are scripting something) that takes the description from the pci.ids file (or just the raw hex IDs) and extrapolates based on prior-knowledge how many ports a particular device has. and the slot number which cards are installed. That's provided by pciconf. Also, it's worth mentioning the excellent dmidecode tool from the ports tree. This too can enumerate the slots themselves (and tell you whether they are PCI, PCI-X, PCIe, etc. including voltage. Search for System Slot Information in the dmidecode output for this info. -- Devin This is interesting. I'm glad this question was raised, because i've noticed i've got two none@ lines listed when using pciconf -lv. I've been trying to figure out what these are over the last week but to no avail. They must be there for some purpose and I wondered if i'm missing some important driver because 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: find slot number and number of ports for each card
thanks every body for your answers. now i know my path. thanks again On Mon, Oct 1, 2012 at 3:18 PM, Jamie Paul Griffin ja...@kode5.net wrote: [ Devin Teske wrote on Sat 29.Sep'12 at 12:32:04 -0700 ] On Sep 29, 2012, at 7:37 AM, saeedeh motlagh wrote: hello all i want to have statistics about my hardware specially the type of card that are installed on my system, Card characteristics are provided by pciconf -l. (pciconf -lv for verbose listing). Two important notes about pciconf -l… 1. It lists more than just cards 2. The type can't always be determined by FreeBSD When looking at the output of pciconf -l, each line represents a component (this can be an integrated component on the mother- board, such as USB port, not necessarily a PCI add-in card). If the line begins with none@ then a driver has not attached to this device (and FreeBSD therefore doesn't know what type it is). In this case, you'll want to look at the chip= portion of the line. The chip= portion of the line gives you two very important pieces of information when it comes to identifying your hardware: a. The 4-digit hexadecimal identifier for the Model of the device b. The 4-digit hexadecimal identifier for the Vendor of the device (in that order from left-to-right) Let's look at a sample line: vgapci0@pci0:2:9:0: class=0x03 card=0x00081002 chip=0x47521002 rev=0x27 hdr=0x00 NOTE: That's my graphics card on an ASUSTek P4B533 motherboard In the above line, see chip=0x47521002. In this case, 4752 is the Model identifier and 1002 is the Vendor identifier. If you're a human and you want to know what these numbers are, you hop on over to pcidatabase.com and punch in the numbers to find out that this is a [particularly ancient] ATI Rage XL graphics card. If you're not a human (i.e., a script), you'll instead reference a local copy of the pci.ids (/usr/local/share/pciids/pci.ids for example): $ grep '1002 4752' /usr/local/share/pciids/pci.ids 1002 4752 Proliant Rage XL the number of ports that each card has That one is near impossible. Since every add-in card is going function differently, you really need a device-specific enumeration method to (for example) count things like PHYs provided by a single NIC. Imagine if you will, the case of the card for which there is no driver loaded in the kernel (where pciconf -l shows a none@ prefix). There really is no way to enumerate the number of ports a card offers in that circumstance. However! You can build logic into your code (if you are scripting something) that takes the description from the pci.ids file (or just the raw hex IDs) and extrapolates based on prior-knowledge how many ports a particular device has. and the slot number which cards are installed. That's provided by pciconf. Also, it's worth mentioning the excellent dmidecode tool from the ports tree. This too can enumerate the slots themselves (and tell you whether they are PCI, PCI-X, PCIe, etc. including voltage. Search for System Slot Information in the dmidecode output for this info. -- Devin This is interesting. I'm glad this question was raised, because i've noticed i've got two none@ lines listed when using pciconf -lv. I've been trying to figure out what these are over the last week but to no avail. They must be there for some purpose and I wondered if i'm missing some important driver because 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 ___ 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: system hangs during dump + compress usb2-drive
From: Xin Li delp...@delphij.net To: Jin Guojun jguo...@sbcglobal.net Cc: questi...@freebsd.org; hack...@freebsd.org Sent: Sun, September 30, 2012 1:07:40 PM Subject: Re: system hangs during dump + compress usb2-drive On 9/29/12 10:49 PM, Jin Guojun wrote: In FreeBSD 8.3 release (possibly in earlier release), dump a file system has 2-3GB or more content can cause system hang in a specific case (pipe to compression): dump FS-on-SATA-drive usb-drive OK dump FS-on-SATA-drive | anyCompress sata-drive OK mv a-large-dump-file from STAT drive to a USB drive OK dump small-FS-on-SATA-drive | anyCompress usb-drive OK small -- 1.8GB or less dump large-FS-on-SATA-drive | anyCompress usb-drive hang content is 3GB or larger (did not try around 2GB yet) When system hangs, no sub system, such video, network, etc, will function. Typically, the unfinished compressed dump file is around 1.5-2.7GB, so guessing dumped file content is close to or over 2GB when failure occurred. Has anyone encountered the same problem? Because this usually takes a few hours to occur, this is hard to watch how/when it happens. Is any way to debug or determine what status the system is? For starters I'd use a different console for doing procstat -kk -a and see what the system is doing. (Perhaps also top) I *think* that if it's just hanging for some time, it's probably because the system is trying to take a snapshot? It takes time on UFS when creating and removing the snapshot. Just a guess... Cheers, --- Not sure how to use a different console. No tty is functioning (neither ttyv? nor over network). You are right on a different case -- mount /dev/da0s4d /mnt# mount a usb drive cd /mnt ssh remote-liux-host tar -cf - 8GB_FS | tar -xf - In this case, doing ls -l /mnt or df will hangs, but system is still alive. The network is 45Mbps. I have no idea how long it took the tar to finish since machine is 60 km away. When I left there last Friday, only 400MB was done in one hour. I will get the processing time tomorrow. The problem we can see now is that tar (probably the pipe) process only finish with 4GB. # df Filesystem1K-blocks Used Avail Capacity Mounted on /dev/ad4s3a 1012974355348 57659038%/ devfs 1 1 0 100%/dev ... /dev/da0s4d 1027486774 4198246 941089588 0%/mnt So, I suspect this is a pipe problem, not a compress issue. ___ 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: freebsd-9.1 and Intel HD 3000
On Mon, 1 Oct 2012 07:22:27 +0700 Erich Dollansky er...@alogreentechnologies.com wrote: Hi, On Mon, 1 Oct 2012 00:52:49 +0200 Frantisek Farka franti...@farka.eu wrote: Hello ... it should be all there, even in an updated 9.0. Did you update your system or did you keep it at the release level? Erich I might have used just release version. But now I can wait for 9.1, already looking forward to that. Thanks for answer FF ___ 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
filter this folder extension in FreeBSD kde3 konqueror
Hello: As I could not find a kde3 specific freebsd list I am asking the question here. How can I make filter this folder extension work in kde 3 konqueror as the image at the link shows? http://i48.tinypic.com/5x5t2s.jpg I have FreeBSD 9.0-REELEASE with the following kdeaddons packages: kdeaddons-3.5.10_5 Additional plugins and scripts for some KDE applications kdeaddons-atlantikdesigner-3.5.10_3 Editor for Atlantik kdeaddons-kaddressbook-plugins-3.5.10_5 Plugins for KAdressbook kdeaddons-kate-plugins-3.5.10_5 Additonal plugins and features for kate kdeaddons-kfile-plugins-3.5.10_5 Plugins for Konqueror (in filemanager mode) kdeaddons-kicker-applets-3.5.10_5 Additional applets for Kicker kdeaddons-knewsticker-scripts-3.5.10_3 Additional scripts for KNewsTicker kdeaddons-konq-plugins-3.5.10_5 Additonal plugins and features for Konqueror kdeaddons-ksig-3.5.10_3 Signature randomiser, available standalone or as a plugin w kdeaddons-noatun-plugins-3.5.10_3 Various plugins for Noatun kdeaddons-renamedlg-plugins-3.5.10_3 Plugins for Konqueror's rename dialog Thanks ins advance, Istvan ___ 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: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
On Wednesday, June 6, 2012 8:36:04 PM UTC-5, Mark Felder wrote: Hi guys I'm excitedly posting this from my phone. Good news for you guys, bad news for us -- we were building HA storage on vmware for a client and can now replicate the crash on demand. I'll be posting details when I get home to my PC tonight, but this hopefully is enough to replicate the crash for any curious followers: ESXi 5 9 or 9-STABLE HAST 1 cpu is fine 1GB of ram UFS SUJ on HAST device No special loader.conf, sysctl, etc No need for VMWare tools Run Bonnie++ on the HAST device We can get the crash to happen on the first run of bonnie++ right now. I'll post the exact specs and precise command run in the PR. We found an old post from 2004 when we looked up the process state obtained from CTRL+T -- flswai -- which describes the symptoms nearly perfectly. http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2004-02/0250.html Hopefully this gets us closer to a fix... Is this a crash or a hang? Over the past couple of weeks, I've been working with a FreeBSD 9.1RC1 system under VMware ESXi 5.0 with a 64GB UFS root FS and 2TB ZFS filesystem mounted via a virtual LSI SAS interface. Sometimes during heavy I/O load (rsync from other servers) on the ZFS FS, this shows up in /var/log/messages: Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 5 ee 60 16 0 1 0 0 Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): Retrying command Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 3 ef 42 51 0 1 0 0 Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): Retrying command Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 3 ef 64 51 0 1 0 0 Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): Retrying command Sep 21 02:18:49 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 3 ef 66 51 0 1 0 0 Sep 21 02:18:49 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:18:49 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy ... Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 41 f3 94 99 0 1 0 0 Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): Retrying command These have been happening roughly every other day. mpt0 and em0 were sharing int 18, so today I put hint.mpt.0.msi_enable=1 into /boot/devices.hints and rebooted; now mpt0 is using int 256. I'll see if it helps. Guy ___ 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: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
On Mon, 01 Oct 2012 15:00:40 -0500, guy.hel...@gmail.com wrote: Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 5 ee 60 16 0 1 0 0 Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): Retrying command Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 3 ef 42 51 0 1 0 0 Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 02:18:44 backups kernel: (da1:mpt0:0:1:0): Retrying command Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 3 ef 64 51 0 1 0 0 Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 02:18:48 backups kernel: (da1:mpt0:0:1:0): Retrying command Sep 21 02:18:49 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 3 ef 66 51 0 1 0 0 Sep 21 02:18:49 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 02:18:49 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy ... Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 41 f3 94 99 0 1 0 0 Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy Sep 21 05:06:18 backups kernel: (da1:mpt0:0:1:0): Retrying command Sometimes you'll see this before a crash, but not every 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
