Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE
Dieter wrote: > That sounds like a major clue that you probably have a very bad stick > of memory (probably a hard error). I would try booting with just 1 stick > at a time (or whatever the minimum is for your board) and isolate the bad > stick. > > Most likely with 7.2 something landed on the bad location that doesn't > actually get used, but with 8.0 something disk related lands there. I'll try that the next time I have a chance to reboot that server. > Let me guess, "Phoenix - AwardBIOS"? ...The very one. As per kenv output : smbios.bios.reldate="11/18/2008" smbios.bios.vendor="Phoenix Technologies Ltd." smbios.bios.version="2004Q3" smbios.chassis.maker="TYAN Computer Corp" smbios.memory.enabled="2097152" smbios.planar.maker="Tyan Computer Corporation" smbios.planar.product="S2895" smbios.planar.serial="0123456789" smbios.planar.version="TYAN Thunder K8WE S2895" smbios.socket.enabled="2" smbios.socket.populated="2" smbios.system.maker="TYAN Computer Corp." smbios.system.product="S2895" smbios.system.serial="0123456789" smbios.system.version="TYAN Thunder K8WE S2895" smbios.version="2.33" > On mine they can't even spell the name of the board correctly: > "TYAN Tomact K8E BIOS V1.00 022105" > (should be Tomcat) Such quality control. Ouch. > Mine hangs in boot if I have 2 JMB363 cards in the 2 PCIe x1 slots. > Moved one to the x16 slot and it boots. I've been blaming the > JMB363 cards but maybe the Phoenix AwardBIOS is the problem child? In my case I guess that would be it. I have never seen FreeBSD freeze on BTX level when loading from media, on any other computer. > Most of the time one of the cards doesn't do it's display the drives > and give me 5.1 nanoseconds to hit some control character to > enter a setup-a-raid thingy. And frequently FreeBSD doesn't see > one of the controllers and thus doesn't make it to multiuser. I'd I also happen to have these ones, but with my Intel NICs (no way I'm using the Marvell default ones, I get lost interrupt messages all over the place when I crank up network I/O a bit) > expect these events to be correlated but oddly they don't seem to be. > Sometimes it takes several reboots to get all the controllers seen. > I haven't seen an "out of memory" message, but the way things fly by > perhaps I just missed it. It always works correctly the first time > after a power cycle, so my theory is that the expansion cards aren't > getting reset properly. I have a firewire PCI card that got into > a funky mode and rebooting didn't fix it but a power cycle did. Just for the recall, it's more like "Could not load Option ROM" (I recall it was because it was out of memory buffers for these, but I don't have the exact message text available at hand), and it pops up randomly ; sometimes as you said, full power cycles do help. Sometimes they don't. > Tyan is supposed to be tier 1 but they aren't doing themselves > any favors with that pathetic excuse for firmware. Definitely not... -- Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo signature.asc Description: OpenPGP digital signature
Re: Hardware Support for new MB
Oliver Lehmann wrote: > I wonder if FreeBSD supports > > Audio: > - ALC690 (ASRock) > - ALC88S / ALC889 (MSI) > > SATA > - ICH10R Southbridge > > I guess since the ICH10R also can do AHCI this is at least supported by > the new (and old) ahci driver. It is supported by both old ata(4) drives, and new ahci(4). I've recently tested it in my lab. > But what about sound? All Realtek HDA codecs are supported fine. There can be some surprises from motherboard vendor, but usually they work out of the box. -- Alexander Motin ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscr...@freebsd.org"
Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE
In message <4b1392cf.5090...@darkbsd.org>, Stephane LAPIE writes: > >> Therefore, I am inclined to think the motherboard/memory (a "TYAN > >> Thunder K8WE S2895") would be at fault here, > >=20 > > I have been told that Tyan does a good job with memory, although even > > assuming that's true it could still be a memory problem. My Tyan > > board has a memory scrubbing feature that can be turned on in > > firmware, but I've never tried it. Also, you could try rotating the > > SIMMs and see if anything changes. > > The memory is brand new, from Corsair. I tried swapping the sticks > (while still using the same slots) and strangely enough, some > combinations just... don't boot at all. That sounds like a major clue that you probably have a very bad stick of memory (probably a hard error). I would try booting with just 1 stick at a time (or whatever the minimum is for your board) and isolate the bad stick. Most likely with 7.2 something landed on the bad location that doesn't actually get used, but with 8.0 something disk related lands there. > Also, completely unrelated to the SATA controller, some quirks on this > motherboard (though at BIOS level) have been annoying me quite a lot : > - Booting FreeBSD from anything besides an IDE device has a 80% chance > of freezing the computer at BTX level. > - Sometimes the Option ROMs (this including the VGA card) are not loaded > properly because of an "out of memory" problem at BIOS level. > > However, once the system is booted, it can go on for several months. > (Though, I have witnessed one "Fatal error 12: Page fault"-type kernel > panic in six months) Let me guess, "Phoenix - AwardBIOS"? On mine they can't even spell the name of the board correctly: "TYAN Tomact K8E BIOS V1.00 022105" (should be Tomcat) Such quality control. Mine hangs in boot if I have 2 JMB363 cards in the 2 PCIe x1 slots. Moved one to the x16 slot and it boots. I've been blaming the JMB363 cards but maybe the Phoenix AwardBIOS is the problem child? Most of the time one of the cards doesn't do it's display the drives and give me 5.1 nanoseconds to hit some control character to enter a setup-a-raid thingy. And frequently FreeBSD doesn't see one of the controllers and thus doesn't make it to multiuser. I'd expect these events to be correlated but oddly they don't seem to be. Sometimes it takes several reboots to get all the controllers seen. I haven't seen an "out of memory" message, but the way things fly by perhaps I just missed it. It always works correctly the first time after a power cycle, so my theory is that the expansion cards aren't getting reset properly. I have a firewire PCI card that got into a funky mode and rebooting didn't fix it but a power cycle did. Tyan is supposed to be tier 1 but they aren't doing themselves any favors with that pathetic excuse for firmware. ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscr...@freebsd.org"
Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE
Dieter wrote: > In message <4b13159d.9010...@darkbsd.org>, Stephane LAPIE writes: > >> On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O >> bursts (confirmed with zpool iostat), before totally freezing down and >> locking the ZFS pool (the system is still up and only ZFS based file >> systems are unusable in this state), probably to avoid data corruption. >> Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)" >> error message showing up, on a random hard disk. > > And there are these, which you didn't mention: >> ad1: FAILURE - SET_MULTI status=3D51 error=3D4 >> ad12: FAILURE - SET_MULTI status=3D51 error=3D4 > (No, I don't know what that means, sorry.) Ah, actually I do have an idea as to what these are about : These two disks are SSDs I'm using in my ZFS pool as cache devices. So I guess this is the kind of error that says "I tried to use an access mode this device was not designed for". In the same fashion, I also get such error messages when trying SMART checks on ad0, which is a flash card. ad0: FAILURE - SMART status=51 error=4 So, I think these could safely be discarded under "not a normal disk device". (Unless I'm completely mistaken about this...) >> ad18: 1430799MB at ata9-master SATA300 >> ad20: 1430799MB at ata10-master SATA300 > > How old is the SD1A disk? As you may know, Seagate had various troubles > with the .11 firmware. I have some of the ST31500341AS CC1H and mine are > new enough that they are supposed to be ok. I bought all these disks at roughly the same time around April, but strangely got an odd one in the lot and didn't bother to change it. From what I checked with the Seagate page about the firmware issues, SD1A is not affected. I also have three spare disks in a drawer in case a problem occurs. >> Therefore, I am inclined to think the motherboard/memory (a "TYAN >> Thunder K8WE S2895") would be at fault here, > > I have been told that Tyan does a good job with memory, although even > assuming that's true it could still be a memory problem. My Tyan > board has a memory scrubbing feature that can be turned on in > firmware, but I've never tried it. Also, you could try rotating the > SIMMs and see if anything changes. The memory is brand new, from Corsair. I tried swapping the sticks (while still using the same slots) and strangely enough, some combinations just... don't boot at all. Also, completely unrelated to the SATA controller, some quirks on this motherboard (though at BIOS level) have been annoying me quite a lot : - Booting FreeBSD from anything besides an IDE device has a 80% chance of freezing the computer at BTX level. - Sometimes the Option ROMs (this including the VGA card) are not loaded properly because of an "out of memory" problem at BIOS level. However, once the system is booted, it can go on for several months. (Though, I have witnessed one "Fatal error 12: Page fault"-type kernel panic in six months) Thanks again for your time. -- Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo signature.asc Description: OpenPGP digital signature
