misc/171840: IPv6 packets transmitting only on queue 0

2012-09-21 Thread Venkat Duvvuru

>Number: 171840
>Category:   misc
>Synopsis:   IPv6 packets transmitting only on queue 0
>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:   Fri Sep 21 07:20:02 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Venkat Duvvuru
>Release:9.0-RELEASE
>Organization:
Emulex
>Environment:
FreeBSD root@xxx FreeBsd 9.0-RELEASE FreeBSD 9.0-RELEASE #12: Thu Aug 23 
23:42:39 IST 2012 root@root@xxx FreeBsd:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
1. The below code is absent for ip6_output? This is causing the ipv6 traffic to 
always flow in just one queue. Flowid is filled by the driver in the receive 
path and the same flowid will be used to transmit packets. I think this logic 
is missing for ipv6 packets.

"netinet/ip_output.c" Function: ip_output
if (inp != NULL) {
INP_LOCK_ASSERT(inp);
M_SETFIB(m, inp->inp_inc.inc_fibnum);
if (inp->inp_flags & (INP_HW_FLOWID|INP_SW_FLOWID)) {
m->m_pkthdr.flowid = inp->inp_flowid;
m->m_flags |= M_FLOWID;
}
}
2. "fle" is NULL after enabling FLOWTABLE for IPv6
 
"net/flowtable.c"
if (af == AF_INET6)
{
fle = flowtable_lookup_mbuf6(ft, m);
if (fle != NULL && m != NULL && (m->m_flags & M_FLOWID) == 0) {
m->m_flags |= M_FLOWID;
m->m_pkthdr.flowid = fle->f_fhash;
}
}
>How-To-Repeat:
Run ipv6 traffic with any tool and check the number of packets transmitted on 
all the created transmit queues. Only num packets on queue0 increases.
>Fix:
For the first problem I think we should populate inp->inp_flowid in the mbuf 
packet header. For the second problem, I'm not sure why flowtable_lookup_mbuf6 
is returning NULL after enabling FLOWTABLE.

>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/171811: [patch] rctl(8) cputime is too high

2012-09-21 Thread ben wilber
The following reply was made to PR kern/171811; it has been noted by GNATS.

From: ben wilber 
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: kern/171811: [patch] rctl(8) cputime is too high
Date: Fri, 21 Sep 2012 03:51:18 -0400

 Sorry, please ignore my patch; I guess the problem is just that =
 p_prev_runtime is never initialized.  I'm not sure why it exists, but =
 removing it makes things work as expected.=
___
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: kernel panic on boot with FreeBSD 8.1 and 9.0

2012-09-21 Thread Bob Bishop
Hi,

On 20 Sep 2012, at 21:18, Iordan Iordanov wrote:

> Hello!
> 
> We have a server with a Supermicro H8DGi-F motherboard.

Is the BIOS on this MB up to date?

> This motherboard has two 4x PCIe slots. Next to the ports on the motherboard 
> is written "(PCIe 4x in 8x)". We have Intel and Supermicro 4-port PCIe 8x 
> ethernet adapters. Whenever an adapter of either manufacturer is inserted 
> into one of the (PCIe 4x in 8x) ports, the FreeBSD 8.1 and 9.0 kernel panics 
> on boot with:
> 
> panic: Couldn't find an APIC vector for IRQ 14
> 
> Putting the adapters into any of the other ports (8x and 16x) has no issues. 
> Just to make sure it's not a hardware issue, we booted into Linux, and the 
> adapters work fine in the 4x (in 8x) PCIe ports, with large transfers 
> performed through them.
> 
> FreeBSD has been upgraded to the latest binaries.
> 
> Do you have any suggestions to us, and/or do you require any more 
> information? Please reply-all so I can see your reply as I am not currently 
> on the mailing list.
> Thanks!
> Iordan Iordanov

--
Bob Bishop
r...@gid.co.uk




___
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: kernel panic on boot with FreeBSD 8.1 and 9.0

2012-09-21 Thread Iordan Iordanov

Hi Bob,

Thanks for your reply.

On 09/21/12 05:50, Bob Bishop wrote:
> Is the BIOS on this MB up to date?

I installed the latest BIOS (version 3.0, we were running 2.0a), and 
FreeBSD 9.0 still fails the same way (my apologies, the IRQ was 4, not 
14 as I wrote from memory previously). Here is the backtrace, hopefulyl 
it will help:


=
panic: Couldn't find an APIC vector for IRQ 4

cpuid = 0
KBD: stack backtrace:
#0 Ox808680fe at kdb_backtrace+0x5e
#1 OI!!ff8O832cb7 at panic+0x187
#2 OI!!ff80b75419 at ioapic_enable_intr+0x49
#3 6u!!ff80b06817 at intr_add_handler+0x127
#4 0x80861f21 at bus_setup_intr+0x91
#5 0x806ab507 at uart_bus_attaeh+0x187
#6 0x80861519 at device_attach+0x69
#7 0x80862f6a at bus_generic_attach+0x1a
#8 0x80307cc5 at acpi_attach+0xbc5
#9 0x80861519 at device_attach+0x69
#10 0x80862f6a at bus_generic_attach+0x1a
#11 0x80b00719 at nexus_acpi_attach+0x69
#12 0x80861519 at device_attach+0x69
#13 9x80863176 at bus_generic_new_pass+0xd6
#14 0x8085eeca at bus_set_pass+0x7a
#15 0x80b0289a at configure+0xa
#16 0x807e7707 at mi_startup+0x77
#17 6x8029f71c at btext+0x2c
Uptime: 1s
=

