headers
Tobias Grosser | 1 Sep 2009 01:26
Picon
Favicon

Re: [PATCH] USB Harddrive not recognized (umass appears, da0 not)

On Mon, 2009-08-31 at 21:07 +0200, Bernd Walter wrote:
> On Mon, Aug 31, 2009 at 06:59:18PM +0200, Tobias Grosser wrote:
> > On Mon, 2009-08-31 at 11:52 +0200, Bernd Walter wrote:
> > > On Sun, Aug 30, 2009 at 07:09:29PM +0200, Hans Petter Selasky wrote:
> > > > Hi,
> > > > 
> > > > I looks like your device is hanging on SCSI command 0x12,00,00,00,4a,00
> > > 
> > > 0x12 is an inquiry, which is bad if the device has problems with.
> > 
> > I tried Linux on the same computer and the drive worked without any
> > problems.
> > 
> 
> If those are timestamps then there is a 5 second delay.
> I wouldn't say that this is without problems.
> Maybe Linux just has a different handling of the case.
> 
> > ---------------------------------------
> > linux_dmesg.log is attached.
> > ---------------------------------------
> > 
> > There was also another report where the drive did not work on FreeBSD. I
> > mailed the user and he did not get it to run on FreeBSD, but his drive
> > also works on Linux.
> > 
> > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028999.html
> > 
> > As I have two of these drives, I am pretty sure my device is not
> > completely broken, but WD has some uncommon/broken way to interact with
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kip Macy | 1 Sep 2009 03:35
Picon
Favicon

Re: Forwarding benchmark

We're not going to see much more 700kpps on forwarding workloads until
we do something about the rtentry locking. I had some interesting
ideas I was exploring, but I don't have the luxury of side projects
right now.

em(9)'s transmit performance has been substantially improved in 8 by
using a buf_ring instead of IFQ so I assume that you're entirely gated
by rx performance. Jeff did some work in that area to reduce the
per-packet overhead of dequeue and to do some NAPI-like opportunistic
polling using a variant of the taskqueue API.

It won't give you any idea about latency breakdown, but it would be
useful for a general time breakdown to look at unhalted core cycles in
PMC.

Good Luck,
Kip

On Fri, Aug 21, 2009 at 02:25, Fabien Thomas<fabien.thomas <at> netasq.com> wrote:
>        Hi all,
>
> Just a quick benchmark on 8.0 Beta2+ (18/08) show no regression vs 7.2.
>
> Result in FPS for 64bytes frame using Breakingpoint Elite
>
> Breakingpoint P1 === DUT === Breakingpoint P2
>
> Stream1 : P1 -> P2
> Stream2: P2 -> P1
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Li, Qing | 1 Sep 2009 03:44

RE: IPv6 regression on 8.x

Hi Hiroki,

>
>  2) Issue of subnet-router anycast address with a global address
> 
>  Thanks for the fixes!  With the two patches 1) and 3) are gone, but
>  2) still remains.  Is there something I can help to narrow down it?
> 

Hmm... I tried multiple test cases and all seem to work as expected.
I also tried the exact configuration sequence as you outlined in your
original bug report email, and that case worked, too.

The only difference I can see from the given information, is I have 
3 em interfaces, whereas you have 2 em interfaces and 1 re, but I 
don't see how that would make a difference.

Would it be possible for you to email me your system configuration 
produced from "ifconfig" and "netstat" privately ?

Thank you.

-- Qing

_______________________________________________
freebsd-net <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 4 comments |
headers
Aristedes Maniatis | 1 Sep 2009 03:52
Picon
Favicon
Gravatar

[beta3] ld-elf Undefined symbol

Upgraded an amd64 FreeBSD machine from beta 2 to beta 3 via freebsd-update. When trying to use the bacula
port (a backup tool), the application will die with the following error:

/libexec/ld-elf.so.1: /usr/local/sbin/bacula-dir: Undefined symbol "_ZN5BSOCK18set_source_addressEP5dlist"

Naturally we have rebuilt all ports and rebuilt (just to be sure) all ports that bacula depends on. Is this a
bug in beta3 or something we are doing wrong?

Cheers
Ari Maniatis

-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
John Nielsen | 1 Sep 2009 05:58

WEP on wi(4) [was: Re: LOR wlan0 wi0]

On Sunday 09 August 2009 01:27:07 am Sam Leffler wrote:
> > Sam Leffler <sam <at> errno.com> wrote:
> I can confirm WEP is broken on wi in sta mode (and probably ap mode). 
> I found at least two bugs but couldn't get it to work so am going to
> leave it as an errata for 8.0.  But what's truly odd is that WPA works
> fine despite a bug that should've caused it to not work.  I knew WPA
> worked which is probably why I ignored WEP (noone in their right mind 
> uses WEP when WPA is available :-)).

So for us wrong-minded people with wi(4) hardware that lacks WPA support 
is it better to stick with 7.x for now? Any patches available or a rough 
ETA? Is there a specific set of 8-CURRENT commits before which WEP is 
known (or strongly suspected) to work? Anything others can do to help 
besides ask annoying questions? (Sadly I'm not quite enough of a kernel 
hacker to adopt maintainership of wi.)

Thanks!

JN
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
FreeBSD Tinderbox | 1 Sep 2009 06:20
Picon
Favicon

[head tinderbox] failure on i386/i386

