misc/187899: rtadvd fill syslog with unneeded error messages
>Number: 187899 >Category: misc >Synopsis: rtadvd fill syslog with unneeded error messages >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 Mar 24 10:30:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Adri Koppes >Release:FreeBSD 9.2-RELEASE-p3 >Organization: SalesManager Software B.V. >Environment: FreeBSD mail.salesmanager.nl 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #1 r260687M: Wed Jan 15 11:42:16 CET 2014 r...@mail.salesmanager.nl:/usr/obj/usr/src/sys/MAIL amd64 >Description: I have rtadvd running to provide IPV6 configuration for the internal network, which uses interface em0. /etc/rc.conf contains: ifconfig_em0="inet 192.168.0.12 netmask 255.255.255.0" ifconfig_em0_ipv6="auto_linklocal 2001:xxx::zzz::1 prefixlen 64" rtadvd_enable="YES" rtadvd_interfaces="em0" The server is also running mpd5 to provide PPTP vpn services. When a PPTP vpn disconnects, the corresponding netgraph (ng) interface is destroyed. When this happens, rtadvd generates a syslog error in /var/log/messages: Mar 24 08:52:23 mail rtadvd[35606]: : ifinfo not found (idx=12) This error should not be logged, since rtadvd is not listening no or servicing any netgraph interfaces. >How-To-Repeat: Configure an interface with ipv6 and configure rtadvd on this interface. Install and configure mpd5. Start rtadvd and mpd5 Establish a VPN and disconnect the VPN. Error message is loged everytime a VPN disconnects. >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"
kern/187900: camcontrol: ATA secure erase always fails with timeout
>Number: 187900 >Category: kern >Synopsis: camcontrol: ATA secure erase always fails with timeout >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 Mar 24 11:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: T. Schaap >Release:9.2 Release >Organization: - >Environment: FreeBSD 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #10: Thu Jan 16 21:33:00 CET 2014 :/usr/obj/usr/src/sys/SERVER amd64 >Description: When trying to securely erase a SATA disk with camcontrol security, the command starts succesfully but gives a timeout after circa 23 minutes. I tried 3 different disks with the same result. As far as I know there are no hardware problems. I think erasing disks should work flawlessly as this is an important security measure when abondoning disks. Example output: server# camcontrol security ada3 pass3: ATA-8 SATA 2.x device pass3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Security Option Value supported yes enabled no drive locked no security config frozenno count expired no security levelhigh enhanced erase supported yes erase time152 min enhanced erase time 152 min master password rev fffe server# time camcontrol security ada3 -s secret -e secret -U user -T 1 pass3: ATA-8 SATA 2.x device pass3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) You are about to ERASE ALL DATA from the following device: pass3,ada3: ATA-8 SATA 2.x device Are you SURE you want to ERASE ALL DATA? (yes/no) yes Issuing SECURITY_SET_PASSWORD password='secret', user='user', mode='high' Issuing SECURITY_ERASE_PREPARE Issuing SECURITY_ERASE_UNIT password='secret', user='user' camcontrol: ATA SECURITY_ERASE_UNIT failed: 0 0.000u 0.010s 23:36.24 0.0% 216+2216k 0+0io 0pf+0w >From /var/log/messages: Mar 24 11:03:13 server kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 Mar 24 11:03:13 server kernel: ada3: ATA-8 SATA 2.x device Mar 24 11:03:13 server kernel: ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Mar 24 11:03:13 server kernel: ada3: Command Queueing enabled Mar 24 11:03:13 server kernel: ada3: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) Mar 24 11:31:36 server kernel: ahcich3: Timeout on slot 0 port 0 Mar 24 11:31:36 server kernel: ahcich3: is cs 0001 ss rs 0001 tfd d0 serr cmd e017 >How-To-Repeat: camcontrol security ada3 -s secret -e secret -U user -T 1 Substitute local device identifier for ada3! >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"
kern/187903: Only 0.44 (always) days of uptime with ciss (w/HP SA P812)
>Number: 187903 >Category: kern >Synopsis: Only 0.44 (always) days of uptime with ciss (w/HP SA P812) >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 Mar 24 16:50:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Nagy, Attila >Release:stable/9@r260621 and stable/10@r262152 >Organization: >Environment: >Description: I have an HP DL360G7 with a HP SmartArray P812 in it, which crashes exactly (well, some minutes plus or minus, but on the graph it's nearly the same) at 0.44 days of uptime no matter what I do, load the machine until it's so hot, I can't touch it, or just leave it idle. The P812 has an HP MDS600 connected to it with 70 1TB disks, with a 6 disk RAID6 (ADG) setup. The volumes have 128k stripe size, because I use ZFS on top of them. The zpool is simply a stripe of the RAID6 volumes. What may be important: the controller's RAID6 initialization is still ongoing. In the first sentence idle means the zpool/zfs is just mounted and only some stat()s happening on them (crashes after 0.44 days) and fully loaded means gstat shows around 100% utilization on the disks nearly all the time (crashes after 0.44 days also). I've already tried with stable/9@r260621 and stable/10@r262152, it's the same. I've also tried with Linux (Ubuntu 13.10, hpsa driver, zfs on linux 0.6.2), it doesn't crash (neither idle or loaded). Already swapped the machine and the P812 to a different one, no effect. Everything (DL360, P812, MDS600, disks) has the latest firmware. The currently used ZFS is created under Linux to see whether this causes the problems, but of course there are many different things in the two OS (kernel, HP SA driver, block/SCSI layer and even ZFS is somewhat different). Linux works, FreeBSD crashes no matter what I do. The exact message I can see is (ciss0 is the built-in P411): ciss1: ADAPTER HEARTBEAT FAILED Fatal trap 1: privileged instruction fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xfe0c59ff795d stack pointer = 0x28:0xfe0baf1ab9d0 frame pointer = 0x28:0xfe0baf1aba20 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 (swi4: clock) trap number = 1 panic: privileged instruction fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0baf1ab560 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe0baf1ab610 panic() at panic+0x155/frame 0xfe0baf1ab690 trap_fatal() at trap_fatal+0x3a2/frame 0xfe0baf1ab6f0 trap() at trap+0x794/frame 0xfe0baf1ab910 calltrap() at calltrap+0x8/frame 0xfe0baf1ab910 --- trap 0x1, rip = 0xfe0c59ff795d, rsp = 0xfe0baf1ab9d0, rbp = 0xfe0baf1aba20 --- (null)() at 0xfe0c59ff795d/frame 0xfe0baf1aba20 softclock_call_cc() at softclock_call_cc+0x16c/frame 0xfee77120 kernphys() at 0x/frame 0xfee778a0 kernphys() at 0x/frame 0xfee78aa0 kernphys() at 0x/frame 0xfee78c20 Uptime: 10h18m12s (da4:ciss1:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da4:ciss1:0:0:0): CAM status: Command timeout (da4:ciss1:0:0:0): Error 5, Retries exhausted (da4:ciss1:0:0:0): Synchronize cache failed (da5:ciss1:0:1:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da5:ciss1:0:1:0): CAM status: Command timeout (da5:ciss1:0:1:0): Error 5, Retries exhausted (da5:ciss1:0:1:0): Synchronize cache failed (da6:ciss1:0:2:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da6:ciss1:0:2:0): CAM status: Command timeout (da6:ciss1:0:2:0): Error 5, Retries exhausted (da6:ciss1:0:2:0): Synchronize cache failed (da7:ciss1:0:3:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da7:ciss1:0:3:0): CAM status: Command timeout (da7:ciss1:0:3:0): Error 5, Retries exhausted (da7:ciss1:0:3:0): Synchronize cache failed (da8:ciss1:0:4:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da8:ciss1:0:4:0): CAM status: Command timeout (da8:ciss1:0:4:0): Error 5, Retries exhausted (da8:ciss1:0:4:0): Synchronize cache failed (da9:ciss1:0:5:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da9:ciss1:0:5:0): CAM status: Command timeout (da9:ciss1:0:5:0): Error 5, Retries exhausted (da9:ciss1:0:5:0): Synchronize cache failed (da10:ciss1:0:6:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da10:ciss1:0:6:0): CAM status: Command timeout (da10:ciss1:0:6:0): Error 5, Retries exhausted (da10:ciss1:0:6:0): Synchronize cache failed (da11:ciss1:0:7:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da11:ci
misc/187904: ipfw (8) does not properly recognize the network in shorthand
>Number: 187904 >Category: misc >Synopsis: ipfw (8) does not properly recognize the network in shorthand >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 Mar 24 18:00:01 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Vladislav V. Prodan >Release:FreeBSD 10.0 >Organization: support.od.ua >Environment: FreeBSD bimbo.YYY 10.0-STABLE FreeBSD 10.0-STABLE #0: Sun Mar 23 08:14:35 EET 2014 r...@bimbo.yyy:/usr/obj/usr/src/sys/bimbo.3 amd64 >Description: When network is added to the table ipfw in shortened form, network ::/0 appears By the context of the rules ipfw - drop or reset, network ::/0 can block access to the target machine. In the system 9.0 such behavior was not observed. For example, the network 177.204/14 #whois -L 177.204/14 .. inetnum: 177.204/14 aut-num: AS18881 abuse-c: GOI owner: Global Village Telecom .. >How-To-Repeat: #ipfw table 100 list #ipfw table 100 add 177.204/14 #ipfw table 100 list ::/0 0 >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/187903: [ciss] Only 0.44 (always) days of uptime with ciss (w/HP SA P812)
Old Synopsis: Only 0.44 (always) days of uptime with ciss (w/HP SA P812) New Synopsis: [ciss] Only 0.44 (always) days of uptime with ciss (w/HP SA P812) Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 24 18:16:58 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=187903 ___ 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"
misc/187905: Confusion zpool with a block size in HDD - block size: 512B configured, 4096B native
>Number: 187905 >Category: misc >Synopsis: Confusion zpool with a block size in HDD - block size: 512B >configured, 4096B native >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 Mar 24 18:20:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Vladislav V. Prodan >Release:FreeBSD 10.0 >Organization: support.od.ua >Environment: FreeBSD bimbo.YYY 10.0-STABLE FreeBSD 10.0-STABLE #0: Sun Mar 23 08:14:35 EET 2014 r...@bimbo.yyy:/usr/obj/usr/src/sys/bimbo.3 amd64 >Description: On a machine using ZFS, after upgrading from 9.0 to 10.0, zpool status says: # zpool status pool: tank state: ONLINE status: One or more devices are configured to use a non-native block size. Expect reduced performance. action: Replace affected devices with devices that support the configured block size, or migrate data to a properly configured pool. scan: scrub repaired 0 in 4h42m with 0 errors on Mon Mar 24 05:38:49 2014 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 gpt/system-ada1 ONLINE 0 0 0 block size: 512B configured, 4096B native errors: No known data errors ashift: 9 # zdb -U /boot/zfs/zpool.cache tank: version: 28 name: 'tank' state: 0 txg: 9794975 pool_guid: 14509785011519350988 hostid: 3616469326 hostname: 'bimbo.fitnessfactor.com.ua' vdev_children: 1 vdev_tree: type: 'root' id: 0 guid: 14509785011519350988 children[0]: type: 'disk' id: 0 guid: 17960990484356700785 path: '/dev/gpt/system-ada1' phys_path: '/dev/gpt/system-ada1' whole_disk: 1 metaslab_array: 30 metaslab_shift: 31 ashift: 9 asize: 495807889408 is_log: 0 DTL: 82314 create_txg: 4 # diskinfo -v /dev/ada0 /dev/ada0 512 # sectorsize 500107862016# mediasize in bytes (466G) 976773168 # mediasize in sectors 4096# stripesize 0 # stripeoffset 969021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. S20BJ90D306953 # Disk ident. # smartctl -a /dev/ada0 smartctl 6.2 2014-02-18 r3874 [FreeBSD 10.0-STABLE amd64] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda SpinPoint F3 Device Model: ST500DM005 HD502HJ Serial Number:S20BJ90D306953 LU WWN Device Id: 5 0004cf 209d3bdd6 Firmware Version: 1AJ10001 User Capacity:500 107 862 016 bytes [500 GB] Sector Size: 512 bytes logical/physical Rotation Rate:7200 rpm Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is:Mon Mar 24 20:00:48 2014 EET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED .. >How-To-Repeat: >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: bin/187904: [ipfw] ipfw(8) does not properly recognize the network in shorthand [regression]
Old Synopsis: ipfw (8) does not properly recognize the network in shorthand New Synopsis: [ipfw] ipfw(8) does not properly recognize the network in shorthand [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-ipfw Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 24 18:33:04 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=187904 ___ 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/187905: [zpool] Confusion zpool with a block size in HDD - block size: 512B configured, 4096B native
Old Synopsis: Confusion zpool with a block size in HDD - block size: 512B configured, 4096B native New Synopsis: [zpool] Confusion zpool with a block size in HDD - block size: 512B configured, 4096B native Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 24 18:34:42 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=187905 ___ 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/173323: mail/cvsmail, mail/mailutils distfiles overwrite each other
Synopsis: mail/cvsmail, mail/mailutils distfiles overwrite each other State-Changed-From-To: open->closed State-Changed-By: rene State-Changed-When: Mon Mar 24 19:47:11 UTC 2014 State-Changed-Why: mail/mailutils has expired and been deleted Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs Responsible-Changed-By: rene Responsible-Changed-When: Mon Mar 24 19:47:11 UTC 2014 Responsible-Changed-Why: Move to correct category http://www.freebsd.org/cgi/query-pr.cgi?pr=173323 ___ 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/187912: Getting Stack Traces of Xorg with DTrace Causes Hang
>Number: 187912
>Category: kern
>Synopsis: Getting Stack Traces of Xorg with DTrace Causes Hang
>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 Mar 24 23:50:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Nick Zivkovic
>Release:10.0 (r260789)
>Organization:
N/A
>Environment:
FreeBSD Stalingrad 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16
22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
When executing the following DTrace script:
sudo dtrace -n 'syscall:::entry /execname == "Xorg"/ {@[ustack()] = count();}'
and pressing ^C, the Xserver freezes. The machine (a laptop) is unresponsive.
So I ssh'd into the laptop (from a different laptop), and did:
pgrep dtrace
Sure enough the dtrace exec was still alive, but not doing anything (that I can
tell).
Firefox still did IO and stuff, but Xorg didn't have _any_ activity (according
to top).
So I did a `kill -9 $(my-dtrace-pid)`
This caused Xorg to restart.
Bottom line: running that simple (and common) DTrace script froze Xorg. I don't
mean to be inflammatory but, this should _never_ happen, especially not in
production --- which means that the FreeBSD DTrace implementation is violating
DTrace's original design constraints. This is a critical error, and shows that
FreeBSD's DTrace may not be suitable for production use, yet.
So far I've only been able to replicate this on Xorg.
It may be of importance that I did `make buildworld` and `make installworld`
with the following options:
CFLAGS+=-fno-omit-frame-pointer
STRIP=
WITH_CTF=1
In other words I made all of my installed packages dtrace-friendly.
>How-To-Repeat:
When running Xorg (not stripped, no frame-pointer optimization, and with CTF)
run:
sudo dtrace -n 'syscall:::entry /execname == "Xorg"/ {@[ustack] = count();}'
resize windows, click around, etc.
go back to terminal and hit ^C.
>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"
