Re: panic after r244584
Jaakko Heinonen wrote: JH On 2013-01-18, Alexander Motin wrote: JH At cam/scsi/ses_set_physpath.c ses_set_physpath(). Duplicate names are JH impossible there, as previous name components are unique. Special JH characters haven't yet seen, but I think theoretically possible. JH JH I see two possible solutions for the problem. JH JH 1) Replace non-printable, space and '/' characters for example with '_'. JH'/' should be replaced anyway. JH JH 2) Apply the patches in JHhttp://lists.freebsd.org/pipermail/svn-src-all/2013-January/063661.html JHto allow spaces again. I haven't committed the patches because I JHthink that there isn't full consensus that it's right thing to do and JHalso I personally prefer not to have spaces in device names. After patch was applied, problem is gone away. da0 at mps0 bus 0 scbus7 target 8 lun 0 da0: ATA ST3500630NS G Fixed Direct Access SCSI-6 device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) ses1: da0,pass7: Element descriptor: 'Slot 08' ses1: da0,pass7: SAS Device Slot Element: 1 Phys at Slot 7 ses1: phy 0: SATA device ses1: phy 0: parent 5003048000baa87f addr 5003048000baa853 JH JH -- JH Jaakko JH ___ JH freebsd-current@freebsd.org mailing list JH http://lists.freebsd.org/mailman/listinfo/freebsd-current JH To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ 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: [RFC/RFT] calloutng
On Sun, Jan 13, 2013 at 09:36:11PM +0200, Alexander Motin wrote: On 13.01.2013 20:09, Marius Strobl wrote: On Tue, Jan 08, 2013 at 12:46:57PM +0200, Alexander Motin wrote: On 06.01.2013 17:23, Marius Strobl wrote: I'm not really sure what to do about that. Earlier you already said that sched_bind(9) also isn't an option in case if td_critnest 1. To be honest, I don't really unerstand why using a spin lock in the timecounter path makes sparc64 the only problematic architecture for your changes. The x86 i8254_get_timecount() also uses a spin lock so it should be in the same boat. The problem is not in using spinlock, but in waiting for other CPU while spinlock is held. Other CPU may also hold spinlock and wait for something, causing deadlock. i8254 code uses spinlock just to atomically access hardware registers, so it causes no problems. Okay, but wouldn't that be a general problem then? Pretty much anything triggering an IPI holds smp_ipi_mtx while doing so and the lower level IPI stuff waits for other CPU(s), including on x86. The problem is general. But now it works because single smp_ipi_mtx is used in all cases where IPI result is waited. As soon as spinning happens with interrupts still enabled, there is no deadlocks. But problem reappears if any different lock is used, or locks are nested. I'm having a hard time getting an alternate time counter device to work. The crystal required for the counters in the south bridge just doesn't seem to be mounted any where near it (I've not looked at the bottom of the PCB though). While the time counter part of the on- board bge(4) driven chips basically work, they don't seem to like concurrent accesses caused by the rest of bge(4). I.e. although the counter is just read, sooner or later this causes a fatal bus error. I haven't tried serializing accesses to the chip, but getting to such a complexity for just reading a non-indexed register at least doesn't feel good ... However, AFAICT the scenario you describe can't happen. On sparc64, spinlock_enter() only raises the processor interrupt level, which doesn't block the direct cross traps I've implemented remote reading of (S)TICK as (which also means that the actions such traps may perform are very limitted and must occur in interrupt context, but which are sufficient for this purpose and in turn makes them very fast). I.e. although the AP holds smp_ipi_mtx or any amount of nested spin locks, this will not deadlock in case the BSP also holds any spin lock when reading (S)TICK from it. Marius ___ 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 ia64/ia64
TB --- 2013-01-21 08:24:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-21 08:24:09 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-21 08:24:09 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-01-21 08:24:09 - cleaning the object tree TB --- 2013-01-21 08:25:27 - /usr/local/bin/svn stat /src TB --- 2013-01-21 08:25:37 - At svn revision 245708 TB --- 2013-01-21 08:25:38 - building world TB --- 2013-01-21 08:25:38 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 08:25:38 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 08:25:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 08:25:38 - SRCCONF=/dev/null TB --- 2013-01-21 08:25:38 - TARGET=ia64 TB --- 2013-01-21 08:25:38 - TARGET_ARCH=ia64 TB --- 2013-01-21 08:25:38 - TZ=UTC TB --- 2013-01-21 08:25:38 - __MAKE_CONF=/dev/null TB --- 2013-01-21 08:25:38 - cd /src TB --- 2013-01-21 08:25:38 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Jan 21 08:25:43 UTC 2013 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 Mon Jan 21 10:02:31 UTC 2013 TB --- 2013-01-21 10:02:31 - generating LINT kernel config TB --- 2013-01-21 10:02:31 - cd /src/sys/ia64/conf TB --- 2013-01-21 10:02:31 - /usr/bin/make -B LINT TB --- 2013-01-21 10:02:31 - cd /src/sys/ia64/conf TB --- 2013-01-21 10:02:31 - /usr/sbin/config -m LINT TB --- 2013-01-21 10:02:31 - building LINT kernel TB --- 2013-01-21 10:02:31 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 10:02:31 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 10:02:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 10:02:31 - SRCCONF=/dev/null TB --- 2013-01-21 10:02:31 - TARGET=ia64 TB --- 2013-01-21 10:02:31 - TARGET_ARCH=ia64 TB --- 2013-01-21 10:02:31 - TZ=UTC TB --- 2013-01-21 10:02:31 - __MAKE_CONF=/dev/null TB --- 2013-01-21 10:02:31 - cd /src TB --- 2013-01-21 10:02:31 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Mon Jan 21 10:02:31 UTC 2013 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 [...] acpi_powerres.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_resource.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_thermal.o:(.sbss+0x20): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_timer.o:(.sbss+0x28): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here *** [kernel] Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-01-21 10:23:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-01-21 10:23:07 - ERROR: failed to build LINT kernel TB --- 2013-01-21 10:23:07 - 5391.37 user 1213.96 system 7137.96 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-ia64-ia64.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: disk flipped - a known problem?
Andriy Gapon a...@freebsd.org wrote: Today something unusual happened on one of my machines: kernel: (ada0:ahcich0:0:0:0): lost device kernel: (aprobe1:ahcich0:0:15:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 kernel: (aprobe1:ahcich0:0:15:0): CAM status: Command timeout kernel: (aprobe1:ahcich0:0:15:0): Error 5, Retries exhausted kernel: (aprobe1:ahcich0:0:15:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 kernel: (aprobe1:ahcich0:0:15:0): CAM status: Command timeout kernel: (aprobe1:ahcich0:0:15:0): Error 5, Retries exhausted kernel: cam_periph_alloc: attempt to re-allocate valid device ada0 rejected flags 0x18 refcount 1 kernel: adaasync: Unable to attach to new device due to status 0x6 I believe I saw something similar when trying to forcefully end the cam lockups reported in: http://lists.freebsd.org/pipermail/freebsd-current/2012-October/037413.html Detaching the disc drive caused /dev/cd0 to disappear as expected, but reinserting the drive didn't bring cd0 back. It looks like the disk disappeared from the bus and then re-appeared on the bus, but not to the OS. One of the partitions that the disk hosted was a swap partition and it seems to be the cause of some of the following consequences. The consequences: [...] * geom_event thread started consuming 100% of CPU in g_wither_washer() This sounds familiar as well: http://www.freebsd.org/cgi/query-pr.cgi?pr=171865 Fabian signature.asc Description: PGP signature
Re: panic after r244584
On 2013-01-19, Jaakko Heinonen wrote: On 2013-01-18, Alexander Motin wrote: At cam/scsi/ses_set_physpath.c ses_set_physpath(). Duplicate names are impossible there, as previous name components are unique. Special characters haven't yet seen, but I think theoretically possible. I see two possible solutions for the problem. 1) Replace non-printable, space and '/' characters for example with '_'. '/' should be replaced anyway. 2) Apply the patches in http://lists.freebsd.org/pipermail/svn-src-all/2013-January/063661.html to allow spaces again. I haven't committed the patches because I think that there isn't full consensus that it's right thing to do and also I personally prefer not to have spaces in device names. Here's a patch to implement 1: http://people.freebsd.org/~jh/patches/scsi_enc_ses-si_name.diff -- Jaakko ___ 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: disk flipped - a known problem?
Hi! On Sunday 20 January 2013 20:00:15 Andriy Gapon wrote: Today something unusual happened on one of my machines: kernel: (ada0:ahcich0:0:0:0): lost device kernel: (aprobe1:ahcich0:0:15:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 kernel: (aprobe1:ahcich0:0:15:0): CAM status: Command timeout kernel: (aprobe1:ahcich0:0:15:0): Error 5, Retries exhausted kernel: (aprobe1:ahcich0:0:15:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 kernel: (aprobe1:ahcich0:0:15:0): CAM status: Command timeout kernel: (aprobe1:ahcich0:0:15:0): Error 5, Retries exhausted kernel: cam_periph_alloc: attempt to re-allocate valid device ada0 rejected flags 0x18 refcount 1 kernel: adaasync: Unable to attach to new device due to status 0x6 It looks like the disk disappeared from the bus and then re-appeared on the bus, but not to the OS. One of the partitions that the disk hosted was a swap partition and it seems to be the cause of some of the following consequences. The consequences: * ZFS properly noticed disappearance of the disk, but its diagnostic was a little bit misleading: pool: pond state: DEGRADED status: One or more devices has been removed by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: scrub repaired 0 in 8h55m with 0 errors on Sat Dec 22 12:06:30 2012 config: NAMESTATE READ WRITE CKSUM pondDEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 12725235722288301230REMOVED 0 0 0 was /dev/gptid/fcf3558b-493b-11de-a8b9-001cc08221ff gptid/48782c6e-8fbd-11de-b3e1-00241d20d446 ONLINE 0 0 0 Yes, I agree that the disk got removed/lost, but disagree that the administrator did it. * geom_event thread started consuming 100% of CPU in g_wither_washer() * /dev/ada0 disappeared but camcontrol devlist still reported ada0: ST3500410AS CC34 at scbus0 target 0 lun 0 (pass0,ada0) * As seen in the system messages, CAM layer refused to re-attach the disk * gpart command would just crash So, I can explain the behavior of the geom_event thread - apparently swapgeom_orphan doesn't do anything that is really meaningful to GEOM and so g_wither_washer is stuck waiting until the swap consumer goes way (drops its access bits). (Another sad thing about this state is that I couldn't swapoff the device, because there was no device entry.) I am not sure if the attempt to re-allocate valid device failure was caused by this, but it could be, if something in CAM layer was waiting for GEOM layer to be done with the disk. It would be nice if the swap code properly supported disappearance of the underlying disks. Especially in this case where the swap was actually never used / touched at all (few hours after reboot and completely idle system). I don't know if it's related, but my new 2 TB WD green harddisk vanished three times during the last couple of weeks, too, Some guys over there at hackers@ told me that that might be due to bad blocks on the disk, but unfortunately (or luckily?) neither of the smart tests did find any errors :-(. So I wonder if there's a hardware or software problem. That happened on 9.1 stable when I was copying data from/to that harddisk (UFS). Ciao, Christian. ___ 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: panic after r244584
Jaakko Heinonen wrote: JH On 2013-01-19, Jaakko Heinonen wrote: JH On 2013-01-18, Alexander Motin wrote: JH At cam/scsi/ses_set_physpath.c ses_set_physpath(). Duplicate names are JH impossible there, as previous name components are unique. Special JH characters haven't yet seen, but I think theoretically possible. JH JH I see two possible solutions for the problem. JH JH 1) Replace non-printable, space and '/' characters for example with '_'. JH '/' should be replaced anyway. JH JH 2) Apply the patches in JH http://lists.freebsd.org/pipermail/svn-src-all/2013-January/063661.html JH to allow spaces again. I haven't committed the patches because I JH think that there isn't full consensus that it's right thing to do and JH also I personally prefer not to have spaces in device names. JH JH Here's a patch to implement 1: JH JH http://people.freebsd.org/~jh/patches/scsi_enc_ses-si_name.diff Ok that patch work's too. ses1: da0,pass5,probe8: Element descriptor: 'Slot 08' ses1: da0,pass5,probe8: SAS Device Slot Element: 1 Phys at Slot 7 ses1: phy 0: SATA device ses1: phy 0: parent 5003048000baa87f addr 5003048000baa853 da0 at mps0 bus 0 scbus7 target 8 lun 0 da0: ATA ST3500630NS G Fixed Direct Access SCSI-6 device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) ___ 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: [head tinderbox] failure on ia64/ia64
On 21 January 2013 14:23, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2013-01-21 08:24:09 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-21 08:24:09 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-21 08:24:09 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-01-21 08:24:09 - cleaning the object tree TB --- 2013-01-21 08:25:27 - /usr/local/bin/svn stat /src TB --- 2013-01-21 08:25:37 - At svn revision 245708 TB --- 2013-01-21 08:25:38 - building world TB --- 2013-01-21 08:25:38 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 08:25:38 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 08:25:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 08:25:38 - SRCCONF=/dev/null TB --- 2013-01-21 08:25:38 - TARGET=ia64 TB --- 2013-01-21 08:25:38 - TARGET_ARCH=ia64 TB --- 2013-01-21 08:25:38 - TZ=UTC TB --- 2013-01-21 08:25:38 - __MAKE_CONF=/dev/null TB --- 2013-01-21 08:25:38 - cd /src TB --- 2013-01-21 08:25:38 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Jan 21 08:25:43 UTC 2013 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 Mon Jan 21 10:02:31 UTC 2013 TB --- 2013-01-21 10:02:31 - generating LINT kernel config TB --- 2013-01-21 10:02:31 - cd /src/sys/ia64/conf TB --- 2013-01-21 10:02:31 - /usr/bin/make -B LINT TB --- 2013-01-21 10:02:31 - cd /src/sys/ia64/conf TB --- 2013-01-21 10:02:31 - /usr/sbin/config -m LINT TB --- 2013-01-21 10:02:31 - building LINT kernel TB --- 2013-01-21 10:02:31 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 10:02:31 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 10:02:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 10:02:31 - SRCCONF=/dev/null TB --- 2013-01-21 10:02:31 - TARGET=ia64 TB --- 2013-01-21 10:02:31 - TARGET_ARCH=ia64 TB --- 2013-01-21 10:02:31 - TZ=UTC TB --- 2013-01-21 10:02:31 - __MAKE_CONF=/dev/null TB --- 2013-01-21 10:02:31 - cd /src TB --- 2013-01-21 10:02:31 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Mon Jan 21 10:02:31 UTC 2013 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 [...] acpi_powerres.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_resource.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_thermal.o:(.sbss+0x20): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_timer.o:(.sbss+0x28): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here *** [kernel] Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** [buildkernel] Error code 1 The (first) patch should fix the build. So that it is only declared when included in utglobal.c (and extern elsewhere). DEFINE_ACPI_GLOBALS defined there expects ACPI_EXTERN to properly handle global objects defined with ACPI_INIT_GLOBAL. ### Index: contrib/dev/acpica/include/acglobal.h === --- contrib/dev/acpica/include/acglobal.h (revision 245745) +++ contrib/dev/acpica/include/acglobal.h (working copy) @@ -420,7 +420,7 @@ #ifdef ACPI_DISASSEMBLER -BOOLEAN ACPI_INIT_GLOBAL (AcpiGbl_IgnoreNoopOperator, FALSE); +ACPI_EXTERN BOOLEAN ACPI_INIT_GLOBAL (AcpiGbl_IgnoreNoopOperator, FALSE); ACPI_EXTERN BOOLEAN AcpiGbl_DbOpt_disasm; ACPI_EXTERN BOOLEAN AcpiGbl_DbOpt_verbose; ### The other way is to declare AcpiGbl_IgnoreNoopOperator as extern below. This seems to be used for other ACPI_INIT_GLOBAL's as well, see acglobal.h But this doesn't work because it is not defined under DEFINE_ACPI_GLOBALS. ### Index: contrib/dev/acpica/include/acpixf.h === --- contrib/dev/acpica/include/acpixf.h (revision 245745) +++ contrib/dev/acpica/include/acpixf.h (working copy) @@ -79,6 +79,7 @@ extern UINT8AcpiGbl_CopyDsdtLocally; extern UINT8AcpiGbl_TruncateIoAddresses; extern UINT8AcpiGbl_DisableAutoRepair; +extern BOOLEAN AcpiGbl_IgnoreNoopOperator; /* ### Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-01-21 10:23:07 - WARNING: /usr/bin/make returned exit code 1 TB ---
[head tinderbox] failure on ia64/ia64
TB --- 2013-01-21 18:24:06 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-21 18:24:06 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-21 18:24:06 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-01-21 18:24:06 - cleaning the object tree TB --- 2013-01-21 18:26:05 - /usr/local/bin/svn stat /src TB --- 2013-01-21 18:26:09 - At svn revision 245742 TB --- 2013-01-21 18:26:10 - building world TB --- 2013-01-21 18:26:10 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 18:26:10 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 18:26:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 18:26:10 - SRCCONF=/dev/null TB --- 2013-01-21 18:26:10 - TARGET=ia64 TB --- 2013-01-21 18:26:10 - TARGET_ARCH=ia64 TB --- 2013-01-21 18:26:10 - TZ=UTC TB --- 2013-01-21 18:26:10 - __MAKE_CONF=/dev/null TB --- 2013-01-21 18:26:10 - cd /src TB --- 2013-01-21 18:26:10 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Jan 21 18:26:15 UTC 2013 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 Mon Jan 21 20:02:02 UTC 2013 TB --- 2013-01-21 20:02:02 - generating LINT kernel config TB --- 2013-01-21 20:02:02 - cd /src/sys/ia64/conf TB --- 2013-01-21 20:02:02 - /usr/bin/make -B LINT TB --- 2013-01-21 20:02:02 - cd /src/sys/ia64/conf TB --- 2013-01-21 20:02:02 - /usr/sbin/config -m LINT TB --- 2013-01-21 20:02:02 - building LINT kernel TB --- 2013-01-21 20:02:02 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 20:02:02 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 20:02:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 20:02:02 - SRCCONF=/dev/null TB --- 2013-01-21 20:02:02 - TARGET=ia64 TB --- 2013-01-21 20:02:02 - TARGET_ARCH=ia64 TB --- 2013-01-21 20:02:02 - TZ=UTC TB --- 2013-01-21 20:02:02 - __MAKE_CONF=/dev/null TB --- 2013-01-21 20:02:02 - cd /src TB --- 2013-01-21 20:02:02 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Mon Jan 21 20:02:02 UTC 2013 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 [...] acpi_powerres.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_resource.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_thermal.o:(.sbss+0x20): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_timer.o:(.sbss+0x28): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here *** [kernel] Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-01-21 20:22:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-01-21 20:22:58 - ERROR: failed to build LINT kernel TB --- 2013-01-21 20:22:58 - 5462.62 user 1225.88 system 7131.85 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-ia64-ia64.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
[PATCH] Variable-size ioctl data handling
Hi,
Could anybody please review and check in the patch
patch-ioctl-var-size.txt from this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=175425 ?
This patch introduces the generic way to pass variable size ioctl
argument using the structure like this struct my_struct {int len; ...any
fields...}.
Thank you,
Yuri
___
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 + usb in trouble?
On Sat, Jan 19, 2013 at 11:26:39PM +0900, Alexander Nedotsukov wrote: Let's use some space out of it. #dd if=/dev/zero of=/tank/foo ^C250939+0 records in 250938+0 records out 128480256 bytes transferred in 30.402453 secs (4225983 bytes/sec) Oops... #zpool status pool: tank state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub repaired 5K in 0h0m with 0 errors on Sat Jan 19 23:11:20 2013 config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da1 ONLINE 0 0 1 da2 ONLINE 0 0 0 da3 ONLINE 0 0 1 This seems like umass/usb issue (hps@ CCed). Can you also try GELI with data integrity verification? # geli onetime -a hmac/sha1 -s 4096 /dev/da0 It will report some problems due to GEOM tasting, but ignore them and run: # dd if=/dev/random of=/dev/da0.eli bs=1m Once that done try to read the data back and look at the logs to see if any corruptions are reported. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgpRaNMtMVNc2.pgp Description: PGP signature
Re: kmem_map auto-sizing and size dependencies
On Fri, Jan 18, 2013 at 08:26:04AM -0800, m...@freebsd.org wrote: Should it be set to a larger initial value based on min(physical,KVM) space available? It needs to be smaller than the physical space, [...] Or larger, as the address space can get fragmented and you might not be able to allocate memory even if you have physical pages available. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgphr9pcEGGow.pgp Description: PGP signature
Re: ZFS + usb in trouble?
I used wrong Hans' login, resending with the proper e-mail. On Mon, Jan 21, 2013 at 09:58:52PM +0100, Pawel Jakub Dawidek wrote: On Sat, Jan 19, 2013 at 11:26:39PM +0900, Alexander Nedotsukov wrote: Let's use some space out of it. #dd if=/dev/zero of=/tank/foo ^C250939+0 records in 250938+0 records out 128480256 bytes transferred in 30.402453 secs (4225983 bytes/sec) Oops... #zpool status pool: tank state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub repaired 5K in 0h0m with 0 errors on Sat Jan 19 23:11:20 2013 config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da1 ONLINE 0 0 1 da2 ONLINE 0 0 0 da3 ONLINE 0 0 1 This seems like umass/usb issue (hps@ CCed). Can you also try GELI with data integrity verification? # geli onetime -a hmac/sha1 -s 4096 /dev/da0 It will report some problems due to GEOM tasting, but ignore them and run: # dd if=/dev/random of=/dev/da0.eli bs=1m Once that done try to read the data back and look at the logs to see if any corruptions are reported. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgphVtGYdmMmd.pgp Description: PGP signature
Re: [head tinderbox] failure on ia64/ia64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-21 15:22:58 -0500, FreeBSD Tinderbox wrote: TB --- 2013-01-21 18:24:06 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-21 18:24:06 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-21 18:24:06 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-01-21 18:24:06 - cleaning the object tree TB --- 2013-01-21 18:26:05 - /usr/local/bin/svn stat /src TB --- 2013-01-21 18:26:09 - At svn revision 245742 TB --- 2013-01-21 18:26:10 - building world TB --- 2013-01-21 18:26:10 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 18:26:10 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 18:26:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 18:26:10 - SRCCONF=/dev/null TB --- 2013-01-21 18:26:10 - TARGET=ia64 TB --- 2013-01-21 18:26:10 - TARGET_ARCH=ia64 TB --- 2013-01-21 18:26:10 - TZ=UTC TB --- 2013-01-21 18:26:10 - __MAKE_CONF=/dev/null TB --- 2013-01-21 18:26:10 - cd /src TB --- 2013-01-21 18:26:10 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Jan 21 18:26:15 UTC 2013 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 Mon Jan 21 20:02:02 UTC 2013 TB --- 2013-01-21 20:02:02 - generating LINT kernel config TB --- 2013-01-21 20:02:02 - cd /src/sys/ia64/conf TB --- 2013-01-21 20:02:02 - /usr/bin/make -B LINT TB --- 2013-01-21 20:02:02 - cd /src/sys/ia64/conf TB --- 2013-01-21 20:02:02 - /usr/sbin/config -m LINT TB --- 2013-01-21 20:02:02 - building LINT kernel TB --- 2013-01-21 20:02:02 - CROSS_BUILD_TESTING=YES TB --- 2013-01-21 20:02:02 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-21 20:02:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-21 20:02:02 - SRCCONF=/dev/null TB --- 2013-01-21 20:02:02 - TARGET=ia64 TB --- 2013-01-21 20:02:02 - TARGET_ARCH=ia64 TB --- 2013-01-21 20:02:02 - TZ=UTC TB --- 2013-01-21 20:02:02 - __MAKE_CONF=/dev/null TB --- 2013-01-21 20:02:02 - cd /src TB --- 2013-01-21 20:02:02 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Mon Jan 21 20:02:02 UTC 2013 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 [...] acpi_powerres.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_resource.o:(.sbss+0x0): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_thermal.o:(.sbss+0x20): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here acpi_timer.o:(.sbss+0x28): multiple definition of `AcpiGbl_IgnoreNoopOperator' dbcmds.o:(.sbss+0x0): first defined here *** [kernel] Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-01-21 20:22:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-01-21 20:22:58 - ERROR: failed to build LINT kernel TB --- 2013-01-21 20:22:58 - 5462.62 user 1225.88 system 7131.85 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-ia64-ia64.full It should be fixed now (r245748, make universe tested). Sorry for the breakage, again. Jung-uk Kim -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJQ/bMgAAoJECXpabHZMqHOtbcH/jNd3nq5/nKaWXP4kdbmi1bj sVPeNi1+C3nYTAxfzIn1UzIlObiyg3u3b2xKuTp2/YNN/k3s9jhloWwzoTCS0YcR qVWGfJ+3zRsMQQ1gMMnzkoZdqnkoznMQNZvCt0Uti0lwk1mASLU7VKxGHsmnyqO8 hnZaa8XgwnZDiQW5ac6utpFpGvQyCQEBJIbsZ/yg2FXz8bHi9QOXRGJs22KiASZB RjQFmv7U4TpeRzQT11UsjopfIZ3RssI7g8pA5+iIbzjZ9nsGaf21itvJSiRfFqlg sFYRy00rm1rMdlgPc+ToTNTtzTc0M/2QULhhEkZjP0S8O/U+w69+qSdpkqcsrdA= =GyLm -END PGP SIGNATURE- ___ 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 + usb in trouble?
On Monday 21 January 2013 22:36:04 Hans Petter Selasky wrote: On Monday 21 January 2013 22:17:19 Pawel Jakub Dawidek wrote: I used wrong Hans' login, resending with the proper e-mail. Hi, You should try to use some tools to write some random data and read it back and see if the data is the same, at /dev/daX level. The USB wrapper for SCSI is very simple and it passes commands directly from CAM to the hardware. I would be surprised if data was corrupted at this stage. Please also check if your USB device suffers from the lack of SYNCHRONIZE CACHE. --HPS ___ 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 + usb in trouble?
On Monday 21 January 2013 22:17:19 Pawel Jakub Dawidek wrote: I used wrong Hans' login, resending with the proper e-mail. Hi, You should try to use some tools to write some random data and read it back and see if the data is the same, at /dev/daX level. The USB wrapper for SCSI is very simple and it passes commands directly from CAM to the hardware. I would be surprised if data was corrupted at this stage. --HPS ___ 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 + usb in trouble?
On Monday 21 January 2013 22:37:11 Hans Petter Selasky wrote: On Monday 21 January 2013 22:36:04 Hans Petter Selasky wrote: On Monday 21 January 2013 22:17:19 Pawel Jakub Dawidek wrote: I used wrong Hans' login, resending with the proper e-mail. Hi, You should try to use some tools to write some random data and read it back and see if the data is the same, at /dev/daX level. The USB wrapper for SCSI is very simple and it passes commands directly from CAM to the hardware. I would be surprised if data was corrupted at this stage. Please also check if your USB device suffers from the lack of SYNCHRONIZE CACHE. Hi, Try this first: usbconfig -d X.Y add_quirk UQ_MSC_NO_SYNC_CACHE Re-plug device. --HPS ___ 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
installworld fails
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22 00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Is anyone seeing this? install -l s usr/src/sys /sys install: /sys/sys: Directory not empty *** [distrib-dirs] Error code 71 ___ 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: installworld fails
On Jan 21, 2013, at 10:13 PM, AN a...@neu.net wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r245766: Tue Jan 22 00:49:02 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Is anyone seeing this? install -l s usr/src/sys /sys install: /sys/sys: Directory not empty *** [distrib-dirs] Error code 71 Yes. I haven't tracked down the cause, but doing 'rm /sys' prior to installworld is an effective workaround. Jason ___ 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
