RE: kern/185596: in_cksum_skip: out of data by 41310

2014-01-14 Thread Jens Kassel
The following reply was made to PR kern/185596; it has been noted by GNATS.

From: Jens Kassel 
To: Gleb Smirnoff 
Cc: "freebsd-gnats-sub...@freebsd.org" 
Subject: RE: kern/185596: in_cksum_skip: out of data by 41310
Date: Tue, 14 Jan 2014 08:01:59 +

 Hi,
 
 I have not tested this on FreeBSD 10.
 
 But I found that the problem can only be reproduced when using the bce driv=
 er.=20
 Tested with both re & bge drivers and with these the problem cannot be repr=
 oduces.
 
 Checked SVN history for bce but could not find any commit that seemed to be=
  related to this issue.
 
 Regards,
 
 Jens
 
 -Original Message-
 From: Gleb Smirnoff [mailto:gleb...@freebsd.org]=20
 Sent: den 9 januari 2014 11:16
 To: Jens Kassel
 Cc: freebsd-gnats-sub...@freebsd.org
 Subject: Re: kern/185596: in_cksum_skip: out of data by 41310
 
   Jens,
 
 On Thu, Jan 09, 2014 at 06:26:14AM +, Jens Kassel wrote:
 J> >Originator: Jens Kassel
 J> >Release:8.4
 J> Aptilo Networks
 J> >Environment:
 J> FreeBSD orbytebuild-freebsd84.sth.aptilo.com 8.4-RELEASE FreeBSD 8.4-REL=
 EASE8 #0 r251259: Mon Jun  3 01:14:28 UTC 2013 r...@bake.isc.freebsd.or=
 g:/usr/obj/usr/src/sys/GENERIC  i386
 J>=20
 J> We sometimes see messages like this in dmesg and /var/log/messages
 J>=20
 J> in_cksum_skip: out of data by 15810
 J> in_cksum_skip: out of data by 15810
 J> in_cksum_skip: out of data by 15810
 J> in_cksum_skip: out of data by 15810
 J> in_cksum_skip: out of data by 41310
 J>=20
 J> I have checked with tcpdump and these messages seems to be triggered whe=
 n receiving "ICMP destination unreachable" packets.
 J>=20
 J> Is this a known issue in this release?
 
 My guessing is that this messages comes off when a packet in wrong byte ord=
 er enters in_cksum().
 
 Starting with 10.0, our stack doesn't change byte order of IP packets, so i=
 f my guessing is right, the bug should vanish.
 
 We do not plan any more releases from stable/8 branch. Thus, I'd like to cl=
 ose the PR if you don't mind.
 
 --
 Totus tuus, Glebius.
 
___
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/185766: /etc/rc.d/mdconfig issues unjustified error message

2014-01-14 Thread Alfred Bartsch

>Number: 185766
>Category:   conf
>Synopsis:   /etc/rc.d/mdconfig issues unjustified error message
>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:   Tue Jan 14 09:40:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Alfred Bartsch
>Release:stable/8
>Organization:
Data-Service GmbH
>Environment:
FreeBSD dsscons3.incore 8.4-STABLE FreeBSD 8.4-STABLE #0 r256119: Wed Oct  9 
23:05:53 CEST 2013 root@dsscons3.incore:/usr/obj/usr/src/sys/SERVER64  amd64
>Description:
After defining two memory disks (swap backed, see below), I'm getting an error 
message during system startup (dmesg):

..
Creating md0 device (swap).
Mounting /dev/md0.
Creating md1 device (swap).
mount:
/var/jail: No such file or directory

Mounting local file systems:
>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"


misc/185769: Installing wolrd and kernel not from /usr/src produces "mkdir: Argument list too long"

2014-01-14 Thread Alexander Yerenkow

>Number: 185769
>Category:   misc
>Synopsis:   Installing wolrd and kernel not from /usr/src produces "mkdir: 
>Argument list too long"
>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:   Tue Jan 14 10:50:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Alexander Yerenkow
>Release:9.2-RELEASE
>Organization:
>Environment:
r255898
>Description:
Seems that using deep (long named) directory for sources (in my case is 
/zbuilder/src/src-stable-10-clone) produced this error at stage world/kernel 
install.

