gvinum/ahc0
Hi, I have a gvinum setup and am using an adaptec 7899 controller. Upon removing a drive (testing gvinum), the following happens... Is this message useful at all without a backtrace? Is there interest in getting a proper backtrace? I am running FreeBSD 5.4-RELEASE on a dell poweredge 1550 using one of its two cpus. GEOM_VINUM: subdisk usr.p0.s1 state change: up- down GEOM_VINUM: plex usr.p0.state change: up-degraded GEOM_VINUM: subdisk home.p0.s1 state change: up-down GEOM_VINUM: plex home.p0.s1 state change up-degraded writing vhdr failed: 6(da1:ahc0:0:1:0): synchronize cache failed, status 0x5b, scsi status = 0x0 (da1:ahc0:1:0): removing device entry gvinum: lost drive 'middle' fatal trap 12: page fault while in kernel mode fault virtual address = 0x18c fault code = supervisor write, page not present instruction pointer = 0x8:0xc00449654 stack pointer = 0x10:0xe5537bf0 frame pointer = 0x10:0xe5537bf0 cs = base 0x0 limit 0xf, type 0x1b DPL = 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IPOL=0 current process = 38 (irq27:ahc0) trap number = 12 panic: page fault uptime 9m20s ahc0: spurious SCSI interrupt. Thanks, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Test
Hey Tester, http://lists.freebsd.org/mailman/listinfo/freebsd-test is a special test list created *just* for tests... Thanks, Mr. Testy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, April 22, 2005 4:37 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Test In a message dated 4/22/2005 at 6:36:25 AM Central Daylight Time, [EMAIL PROTECTED] writes: Test -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list seems that it passed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [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: Error: /usr/lib/crt1.o(.text+0x64): In function `_start':
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexander Chamandy Sent: Wednesday, April 20, 2005 10:37 AM To: freebsd-stable@freebsd.org; freebsd-questions@freebsd.org Subject: Error: /usr/lib/crt1.o(.text+0x64): In function `_start': Has anyone seen these sorts of errors when compiling applications (such as PHP or Apache2)? I can buildworld, kernels and most of the ports.. but occasionally I run in to this error: /usr/lib/crt1.o(.text+0x64): In function `_start': : undefined reference to `_init_tls' Here's the dmesg: Copyright (c) 1992-2005 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 5.4-STABLE #5: Wed Apr 6 08:31:13 EDT 2005 I'd say look at the lists pertaining to -STABLE... because -STABLE isnt necessarily what its name implies, so many you need to cvsup and build world/kernel again, and possibly all your other applications. Maybe your /usr/src/UPDATING covers this... It's important to read. You never said what you're doing when you get that error. Andrew H. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: df question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Osmany Guirola Cruz Sent: Tuesday, April 19, 2005 5:37 AM To: freebsd-questions@freebsd.org Subject: df question Hi people I do df -h on my machine and got this RARE ouput %df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a7.7G2.2G4.9G31%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad0s1d 65G9.5G 50G16%/usr/home %df Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad0s1a 8122126 2328406 514395031%/ devfs 1 10 100%/dev /dev/ad0s1d 68372608 9940308 5296249216%/usr/home 50G+9.5G=60.5G but the partition size is 65G ... where are my ~5G,? What can i do? Thanks Osmany - Hi, That output is far from rare! Type man tunefs and type /-m without the quotes, and then hit n without the quotes. Read that section carefully. Also, some space is used in any file system for storage of data about the data (metadata). Inodes, superblocks, etc all take up space. Reading man tuning may also shed some light on this supposedly lost space. Thanks, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compaq Proliant 8500 issue with Integrated SMART Array RAIDController (ida)
On Saturday 09 April 2005 05:35, Ted Mittelstaedt wrote: [EMAIL PROTECTED] wrote: Hi, I have a Compaq Proliant 8500 with the integrated SMART Array RAID controller. I recall seeing Symbios and ARM on a chip on the center of the PCI module must be the RAID controller. I used to have extreme problems even getting the system to boot up until I used the SmartStart CD and disabled the Array Accelerator for my one and only RAID1+0 Container. (Before doing this) I would get numerous ida0: soft write error and if the system did manage to boot up, a process might read the disk, and forever be stuck in some kernel routine between userland and the disk that gets a block or whatever. Now, I only get an occasional ida0: soft read/write error which occasionally causes a 15 or so second delay. The Array Accelerator for the Integrated SMART array controller is 8MB of read-only cache. Other SMART Array models like the 4200 have battery backed up cache that can be user-separated between write and read cache. I'm wondering if anybody has ever seen the problem mentioned above. I would hate to have to replace the whole PCI module because of some bad controller ram since that darn thing is integrated, and would make useless the internal bays if another raid card was added. As a note, the contacts between the hard drive and the drive module have been cleaned out multiple times for all the drives in the array. The connection between the drive module and the back of the computer is sturdy and clean. There are only TWO cables in this entire system that I know of, and one is for the IDE CDROM, and one is for the floppy. So, cabling cannot be a problem. I also have two working PSUs that each have a 120V line going into it, so I doubt it's a lack of power. Even though 220V is recommended for both of them, it works fine with even just one 120V line. I asked the HP/Compaq forum and they weren't able to give me much more of an answer than check the cabling and blow off the dust which I found extremely irritating because the data is carried on copper wires that resemble the pins found on an IDE hard drive or floppy, not your standard cabling. I might ultimately be wrong...but I doubt it. You should ask Windows questions in a Windows forum. Oh, you aren't running Windows on this system? Must be FreeBSD 2.2 then, right? Ted Right now, the machine runs FreeBSD 5.3-RELEASE. I've also tried a specially modified 6.0-CURRENT kernel upon suggestion of Matthew N. Dodd, and FreeBSD 4.11, but the nature of the problem never changed and no more useful information was able to be found. The same thing also happened running linux 2.4.27 and some version of Linux 2.6. I had given up hope that it was a software issue and was trying to see if any of the number of people on this list have ever had a machine that did this, or had details about somebody else's machine that did the same thing also. Also, the ROM on the controller and the primary system BIOS have been updated to the latest available versions. I have also updated the firmwares on the disk drives. Thanks, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Compaq Proliant 8500 issue with Integrated SMARTArrayRAIDController (ida)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ted Mittelstaedt Sent: Monday, April 11, 2005 10:08 AM To: Andrew Heyn; freebsd-questions@freebsd.org Subject: RE: Compaq Proliant 8500 issue with Integrated SMARTArrayRAIDController (ida) [EMAIL PROTECTED] wrote: On Saturday 09 April 2005 05:35, Ted Mittelstaedt wrote: [EMAIL PROTECTED] wrote: Hi, I have a Compaq Proliant 8500 with the integrated SMART Array RAID controller. I recall seeing Symbios and ARM on a chip on the center of the PCI module must be the RAID controller. I used to have extreme problems even getting the system to boot up until I used the SmartStart CD and disabled the Array Accelerator for my one and only RAID1+0 Container. (Before doing this) I would get numerous ida0: soft write error and if the system did manage to boot up, a process might read the disk, and forever be stuck in some kernel routine between userland and the disk that gets a block or whatever. Now, I only get an occasional ida0: soft read/write error which occasionally causes a 15 or so second delay. The Array Accelerator for the Integrated SMART array controller is 8MB of read-only cache. Other SMART Array models like the 4200 have battery backed up cache that can be user-separated between write and read cache. I'm wondering if anybody has ever seen the problem mentioned above. I would hate to have to replace the whole PCI module because of some bad controller ram since that darn thing is integrated, and would make useless the internal bays if another raid card was added. As a note, the contacts between the hard drive and the drive module have been cleaned out multiple times for all the drives in the array. The connection between the drive module and the back of the computer is sturdy and clean. There are only TWO cables in this entire system that I know of, and one is for the IDE CDROM, and one is for the floppy. So, cabling cannot be a problem. I also have two working PSUs that each have a 120V line going into it, so I doubt it's a lack of power. Even though 220V is recommended for both of them, it works fine with even just one 120V line. I asked the HP/Compaq forum and they weren't able to give me much more of an answer than check the cabling and blow off the dust which I found extremely irritating because the data is carried on copper wires that resemble the pins found on an IDE hard drive or floppy, not your standard cabling. I might ultimately be wrong...but I doubt it. You should ask Windows questions in a Windows forum. Oh, you aren't running Windows on this system? Must be FreeBSD 2.2 then, right? Ted Right now, the machine runs FreeBSD 5.3-RELEASE. I've also tried a specially modified 6.0-CURRENT kernel upon suggestion of Matthew N. Dodd, and FreeBSD 4.11, but the nature of the problem never changed and no more useful information was able to be found. The same thing also happened running linux 2.4.27 and some version of Linux 2.6. I had given up hope that it was a software issue and was trying to see if any of the number of people on this list have ever had a machine that did this, or had details about somebody else's machine that did the same thing also. Also, the ROM on the controller and the primary system BIOS have been updated to the latest available versions. I have also updated the firmwares on the disk drives. I can tell you right off the EISA versions of this controller don't work at all. Seems to me I recall some discussion a couple years back that there were problems with certain versions of this controller. Check in the mailing list archives, but more importantly check the google news archives, as I thought I saw the thread on Usenet. Ted Ted, Thanks for the response. [EMAIL PROTECTED]:14:0: class=0x010400 card=0x40400e11 chip=0x00101000 rev=0x01 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'LSI53C1510 I2O-Ready PCI RAID Ultra2 SCSI Controller (Intelligent mode)' class= mass storage subclass = RAID I believe that output from pciconf -v -l is enough to show that it's not EISA... Does anything else about that model ring any bells for you? The only reference to something related to my problem is people reporting ida0: soft error or ida0: soft read/write error, which are related to having a failed drive... I noticed myself that if the raid container wasn't 100%, those errors would come out by the thousands... But nobody reports temporarily halts, or having to disable the integrated smart array's read cache to boot up. Thanks, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Compaq Proliant 8500 issue with Integrated SMART Array RAID Controller (ida)
Hi, I have a Compaq Proliant 8500 with the integrated SMART Array RAID controller. I recall seeing Symbios and ARM on a chip on the center of the PCI module must be the RAID controller. I used to have extreme problems even getting the system to boot up until I used the SmartStart CD and disabled the Array Accelerator for my one and only RAID1+0 Container. (Before doing this) I would get numerous ida0: soft write error and if the system did manage to boot up, a process might read the disk, and forever be stuck in some kernel routine between userland and the disk that gets a block or whatever. Now, I only get an occasional ida0: soft read/write error which occasionally causes a 15 or so second delay. The Array Accelerator for the Integrated SMART array controller is 8MB of read-only cache. Other SMART Array models like the 4200 have battery backed up cache that can be user-separated between write and read cache. I'm wondering if anybody has ever seen the problem mentioned above. I would hate to have to replace the whole PCI module because of some bad controller ram since that darn thing is integrated, and would make useless the internal bays if another raid card was added. As a note, the contacts between the hard drive and the drive module have been cleaned out multiple times for all the drives in the array. The connection between the drive module and the back of the computer is sturdy and clean. There are only TWO cables in this entire system that I know of, and one is for the IDE CDROM, and one is for the floppy. So, cabling cannot be a problem. I also have two working PSUs that each have a 120V line going into it, so I doubt it's a lack of power. Even though 220V is recommended for both of them, it works fine with even just one 120V line. I asked the HP/Compaq forum and they weren't able to give me much more of an answer than check the cabling and blow off the dust which I found extremely irritating because the data is carried on copper wires that resemble the pins found on an IDE hard drive or floppy, not your standard cabling. I might ultimately be wrong...but I doubt it. Thanks, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: [OT] is there a ThinkPad clone?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gary Kline Sent: Thursday, April 07, 2005 9:01 AM To: FreeBSD Mailing List Subject: [OT] is there a ThinkPad clone? People, Apologies up front if anybody thinks this is *too* far OT, but if the 8 months I've been using FreeBSD on my TP 600E (400MHz, 288M, 12G). it has become my favorite computer. __Not__ having that std mouse-pad thing where you scratch or drag or tap your fingers lets me rest the heel of my left hand dead-center and type away. The tiny mouse-stick and the three cut/paste bars work well too. When I upgrade, I'd like another laptop with the same layout. The few other laptops I've looked at all have that mouse-pad. Anybody know if there is anything like a ThinkPad clone?? gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix --- Gary, Your typing habits disturb me greatly. Please consider this document: http://www3.gov.ab.ca/hre/whs/publications/pdf/erg029.pdf Save yourself! Thanks, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ATI RAGE Mobility
Sorry, Rage mobility is mach64... you're trying to use a rage128/radeon driver. That won't work. There is some preliminary mach64 support but you have to build it yourself. It really sucks, it's not so worth it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Busby Sent: Tuesday, March 29, 2005 11:23 AM To: freebsd-questions@freebsd.org Subject: re: ATI RAGE Mobility On Monday 28 March 2005 20:25, Edwin Mons wrote: On Mon, 28 Mar 2005 20:20:50 +0200, Edwin Mons wrote: I'm trying to enable DRI on my IBM ThinkPad A20m, which has an ATI Rage Mobility P/M AGP 2x rev 100 GPU onboard. I succesfully installed the mach64 DRM module, which shows the following lines in my dmesg: drm0: Rage Mobility P/M AGP 2X port 0x2000-0x20ff mem 0xf420-0xf4200fff,0xf500-0xf5ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized mach64 1.0.0 20020904 on minor 0 However, when I start X.org 6.8.2, it doesn't show anything about DRM in the logfiles (attached). glxinfo reports it doesn't use Direct Rendering as well. Attached is my xorg.conf, as well. My questions: 1) does anybody know if it is possible to have DRI on this configuration at all, and 2) how does one get it to work? from kernel LINT file # DRM options: # mgadrm:AGP Matrox G200, G400, G450, G550 # tdfxdrm: 3dfx Voodoo 3/4/5 and Banshee # r128drm: ATI Rage 128 # radeondrm: ATI Radeon up to 9000/9100 # DRM_DEBUG: include debug printfs, very slow # # mga requires AGP in the kernel, and it is recommended # for AGP r128 and radeon cards. device mgadrm device r128drm device radeondrm device tdfxdrm options DRM_DEBUG You may need to add the device mgadrm Hope it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [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: ATI RAGE Mobility
I would like to state that at one point, I did get this to work. This was also a long time ago, when the patches mentioned in some of the proceeding links had to be done.. (which were and probably still are XFree86 specific) http://people.freebsd.org/~anholt/dri/news.html http://am-productions.biz/docs/fujitsu-p2110.php leads to http://dri.freedesktop.org/wiki/Building I noticed that I had to make sure I rebuilt mach64.ko and some of the X libraries regarding dri if I was to upgrade the kernel. Note this from the Wiki: The DRM is shipped with the kernel, so you shouldn't need to build it. If you choose to, simply run make make install from the drm/bsd directory. This is contrary to the suggestion to install ports/graphics/drm. The building referred to above is within the X tree. The history to the mach64 dri support may be of interest: http://people.freebsd.org/~anholt/dri/news.html (already gave this link) You can always (if you are patient) contact anholt who is rather busy on freenode.net in #dri. Beware, I asked a question there, and fixed it myself before I got an answer. Hope this helps more than my other post. It still sucked pretty bad once I got DRI working with my mach64, but... It was better... Thanks! Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Busby Sent: Tuesday, March 29, 2005 11:23 AM To: freebsd-questions@freebsd.org Subject: re: ATI RAGE Mobility On Monday 28 March 2005 20:25, Edwin Mons wrote: On Mon, 28 Mar 2005 20:20:50 +0200, Edwin Mons wrote: I'm trying to enable DRI on my IBM ThinkPad A20m, which has an ATI Rage Mobility P/M AGP 2x rev 100 GPU onboard. I succesfully installed the mach64 DRM module, which shows the following lines in my dmesg: drm0: Rage Mobility P/M AGP 2X port 0x2000-0x20ff mem 0xf420-0xf4200fff,0xf500-0xf5ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized mach64 1.0.0 20020904 on minor 0 However, when I start X.org 6.8.2, it doesn't show anything about DRM in the logfiles (attached). glxinfo reports it doesn't use Direct Rendering as well. Attached is my xorg.conf, as well. My questions: 1) does anybody know if it is possible to have DRI on this configuration at all, and 2) how does one get it to work? from kernel LINT file # DRM options: # mgadrm:AGP Matrox G200, G400, G450, G550 # tdfxdrm: 3dfx Voodoo 3/4/5 and Banshee # r128drm: ATI Rage 128 # radeondrm: ATI Radeon up to 9000/9100 # DRM_DEBUG: include debug printfs, very slow # # mga requires AGP in the kernel, and it is recommended # for AGP r128 and radeon cards. device mgadrm device r128drm device radeondrm device tdfxdrm options DRM_DEBUG You may need to add the device mgadrm Hope it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FW: dmesg -a lines' explanation? NEWBIE
And it's off to the list! -Original Message- From: David Armour [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 29, 2005 3:40 PM To: Andrew Heyn Subject: Re: dmesg -a lines' explanation? NEWBIE hello, thank you for your response. Regarding grep, you got it half right. that is just *so* ME! :c) plugging your recommendation onto the command line produced: /etc/devfs.conf:permxpt00666#permissions are set properly at boot ... which is still largely un-intelligible to me, at the moment. and which co-incides, oddly enough, with the moment at which i have to leave for work! dang! so i'll have to take another google around, later tonight... grep's command line can be made to look less scary like: grep options search string filename yes. that helps. i did sort of think of it in those terms. or grep -ri something /etc/* which searches recursively, and ignores What you did when you didnt tell grep what file to use for input was i mis-read the manpage. tell it to get info from the terminal (standard input)! Control-C would quit grep, or control-d would tell grep end of file and stop grep. yes, i used crtl-c to quit. didn't know about crtl-d though. I'm pretty sure that searching google a little bit can help you with UNIX basics. there is a lot of stuff out there, i agree. making sense of it's another story though. thanks v. much for your help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
