Re: ZFS import panic with r219703
17.03.2011 01:03, Freddie Cash wrote: Anytime I try to import my pool built using 24x HAST devices, I get the following message, and the system reboots: panic: solaris assert: dmu_free_range(os, smo->smo_object, 0, -1ULL, tx) == 0, file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/space_map.c, line: 484 Everything runs nicely if I don't import the pool. Doing a "zpool import" shows that one of the HAST devices is FAULTED "corrupted data". Haven't tried anything to remove/replace the faulted device, just wanted to see if anyone knew what the above error meant. Pool was created using r219523 and successfully copied over 1 TB of data from another ZFS system. Had some issues with gptboot this morning and the system locking up and rebooting a bunch, and now the pool won't import. Oh, the garbled space_map issue. The system will assert any time the pool is imported in r/w. ZFSv28 is able to import pool in r/o state and this is as far as I know the only way to recover data from such pool. Anyway pool should be recreated. -- Sphinx of black quartz judge my vow. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on i386/pc98
TB --- 2011-03-17 01:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-17 01:00:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2011-03-17 01:00:00 - cleaning the object tree TB --- 2011-03-17 01:00:18 - cvsupping the source tree TB --- 2011-03-17 01:00:18 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2011-03-17 01:00:49 - building world TB --- 2011-03-17 01:00:49 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-17 01:00:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-17 01:00:49 - TARGET=pc98 TB --- 2011-03-17 01:00:49 - TARGET_ARCH=i386 TB --- 2011-03-17 01:00:49 - TZ=UTC TB --- 2011-03-17 01:00:49 - __MAKE_CONF=/dev/null TB --- 2011-03-17 01:00:49 - cd /src TB --- 2011-03-17 01:00:49 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 17 01:00:49 UTC 2011 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Mar 17 02:51:35 UTC 2011 TB --- 2011-03-17 02:51:36 - generating LINT kernel config TB --- 2011-03-17 02:51:36 - cd /src/sys/pc98/conf TB --- 2011-03-17 02:51:36 - /usr/bin/make -B LINT TB --- 2011-03-17 02:51:36 - building LINT kernel TB --- 2011-03-17 02:51:36 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-17 02:51:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-17 02:51:36 - TARGET=pc98 TB --- 2011-03-17 02:51:36 - TARGET_ARCH=i386 TB --- 2011-03-17 02:51:36 - TZ=UTC TB --- 2011-03-17 02:51:36 - __MAKE_CONF=/dev/null TB --- 2011-03-17 02:51:36 - cd /src TB --- 2011-03-17 02:51:36 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Mar 17 02:51:36 UTC 2011 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Thu Mar 17 03:15:30 UTC 2011 TB --- 2011-03-17 03:15:30 - building GENERIC kernel TB --- 2011-03-17 03:15:30 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-17 03:15:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-17 03:15:30 - TARGET=pc98 TB --- 2011-03-17 03:15:30 - TARGET_ARCH=i386 TB --- 2011-03-17 03:15:30 - TZ=UTC TB --- 2011-03-17 03:15:30 - __MAKE_CONF=/dev/null TB --- 2011-03-17 03:15:30 - cd /src TB --- 2011-03-17 03:15:30 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Mar 17 03:15:30 UTC 2011 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] objcopy --strip-debug --add-gnu-debuglink=nfscommon.ko.symbols nfscommon.ko.debug nfscommon.ko ===> nfsd (all) cc -O2 -pipe -DPC98 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/pc98.i386/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -I/obj/pc98.i386/src/sys/GENERIC -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/nfsd/../../fs/nfsserver/nfs_nfsdserv.c /src/sys/modules/nfsd/../../fs/nfsserver/nfs_nfsdserv.c: In function 'nfsrvd_mknod': /src/sys/modules/nfsd/../../fs/nfsserver/nfs_nfsdserv.c:1032: internal compiler error: in var_ann, at tree-flow-inline.h:128 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 Stop in /src/sys/modules/nfsd. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/pc98.i386/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-17 03:28:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-17 03:28:07 - ERROR: failed to build GENERIC kernel TB --- 2011-03-17 03:28:07 - 7106.94 user 1218.42 system 8887.29 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS import panic with r219703
On Wed, Mar 16, 2011 at 4:03 PM, Freddie Cash wrote: > Anytime I try to import my pool built using 24x HAST devices, I get > the following message, and the system reboots: > > panic: solaris assert: dmu_free_range(os, smo->smo_object, 0, -1ULL, > tx) == 0, file: > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/space_map.c, > line: 484 > > Everything runs nicely if I don't import the pool. > > Doing a "zpool import" shows that one of the HAST devices is FAULTED > "corrupted data". > > Haven't tried anything to remove/replace the faulted device, just > wanted to see if anyone knew what the above error meant. > > Pool was created using r219523 and successfully copied over 1 TB of > data from another ZFS system. Had some issues with gptboot this > morning and the system locking up and rebooting a bunch, and now the > pool won't import. Along with this ZFS import issue, it seems that hastd doesn't like it when you fire up 24 hast devices all at once (via for loop), each with over 100 MB of dirty data in it. hast dumps core, kernel panics, and system reboots. If I do 1 hast device every 2 seconds (or however long it takes to manually type "hastctl role primary disk-a1") then it starts up fine. So, I can now panic my 9-CURRENT system by either: - starting 24 hast devices at once, or - importing a ZFS pool made up of those 24 hast devices, with 1 corrupted device Isn't testing fun? :) I have a bunch of vmcore files from the hast crashes, not really sure what to do with them, though. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ZFS import panic with r219703
Anytime I try to import my pool built using 24x HAST devices, I get the following message, and the system reboots: panic: solaris assert: dmu_free_range(os, smo->smo_object, 0, -1ULL, tx) == 0, file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/space_map.c, line: 484 Everything runs nicely if I don't import the pool. Doing a "zpool import" shows that one of the HAST devices is FAULTED "corrupted data". Haven't tried anything to remove/replace the faulted device, just wanted to see if anyone knew what the above error meant. Pool was created using r219523 and successfully copied over 1 TB of data from another ZFS system. Had some issues with gptboot this morning and the system locking up and rebooting a bunch, and now the pool won't import. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 2:44 PM, Freddie Cash wrote: > On Wed, Mar 16, 2011 at 2:20 PM, Garrett Cooper wrote: >> On Wed, Mar 16, 2011 at 10:20 AM, Freddie Cash wrote: >>> On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 >>> >>> Nevermind. PEBCAK error. Adding the right port address would work. >>> Amazing how easy it is to mixup a 3 and an E. :( >> >> Are you referring to the .flags value or the BOOT_COMCONSOLE_PORT value? Sorry, not the .flags value, that was set correctly. The .port value. >> Thanks, > > Both. > > The BIOS is configured to use COM3 for the remote access support, with > an address of 3E8. > > The kernel sees COM3 as uart0 with an address of 0x3e8. > > Me, in my infinite copy/paste wisdom set loader.conf and make.conf to use 3F8. > > Figured that one out by dropping to a loader prompt and reading > through the output of "show" and manually setting the hint.uart.0.port > correctly. Then setting it in loader.conf and make.conf correctly > afterward. > > -- > Freddie Cash > fjwc...@gmail.com > -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 2:20 PM, Garrett Cooper wrote: > On Wed, Mar 16, 2011 at 10:20 AM, Freddie Cash wrote: >> On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: >>> I feel like an idiot right now because I can just not figure out how >>> to make $subject work on a -CURRENT system. :( >>> >>> I've read through the Handbook chapter on this. I've done the process >>> I've used with 8.x systems. But once the kernel loads, the serial >>> console stops working. I'm obviously missing a step somewhere. >>> >>> Here's what I've done. Please point out my error(s): >>> >>> /boot/loader.conf: >>> hint.uart.0.disabled="0" >>> hint.uart.0.flags="0x30" >>> console="comconsole vidconsole" >>> comconsole_speed="115200" >>> boot_multicons="yes" >>> >>> /etc/make.conf: >>> BOOT_COMCONSOLE_PORT=0x3F8 >>> BOOT_COMCONSOLE_SPEED=115200 >> >> Nevermind. PEBCAK error. Adding the right port address would work. >> Amazing how easy it is to mixup a 3 and an E. :( > > Are you referring to the .flags value or the BOOT_COMCONSOLE_PORT value? > Thanks, Both. The BIOS is configured to use COM3 for the remote access support, with an address of 3E8. The kernel sees COM3 as uart0 with an address of 0x3e8. Me, in my infinite copy/paste wisdom set loader.conf and make.conf to use 3F8. Figured that one out by dropping to a loader prompt and reading through the output of "show" and manually setting the hint.uart.0.port correctly. Then setting it in loader.conf and make.conf correctly afterward. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 10:20 AM, Freddie Cash wrote: > On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: >> I feel like an idiot right now because I can just not figure out how >> to make $subject work on a -CURRENT system. :( >> >> I've read through the Handbook chapter on this. I've done the process >> I've used with 8.x systems. But once the kernel loads, the serial >> console stops working. I'm obviously missing a step somewhere. >> >> Here's what I've done. Please point out my error(s): >> >> /boot/loader.conf: >> hint.uart.0.disabled="0" >> hint.uart.0.flags="0x30" >> console="comconsole vidconsole" >> comconsole_speed="115200" >> boot_multicons="yes" >> >> /etc/make.conf: >> BOOT_COMCONSOLE_PORT=0x3F8 >> BOOT_COMCONSOLE_SPEED=115200 > > Nevermind. PEBCAK error. Adding the right port address would work. > Amazing how easy it is to mixup a 3 and an E. :( Are you referring to the .flags value or the BOOT_COMCONSOLE_PORT value? Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On 3/16/11 10:20 AM, Freddie Cash wrote: On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 Nevermind. PEBCAK error. Adding the right port address would work. Amazing how easy it is to mixup a 3 and an E. :( I'll hang my head in shame now. :( not a waste because I was looking for an example set of configs and steps.. :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFR]RT305xF support, w/o attachment
Hi, On Wed, 16 Mar 2011 18:06:59 +0100 Jan Henrik Sylvester wrote: > Hello! > > On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: > > 3. RT2860 802.11n controller authors Damien Bergamini and Alexander > > Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch > > only modification to work with RT2872 (embedded to RT305[02] > > F) wrote by me. > > Is this supposed to work on its own bringing support for Ralink 2860 > to FreeBSD? (The one in the Asus EeePC 901/1000H according to > http://wiki.freebsd.org/AsusEee .) > > > Remaining issues: > > RT2860 support only Open(no crypto) mode for RT305[02]F > > Does this mean WPA should work for RT2860? (Just not for the chips > you added support for?) As I know this driver support WPA, but best place to read/ask about this on this thread http://forums.freebsd.org/showthread.php?t=7010 > > If this is supposed to bring RT2860 support to FreeBSD in general: > > - Should it work on amd64 and i386? > - Should it work on 8.2-RELEASE? > - Should it work as a module? > > In case this is all supposed to work: I tried to create a module on > 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as > I did not want to modify my stock 8.2-RELEASE kernel). I only got to: > > In file included from > /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: > @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file > or directory > > I do not find opt_rt2860.h anywhere in your patches. Assuming it was > optional, I have commented it out only to get to: > > cc1: warnings being treated as errors > /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: > warning: 'rt2860_pci_detach' declared 'static' but never defined > > Probably, I am doing something unsupported here (especially as there > is no if_rt2860_pci.c, which I would expect). No, it's me. Too much data, so I a little confused here. Patch targeting to start support RT3052F/RT3050F System on Chip. Which main part for embedded systems like routers, AP etc. To get it compiled need remove 'rt2860_pci_detach' declaration, because pci and obio interfaces have same detach device methods (rt2860_detach in rt2860.c) And opt_rt2860.h must be defined in sys/conf/options # options for the Ralink RT286x driver (rt2860) RT2860_DEBUGopt_rt2860.h > > Cheers, > Jan Henrik I will remake patch tomorrow. Thanks for your report and questions? -- Aleksandr Rybalko ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFR]RT305xF support, w/o attachment
Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). Cheers, Jan Henrik ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How does one get a working serial console with gptboot?
On Wed, Mar 16, 2011 at 9:49 AM, Freddie Cash wrote: > I feel like an idiot right now because I can just not figure out how > to make $subject work on a -CURRENT system. :( > > I've read through the Handbook chapter on this. I've done the process > I've used with 8.x systems. But once the kernel loads, the serial > console stops working. I'm obviously missing a step somewhere. > > Here's what I've done. Please point out my error(s): > > /boot/loader.conf: > hint.uart.0.disabled="0" > hint.uart.0.flags="0x30" > console="comconsole vidconsole" > comconsole_speed="115200" > boot_multicons="yes" > > /etc/make.conf: >BOOT_COMCONSOLE_PORT=0x3F8 >BOOT_COMCONSOLE_SPEED=115200 Nevermind. PEBCAK error. Adding the right port address would work. Amazing how easy it is to mixup a 3 and an E. :( I'll hang my head in shame now. :( -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
How does one get a working serial console with gptboot?
I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 /etc/ttys: ttyu0 "/usr/libexec/getty std.115200" vt100 on secure Then I rebuilt the boot code via: cd /usr/src/sys/boot make cleandepend; make depend; make; make install And I loaded the new boot code into the GPT via: gpart bootcode -p /boot/gptboot -i 1 ada0 This motherboard (SuperMicro H8DGi-F) includes an IPMI-enabled serial-over-LAN setup, including a KVM-over-LAN. The KVM-over-LAN uses a virtual onscreen keyboard, though, so it's a pain to use, which is why I'm trying to get the serial console stuff working. The BIOS is configured to use COM3 for the remote access setup. The kernel detects this as uart0, and dmesg shows it as being detect and set as "uart0: console (115200,n,8,12). The serial console works at the boot loader screens and I can drop to a loader prompt, type away, etc. As soon as I type "boot" and the kernel loads ... the serial console dies. Any suggestions? -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