Probably either some part of Makefiles must be rewritten (from * to find+exec), 
or MAX_ARGS should be raised (but this will be temporary fix anyway)
>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"


kern/185771: Kernel panic with RADIX_MPATH kernel option

2014-01-14 Thread Attila Nagy

>Number: 185771
>Category:   kern
>Synopsis:   Kernel panic with RADIX_MPATH kernel option
>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:   Tue Jan 14 12:20:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Attila Nagy
>Release:stable/10@r260625
>Organization:
>Environment:
>Description:
On a netbooted machine, with the following kernel config:

include GENERIC
options RADIX_MPATH
options SMP
options BOOTP
options BOOTP_NFSV3
options BOOTP_NFSROOT
options NFSCLIENT
device  carp
device  crypto  # core crypto support
device  cryptodev   # /dev/crypto for access to h/w
options KDB
options DDB

it crashes during the kernel BOOTP/DHCP phase with:
da0 at mpt0 bus 0 scbus2 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device
da0: 300.000MB/s transfers
da0: Command Queueing enabled
da0: 5120MB (10485760 512 byte sectors: 255H 63S/T 652C)
panic: bootpc_fakeup_interfac: SIOCAIFADDR, error=17
cpuid = 0
KDB stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x81891a40
kdb_backtrace() at kdb_backtrace+0x39/frame 0x81891af0
panic() at panic+0x155/frame 0x81891b70
bootpc_init() at bootpc_init+0x1ef7/frame 0x81891c90
mi_startup() at mi_startup+0x118/frame 0x81891cb0
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 10 ]
Stopped at  kdb_enter+0x3e: movq$0, kdb_why


>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: kern/176748: [libi386] [patch] BTX Loader i386 incorrectly probes EDD, possibly resulting division by zero

2014-01-14 Thread Arrigo Marchiori
The following reply was made to PR kern/176748; it has been noted by GNATS.

From: Arrigo Marchiori 
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: kern/176748: [libi386] [patch] BTX Loader i386 incorrectly
 probes EDD, possibly resulting division by zero
Date: Tue, 14 Jan 2014 17:21:13 +0100

 Hello,
 
 this patch still applies to today's 9-STABLE.
 
 Can I do anything to help integrating it?
 
 Regards,
 -- 
 rigo
 
 http://rigo.altervista.org
___
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/185596: in_cksum_skip: out of data by 41310

2014-01-14 Thread Gleb Smirnoff
The following reply was made to PR kern/185596; it has been noted by GNATS.

From: Gleb Smirnoff 
To: Jens Kassel 
Cc: "freebsd-gnats-sub...@freebsd.org" 
Subject: Re: kern/185596: in_cksum_skip: out of data by 41310
Date: Tue, 14 Jan 2014 22:58:29 +0400

   Jens,
 
 On Tue, Jan 14, 2014 at 08:01:59AM +, Jens Kassel wrote:
 J> I have not tested this on FreeBSD 10.
 J> 
 J> But I found that the problem can only be reproduced when using the bce 
driver. 
 J> Tested with both re & bge drivers and with these the problem cannot be 
reproduces.
 J> 
 J> Checked SVN history for bce but could not find any commit that seemed to be 
related to this issue.
 
 If memory serves me well, that were panics with bce(4) and wrong byte order,
 that urged me to make byte order stable throughout the network stack. However,
 we didn't find any special in the driver itself after all. It might have a bug,
 but it also might just exposed a bug in the stack.
 
 -- 
 Totus tuus, Glebius.
___
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/163602: pmcstat(8) doesn' t search symbols under /boot/modules

2014-01-14 Thread Ulf Lilleengen
The following reply was made to PR bin/163602; it has been noted by GNATS.

