Re: 6.2 ETA
It may be a bit early but I switched to RELENG_6 fot that reason. After I switched, it seems the number of interrupts increased a lot. When I do 'dump -0 -f - -L /somewhere | restore -r -f', I see hight interrupt rates which I don't remember seeing in 6.1-RELEASE. Is it too early to report incidents? Hiro On Wed, 30 Aug 2006 07:36:51 -0700 Colin Percival [EMAIL PROTECTED] wrote: Bryan Fullerton wrote: So... the releng web page indicates that RELENG_6 is frozen as of August 25th pending a 6.2R release on October 9th. I'm guessing, since there seem to still be lots of commits and there's no /releases/6.2R/ doc tree on the FreeBSD site, that these dates are no longer accurate. What is a valid ETA for starting the 6.2R releng process? I'm not part of the release engineering team, but I'm not aware of anything which they're waiting for before starting the freeze. I'd be surprised if RELENG_6 isn't frozen by this time next week. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2? (fwd)
On Wed, 13 Sep 2006 13:07:20 +0200 (CEST) kama [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Oliver Fromme wrote: That's true, and the schedule will most probably change. Currently the release is listed for Oct. 9th, but I bet that it'll be delayed. I disagree, I would like to have an notice about it. Even though it might not say much. Just a The code of the stable branch has been freezed due to the upcomming release of X.Y I agree with Kama. I specificly switched once to stable for pre-release testing purpose. I saw email from one of the developers claiming that not many people join pre-release testing. (I do not remember whether it was not many people join BETA testing or RC testing. Anyway, I saw it in one of the quota issue e-mail chain on 6.1-RELEASE.) If we are not in such a stage, I personally prefer to stick with releases. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4.x EoL
On Wed, 18 Oct 2006 12:13:11 +0100 (BST) Jan Grant [EMAIL PROTECTED] wrote: If you're setting up machines that you're going to be upgrading like this in the future, I think it's _really_ worthwhile hacking out a couple of root slices - that is, space for a second / and /usr - to facilitate this. You can run mergemaster on a secondary copy of your /etc (this, of course, requries that the contents of /etc are relatively quiescent for this step) and tidy up by hand. You can perform a dump restore followed by a source upgrade, a fresh source install or a binary upgrade ad lib; just reboot (with nextboot) when done. This also means you can keep the previous OS around for a while in case there are problems with the new one. For setups that aren't amenable to automated deployments this works pretty well and gives you a safety-net for upgrades. Good advice. I have a few additions. In fact, you don't need *a* partitions to boot such as ad0s1a. You simply need to spare a FreeBSD partition. At boot loader, you could type: ad(0,2,e) to boot e partition of the 2nd slice on the first drive which is denoted by 0. ad(2,2,f) to boot from f partition of the 2nd slice on the 3rd drive. If you have lots of physical memory and swap space, you may be able to spare swap space for this porpuse for a moment. In another word, you can disable swap device for a while and use it as a root parition. Regards, Hiro ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portaudit
On Sun, 22 Oct 2006 20:03:55 +0200 Miroslav Lachman [EMAIL PROTECTED] wrote: gareth wrote: There are more than one way to install vulnerable port. Sometimes DISABLE_VULNERABILITIES=yes may be enough. Hello. What are other ways? I want to see vulnerable message but still want to install without portupgrade being interrupted. According to /usr/ports/Mk/bsd.port.mk, DISABLE_VULNERABILITIES=yes disables vulnerable check, don't it? Thanks, Hiro ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: out of memory in restore?
I think you have to extend your user space memory by adding the following to /boot/loader.conf. If 5.4-RELEASE doesn't support these options, adjust your kernel. kern.maxdsiz=2048m kern.maxssiz=1024m Hiro On Tue, 24 Oct 2006 10:08:01 +0400 Alex Povolotsky [EMAIL PROTECTED] wrote: Hello! I've tried an interactive restore from a dump, and glob fails, so restore fails with out of memory. Is my dump useless now? (dumped and tried to restore under 5.4-RELEASE) Alex. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Migrating from x86 (32) to amd64
About one year ago, I was able to do the regular procedure after enabling i386 compat. It was just another make world for me. options COMPAT_IA32 What I mean is: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster' # 10. `reboot' There are some risks doing this way, though. Regards, Hiro On Sat, 10 Mar 2007 00:24:51 -0600 Matthew D. Fuller [EMAIL PROTECTED] wrote: On Fri, Mar 09, 2007 at 08:54:42PM +0300 I heard the voice of Artem Kuchin, and lo! it spake thus: Theoretically, what would be the procedure? - Do a full cross-build of the amd64 world/kernel. - newfs your swap partition (or an extra partition/drive). - installworld/kernel the amd64 stuff onto that. - Boot into that temporary amd64 world. - installworld/kernel the amd64 stuff onto your main partition. - Boot back normal-like, re-enable swap. You should be able to do that in an hour hands-on easily. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Migrating from x86 (32) to amd64
On Sat, 10 Mar 2007 13:57:09 +0200 Danny Braniss [EMAIL PROTECTED] wrote: Yoshihiro Ota wrote: About one year ago, I was able to do the regular procedure after enabling i386 compat. It was just another make world for me. options COMPAT_IA32 What I mean is: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=3DYOUR_KERNEL_HERE' (default is GENERIC). But if you already have an i386 kernel running, wouldn't running make buildkernel just make another i386 kernel? try make buildkernel TARGET_ARCH=amd64 KERNCONF=YOUR_KERNEL_HERE works for me, danny I believe I have done with TARGET_ARCH=amd64 or something on the line. As I've done it about a year ago, I don't recall some of these details. After a couple of months, I decided to switch back to i386. It was just to experiment amd64. I share the same executables among multiple systems (although there are only 2 or 3) to sync software versions. (It is not often but having diffrent versions of the same software causes some problems.) Since I have i386 machines, I cannot share amd64 binraries. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumping large partition to USB drive fails
It's probabry your disk is dying based on your output. I've being using GELI for while, i.e. like a year, with dump/resotre, too. I never had problems with dump/restore. My disk also failed recently with very similer messages. Hiro On Mon, 25 Jun 2007 19:40:45 +0200 Roland Smith [EMAIL PROTECTED] wrote: Some background; I'm using a 160GB USB harddisk to write dumps to. This disk is encrypted with GEOM_ELI; umass0: Prolific Technology Inc. Mass Storage Device, rev 2.00/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: WDC WD25 00JB-00REA0 20.0 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) GEOM_ELI: Device da0.eli created. GEOM_ELI: Encryption: AES-CBC 256 GEOM_ELI: Crypto: software Since I've converted my largest partition (/home) to GEOM_ELI as well, I'm having trouble making backups. slackbox:~$ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a496M 88M368M19%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g.eli120G 65G 46G59%/home /dev/ar0s1e496M 24K456M 0%/tmp /dev/ar0s1f 19G4.5G 13G25%/usr /dev/ar0s1d1.9G147M1.6G 8%/var /dev/da0.eli 226G100G107G48%/mnt/root Backing up non-encrypted partitions like /, /usr and /var works fine. But when I get to /home, the following happens; (da0:umass-sim0:0:0:0): AutoSense Failed GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165967687 68, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165968998 40, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165970309 12, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165971619 84, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165972930 56, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165974241 28, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165975552 00, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165976862 72, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165966376 96, length=131072)] g_vfs_done():da0.eli[WRITE(offset=116596768768, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116596899840, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597030912, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597161984, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597293056, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597424128, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597555200, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116597686272, length=131072)]error = 5 g_vfs_done():da0.eli[WRITE(offset=116596637696, length=131072)]error = 5 GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=65536, len gth=2048)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=6144000, l ength=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=6160384, l ength=6144)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1161638707 20, length=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1163565137 92, length=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165491568 64, length=16384)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165979484 16, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165980794 88, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165982105 60, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165983416 32, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165984727 04, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165984727 04, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165986037 76, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165987348 48, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165988659 20, length=131072)] GEOM_ELI: Crypto WRITE request failed (error=5). da0.eli[WRITE(offset=1165978173 44, length=131072)] g_vfs_done():da0.eli[WRITE(offset=65536, length=2048)]error = 5 g_vfs_done():da0.eli[WRITE(offset=6144000, length=16384)]error = 5
Re: Broken loader on 7.1-STABLE?
On Sun, 08 Feb 2009 17:05:04 +1300 Mark Kirkwood mar...@paradise.net.nz wrote: Mark Kirkwood wrote: I wrote: I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and I have: panic: free: guard1 fail @ 0x511d from /usr/src/sys/boot/i386/loader/../../common/module.c:959 Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0 I am experiencing same error. In my case, I cannot boot from anything other than /boot/kernel. While my /boot/kernel is bootable, I do cp -pr /boot/kernel /boot/kernel.ok. Then, it fails like the error message above. After I do mv /boot/kernel.ok /boot/kernel, it boots fine. My environment is HP pavilion dv6425 with FreeBSD 7.1. I think I started noticing this since 7.1-RC. Regards, Hiro ___ 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: unionfs panic in 7.1
On Sat, 21 Feb 2009 18:35:16 +0900 Daichi GOTO dai...@freebsd.org wrote: Steve Wills wrote: Hi, I've found an reproducable panic in unionfs on 7.1-R. /usr/src/sys/fs/unionfs/union_subr.c is: $FreeBSD: src/sys/fs/unionfs/union_subr.c,v 1.92.2.7.2.2 2008/12/15 03:58:55 daichi Exp $ kgdb output is below. I reproduce this by unionfs mounting a ports dir used by the ports tinderbox. If anyone would like more info, please let me know, I have the core around, and can reproduce, help debug, resend in case my mailer has mangled this, etc. I have some research around that issue. First I should say, I cannot judge that unionfs leads that problem or not. JIMO, I guess that is not depends on unionfs itself. Very similar panis is reported without unionfs. At least, I cannot figure out what is the main cause of this problem. sorry. I wonder if it is one of LORs, http://sources.zabbadoz.net/freebsd/lor.html If you can try on 8-CURRENT and reproduce, it may provide you better info. Regards, Hiro ___ 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
Question about disk schedulers
Hi, Luigi and Fabio: I have a question about the GEOM disk scheduler you announed a while ago. http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047597.html Can you tell me how does the scheduler interact with gjournal? Do you expect to improve response time even if used together with gjounral or to interfere each other? As I only had a journaled partition available for an experiment, I tried this combination on 7.1-RELEASE but it paniced 4 times out of 5 at attempts as soon as I mounted. Thanks, Hiro ___ 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: ZFS root File System
On Fri, 27 Feb 2009 19:21:15 -0800 (PST) Matthew Dillon dil...@apollo.backplane.com wrote: My experience with one of our people trying to do the same thing w/ HAMMER... we got it working, but it is not necessarily cleaner. Does that mean someone ported HAMMER to FreeBSD or someone did it on DragonFlyBSD? Thanks, Hiro ___ 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
Where is nfsiod now?
Hello. I thought rc used to start nfsiod if you set nfs_cilent_enable back years ago. Now, on my 7.1-RELEASE machine, it sets up a couple of sysctls in /etc/rc.d/nfsclient script but not nfsiod. Is nfsiod obsolete by now? It is still on the system; does it still improve nfs performance? Thanks, Hiro ___ 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: dump | restore fails: unknown tape header type 1853384566
On Tue, 24 Mar 2009 02:30:37 -0400 Mikhail T. mi+t...@aldan.algebra.com wrote: Daniel O'Connor написав(ла): On Tuesday 24 March 2009 11:55:07 Mikhail T. wrote: I'm trying to migrate a filesystem from one disk to another using: dump a0hCf 0 32 - /old | restore -rf - (/old is already mounted read-only). The process runs for a while and then stops with: [...] DUMP: 22.85% done, finished in 3:57 at Tue Mar 24 01:03:21 2009 DUMP: 24.66% done, finished in 3:50 at Tue Mar 24 01:00:58 2009 DUMP: 26.44% done, finished in 3:43 at Tue Mar 24 00:59:14 2009 unknown tape header type 1853384566 abort? [yn] Any idea, what's going on? Why can't FreeBSD's restore read FreeBSD's dump's output? What happens if you don't use the cache? No big difference: dump a0f - /old | restore -rf - [...] DUMP: 17.25% done, finished in 3:27 at Tue Mar 24 05:42:00 2009 DUMP: 20.36% done, finished in 3:09 at Tue Mar 24 05:28:13 2009 DUMP: 23.83% done, finished in 2:50 at Tue Mar 24 05:14:32 2009 unknown tape header type -621260722 abort? [yn] Looks like a junk value somewhere... Unitialized variable or some such. -mi -a option seems to be the problem. Try without it. Hiro ___ 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
7-BETA4/7-RC1 crashes randomly at shutdown
Hello. I have been following RELENG_7 and then RELENG_7_0. I update /usr/src daily and install them. I think the crash started around 12/18. Since then, I started seen pancing at umount during shutdown. I am using GENERIC kernel with SCHED_ULE. This crash tends to happen after some amount of I/O performed. I cannot really tell what kind of I/O will trigger this umount failure, yet. I got a core and 'where' command. Does anyone have any ideas or suggestions? Thanks, Hiro # kgdb /usr/obj/usr/src/sys/GENERIC/kernel.debug /var/crash/vmcore.3 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. Unread portion of the kernel message buffer: 118/etc/rc.shutdown: WARNING: $samba_enable is not set properly - see rc.conf(5). 118Writing entropy file: 118. 118. 118Dec 26 01:11:56 XX syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Wait iSnygn c(imnagx dis60k s,s evcnoonddess) rfeomra isynsitneg.m. .p3r ocess `syncer' to stop...3 3 1 1 1 1 0 0 0 0 done All buffers synced. GEOM_ELI: Detached da0.eli on last close. acpi_ec0: warning: EC done before starting event wait GEOM_ELI: Detached ad4s2f.eli on last close. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07479d4 stack pointer = 0x28:0xe3c71b1c frame pointer = 0x28:0xe3c71b34 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1 (init) trap number = 12 panic: page fault cpuid = 0 Uptime: 1h24m11s Physical memory: 2025 MB Dumping 155 MB: 140 124 108 92 76 60 44 28 12 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:195 #1 0xc0753e87 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0754149 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a689ec in trap_fatal (frame=0xe3c71adc, eva=392) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a68c70 in trap_pfault (frame=0xe3c71adc, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a6961c in trap (frame=0xe3c71adc) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a4f5ab in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc07479d4 in _mtx_lock_sleep (m=0xc8abfa18, tid=3306133088, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:335 #8 0xc07cc94f in vgone (vp=0xc8abf990) at /usr/src/sys/kern/vfs_subr.c:2471 #9 0xc5742a79 in ?? () #10 0xc8abf990 in ?? () #11 0xc55a9a70 in ?? () #12 0x in ?? () #13 0xc5743c20 in ?? () #14 0x016c in ?? () #15 0xc5746074 in ?? () #16 0x3002 in ?? () #17 0xc8abf990 in ?? () #18 0xe3c71bf0 in ?? () #19 0x0004 in ?? () ---Type return to continue, or q return to quit--- #20 0xc50f9660 in ?? () #21 0xe3c71ba8 in ?? () #22 0xc57420b4 in ?? () #23 0xc55a9a70 in ?? () #24 0xc5746000 in ?? () #25 0x1002 in ?? () #26 0xe3c71bf0 in ?? () #27 0xc50f9660 in ?? () #28 0xc569d550 in ?? () #29 0xe3c71c00 in ?? () #30 0xc07c6ac1 in dounmount (mp=0xc55a9a70, flags=-982228992, td=0x10) at /usr/src/sys/kern/vfs_mount.c:1270 Previous frame inner to this frame (corrupt stack?) (kgdb) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PR backlog
On Thu, 27 Dec 2007 09:43:08 +0100 (CET) Remko Lodder [EMAIL PROTECTED] wrote: Hello Warner et all, On Wed, December 26, 2007 7:42 pm, M. Warner Losh wrote: Mark and Henrik make a number of good points here. Rather than reply to the details, I'm going to make a couple of quick observations. As a project we're not leveraging the community sufficiently when it comes to contributions. The current system of patch review and submission is very hap-hazard. If you happen to get the attention of the right person at the right time, then it goes in. If not, patches can languish a long time in the PR system. Indeed, I am one of the persons trying to find these relatively easy things which I can do along side my other projects and things, but I dont see them all (eventhough I try to keep track of them as much as possible); but what will happen is that I learn more and more about the system and at some point in time I will stop working on these easy PR's and seeking more difficult ones to fix, at that point someone else has to step up to fill in the gap that gets created; this might be a problematic part :-) Though for everyone having simple fixes, please send them to me so that I can evaluate them and (together with Warner in this case (As my mentor)) I will try to get them in as correctly and quickly as possible :-) (keeping up with the high standards of FreeBSD ofcourse). I also opened the PR database a couple weeks ago looking for a solution to bugs I encountered. It's been quite long, some years, since I opened the PR page last time. It was surprising and also disappointing on the number of PRs left open for long time. How do I help that cleaning job? I am also interested fixing and concerned about this fact. Thanks, Hiro ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with gmirror on ggate over slow link
I think you hit the same bug as I did a while ago. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/132798 You can get a patch at PR and give a try. Make sure you update both server and client; otherwise, it will cause a panic or so. Hiro On Tue, 03 Nov 2009 16:23:24 + Pete French petefre...@ticketswitch.com wrote: Have you done any sockets tuning? In an older posting the following values were recommended: Yes, I need that to get the speed out of it for normal use to a disc on a machine on the same ether - but even so, surely it should block on a slow disc, not just abandon the mirroring ? -pete. ___ 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 ___ 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
ZFS WARNING: Cannot open ad4s3d for writting; how do I clear it?
Hi, I have running FreeBSD 7.1-RELEASE-p14. I had had a ZFS partition as one of data area on a system and replicated a system using dump/restore. On the replicated system, I don't use ZFS and ad4s3d is mounted as /usr. I get ZFS WARNING: Cannot open ad4s3d for writting. each time I run zfs import on relicated system. How can I clear this meta-data information ZFS carries? Thanks, Hiro ___ 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
ndis wireless on 11.0-RELESE has been broken and its patch
Hi, I've been chasing a NDIS wireless bug for a while as I realized network stopped working on some of hardware. I have its PR and also attached a patch. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213237 It will be nice if someone can follow up so that we can have 11.1-RELEASE NDIS wireless working. Regards, Hiro On Tue, 3 Jan 2017 23:40:48 -0500 Yoshihiro Ota <o...@j.email.ne.jp> wrote: > Hi Gleb, > > Are you still accepting a bug report on this? > I have a laptop that I need to use NDIS driver. > This change impacted and causes kernel panic. > I haven't used this laptop for a quite while and > didn't realize it had stopped working. > > When I setup a wlan0 device with NDIS in wepmode, > "ifconfig wlan0 up" causes kernel memory currupption > and causes next ioctl/sysctl access programs such > as "ps" and "sysctl -a" crash the kernel. > > Regards, > Hiro > > On Fri, 31 Jul 2015 15:12:26 +0300 > Gleb Smirnoff <gleb...@freebsd.org> wrote: > > > Hi! > > > > I need to make couple of non-functional but rather large changes > > to the if_ndis driver and will appreciate if anyone signs up to > > test my changes. Please contact me if you can provide help. > > > > -- > > Totus tuus, Glebius. > > ___ > > freebsd-curr...@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ > freebsd-curr...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.0-RELEASE-p4 i386/PAE kernel spins
Hi, I'm attaching to this thread as I think my problem started happening after the SA updates. I saw 3 suspicious spins with i386/PAE kernel since I updated on May 15th/16th. I boot FreeBSD 12.0-RELEASES i386/PAE once per a day and shutdown each time and use BSD everyday. I start with console and decide whether I want to use X or not and if so, I run startx. In the past, startx didn't come up twice in 30 seconds or so and console wasn't responding. Both times, I wasn't able to monitor system and gave up - hard reset. I had another and similar symptom. This time, I had ran X for a while. I started moving about 2 of 100MB files from tmpfs to zfs, I started seeing system lagging and also high CPU usage by kernel and syncer by top. Ctrl-T on mv printed "runnable" and "running" a lot while "systat -vm" wasn't showing any IO activities. After a minute or longer, system came back to normal. I haven't run non-PAE kernel as much, once or twice since the SA. I don't know if this issue is PAE kernel only. I definitely hadn't seen before the SA. Hiro On Wed, 15 May 2019 00:35:07 -0400 Ed Maste wrote: > On Wed, 15 May 2019 at 00:03, Ed Maste wrote: > > > > On Wed, 15 May 2019 at 15:09, wintellect Auser > > wrote: > > > > > > Hi all, > > > > > > Wanted to make you aware of an issue I have encountered, sorry if this is > > > the wrong list. > > > > This is the right place and thank you for reporting. Looking into it. > > It looks like a new update for 12.0 i386 will be needed and will be > rolled out as soon as possible. > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD dual boot on Chromebook
Hi, What's the latest with Chromebook and FreeBSD dual boot? I found more documents on ARM Chromebook but it looks there are i386 based Chromebooks are also sold, too. Is Chromebook good or recommended to dual boot with FreeBSD? Thanks, Hiro ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
12.1-PRE-RELEASE, 352114 is ok but 352202 is bad
Hi, After updating from 352114 to 352202 on 12/stable, 12.1-PRE-RELEASE, my kernel stopped booting. This one runs on Parallels VM. Looking at boot message, I seeswap init is passed. Then, after printing the following 2 lines, it doesn't proceed further. uhub0: 2 ports with 2 removables, self powered uhub1: 15 ports with 15 removables, self powered As 13-CURRENT with the last night's code boots okay, I suspect some merge error to the branch. Hiro ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.1-PRE-RELEASE, 352114 is ok but 352202 is bad
Thanks for replays (including personal ones). Next svn up picked up and I booted ok. Regards, Hiro On Thu, 12 Sep 2019 06:03:53 -0700 John Kennedy wrote: > On Wed, Sep 11, 2019 at 11:46:14PM -0400, Yoshihiro Ota wrote: > > After updating from 352114 to 352202 on 12/stable, 12.1-PRE-RELEASE, my > > kernel stopped booting. > > ... This one runs on Parallels VM. ... > > As 13-CURRENT with the last night's code boots okay, I suspect some merge > > error to the branch. > > There was a bug (240487) yesterday that was present from r352179 up to > r352217 which is literally the patch after r352202 as it landed in 12-stable. > > This booted for me: > > FreeBSD 12.1-PRERELEASE #106 r352217+0e6a9a9426c7(stable/12) > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
"dhclient: send_packet: No buffer space available"
Hi, I recently switched internet service provider and got much faster connection. However, I started seeing some unstable connections between the WiFi router and FreeBSD. I was on FreeBSD 12.0-RELEASE and switched to 12.1-RELEASE. Both versions have same symptoms. I get "dhclient: send_packet: No buffer space available" to console and then I frequently lose connection after seeing it. After taking the wlan down and re-connect it with wpa_supplicant, I usually get a connection back. On the side note, I also see these outputs to console and syslog: ath0: bb hang detected (0x4), resetting ath0: ath_legacy_rx_tasklet: sc_inreset_cnt > 0; skipping Does anyone have any advice how to fix/work-around or where to start looking: ath driver, dhclinet, kernel, wlan, and/or wpa_supplicant? Thanks, Hiro ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kldload zfs spins the system after upgrading from 12.2 to 13-BETA
On Tue, 9 Mar 2021 11:24:53 +0200 Andriy Gapon wrote: > On 08/03/2021 05:24, Yoshihiro Ota wrote: > > On Sun, 7 Mar 2021 00:09:33 +0200 > > Andriy Gapon wrote: > > > >> On 06/03/2021 20:09, Yoshihiro Ota wrote: > >>> Hi all, > >>> > >>> I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one. > >>> > >>> After upgrading one in VMWare, 'zfs mount -a' hangs the system. > >>> I don't have boottime zfs mount on nor don't have zfsroot. > >>> I just simply ran install world/kernel and mergemaster. > >> > >> Please use procstat -kk to capture a kernel stack trace of the hung > >> process. > > > > Actually, spining was 'kldload zfs'. > > Console doesn't response but ping and sshd sessions still work. > > procstat output is below. > > In addition, this doesn't happen to systems that I've been following > > 13-CURRENT > > but rather happen only wiht a system upgraded from 12.2-RELEASE to 13-RC. > > > > > > # procstat -kk 1049 > > PIDTID COMMTDNAME KSTACK > > > > 1049 100215 kldload - spa_init+0xc6 > > zfs_kmod_init+0x1a > > zfs_modevent+0x34 module_register_init+0x8c linker_load_module+0xaab > > kern_kldload+0xc1 > > sys_kldload+0x50 syscall+0x17d g_ctx+0xe280bf29 > > > > If you could use kgdb to find out what source code line spa_init+0xc6 > corresponds to that may help to see what's going on. Hi Andriy, Could you teach me what command can show such address in kgdb? Thanks, Hiro ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kldload zfs spins the system after upgrading from 12.2 to 13-BETA
On Tue, 9 Mar 2021 11:24:53 +0200
Andriy Gapon wrote:
> On 08/03/2021 05:24, Yoshihiro Ota wrote:
> > On Sun, 7 Mar 2021 00:09:33 +0200
> > Andriy Gapon wrote:
> >
> >> On 06/03/2021 20:09, Yoshihiro Ota wrote:
> >>> Hi all,
> >>>
> >>> I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one.
> >>>
> >>> After upgrading one in VMWare, 'zfs mount -a' hangs the system.
> >>> I don't have boottime zfs mount on nor don't have zfsroot.
> >>> I just simply ran install world/kernel and mergemaster.
> >>
> >> Please use procstat -kk to capture a kernel stack trace of the hung
> >> process.
> >
> > Actually, spining was 'kldload zfs'.
> > Console doesn't response but ping and sshd sessions still work.
> > procstat output is below.
> > In addition, this doesn't happen to systems that I've been following
> > 13-CURRENT
> > but rather happen only wiht a system upgraded from 12.2-RELEASE to 13-RC.
> >
> >
> > # procstat -kk 1049
> > PIDTID COMMTDNAME KSTACK
> >
> > 1049 100215 kldload - spa_init+0xc6
> > zfs_kmod_init+0x1a
> > zfs_modevent+0x34 module_register_init+0x8c linker_load_module+0xaab
> > kern_kldload+0xc1
> > sys_kldload+0x50 syscall+0x17d g_ctx+0xe280bf29
> >
>
> If you could use kgdb to find out what source code line spa_init+0xc6
> corresponds to that may help to see what's going on.
>
It look me a while to get kgdb working properly.
At last, I got the output.
It looks it is spining on a mutex.
I have few other machines run the same kernel but they can load zfs.ko.
It is only vmware VM that spins with 'kldload zfs'.
vmware# kgdb101 /usr/usr/lib/debug/boot/kernel/zfs.ko.debug
GNU gdb (GDB) 10.1 [GDB v10.1 for FreeBSD]
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd13.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "helpType "apropos word" to search for commands related to
"word"...
Reading symbols from zfs.ko.debug...
(kgdb) info line *spa_init+0xc6
Line 2345 of "/usr/src/sys/contrib/openzfs/module/zfs/spa_misc.c"
starts at address 0x2b0461
and ends at 0x2b0467 .
(kgdb)
void
spa_init(spa_mode_t mode)
{
mutex_init(_namespace_lock, NULL, MUTEX_DEFAULT, NULL);
mutex_init(_spare_lock, NULL, MUTEX_DEFAULT, NULL); // <- line 2345
Hiro
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
zfs mount -a spins the system after upgrading from 12.2 to 13-BETA
Hi all, I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one. After upgrading one in VMWare, 'zfs mount -a' hangs the system. I don't have boottime zfs mount on nor don't have zfsroot. I just simply ran install world/kernel and mergemaster. Are there any special steps we need to take before upgrading? Thanks, Hiro ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kldload zfs spins the system after upgrading from 12.2 to 13-BETA
On Sun, 7 Mar 2021 00:09:33 +0200 Andriy Gapon wrote: > On 06/03/2021 20:09, Yoshihiro Ota wrote: > > Hi all, > > > > I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one. > > > > After upgrading one in VMWare, 'zfs mount -a' hangs the system. > > I don't have boottime zfs mount on nor don't have zfsroot. > > I just simply ran install world/kernel and mergemaster. > > Please use procstat -kk to capture a kernel stack trace of the hung process. Actually, spining was 'kldload zfs'. Console doesn't response but ping and sshd sessions still work. procstat output is below. In addition, this doesn't happen to systems that I've been following 13-CURRENT but rather happen only wiht a system upgraded from 12.2-RELEASE to 13-RC. # procstat -kk 1049 PIDTID COMMTDNAME KSTACK 1049 100215 kldload - spa_init+0xc6 zfs_kmod_init+0x1a zfs_modevent+0x34 module_register_init+0x8c linker_load_module+0xaab kern_kldload+0xc1 sys_kldload+0x50 syscall+0x17d g_ctx+0xe280bf29 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 13.0-BETA3 Now Available
Hi, tmp/legacy/usr/bin/make fails to run when sharing /usr/obj built on 13-BETA* to 12.2-RELEASE machines. I entered https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253727 Hiro On Sat, 20 Feb 2021 20:39:50 + Glen Barber wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The third BETA build of the 13.0-RELEASE release cycle is now available. > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
