Re: kernel compile fails without AH_SUPPORT_AR5416
2009/4/16 Maxim Sobolev : > Dennis Melentyev wrote: >> >> Could be worth an entry in UPDATING and/or explicitly added to GENERIC. > > My point is that if the option is mandatory for compiling ath(4) driver, > then there is no point in having this option in the first place. Well, fair. +1 from me :). -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kernel compile fails without AH_SUPPORT_AR5416
Hi Max, Also seen that. Fixed with careful merging on my kernel config with GENERIC one. There are additional strings involved: device ath device ath_rate_sample After adding the later one (and probably, the first one too (?)) compiled ok. Could be worth an entry in UPDATING and/or explicitly added to GENERIC. /dennis 2009/4/16 Maxim Sobolev : > Sam, > > What is the reason to have this option in the kernel config if kernel > compilation fails when this option is enabled? It also affects 7-stable. > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include > opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 > --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -Werror > /usr/src/sys/dev/ath/if_ath.c -I/usr/src/sys/dev/ath > /usr/src/sys/dev/ath/if_ath.c: In function 'ath_rx_tap': > /usr/src/sys/dev/ath/if_ath.c:3414: error: 'const struct ath_rx_status' has > no member named 'rs_flags' > /usr/src/sys/dev/ath/if_ath.c:3416: error: 'const struct ath_rx_status' has > no member named 'rs_flags' > > -Maxim > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Appeal for active bug reports relating to TCP, UDP, routing locking in 7-STABLE
Hi Robert, Could you please have a look into PR 133572? It's pretty critical for me (no incoming VPN to the office). Looks like related to this posting for me. If more info is needed, I'd be happy to provide. Including an ssh access for you, or person you name. /dennis 2009/3/17 Robert Watson : > > Dear all: > > With 7.2 approaching, I wanted to review the set of known network bug > reports (especially panics, hangs, lock order reversals) relating to TCP, > UDP, sockets, and routing in 7-STABLE. > > If you are aware of problems along these that you can confirm definitely > occur with 7-STABLE checked out no earlier than 17 March, 2009, please drop > me a private e-mail with a pointer to the thread, PR, or a reminder that > you've sent me the details already. If you don't have a PR open on the > problem, opening one and forwarding me the receipt so I can grab ownership > would be most welcome. > > I don't promise I can get them fixed by the release, but doing a review and > prioritizing the bugs that are known is a useful step in that direction. I > am specifically not interested in device driver-related problems, not > because they shouldn't be fixed, but because there's only so much time in > the day and it appears folks like Pyun have it well in hand :-). > > Robert N M Watson > Computer Laboratory > University of Cambridge > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Could Not open some sites from Windows Vista and Server 2008 when using FreeBSD as gw
Hi! Well, I'm not a PF professional, and you have rather advanced setup. So, someone with good PF experience is needed here. 2008/3/5, Владислав Недосекин <[EMAIL PROTECTED]>: > Hi, i understand that there is too little facts to analyze, but maybe some > one have the same problem and also i can provide you information. > TCP dump 192.168.200.11 - ip of PC with vista > # tcpdump | grep 192.168.200.11 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on ste0, link-type EN10MB (Ethernet), capture size 96 bytes > ^C^C^C^C3 packets captured > 433 packets received by filter > 0 packets dropped by kernel > # tcpdump | grep 192.168.200.111 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on ste0, link-type EN10MB (Ethernet), capture size 96 bytes ... > 13:51:47.676471 arp who-has 192.168.200.200 (00:1d:60:ce:74:e8 (oui > Unknown)) tell 192.168.200.111 What's that? ... > PF.CONF > ... > # Block Policy > block in log all > block in log quick from no-route to any > block in log quick on $ext_if from > block return-icmp out log quick on $ext_if to > antispoof quick for $int_if > antispoof quick for $ext_if > block out from 192.168.0.146 to any Does log shows anything interesting? I mean dropped packets. What about SQUID's log? Some special auth? Client's insisting on HTTP/1.1? Some glitches with transparent proxying (if I get it right from your PF config)? > i've tried > sysctl net.inet.tcp.rfc1323=0 > but it does't help. > > And about ip6 it is disabled, but in enabled state it does't help. Dropped by PF? -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Could Not open some sites from Windows Vista and Server 2008 when using FreeBSD as gw
Hello Vladislav, 2008/3/5, Владислав Недосекин <[EMAIL PROTECTED]>: > We are using FreeBSD as GateWay with PF. > And the problem is that some web-sites as Gmail.com or Msn.com are > unavailable from machines with Vista or Server 2008 installed. > If use external or internal proxy (Kerio WinRoute, wich also goes through > the same FreeBSD gw) they are opening correctly. > Also in 6.1 version were problems with skype from such machines. As Jeremy stated, it's too little facts to analyse. What does tcpdump show, what are the PF rules, proxy settings, authentification, etc. Just wild guess: is it IPv6 running on MS stations? PS. You might have more help from Russian/Ukrainian speaking UAFUG maillist. See http://uafug.org.ua for details. -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to take down a system to the point of requiring a newfs with one line of C (userland)
Dag-Erling: you win! Your's longer a couple of inches :)
Sorry, my hands runs in front of the loco...
Hope there are not much of *such* styled preprocessor code in FreeBSD?
It should be a plain suicide to fix a bug in it.
2008/2/18, Dag-Erling Smørgrav <[EMAIL PROTECTED]>:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Purely in the interest of showing off, here is my version. It is 81
> > bytes shorter than yours, it is valid C99 with POSIX extensions (yours
> > is not), and it produces 11,450 files in about 0.2% of the time yours
> > takes to produce 10,000.
> >
> > #include
> > #define b(i,v) for(int v=48;v<127;++v){f[i]=v;
> > #define a(i) b(i,v##i)
> > int main(void){char f[5]={'/'};a(1)a(2)a(3)truncate(f,0);
>
> Two bugs:
>
> 1) I forgot to include the correct version of the code
>
> 2) the version I had created a few files with '/' in their names; this
>slightly nastier creates 10,648 files with only letters.
>
> #include
> #define b(i,v)for(int v=65;v<87;){i[f]=v++;
> #define a(i)b(i,v##i)
> int main(void){char f[4]={47};a(1)a(2)a(3)truncate(f,0);
>
> DES
> --
> Dag-Erling Smørgrav - [EMAIL PROTECTED]
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
--
Dennis Melentyev
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very bad performances with wpi and 7.0-RC1
device ID 3 > pmtimer0 on isa0 > orm0: at iomem 0xc-0xcefff pnpid ORM on isa0 > ppc0: parallel port not found. > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > ums0: on > uhub0 > ums0: 3 buttons and Z dir. > Timecounters tick every 1.000 msec > hptrr: no controller detected. > ad0: 95396MB at ata0-master UDMA100 > acd0: DVDR at ata0-slave UDMA33 > pcm0: > pcm0: > SMP: AP CPU #1 Launched! > GEOM_LABEL: Label for provider ad0s1 is msdosfs/RECOVERY. > GEOM_LABEL: Label for provider ad0s2 is ntfs/Syst\M-hme. > GEOM_LABEL: Label for provider ad0s5 is msdosfs/ . > Trying to mount root from ufs:/dev/ad0s3a > * > > Am is alone with this performance problem? I cannot use wpi driver in > these conditions, so I use re driver for my NIC. > > Nicolas > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installation problems of FreeBSD 7 beta 2 on Dell D610 (multiboot con solaris, linux, winxp)
HI Stefano! 2007/11/27, Stefano Spinucci <[EMAIL PROTECTED]>: > On 11/27/07, Dennis Melentyev <[EMAIL PROTECTED]> wrote: > > Hi! > > > > 2007/11/27, Stefano Spinucci <[EMAIL PROTECTED]>: > > > I encountered some problems installing FreeBSD 7 beta 2 on my Dell > > > D610 laptop, on the original 60 gb hd; the hd is formatted as follows: > > > - primary 1, 15 gb, ntfs for Windows XP > > > - primary 2, 15 gb, solaris for Open Solaris > > > - primary 3, 10 gb, fat32 for FreeBSD > > > - extended, 20 gb, 3 partitions for linux > > > > > > I tried to install FreeBSD many times, but after the geometry error > > > (the geometry is however correctly recognized), FDISK doesn't find any > > > partition and the space is shown as free, unpartitioned. > > > > > > I tried to set the partition type for FreeBSD to FAT16, FAT32, FreeBSD > > > and I also reformatted the partition many times, but with no success. > > > > > > have you any idea??? > > > > Are you kidding? > > If no, just read the handbook. And check the partition type for > > FreeBSD. FAT[13][26] is for MustDie. > > > > -- > > Dennis Melentyev > > I'm not kidding. > > I read the handbook before installing, before writing this emai and > now and, correct me if I'm wrong, FDISK should recognize existent primary > partitions; then, *inside* FDISK, I can format the primary partiton (for me > #3) > for FreeBSD. Well, one of us are just using different terminology then. 0. FAT* is not a right filesystem type for FreeBSD. It must be UFS/UFS2 1. Geometry is what you BIOS think what should it be. Not the numbers on device label. 2. Sysinstall is NOT fdisk. It has some functionality though. So, find out what geometry is used by BIOS for you disk and supply it before any access to slices. PS. There are some reports on local mailing lists about problems with sysinstall's fdisk. Try just real fdisk, disklabel and newfs instead (man fdisk disklabel newfs for details). PPS. Nevertheless, handbook and man pages are a mandatory for all this issues. > > from section 2.6.2 of the Hankbook > "The second section [of FDISK] shows the slices that are currently on > the disk, where they start and end, how large they are, the name > FreeBSD gives them, and their description and sub-type." > > Then I repeat my question: > why FDISK shows my disk (with 3 primary partitions and an extended partition) > as a single block of unused space ??? Well, this is much more clean problem description. Fix your geometry. Also, if disks are not ATA/SATA, state this. > > If you have some useful ideas (and not, RTFManual/MailingList is not an useful > idea) please reply me. /me disagree here -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installation problems of FreeBSD 7 beta 2 on Dell D610 (multiboot con solaris, linux, winxp)
Hi! 2007/11/27, Stefano Spinucci <[EMAIL PROTECTED]>: > I encountered some problems installing FreeBSD 7 beta 2 on my Dell > D610 laptop, on the original 60 gb hd; the hd is formatted as follows: > - primary 1, 15 gb, ntfs for Windows XP > - primary 2, 15 gb, solaris for Open Solaris > - primary 3, 10 gb, fat32 for FreeBSD > - extended, 20 gb, 3 partitions for linux > > I tried to install FreeBSD many times, but after the geometry error > (the geometry is however correctly recognized), FDISK doesn't find any > partition and the space is shown as free, unpartitioned. > > I tried to set the partition type for FreeBSD to FAT16, FAT32, FreeBSD > and I also reformatted the partition many times, but with no success. > > have you any idea??? Are you kidding? If no, just read the handbook. And check the partition type for FreeBSD. FAT[13][26] is for MustDie. -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random data corruption with USB mass storage on 7.0-BETA2
Hello Heiko, Yes, you really have different issue. From now on, I have no more ideas. Hope you'll find the root of the problem. 2007/11/16, Heiko Wundram (Beenic) <[EMAIL PROTECTED]>: > Am Donnerstag, 15. November 2007 20:34:57 schrieb Dennis Melentyev: > > You need to check is it FAT12 or FAT16 on a card. AFAIR fdisk can show > > this info. > > It's a FAT16 when formatted by the phone software (I checked that initially), > but I can format the stick as FAT32 (by using newfs_msdos on the device) and > still have the phone accept it, but when copying to the FAT32-formatted > device random data corruption still occurs, i.e. the same problem noted in my > last mail: > > 1) format device as FAT32 with newfs_msdos, > 2) mount, > 3) copy files, > 4) unmount, (and don't plug the USB out) > 5) mount, > 6) checking files shows the metadata as being the same as before the unmount, > but the files being different. > > The file corruption that occurs is similar: random, but not completely, > because the differing file content comes at (somewhat) fixed offsets in the > files. > > As I did not unplug the phone from the USB port while doing the FAT32 check > run, the phone software never got a chance to actually access the memory > stick while doing the above (Symbian blocks all accesses to the stick when > USB in file-transfer mode is active), so I should guess the corruption comes > purely from the host system. > > > Had the same problem with SE 64Mb card in K750i. It turned out that SE > > creates FAT12 on a 32+Mb disk, which is not supposed to be an option. > > The K750i is not comparable, as the W600i is UIQ-based (i.e. Symbian + > extras), whereas the K750i is not. > > > PS. To just make it work - just re-format it and restore folders > > structure. But please, create a filesystem dump first, to let > > developers decide is it a fault of SE phone or MSDOSFS code. > > After you talked about filesystem dumps, you got me an idea: > > 1) format the memory stick with the phone software > 2) make a dump with dd (dd if=/dev/da0 of=disk.img bs=4k) > 3) set that up as a memory disk, > 4) mount that: lo and behold, the directory structure on the memory disk was > just as it is displayed in the file manager of the phone (i.e., MEMSTICK.IND > and MEMSTICK_PRO.IND were there in the root of the mount-point) > 5) copy my files over to the mount point, > 6) unmount the memory disk, > 7) mount the memory disk, check files against the source, lo and behold, the > files were equal (i.e., not corrupted during copy), > 8) unmount the memory disk, > 9) remove the memory disk, > 10) copy the disk image back to the phone (dd if=disk.img of=/dev/da0 bs=4k) > > When I now access the memory stick from the phone (by unplugging it from USB), > the files aren't corrupt. > > To finally test my hypothesis that this is a bug in the msdosfs-code, I > mounted the device directly after doing this (which had MEMSTICK.IND and > MEMSTICK_PRO.IND disappear again under the mount-point), copied some more > files over, unmounted, remounted, and the same corruption seen before > occurred again with the newly copied files (i.e., the phone software > complained about broken MP3s when unplugging the phone from USB later on). > Testing the old files (which I put on the memory stick with the above > procedure) under the mount-point against the source showed them as being not > equal, but the phone did not complain about corrupted MP3s when trying to > play them, so basically on the "real" medium the data was still intact. > > If anybody wants to test with a dump of the filesystem or just more info, mail > me, and I'll set that up somewhere as a download. > > For now, I'll personally try and see what changed between 6.2-STABLE and > 7.0-BETA2 in the msdosfs-code that breaks this. > > -- > Heiko Wundram > Product & Application Development > - > Office Germany - EXPO PARK HANNOVER > > Beenic Networks GmbH > Mailänder Straße 2 > 30539 Hannover > > Fon+49 511 / 590 935 - 15 > Fax+49 511 / 590 935 - 29 > Mobil +49 172 / 437 3 734 > Mail [EMAIL PROTECTED] > > > Beenic Networks GmbH > - > Sitz der Gesellschaft: Hannover > Geschäftsführer: Jorge Delgado > Registernummer: HRB 61869 > Registergericht: Amtsgericht Hannover > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random data corruption with USB mass storage on 7.0-BETA2
You need to check is it FAT12 or FAT16 on a card. AFAIR fdisk can show this info. Had the same problem with SE 64Mb card in K750i. It turned out that SE creates FAT12 on a 32+Mb disk, which is not supposed to be an option. Some time ago this was discussed, but I was unable to provide a dump from such card (have no such card anymore). PS. To just make it work - just re-format it and restore folders structure. But please, create a filesystem dump first, to let developers decide is it a fault of SE phone or MSDOSFS code. PPS. http://docs.FreeBSD.org/cgi/mid.cgi?b84edfa10707011305g4cffb298q70c3507f75121799 2007/11/15, Heiko Wundram (Beenic) <[EMAIL PROTECTED]>: > Hey all! > > While trying to upload some music to my mobile phone, I stumbled across the > following odd behaviour when uploading files to an SD-card (inserted into my > Sony Ericsson M600i) which is connected via USB as a mass-storage device: > > - > ... > umass0: addr 2> on uhub0 > ... > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: < M600i 1.0> Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 59MB (121821 512 byte sectors: 64H 32S/T 59C) > ... > - > > The card is formatted as FAT (by the phone software), and I can mount it with > a plain "mount -t msdosfs /dev/da0 /mnt" without any kind of problems, except > that directories that should be there, at least as displayed by the File > Manager on the phone, aren't present under the mount point. There is no > output to dmesg on the mounting (besides the GEOM label for the stick being > removed). > > When copying files to the device, the phone displays that a transfer is taking > place, and after finishing the transfer, comparing files on the mountpoint to > the source files shows them as being equal. When I then unmount the device > (which also runs cleanly, without any further output to dmesg except the > reappearance of the GEOM label) and remount it, the copied files appear under > the mount-point, but comparing the files on the mount-point against the > source files shows them as being different. The sizes and modification dates > are equal, though, and most of a file is correct, but non-deterministically > every 16k or similar a stream of random bytes appears. > > When I do the same transfer from a 6.2-STABLE (last csupped some two months > ago), the directories the phone reports appear under the mount-point, and the > same transfer works properly (i.e., uploading the file, unmounting, > remounting and comparing show the files as being the same, and playing the > file on the phone works, and doesn't contain corruption artefacts). > > The 6.2-STABLE shows similar information on the device in dmesg (esp. the > H/S/C info). > > 6.2-STABLE is a plain GENERIC kernel, with atapicam loaded (and some other > device drivers for sound and Bluetooth), 7.0-BETA2 is a slightly adapted > GENERIC (with SCHED_4BSD replaced with SCHED_ULE and SMP support removed) > also with atapicam loaded (and some other device drivers for sound and > bluetooth). > > I'll try to do some digging into the changes made to msdosfs between > 6.2-STABLE and 7.0-BETA2 some time later on, but if anybody else is seeing > this behaviour too or wants me to produce more debugging info on this (esp. > some msdosfs debugging infos), feel free to send me a mail, and I'll try to > get this done some time during the day. > > -- > Heiko Wundram > Product & Application Development > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Get packages from stabele tree via sysinstall
Hello Michael, AFAIU, the problem is that 6.3-PRERELEASE does not have binary packages built for it. It is intended for testing purposes. Just wait for 6.3-RELEASE plus allow some time to build everything. PS. There is Russian/Ukrainian speaking UA-FUG with some of FreeBSD committers and big ISP professionals in members. See http://uafug.org.ua 2007/10/31, Михаил Кипа <[EMAIL PROTECTED]>: > I want to install precompiled packages via sysinstall. I have update my > 6.2-RELEASE system with cvsup to 6.3-PRELEASE. Now I want to use sysinstall to > install precompiled packages, but I get an error " Can`t find "6.3-PREREASE" > on ..." (I use ftp!). So what release name I shoul use to get packages from > 6-stable package collection? > Mihail > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BIND 9.3.1 - How to get rid of AAAA querys?
Hi Ian, 2007/9/14, Ian Smith <[EMAIL PROTECTED]>: > On Thu, 13 Sep 2007, Andreas Pettersson wrote: > > > > [snip] > > >Why don't you go the other way and get yourself IPv6 > > >connectivity. You do realise that you will require it to > > >reach many sites in about 3 years time as they will be IPv6 > > >only > > > > For almost 10 years I've heard discussions about the successor to IPv4, > > but from my point of view (may differ from others..) not much has > > happened. Of course, I can imagine that when the wheel starts rolling > > for real things might change quickly. 3 years may prove to be correct, > > but are there any clear signs pointing in this direction? > > eg: > > http://www.potaroo.net/tools/ipv4/index.html > > http://www.circleid.com/posts/transition_to_ipv6_address/ > > http://www.circleid.com/posts/ipv6_extinction_evolution_or_revolution/ Nice readings! Thanks for the links! -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: removing external usb hdd without unmounting causes reboot?
Hi Oliver! 2007/7/30, Oliver Fromme <[EMAIL PROTECTED]>: > Peter Jeremy wrote: > > Dennis Melentyev wrote: > > > Is there any correct way to initiate funding to rewrite VM/VFS related > > > parts (getting non-panicable removable devices)? Who should one > > > contact for this? > > > > I would suggest that the first step is finding someone (or a few > > people) with the necessary skills who is/are willing to work on the > > problem. Offering funding may increase the potential pool but will > > not automatically solve the skills/knowledge issue. > > By the way, the problem apparently has been solved in > DragonFly BSD (i.e. DF BSD does not panic when a mounted > FS is physically removed). Maybe it is worth to have a > look at what they did to fix it, and possibly port it > over to FreeBSD. On the other hand, the internal data > structures of the VM subsystem have diverged quite a lot > from FreeBSD, so I don't know if it would really help. > > (No, I'm not volunteering; lack of time and interest.) That was I asking same question in DragonflyBSD list :) But yes, VFS and VM in FBSD and DFBSD are way too differ since 4.1 times. It is not an option, sadly. -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: removing external usb hdd without unmounting causes reboot?
Hello Peter, Thank you for your answer. 2007/7/28, Peter Jeremy <[EMAIL PROTECTED]>: > On 2007-Jul-27 18:29:44 +0300, Dennis Melentyev <[EMAIL PROTECTED]> wrote: [skipped architectural description, and, thank for it] > > >I'd rather consider this problem as security one. > > I think that is a very long stretch. Well, it is. :) > > >Is there any correct way to initiate funding to rewrite VM/VFS related > >parts (getting non-panicable removable devices)? Who should one > >contact for this? > > I would suggest that the first step is finding someone (or a few > people) with the necessary skills who is/are willing to work on the > problem. Offering funding may increase the potential pool but will > not automatically solve the skills/knowledge issue. Got your point. > > As for initiating funding, you have several options: > 1) Do it yourself: Find someone(s) to do the work (either by approaching >likely candidates or advertising on FreeBSD lists), get an indication >of the necessary funding and then raise the funds yourself. > 2) Approach the FreeBSD Foundation, with or without names. > 3) Approach corporations that are FreeBSD-friendly. Yahoo! and Apple are >the first ones that come to mind. I'd probably try 2nd and 3rd items - unfortunately I can't offer enough myself. Hope, it would be possible to find enough support from the community and/or corporations. Thanks for the clues! -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: removing external usb hdd without unmounting causes reboot?
Hello Peter and everybody, Sorry for continuing this thread, but let's not forgot the security aspect of this issue: If you run amd on some host configured to automount USB drives, it's easy to force DoS attack. Just insert the flash/HDD and remove it short after it's mounted. Sure, it's almost close to ability of just pulling off power cable or pressing reset, but still a problem. Even if nobody will put out the USB stick, just in case of a Flash with dead blocks on it or just badly formatted one it's too easy to get totally unexpected panics. I'd rather consider this problem as security one. Is there any correct way to initiate funding to rewrite VM/VFS related parts (getting non-panicable removable devices)? Who should one contact for this? PS. Happy sysadmin day! *drink* 2007/7/24, Peter Jeremy <[EMAIL PROTECTED]>: > On 2007-Jul-23 16:15:56 +0200, Oliver Fromme <[EMAIL PROTECTED]> wrote: > >So, currently the best work-around is to use amd with a > >very short timeout. Or simply remember to umount your > >removable media manually. > > Or ports/emulators/mtools > > -- > Peter Jeremy > > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: removing external usb hdd without unmounting causes reboot?
Hi All! 2007/7/19, Momchil Ivanov <[EMAIL PROTECTED]>: On Thursday 19 July 2007 09:17:48 [LoN]Kamikaze wrote: > Norberto Meijome wrote: > > On Wed, 18 Jul 2007 17:41:04 +0200 (CEST) > > > > Oliver Fromme <[EMAIL PROTECTED]> wrote: > >> another work-around > >> is to use the auto mounter daemon (amd(8)). It umounts > >> file systems automatically that are not in use. > >> Another nice feature of amd(8) is that you don't have > >> to mount the file system either -- Simply plug the USB > >> stick in, then access it, and amd(8) will automatically > >> mount it for you. > > > > Now, something I dont understand - amd runs > > at user level, and it mounts filesystems, and nothing dies when the > > filesystems go away (other than the obvious cases for the applications > > trying to write to the FS in question). Doesn't amd , at some point , > > have to tell the kernel 'please mount this filesystem' here or there? > > Isn't the kernel STILL involved in all this? and why doesnt the kernel > > panic when the FS goes away? > > The trick is that amd unmounts the device after a couple of seconds, so > when someone accidentally removes a usb drive, it doesn't really matter. > Amd will simply fail to mount it on the next access. If you remove the > device during or shortly after accessing it, it still will panic the > system. What is then the reason for the kernel not being able to unmount a filesystem whose provider is no longer present? What in the process of unmounting denies unmounting a filesystem whose provider is no longer available? Why can the kernel not just inform all programs that files have to be closed and are unaccessible any more, then consider the fs as unmounted and remove any bits of it left in the VM. Why can kernel not just ignore interruped/pending writes to that fs, drop the data, return an error to the program that initiated the write and just go on. For me, the most expected behaviour of API is the same as socket one: In case recv/send fails (socket peer gone, router in-the-middle is died, excavator came across the cables, etc) I just get a timeout (for the first time), then (once remote socket is considered closed) just return with -1 and appropriate errno set. Since every (not braindamaged) program expect possible disk failures, everyone checks for return/errno. It should be extremely safe to just supply notify userland with "-1/errno" to handle over the error case at application level. Since I do understand the complexity and impact of VM/[V]FS code, I'd rather vote for funding an external project on better VM/VFS separation and improvement. Later, this project codebase must be merged into the CURRENT, tested and go "STABLE" the usual way. The famous "Floppy" issue of FreeBSD MUST go away, it's just a shame and long standing base for unpleasant rumor/jokes. Could it be the good task for FreeBSD Foundation or what ever other investor? Sorry for adding just 0.02UAH instead of real $20-30-50 of personal money to the fund's account. If there is such a fund for this particular problem, I'll vote with money instead of bytes. I believe, there will be a lot more people willing to do the same to gain enough funding. -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot mount Sony Ericsson mobile phone, msdosfs too restrictive?
Can't confirm, but it seems like formating card with phone will give you FAT12 even on 1Gb card. (Not volunteering to reformat my "player") :) 2007/7/2, Dennis Melentyev <[EMAIL PROTECTED]>: Hi! 2007/7/2, Raaf <[EMAIL PROTECTED]>: > Brian Chu wrote: > > Raaf, > > > > What's the size of the memory stick? Is it 32MB like Dennis has? It was 64MB card also. :) AFAIR, FAT12 is just not correct format for disks larger than 32Mb. It has to use clusters not handled by original MSDOS in this case. So, my answer is: SE just use wrong FAT. But, meanwile, it should be ok to allow this insanity be handled. Despite I'd rather use smaller clusters for such a tiny drive. > > > > It's a 64MB memory stick using FAT12. MSDOS 3.3 will go crazy with that :) > > > The check for the field that affected you isn't critical to msdosfs' > > operation, but the field itself is specified to be non-zero. > > Konstantin, is it alright to remove this field? > > > > It seems there are more people having problems with the sanity checking > code of msdosfs, see also this related pr: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=93860 > > -- Dennis Melentyev -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot mount Sony Ericsson mobile phone, msdosfs too restrictive?
Hi! 2007/7/2, Raaf <[EMAIL PROTECTED]>: Brian Chu wrote: > Raaf, > > What's the size of the memory stick? Is it 32MB like Dennis has? It was 64MB card also. :) AFAIR, FAT12 is just not correct format for disks larger than 32Mb. It has to use clusters not handled by original MSDOS in this case. So, my answer is: SE just use wrong FAT. But, meanwile, it should be ok to allow this insanity be handled. Despite I'd rather use smaller clusters for such a tiny drive. > It's a 64MB memory stick using FAT12. MSDOS 3.3 will go crazy with that :) > The check for the field that affected you isn't critical to msdosfs' > operation, but the field itself is specified to be non-zero. > Konstantin, is it alright to remove this field? > It seems there are more people having problems with the sanity checking code of msdosfs, see also this related pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=93860 -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot mount Sony Ericsson mobile phone, msdosfs too restrictive?
Well, had the same problem.
For me, it looks like SE is using FAT12 (!!!Not 16!!!) on a devive
larger than 32MB. Could have something slipped off my mind, but quite
close. It is a BROKEN msdosfs on a stick.
Just re-formated 1Gb flash with FAT32 using card reader and both K750i
and FreeBSD are happy.
2007/7/1, Raaf <[EMAIL PROTECTED]>:
Hi, i got a Sony Ericsson mobile phone that came with a pre-formatted
memory stick that i'm unable to mount in FreeBSD (it mounts fine in
Linux).
After investigating i found out that the FreeBSD msdsofs driver bails
out on the following code (the pmp->pm_Heads being zero):
--
if (!pmp->pm_BytesPerSec || !SecPerClust
|| !pmp->pm_Heads
#ifdef PC98
|| !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 255) {
#else
|| !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 63) {
#endif
error = EINVAL;
goto error_exit;
}
--
Removing the check for pmp->pm_Heads fixes it for me.
Is the check for pmp->pm_Heads really necessary?
Grepping through the msdosfs sources i can only see it being used for
validation and not used in any calculation (the same applies for the
pmp->pm_SecPerTrack value)
--- sys/fs/msdosfs/msdosfs_vfsops.c.origSun Jul 1 20:42:14 2007
+++ sys/fs/msdosfs/msdosfs_vfsops.c Sun Jul 1 20:46:57 2007
@@ -483,7 +483,6 @@
/* XXX - We should probably check more values here */
if (!pmp->pm_BytesPerSec || !SecPerClust
- || !pmp->pm_Heads
#ifdef PC98
|| !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 255) {
#else
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Dennis Melentyev
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how much beer do I need to get this patch applied?
While I haven't seen any problem with patch itself since it just adding a _useful_ knob, I personaly managed to use procmail to filter most of that SPAM. My solution is not as CPU friendly as patch but 2000 messages is not an ultimate load for modern comps. +1 for adding the patch. Also, will not die if not added :) Just another 0.02UAH into the bike sched budget. 2007/6/20, Kurt Jaeger <[EMAIL PROTECTED]>: Hi! [on a bikeshed:] > >3. Actual errors *will* be reported, and *will be read* if I don't > >have to delete thousands of non-errors. > > Perhaps a separate mailbox dedicated to this task, with a script > (grep?) that parses the emails in that mailbox daily looking for > expected messages, noting and deleting them, with unsent messages > noted via an email and messages with unexpected content forwarded as > well? Yes, that's what I have hoped for in the past as well. That script to analyse is not that easy to write, because there are many border cases. This script never materialized until now, and therefore, for the time being, I seriously hope this patch will be committed. -- [EMAIL PROTECTED] +49 171 310137213 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Q] multisync irmc/irmc_bluetooth plugins
2006/9/18, Henrik Brix Andersen <[EMAIL PROTECTED]>: On Sun, Sep 17, 2006 at 10:55:24PM +0200, Pav Lucistnik wrote: > Plus, Multisync is dead in water, project abandoned... Not completely true. Multisync in its current form is abandoned, but a new version based on the OpenSync framework (http://www.opensync.org/) is in the works. Thanks, will check it. -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Q] multisync irmc/irmc_bluetooth plugins
Hi all, Is it possible to build irmc/irmc-bluetooth plugins? I tried to play with them a bit, and stuck at the very beginning with configure unable to find proper entries in obex structures for just irmc plugin. Looks like we have "customdata" member in obex_ctrans_t while irmc code trying to find "userdata". Bluetooth refers to some bluez/bluez-kernel >=2.3 which means nothing to me. Is it Linux-only app, or it is possible to make it finally run on FreeBSD? -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.1-STABLE: Unexplained power off
2006/8/15, Android Andrew [:] <[EMAIL PROTECTED]>: Dennis Melentyev wrote: > Don't take it personally, but could it just power-off the monitor? > What does show the disk activity led? :) No, monitor shows there's no signal... Disk activity led and power led are off. Keyboard leds are off too. There is no network activity, no ping-reply... Hm... According to this, no need for logging script: if network is not responding, the whole system should have been halted... :( Afraid there is only one way - to kernell debugger, but I not an expert there. > AFAIR, if you have to power-off manually (long pressing power button) > before power-on, it does will make FS dirty. Instead of real correct > power-off case. > > Try to make a simple script appending some log/file with timestamps, > wait untill your issue occurs, then check the time, wait for, say, 5 > more minutes and then cold-start system again. > > I bet, the script will still be logging messages into the file while > system looks like "sleeping". Ok, I'll try it. -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.1-STABLE: Unexplained power off
Don't take it personally, but could it just power-off the monitor?
What does show the disk activity led?
AFAIR, if you have to power-off manually (long pressing power button)
before power-on, it does will make FS dirty. Instead of real correct
power-off case.
Try to make a simple script appending some log/file with timestamps,
wait untill your issue occurs, then check the time, wait for, say, 5
more minutes and then cold-start system again.
I bet, the script will still be logging messages into the file while
system looks like "sleeping".
15.08.06, Android Andrew<[EMAIL PROTECTED]> написал(а):
On Tue, 15 Aug 2006 13:31:08 +0300, Alexey Karagodov <[EMAIL PROTECTED]>
wrote:
> are you realy SURE that you workstation turned off? i think it just
> "sleeping" ;-) .
> after power and boot up is your file-systems "clean" or fsck takes place
> during boot-time?
> please, check your power-save settings in BIOS and is OS ...
Thanks for idea Alexey!
I think it is not "sleeping" because log messages look like ones after
crash:
Aug 15 00:23:04 callisto kernel: Trying to mount root from ufs:/dev/ar0s1a
Aug 15 00:23:04 callisto kernel: WARNING: / was not properly dismounted
Aug 15 00:23:04 callisto kernel: WARNING: /home was not properly dismounted
Aug 15 00:23:04 callisto kernel: WARNING: /tmp was not properly dismounted
Aug 15 00:23:04 callisto kernel: WARNING: /usr was not properly dismounted
Aug 15 00:23:04 callisto kernel: WARNING: /var was not properly dismounted
Sometimes system boots in single-user mode with "run fsck mannualy"
message.
I've tried to play with power-save settnigs in BIOS and with kernel
apm-module but it takes no effect.
There are two SATA-HDD in my system. They are configured as RAID0 ("Intel
Matrix" on-board controller). I guess the problem could be here, but I
don't know how to check it.
_
.-._.=\-.
(_)=='(_)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Dennis Melentyev
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to use firefox
2006/7/11, Mihir Sanghavi <[EMAIL PROTECTED]>: Hi, I have installed firefox using pkg_add -r firefox and now want to use xterm i tried using xterm and it says: Cannot open display and display not set Exit root shell back to user's one. -- What we see depends mainly on what we look for. -MIHIR ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 and USB: problems with mounting SonyEricsson K750 flash
Hi! 2006/5/17, Bengt Ahlgren <[EMAIL PROTECTED]>: Hi! "Dennis Melentyev" <[EMAIL PROTECTED]> writes: > I've got a problem with mounting SonyEricsson K750 flash card: > 6.1 is not stabily mounting/recognizing device, and, after several tries > ended up in creating TWO IDENTICAL device nodes in /dev!!! > > Has anyone any suggestion on how to resolve such a problem? > > Here is kind of my actions log: > After connecting the cable, got this in console: > umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 1902MB (3895296 512 byte sectors: 255H 63S/T 242C) > > so far everything is ok, except the reported disk size: it's 1Gb, not 2Gb. I get a different error, but which could possibly be related. I am running 6.1R on a Thinkpad X40. I just thought my connectors have accumulated too much dirt, because after retrying two-three times it succeeds. But perhaps dirt is not the issue, because when it succeeds in reading the size, mounting and reading works perfectly without errors. Here is what I get about 3 times out of 4 when attaching: [ log skipped] And, correctly when it succeeds: umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 61MB (126912 512 byte sectors: 64H 32S/T 61C) I am not sure when the above problems started. When my phone was new (July 2005) it worked without any problems. I was most likely running 5.4 at that time. It runs perfectly on WinXP. So, connectors should not be an issue. It might be a problem with not-fully-standard things by SE, Also, I tried to play with different FAT types (16/32). FAT16 seemd to be much faster, but also not yet ideal. After I upgraded the phone software yesterday and reformated flash using native phone tools, it helped: da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present umass0: at uhub2 port 2 (addr 2) disconnected ### first try was not successful, but w/o any other errors in console (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached ### Reattached the device umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 951MB (1947648 512 byte sectors: 64H 32S/T 951C) ### And yes, it's finally up and correctly sized So, the only FBSD-related issue left is a duplicated entry in /dev listing. Reboot helped, but that's not the way it should be. Could someone check the possibilities to have duplicate entries in directory listing (at least under /dev)? -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.1 and USB: problems with mounting SonyEricsson K750 flash
Hi All! I've got a problem with mounting SonyEricsson K750 flash card: 6.1 is not stabily mounting/recognizing device, and, after several tries ended up in creating TWO IDENTICAL device nodes in /dev!!! Has anyone any suggestion on how to resolve such a problem? Here is kind of my actions log: After connecting the cable, got this in console: umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1902MB (3895296 512 byte sectors: 255H 63S/T 242C) so far everything is ok, except the reported disk size: it's 1Gb, not 2Gb. Trying to mount, get at console: umass0: BBB reset failed, STALLED Killing mount with ^C. After extracting plug from the socket: umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED g_vfs_done():da0s1[READ(offset=16384, length=4096)]error = 5 umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: at uhub2 port 2 (addr 2) disconnected Trying to plug it back again for several times, some failures to recognize the device, and finally it recognized again. Mounting again, got: D-MELENTYEV# mount /mnt/flash/ mount_msdosfs: /dev/da0s1: Device not configured Take a look at /dev and start going mad seeing two identical nodes: D-MELENTYEV# ll /dev/da0* crw-r- 1 root operator0, 116 May 15 12:39 /dev/da0 crw-r- 1 root operator0, 114 May 15 12:39 /dev/da0s1 crw-r- 1 root operator0, 114 May 15 12:39 /dev/da0s1 D-MELENTYEV# stat /dev/da0* 67174144 116 crw-r- 1 root operator 116 0 "May 15 12:39:14 2006" "May 15 12:39:14 2006" "May 15 12:39:14 2006" "Jan 1 02:59:59 1970" 4096 0 0 /dev/da0 67174144 114 crw-r- 1 root operator 114 0 "May 15 12:39:14 2006" "May 15 12:39:14 2006" "May 15 12:39:14 2006" "Jan 1 02:59:59 1970" 4096 0 0 /dev/da0s1 67174144 114 crw-r- 1 root operator 114 0 "May 15 12:39:14 2006" "May 15 12:39:14 2006" "May 15 12:39:14 2006" "Jan 1 02:59:59 1970" 4096 0 0 /dev/da0s1 The file names are absolutely identical!!! D-MELENTYEV# find /dev -name "da0*" -print0 | hd 2f 64 65 76 2f 64 61 30 73 31 00 2f 64 65 76 2f |/dev/da0s1./dev/| 0010 64 61 30 00 2f 64 65 76 2f 64 61 30 73 31 00 |da0./dev/da0s1.| Any ideas? What could I include in PR apart from info in this message? PS. 6.1-RC1 worked fine PPS. uname -a FreeBSD D-MELENTYEV.HOME 6.1-STABLE FreeBSD 6.1-STABLE #2: Wed May 10 15:08:05 EEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 cvsup'ed on May 10th several hours before rebuilding everything. -- Dennis Melentyev console.log Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed
Sorry, forgot to add the list into CC... -- Forwarded message -- From: Dennis Melentyev <[EMAIL PROTECTED]> Date: 06.04.2006 16:12 Subject: Re: Disappointed To: Alexey Karagodov <[EMAIL PROTECTED]> Alexey, 2006/4/6, Alexey Karagodov <[EMAIL PROTECTED]>: > hi. > i think, this unstablity happaning just because developers trying to make > two systems at one time, one is 6.0 and another 7.0 current and they > supporting old version, lower then 6.0 > i want to ask developers, why you developing new system, 7.0, if you don't > finish old, 6.0 ?! > finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 and > so > on ... > what so new and revolutionary in 7.0 in comparison with 6.0 ?! > to use your system i must be a DEVELOPER, but i don't have so much time! i > 'Must' is a t strong word. If they wish - they will. If you need you have two options: do it yourself or pay some money to someone who can. Period. Or have you paid them for that? :) Just don't use any system in production without having it tested first. This world is not perfect, and software is way less perfect than world. :) don't want to develope! i want to use, i want to help you with some advise ( > e.g. what feature to add, what feature to change etc), i can and i want to > share some of my hardware to feet your needs, make a mirror, make a test > server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm > just That's great! That's your contribution to the project. Every one here contribute whatever they can: money, hardware, code, PR, support. But no one can say what someone must to do. PS. Без обид? -- Dennis Melentyev -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: Usb Router
AFAIK, it's still impossible to connect any human body to the Internet via USB routers. :) Be more descriptive: show your 'uname -sr', usb-related parts of dmesg, router model, what do you wish to have as a result, etc. 2006/3/25, Maher Mohamed <[EMAIL PROTECTED]>: > > How can i connect to my usb router? > > -- > Mohamed M. Maher > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata timeouts in 4.1-stable?
IMHO problem may be within with your CD-DRIVE. I has such a problem with SAMSUNG 24xCD until I haven't pull it out and throw away. It can work normally ONLY as a single drive on the controller. BTW it's "IMHO" ;) On Fri, Oct 13, 2000 at 08:48:44PM -0400, Andy wrote: > I'm using fbsd 4.1-stable, last cvsup and make world was > 2000-09-24. Everything looked fine until I added another ide drive, as > secondary slave, to the primary master. I did check the archives first, > and what I found was that people have reported this problem with ATA-66 > controllers, not ATA-33. I now get log warnings such as: > > Oct 13 19:29:30 lowrider /kernel: ad2: WRITE command timeout - resetting > Oct 13 19:29:30 lowrider /kernel: ata1: resetting devices .. done > Oct 13 19:29:40 lowrider /kernel: ad2: WRITE command timeout - resetting > Oct 13 19:29:50 lowrider /kernel: ata1: resetting devices .. done > Oct 13 19:30:11 lowrider /kernel: ad2: WRITE command timeout - resetting > Oct 13 19:30:11 lowrider /kernel: ata1: resetting devices .. done > Oct 13 19:30:11 lowrider /kernel: ad2: WRITE command timeout - resetting > Oct 13 19:30:11 lowrider /kernel: ata1: resetting devices .. done > Oct 13 19:30:11 lowrider /kernel: ad2: WRITE command timeout - resetting > Oct 13 19:30:11 lowrider /kernel: ata1-master: WARNING: WAIT_READY > active=ATA_ACTIVE_ATA > Oct 13 19:30:11 lowrider /kernel: ad2: trying fallback to PIO mode > Oct 13 19:30:11 lowrider /kernel: ata1: resetting devices .. done > > My controller is: > > Oct 11 22:51:53 lowrider /kernel: atapci0: > port 0xf000-0xf00f at device 7.1 on pci0 > Oct 11 22:51:53 lowrider /kernel: ata0: at 0x1f0 irq 14 on atapci0 > Oct 11 22:51:53 lowrider /kernel: ata1: at 0x170 irq 15 on atapci0 > > and my disks are: > > Oct 11 22:51:54 lowrider /kernel: ad0: 5006MB > [10850/15/63] at ata0-master using UDMA33 > Oct 11 22:51:54 lowrider /kernel: ad2: 4134MB > [8960/15/63] at ata1-master using WDMA2 > Oct 11 22:51:54 lowrider /kernel: acd0: CDROM at ata0-slave using > PIO3 > > > The errors above occur during the dump of an fs, the creation of a large > tarball, or nightly run jobs that involve ad2. The actual disk in ad2 > came out of a 3.5-stable system that ran without these errors. The disk > appears to be fine, as I've put it back into the old system, and dumped > the /usr fs to a tarball on it. > > These errors don't appear to be affecting the end result, as the tarballs, > and dump files are still valid, but I'm wondering if these are cause for > concern. Or if I should add this to a PR? > > > -- > > | Andy | e-mail | web | > | | [EMAIL PROTECTED] | www.lewman.com | > > ... If forced to travel on an airplane, try and get in the cabin with > the Captain, so you can keep an eye on him and nudge him if he falls > asleep or point out any mountains looming up ahead ... > -- Mike Harding, "The Armchair Anarchist's Almanac" > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Dennis Melentyev C/C++ programmer @ Mebius-KB, Kiev, Ukraine [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
