Re: Unable to mount ext2fs partition
Hi Bruce, Thanks for this info. It's way beyond my technical understanding (which is truely minimal!), but I think I get the idea. What would this look like as a series of commands? Or better yet, what's the "right" way to share data between FreeBSD -current/coming and linux in a dual boot situation? ... Which is the real objective, (not playing with e2fs! ;.-) /Paul Bruce Evans wrote: On Sun, 5 Jan 2003, Paul A. Mayer wrote: I does printf, but it doesn't initiate the e2fsck. Using the ports It prints essentially the same mount failure message as ufs. e2fsck has not shown itself to be the way to do restore order. (I get "et hav" of ata unaligned access errors and lots of other garbage.) It always worked for me until block devices were axed. Apparently it still depends on random accesses to non-block boundaries and sizes working. It's easier to boot up a Gentoo LiveCD and "do it right".) Or upgrade to FreeBSD-3 to get unaxed block devices :->. The ext2fs utilites work on regular files (better than ffs ones), so they can be used (very slowly and with muttering about axes) directly under FreeBSD by copying partitions to regular files, fixing them there, and copying them back. This is least painful for mke2fs since you can start with a sparse file instead of a copy of a partition. [Context lost to top posting] Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to mount ext2fs partition
Hi Rahul, The mount capability has to be included as a kernel option in a custom build kernel. I forget exactly what it's called (I'm writing in another OS on the system, so I can't check it right now), but I think it's something like this: option EXT2FS Have you included that in your kernel build? /Paul Rahul Siddharthan wrote: Paul A. Mayer wrote: I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. Hm, didn't know about this port.. but it still doesn't include a mount program, and I still can't mount the partition even after installing the port. I don't want to fsck it and risk screwing it up: it's a "real" linux system (ie, a dual-boot machine) and the linux continues to boot perfectly nicely. But here's what I get with an e2fsck -n : # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes Not a problem for me (it's likely to be mounted read-only anyway, and I can always boot into linux to fix it if it's dirty) - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound playback problem with Maestro3.c (?) -- clock issue
Hi Michael, Regarding your linux clock issue: There was a rather lively discussion at forums.gentoo.org about drastic clock sync loss caused by KDE. I don't know if it has been resolved in the 3.1 line, but if you were running linux KDE, you might take a look at that as a cause for the linux clock sync problem. /Paul Michael Ferguson wrote: Hi all, On a probably-unrelated side note, when I was running Linux on the same laptop (ducks), I had issues with the OS clock getting quickly out of sync with the HW clock; typically I would loose five minutes or more every hour. Although I haven't experienced the same thing with FreeBSD, I wonder if there is just something odd about interrupt handling or timing on the Inspiron 8000 line? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3 ACPI failure on locally compiled kernel
Hi folks, I was so delighted to see that the shipping (iso) version RC3 didn't crash immediately in ACPI thermal on my i845 based laptop! (I reported this after installing RC1 in December and it reoccured with RC2.) The problem comes back though if I compile a kernel myself after CVSUP'ing yesterday morning 2003-01-15 10.00 UTC. My configuration file is essentially GENERIC, make.conf is vanilla. Barring wiping out the machine with a clean install, (my installation was an upgrade), are there any suggestions about where I might look for critical differences that cause my compiles to generate faulty kernels/modules? (I've been following the procedure outlined for upgrading in /usr/src/Makefile .) Thanks, Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error Mounting /dev/acd0 on /dist: during sysinstall of 5.0-RELEASE
Hi, I have a similar problem, i.e., a clean installation process for 5.0-RELEASE produces the error: "Error Mounting /dev/acd0 on dist: Operation not supported by device (19)" (I wound up doing a minimal ftp install and then did a binary upgrade with the CD as the distribution medium.) Nate suggests: >>Does setting hw.ata.atapi_dma=1 help? How would you do this in the clean installation scenario. Is there a way to pass this setting to the kernel during the boot process, or modify the running environment by some other means before sysinstall takes over? Regards, /Paul Thomas T. Veldhouse wrote: I am trying to install from the CD-ROM, so I don't really have the option unless I do it from the boot loader. I can say that it is not set for the installed system (which I installed via FTP) and yet, I can mount a CD just fine. It is just a problem from within sysinstall. Below are the results of dmesg on my system after I installed from an FTP server. Copyright (c) 1992-2003 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 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0673000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06730a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 600024637 Hz CPU: AMD-K7(tm) Processor (600.02-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc040 real memory = 402571264 (383 MB) avail memory = 384110592 (366 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 8 entries at 0xc00f15e0 ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 5 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uscanner0: Visioneer Visioneer 6100 USB Scanner, rev 1.00/0.00, addr 2 uhci1: port 0xb000-0xb01f irq 5 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 11.0 (no driver attached) pci0: at device 11.1 (no driver attached) fxp0: port 0x8800-0x883f mem 0xd600-0xd60f,0xd680-0xd6800fff irq 5 at device 13.0 on pci0 fxp0: Ethernet address 00:03:47:97:f6:b8 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xc-0xcbfff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb
Re: Synaptics touchpad support
Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Thanks! /Paul Rahul Siddharthan wrote: Lest this disappear, like so much else, into the black hole that is GNATS, can some laptop user take a look at this? It works great for me, I can now scroll using the "up" and "down" touchpad buttons which were useless decorations earlier. Thanks to Marcin Dalecki. PR kern/48116 http://www.freebsd.org/cgi/query-pr.cgi?pr=48116 - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Hi, Terry Lambert wrote: "Paul A. Mayer" wrote: You actually lose the tap/tap-tap click and doubleclick button emulation with the new driver, and, as you note, the pressure sensitivity. Both of these issues were noted when the driver was posted for review. It semed the consensus at the time that until at least the tap/tap-tap was brought back (via software emulation), the driver would not be replaced, only optioned. You can check the list archives for details, I think. I wasn't aware of the prehistory ... (Rahul's link in another post was very interesting.) The "pressure sensitivity is, I think, really an area sensitivity and not a real pressure sensitivity (I can't imagine actually losing an axis of data!). That would mean, like the tap/tap-tap, it could be emulated in software. It would be interesting to get this back. I can (and have) lived without the "roller" buttons, but I wasn't aware of how used I had become to tapping instead of clicking. Probably the best thing to do would be to disassemble the BIOS on your box, knowing the difference between the older driver's interface, and use the same techniques that were hidden from the older driver (and "just built in" instead). This is certainly beyond my technical understanding! /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Hi, Rahul Siddharthan wrote: Paul A. Mayer said on Feb 10, 2003 at 11:01:45: Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. Yes, this was noted back then. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2003/freebsd-hackers/20030112.freebsd-hackers I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Well, without doing anything, you should be able to see some activity from the "up" button: in my case, it worked by default as a middle button, while the "down" button did nothing but showed up in xev, for example. Basically, left=1, up=2 right=3 ,down=4. What I really wanted was for "up" to mean up, "down" to mean down, and I was happy to emulate "middle" with simultaneous left-right as before. The following does it for me: I run moused with the options -m 5=4 -m 4=2 -a 0.5 (the -a is because this driver scales the speed up a bit too much for my liking). And in my XF86Config I have Option "Emulate3Buttons" Option "Buttons" "5" I *don't* have the Option "ZAxisMapping "4 5" which the howto's for wheel mice will tell you to insert -- seems it's there by default. And if I insert it, curiously, it stops working... This was very helpful and works as you describe. Thank you very much! /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
Hmmm, fails to build for me: FreeBSD asus 5.0-RELEASE-p1 FreeBSD 5.0-RELEASE-p1 #3: Mon Feb 10 10:39:34 CET 2003 root@asus:/usr/obj/usr/src/sys/ASUS i386 gmake[3]: Entering directory `/usr/ports/lang/gcc32/work/build/gcc' for d in libgcc; do \ if [ -d $d ]; then true; else /bin/sh .././..//gcc-3.2.2/gcc/mkinstalldirs $d; fi; \ done if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi gmake[3]: Leaving directory `/usr/ports/lang/gcc32/work/build/gcc' gmake[2]: Leaving directory `/usr/ports/lang/gcc32/work/build/gcc' gmake[1]: *** [configure-target-libstdc++-v3] Illegal instruction (core dumped) gmake[1]: Leaving directory `/usr/ports/lang/gcc32/work/build' gmake: *** [bootstrap] Error 2 *** Error code 2 Stop in /usr/ports/lang/gcc32. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade97111.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! lang/gcc32(missing header) Any ideas? /Paul Wesley Morgan wrote: The import of gcc 3.2.2 brings a question to mind... Many people have mentioned problems with SSE / SSE2 instructions, optimizer problems etc that are supposedly fixed with 3.2.2... My question is, should I consider rebuilding my ports with this new compiler because of stability and/or speed improvements? Or is this point release not worth the effort. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
A couple of 5.0-RELEASE bugs...
I think I may have found a few bugs in 5.0 that need to be addressed. The first problem is with GCC, which means it may not be FreeBSD-specific. I build world and kernel with the CPUTYPE flag set to "p4" in /etc/make.conf, then installed it. Everything seemed to work fine, except periodically "make" and "as" would crash: make with a signal 10 and as with a signal 11. There was no rhyme or reason to the timing. I could re-run the same compilation with no error the next time through. On a whim, I removed the CPUTYPE flag from make.conf and rebuilt/reinstalled binutils and cc. After that, everything seemed to work fine. Just to be safe, I rebuilt and installed both world and kernel without the "p4" modifier. The second problem is related to the "NOMANCOMPRESS" flag in make.conf. When installing the XFree86-4 port, I found that the "install" and "package" targets would stop with an error saying that they couldn't find gzip'd versions of the man pages. Of course that made sense when I specifically didn't want the man pages compressed! I think some of the scripts are not paying attention to that flag. If there's anything that I can do to help further investigate either of these, please let me know. -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
devastating 5.0R crash
H. I think that my 5.0R installation has self destructed. Background: * 60GB toshiba disk with two active OS partitions (win2k, freebsd) booted with ranish * Freebsd partition has 4 slices, swap (ca. 2GB), root (250MB), var (250MB), usr (ca. 6GB), other msdosfs partitions are occassionally mounted. * Kernel is 5.0 release p1, updated about 3-4 days ago (don't recall exactly but I did notice some updates to ffs.) Loads ko's for acpi, radeon, linux, sound support, and one or two other things I don't recall right now. * Hardware is Asus L3800, (i845-based p4 mobile w/ 1GB RAM). Has otherwise run great with 5.0R (there were acpi problems with RC* version, which have disappeared). The machine is new; it has about 8 weeks of running time. * Running configuration is strictly desktop. Not serving anything, not developing anything, not running a db app or similar. * After a normal shutdown in the evening, the machine rebooted normally in the morning. I logged on to my user account and start X (running gnome2). I checked mail in moz 1.2.1. I go to open phoenix and nothing happens. I was called away to look at something. When I return to my machine it's in the process of rebooting. It has hard reset itself for some reason and is stumbling through the tail end of the boot up sequence and goes into lock, clearly not able to read some thing in /etc like ttys (gives a blank shell type prompt, where I have my console set to secure.) Status: I'm presently running fsck_ffs from a live cd. It fsck'ed / with some complaints about an unreadable sector. It's now on /var and reporting vast, vast numbers of sectors as unreadable, with "UNEXPECTED SOFT UPDATE INCONSISTENCY". I've not visited /usr yet. I hope my disk (with less than 800 hours of service) hasn't been somehow physically borked. (The windows partition boots and runs seemingly fine.) Any ideas? Any guesses about what caused a hard reset (loading phoenix)? How to gaurd against this in the future? (Besides don't run 5.0R! ;-) ... I'm just hoping to be able to get /usr/home/(user) off, I'm assume the installation is utterly trashed.) /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: devastating 5.0R crash
There were some ATA complaints, (don't recall exactly what though it was clear that there were read errors), when attempting to boot the system off the HD. I don't recall "medium error" there, and have not seen it in fsck_ffs booted from the live cd. The sector numbers I'm seeing seem to be in short sequences or in proximity, but spread in various groups with in the partitions. The /var fsck has resulted in clearing to the last phase pass, where it repeatedly asks for fsck to be rerun. I'm on /usr now. /Paul David Schultz wrote: Thus spake Paul A. Mayer <[EMAIL PROTECTED]>: I'm presently running fsck_ffs from a live cd. It fsck'ed / with some complaints about an unreadable sector. It's now on /var and reporting vast, vast numbers of sectors as unreadable, with "UNEXPECTED SOFT UPDATE INCONSISTENCY". I've not visited /usr yet. I hope my disk (with less than 800 hours of service) hasn't been somehow physically borked. (The windows partition boots and runs seemingly fine.) If many (say, more than a track's worth) of sectors are unreadable (e.g. you get a ``medium error''), your hard disk is probably failing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mod_ssl & current
I'm having a problem getting Apache setup to work with modssl; I'm running apache1.3.12+php4+mod_ssl2.6.0 [root@valiant]-~# apachectl startssl /usr/local/sbin/apachectl startssl: httpd could not be started No other info whatsoever. (helpful, huh? :-) I'm using the stock configuration file with just hostname changes throughout. Any ideas? I'm running current from 2/26/2000. -- Cheers, Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mod_ssl & current
On Tue, Feb 29, 2000 at 07:26:53PM -0800, Manfred Antar wrote: > I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in > /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile > and install the recompiled libssl.so in /usr/local/libexec/apache. > Works fine > Note this is for the apache13-php3 port but I bet it will work for the apache13-php4 >port > Manfred Thanks! It works :-) -- Cheers, Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Shared IRQs
I have a FreeBSD 4.0-CURRENT (cvsup'ed as of tonight) machine. It has a USB controller (PIIX3) and an ethernet controller sharing irq 10. I'm not much in the way of a hardware expert, so I'm wondering if this is safe or if I should reroute the ethernet card or the usb to another irq. In case it matters (don't think it would), this machine is an IBM PC Server 325 with an Intel 440FX motherboard. -- Cheers, Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SB AWE64 in -CURRENT
Ok, I'm giving serious thought to ditching the Debian installation on this drive and go with FreeBSD. I run FreeBSD on this machine already, but on a smaller drive. Debian and Linux have been routinely irritating me. I'm used to the traditional set of Unix tools, and the traditional command line options. Linux utils are close, but most seem to have weird little quirks to them to their traditional counterparts. I run 4-CURRENT on my network server here also. Does 4-CURRENT have drivers for the SB64 AWE synth? I have the regular PCM stuff going pretty well already... Sorry to ask here, but the LINT file isn't much help and the sound driver documentation is slightly out of date. -- Cheers, Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 Fails with signal 11 in FreeBSD 4.6 and 4.7
XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and 4.7. It is not possible to run the graphical configuration utility at all. After running curses configuration utility, running startx produces signal 11. No other debugging information is available. No other messages from the server. Note that X runs fine on FreeBSD 4.5 and earlier, using the exact same machine and configuration. When XFree86 moved to a combined server (beginning in FreeBSD 4.6), something broke. Earlier versions (on FreeBSD 4.5 and earlier) using individual X server modules worked fine. Can anyone help me debug and resolve this problem? I've tried everything I can think of to no avail. Thanks, Paul A. Scott mailto:pscott@;skycoast.us http://skycoast.us/pscott/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Linux Netscape
Under my 5.0-C setup here, the Linux netscape takes AGES to load (>5min) and is so unresponsive, I have to kill it. I experienced a similar problem with StarOffice 5.2, where performance was just dog slow. Is the Linuxulator broken? -- Cheers, Sean Sean-Paul Rees ([EMAIL PROTECTED]) Web: http://www.seanrees.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Question about KLDs...
All, This may be a fairly elementary question, but I have not seen this addressed in the Handbook at all -- Which is the preferred method for using drivers: KLDs or compiling into the kernel? Are there some that work better one way than the other? Inquiring minds would like to know! :-) Thanks! -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cc: Internal error: Illegal instruction (program as)
All, I am receiving some strange errors during a buildworld of 5.0-RELEASE-p2 from 5.0-RELEASE-p1. The location of where the failure varies, but the program that causes the failure is the same every time: "as". The errors are a variety of signal 10 and signal 4. I do find an "as.core" file under /usr/obj, but as is stripped, so there are no debugging symbols or listing that I can provide. The strange thing is that I have been able to successfully build XFree86, KDE, and many other ports on this system. I followed the 4.x-to-5.0 upgrade directions to the letter about a month ago, and have had no major problems before this. Any help would be greatly appreciated! -- Paul A. Howes Hardware Tyan S2099GNNR motherboard Intel P4-2.4/533 Crucial 512 MB PC2100 DIMM Maxtor 20 GB hard drive. dmesg Copyright (c) 1992-2003 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 5.0-RELEASE-p1 #2: Thu Feb 13 08:39:59 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src-5.0/sys/HYDROGEN Preloaded elf kernel "/boot/kernel/kernel" at 0xc047. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04700a8. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04700f8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2430010060 Hz CPU: Pentium 4 (2430.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 536805376 (511 MB) avail memory = 516771840 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc03b34a2 (122) VESA: ATI MACH64 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Using $PIR table, 11 entries at 0xc00fdeb0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 o n pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 uhci0: port 0xd800-0xd81f irq 12 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 5 at d evice 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: at device 1.0 (no driver attached) ahc0: port 0xc400-0xc4ff mem 0xe6042000-0xe604 2fff irq 11 at device 4.0 on pci2 aic7880: Ultra Single Channel A, SCSI Id=6, 16/253 SCBs pci2: at device 8.0 (no driver attached) em0: port 0xcc00-0xcc3f mem 0xe602-0xe603,0xe600-0xe601 irq 12 at device 10.0 on pci2 em0: Speed:100 Mbps Duplex:Full isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0 x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 31.3 (no driver attached) speaker0 port 0x61 on acpi0 fdc0: port 0x3f7,0x3f0-0 x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xd1000-0xd27ff,0xd-0xd07ff,0xc8000-0xc,0xc -0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to den y, logging disabled acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad0: 19541MB [39703/16/63] at ata0-master UDMA66 ad1: 38172MB [77557/16/63] at ata0-slave UDMA100 acd0: CDROM at ata1-slave PIO3 Waiting 2 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) Mounting root from ufs:/dev/ad0s1a fxp0: p
RE: cc: Internal error: Illegal instruction (program as)
All; These two kernel options seem to have solved the problem. Builds now run smoothly and error-free. I read the comments in NOTES about these options and something clicked: I recall that most Pentium processors will only deal with 4 kB pages. Aren't 4 MB pages a feature of the Xeon processor, as it can address much more memory? If that is the case, then these options should be the default, and their inverse provided in the kernel configuration file (ENABLE_PSE & ENABLE_PG_G). -- Paul A. Howes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hay Sent: Saturday, February 22, 2003 1:05 PM To: Paul A. Howes Cc: [EMAIL PROTECTED] Subject: Re: cc: Internal error: Illegal instruction (program as) On Sat, Feb 22, 2003 at 11:43:01AM -0500, Paul A. Howes wrote: > All, > > I am receiving some strange errors during a buildworld of 5.0-RELEASE-p2 > from 5.0-RELEASE-p1. The location of where the failure varies, but the > program that causes the failure is the same every time: "as". > > The errors are a variety of signal 10 and signal 4. I do find an > "as.core" file under /usr/obj, but as is stripped, so there are no > debugging symbols or listing that I can provide. > > The strange thing is that I have been able to successfully build > XFree86, KDE, and many other ports on this system. I followed the > 4.x-to-5.0 upgrade directions to the letter about a month ago, and have > had no major problems before this. > > Any help would be greatly appreciated! > > -- > Paul A. Howes > > > > > Hardware > > Tyan S2099GNNR motherboard > Intel P4-2.4/533 > Crucial 512 MB PC2100 DIMM > Maxtor 20 GB hard drive. > > I see it is a P4, try adding options DISABLE_PSE and DISABLE_PG_G to your kernel. My 1.8G P4 do the same without them. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cc: Internal error: Illegal instruction (program as)
Jiawei, I always remove the contents of /usr/obj prior to performing a buildworld, and I could reproduce this behavior every time. -- Paul A. Howes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of leafy Sent: Monday, February 24, 2003 7:08 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: cc: Internal error: Illegal instruction (program as) On Mon, Feb 24, 2003 at 12:10:46PM +0100, Soeren Schmidt wrote: > > inverse provided in the kernel configuration file (ENABLE_PSE & > > ENABLE_PG_G). > > Just for the record but my [EMAIL PROTECTED]/533 512MB/DDR does *not* show this > problem no matter how hard I beat it. > > -S?en Try this: DON'T remove /usr/obj before doing a buildworld, just let it accumulate. It will show up someday (it's not deterministic). Even sh(1) can die during the build along with make(1) and as and gcc. My P4 never showed such behaviour if I properly remove /usr/obj before a build. Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cc: Internal error: Illegal instruction (program as)
Soren, I have a machine that uses a SiS 648, but it has other problems... I'm one of the unlucky individuals who bought the ASUS implementation of this board, and ended up with a flaky P.O.S. I'm seriously thinking of swapping it for a Tyan S2662 (Granite Bay) motherboard, or waiting a few months for the 800 MHz FSB boards and chips to come out. My wife does a great deal of photo restoration, and the faster FSB would be a major improvement over the ASUS board. I haven't bothered to test any of my systems in an over clocked state, as the stability is more important to me, and my work, than wringing out the last MHz of performance. :) -- Paul A. Howes -Original Message- From: Soeren Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 7:15 AM To: [EMAIL PROTECTED] Subject: Re: cc: Internal error: Illegal instruction (program as) Could very well be that, this is a SiS 648 system with DDR333 RAM.. I can provoke something that looks like this problem if I overclock it severely ie run it a ~3Ghz with 233Mhz mem clock... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: buildworld dies with Signal 4
Paulius, I had the exact same problem less than a week ago. The solution was the edit my kernel build configuration file and add the following two lines: options DISABLE_PSE options DISABLE_PG_G This changes the VM subsystem so that it uses 4 kB pages instead of the default 4 MB pages. There is a bug in some hardware that only shows up under heavy CPU & memory loading, such as a buildworld incurs. Someone had told me that there is a 10% - 15% performance penalty from doing this, but I don't run the system hard enough to be able to notice. -- Paul A. Howes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paulius Bulotas Sent: Tuesday, February 25, 2003 11:21 AM To: [EMAIL PROTECTED] Subject: Re: buildworld dies with Signal 4 On 03 02 25, Steve Kargl wrote: > On Tue, Feb 25, 2003 at 05:12:52PM +0200, Paulius Bulotas wrote: > > and I'm trying to make buildworld today, but it crashes in various > > places with Signal 4. > Do you have CPUTYPE=p4? How much memory > is in the computer? You are right, it's CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1799.81-MHz 686-class CPU) real memory = 527695872 (503 MB) on Intel 845G motherboard and in make.conf I have CPUTYPE and other compile time options commented out (because some time ago I was unable to build mozilla) sometimes I get Signal 10... Paulius To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMBus support...
All, My motherboard has SMBus support: [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x24c28086 chip=0x24c38086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB (ICH4) SMBus Controller' class= serial bus subclass = SMBus ...but there is no driver. I didn't see a module in /boot/kernel that looked likely, and there isn't a driver listed in /usr/src/sys/i386/conf/NOTES for it. Is there a way to enable SMBus support on 5.0-RELEASE? Thanks! -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMBus support...
Sergey, Thanks! Where is this documented? -- Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergey A. Osokin Sent: Wednesday, February 26, 2003 7:10 AM To: Paul A. Howes Cc: [EMAIL PROTECTED] Subject: Re: SMBus support... Try to use device ichsmb, maybe its helps you. -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Belkin USB 2.0 Cardbus card
Has anyone got one of these cards working? I plug it into my laptop with 5.1, cvsupped on Monday or Tuesday (long week), and try to plug this card in. It is recognized the card, but has errors and disables them. I also am trying a Sony DRX-500UL drive. It's recognized in the built-in USB 1.1 ports, and I'm able to mount a CD. Any chance burning on it could happen? CD VCD and DVD +/- RW. Thanks, Paul. -- Paul T. RootCCSA, CCSE, CCNA Qwest CommunicationsPAG: +1 (877) 693-7155 600 Stinson Blvd, Flr 1SWRK: +1 (612) 664-3385 Minneapolis, MN 55413 FAX: +1 (612) 664-4778 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
looking for warn quota tools
Hi, I am looking for a tool that will email to the user if his/her account (more specifically email box) is approaching quota limit. I've searched everywhere for such a tool but to no avail. On Linux, there is a tool called "warnquota" that fits my need but I am running FreeBSD 4.5 -RELEASE so I can't utilize that tool. Also, from searching on google, I've found a tool called "psntools" that has the warnquota feature but it doesn't work on a filesystem that has a mailspool. Can someone help me? Thanks, Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: looking for warn quota tools
Thank for the quick response, Robert.
I fail to mention that this machine is strictly a mail server with over
10K+ accounts. Users cannot log into their shell account and they check
email via POP/IMAP only.
At 05:31 PM 6/11/2002 -0400, Robert Watson wrote:
>I always just used the following script in the /etc/csh.login:
>
>#if ("`quota | grep '\*'`" != "") then
># echo Warning: Quota Exceeded:
># quota
>#endif
>
>Given that the output of the quota command is fairly parseable, a little
>bit of scripting or perl should do the trick.
>
>Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
>[EMAIL PROTECTED] Network Associates Laboratories
>
>On Tue, 11 Jun 2002, Paul S. Puth wrote:
>
> > Hi,
> >
> > I am looking for a tool that will email to the user if his/her account
> > (more specifically email box) is approaching quota limit. I've searched
> > everywhere for such a tool but to no avail.
> >
> > On Linux, there is a tool called "warnquota" that fits my need but I am
> > running FreeBSD 4.5 -RELEASE so I can't utilize that tool. Also, from
> > searching on google, I've found a tool called "psntools" that has the
> > warnquota feature but it doesn't work on a filesystem that has a mailspool.
> >
> > Can someone help me?
> >
> > Thanks,
> >
> > Paul
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ATAPI CD errors
I switched to the 'new' atapi driver and I am having trouble with my cdrom
which worked fine using the old wd driver.
I have the following in my config file :
controller ata0
device atadisk0
device atapicd0
The device exists:
$ ls -l /dev/acd0*
brw-r- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a
brw-r- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c
Booting gives the following :
ad0: ATA-3 disk at ata0 as master
ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, UDMA33
Creating DISK ad0
Creating DISK wd0
atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00
acd0: CDROM drive at ata0 as slave
acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33
acd0: supported read types: CD-DA
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
But when I try to mount the CD I get the following error :
atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00
atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00
Anybody any idea or hint ??
TIA
Paul
--
Paul van der Zwan paulz @ trantor.xs4all.nl
"I think I'll move to theory, everything works in theory..."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
In message <[EMAIL PROTECTED]>, Paul van der Zwan wrote: > >I switched to the 'new' atapi driver and I am having trouble with my cdrom >which worked fine using the old wd driver. > >I have the following in my config file : > >controller ata0 >device atadisk0 >device atapicd0 > >The device exists: >$ ls -l /dev/acd0* >brw-r- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a >brw-r- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c > >Booting gives the following : >ad0: ATA-3 disk at ata0 as master >ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S >ad0: 16 secs/int, 0 depth queue, UDMA33 >Creating DISK ad0 >Creating DISK wd0 >atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 >acd0: CDROM drive at ata0 as slave >acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 >acd0: supported read types: CD-DA >acd0: Audio: play, 255 volume levels >acd0: Mechanism: ejectable tray >acd0: Medium: no/blank disc inside, unlocked > >But when I try to mount the CD I get the following error : >atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 >atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 > >Anybody any idea or hint ?? I hate to followup on my own messages , but I made a 'small' error. The message above was cause by an empty drive ( wrong PC ;-() The real message I get is : $ sudo mount /cdrom cd9660: Operation not permitted And dmesg gives the following: atapi: PREVENT_ALLOW - UNIT ATTENTION skey=6 asc=28 ascq=00 error=08 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 BTW this is on a -current cvsupped and built last night. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
In message <[EMAIL PROTECTED]>, Brian Fun dakowski Feldman wrote: >Have you either tried disabling DMA on the drive? This is easily achieved >by the following (whitespace mangled): > >--- atapi-all.c 1999/10/10 18:08:38 1.19 >+++ atapi-all.c 1999/10/23 16:51:12 >@@ -135,7 +135,8 @@ > udmamode(atp->atapi_parm), > atp->atapi_parm->dmaflag); >- if (!(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && >+ if (atp->atapi_parm->device_type != ATAPI_TYPE_CDROM && >+ !(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && >!ata_dmainit(atp->controller, atp->unit, > (apiomode(atp->atapi_parm) < 0) ? > (atp->atapi_parm->dmaflag ? 4 : 0) : > This patch allows me to mount the cdrom... The probes show PIO mode i.s.o. DMA. So it looks like DMA is broken for this drive.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Par. gone missing
I just notice my par. port is no longer detected. A kernel built on Jan 21st
fails to detect my par. port which has worked fine so far.
In /var/log/messages I get the following:
Jan 27 22:29:53 trantor /kernel: ppc0: parallel port found at 0x3bc
Jan 27 22:29:53 trantor /kernel: ppc0: cannot reserve I/O port range
When doing a boot -v.
An older kernel booted Jan 13th showed the following :
Jan 13 21:08:47 trantor /kernel: ppc0 at port 0x3bc-0x3c3 irq 7 on isa0
Jan 13 21:08:47 trantor /kernel: isa_compat: didn't get ports for ppc
Jan 13 21:08:47 trantor /kernel: ppc0: Generic chipset (NIBBLE-only) in
COMPATIBLE mode
Jan 13 21:08:47 trantor /kernel: lpt0: on ppbus 0
Jan 13 21:08:47 trantor /kernel: lpt0: Interrupt-driven port
Rebooting the older kernel brings back my port so I doubt it's a hardware
problem. Any hints on tracing the reason for it not being detected ??
Paul
--
Paul van der Zwan paulz @ trantor.xs4all.nl
"I think I'll move to theory, everything works in theory..."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Parallel port gone missing (extra info)
In message <[EMAIL PROTECTED]>, Paul van der Zwan wrote: > >I just notice my par. port is no longer detected. A kernel built on Jan 21st >fails to detect my par. port which has worked fine so far. >In /var/log/messages I get the following: > >Jan 27 22:29:53 trantor /kernel: ppc0: parallel port found at 0x3bc >Jan 27 22:29:53 trantor /kernel: ppc0: cannot reserve I/O port range > >When doing a boot -v. >An older kernel booted Jan 13th showed the following : >Jan 13 21:08:47 trantor /kernel: ppc0 at port 0x3bc-0x3c3 irq 7 on isa0 >Jan 13 21:08:47 trantor /kernel: isa_compat: didn't get ports for ppc >Jan 13 21:08:47 trantor /kernel: ppc0: Generic chipset (NIBBLE-only) in >COMPATIBLE mode >Jan 13 21:08:47 trantor /kernel: lpt0: on ppbus0 >Jan 13 21:08:47 trantor /kernel: lpt0: Interrupt-driven port > >Rebooting the older kernel brings back my port so I doubt it's a hardware >problem. Any hints on tracing the reason for it not being detected ?? > Some extra info , the MB is a Chaintech 5TDM2, changing biossettings from EPP to ECP/EPP does not help. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Parallel port back
My parallel port is back. Switching the it from 3BC to 378 made the probe
recognize it again.
Apparently the new code doesn't like the 3BC address as much as the old code..
Paul
--
Paul van der Zwan paulz @ trantor.xs4all.nl
"I think I'll move to theory, everything works in theory..."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Slow seq. write on Seagate ST36530N
I am having some performance problems on my -current ( update last weekend) I hooked up a new Seagate ST36530N yesterday ( connected to an Adaptec 2940U) and sequential write is very slow. Compared to an IBM DORS-32160 connected to the same controller ( even the same cable) it is half as fast. Iozone auto shows the following : Seagate IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) By Bill Norcott Operating System: FreeBSD 2.x -- using fsync() IOZONE: auto-test mode MB reclen bytes/sec written bytes/sec read 1 512 5835553 22369621 1 10243627506 33554432 1 20483441480 44739242 1 40964329604 44739242 1 81923121342 67108864 2 512 3627506 22369621 2 10244260880 44739242 2 20483273603 38347922 2 40964067203 67108864 2 81924067203 67108864 4 512 4161790 21474836 4 10242354696 35791394 4 20482418337 38347922 4 40962418337 59652323 4 81921988410 53687091 8 512 2863311 20259279 8 10241565221 37025580 8 20481470879 31580641 8 40961514445 48806446 8 81921337162 56512727 16 512 2041334 14412641 16 10241536111 27531841 16 20481476948 43826196 16 40961410961 48806446 16 81921432610 52377649 IBM MB reclen bytes/sec written bytes/sec read 1 512 3728270 22369621 1 10244067203 26843545 1 20483947580 67108864 1 40963728270 44739242 1 81923834792 67108864 2 512 4549753 13421772 2 10244194304 44739242 2 20483890368 53687091 2 40964400581 67108864 2 81923677198 67108864 4 512 4129776 21474836 4 10243532045 44739242 4 20482451465 53687091 4 40963016128 59652323 4 81922870967 53687091 8 512 2396745 21053761 8 10242894182 37025580 8 20482587329 42949672 8 40962526451 51130563 8 81922520520 56512727 16 512 3067833 20069940 16 10242701237 34087042 16 20483591109 43826196 16 40962306641 42949672 16 81923121342 52377649 Bonnie shows the following: Seagate ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 3251 44.0 1307 4.0 2285 11.5 5006 69.0 8644 23.0 115.1 4.2 IBM 100 45.0 2533 8.8 1878 10.1 4244 58.2 5140 19.7 76.4 3.3 If I interpret it correctly the Seagate is faster in everything but sequential writes. dmesg shows the following : da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Anybody an idea ?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'
Re: Slow seq. write on Seagate ST36530N
> Paul van der Zwan wrote... > > > > I am having some performance problems on my -current ( update last weekend) > > I hooked up a new Seagate ST36530N yesterday ( connected to an Adaptec > > 2940U) > Andreas Klemm has had similar trouble, as he pointed out. > Can you check and see whether or not you have write caching turned on for > your disk? I have seen problems with sequential writes that appear to be > caused by conflicts between FreeBSD's caching policy and disk caching > policies. These problems often go away when you disable write caching on a > disk. > > The Write Cache Enable (WCE) bit is in mode page 8. To check it: > > camcontrol modepage -n da -u 1 -v -m 8 > > To edit the mode page: > > camcontrol modepage -n da -u 1 -v -m 8 -e > > Let me know whether that affects the problem at all. This did not improve anything , but I think I have found the couse. In that modepage there is a DISC value which was 0 on the IBM and 1 on the Seagate. I remembered a ' Enable disconnect' option in the Adaptec 2940 bios, setting this to 'off' for both harddisks led to a huge performance increase on the Seagate. If I also enable Ultra mode iozone write goes from 1.5 MB/s to 12 MB/s ( a factor of 8 !!!). Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Slow seq. write on Seagate ST36530N
> > > > This did not improve anything , but I think I have found the couse. > > In that modepage there is a DISC value which was 0 on the IBM and 1 on the > > Seagate. I remembered a ' Enable disconnect' option in the Adaptec 2940 > > bios, > > setting this to 'off' for both harddisks led to a huge performance increase > > on > > the Seagate. If I also enable Ultra mode iozone write goes from 1.5 MB/s > > to 12 MB/s ( a factor of 8 !!!). > > The 'DISC' bit in mode page 8 has nothing to do with disconnection. Here's > the description of it from the SCSI-3 spec: > > > The discontinuity (DISC) bit, when one, requests that the device server > continue the pre-fetch across time discontinuities, such as across > cylinders (or tracks in an embedded servo device), up to the limits of the > buffer, or segment, space available for the pre-fetch. When zero, the DISC > requests that pre-fetches be truncated (or wrapped) at time discontinuities. > I did not change it but it triggered me to have a look at the Adaptec BIOS settings. I have done some testing and reenabled disconnection, preformance dropped to less than 2MB/s writing. After searching the freebsd-scsi archives I found out it might be related to tagging, so I edited /usr/src/sys/cam/cam_xpt.c and added an entry to disallow tagging for this drive. Back to 12 MB/s. So it looks like there is at least an acceptable ( to me ) workaround. Maybe the CAM maintainer can put an entry in cam_xpt.c for this drive ??? dmgs shows is as : da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15) da1: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
CPP broken on egcs current
A make buildworld fails on an freshly rebuilt system. The following error is shown: -- >>> Rebuilding /usr/include -- cd /usr/source/src; SHARED=copies PATH=/usr/obj/usr/source/src/tmp/sbin:/usr/obj /usr/source/src/tmp/usr/sbin:/usr/obj/usr/source/src/tmp/bin:/usr/obj/usr/source /src/tmp/usr/bin:/home/paulz/bin:/home/paulz/bin/trantor.xs4all.nl:/usr/local/bi n:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/games:/sbin:/bin:/usr/l ocal/jdk1.1.7/bin:/usr/local/pilot/bin:/usr/local/pgsql/bin BISON_SIMPLE=/usr/ob j/usr/source/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/sou rce/src/tmp/usr/libexec:/usr/obj/usr/source/src/tmp/usr/bin GCC_EXEC_PREFIX=/us r/obj/usr/source/src/tmp/usr/lib:/usr/obj/usr/source/src/tmp/usr/lib/ LD_LIBRAR Y_PATH=/usr/obj/usr/source/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/source/src /tmp/usr/lib:/usr/obj/usr/source/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH =/usr/obj/usr/source/src/tmp/usr/libexec:/usr/libexec /usr/obj/usr/source/src/tm p/usr/bin/make DESTDIR=/usr/obj/usr/source/src/tmp -f Makefile.inc1 includes cd /usr/source/src/include; /usr/obj/usr/source/src/tmp/usr/ bin/make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/source/src/include/../sys/sys/param.h; . /usr/source/src/ include/../sys/conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h ;echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __FreeBSD_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/source/src/include/rpcsvc/key_prot.x -o key_prot.h /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Int ernal compiler error in function main *** Error code 33 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I get the same internal error when xrdb tries to run my .Xresources file thru CPP so does xdm trying the run Xresources thru cpp.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
cpp breakage on egcs -current
I just found that just calling /usr/libexec/cpp -traditional causes it to abort with the following error: /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main This breaks rpcgen thus breaking make buildworld in my box . In addition xdm and xdrb also suffer .. This is on a system on which I ran a succesfull make world last night. The kernel is also built using egcs. This is the only problem I have found so far. The CFLAGS for make world were -O2 -pipe, for the kernel -O -pipe. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: CPP broken on egcs current
> In article <199904051112.naa22...@trantor.xs4all.nl>, > Paul van der Zwan wrote: > > > > A make buildworld fails on an freshly rebuilt system. > > The following error is shown: > ... > > /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: > > Int > > ernal compiler error in function main > > *** Error code 33 > > Your installed cpp was built from slightly old sources. Make sure > your source tree is up-to-date. Then manually "make cleandir; > make cleandir; make obj; make depend; make all install" in > "src/gnu/usr.bin/cc". It will be OK after that. > That seems to fix it.. Thanks. BTW why the double make cleandir ?? a typo ? or is there some magic. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
sio.c breaks kernel ( even GENERIC)
I haven't been able to get a kernel built because of some undefined references in sio.o. Even GENERIC is broken. (cvsupped just a few minutes ago ) loading kernel sio.o: In function `siocnprobe': sio.o(.text+0x286e): undefined reference to `gdbdev' sio.o(.text+0x2874): undefined reference to `gdb_getc' sio.o(.text+0x287e): undefined reference to `gdb_putc' sio.o(.text+0x2895): undefined reference to `gdbdev' sio.o(.text+0x28c9): undefined reference to `gdbdev' sio.o(.text+0x28cf): undefined reference to `gdb_getc' sio.o(.text+0x28d9): undefined reference to `gdb_putc' *** Error code 1 Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Multiple NFS server problems with Solaris 8 clients
In message <[EMAIL PROTECTED]>, Thomas Quinot wrote: >Le 2001-10-14, Paul van der Zwan écrivait : > >> I am using -current box as a homedir server for my Solaris clients and >> have noticed a wierd problem. > >Other problems here, with Solaris 2.[68] as clients, and -CURRENT of >yesterday as server. ls works, but ls -l issues a 'NFS getacl failed' >message *and* waits for a timeout once for each file in the directory. > >The server is not multi-homed, and a packet capture shows no trace of >address mismatch problems. One interesting thing is that the client >first does GETATTR on the file (and apparently gets a reply), and >then sends some other RPC, to which the server never replies. >Could this be the getacl request mentioned in the client error message? >I see no mention of getacl whatsoever in the -CURRENT server code. If >no such function is implemented, shouldn't we reject the request? > >A packet capture is available at > http://www.infres.enst.fr/~quinot/nfs.cap > >Client is 137.194.192.1, server is 137.194.162.11. The test consists >in first performing an 'ls' on one file, then an 'ls -l' on the same >file. Result: > >ls photos-ta; ls -l photos-ta >photos-ta >NFS getacl failed for server shalmaneser.enst.fr: error 5 (RPC: Timed >out) >-rw--- 1 quinot astre474 Oct 18 14:17 photos-ta I have looked at a trace I made using snoop and it shows an NFS_ACL call which is not supported by FreeBSD. It should have sent a reply that it does not know the NFS_ACL protocol but apparently it does not. The only return traffic I see is an empty packet with the tcp ACK. It looks like an implementation error in the -current NFS server. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Multiple NFS server problems with Solaris 8 clients
In message <[EMAIL PROTECTED]>, BSD User wrote: >Actually, upon instrumenting some code, it looks like RELEASE-4.4 gets it >mostly right. It ejects a PROG_UNAVAIL call which causes the Solaris 8 >client to back off. The correct message would seem to be PROC_UNAVAIL, >but I would take PROG_UNAVAIL if I could get -current to eject it. In this case ( the NFS_ACL one) it seems PROG_UNAVAIL is the right thing. It has a different program number from NFS and it is not just a not implemented procedure that is part of NFS. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
df -l broken
I noticed the -l option of the df command is broken. It is supposed to print df for local filesystems but on my system it prints nothing at all. I had a quick look at the code , as far as I can tell it uses sysctl to figure out the mounted filesystems but thinks all of them are non-local and ignores them. Using sysctl -a I could not find any entries which looked vaguely like describing a mount.. Paul -- I have discovered the art of deceiving diplomats. I tell them the truth and they never believe me. -- Camillo Di Cavour To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: df -l broken
> Paul van der Zwan wrote: > > > > I noticed the -l option of the df command is broken. It is supposed to > > print df for local filesystems but on my system it prints nothing at all. > > I had a quick look at the code , as far as I can tell it uses sysctl to > > figure out the mounted filesystems but thinks all of them are non-local and > > ignores them. > > Using sysctl -a I could not find any entries which looked vaguely like > > describing a mount.. > > > > Paul > > Could you please test the attached patch ? I did it in a hurry but it > may fix the problem. > It looks ok to me, just the local mounts show up.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
nfsclient and amd
It looks like using amd to mount remote hosts on /net will not cause the nfsclient.ko module to be loaded. This causes the mounts to fail. Maybe rc.network kan be changed to kldload the nfsclient.ko module if it is not built into the kernel, just like it does for the server module ?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Multiple NFS server problems with Solaris 8 clients
I am using -current box as a homedir server for my Solaris clients and have noticed a wierd problem. When I login my homedir gets mounted ok but when I type ls -l it just waits until I ^C it. If I run snoop on Solaris I see a getattr request being sent and an answer being received but apparently it gets ignored by Solaris. This happens on both Sol x86 and Sparc ( both with MU5 installed) Another problem I see is that rebooting the client causes the server to ignore request afterwards. I see SYNS sent to the server but no respons at all... One more problem is in nfsd, if I set it to use udp only it starts eating all cpu cycles it can get,but only the master process. Trussing the proces shows no system calls whatsoever being performed. BTW This is -current built yesterday ( oct 13). Paul PS Snoop logs or tcpdump logs are avialable for those who know what to look for... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usdb missing detaches ???
I'm experimenting with my Sony DSC S70 and USB. I can get -current to mount the stick in the camera but it won't umount the filesystem on detach. When I run usbd with -d -v it looks like usbd not even receives the detach event. It give the following output: usbd: opened /dev/usb0 usbd: opened /dev/usb1 usbd: opened /dev/usb2 usbd: reading configuration file /etc/usbd.conf usbd: opened /dev/usb usbd: device-attach event at 1012737567.535227000, Sony DSC, Sony: vndr=0x054c prdct=0x0010 rlse=0x0210 clss=0x subclss=0x prtcl=0x device names: umass0 usbd: Found action 'Sony DSC S70 Camera' for Sony DSC, Sony at umass0 usbd: Executing 'sleep 5 ;mount /sony' usbd: device-attach event at 1012737599.54987, Sony DSC, Sony: vndr=0x054c prdct=0x0010 rlse=0x0210 clss=0x subclss=0x prtcl=0x device names: umass0 usbd: Found action 'Sony DSC S70 Camera' for Sony DSC, Sony at umass0 usbd: Executing 'sleep 5 ;mount /sony' msdosfs: /dev/da0s1: Device busy usbd: 'sleep 5 ;mount /sony' returned 71 The second attach happend when I switched the camera off and on again. Syslog shows the following: Feb 3 12:59:27 trantor kernel: umass0: Sony Sony DSC, rev 1.00/2.10, addr 2 Feb 3 12:59:27 trantor kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Feb 3 12:59:27 trantor kernel: da0: Removable Direct Access SCSI-0 device Feb 3 12:59:27 trantor kernel: da0: 150KB/s transfers Feb 3 12:59:27 trantor kernel: da0: 61MB (126848 512 byte sectors: 0H 0S/T 0C) Feb 3 12:59:42 trantor kernel: umass0: at uhub2 port 2 (addr 2) disconnected Feb 3 12:59:42 trantor kernel: (da0:umass-sim0:0:0:0): lost device Feb 3 12:59:42 trantor kernel: umass0: detached Feb 3 12:59:59 trantor kernel: umass0: Sony Sony DSC, rev 1.00/2.10, addr 2 So it looks like the kernel sees the detach but usbd does not. /etc/usbd.conf has the following entry for the camera: device "Sony DSC S70 Camera" vendor 0x054c product 0x0010 attach "sleep 5 ;mount /sony" detach "umount -f /sony" BTW This is on -current compiled and installed yesterday. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB detach crashes possibly fixed
> On 14-Feb-2002 (08:29:50/GMT) Brian Fundakowski Feldman wrote:
>
> > Please try this change (already committed to -CURRENT) and let me
> > know if crashes due to detaching USB devices specifically have been
> > eliminated.
>
> I cvsupped on Feb 14, 20:21 CET (GMT+1, Italian time), recompiled
> both world & kernel (yes, runned mergemaster also :-) and messages
> show that device attach and detach (before I got only attach)
>
> ...kernel: uscanner0: EPSON Perfection1240, rev 1.00/1.14, addr 2
>
> ...kernel: uscanner0: at uhub0 port 1 (addr 2) disconnected
> ...kernel: uscanner0: detached
>
> _BUT_
>
> I lost /dev/speaker. I don't know if this is related to patch but
> with my previous installed build (a bit old, of December 11, 2001)
> I have those lines on /etc/usbd.conf:
>
> attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker"
> detach "echo L16eec > /dev/speaker"
>
> and I got a small tune on attach but nothing on detach.
> Now I am unable to play notes on /dev/speaker. Any hint?
>
I have no crashes but the detach action is never executed when I switch off
my Sony camera ( it has never worked as far as I know)
Attach actions are executed fine..
Paul
--
Paul van der Zwan paulz @ trantor.xs4all.nl
"I think I'll move to theory, everything works in theory..."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: USB detach crashes possibly fixed
Fcc: outbox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii > > > > > > and I got a small tune on attach but nothing on detach. > > > Now I am unable to play notes on /dev/speaker. Any hint? > > As Terry notes, shouldn't possibly be related. > > > I have no crashes but the detach action is never executed when I switch off > > my Sony camera ( it has never worked as far as I know) > > Attach actions are executed fine.. > > Have you tried compiling in all available USB debugging support or seeing if > anyone else is using one like yours? No, but if I run usbd in the foreground and with some -v flags it never reports seeing a detach event even though the device driver reports it. It looks like usbd just doesn't get it... This is what the kernel logs when switching the camera on and off. Feb 17 11:57:44 trantor kernel: umass0: Sony Sony DSC, rev 1.00/2.10, addr 2 Feb 17 11:57:44 trantor kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Feb 17 11:57:44 trantor kernel: da0: Removable Direct Access SCSI-0 device Feb 17 11:57:44 trantor kernel: da0: 150KB/s transfers Feb 17 11:57:44 trantor kernel: da0: 61MB (126848 512 byte sectors: 0H 0S/T 0C) Feb 17 11:58:04 trantor kernel: umass0: at uhub0 port 1 (addr 2) disconnected Feb 17 11:58:04 trantor kernel: (da0:umass-sim0:0:0:0): lost device Feb 17 11:58:04 trantor kernel: umass0: detached Looks OK to me. And this is what usbd prints $ sudo usbd -d -v -v -v -v usbd: opened /dev/usb0 usbd: opened /dev/usb1 usbd: opened /dev/usb2 usbd: reading configuration file /etc/usbd.conf usbd: action 1: Sony DSC S70 Camera vndr=0x054c prdct=0x0010 attach='sleep 5 ;mount /sony' detach='umount -f /sony' usbd: action 2: USB device usbd: 2 actions usbd: opened /dev/usb usbd: device-attach event at 1013898654.50584, Sony DSC, Sony: vndr=0x054c prdct=0x0010 rlse=0x0210 clss=0x subclss=0x prtcl=0x device names: umass0 usbd: Found action 'Sony DSC S70 Camera' for Sony DSC, Sony at umass0 usbd: action 0: Sony DSC S70 Camera vndr=0x054c prdct=0x0010 attach='sleep 5 ;mount /sony' detach='umount -f /sony' usbd: Setting DEVNAME='umass0' usbd: Executing 'sleep 5 ;mount /sony' msdosfs: /dev/da0s1: No such file or directory usbd: 'sleep 5 ;mount /sony' returned 71 usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: processing event queue on /dev/usb usbd: device-attach event at 1013943463.949946000, Sony DSC, Sony: vndr=0x054c prdct=0x0010 rlse=0x0210 clss=0x subclss=0x prtcl=0x device names: umass0 usbd: Found action 'Sony DSC S70 Camera' for Sony DSC, Sony at umass0 usbd: action 0: Sony DSC S70 Camera vndr=0x054c prdct=0x0010 attach='sleep 5 ;mount /sony' detach='umount -f /sony' usbd: Setting DEVNAME='umass0' usbd: Executing 'sleep 5 ;mount /sony' usbd: 'sleep 5 ;mount /sony' is ok usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb ^C It looks like the driver works fine as far as I can tell, but usbd just doesn't see the detach event. -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: nsswitch changes break world build
I just did a new cvsup on a newly installed 4.1-RELEASE box with src-all so go the complete new tree and go the same error. Paul Petersen Infospace, Inc. 425-201-8966 -Original Message- From: Matthew Jacob [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 06, 2000 3:21 PM To: Jordan Hubbard Cc: [EMAIL PROTECTED] Subject: Re: nsswitch changes break world build Are you sure you don't have a partial update? On Wed, 6 Sep 2000, Jordan Hubbard wrote: > .. during the depend phase.. > > /usr/src/lib/libc/../libc/gen/getgrent.c:48: nsswitch.h: No such file or directo > ry > /usr/src/lib/libc/../libc/gen/getpwent.c:54: nsswitch.h: No such file or directo > > - Jordan > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA problems on Promise controller
With a -current kernel ( cvsupped today ) I can no longer boot. It hangs on the drives connected to the promis controller built into my MSI KT266 mobo. The messages are like ad2: READ command timeout tag=0 serv=0 - resetting Same for ad3. It tries falling back to pio mode but after that it hangs completely. I have tried putting hw.at.tags=0 in /boot/loader.conf as suggested in some older messages on this list but that dit not help. dmesg of a working kernel built 19-1-2003 is attached Copyright (c) 1992-2003 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 5.0-CURRENT #1: Sun Jan 19 15:50:33 MET 2003 [EMAIL PROTECTED]:/raid/bsd/obj/raid/bsd/freebsd/src/sys/trantor Preloaded elf kernel "/boot/kernel.ok/kernel" at 0xc04b1000. Preloaded elf module "/boot/kernel.ok/acpi.ko" at 0xc04b10ac. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1405012013 Hz CPU: AMD Athlon(tm) XP 1600+ (1405.01-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383f9ff AMD Features=0xc048 real memory = 536805376 (511 MB) avail memory = 516407296 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: flags 0x7 npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 10 entries at 0xc00f7d80 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci0: at device 6.0 (no driver attached) pci0: at device 7.0 (no driver attached) sym0: <810a> port 0xd800-0xd8ff mem 0xdbfeff00-0xdbfe irq 10 at device 8.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking atapci0: port 0xc400-0xc43f,0xc800-0xc803,0xcc00-0xcc07,0xd000-0xd003,0xd400-0xd407 mem 0xdbfc-0xdbfd irq 11 at device 12.0 on pci0 ata2: at 0xd400 on atapci0 ata3: at 0xcc00 on atapci0 isab0: at device 17.0 on pci0 isa0: on isab0 atapci1: port 0xff00-0xff0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: port 0xb800-0xb81f irq 10 at device 17.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhci1: port 0xbc00-0xbc1f irq 10 at device 17.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 ugen0: Genesys Logic USB Host To Host Bridge, rev 1.00/1.80, addr 2 uhci2: port 0xc000-0xc01f irq 10 at device 17.4 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 fdc0: cmd 3 failed at out byte 1 of 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port fdc0: cmd 3 failed at out byte 1 of 3 orm0: at iomem 0xd1000-0xd3fff,0xc9000-0xd0fff,0xc8000-0xc8fff,0xc-0xc7fff on isa0 fdc0: cannot reserve I/O port range (6 ports) sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. acpi_cpu: CPU throttling available, 16 steps from 100% to 6.2% ad0: 28629MB [58168/16/63] at ata0-master UDMA100 ad1: 29312MB [59556/16/63] at ata0-slave UDMA100 acd0: CD-RW at ata1-master PIO4 ar0: 78533MB [10011/255/63] status: READY subdisks: 0 READY ad2: 39266MB [79780/16/63] at ata2-master UDMA100 1 READY ad3: 39266MB [79780/16/63] at ata3-master UDMA100 Waiting 2 seconds for SCSI devices to settle Opened disk ad2 -> 16 Opened disk ad2 -> 16 Opened disk ad3 -> 16 Opened disk ad3 -> 16 Mounting root from ufs:/dev/ad0s1a fxp0: port 0xdc00-0xdc3f mem 0xdbe0-0xdbef,0xdbfee000-0xdbfeefff irq 12 at device 7.0 on pci0 fxp0: Ethernet address 00:d0:b7:0e:a9:cb inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listin
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
2001-02-15
Thread
Paul Richards_imap/mail.originative.co.uk/Inbox.sbd/New Mail.sbd/OpenLDAP.sbd/Devel
David O'Brien wrote: > > On Thu, Feb 15, 2001 at 11:14:38AM +, Paul Richards wrote: > > Commercial vendors will skip version numbers in their public releases > > if their internal development required more than one bump. > > Which ones? Sun Solaris still ships their libc as "libc.so.1", even in > Solaris 8. I suggest you take a look at http://www.usenix.org/publications/library/proceedings/als2000/full_papers/browndavid/browndavid_html/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
