Problem with aac0 on FreeBSD 6.1R/amd64
hi, I have Dawning A950(4 CPUs) with raid card Adaptec SCSI RAID 2230SLP. when install FreeBSD 6.1R/amd64, everying is fine except probing aac: aac0: COMMAND 0x TIMEOUT AFTER XXX SECONDS kernel trap 12 with interrupts disabled. This machine can install TurboLinux. Thankfull for any advice --hwh ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.X wont boot on Dell XPS 700
I have a new XPS 700 Pentium D 3.6 Dual Core with 2 gigs RAM, 2 250 GB SATA drives, and 2 NVIDIA GeForce 7900GS video cards. So far I have tried: 6.0-RELEASE - will boot to sysinstall but finds no drives. 6.1-RELEASE - hangs after probing md0 and first hard drive. 6.1-STABLE - hangs after probing md0 and first hard drive. 7.0-CURRENT - hangs after probing md0 and both hard drives. I have unplugged the USB keyboard and mouse and used a PS/2 keyboard. Disabling ACPI causes a panic on all versions. Anyone have a clue what it will take to install on this machine? -- Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD with a Gigabyte GA-K8NSC?
Hi I'm about to get a new server... In this case what I'm looking at is a Gigabyte GA-K8NSC mobo with nForce3 250Gb chipset, and a AMD 64 3200+ Venice S939. Does anyone have any experience with FreeBSD (6.1) and this mobo/ chipset? Does the network work? How good? SATA? Any stability/ performance issues? I did notice it was mentioned on http://www.freebsd.org/platforms/ amd64/motherboards.html on 5.4 with the only comment Sound and USB untested... So.. anyone got more detailed experience than that? Thanks :) -- Johan Ström [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LSI/amr driver controller cache problem?
On Fri, Sep 01, 2006 at 11:15:37AM -0600, Scott Long wrote: Patrick M. Hausen wrote: [snip] It is very arguably a bug in the LSI firmware if it is actually dumping its cache when a PCI reset occurs, especially if a battery unit is present. However, I seriously doubt that you will get anyone at LSI to listen to this problem. Do you get any messages on the console at shutdown about the amr driver flushing the cache? Also, check the cache setting on the drives itself. Maybe the drives are loosing power or getting reset while data is in their cache. It's bad practice to enable the write cache on a drive in an RAID array for just this very reason, but some vendors do it anyways in an attempt to cover up poor performance. Is there some way to tell if write caching is turned on or not for the drives in the array? In particular, I have an Areca controller (ARC-1210) with 4 SATA drives attached that I would like to check for this on. Bob -- Bob Willcox Possessions increase to fill the space [EMAIL PROTECTED]available for their storage. Austin, TX -- Ryan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD bemused by USB card reader
I was playing with a USB card reader and FreeBSD, and I've discovered some quirks that I imagine need attention. The driver involved is umass(4). The card reader itself has four slots in which various formats of flash card can be inserted, and is a USB device. The quirks are as follows: 1. If the card reader is plugged in to the USB with no cards inserted, the result is a storm of messages, one for each of the four slots, saying in effect Medium not present; Unretryable error. Ok, kindof, but given how hard it tries (more than 80 lines of dmesg output are generated!), I think BSD is missing the point (ie, the media may come later...). 2. Device entry points da0, da1, da2 and da3 are created in /dev without any slice or partition subdevices (can somebody please point me to documentation which explains when and why I get da0s1 or da0a or da0s1a: I'd really like to know at the block device level what's going on there). 3. When I insert a card into the card reader: no messages are generated, and no new devices are generated (so I have to mount the device as da0, and can't mount any slices or partitions). Of course, there is a workaround here: plugging the card into the card reader *before* plugging it into the USB port works, but FreeBSD is underperforming here. For example, OSX has no problem in recognising a card being inserted or removed. Similarly, removing a card from the reader is also not noticed. I've tried `camcontrol rescan 0` (or all), as suggested in umass(4), but it doesn't change the devices present in /dev, so is clearly *not* recognising insertion or removal of cards. I don't know if this is an issue or not, but `usbdevs` never shows the cards, only the card reader. 4. This one is quite interesting: if I reboot with the card reader installed with a card in one slot (I was trying to boot off the card; no luck) and then remove it: it fails to remove da1, da2 and da3 from /dev. When I re-insert the card reader... I get two copies of da1! Look: # ls /dev/da1* /dev/da1 /dev/da1 Looks well dodgy to me. Ok, tried again (with the card removed), and this time I get two copies of da2 and da3 also: # ls /dev/da* /dev/da0 /dev/da1 /dev/da1 /dev/da2 /dev/da2 /dev/da3 /dev/da3 How very very strange. In case it's of interest, I've attached the output from `dmesg`. Oh: and here's `uname -a`: FreeBSD venus.araneidae.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon Aug 28 18:32:17 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386pci0: multimedia, audio at device 7.5 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xd800-0xd8ff mem 0xe581-0xe58100ff irq 5 at device 8.0 on pci0 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:40:f4:b8:db:20 rl1: RealTek 8139 10/100BaseTX port 0xdc00-0xdcff mem 0xe5811000-0xe58110ff irq 10 at device 9.0 on pci0 miibus1: MII bus on rl1 rlphy1: RealTek internal media interface on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: Ethernet address: 00:40:f4:b8:db:1f rl2: RealTek 8139 10/100BaseTX port 0xe000-0xe0ff mem 0xe5812000-0xe58120ff irq 11 at device 11.0 on pci0 miibus2: MII bus on rl2 rlphy2: RealTek internal media interface on miibus2 rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl2: Ethernet address: 00:40:f4:b8:db:1e fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xcbfff,0xcc000-0xc,0xd-0xda7ff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 umass0: ICSI 2.0 Card Reader, rev 2.00/1.3a, addr 2 Timecounter TSC frequency 532640640 Hz quality 800 Timecounters tick every 1.000 msec ad2: 38204MB SAMSUNG MP0402H YQ200-04 at ata1-master UDMA100 da0 at umass-sim0 bus 0 target 0 lun 0 da0: ICSI CF Card CF 1.3A Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 122MB (250368 512 byte sectors: 64H 32S/T 122C) (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:1):
Re: atheros driver: countrycode and athdebug
Daniel Dvoøák wrote: You can override the country code but the potential values depends on the regdomain. I thought hw.ath.countrycode was r/w but it appears you can only set via the tunable api (kenv hw.ath.countrycode=XXX). The dev.ath mib must be r/o since you cannot (yet) change this after attaching the device (the driver does not implement it). Adding support to do this is not a big deal but hasn't been done; feel free to supply a patch. Ok, I tried to set via the tunable api kenv through loader, but this is the result: # ifconfig ath0 ifconfig: interface ath0 does not exist # ifconfig ath1 ifconfig: interface ath1 does not exist ath0: Atheros 5212 mem 0x8000-0x8000 irq 12 at device 13.0 on pci0 ath0: unable to collect channel list from hal; regdomain likely 96 country code 203 device_attach: ath0 attach returned 22 ath1: Atheros 5212 mem 0x800c-0x800c irq 9 at device 17.0 on pci0 ath1: unable to collect channel list from hal; regdomain likely 96 country code 203 device_attach: ath1 attach returned 22 ath0: Atheros 5212 mem 0x8000-0x8000 irq 12 at device 13.0 on pci0 ath0: unable to collect channel list from hal; regdomain likely 96 country code 203 device_attach: ath0 attach returned 22 ath1: Atheros 5212 mem 0x800c-0x800c irq 9 at device 17.0 on pci0 ath1: unable to collect channel list from hal; regdomain likely 96 country code 203 device_attach: ath1 attach returned 22 # sysctl hw.ath hw.ath.hal.version: 0.9.17.2 hw.ath.hal.dma_brt: 2 hw.ath.hal.sw_brt: 10 hw.ath.hal.swba_backoff: 0 hw.ath.dwell: 200 hw.ath.calibrate: 30 hw.ath.outdoor: 1 hw.ath.xchanmode: 1 hw.ath.countrycode: 203 hw.ath.regdomain: 0 -- not setted to 96 hw.ath.rxbuf: 40 hw.ath.txbuf: 100 So ? I don´t know. :) Your card has a regdomain in the eeprom that is 96. I believe that's the FCC regdomain. With that regdomain you cannot specify any country code except US. The hw.ath mib tree mostly contains default settings that are applied to instances of the ath driver as they are attached. The hw.ath.regdomain is there in case I'm able to add the ability to override the eeprom regdomain at some point the future (something high on my todo list). In the mean time it is well known how to deal with this situation--take a look at the madwifi.org web pages. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cron abuse
I reinstalled my crontab (with crontab -e) after a user edited the crontab directly and nothing appears to be working now. The mails I get suggest that it's trying to find 'root' and 'operator' as programs. Would somebody kindly help me recover from this copilot error? I can't find anything in crontab(5) or cron(8). My procedure was to invoke crontab -e (getting a blank emacs editor window), split the window, opening a copy of the /etc/crontab copied the contents into the temporary crontab save and exit kill -1 1 these are the e-mails I'm getting Subject: Cron [EMAIL PROTECTED] root /usr/libexec/atrun root: not found TIA! Don Wilde ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheros driver under high load, panics and even more freezes
Daniel Dvořák wrote: Ok, I will upgrade my boxes and I will do simple ping tests again. Did you see my sysctl.conf file ? I mean these options: kern.ipc.maxsockbuf=2097152 net.inet.ip.fastforwarding=1 net.inet.tcp.sendspace=65536 Could be this connected with increasing latency up to 500ms ? Seems unlikely but I have little to go on. You can easily identify whether the delays are in the OS or due to wireless issues by sniffing traffic. Tools like athstats are also important for diagnosing problems. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron abuse
On 9/3/06, David Wolfskill [EMAIL PROTECTED] wrote: Formats for /etc/crontab user-specific crontabs are different; the former contains a field for the user under whose auspices the command should be run, while the latter does not (as it's implied by the owner of the crontab in question). Peace, david Thanks for taking the time to answer, David. Yes, I see that. I'm reinstalling the old /etc/crontab back into /etc/crontab. This is what's driving me nuts. Why would it be acting as though it's a user crontab? %D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron abuse
On 9/3/06, David Wolfskill [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 11:43:01AM -0500, Don Wilde wrote: ... Thanks for taking the time to answer, David. Sure thing. Yes, I see that. I'm reinstalling the old /etc/crontab back into /etc/crontab. OK. This is what's driving me nuts. Why would it be acting as though it's a user crontab? I doubt that it is -- more likely, a copy of /etc/crontab was installed as a user crontab -- go check /var/cron/tabs. Yes, it did exactly that. Will removing the /var/cron/tabs entry make everything Just Work again? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron abuse
On Sun, Sep 03, 2006 at 11:57:44AM -0500, Don Wilde wrote: On 9/3/06, David Wolfskill [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 11:43:01AM -0500, Don Wilde wrote: ... Thanks for taking the time to answer, David. Sure thing. Yes, I see that. I'm reinstalling the old /etc/crontab back into /etc/crontab. OK. This is what's driving me nuts. Why would it be acting as though it's a user crontab? I doubt that it is -- more likely, a copy of /etc/crontab was installed as a user crontab -- go check /var/cron/tabs. Yes, it did exactly that. Will removing the /var/cron/tabs entry make everything Just Work again? Yes or run crontab -e and delete everything in the editor window before saving. One good thing about your problem is it reminded me I'd forgotten to MFC the anti foot shooting measure I added a while back which causes crontab to refuse to load /etc/crontab as a user crontab. It doesn't try very hard, but it does prevent the most common error. -- Brooks pgpdwkRsQA33T.pgp Description: PGP signature
Re: FreeBSD bemused by USB card reader
Date: Sun, 3 Sep 2006 15:29:06 + (GMT) From: Michael Abbott [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-817021360-1157297346=:39827 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed I was playing with a USB card reader and FreeBSD, and I've discovered some quirks that I imagine need attention. The driver involved is umass(4). The card reader itself has four slots in which various formats of flash card can be inserted, and is a USB device. The quirks are as follows: 1. If the card reader is plugged in to the USB with no cards inserted, the result is a storm of messages, one for each of the four slots, saying in effect Medium not present; Unretryable error. Ok, kindof, but given how hard it tries (more than 80 lines of dmesg output are generated!), I think BSD is missing the point (ie, the media may come later...). 2. Device entry points da0, da1, da2 and da3 are created in /dev without any slice or partition subdevices (can somebody please point me to documentation which explains when and why I get da0s1 or da0a or da0s1a: I'd really like to know at the block device level what's going on there). 3. When I insert a card into the card reader: no messages are generated, and no new devices are generated (so I have to mount the device as da0, and can't mount any slices or partitions). Of course, there is a workaround here: plugging the card into the card reader *before* plugging it into the USB port works, but FreeBSD is underperforming here. For example, OSX has no problem in recognising a card being inserted or removed. Similarly, removing a card from the reader is also not noticed. I've tried `camcontrol rescan 0` (or all), as suggested in umass(4), but it doesn't change the devices present in /dev, so is clearly *not* recognising insertion or removal of cards. I don't know if this is an issue or not, but `usbdevs` never shows the cards, only the card reader. 4. This one is quite interesting: if I reboot with the card reader installed with a card in one slot (I was trying to boot off the card; no luck) and then remove it: it fails to remove da1, da2 and da3 from /dev. When I re-insert the card reader... I get two copies of da1! Look: # ls /dev/da1* /dev/da1 /dev/da1 Looks well dodgy to me. Ok, tried again (with the card removed), and this time I get two copies of da2 and da3 also: # ls /dev/da* /dev/da0 /dev/da1 /dev/da1 /dev/da2 /dev/da2 /dev/da3 /dev/da3 How very very strange. Strange, yes. Surprising, no. umass (and USB support is not in the best of shape in FreeBSD. But there is hope. A re-written USB driver set is currently in development. It's not even in -current, but the word from a limited number of testers is that it's a BIG improvement. (Giant free!) On the down side, umass is not one of the drivers that has been re-written last I checked. It is by far the most heavily utilized of the remaining drivers, but is also one of the more complex because of the huge number of different devices it must work with. I suspect that little work will be done on fixing the existing driver unless someone spots an easy bug to fix. (One or two of your problems MAY fit that category, but I am not familiar enough with the driver to really have an opinion worth listening to. I suspect that the new drivers are still a month or two from hitting -current and I don't know if they will be such that they can be merged into 6-stable or not. (If they require API or ABI changes, they can't go into V6.) If you want to follow this more closely (and maybe get some of your concerns addressed), you might try subscribing to the freebsd-usb list and sending details there and sending in a PR on what you've seen. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp6sDZXJyEwx.pgp Description: PGP signature
Re: cron abuse
One good thing about your problem is it reminded me I'd forgotten to MFC the anti foot shooting measure I added a while back which causes crontab to refuse to load /etc/crontab as a user crontab. It doesn't try very hard, but it does prevent the most common error. -- Brooks Which is what happened here. :) It never ceases to amaze me how rich a world FreeBSD is, and there's always more to learn. Many tanks of beer to all who added suggestions. The root crontab was indeed saved by my actions as /var/cron/tabs/root, and it was that which was complaining vociferously. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD bemused by USB card reader
On Sun, 3 Sep 2006, Kevin Oberman wrote: From: Michael Abbott [EMAIL PROTECTED] # ls /dev/da* /dev/da0 /dev/da1 /dev/da1 /dev/da2 /dev/da2 /dev/da3 /dev/da3 How very very strange. Strange, yes. Surprising, no. umass (and USB support) is not in the best of shape in FreeBSD. Does this phenomenon also point to a problem with devfs, or is the set of device names completely delegated to the corresponding driver (umass) by devfs? If you want to follow this more closely (and maybe get some of your concerns addressed), you might try subscribing to the freebsd-usb list and sending details there and sending in a PR on what you've seen. Sigh. I ought to. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Recovering Swap Partition
Hi all, After a random power outage, my FreeBSD 6.1 box failed to reboot because the swap partition is toast. The disklabel looks to be intact. I've been researching all afternoon trying to find out how to recover the swap with something like newfs, but I haven't found any examples of how to do it, only how to create the swap during a system installation. Can anyone tell me which tool to use and show me either an example or point me in the direction of more information? -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
malloc(): warning: recursive call
Just got this while running a script that uses mail(1) to send mail: mail in malloc(): warning: recursive call mail: Out of memory: Programming error $ uname -a FreeBSD schoner 6.1-STABLE FreeBSD 6.1-STABLE #11: Tue Aug 29 09:46:29 CEST 2006 root@:/usr/obj/usr/src/sys/EISENBOOT i386 $ ls -l /etc/malloc.conf ls: /etc/malloc.conf: No such file or directory Running the script again did not produce the message again. Cosmic rays? Anything I could try to find the cause? Stefan -- Stefan Bethke [EMAIL PROTECTED] Fon +49 170 346 0140 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recovering Swap Partition
In the last episode (Sep 03), Ron Tarrant said: After a random power outage, my FreeBSD 6.1 box failed to reboot because the swap partition is toast. The disklabel looks to be intact. I've been researching all afternoon trying to find out how to recover the swap with something like newfs, but I haven't found any examples of how to do it, only how to create the swap during a system installation. Can anyone tell me which tool to use and show me either an example or point me in the direction of more information? What error are you getting? Swap doesn't need to be formatted; it just has to exist if enabled. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD bemused by USB card reader
On Sun, 3 Sep 2006, Kevin Oberman wrote: From: Michael Abbott [EMAIL PROTECTED] # ls /dev/da* /dev/da0 /dev/da1 /dev/da1 /dev/da2 /dev/da2 /dev/da3 /dev/da3 How very very strange. Strange, yes. Surprising, no. umass (and USB support) is not in the best of shape in FreeBSD. Does this phenomenon also point to a problem with devfs, or is the set of device names completely delegated to the corresponding driver (umass) by devfs? Almost certainly. The creation of devfs entries is done by the driver (or at least the calls to the devfs to do so) are in the driver. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpPzbd0CaBoV.pgp Description: PGP signature
Re: malloc(): warning: recursive call
Stefan Bethke wrote: mail in malloc(): warning: recursive call Cosmic rays? Anything I could try to find the cause? I know what it is, but you won't going to like it. As far as I understand this happens when a process gets a signal in the middle of using malloc(), and the signal handler also uses malloc(). The solution would be not to use malloc() in a signal handler, but this is tricky since unknown code can use malloc() (e.g. printf()?). This appears to be undefined by standards, but GNU libc allows it because it makes sense, while phkmalloc dissallows it, causing (me) considerable problems with certain applications. I hope jemalloc is better in this respect :) I don't know how it happened in mail(1) if mail(1) is the FreeBSD version. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cardbus0: Resource not specified in CIS: id=14, size=400?????
I have a Netgear FA511 Cardbus NIC that I am trying to use in a Dell Inspiron 8600 laptop running 6.1-STABLE, but with limited success. When I insert it, I get the message cardbus0: Resource not specified in CIS: id=14, size=400 appear as part of the cardbus probe. The card superficially works, but very unreliably (e.g., quite a few dc0: watchdog timeout messages and no network traffic at times). What does cardbus0: Resource not specified in CIS: id=14, size=400 mean? Is this a hardware or a firmware or a driver issue? When I insert the NIC into the Dell Inspiron 8600 laptop, the MAC address that gets assigned to the interface is 00-00-00-00-00-00. This happens both under FreeBSD and Windows XP. However, when I tried the NIC in a friend's Acer laptop, the MAC address was correctly reported by Windows XP (couldn't try FreeBSD), and corresponds with the one printed on the underside of the NIC. So, it seems that the Cardbus NIC itself is okay, just not in the Dell laptop. :-( Is this something that is fixable, e.g., with a suitable device.hints or sysctl setting? Here's what is output on the Dell Inspiron 8600 when I insert the Netgear FA511 NIC (extra cardbus debugging enabled): cbb0: card inserted: event=0x, state=3920 cbb0: cbb_power: 3V TUPLE: LINKTARGET [3]: 43 49 53 Product version: 5.0 Product name: NETGEAR, Inc. | FA511 | CardBus Mobile Adapter | 1.00 | Manufacturer ID: 2d021a51 Functions: Network Adaptor, Multi-Functioned Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 cardbus0: Opening BAR: type=IO, bar=10, len=0100 TUPLE: Unknown(0x04) [7]: 03 01 00 00 00 00 ff TUPLE: Unknown(0x05) [5]: 41 80 fb 00 ff CIS reading done cardbus0: Resource not specified in CIS: id=14, size=400 cardbus0: Non-prefetchable memory at f6001000-f60013ff cardbus0: IO port at d000-d0ff dc0: Netgear FA511 10/100BaseTX port 0xd000-0xd0ff mem 0xf6001000-0xf60013ff irq 11 at device 0.0 on cardbus0 miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: link state changed to DOWN dc0: link state changed to UP Here is how the Cardbus adapter is probed during boot: pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci_link1: BIOS IRQ 11 for 2.3.INTA is invalid pci2: ACPI PCI bus on pcib2 cbb0: TI4510 PCI-CardBus Bridge at device 1.0 on pci2 cbb0: Found memory at f600 cbb0: Secondary bus is 0 cbb0: Setting primary bus to 2 cbb0: Secondary bus set to 3 subbus 4 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 Finally, here is the output of pciconf -vl for the laptop (the PCI4510SDFSDFSD PC Card Controller SDFSDAFSADFSDAFSDAF description for the Cardbus bridge looks highly suspicious to me): [EMAIL PROTECTED]:0:0:class=0x06 card=0x016a1028 chip=0x33408086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82855PM Host-Hub Interface Bridge' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x33418086 rev=0x03 hdr=0x01 vendor = 'Intel Corporation' device = '82855PM AGP Bridge' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x016a1028 chip=0x24c28086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x016a1028 chip=0x24c48086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x016a1028 chip=0x24c78086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x016a1028 chip=0x24cd8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 2.0 EHCI Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:30:0:class=0x060400 card=0x chip=0x24488086 rev=0x81 hdr=0x01 vendor = 'Intel Corporation' device = '82801BAM/CAM/DBM (ICH2-M/3-M/4-M) Hub Interface to PCI Bridge' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:31:0:class=0x060100 card=0x chip=0x24cc8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DBM (ICH4-M) LPC Interface Bridge' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:31:1: class=0x01018a card=0x016a1028 chip=0x24ca8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DBM (ICH4-M) UltraATA/100 EIDE Controller' class= mass storage subclass = ATA [EMAIL
Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT)
On Sat, Sep 02, 2006 at 04:23:21AM -0500, Alex Salazar wrote: Apologies for the long message, and thanks in advance for any response. I've just bought one of those new generation Dell servers, specifically, the PowerEdge 1950. This is a dual Intel Dual Core Xeon 5050, 3.0 GHz, 667MHz FSB, 1GB 533MHz RAM, system. This server has a LSI Logic SAS 5/i integrated adapter and dual embedded Broadcom NetXtreme II 5708 Gigabit Ethernet NIC. snip Just wanted to say that I'm running FreeBSD/i386 6.1-STABLE on two Dell PE 1950's without any problems. The only thing I had to do was update the bce driver for the NIC, but other than that the mfi RAID controller is detected properly, as well as the SAS disks and RAID array. The only difference I can think of is perhaps the firmware and BIOS versions Attached is the dmesg output from one of the two 1950's I've got. with regards, -- Morten A. Middelthon I have been Foolish and Deluded, and I am a Bear of No Brain at All. -- Pooh pgpsU5t10vT6h.pgp Description: PGP signature
