Problems when writing to a Compact Flash card, FreeBSD 5.1
Does anyone has good suggestions for the following problem? Configuration Basic FreeBSD 5.1-RELEASE, not upgraded or patched except as mentioned below. Full verbose dmesg and kernel config below. CPU: VIA C3 Samuel 2 (532.64-MHz 686-class CPU) mfsroot atapci0: VIA 82C686B UDMA100 controller port 0xc000-0xc00f at device 7.1 on pci0 ad2: success setting PIO0 on VIA 82C686B chip ad2: CFA/4.0 ATA-0 disk at ata1-master Verbatim 64MB CF card. Writing to the CF card freezes the whole system, only way out is to power cycle the machine. I have experimented a little bit and it seems that the freezing happens after writing about 8MB of data. If the data is written in smaller chunks, problem doesn't occur. I alse patched ata-disk.c and added arbitrary delays in different places. It seems that DELAY(600) (value 60 in twait variable) in relevant places mostly prevents the problem. I think the delay is not the real solution but it only hides the real problem and cures the symptom, not the disease itself. It may be that slowing down the data transfer makes the problem go away. sysctl.conf, kernel config, dmesg (verbose) and the patched ata-disk.c are here: URL:http://www.louko.com/alo/FreeBSD-CF-problem/ Regards, Antti Louko ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Prebinding for DragonFly/FreeBSD-4
Lately Matthew N. Dodd told: Prebinding on a per executable basis rather than a per object (ELF executable or library) means that when you go to prebind KDE (for example) you run /var out of diskspace :/ Yes, that might be true. How about this approach: (doesn't cope with cyclic ``needs'' yet) - assign every .so a base address so that no collisions happen for every binary considered Then, for every binary: - start with resolving the last object (often libc), as if only this object was loaded - proceed to the next object (might be another .so or the binary) - there again, resolve stuff. if this changes resolved data in objects resolved before (global references...), save this data too, like deltas to the data of the object before. - loop This means: Every object has the data assigned which it ultimatively requests. If globals etc exists they will overridden by the next object which requested previous object. On load, just run the same way. First, load data of the last object (i.e. libc), then running the object list back to the binary, load data. Globals that get resolved another way than without object X will be overwriten by the patchup data for object X. Uhg, I hope I made myself (at least partly) clear enough to follow. cheers simon -- /\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News pgp0.pgp Description: PGP signature
inode recovery and differences between UFS1/2 soft updates
Hello. I posted a message to ports yesterday regarding the status of sysutils/ffsrecov, which won't compile with UFS2 headers. I'm in dire need of reconnecting or dumping inodes (well the associated files) because of a pair of crashes causing fsck to fail due to unreferenced files. A few years back I did a bunch of work with UFS1/FFS including a few personal utilities to dump unconnected files, etc. I know the UFS1 implementation pretty well, but that was prior to the use of soft updates or the new UFS2. I'd like to pull the valuable data off this drive before I fsck it clean and thus modify the file system. My question(s) concern the differences between UFS1 UFS2 and the use of soft updates. AFAICT, soft-updates affects the in-memory copy and does not affect the structures on the FS itself, just the order in which those structures are updated to improve performance. I therefore assume that the FS structure is similar to the original UFS1/FFS and could use my old utilities to dump the files without modification. The concern is that possibly soft updates was interrupted during a metadata write and maybe the inode or something else became corrupt; I can't imagine how, I just wanted to verify that this wouldn't happen. It seems to me that the basic differences between UFS1 UFS2 are the new ACLs and extended attributes, both of which don't change the underlying format of the file system. It is my guess that I should be able to repair this and even recompile ffsrecov using the old UFS headers. I'm also guessing that I should be able to throw the drives into an older freebsd system (w/o UFS2) and recover it that way. Please let me know if I'm way off base here. On a related note, the soft-updates document, http://www.usenix.org/publications/library/proceedings/usenix99/mckusick.html implies that the unconnected inodes I'm seeing with fsck are files that were deleted when the system was previously up, whose metadata was written but whose inodes' link counts weren't decremented yet. In such a case, these unreferenced files should be unimportant. I still wish to dump the inodes because one of my drives had a low-level failure (hence why the system crashed twice in a row) and after fsck-ing some important files did disappear without a trace (I have a list of inodes and the FS was only mounted read-only to verify the file integrity). I'm running 5.1-RELEASE with UFS2 on both drives and softupdates enabled. They are ATA/133 and ATA/100 respectfully (although the ATA/100 workes better at udma66-- otherwise I get a bunch of ICRC errors and often it'll drop to PIO mode). Any help on this topic would be appreciated. Some of the data is vital and I need it quickly. Thanks in advance, -- Rick C. PettySenior Software Engineer, KIWI Computer --- [EMAIL PROTECTED]http://www.kiwi-computer.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
How to use usb storage in Freebsd?
the version of FreeBSD is 4.8 use the dmesg, I found some related information about my usb strorage --begin here umass0: Digital , Inc. TGE UFD MP3 Player., rev 1.10/0.01, addr 2 umass0: Get Max Lun not supported (IOERROR) da0 at umass-sim0 bus 0 target 0 lun 0 da0: SigmaTel MP3UFD 0001 Removable Direct Access SCSI-4 device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) 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 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 umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR da0: reading primary partition table: error reading fsbn 0 umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 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 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 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 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 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 umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR --end here when I use the the command mkdir /mnt/usb mount -t msdos /dev/da0s1 /mnt/usb, error message withInput/output error What I should do? _ MSN Messenger: http://messenger.msn.com/cn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FYI: NetBSD mmap Improvements
Hi again; Reading more deeply,the patch was made to be able to run Linux's crossover office, but it would seem like it's not required on FreeBSD though as out mmap behaves similar to the linux one. FWIW, I found this reference on the NetBSD mailing lists: http://mail-index.netbsd.org/tech-kern/2003/06/20/0006.html cheers, Pedro. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
motherboard agp panic :O
my mobo doesnt have agp - it's a PCCHIPS m754lmr. The a href=http://www.pcchips.com.tw/M754LMR.htmlsite/a says its supposed to have AGP but mine doesnt. On boot, however, my kernel panics with agp0:contigmalloc1: size must not be 0 I just installed 5.1 from floppies - i didnt touch anything. I tried unloading the agp module with the bootloader but that doesnt work. Does anyone have any ideas on how to fix this? =/ _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: EMCsq/SAN
In the last episode (Sep 14), Danny Braniss said: hi all, Any experiance with EMCsq./SAN? I know FreeBSD is not on their list, but was wondering if it works even without the 'qualified' stamp. I'd be surprised if there were any problems, but if you already have an EMC unit, let them know you'd like to attach a FreeBSD box (give them exact hardware specs) and they'll certify it. It's in their best interest to support their customers' systems :) -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.8-stable kernel panic
Hello, It's been almost a month now since I posted the original message on the list and I'm wondering about the progress on resolving this problem. I still can reproduce the panics after cvs-supping to RELENG_4 ~ 23:00 EDT today. Thanks much. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.8-stable kernel panic
and the problem is/was? On Sun, 14 Sep 2003 [EMAIL PROTECTED] wrote: Hello, It's been almost a month now since I posted the original message on the list and I'm wondering about the progress on resolving this problem. I still can reproduce the panics after cvs-supping to RELENG_4 ~ 23:00 EDT today. Thanks much. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.8-stable kernel panic
On Sun, 14 Sep 2003 [EMAIL PROTECTED] wrote: Hello, It's been almost a month now since I posted the original message on the list and I'm wondering about the progress on resolving this problem. I still can reproduce the panics after cvs-supping to RELENG_4 ~ 23:00 EDT today. Thanks much. Ooops, I forgot to follow up on this. Ok, a few questions: 1. Can you compile INVARIANTS and INVARIANT_SUPPORT into your kernel? That might help us track down the problem. 2. What does your network setup look like? Are you using divert sockets, is there ppp in action, etc. I believe that I tried out your script at the time, and I couldn't find it to cause any problems on my system. Mike Silby Silbersack ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.8-stable kernel panic
On Sun, 14 Sep 2003, 23:05-0500, Mike Silbersack wrote: On Sun, 14 Sep 2003 [EMAIL PROTECTED] wrote: Hello, It's been almost a month now since I posted the original message on the list and I'm wondering about the progress on resolving this problem. I still can reproduce the panics after cvs-supping to RELENG_4 ~ 23:00 EDT today. Thanks much. Ooops, I forgot to follow up on this. Ok, a few questions: 1. Can you compile INVARIANTS and INVARIANT_SUPPORT into your kernel? That might help us track down the problem. 2. What does your network setup look like? Are you using divert sockets, is there ppp in action, etc. I believe that I tried out your script at the time, and I couldn't find it to cause any problems on my system. rwatson has fixed this panic in rev. 1.115 in -current: revision 1.115 date: 2003/08/26 14:11:48; author: rwatson; state: Exp; lines: +2 -0 M_PREPEND() with an argument of M_TRYWAIT can fail, meaning the returned mbuf can be NULL. Check for NULL in rip_output() when prepending an IP header. This prevents mbuf exhaustion from causing a local kernel panic when sending raw IP packets. PR: kern/55886 Reported by:Pawel Malachowski [EMAIL PROTECTED] MFC after: 3 days and haven't MFCed it yet. Here is a patch for -stable: Index: sys/netinet/raw_ip.c === RCS file: /home/ncvs/src/sys/netinet/raw_ip.c,v retrieving revision 1.64.2.17 diff -u -r1.64.2.17 raw_ip.c --- sys/netinet/raw_ip.c9 Sep 2003 19:09:22 - 1.64.2.17 +++ sys/netinet/raw_ip.c15 Sep 2003 04:21:59 - @@ -257,6 +257,8 @@ return(EMSGSIZE); } M_PREPEND(m, sizeof(struct ip), M_WAIT); + if (m == NULL) + return(ENOBUFS); ip = mtod(m, struct ip *); ip-ip_tos = inp-inp_ip_tos; ip-ip_off = 0; %%% -- Maxim Konovalov, [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