From: Ulf Lilleengen 
To: bug-follo...@freebsd.org, jbe...@tormail.net
Cc:  
Subject: Re: bin/163602: pmcstat(8) doesn't search symbols under 
/boot/modules
Date: Tue, 14 Jan 2014 20:44:15 +0100

 This is a multi-part message in MIME format.
 --030308020102060505000202
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit
 
 I'm not able to reproduce this at the moment. Any tips on how? Or maybe 
 you could test out this patch:
 
 http://people.freebsd.org/~lulf/patches/pmcstat_modules.diff
 
 
 --030308020102060505000202
 Content-Type: text/x-patch;
  name="pmcstat_modules.diff"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
  filename="pmcstat_modules.diff"
 
 diff --git a/usr.sbin/pmcstat/pmcstat.c b/usr.sbin/pmcstat/pmcstat.c
 index cc43b82..d0db9c5 100644
 --- a/usr.sbin/pmcstat/pmcstat.c
 +++ b/usr.sbin/pmcstat/pmcstat.c
 @@ -583,7 +583,7 @@ main(int argc, char **argv)
args.pa_verbosity   = 1;
args.pa_logfd   = -1;
args.pa_fsroot  = "";
 -  args.pa_kernel  = strdup("/boot/kernel");
 +  args.pa_kernel  = strdup("/boot/kernel;/boot/modules");
args.pa_samplesdir  = ".";
args.pa_printfile   = stderr;
args.pa_graphdepth  = DEFAULT_CALLGRAPH_DEPTH;
 diff --git a/usr.sbin/pmcstat/pmcstat_log.c b/usr.sbin/pmcstat/pmcstat_log.c
 index fdcf9c4..6606fa5 100644
 --- a/usr.sbin/pmcstat/pmcstat_log.c
 +++ b/usr.sbin/pmcstat/pmcstat_log.c
 @@ -230,6 +230,8 @@ float pmcstat_threshold = 0.5; /* Cost filter for top 
mode. */
  static struct pmcstat_image *pmcstat_image_from_path(pmcstat_interned_string
  _path, int _iskernelmodule);
  static void pmcstat_image_get_aout_params(struct pmcstat_image *_image);
 +static void pmcstat_locate_kernelmodule(char *_buffer, size_t _buffer_length,
 +  const char *_path);
  static void pmcstat_image_get_elf_params(struct pmcstat_image *_image);
  static void   pmcstat_image_link(struct pmcstat_process *_pp,
  struct pmcstat_image *_i, uintfptr_t _lpc);
 @@ -602,6 +604,22 @@ pmcstat_image_add_symbols(struct pmcstat_image *image, 
Elf *e,
symptr->ps_end = (symptr+1)->ps_start;
  }
  
 +static void
 +pmcstat_locate_kernelmodule(char *buffer, size_t buffer_length,
 +const char *path)
 +{
 +  char * module_paths = strdup(args.pa_kernel);
 +  char * module_path = NULL;
 +  while ((module_path = strsep(&module_paths, ";")) != NULL) {
 +  (void) snprintf(buffer, buffer_length, "%s%s/%s", 
args.pa_fsroot,
 +  module_path, path);
 +  if (access(buffer, R_OK) == 0) {
 +  break;
 +  }
 +  }
 +  free(module_paths);
 +}
 +
  /*
   * Examine an ELF file to determine the size of its text segment.
   * Sets image->pi_type if anything conclusive can be determined about
 @@ -641,8 +659,7 @@ pmcstat_image_get_elf_params(struct pmcstat_image *image)
 * and user mode executable objects under FSROOT/PATHNAME.
 */
if (image->pi_iskernelmodule)
 -  (void) snprintf(buffer, sizeof(buffer), "%s%s/%s",
 -  args.pa_fsroot, args.pa_kernel, path);
 +  (void) pmcstat_locate_kernelmodule(buffer, sizeof(buffer), 
path);
else
(void) snprintf(buffer, sizeof(buffer), "%s%s",
args.pa_fsroot, path);
 
 --030308020102060505000202--
___
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: ports/185763: ports-mgmt/pkg should fail if no category is specified for the package

2014-01-14 Thread linimon
Old Synopsis: pkg should fail if no category is specified for the package
New Synopsis: ports-mgmt/pkg should fail if no category is specified for the 
package

Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Jan 14 20:28:34 UTC 2014
Responsible-Changed-Why: 
ports PR.