___
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: kernel panic on boot with FreeBSD 8.1 and 9.0

2012-09-21 Thread Bob Bishop
Hi,

On 21 Sep 2012, at 19:10, Iordan Iordanov wrote:

> Hi Bob,
> 
> Thanks for your reply.
> 
> On 09/21/12 05:50, Bob Bishop wrote:
> > Is the BIOS on this MB up to date?
> 
> I installed the latest BIOS (version 3.0, we were running 2.0a), and FreeBSD 
> 9.0 still fails the same way (my apologies, the IRQ was 4, not 14 as I wrote 
> from memory previously). Here is the backtrace, hopefulyl it will help:
> 
> =
> panic: Couldn't find an APIC vector for IRQ 4
> 
> cpuid = 0
> KBD: stack backtrace:
> #0 Ox808680fe at kdb_backtrace+0x5e
> #1 OI!!ff8O832cb7 at panic+0x187
> #2 OI!!ff80b75419 at ioapic_enable_intr+0x49
> #3 6u!!ff80b06817 at intr_add_handler+0x127
> #4 0x80861f21 at bus_setup_intr+0x91
> #5 0x806ab507 at uart_bus_attaeh+0x187
  

Hmm. Can you disable serial ports in the BIOS? Might be a workaround.

> #6 0x80861519 at device_attach+0x69
> #7 0x80862f6a at bus_generic_attach+0x1a
> #8 0x80307cc5 at acpi_attach+0xbc5
> #9 0x80861519 at device_attach+0x69
> #10 0x80862f6a at bus_generic_attach+0x1a
> #11 0x80b00719 at nexus_acpi_attach+0x69
> #12 0x80861519 at device_attach+0x69
> #13 9x80863176 at bus_generic_new_pass+0xd6
> #14 0x8085eeca at bus_set_pass+0x7a
> #15 0x80b0289a at configure+0xa
> #16 0x807e7707 at mi_startup+0x77
> #17 6x8029f71c at btext+0x2c
> Uptime: 1s
> =
> 

--
Bob Bishop
r...@gid.co.uk




___
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/171604: commit references a PR

2012-09-21 Thread dfilter service
The following reply was made to PR bin/171604; it has been noted by GNATS.

From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: bin/171604: commit references a PR
Date: Sat, 22 Sep 2012 05:28:00 + (UTC)

 Author: kib
 Date: Sat Sep 22 05:27:47 2012
 New Revision: 240801
 URL: http://svn.freebsd.org/changeset/base/240801
 
 Log:
   MFC r240686:
   Do not reference z_nodeflib for !objgiven case, thus fixing LD_PRELOAD
   for a non-absolute path.
   
   PR:  bin/171604
 
 Modified:
   stable/9/libexec/rtld-elf/rtld.c
 Directory Properties:
   stable/9/libexec/rtld-elf/   (props changed)
 
 Modified: stable/9/libexec/rtld-elf/rtld.c
 ==
 --- stable/9/libexec/rtld-elf/rtld.c   Sat Sep 22 04:22:17 2012
(r240800)
 +++ stable/9/libexec/rtld-elf/rtld.c   Sat Sep 22 05:27:47 2012
(r240801)
 @@ -1429,7 +1429,7 @@ find_library(const char *xname, const Ob
  {
  char *pathname;
  char *name;
 -bool objgiven;
 +bool nodeflib, objgiven;
  
  objgiven = refobj != NULL;
  if (strchr(xname, '/') != NULL) { /* Hard coded pathname */
 @@ -1464,6 +1464,7 @@ find_library(const char *xname, const Ob
  (pathname = search_library_path(name, STANDARD_LIBRARY_PATH)) != NULL)
return (pathname);
  } else {
 +  nodeflib = objgiven ? refobj->z_nodeflib : false;
if ((objgiven &&
  (pathname = search_library_path(name, refobj->rpath)) != NULL) ||
  (objgiven && refobj->runpath == NULL && refobj != obj_main &&
 @@ -1471,9 +1472,8 @@ find_library(const char *xname, const Ob
  (pathname = search_library_path(name, ld_library_path)) != NULL ||
  (objgiven &&
  (pathname = search_library_path(name, refobj->runpath)) != NULL) ||
 -(pathname = search_library_path(name, gethints(refobj->z_nodeflib)))
 -!= NULL ||
 -(objgiven && !refobj->z_nodeflib &&
 +(pathname = search_library_path(name, gethints(nodeflib))) != NULL ||
 +(objgiven && !nodeflib &&
  (pathname = search_library_path(name, STANDARD_LIBRARY_PATH)) != 
NULL))
return (pathname);
  }
 ___
 svn-src-...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/svn-src-all
 To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.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"