kern/178771: QUIRK: Western Digital My Passport HD
>Number: 178771 >Category: kern >Synopsis: QUIRK: Western Digital My Passport HD >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun May 19 07:40:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Tim Matthews >Release:9.1-STABLE >Organization: - >Environment: Commands below run with patch applied: tim-desktop# uname -a FreeBSD tim-desktop.matthews 9.1-STABLE FreeBSD 9.1-STABLE #33 r250230M: Sat May 11 22:21:52 NZST 2013 root@tim-desktop.matthews:/usr/obj/usr/src/sys/MYKERNEL amd64 tim-desktop# camcontrol inquiry da0 pass5: Fixed Direct Access SCSI-6 device pass5: Serial Number 575842314139324630363435 pass5: 40.000MB/s transfers >Description: P/N: WDBKXH5000ABK-01 Western Digital My Passport USB portable hard drive not mountable and /dev/da0s1 is not present. Dmesg after attaching the HD is: ugen7.2: at usbus7 umass0: on usbus7 umass0: SCSI over Bulk-Only; quirks = 0x4001 umass0:9:0:-1: Attached to scbus9 (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (da0:umass-sim0:0:0:0): got CAM status 0x44 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 4 refs (da0:umass-sim0:0:0:0): removing device entry >How-To-Repeat: Try to plug Hd in. Issues are appended to dmesg and won't be mountable. >Fix: Attached patches make the HD work like normal and dmesg upon connecting the drive with patches is: ugen7.2: at usbus7 umass0: on usbus7 umass0: SCSI over Bulk-Only; quirks = 0x4000 umass0:9:0:-1: Attached to scbus9 da0 at umass-sim0 bus 0 scbus9 target 0 lun 0 da0: Fixed Direct Access SCSI-6 device da0: 40.000MB/s transfers da0: 476908MB (976707584 512 byte sectors: 255H 63S/T 60797C) ses0 at umass-sim0 bus 0 scbus9 target 0 lun 1 ses0: Fixed Enclosure Services SCSI-6 device ses0: 40.000MB/s transfers ses0: SCSI-3 ENC Device GEOM_LABEL[1]: MSDOSFS: da0: no FAT volume detected. GEOM_LABEL[1]: MSDOSFS: da0s1: FAT32 volume detected. GEOM_LABEL[1]: Label for provider da0s1 is msdosfs/NO_NAME. Patch attached with submission follows: *** /sys/dev/usb/quirk/usb_quirk.c Sun Feb 3 13:41:14 2013 --- /root/usb-quirk-fix/usb_quirk.c Sat May 11 22:00:50 2013 *** static struct usb_quirk_entry usb_quirks *** 424,429 --- 424,430 UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_INQUIRY_EVPD, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(WESTERN, MYPASSWORD, 0x, 0x, UQ_MSC_FORCE_SHORT_INQ), + USB_QUIRK(WESTERN, MYPASSPORT, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(WINMAXGROUP, FLASH64MC, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_INQUIRY), USB_QUIRK(YANO, FW800HD, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, *** /sys/dev/usb/usbdevsSun Mar 3 09:46:31 2013 --- /root/usb-quirk-fix/usbdevs Sat May 11 21:58:37 2013 *** product WESTERN EXTHDD 0x0400 External *** 4194,4199 --- 4194,4200 product WESTERN HUB 0x0500 USB HUB product WESTERN MYBOOK0x0901 MyBook External HDD product WESTERN MYPASSWORD0x0704 MyPassword External HDD + product WESTERN MYPASSPORT0x0748 MyPassport External HDD /* WIENER Plein & Baus GmbH products */ product WIENERPLEINBAUS PL512 0x0010 PL512 PSU >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: junk/178758: aUzkGdLCKdUhdPiKWGu
Synopsis: aUzkGdLCKdUhdPiKWGu State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun May 19 08:19:51 UTC 2013 State-Changed-Why: spam Responsible-Changed-From-To: freebsd-bugs->gnats-admin Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 19 08:19:51 UTC 2013 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=178758 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: junk/178735: qwUEKdjFxOO
Synopsis: qwUEKdjFxOO State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun May 19 08:20:26 UTC 2013 State-Changed-Why: spam Responsible-Changed-From-To: freebsd-bugs->gnats-admin Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 19 08:20:26 UTC 2013 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=178735 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: junk/178740: lbCUwfGVvZFF
Synopsis: lbCUwfGVvZFF State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun May 19 08:20:26 UTC 2013 State-Changed-Why: spam Responsible-Changed-From-To: freebsd-bugs->gnats-admin Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 19 08:20:26 UTC 2013 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=178740 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: junk/178761: jYlMwoHO
Synopsis: jYlMwoHO State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun May 19 08:20:26 UTC 2013 State-Changed-Why: spam Responsible-Changed-From-To: freebsd-bugs->gnats-admin Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 19 08:20:26 UTC 2013 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=178761 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: usb/178771: [usbdevs] [patch] Western Digital My Passport HD
Old Synopsis: QUIRK: Western Digital My Passport HD New Synopsis: [usbdevs] [patch] Western Digital My Passport HD Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 19 08:22:01 UTC 2013 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=178771 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/178664: truss(1) may kill process
The following reply was made to PR bin/178664; it has been noted by GNATS. From: Jilles Tjoelker To: bug-follo...@freebsd.org, kwia...@panic.pl Cc: Subject: Re: bin/178664: truss(1) may kill process Date: Sun, 19 May 2013 14:09:32 +0200 In PR bin/178664, you wrote: > [attaching truss(1) may terminate sleep(1) early] What actually happens is that the nanosleep(2) system call fails with [EINTR] immediately when the debugger (ptrace(2)) attaches. You can verify this using ktrace(1). This is really a longstanding known bug, although I don't know where it is documented. It is longstanding because it is very hard to fix. The kernel wants threads to return to the kernel-userspace boundary when a debugger attaches, and this causes the state of the in-progress system call to be lost. The effect is much like a signal with SA_RESTART set. If you care about sleep(1) itself, that is easy to fix. It already continues the sleep when nanosleep(2) was interrupted by SIGINFO; this can be extended to any [EINTR] error. A workaround is to use ktrace(1) instead of truss(1) or strace(1) from ports. ktrace(1) generally affects the traced program much less. -- Jilles Tjoelker ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/178773: [patch] Huawei E303 USB 3G modem support
>Number: 178773 >Category: kern >Synopsis: [patch] Huawei E303 USB 3G modem support >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun May 19 15:40:02 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Peter Sopko >Release:9.1-RELEASE >Organization: BACKBONE, s.r.o. >Environment: FreeBSD avantgarde.backbone.sk 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Sun May 19 16:43:43 CEST 2013 r...@avantgarde.backbone.sk:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Huawei E303 USB 3G modem is considered as an unknown device. It is possible to use camcontrol and/or sysutils/usb_modeswitch port to manually force it to become a 3g modem recognised by cdce, u3g and ue drivers, but no /dev/cua* and /dev/ttyU* /dev-entires are created. After usb_modeswitch* there is a message in dmesg stating May 19 16:05:03 avantgarde root: Unknown USB device: vendor 0x12d1 product 0x1506 bus uhub1 *usb_modeswitch command used was 'usb_modeswitch -v 0x12d1 -p 0x14fe -V 0x12d1 -P 0x1506 -s 20 -M "55534243123456780a11062100"' >How-To-Repeat: Just plug the usb 3g modem into the machine >Fix: Please see the attached patch (two-line additions to sys/dev/usb/usbdevs and sys/dev/usb/serial/u3g.c). Apply in /usr/src using 'patch -p0 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2.0: u3g0: ugen1.2.1: cdce0: ugen1.2.4: umass0: ugen1.2.5: umass1: bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1506 bcdDevice = 0x0102 iManufacturer = 0x0003 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 Patch attached with submission follows: diff -rupN original/u3g.c new/u3g.c --- sys/dev/usb/serial/u3g.c2013-05-19 17:20:38.0 +0200 +++ sys/dev/usb/serial/u3g.c2013-05-19 17:21:32.0 +0200 @@ -280,6 +280,8 @@ static const STRUCT_USB_HOST_ID u3g_devs U3G_DEV(HUAWEI, E143D, U3GINIT_HUAWEI), U3G_DEV(HUAWEI, E143E, U3GINIT_HUAWEI), U3G_DEV(HUAWEI, E143F, U3GINIT_HUAWEI), + U3G_DEV(HUAWEI, E303, 0), + U3G_DEV(HUAWEI, E303_INIT, U3GINIT_HUAWEISCSI), U3G_DEV(HUAWEI, E173, 0), U3G_DEV(HUAWEI, E173_INIT, U3GINIT_HUAWEISCSI), U3G_DEV(HUAWEI, E180V, U3GINIT_HUAWEI), diff -rupN original/usbdevs new/usbdevs --- sys/dev/usb/usbdevs 2013-05-19 17:20:49.0 +0200 +++ sys/dev/usb/usbdevs 2013-05-19 17:21:37.0 +0200 @@ -1885,6 +1885,8 @@ product HUAWEI E143F 0x143f 3G modem product HUAWEI E1752 0x1446 3G modem product HUAWEI K3765 0x1465 3G modem product HUAWEI E1820 0x14ac E1820 HSPA+ USB Slider +product HUAWEI E303_INIT 0x14fe 3G modem initial +product HUAWEI E3030x1506 3G modem product HUAWEI K3765_INIT 0x1520 K3765 Initial product HUAWEI E1730x1c05 3G modem product HUAWEI E173_INIT 0x1c0b 3G modem initial >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: usb/178773: [usbdevs] [patch] Huawei E303 USB 3G modem support
Old Synopsis: [patch] Huawei E303 USB 3G modem support New Synopsis: [usbdevs] [patch] Huawei E303 USB 3G modem support Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 19 16:04:31 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178773 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/178664: truss(1) may kill process
On Sun, 19 May 2013, Jilles Tjoelker wrote: The following reply was made to PR bin/178664; it has been noted by GNATS. From: Jilles Tjoelker To: bug-follo...@freebsd.org, kwia...@panic.pl Cc: Subject: Re: bin/178664: truss(1) may kill process Date: Sun, 19 May 2013 14:09:32 +0200 In PR bin/178664, you wrote: > [attaching truss(1) may terminate sleep(1) early] What actually happens is that the nanosleep(2) system call fails with [EINTR] immediately when the debugger (ptrace(2)) attaches. You can verify this using ktrace(1). That's ktrace sleep(1) process. ptrace() could see the EINTR in a register like it does for gdb, but I think truss doesn't report this detail so neither does ktrace on the truss process. This is really a longstanding known bug, although I don't know where it is documented. It is longstanding because it is very hard to fix. The kernel wants threads to return to the kernel-userspace boundary when a debugger attaches, and this causes the state of the in-progress system call to be lost. The effect is much like a signal with SA_RESTART set. If you care about sleep(1) itself, that is easy to fix. It already continues the sleep when nanosleep(2) was interrupted by SIGINFO; this can be extended to any [EINTR] error. sleep(1) is specified to sleep for at least as long as the specified number of seconds. It is broken since it "knows" that EINTR can't happen. sleep(2) is specified to sleep for at least as long as the specified number of seconds unless a signal is delivered to the thread and its action is to invoke a signal-catching function or terminate the process. Since there is no real signal here, there is no possibility of catching it, and the unreal signal doesn't terminate the process either (it just causes nanosleep(2) to return early). Thus sleep(2) is broken too. Similarly for nanosleep(2). Not similarly for clock_nanosleep(2), since it is just missing in FreeBSD. A workaround is to use ktrace(1) instead of truss(1) or strace(1) from ports. ktrace(1) generally affects the traced program much less. Old versions of truss don't have the bug. This seems to be because they don't use ptrace (they use procfs and ioctl). However, all versions of gdb have the bug: - old (FreeBSD-~5.2) versions of gdb and/or ptrace(2) have the bug in a worse form. Now even ktrace on the sleep(2) process doesn't see the EINTR (nanosleep() returns 0 with no error). - current versions of gdb and/or ptrace make nanosleep() return -1/EINTR, but to handle this problem using gdb you would prefer gdb to trap the signal before it causes the EINTR. But unreal signals are especially hard to trap. Bruce ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
conf/178775: [PATCH] make distributekernel when -DNO_ROOT is not specified is broken
>Number: 178775
>Category: conf
>Synopsis: [PATCH] make distributekernel when -DNO_ROOT is not specified
>is broken
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun May 19 19:20:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Garrett Cooper
>Release:10-CURRENT
>Organization:
EMC Isilon
>Environment:
FreeBSD fuji-current.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1
r+4f99885-dirty: Thu May 16 15:52:49 PDT 2013
root@fuji-current.local:/usr/obj/usr/src/sys/FUJI-NOCOMPAT i386
>Description:
make distributekernel fails today with the following message if -DNO_ROOT is
specified:
sed -e 's|^./kernel|.|' //usr/obj/usr/src/release/dist/kernel.premeta >
//usr/obj/usr/src/release/dist/kernel.meta
sed: //usr/obj/usr/src/release/dist/kernel.premeta: No such file or directory
The attached patch adds the needed guard for distributekernel to pass.
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
>From 25179851a175ff81ea6e3147286da11c2c1519ad Mon Sep 17 00:00:00 2001
From: Garrett Cooper
Date: Sun, 19 May 2013 12:10:02 -0700
Subject: [PATCH] Fix distributekernel when NO_ROOT is not defined
Signed-off-by: Garrett Cooper
---
Makefile.inc1 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Makefile.inc1 b/Makefile.inc1
index 6a18156..296d725 100644
--- a/Makefile.inc1
+++ b/Makefile.inc1
@@ -1051,8 +1051,10 @@ distributekernel distributekernel.debug:
${IMAKE_MTREE} PATH=${TMPPATH} ${MAKE} KERNEL=${INSTKERNNAME} \
DESTDIR=${INSTALL_DDIR:S://:/:g:C:/$::}/kernel \
${.TARGET:S/distributekernel/install/}
+.if defined(NO_ROOT)
sed -e 's|^./kernel|.|' ${DESTDIR}/${DISTDIR}/kernel.premeta > \
${DESTDIR}/${DISTDIR}/kernel.meta
+.endif
.for _kernel in ${BUILDKERNELS:S/${INSTALLKERNEL}//}
.if defined(NO_ROOT)
echo "#${MTREE_MAGIC}" > ${DESTDIR}/${DISTDIR}/kernel.${_kernel}.premeta
--
1.8.2.3
>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/178683: [install] segmentation fault in disklabel while installing
Old Synopsis: segmentation fault in disklabel while installing New Synopsis: [install] segmentation fault in disklabel while installing Responsible-Changed-From-To: freebsd-i386->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:12:05 UTC 2013 Responsible-Changed-Why: probably not i386-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=178683 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178540: [geom] [patch] kern.geom.confdot contains superfluous semicolon at the end of the last curly brace
Old Synopsis: kern.geom.confdot contains superfluous semicolon at the end of the last curly brace New Synopsis: [geom] [patch] kern.geom.confdot contains superfluous semicolon at the end of the last curly brace Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:25:50 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178540 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178482: [ipfw] logging problem from vnet jail
Old Synopsis: ipfw logging problem from vnet jail New Synopsis: [ipfw] logging problem from vnet jail Responsible-Changed-From-To: freebsd-bugs->freebsd-ipfw Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:26:47 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178482 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178480: [ipfw] dynamically loaded ipfw with a vimage kernel don't work.
Old Synopsis: dynamically loaded ipfw with a vimage kernel don't work. New Synopsis: [ipfw] dynamically loaded ipfw with a vimage kernel don't work. Responsible-Changed-From-To: freebsd-bugs->freebsd-ipfw Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:27:30 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178480 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: usb/178267: [usb] USB causing interrupt storm on irq16
Old Synopsis: USB causing interrupt storm on irq16 New Synopsis: [usb] USB causing interrupt storm on irq16 Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:28:08 UTC 2013 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=178267 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178238: [nullfs] nullfs don't release i-nodes on unlink.
Old Synopsis: nullfs don't release i-nodes on unlink. New Synopsis: [nullfs] nullfs don't release i-nodes on unlink. Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:28:53 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178238 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178231: [nfs] 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026"
Old Synopsis: 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026" New Synopsis: [nfs] 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026" Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:29:21 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178231 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178103: [kernel] [nfs] [patch] Correct support of index files for WebNFS exports
Old Synopsis: Correct support of index files for WebNFS exports New Synopsis: [kernel] [nfs] [patch] Correct support of index files for WebNFS exports Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:29:52 UTC 2013 Responsible-Changed-Why: Involves NFS, but also a kernel and binary change. Perhaps the NFS folks can review. http://www.freebsd.org/cgi/query-pr.cgi?pr=178103 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178079: [tcp] Switching TCP CC algorithm panics on sparc64 with a complaint from the MMU
Old Synopsis: Switching TCP CC algorithm panics on sparc64 with a complaint from the MMU New Synopsis: [tcp] Switching TCP CC algorithm panics on sparc64 with a complaint from the MMU Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:30:59 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178079 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/177335: [nfs] [panic] Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NFSnode lock (NFSnode lock)
Old Synopsis: Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NFSnode lock (NFSnode lock) New Synopsis: [nfs] [panic] Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NFSnode lock (NFSnode lock) Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 03:32:02 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=177335 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/178782: [ixgbe] 82599EB SFP does not work with passthrough under KVM.
>Number: 178782 >Category: kern >Synopsis: [ixgbe] 82599EB SFP does not work with passthrough under KVM. >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon May 20 06:30:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Jason Shi >Release:9.1-PRERELEASE >Organization: Arraynetworks >Environment: Host OS: OpenSUSE 12.2 Linux linux-kj2u 3.4.6-2.10-desktop #1 SMP PREEMPT Thu Jul 26 09:36:26 UTC 2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux QEMU emulator version 1.1.1 (kvm-1.1.1-1.8.1), Copyright (c) 2003-2008 Fabrice Bellard Guest OS: FreeBSD freebsd9.1 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The 10G Intel 82599EB SFP NIC could not work with passthrough on KVM. I did some tests with different Hypervisors and Guest OS, which make me think it's a FreeBSD problem. 1. OpenXen + FreeBSD9.1 guest os. -- [OK] 2. OpenXen + Linux guest os (e.g. Fedora 12). -- [OK] 3. KVM + Linux guest os (e.g. Fedora 12). -- [OK] 4. KVM + FreeBSD9.1 guest os. -- [Failed] >How-To-Repeat: 1.Make the pci device of 82599SFP assignale. From lspci on OpenSUSE: 0d:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01) Subsystem: QLogic, Corp. Device 00e4 Flags: fast devsel, IRQ 25 Memory at f8fe (64-bit, prefetchable) [size=128K] I/O ports at cc00 [size=32] Memory at f8fdc000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable- Count=64 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [e0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-00-00-ff-ff-00-00-00 Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [160] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: pci-stub 2. Passthrough it to the guest FreeBSD os. Here is my vm configuration file FreeBSD9.1 4d56613e-400c-f37d-2a9a-e0332d81ca63 2097152 2097152 2 hvm destroy restart destroy /usr/bin/qemu-kvm 3.The device could be probed and attached by FreeBSD. From dmesg on FreeBSD: ix0: port 0xc020-0xc03f mem 0xfe00-0xfe01,0xfe02-0xfe023fff irq 11 at device 4.0 on pci0 ix0: Using MSIX interrupts with 2 vectors ix0: Ethernet address: 00:0c:bd:05:7d:4a ix0: PCI Express Bus: Speed 5.0Gb/s Width x8 But no interrupt could be found. From "vmstat -i": interrupt total rate irq1: atkbd0 143 0 irq4: uart0 177 1 irq15: ata1 1593 10 cpu0:timer 7140 46 Total 9053 58 And ix0 keeps to be "no carrier" (even if I config an IP address on it and ping). From "ifconfig": ix0: flags=8802 metric 0 mtu 1500 options=401bb ether 00:0c:bd:05:7d:4a nd6 options=29 media: Ethernet autoselect status: no carrier >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/178782: [ixgbe] 82599EB SFP does not work with passthrough under KVM.
Synopsis: [ixgbe] 82599EB SFP does not work with passthrough under KVM. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 20 06:35:14 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178782 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
