similar to: FreeBSD and serial ata

Howdy. I apologize for vagueness of this report but I am not immediately sure how to proceed with this or what details will be relevant. I look after a community server which has been running just fine for the last 6 months or so with no disk issues at all. The box has an all in one Shuttle motherboard which uses the VIA 8233 ATA133 disk controller according to what I see from dmesg. The

Hi all, I have been tracking -STABLE on one of my home machines for a little while, now and noticed something the other day. I was given this system, and I have only run FreeBSD-STABLE on it. The motherboard is a Supermicro370SWD with an Intel 810 "Whitney" chipset (82810DC100 GMCH + 82801AA ICH). The docs say that there is support for UDMA66, but FreeBSD reports that the drive is

Hello, I didn't recieve a response on freebsd-mobile, so I'm trying here. I'm trying to install FreeBSD 4.7-RELEASE or 5.0-RELEASE onto my Dell Inspirion 8100. I'mjust doing a Standard installation and when FDisk loads I get: Disk name: ad0 DISK Geometry: 88 cyls/255 heads/63 sectors = 1413720 sectors (690MB) So I go and manually change the drive geometry with the G option and

Hi List, I've been getting the following EDAC memory errors EDAC MC0: CE page 0xeb0dd, offset 0x0, grain 4096, syndrome 0x45, row 3, channel 0, label "": i82875p CE and from this seeing that these errors have been corrected. Checking cat /sys/devices/system/edac/mc/mc0/csrow3/ch0_ce_count gives me a count of 4 thus I now know that csrow3 - ch0 is the problem My question is, how

Hi there. OS version: FreeBSD 4.7-Stable FreeBSD #3 I just added a disk to my box and after playing with fdisk and disklabel with this configuration: fdisk: **************************************************************** g c16383 h16 s63 p 1 165 0 39102336 **************************************************************** disklabel

I'm trying to get stable booted on a little ITX board off of a CF card, but it hangs as it's trying to run init. Here's what the boot looks like. SMAP type=01 base=0000000000000000 len=000000000009fc00 SMAP type=01 base=000000000009fc00 len=0000000000000400 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000ffff0000 len=0000000000010000 SMAP type=01

Here's a patch against 4.8-RELEASE kernel that allows disk writes on softupdates-enabled filesystems to be delayed for (theoretically) arbitrarily long periods of time. The motivation for such updating policy is surprisingly not purely suicidal - it can allow disks on laptops to spin down immediately after I/O operations and stay idle for longer periods of time, thus saving considerable amount

Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have

If you start to experience problems with ata devices, please direct your report this way. Thanks -lq

Hi there, sorry for rather long mail. Two verbose dmesgs and `pciconf -vl` outputs attached. trying to set up new machine based on ASUS P4BGL-MX motherboard, I'd encountered hangs after detecting pcib1 (ICH2). MB has rl 8100 ethernet chip onboard. This is for 4.8-R; however, machine hangs in very similar way also with 4.4-R and 5.1-R. Matrix of hangs: Onboard Ether External Ether Result

Hello, I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the same day. I had a panic that looks to me very similiar to the one described here (hence the subject): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html What caught my curiosity is the message: Unread portion of the kernel message buffer: acd0: WARNING - TEST_UNIT_READY read

Hi, in the kernel I have these lines: [...] device miibus # MII bus support device rl device ed options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=0 #limit verbosity options IPDIVERT #divert sockets options DUMMYNET

Hi everyone, I just finished installing FreeBSD 6 RELEASE on my Toshiba Tecra A4 laptop and the installation was fine, however, when I rebooted the machine, I don't get the boot loader screen as if the machine can not see my drive! I tried the reinstalling and ensured that I set the slice to be bootable but that didn't change anything. Not sure if this is a common issue with FreeBSD 6 on

I am having problems with silent data corruption on (some) drives connected to an MCP55 SATA controller. I have two servers, both running RELENG_7_0/amd64. One has the 570 Ultra chipset, the other has 570 SLI. Both chipsets have the MCP55 SATA controller. The server with 570 Ultra chipset has a bunch of older 250GB SATA-150 drives hooked up to the MCP55 controller and it is working just fine.

Dear colleagues, experimenting with vinum stripes and mirrors, I'd stuck myself with the following: panic: throw_rude_remark: called without config lock (from vinumconfig.c:throw_rude_remark:103) The system before this panic has two 160G drives with two vinum partitions on each (one for mirrored root and one for the rest with swap between); these were ad0 and ad2. For the experiments,

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if

I have a Lite-On 24102B burner on an Epox 7KXA (VIA 686A southbridge) together with a few SCSI disks. I recently upgraded from FreeBSD 4.5 to 4.7 then almost immediately to 4.8. I've had trouble with the burner since. With FreeBSD 4.5, I used "sysctl hw.atamodes=---,---,dma,---" to set the burner to DMA. Everything then worked fine. As far as I know it was using UDMA33.

Hi, hackers : Yesterday night and this morning, I cvsup my system to latest STABLE branch source (RELENG_4). All make buildworld, buildkernel, and installkernel procedure was completed with no error. But when I boot into single user mode and try to make installworld, I always got " touch: not found " error. Does anyone encounter this situation ? I have no idea about that. :-( Here is

Heya.. Yesterday someone "attacked" by box by connection to several ports.. In other words, a simple portscan.. yet, since my box has "log_in_vain" enabled, so it tries to log everything to /var/log/messages, since the logfile got full and the size went over 100K, it tried to rotate the log to save diskspace. (Apr 16 21:00:00 omikron newsyslog[32137]: logfile turned over due

Hello, I have the following hardware configuration. Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered ECC DRAM, Onboard 3Com NIC (xl type) Radeon 8500 AGP video card Adaptec 3210S SCSI RAID controller Comtrol RocketPort 8 port PCI serial card I have started to experience some odd system lockups in the past couple months, and it seems to be getting worse. I particular,