New mobo means USB problems
I recently got a new motherboard and now I have trouble with USB. I had no problems with my two USB drives before, but now a) I can't boot with my external USB hard drive connected and powered on, and b) moving files onto my Creative MP3 player causes that file system to hang. This second problem seems to be the same as was mentioned here on 5 May, at http://docs.FreeBSD.org/cgi/mid.cgi?iiuui3-q31.ln1 The new motherboard is an ASUS P5S800-VM and the BIOS is right up to date. It comes with USB 2.0 built in. I'm running FreeBSD 6.1-STABLE, and built a new world on 6 May, after I got this new mobo home. A healthy dmesg is at the bottom of this message. I saw some talk on mailing lists about ACPI being related to this kind of thing, so I tried booting without it (with unset acpi_load at the boot prompt) and it panicked, which wasn't helpful. a) Timeouts and failures when booting with external USB hard drive plugged in and turned on. I have a Maxtor drive in an external USB 2.0 enclosure. When it's connected and turned on, I cannot boot. The different bits from dmesg look like this: [same stuff as usual up to this point; see below] uhub3: 8 ports with 8 removable, self powered [ten-second or so delay, which I don't see on a normal boot] atapci1: SiS 181 SATA150 controller port 0xeff0-0xeff7,0xefe4-0xefe7,0xefa8-0xefaf,0xefe0-0xefe3,0xef90-0xef9f,0xe480-0xe4ff irq 17 at device 5.0 on pci0 [continues as normal until ...] ad0: 39205MB Maxtor 6E040L0 NAR61HA0 at ata0-master UDMA133 ad1: 19092MB WDC WD200BB-00CAA0 16.06V16 at ata0-slave UDMA100 acd0: CDRW HL-DT-ST GCE-8526B/1.03 at ata1-master UDMA33 pcm0: ac97 link rate calibration timed out after 1952041 us ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad0: TIMEOUT - FAILURE [something] ad1: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad1: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad1: TIMEOUT - FAILUER [someting] [repeats two more times] acd0: TIMEOUT - READ_BIG retrying (1 retry left) [acd0 TIMEOUTs and FAILURES repeated many times] I usually don't see that pcm0 warning. Finally after lots of errors I have to power cycle it. I can boot with the USB hard drive turned off, and then turn it on and mount it normally, in which case I see: umass0: vendor 0x04b4 USB Mass Storage Device, rev 2.00/2.40, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Maxtor 6 L160P0 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) I have no trouble moving files on or off the drive after that, so it's annoying that I have to worry about it when I boot, but it's still usable. b) USB Creative Muvo TX FM hangs: BBB reset failed, TIMEOUT I have an MP3 player that has a 1 GB flash drive, and it is no longer usable on this box. Here's what it is: umass0: CREATIVE MuVo TX FM, rev 2.00/11.91, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: CREATIVE MuVo TX FM 1191 Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 993MB (2035456 512 byte sectors: 64H 32S/T 993C) When I mount the file and moves some files onto it, after a couple of files, it stops and hangs. I can't access the file system any more, and get these errors: umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, TIMEOUT umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR That continues on and I have to reboot, at which point I see scores of errors like this: g_vfs_done():da0[WRITE(offset=995237848, length=4096)]error = 5 Then I get more BBB reset failed messages, and I have to power cycle. As I said, I used to be able to use this just fine with my old mobo, and my other FreeBSD 6.1-STABLE box can handle it without trouble. Bill -- William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org Copyright (c) 1992-2006 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 6.1-STABLE #4: Sat May 6 22:18:56 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHERLOCK ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2653.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf49 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x651dSSE3,RSVD2,MON,DS_CPL,TM2,CNTX-ID,CX16,b14 AMD Features=0x2000LM AMD Features2=0x1LAHF real memory = 1576730624 (1503 MB) avail memory = 1535930368 (1464 MB) ioapic0 Version 1.1
Re: Errors after upgrading to new portupgrade
On 2 January 2006, Jack Raats wrote: /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `': failed to allocate memory (NoMemoryError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `trace' from /usr/local/sbin/portupgrade:723:in `do_upgrade' from /usr/local/sbin/portupgrade:696:in `main' from /usr/local/sbin/portupgrade:693:in `each' from /usr/local/sbin/portupgrade:693:in `main' from /usr/local/sbin/portupgrade:208:in `initialize' from /usr/local/sbin/portupgrade:208:in `new' from /usr/local/sbin/portupgrade:208:in `main' from /usr/local/sbin/portupgrade:1893 Anyone know how to cure this error? I had this too, on 6.0-STABLE (to which I upgraded from 5 on Saturday without any trouble). I recompiled all my ruby ports (which took a long time because because it kept saying the pkgdb was in the wrong format and would rebuild it every time I added or removed something, I guess because of the ruby-bdb1 and ruby-bdb4 ports going and coming), then reinstalled portupgrade, and that did it. My /var/db/ports/portupgrade/options now looks like: # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for portupgrade-2.0.0_1,1 _OPTIONS_READ=portupgrade-2.0.0_1,1 WITH_BDB4=true This is just me stumbling around without a clue, but it worked. Bill -- William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Crashing after umounting unavailable filesystems
On 10 November 2005, Michael C. Shultz wrote: Opps, I crashed the machine. When I moved it, I unplugged the USB DVD-RW and I had mounted one of the dist discs on there. When I did a umount it paniced. My bad. That happened to me the other day too. I'd mounted a USB flash drive, unplugged the USB hub, replugged it, remounted the drive, and then of course I couldn't umount the first mount. I did a umount -f and the machine crashed instantly. Is this the sort of thing that's really hard to handle, or might it be safer one day? I don't know how serious it is to do bad things to mounted file systems, but I'm curious. Bill -- William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building your own FreeBSD installation CD-ROM
On 18 January 2005, David Landgren wrote: : how does one go about creating a FreeBSD install CD-ROM? I'd like to be : able to build my own CD-ROM with as much as possible of the install : process done automatically. The latter question I can't answer, but I made my own generic install CDs for 4.8-PRERELEASE in 2003 and got some help from the list. I wrote up what I did here, in the 18 April 2003 entry: http://www.miskatonic.org/freebsd.html (Sorry, no direct link to that entry.) I don't know how different things are for 5, and what I did was basic, but perhaps it'll be of use. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Building my own release
I was having a hell of a time downloading ISO images of 4.8-RC1 or 5.0 to install on an old machine I just got--they'd freeze, no matter what mirror I used--so I thought I'd try making my own release and ISO images. I could compile everything here, burn a CD, and I'd be all set. I read release (7), and looked the examples, but I'm still not sure what to do. I used the sample cvs-supfile to download all the CVS files, but then I got stuck. The release man page says this was used to build 4.5-RELEASE: cd /usr cvs co -rRELENG_4_5_0_RELEASE src cd src make buildworld cd release make release CHROOTDIR=/local3/release BUILDNAME=4.5-RELEASE \ CVSROOT=/host/cvs/usr/home/ncvs RELEASETAG=RELENG_4_5_0_RELEASE What does that cvs in the second line do? Where they used RELENG_4_5_0_RELEASE, what would I use if I wanted to build from my system and I've cvsupped so I'm up to date? uname -a says 4.8-PRERELEASE now, of course, and I just want to take what I've got and make a CD of it. I couldn't get the cvs line to go, and when I tried the make release, whatever release I tried or guessed at, I'd get: === include creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys/conf/newvers.sh; echo $COPYRIGHT osreldate.h; echo #ifdef _KERNEL osreldate.h; echo '#error osreldate.h must not be used in the kernel, use sys/param.h' osreldate.h; echo #else osreldate.h; echo \#'undef __FreeBSD_version' osreldate.h; echo \#'define __FreeBSD_version' $RELDATE osreldate.h; echo #endif osreldate.h touch: not found *** Error code 127 [more errors and make dies] I read through the release engineering stuff at http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/ but that didn't clear it up. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
make buildworld fails on 3.5-STABLE
While making buildworld on a freshly cvsupped 3.5-STABLE box: === games/worms cc -nostdinc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/games/worms/worms.c /usr/src/games/worms/worms.c: In function `main': /usr/src/games/worms/worms.c:418: `delay' undeclared (first use this function) /usr/src/games/worms/worms.c:418: (Each undeclared identifier is reported only once /usr/src/games/worms/worms.c:418: for each function it appears in.) *** Error code 1 Stop. It's not like I really care whethers worms is there or not, but it does stop the make. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Kernel build numbers and kernel-building methods
After all the recent chat following that heads-up about how to build a world, I gave it a shot and rebuilt my system, gave the buildkernel and installkernel a KERNEL=MYCROFT setting, and adjusted /boot/loader.conf so it'd load /MYCROFT. All went well, but I noticed that the kernel build number reported by uname had changed. It said "FreeBSD 4.0-STABLE #0," while the number had been above 0 before. I rebuilt the system today and it stayed at 0, but then I recompiled the kernel alone (the old way) and now it says "FreeBSD 4.1-RC #6." Does compiling a kernel with make buildkernel not increment this number? If not, shouldn't it? Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Serial port problems with 4.0
On 19 April 2000, Brian Somers wrote: : I suspect on a real tty, this will have problems after ``opening - : carrier'' ! Does ``set cd off'' make any difference ? If it does, : that's a bug. Here's a dump of a ppp session: bash-2.03# ppp Working in interactive mode Using interface: tun0 ppp ON mrs-hudson set log local phase ppp ON mrs-hudson term Phase: bundle: Establish Phase: deflink: closed - opening Phase: deflink: Connected! deflink: Entering terminal mode on /dev/cuaa0 Type `~?' for help Phase: deflink: opening - carrier Phase: deflink: /dev/cuaa0 doesn't support CD Phase: deflink: carrier - ready atdt3418903 CONNECT 115200 Nothing happened, so I stopped it ppp ON mrs-hudson close Phase: deflink: Disconnected! Phase: deflink: Connect time: 91 secs: 0 octets in, 0 octets out Phase: total 0 bytes/sec, peak 0 bytes/sec on Wed Apr 19 21:55:55 2000 Phase: deflink: ready - closed Phase: bundle: Dead ppp ON mrs-hudson set cd off ppp ON mrs-hudson term Phase: bundle: Establish Phase: deflink: closed - opening Phase: deflink: Redial timer expired. Phase: deflink: Connected! deflink: Entering terminal mode on /dev/cuaa0 Type `~?' for help Phase: deflink: opening - carrier Phase: deflink: carrier - ready atdt3418903 CONNECT 115200 Nothing happened In ppp.log on my other machine (3.4 where it's all fine), I see lines like, "tun0: Phase: deflink: /dev/cuaa1: CD detected." So what's up with the carrier detect here, I don't know. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