TB --- 2009-09-01 02:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2009-09-01 02:20:00 - starting HEAD tinderbox run for i386/i386
TB --- 2009-09-01 02:20:00 - cleaning the object tree
TB --- 2009-09-01 02:20:43 - cvsupping the source tree
TB --- 2009-09-01 02:20:43 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile
TB --- 2009-09-01 02:22:00 - building world
TB --- 2009-09-01 02:22:00 - MAKEOBJDIRPREFIX=/obj
TB --- 2009-09-01 02:22:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2009-09-01 02:22:00 - TARGET=i386
TB --- 2009-09-01 02:22:00 - TARGET_ARCH=i386
TB --- 2009-09-01 02:22:00 - TZ=UTC
TB --- 2009-09-01 02:22:00 - __MAKE_CONF=/dev/null
TB --- 2009-09-01 02:22:00 - cd /src
TB --- 2009-09-01 02:22:00 - /usr/bin/make -B buildworld
>>> World build started on Tue Sep  1 02:22:01 UTC 2009
>>> 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 Tue Sep  1 03:27:03 UTC 2009
TB --- 2009-09-01 03:27:03 - generating LINT kernel config
TB --- 2009-09-01 03:27:03 - cd /src/sys/i386/conf
TB --- 2009-09-01 03:27:03 - /usr/bin/make -B LINT
(Continue reading)

Permalink | Reply | 0 comments |
headers
pluknet | 1 Sep 2009 08:55
Picon

Re: [beta3] ld-elf Undefined symbol

2009/9/1 Aristedes Maniatis <ari <at> ish.com.au>:
> Upgraded an amd64 FreeBSD machine from beta 2 to beta 3 via freebsd-update.
> When trying to use the bacula port (a backup tool), the application will die
> with the following error:
>
> /libexec/ld-elf.so.1: /usr/local/sbin/bacula-dir: Undefined symbol
> "_ZN5BSOCK18set_source_addressEP5dlist"
>
> Naturally we have rebuilt all ports and rebuilt (just to be sure) all ports
> that bacula depends on. Is this a bug in beta3 or something we are doing
> wrong?
>

Hi. Quoting Ken Smith:

"There was a shared library version bump after BETA2 was
announced (bump was done July 19th with svn commit r195767) so
if you update a system that was last rebuilt earlier than that it would
be a good idea to rebuild all user-level applications including the
ports/packages."

You definitely need to rebuild all installed packages.

--

-- 
wbr,
pluknet
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hans Petter Selasky | 1 Sep 2009 08:56
X-Face

Re: [PATCH] USB Harddrive not recognized (umass appears, da0 not)

On Tuesday 01 September 2009 01:26:57 Tobias Grosser wrote:
> On Mon, 2009-08-31 at 21:07 +0200, Bernd Walter wrote:
> > On Mon, Aug 31, 2009 at 06:59:18PM +0200, Tobias Grosser wrote:
> > > On Mon, 2009-08-31 at 11:52 +0200, Bernd Walter wrote:
> > > > On Sun, Aug 30, 2009 at 07:09:29PM +0200, Hans Petter Selasky wrote:
> > > > > Hi,
> > > > >
> > > > > I looks like your device is hanging on SCSI command
> > > > > 0x12,00,00,00,4a,00
> > > >
> > > > 0x12 is an inquiry, which is bad if the device has problems with.
> > >
> > > I tried Linux on the same computer and the drive worked without any
> > > problems.
> >
> > If those are timestamps then there is a 5 second delay.
> > I wouldn't say that this is without problems.
> > Maybe Linux just has a different handling of the case.
> >
> > > ---------------------------------------
> > > linux_dmesg.log is attached.
> > > ---------------------------------------
> > >
> > > There was also another report where the drive did not work on FreeBSD.
> > > I mailed the user and he did not get it to run on FreeBSD, but his
> > > drive also works on Linux.
> > >
> > > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028999
> > >.html
> > >
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nick Hibma | 1 Sep 2009 09:31
Favicon
Gravatar

Reducing noise in dmesg output

Folks,

dmesg is getting cluttered with random bits of irrelevant information which 
either should be behind bootverbose or not at all present. Below two 
locations where I intend to remove that information. The fact that a module 
is loaded can be seen in the output of

	kldstat -v | grep netsmb

the amount of stolen memory and aperture size might be interesting when 
configuring your X server. Then again, most X servers nowadays HAVE no 
configuration file anymore because of auto-configuration.

Any objections?

Nick

Index: kern/kern_shutdown.c
===================================================================
--- kern/kern_shutdown.c	(revision 196710)
+++ kern/kern_shutdown.c	(working copy)
 <at>  <at>  -581,6 +581,10  <at>  <at> 

 /*
  * Support for poweroff delay.
+ *
+ * Please note that setting this delay too short might power off your 
machine
+ * before the write cache on your hard disk has been flushed, leading to
+ * soft-updates inconsistencies.
(Continue reading)

Permalink | Reply | 18 comments |
headers
Rink Springer | 1 Sep 2009 10:08
Picon
Favicon

Re: Reducing noise in dmesg output

Hi Nick,

On Tue, Sep 01, 2009 at 09:31:16AM +0200, Nick Hibma wrote:
> dmesg is getting cluttered with random bits of irrelevant information which 
> either should be behind bootverbose or not at all present. Below two 
> locations where I intend to remove that information. The fact that a module 
> is loaded can be seen in the output of

I'd say this is an useful change; the netsmb messages seem just
leftovers from debugging and I never saw the need for the aperture size
either (granted, I don't know what it indicates...)

Regards,

--

-- 
Rink P.W. Springer                                - http://rink.nu
"Beauty often seduces us on the road to truth."
- Dr. Wilson
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |

Gmane