AMI Megaraid, failed array
Hi all, A FreeBSD 4.7 machine with an AMI Megaraid controller and 3 disks in a RAID 5 array failed on me this week. One of the disk drives went into offline state due to overheating and the array, to the best of my knowledge should have continued in degraded mode. Two things concern me at this point. 1. There were no messages in /var/log/messages to indicate that a disk had failed and the array was in degraded mode. 2. With 2 disks of the array still online, we were unable to read / execute loads of data. Many text files were unreadable and system binaries like tar unusable. When we got the disk back online and rebooted the box, we were able to easily read data, and files that appeared to be corrupt turned out not to be. Can anyone advise me on why I saw what I saw and how I can get around this in the future. Regards, -- Wayne Pascoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Problems getting wireless card working with PCI adaptor
Wayne Pascoe [EMAIL PROTECTED] writes: M. Warner Losh [EMAIL PROTECTED] writes: : I have found that IRQ 5 is used by the onboard usb controller, but : even if I disable in the bios I still get this message popping up. Using a PCI expantion card requires you to use PCI routing. Can you post the complete dmesg? I need to know how we're setting things up and what you've posted so far isn't sufficient. I'm attaching a dmesg from a fresh install to this email. All I've done to the install is to add the following lines to /etc/rc.conf and reboot Apparantly the dmesg attachment never made it through. I've uploaded it to http://www.penguinpowered.org.uk/dmesg.txt Last night I tried a RedHat load and found almost exactly the same problem with Linux kernel 2.4.18 and pcmcia-cs. So it looks like I'm missing something fundamental about getting a PCI-PCMCIA card working :( -- - Wayne Pascoe - http://www.penguinpowered.org.uk/wayne/ The thing is, I was POSITIVE that I wasn't actually depressed, just that life had no meaning and I was tired of living. -- daystar on k5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Problems getting wireless card working in PCI adaptor
Hi again, I'm trying to get a wireless card going in a desktop machine. The wireless card is a ORiNOCO Wireless LAN PC Card The PCI-PCMCIA controller has a texas instruments chip on it and appears to be made by Elan. I was receiving some assistance on this, but the trail seems to have gone cold. I'm reposting all of the information that I previously supplied in the hopes of someone being able to help me. The last request for information I got was to provide a full dmesg output. This dmesg output is now at http://www.penguinpowered.org.uk/dmesg.txt The hardware combo works under XP but does not work under FreeBSD 4.6 The pc card worked in the old ISA controller, but I recently had to replace my board and I could not find a motherboard with an ISA slot. When I boot the machine up, I get the following output: pccardd[46]: Card Lucent Technologies(WaveLAN/IEEE) [Version 01.01] [] matched Lucent Technologies (WaveLAN/IEEE) [(null)] [(null)] pccardd[46]: Using IO addr 0x240, size 64 pccardd[46]: Setting config reg at offs 0x3e0 to 0x41, Rest time = 50 ms pccardd[46]: Assigning I/O window 0, start 0x240, size 0x40 flags 0x5 pccardd[46]: Assign wi0, io 0x240-0x27f, mem 0x0, 0 byes, irq 5, flags 0 wi0 at port 0x240-0x27f irq 5 slot 0 on pccard0 wi0: 802.11 address: 00:02:2d:02:a6:13 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Licent Firmware: Station 7.28.01 pccardd[46]: wi0: Lucent Technlogies (WaveLAN/IEEE) inserted. pccardd[46]: pccardd started This information became available when I set debuglevel in pccard.conf to 4. I am then able to assign and IP address to wi0 and set other options like network, etc using wicontrol. However when I do anything network related (ping, traceroute, etc) I get the following message: wi0: watchdog timeout The settings under XP are as follows: ORiNOCO Wireless LAN PC Card IRQ 5 I/O Range FF40-FF7F Texas Instruments PCI-1211 CardBus Controller (says Elan on card) Memory Range EF004000 - EF004FFF Memory Range FEBFF000 - FEBF Memory Range FABFF000 - FEBFEFFF I/O Range FE00 - FEFF I/O Range FD00 - FDFF IRQ 5 Memory Range 000DF000 - 000D I've tried both compiling the wi driver into the kernel and using it as a kernel module. The problem happens the same. I've recompiled the kernel and I have the following line for my pcic device in my kernel configuration file: device pcic0 at pci? irq 0 port 0x3e0 iomem 0xdf This iomem seems to be one of the ones XP is reporting as being in use for this device. I've also tried having the above line with at isa replacing at pci. I have found that IRQ 5 is used by the onboard usb controller, but even if I disable in the bios I still get this message popping up. -- - Wayne Pascoe - http://www.penguinpowered.org.uk/wayne/ Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
[Wayne Pascoe wayne@penguinpowered.org.uk] Re: Problems getting wireless card working with PCI adaptor
Sorry if this is a repost, but I didn't see this come through last night. M. Warner Losh [EMAIL PROTECTED] writes: : I have found that IRQ 5 is used by the onboard usb controller, but : even if I disable in the bios I still get this message popping up. Using a PCI expantion card requires you to use PCI routing. Can you post the complete dmesg? I need to know how we're setting things up and what you've posted so far isn't sufficient. I'm attaching a dmesg from a fresh install to this email. All I've done to the install is to add the following lines to /etc/rc.conf and reboot pccard_enable=YES pccard_ifconfig=inet 192.168.10.20 netmask 255.255.255.0 This dmesg is with USB disabled in the bios. At boot time, I see no other devices sharing interrupt 5 on the screen just before the bootloader. Ideally, I'd like to be able to use the PCMCIA card with USB but for now I'll just settle for seeing it work :) If the dmesg does not come through ok, please let me know and I will put it on my site and just send a link. Thanks in advance -- - Wayne Pascoe - http://www.penguinpowered.org.uk/wayne/ Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Problems getting wireless card working with PCI adaptor
Hi all, Sorry to cross post this, but I'm having problems getting this card working under FreeBSD. It works under Windows XP and I've had reports of it working on RedHat 7.3. I'm trying to get a wireless card going in a desktop machine. The wireless card is a ORiNOCO Wireless LAN PC Card The PCI-PCMCIA controller has a texas instruments chip on it and appears to be made by Elan. This combo works under XP but does not work under FreeBSD 4.6 The pc card worked in the old ISA controller, but I recently had to replace my board and I could not find a motherboard with an ISA slot. When I boot the machine up, I get the following output: pccardd[46]: Card Lucent Technologies(WaveLAN/IEEE) [Version 01.01] [] matched Lucent Technologies (WaveLAN/IEEE) [(null)] [(null)] pccardd[46]: Using IO addr 0x240, size 64 pccardd[46]: Setting config reg at offs 0x3e0 to 0x41, Rest time = 50 ms pccardd[46]: Assigning I/O window 0, start 0x240, size 0x40 flags 0x5 pccardd[46]: Assign wi0, io 0x240-0x27f, mem 0x0, 0 byes, irq 5, flags 0 wi0 at port 0x240-0x27f irq 5 slot 0 on pccard0 wi0: 802.11 address: 00:02:2d:02:a6:13 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Licent Firmware: Station 7.28.01 pccardd[46]: wi0: Lucent Technlogies (WaveLAN/IEEE) inserted. pccardd[46]: pccardd started This information became available when I set debuglevel in pccard.conf to 4. I am then able to assign and IP address to wi0 and set other options like network, etc using wicontrol. However when I do anything network related (ping, traceroute, etc) I get the following message: wi0: watchdog timeout The settings under XP are as follows: ORiNOCO Wireless LAN PC Card IRQ 5 I/O Range FF40-FF7F Texas Instruments PCI-1211 CardBus Controller (says Elan on card) Memory Range EF004000 - EF004FFF Memory Range FEBFF000 - FEBF Memory Range FABFF000 - FEBFEFFF I/O Range FE00 - FEFF I/O Range FD00 - FDFF IRQ 5 Memory Range 000DF000 - 000D I've tried both compiling the wi driver into the kernel and using it as a kernel module. The problem happens the same. I've recompiled the kernel and I have the following line for my pcic device in my kernel configuration file: device pcic0 at pci? irq 0 port 0x3e0 iomem 0xdf This iomem seems to be one of the ones XP is reporting as being in use for this device. I've also tried having the above line with at isa replacing at pci. I have found that IRQ 5 is used by the onboard usb controller, but even if I disable in the bios I still get this message popping up. Any advice on how to fix this, or even whether or not this card is supported would be MUCH appreciated. I've tried a Belkin controller as well with even less result (couldn't even get the machine to find a pccard port). -- - Wayne Pascoe - http://www.penguinpowered.org.uk/wayne/ If someone eventually manages to bag a B-2, that's a cool US$1bn worth of scrap metal - missiles, on the other hand, are cheap. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
wi0: watchdog timeout
Hi all, I'm trying to get a wireless card going in a desktop machine. The wireless card is a ORiNOCO Wireless LAN PC Card The PCI-PCMCIA controller has a texas instruments chip on it and appears to be made by Elan. This combo works under XP but does not work under FreeBSD 4.6 The pc card worked in the old ISA controller, but I recently had to replace my board and I could not find a motherboard with an ISA slot. When I boot the machine up, I get the following output: pccardd[46]: Card Lucent Technologies(WaveLAN/IEEE) [Version 01.01] [] matched Lucent Technologies (WaveLAN/IEEE) [(null)] [(null)] pccardd[46]: Using IO addr 0x240, size 64 pccardd[46]: Setting config reg at offs 0x3e0 to 0x41, Rest time = 50 ms pccardd[46]: Assigning I/O window 0, start 0x240, size 0x40 flags 0x5 pccardd[46]: Assign wi0, io 0x240-0x27f, mem 0x0, 0 byes, irq 5, flags 0 wi0 at port 0x240-0x27f irq 5 slot 0 on pccard0 wi0: 802.11 address: 00:02:2d:02:a6:13 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Licent Firmware: Station 7.28.01 pccardd[46]: wi0: Lucent Technlogies (WaveLAN/IEEE) inserted. pccardd[46]: pccardd started This information became available when I set debuglevel in pccard.conf to 4. I am then able to assign and IP address to wi0 and set other options like network, etc using wicontrol. However when I do anything network related (ping, traceroute, etc) I get the following message: wi0: watchdog timeout The settings under XP are as follows: ORiNOCO Wireless LAN PC Card IRQ 5 I/O Range FF40-FF7F Texas Instruments PCI-1211 CardBus Controller (says Elan on card) Memory Range EF004000 - EF004FFF Memory Range FEBFF000 - FEBF Memory Range FABFF000 - FEBFEFFF I/O Range FE00 - FEFF I/O Range FD00 - FDFF IRQ 5 Memory Range 000DF000 - 000D I've tried both compiling the wi driver into the kernel and using it as a kernel module. The problem happens the same. I've recompiled the kernel and I have the following line for my pcic device in my kernel configuration file: device pcic0 at pci? irq 0 port 0x3e0 iomem 0xdf This iomem seems to be one of the ones XP is reporting as being in use for this device. I've also tried having the above line with at isa replacing at pci. I have found that IRQ 5 is used by the onboard usb controller, but even if I disable in the bios I still get this message popping up. Any advice on how to fix this, or even whether or not this card is supported would be MUCH appreciated. I've tried a Belkin controller as well with even less result (couldn't even get the machine to find a pccard port). -- - Wayne Pascoe - http://www.penguinpowered.org.uk/wayne/ God gave you the power - Preacher on the Simpsons Hmm. You'd think he'd wanna... limit my power - Bart To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Where are the closed PR's ?
Hi there, I am trying to break into contributing to FreeBSD. I've been reading through the PR database, but the one thing that I do not see is the closed PR's. The reason I want to see these is to see some sample problems, and how they were closed. Being able to see the patch, etc. would also be great. So in short, where can I find the closed PR's ? Thanks, -- - Wayne Pascoe | WINDOWS: Where do you want to go today? [EMAIL PROTECTED] | LINUX: Where do you want to go tomorrow? http://www.molemanarmy.com | FreeBSD: Are you guys coming or what? | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
SMP machine does not reboot
Hi all, I've just done an install of 4.4-RELEASE onto a new dual processor machine. I then cvsup'd to 4_4 (4.4-RELEASE-p3), ran make world and make kernel KERNCONF=EHSB. uname -a reports : FreeBSD tethys.mydomain.com 4.4-RELEASE-p3 FreeBSD 4.4-RELEASE-p3 #0: Wed Jan 23 15:47:56 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EHSB i386 The machine seems to run ok, but if I do a shutdown -r now it does not reboot. I get the following message: syncing disks... 7 done Uptime: 48s amr0: flusing cache...done Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock for BSP cpu_reset_proxy: Stopped CPU 1 And there it sits. The motherboard is a GA-6VTXDR-C with 2 x 1.26 PIII Processors and 3GB Ram. Any idea what is wrong here ? Thanks -- - Wayne Pascoe | You cannot apply a technological [EMAIL PROTECTED] | solution to a sociological problem. http://www.molemanarmy.com | (Edwards' Law) | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Repost - f_type value in statfs structure
Chad David [EMAIL PROTECTED] writes: They are local :). Local means that the fs originates on the local machine. yes. I realise this now. Note to self, define what it is you are trying to do before trying to do it :( I could have saved so much time if I'd been clearer on that earlier. I think you should be able to call getvfsbyname() and check the flags in the resulting vfsconf struct for VFCF_SYNTHETIC, but I'm not sure how reliable that is. I'm pretty sure devfs is ok, but procfs might not be? Hmm. I've ended up using getfsfile. I'm just checking that the first 4 characters of .fs_spec are /dev I am working on the assumption that all filesystems I want to check would be mounted out of /dev. Other things like proc and devfs wouldn't be, so they would be skipped. Is this a safe assumption ? try vn_isdisk(vp, error) where vp is the vnode pointer to the block device? He is trying to do this from userland, I think...? Yes, I am. The kernel is faar beyond me for the forseeable future. Thanks for all the help. Merry Christmas and a hacky new year to all :) -- - Wayne Pascoe | WINDOWS: Where do you want to go today? [EMAIL PROTECTED] | LINUX: Where do you want to go tomorrow? http://www.molemanarmy.com | FreeBSD: Are you guys coming or what? | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Repost - f_type value in statfs structure
Chad David [EMAIL PROTECTED] writes: The issue that I am having is detecting valid filesystems to do further checks on. I am only interested in checking local filesystems such as UFS. Check for the MNT_LOCAL flag in f_flags. -- code example snipped -- Thanks for that. I've tried it and the problem with it is that it reports things like procfs and devfs as being local. The only things that don't appear local are things like nfs mounts. I guess I need a way to check only filesystems mounted off of disks. Is there any way of doing this ? -- - Wayne Pascoe | I laugh in the face of danger... [EMAIL PROTECTED] | Then I run and hide until it goes away! http://www.molemanarmy.com | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [SUGGESTION] - JFS for FreeBSD
Josef Karthauser [EMAIL PROTECTED] writes: It is probably a one man job if that man knows the kernel inside and out in these areas, and has the time and energy to see it through. I'd suggest that you find a much much smaller area to work on yourself for now though. (Take a look in the PR database for ideas of where to start). What is the PR database of which you speak and where can I find it? I am looking for a project to work on in my free time. Thanks, -- - Wayne Pascoe | The thing is, I was POSITIVE that I [EMAIL PROTECTED] | wasn't actually depressed, just that life http://www.molemanarmy.com | had no meaning and I was tired of living. | -- daystar on k5 | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Repost - f_type value in statfs structure
Hi all, Sorry to repost this, but I'm still trying to nail this issue. Any assistance would be much appreciated. I've written an application that uses getmntinfo which creates an array of statfs structs and stores information about mounted filesystems there. The issue that I am having is detecting valid filesystems to do further checks on. I am only interested in checking local filesystems such as UFS. Originally I was checking to see if f_type in the created struct was a certain number. The man page described this as being int f_type; /* type of filesystem */ I have now had to revert to checking f_fstypename against a string (ufs only for now) because f_type seems to contain different numbers for the same f_fstypename on different machines. Eg on three different machines running FreeBSD 4.4-STABLE I got 1, 3 and 5 for f_type where the f_fstypename was ufs. Is the f_type supposed to be consistent? If so, where is this normally defined? If the f_type is not supposed to be consistent, is there any way to check a the filesystem in the current statfs struct against a list of values without having to do if ( (strcmp(mounted_fs[count].f_fstypename, ufs) != 0) || (strcmp(mounted_fs[count].f_fstypename, hfs) !=0) ) ? Thanks -- - Wayne Pascoe | I haven't lost my mind... [EMAIL PROTECTED] | It's backed up on tape somewhere. http://www.molemanarmy.com | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Application using getmntinfo and statfs
Hi all, I've written an application that uses getmntinfo which creates an array of statfs structs and stores information about mounted filesystems there. The issue that I am having is detecting valid filesystems to do further checks on. I am only interested in checking local filesystems such as UFS. Originally I was checking to see if f_type in the created struct was a certain number. The man page described this as being int f_type; /* type of filesystem */ I have now had to revert to checking f_fstypename against a string (ufs only for now) because f_type seems to contain different numbers for the same f_fstypename on different machines. Eg on three different machines running FreeBSD 4.4-STABLE I got 1, 3 and 5 for f_type where the f_fstypename was ufs. Is the f_type supposed to be consistent? If so, where is this normally defined? If the f_type is not supposed to be consistent, is there any way to check a the filesystem in the current statfs struct against a list of values without having to do if ( (strcmp(mounted_fs[count].f_fstypename, ufs) != 0) || (strcmp(mounted_fs[count].f_fstypename, hfs) !=0) ) ? Thanks -- - Wayne Pascoe | What we need is either less corruption, [EMAIL PROTECTED] | or more chance to participate in it. http://www.molemanarmy.com | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
