Re: ZFS stalls -- and maybe we should be talking about defaults?
On Mar 5, 2013, at 11:09 PM, Jeremy Chadwick wrote: - Disks are GPT and are *partitioned, and ZFS refers to the partitions not the raw disk -- this matters (honest, it really does; the ZFS code handles things differently with raw disks) Not on FreeBSD as far I can see. My statement comes from here (first line in particular): http://lists.freebsd.org/pipermail/freebsd-questions/2013-January/248697.html If this is wrong/false, then this furthers my point about kernel folks who are in-the-know needing to chime in and help stop the misinformation. The rest of us are just end-users, often misinformed. As far as I know, this is lore than surfaces periodically in the lists. It was true in Solaris (at least in the past). But unless I'm terribly wrong, this doesn't happen in FreeBSD. ZFS sees disks, and they can be a whole raw device or a partition/slice, even a gnop device. No difference. That's why I mentioned in freebsd-fs that we badly need an official doctrine, carefully curated, and written in holy letters ;) Borja. ___ 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: Sanity Check on Mac Mini
On 03/07/13 17:18, Doug Hardie wrote: On 7 March 2013, at 11:57, Kevin Oberman rkober...@gmail.com wrote: On Thu, Mar 7, 2013 at 11:10 AM, Doug Hardie bc...@lafn.org wrote: On 7 March 2013, at 06:42, Richard Kuhns r...@wintek.com wrote: On 03/07/13 01:59, Doug Hardie wrote: I have a new Mac Mini and have encountered the same problem reported last year by Richard Kuhns. YongHyeon PYUN provided some patches to the kernel that resolved the problem. However, without an internet connection its a bit tricky to get them into the system. Here is the approach I believe will work, but wanted to check first before I really mess things up. 1. Downloaded from current today via svnweb.freebsd.org: sys/dev/bge/if_bgereg.h sys/dev/bge/if_bge.c sys/dev/mii/brgphy.c I believe the patches are incorporated in today's versions. The comments indicate such. Thus I don't need to apply the original supplied patch. 2. Put those on a flash drive. 3. Install 9.1 release from flash drive onto the Mini disk. Have to include the system source. 4. Copy the files from 1 above from flash over the files on the disk. 5. Rebuild the kernel and install it. Thanks, -- Doug That's worked for me 3 times now. Thanks. Well, I got 9.1 Release installed, but it won't boot from the internal disk. It doesn't see the disk as bootable. I installed using the entire disk for FreeBSD. I used the i386 release. Perhaps I need to switch to the amd64 release? I would generally recommend using the amd64 release, but it may not get your system to boot. How is your disk partitioned? GPT? Some BIOSes are broken and assume that a GPT formatted disk is UEFI and will not recognize them if they lack the UEFI boot partition. UEFI boot is a current project that seems likely to reach head in the fairly near future, but it's not possible now. No idea what the default partitioning is for BSDInstall. However the Mini is only EFI or UFEI with some fallbacks although the comments I find in the web indicate that different models have different fallbacks. One comment indicates that an older unit will boot if its MBR partitioning. I don't know if the new installer supports that or not. You may be able to tweak your BIOS to get it to work or you may have to install using the traditional partitioning system. The installer defaults to GPT, but can create either. I have such a system (ThinkPad T520) and I have two disks... one that came with the system and containing Windows, and my GPT formatted FreeBSD disk. I wrote a FreeBSD BootEasy boot into the MBR of the Windows disk and it CAN boot the GPT disk just fine. Not ideal for most, but it works well for me Based on a comment I say, waiting till the empty folder icon appears and then plugging in the install memstick causes the mini to boot from disk. That just downright weird, but it works. I could live with that, but this is an unattended server and would experience some down time if I am not there when there is a power failure. I just found some instructions for using MBR with bsdinstall, but given there is an effort to create a UEFI boot which I suspect would expect to find the GPT boot partition, perhaps I should just go with the memstick approach? -- Doug FWIW, here are the brief notes I made for what has been working for me for the last year or so; most recently with a new Mini purchased about 2 weeks ago. I'm using the entire drive for FreeBSD. Hit Option key while booting, then select 'Windows' USB image. Now trying GPT; looks fine, but will only boot with USB stick in place. If it's not there, just get a folder with a '?' when starting up. Using MBR; boots ok without USB stick. It just takes about 30 seconds before it actually boots. Select YES when asked about GMT. -- Richard Kuhns r...@wintek.com My Desk: 765-269-8541 Wintek Corporation Internet Support: 765-269-8503 427 N 6th Street Consulting: 765-269-8504 Lafayette, IN 47901-2211 Accounting: 765-269-8502 ___ 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: Strange reboot since 9.1
On Fri, Mar 08, 2013 at 11:32:54AM +0900, YongHyeon PYUN wrote: On Thu, Mar 07, 2013 at 08:38:27AM -0800, Jeremy Chadwick wrote: On Thu, Mar 07, 2013 at 04:38:54PM +0100, Lo?c Blot wrote: Hi Marcelo, thanks. Here is a better trace: - kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.11 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 amd64-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code= supervisor read data, page not present instruction pointer = 0x20:0x80a84414 stack pointer = 0x28:0xff822fc267a0 frame pointer = 0x28:0xff822fc26830 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (irq265: bce0) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x809208a6 at kdb_backtrace+0x66 #1 0x808ea8be at panic+0x1ce #2 0x80bd8240 at trap_fatal+0x290 #3 0x80bd857d at trap_pfault+0x1ed #4 0x80bd8b9e at trap+0x3ce #5 0x80bc315f at calltrap+0x8 #6 0x80a861d5 at udp_input+0x475 #7 0x80a043dc at ip_input+0xac #8 0x809adafb at netisr_dispatch_src+0x20b #9 0x809a35cd at ether_demux+0x14d #10 0x809a38a4 at ether_nh_input+0x1f4 #11 0x809adafb at netisr_dispatch_src+0x20b #12 0x80438fd7 at bce_intr+0x487 #13 0x808be8d4 at intr_event_execute_handlers+0x104 #14 0x808c0076 at ithread_loop+0xa6 #15 0x808bb9ef at fork_exit+0x11f #16 0x80bc368e at fork_trampoline+0xe Uptime: 27m20s Dumping 1265 out of 8162 MB:..2%..11%..21%..31%..41%..51%..61%..71%..81%..92% #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt f #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 No locals. #1 0x808ea3a1 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 _ep = Variable _ep is not available. (kgdb) bt #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808ea3a1 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #2 0x808ea897 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #3 0x80bd8240 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #4 0x80bd857d in trap_pfault (frame=0xff822fc266f0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:773 #5 0x80bd8b9e in trap (frame=0xff822fc266f0) at /usr/src/sys/amd64/amd64/trap.c:456 #6 0x80bc315f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x80a84414 in udp_append (inp=0xfe019e2a1000, ip=0xfe00444b6c80, n=0xfe00444b6c00, off=20, udp_in=0xff822fc268a0) at /usr/src/sys/netinet/udp_usrreq.c:252 #8 0x80a861d5 in udp_input (m=0xfe00444b6c00, off=Variable off is not available. ) at /usr/src/sys/netinet/udp_usrreq.c:618 #9 0x80a043dc in ip_input (m=0xfe00444b6c00) at /usr/src/sys/netinet/ip_input.c:760 #10 0x809adafb in netisr_dispatch_src (proto=1, source=Variable source is not available. ) at /usr/src/sys/net/netisr.c:1013 #11 0x809a35cd in ether_demux (ifp=0xfe00053fa000, m=0xfe00444b6c00) at /usr/src/sys/net/if_ethersubr.c:940 #12 0x809a38a4 in ether_nh_input (m=Variable m is not available. ) at /usr/src/sys/net/if_ethersubr.c:759 #13 0x809adafb in netisr_dispatch_src (proto=9, source=Variable source is not available. ) at /usr/src/sys/net/netisr.c:1013 #14 0x80438fd7 in bce_intr (xsc=Variable xsc is not available. ) at /usr/src/sys/dev/bce/if_bce.c:6903 #15 0x808be8d4 in intr_event_execute_handlers (p=Variable p is not available. ) at /usr/src/sys/kern/kern_intr.c:1262 #16 0x808c0076 in ithread_loop (arg=0xfe00057424e0) at /usr/src/sys/kern/kern_intr.c:1275 #17 0x808bb9ef in fork_exit (callout=0x808bffd0 ithread_loop, arg=0xfe00057424e0,
Re: Sanity Check on Mac Mini
On 7 March 2013, at 17:00, John Mehr j...@visi.com wrote: On Thu, 7 Mar 2013 14:18:23 -0800 Doug Hardie bc...@lafn.org wrote: On 7 March 2013, at 11:57, Kevin Oberman rkober...@gmail.com wrote: On Thu, Mar 7, 2013 at 11:10 AM, Doug Hardie bc...@lafn.org wrote: On 7 March 2013, at 06:42, Richard Kuhns r...@wintek.com wrote: On 03/07/13 01:59, Doug Hardie wrote: I have a new Mac Mini and have encountered the same problem reported last year by Richard Kuhns. YongHyeon PYUN provided some patches to the kernel that resolved the problem. However, without an internet connection its a bit tricky to get them into the system. Here is the approach I believe will work, but wanted to check first before I really mess things up. 1. Downloaded from current today via svnweb.freebsd.org: sys/dev/bge/if_bgereg.h sys/dev/bge/if_bge.c sys/dev/mii/brgphy.c I believe the patches are incorporated in today's versions. The comments indicate such. Thus I don't need to apply the original supplied patch. 2. Put those on a flash drive. 3. Install 9.1 release from flash drive onto the Mini disk. Have to include the system source. 4. Copy the files from 1 above from flash over the files on the disk. 5. Rebuild the kernel and install it. Thanks, -- Doug That's worked for me 3 times now. Thanks. Well, I got 9.1 Release installed, but it won't boot from the internal disk. It doesn't see the disk as bootable. I installed using the entire disk for FreeBSD. I used the i386 release. Perhaps I need to switch to the amd64 release? I would generally recommend using the amd64 release, but it may not get your system to boot. How is your disk partitioned? GPT? Some BIOSes are broken and assume that a GPT formatted disk is UEFI and will not recognize them if they lack the UEFI boot partition. UEFI boot is a current project that seems likely to reach head in the fairly near future, but it's not possible now. No idea what the default partitioning is for BSDInstall. However the Mini is only EFI or UFEI with some fallbacks although the comments I find in the web indicate that different models have different fallbacks. One comment indicates that an older unit will boot if its MBR partitioning. I don't know if the new installer supports that or not. You may be able to tweak your BIOS to get it to work or you may have to install using the traditional partitioning system. The installer defaults to GPT, but can create either. I have such a system (ThinkPad T520) and I have two disks... one that came with the system and containing Windows, and my GPT formatted FreeBSD disk. I wrote a FreeBSD BootEasy boot into the MBR of the Windows disk and it CAN boot the GPT disk just fine. Not ideal for most, but it works well for me Based on a comment I say, waiting till the empty folder icon appears and then plugging in the install memstick causes the mini to boot from disk. That just downright weird, but it works. I could live with that, but this is an unattended server and would experience some down time if I am not there when there is a power failure. I just found some instructions for using MBR with bsdinstall, but given there is an effort to create a UEFI boot which I suspect would expect to find the GPT boot partition, perhaps I should just go with the memstick approach? Hello, If you still have a drive with OS X on it, you may have some luck with OS X's bless command: https://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/bless.8.html I got a late 2012 mac mini to boot FreeBSD 9.1 (AMD64) from a hard drive using 'bless' (unfortunately I don't remember the exact command line parameters I used). If you're looking to dual boot, the only luck I had (without resorting to using third party software like rEFIt) was to put the OS's on different drives and install FreeBSD using MBR on the second drive. I have investigated the bless command and nothing I find on google gives me any good ideal on what folder/file to bless. I am wondering if just using the volume command and ignoring folder and file would work? ___ 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: Sanity Check on Mac Mini
I have investigated the bless command and nothing I find on google gives me any good ideal on what folder/file to bless. I am wondering if just using the volume command and ignoring folder and file would work? Hello, If memory serves, I used it in device mode and used the --setBoot option to select the bootable FreeBSD partition. I was trying to find a dual boot solution at the time and I remember giving up on the bless command when it booted me straight into FreeBSD. I wish I could remember more... ___ 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