http://www.freebsd.org/cgi/query-pr.cgi?pr=185763
___
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: gnu/155309: [PATCH] gcc: backport bswap32() and bswap64()

2014-01-14 Thread Pedro Giffuni
The following reply was made to PR gnu/155309; it has been noted by GNATS.

From: Pedro Giffuni 
To: bug-follo...@freebsd.org, m...@freebsd.org
Cc:  
Subject: Re: gnu/155309: [PATCH] gcc: backport bswap32() and bswap64()
Date: Tue, 14 Jan 2014 16:37:30 -0500

 Hello;
 
 In an effort to reduce differences against Apple's GCC,
 I committed the bswap34/64 builtins as part of r258428.
 
 The change was not MFCd to FreeBSD 9.x because I
 noticed something in the bigger patch causes issues when
 building OpenOffice. It is probable that just rebuilding all the
 dependencies fixes the issue but I obviously wanted to avoid
 some pain to existing users.
 
 Further investigation is welcome or we can just close this PR.
___
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/163585: cpuset(1) by twice kill SMP functionality

2014-01-14 Thread Andrey Chernov
The following reply was made to PR kern/163585; it has been noted by GNATS.

From: Andrey Chernov 
To: fi...@ukr.net, bug-follo...@freebsd.org
Cc:  
Subject: Re: kern/163585: cpuset(1) by twice kill SMP functionality
Date: Wed, 15 Jan 2014 03:53:28 +0400

 Right now I notice the same situation for 9.2-stable, but only with 
 SCHED_ULE, SCHED_4BSD looks working.
 See http://lists.freebsd.org/pipermail/freebsd-stable/2014-January/076894.html
 (cpuminer calls cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_CPUSET), 
 so few restarts show the bug)
 
___
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/185791: [patch] devel/lua-posix: remove unsupported function

2014-01-14 Thread Kan Sasaki

>Number: 185791
>Category:   misc
>Synopsis:   [patch] devel/lua-posix: remove unsupported function
>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:   Wed Jan 15 02:20:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Kan Sasaki
>Release:FreeBSD 9.2-STABLE amd64
>Organization:
>Environment:
>Description:
Remove unsupported function 'fdatasync.'

>How-To-Repeat:

>Fix:


Patch attached with submission follows:

Index: files/patch-ext__posix__posix.c
===
--- files/patch-ext__posix__posix.c (revision 339685)
+++ files/patch-ext__posix__posix.c (working copy)
@@ -1,5 +1,5 @@
 ./ext/posix/posix.c.orig   2013-09-09 09:15:14.0 +0200
-+++ ./ext/posix/posix.c2014-01-10 15:21:47.831554392 +0100
+--- ./ext/posix/posix.c.orig   2013-09-09 16:15:14.0 +0900
 ./ext/posix/posix.c2014-01-15 11:00:23.0 +0900
 @@ -68,6 +68,10 @@
  #include "lauxlib.h"
  #include "lua52compat.h"
@@ -11,3 +11,31 @@
  #ifndef STREQ
  #  define STREQ(a, b) (strcmp (a, b) == 0)
  #endif
+@@ -3697,6 +3701,7 @@
+   return pushresult(L, fsync(fd), NULL);
+ }
+ 
++#if 0
+ #if _POSIX_VERSION >= 200112L
+ /***
+  synchronize a file's in-core state with storage device without metadata
+@@ -3712,6 +3717,7 @@
+   return pushresult(L, fdatasync(fd), NULL);
+ }
+ #endif
++#endif
+ 
+ /***
+ reposition read/write file offset
+@@ -3771,9 +3777,11 @@
+   MENTRY( Perrno  ),
+   MENTRY( Pexec   ),
+   MENTRY( Pexecp  ),
++#if 0
+ #if _POSIX_VERSION >= 200112L
+   MENTRY( Pfdatasync  ),
+ #endif
++#endif
+   MENTRY( Pfcntl  ),
+   MENTRY( Pfileno ),
+   MENTRY( Pfiles  ),


>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"