OK, but what this does not explain is why I do not see this if
its so easily reproduced, what causes the failure case, any idea?
As I said, given the code was not feasible for igb anyway I would not
be unhappy about returning to the old way of doing things.
Jack
On Wed, May 4, 2011 at 11:03 PM,
Hello,
on freebsd version 6 and 7 I was relaying on bsdlabel to get block size :
# bsdlabel /dev/mirror/gm4s1
# /dev/mirror/gm4s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 419430404.2BSD 2048 16384 28528
b: 8388608 4194304 swap
c: 29
Hi,
On Thu, May 5, 2011 at 1:20 AM, Arnaud Lacombe wrote:
> Hi,
>
> On Wed, May 4, 2011 at 5:38 PM, Jack Vogel wrote:
>> I have had my validation engineer busy all day, we have tried both
>> a 9 kernel as well as 8.2, using the code from HEAD, and we
>> cannot reproduce this problem.
>>
> Actua
Hi,
On Wed, May 4, 2011 at 5:38 PM, Jack Vogel wrote:
> I have had my validation engineer busy all day, we have tried both
> a 9 kernel as well as 8.2, using the code from HEAD, and we
> cannot reproduce this problem.
>
Actually, it can be trivially reproduced by tainting `error'. As it is
unini
OK, but the reason you see the multiple cases of irq 16 is that's the
bridge,
once you are using MSIX, as vmstat shows, its using other vectors.
Can you capture the messages file with the actual storm happening?
I noticed some complaints about checksums in the dmesg, have you
checked on BIOS upgr
On Thursday 05 May 2011 00:15:43 you wrote:
> This all looks completely kosher, what IRQ is the storm on??
IRQ 16. Further down this email there is a list of devices that share the IRQ
according to 'dmesg'.
> On Wed, May 4, 2011 at 3:04 PM, Daan Vreeken wrote:
> > Hi,
> >
> > On Wednesday 04
2011/5/4 Jack Vogel :
> This is the second report in a matter of a week perhaps about a problematic
> motherboard, I would like to know who makes them.
Just for the record, the motherboard with which I had problems (I
guess my problem is here referred) is VIA EPIA SN1. It's nothing
new, and pr
Right, it was you Wiktor :) Oh, so yours is sort of a special case.
Thanks,
Jack
On Wed, May 4, 2011 at 3:27 PM, Wiktor Niesiobedzki wrote:
> 2011/5/4 Jack Vogel :
> > This is the second report in a matter of a week perhaps about a
> problematic
> > motherboard, I would like to know who make
This all looks completely kosher, what IRQ is the storm on??
Jack
On Wed, May 4, 2011 at 3:04 PM, Daan Vreeken wrote:
> Hi,
>
> On Wednesday 04 May 2011 20:47:32 Jack Vogel wrote:
> > Will you please set it back to a default and then boot and capture the
> > message for me?
>
> No problem. He
Hi,
On Wednesday 04 May 2011 20:47:32 Jack Vogel wrote:
> Will you please set it back to a default and then boot and capture the
> message for me?
No problem. Here's the output with MSI/MSIX enabled :
http://vehosting.nl/pub_diffs/dmesg_plantje2_with_msix_2011_05_04.txt
I've also added t
Hi,
On Wed, May 4, 2011 at 5:38 PM, Jack Vogel wrote:
> I have had my validation engineer busy all day, we have tried both
> a 9 kernel as well as 8.2, using the code from HEAD, and we
> cannot reproduce this problem.
>
> The data your netstat -m shows suggests to me that what's happening
> is s
I have had my validation engineer busy all day, we have tried both
a 9 kernel as well as 8.2, using the code from HEAD, and we
cannot reproduce this problem.
The data your netstat -m shows suggests to me that what's happening
is somehow setup of the receive ring is running more than once maybe??
> On 2011-Apr-25 20:33:14 -0400, Rick Macklem
> wrote:
> >I believe that the new/experimental NFS client in head is now
> >compatible with the old/regular NFS client.
>
> Possibly even too compatible...
>
> Both the old and new NFS clients assume a 1:1 mapping between NFS
> error codes (NFSERR_*
2011/5/4 Arnaud Lacombe :
> Obviously, I am no longer the only one finding that em(4) has
> unacceptable issue, this thread is the proof.
Right, and Jack seems to be willing to help, he asked something (I'll
reply tomorrow when I'll be in front of the hardware) and is trying to
find the same hardw
Will you please set it back to a default and then boot and capture the
message for me?
Thank you,
Jack
On Wed, May 4, 2011 at 11:19 AM, Daan Vreeken wrote:
> Hi Jack,
>
> Wednesday 04 May 2011 19:46:05 Jack Vogel wrote:
> > Who makes your motherboard? The problem you are having is that MSIX A
Hi Jack,
Wednesday 04 May 2011 19:46:05 Jack Vogel wrote:
> Who makes your motherboard? The problem you are having is that MSIX AND
> MSI are both failing as em0 comes up, so it falls back to Legacy interrupt
> mode,
> and must be having some issue with sharing the line, causing the storm.
The mo
Who makes your motherboard? The problem you are having is that MSIX AND
MSI are both failing as em0 comes up, so it falls back to Legacy interrupt
mode,
and must be having some issue with sharing the line, causing the storm.
This is the second report in a matter of a week perhaps about a problemat
Hi,
On Wed, May 4, 2011 at 1:24 PM, Jack Vogel wrote:
> No, I do not Arnaud. But I refuse to rise to rude and uncivil behavior. Its
> your
> behavior again and again which causes you to not get responses, not my
> willingness to help and respond to those that behave like respectful
> customers
>
No, I do not Arnaud. But I refuse to rise to rude and uncivil behavior. Its
your
behavior again and again which causes you to not get responses, not my
willingness to help and respond to those that behave like respectful
customers
and adults.
Jack
On Wed, May 4, 2011 at 10:20 AM, Arnaud Lacombe
Hi,
On Tue, May 3, 2011 at 7:25 PM, Olivier Smedts wrote:
> 2011/5/4 Arnaud Lacombe :
>> A more rude version might be "Why the frak my network adapter stopped
>> working with the default setting ?" :)
>
> ...on a -STABLE branch
>
Maybe you should not have picked the rude version, Jack has a
relat
Hi,
On Wed, May 4, 2011 at 3:58 AM, Olivier Smedts wrote:
> em0: Using an MSI interrupt
> em0: Ethernet address: d4:85:64:b2:aa:f5
> em0: Could not setup receive structures
> em0: Could not setup receive structures
>
> What can we do to help you debug this ?
>
At some point in time, in late Febru
2011/5/4 Kostik Belousov :
> On Tue, May 03, 2011 at 11:58:49PM -0700, Garrett Cooper wrote:
>> On Tue, May 3, 2011 at 11:42 PM, Garrett Cooper wrote:
>> > On Tue, May 3, 2011 at 10:59 PM, Kirk McKusick
>> > wrote:
>> >>> Date: Tue, 3 May 2011 22:40:26 -0700
>> >>> Subject: Nasty non-recursive l
On Wed, May 4, 2011 at 8:16 AM, krad wrote:
> On 4 May 2011 04:13, Jason Hellenthal wrote:
>> Edwin,
>>
>> >>> >> /dev/acd0 /cdrom cd9660 ro,noauto 0
>> 0
>> >>> >> /dev/acd1 /cdrom1 cd9660 ro,noauto 0
>> 0
>>
>> As a side note. T
On 4 May 2011 04:13, Jason Hellenthal wrote:
>
> Edwin,
>
> >>> >> /dev/acd0 /cdrom cd9660 ro,noauto 0
> 0
> >>> >> /dev/acd1 /cdrom1 cd9660 ro,noauto 0
> 0
>
> As a side note. These are also now useless & can be sent to /dev/null
Hi All,
I've just updated a machine to -current (r221321) and since then I'm seeing an
interrupt storm on irq 16. The storm goes away when I disable MSI/MSIX with
the following lines in "loader.conf" :
hw.pci.enable_msix="0"
hw.pci.enable_msi="0"
According to "dmesg" the follow
On Tuesday, May 03, 2011 7:49:29 pm Michael Butler wrote:
> > I have WIP patches to fix this but they aren't ready yet.
> >
> >> pcib4: I/O decode0x4000-0x4fff
> >> pcib4: memory decode 0xf090-0xf09f
> >> *** this memory widow is what I expected all children to allocate fro
On 2011-05-04 15:44, Manfred Antar wrote:
...
src.conf:
WITHOUT_DYNAMICROOT=yes
WITH_IDEA=yes
.if !defined(CC) || ${CC} == "cc"
CC=clang
.endif
.if !defined(CXX) || ${CXX} == "c++"
CXX=clang++
.endif
#Don't die on warnings
NO_WERROR=
WERROR=
Aha. Please move the clang-related stuff to make.co
At 11:38 PM 5/3/2011, Dimitry Andric wrote:
>On 2011-05-04 03:07, Manfred Antar wrote:
>>I get this error when trying to buildworld on current i386.
>>It's been this way for awhile Any Ideas ?
>>
>>===> boot/i386/boot0 (all)
>>clang -O2 -pipe -DVOLUME_SERIAL -DPXE -DFLAGS=0x8f -DTICKS=0xb6
>>-
After building FreeBSD 9.0/amd64 (FreeBSD 9.0-CURRENT #182 r221413: Tue
May 3 23:30:11 CEST 2011), the opensource office software LibreOffice
(libreoffice-3.3.2) won't start and crashes with
pid 53801 (soffice.bin), uid 8152: exited on signal 8 (core dumped)
(shown in console).
What's wrong?
On Tue, May 03, 2011 at 11:50:53PM +0200, Michael Schmiedgen wrote:
> On 03.05.2011 23:24, Jack Vogel wrote:
> > If you get the setup receive structures fail, then increase the nmbclusters.
> >
> > If you use standard MTU then what you need are mbufs, and standard size
> > clusters (2K).
> > Only w
> Date: Tue, 3 May 2011 22:40:26 -0700
> Subject: Nasty non-recursive lockmgr panic on softdep only enabled UFS
> partition when filesystem full
> From: Garrett Cooper
> To: Jeff Roberson ,
> Marshall Kirk McKusick
> Cc: FreeBSD Current
>
> Hi Jeff and Dr. McKusick,
> Ran into this
On 05/04/11 09:00, Dimitry Andric wrote:
On 2011-05-03 20:53, O. Hartmann wrote:
...
ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 �-o
gcrt1.o -r
crt1_s.o gcrt1_c.o
ld: Relocatable linking with relocations from format
elf64-x86-64-freebsd
(crt1_s.o) to format elf32-i386-freebsd (gcrt
On 05/04/11 09:00, Dimitry Andric wrote:
On 2011-05-03 20:53, O. Hartmann wrote:
...
ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 �-o
gcrt1.o -r
crt1_s.o gcrt1_c.o
ld: Relocatable linking with relocations from format
elf64-x86-64-freebsd
(crt1_s.o) to format elf32-i386-freebsd (gcrt
On 2011-Apr-25 20:33:14 -0400, Rick Macklem wrote:
>I believe that the new/experimental NFS client in head is now
>compatible with the old/regular NFS client.
Possibly even too compatible...
Both the old and new NFS clients assume a 1:1 mapping between NFS
error codes (NFSERR_* macros defined in
On Tue, May 03, 2011 at 08:13:41PM +0200, Guido Falsi wrote:
> On 05/03/11 19:19, Francois Gerodez wrote:
> >Hi all,
> >
> >I'm currently running FreeBSD 8.1 (latest update) and I'm experiencing a
> >similar issue. HTML5 videos are very laggy (both image and sound) with
> >Firefox 4. I ended up ins
Yes, I understand this, but the same issue occurs on 8.x branch...
But, I turned off all options for debugging and rebuild the kernel.
Issue has not disappeared.
On Tue, 3 May 2011 15:59:23 +
Holger Kipp wrote:
> Dear Vitaly,
>
> I'm usually not using FreeBSD for accessing youtube, but
>
On Tue, May 03, 2011 at 11:58:49PM -0700, Garrett Cooper wrote:
> On Tue, May 3, 2011 at 11:42 PM, Garrett Cooper wrote:
> > On Tue, May 3, 2011 at 10:59 PM, Kirk McKusick
> > wrote:
> >>> Date: Tue, 3 May 2011 22:40:26 -0700
> >>> Subject: Nasty non-recursive lockmgr panic on softdep only enabl
On 4 May 2011 10:42, Garrett Cooper wrote:
> On Tue, May 3, 2011 at 10:59 PM, Kirk McKusick wrote:
>>> Date: Tue, 3 May 2011 22:40:26 -0700
>>> Subject: Nasty non-recursive lockmgr panic on softdep only enabled UFS
>>> partition when filesystem full
>>> From: Garrett Cooper
>>> To: Jeff Roberso
On 2011-05-04 09:17, O. Hartmann wrote:
...
But when I tried to compile essential ports (essential to me), like
x11-wm/windowmaker, mulitmedia/ffmpeg, for instance, I run into serious
compiler/assembler error with LLVM/CLANG. I guess the ports- tree isn't
mature for clang.
Several patches for t
2011/5/4 O. Hartmann :
>
> But when I tried to compile essential ports (essential to me), like
> x11-wm/windowmaker, mulitmedia/ffmpeg, for instance, I run into serious
> compiler/assembler error with LLVM/CLANG. I guess the ports- tree isn't
> mature for clang. So am I right in this thinking: leav
2011/5/4 Jack Vogel :
> It has nothing to do with load, it has to do with the prerequisites to init
> your interfaces.
> The amount you need is fixed, it doesn't vary with load. Every RX descriptor
> needs one,
> so its simple math, number-of-interfaces X number-of-queues X size of the
> ring.
>
>
On 2011-05-03 20:53, O. Hartmann wrote:
...
ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 �-o gcrt1.o -r
crt1_s.o gcrt1_c.o
ld: Relocatable linking with relocations from format elf64-x86-64-freebsd
(crt1_s.o) to format elf32-i386-freebsd (gcrt1.o) is not supported
...
Today, I tried
42 matches
Mail list logo
