On Fri 2010-09-10 (10:43), Jack Vogel wrote:
No, not the add-on adapter, i have no trouble finding those, what I want to
know about is the details about the system that has em0 LOM, only
way to check on that is to have the whole enchilada :)
Ah right. These are snippets from dmidecode, is
We don't deal with desktop systems that much in my group, it was pointed out
by a coworker that the BIOS has settings that could disable MSI, please
check
out how yours is set.
Jack
On Mon, Sep 13, 2010 at 7:42 AM, Gareth de Vaux b...@lordcow.org wrote:
On Fri 2010-09-10 (10:43), Jack Vogel
On Fri 2010-09-10 (10:41), Gareth de Vaux wrote:
Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at boot
btw.
Ok, I'll have to get back to you in a day or 2 when I reboot.
Done:
$ sysctl -a | grep msi
hw.bce.msi_enable: 1
hw.pci.honor_msi_blacklist: 0
hw.pci.enable_msix:
On Thu 2010-09-09 (17:00), Gareth de Vaux wrote:
On Thu 2010-09-09 (16:54), Kurt Jaeger wrote:
-c asks for pci device capabilities, which are read in
/usr/src/usr.sbin/pciconf/pciconf.c:177 with O_RDWR
Ah. I'll have to schedule a reboot then ..
pciconf -lcv,
onboard:
On Sun, Sep 12, 2010 at 1:15 AM, Gareth de Vaux b...@lordcow.org wrote:
On Fri 2010-09-10 (10:41), Gareth de Vaux wrote:
Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at
boot
btw.
Ok, I'll have to get back to you in a day or 2 when I reboot.
Done:
$ sysctl -a |
John Baldwin j...@freebsd.org wrote:
On Friday, September 10, 2010 2:55:15 am per...@pluto.rain.com wrote:
...
It is arguably a bug to open O_RDWR when only examining things.
You have to have RDWR permission to issue the ioctl to read config
registers which pciconf does when examining
per...@pluto.rain.com wrote:
John Baldwin j...@freebsd.org wrote:
On Friday, September 10, 2010 2:55:15 am per...@pluto.rain.com wrote:
...
It is arguably a bug to open O_RDWR when only examining things.
You have to have RDWR permission to issue the ioctl to read config
registers which
Gareth de Vaux b...@lordcow.org wrote:
On Thu 2010-09-09 (16:54), Kurt Jaeger wrote:
-c asks for pci device capabilities, which are read in
/usr/src/usr.sbin/pciconf/pciconf.c:177 with O_RDWR
Ah. I'll have to schedule a reboot then ..
or hack on pciconf.c to not request more permission
On Thu 2010-09-09 (13:48), Jack Vogel wrote:
Gareth's email bouncing for anybody else or is it just me?
Yes sorry I disabled this alias after picking up years of spam on the
mailman archives. I assumed people would primarily reply to the list.
I've re-enabled it for now.
Gareth, set
On Fri 2010-09-10 (10:41), Gareth de Vaux wrote:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058748.html
Just to reiterate - those are the specs of the PCI card that doesn't
work. The PCI card doesn't come up with MSIX failures. The onboard
has the MSIX failures but
On Friday, September 10, 2010 2:55:15 am per...@pluto.rain.com wrote:
Gareth de Vaux b...@lordcow.org wrote:
On Thu 2010-09-09 (16:54), Kurt Jaeger wrote:
-c asks for pci device capabilities, which are read in
/usr/src/usr.sbin/pciconf/pciconf.c:177 with O_RDWR
Ah. I'll have to
On Fri, Sep 10, 2010 at 1:41 AM, Gareth de Vaux b...@lordcow.org wrote:
On Thu 2010-09-09 (13:48), Jack Vogel wrote:
Gareth's email bouncing for anybody else or is it just me?
Yes sorry I disabled this alias after picking up years of spam on the
mailman archives. I assumed people would
On Wed 2010-09-08 (09:41), Jack Vogel wrote:
This is what'd I'd expect, the onboard is PCH chipset, support was not in
8.0, but as I said, in 8.1 (and hence stable/8) it is supported, and it should
work.
I've just paid the machine a visit and yes, MSIX fails on the onboard but
the device still
On Thu, Sep 09, 2010 at 02:54:01PM +0200, Gareth de Vaux wrote:
On Wed 2010-09-08 (09:41), Jack Vogel wrote:
This is what'd I'd expect, the onboard is PCH chipset, support was not in
8.0, but as I said, in 8.1 (and hence stable/8) it is supported, and it
should
work.
I've just paid
On Thu 2010-09-09 (06:13), Jeremy Chadwick wrote:
Can you add the -c flag to your pciconf command? Thanks.
Forbidden?
# pciconf -lvc
pciconf: /dev/pci: Operation not permitted
# pciconf -lc
pciconf: /dev/pci: Operation not permitted
# ls -l /dev/pci
crw-r--r-- 1 root wheel0, 9 Sep 9
On Thu, Sep 09, 2010 at 03:25:19PM +0200, Gareth de Vaux wrote:
On Thu 2010-09-09 (06:13), Jeremy Chadwick wrote:
Can you add the -c flag to your pciconf command? Thanks.
Forbidden?
# pciconf -lvc
pciconf: /dev/pci: Operation not permitted
# pciconf -lc
pciconf: /dev/pci: Operation
On Thu 2010-09-09 (07:02), Jeremy Chadwick wrote:
You need to be root to use the -c flag. Despite your prompt, I don't
think you're root. Reproduction:
That was as root,
# id
uid=0(root) gid=0(wheel) groups=0(wheel),5(operator)
# pciconf -lc
pciconf: /dev/pci: Operation not permitted
On Thu, Sep 09, 2010 at 04:22:26PM +0200, Gareth de Vaux wrote:
On Thu 2010-09-09 (07:02), Jeremy Chadwick wrote:
You need to be root to use the -c flag. Despite your prompt, I don't
think you're root. Reproduction:
That was as root,
# id
uid=0(root) gid=0(wheel)
On Thu 2010-09-09 (07:24), Jeremy Chadwick wrote:
Is this within a jail or something else along those lines? I can't
reproduce the problem otherwise. Frustrating! Someone else on the list
might have ideas as to what could cause this.
Nope, this's a normal host. I've got securelevel on 1,
Hi!
Is this within a jail or something else along those lines? I can't
reproduce the problem otherwise. Frustrating! Someone else on the list
might have ideas as to what could cause this.
Nope, this's a normal host. I've got securelevel on 1, but doubt that
would affect this?
I
On Thu, Sep 9, 2010 at 4:22 PM, Gareth de Vaux b...@lordcow.org wrote:
On Thu 2010-09-09 (07:02), Jeremy Chadwick wrote:
You need to be root to use the -c flag. Despite your prompt, I don't
think you're root. Reproduction:
That was as root,
# id
uid=0(root) gid=0(wheel)
Hi!
Is this within a jail or something else along those lines? I can't
reproduce the problem otherwise. Frustrating! Someone else on the list
might have ideas as to what could cause this.
Nope, this's a normal host. I've got securelevel on 1, but doubt that
would affect this?
Jeremy Chadwick wrote:
On Thu, Sep 09, 2010 at 04:22:26PM +0200, Gareth de Vaux wrote:
On Thu 2010-09-09 (07:02), Jeremy Chadwick wrote:
You need to be root to use the -c flag. Despite your prompt, I don't
think you're root. Reproduction:
That was as root,
# id
uid=0(root)
On Thu 2010-09-09 (16:54), Kurt Jaeger wrote:
-c asks for pci device capabilities, which are read in
/usr/src/usr.sbin/pciconf/pciconf.c:177 with O_RDWR
Ah. I'll have to schedule a reboot then ..
___
freebsd-stable@freebsd.org mailing list
On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger p...@opsec.eu wrote:
Hi!
Is this within a jail or something else along those lines? I can't
reproduce the problem otherwise. Frustrating! Someone else on the
list
might have ideas as to what could cause this.
Nope, this's a normal
Hi!
Basically, when the securelevel is positive, the kernel restricts
certain tasks; not even the superuser (i.e., root) is allowed to
do them.
OH YUCK, another root isn't really root, so is it also possibly
the reason for the MSIX failure?? Is this pile, er feature, on by default?
No,
On Thu, Sep 9, 2010 at 11:37 AM, John Baldwin j...@freebsd.org wrote:
On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote:
On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger p...@opsec.eu wrote:
Hi!
Is this within a jail or something else along those lines? I can't
Gareth's email bouncing for anybody else or is it just me?
Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at boot
btw.
Tell me more exactly the make/model of the hardware so I might try to get
my hands on one?
Jack
On Thu, Sep 9, 2010 at 1:20 PM, John Baldwin
On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote:
On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger p...@opsec.eu wrote:
Hi!
Is this within a jail or something else along those lines? I can't
reproduce the problem otherwise. Frustrating! Someone else on the
list
might
On Thursday, September 09, 2010 3:04:27 pm Jack Vogel wrote:
On Thu, Sep 9, 2010 at 11:37 AM, John Baldwin j...@freebsd.org wrote:
On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote:
On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger p...@opsec.eu wrote:
Hi!
Is this
On Tue 2010-09-07 (10:00), Jack Vogel wrote:
First off, this device was not supported in 8.0 REL, what were you running
that last worked?
Hey, I was running 8.0 REL and it worked. I installed the system from the
8.0 .iso, but the onboard card didn't work. I added the PCI card and it
worked.
On Tue 2010-09-07 (13:25), Jack Vogel wrote:
I've looked at the code, this message was misleading, what really happens
is that the driver fails to be able to setup either MSIX OR MSI, when this
happens it will fall back and use a Legacy interrupt, so its non-fatal and
the device should work
This is what'd I'd expect, the onboard is PCH chipset, support was not in
8.0,
but as I said, in 8.1 (and hence stable/8) it is supported, and it should
work.
I do not know why you don't have MSI support, but it should still work with
Legacy interrupts.
Jack
On Wed, Sep 8, 2010 at 2:40 AM,
Email to Gareth de Vaux is bouncing :(
First off, this device was not supported in 8.0 REL, what were you running
that last
worked?
Do you have MSI disabled on this system of yours, the reason for this
message
is that both MSIX and MSI setup failed, your device should succeed with MSI.
Tell me
I've looked at the code, this message was misleading, what really happens
is that the driver fails to be able to setup either MSIX OR MSI, when this
happens it will fall back and use a Legacy interrupt, so its non-fatal and
the device should work anyway.
The only real reason you should see this
In the future make sure that you put E1000 or EM in the title otherwise I
might miss it,
fortunately I looked at this :)
I'm on a holiday weekend, I will investigate this tomorrow.
Jack
On Mon, Sep 6, 2010 at 8:53 AM, Gareth de Vaux b...@lordcow.org wrote:
Hi all, I moved from 8.0-RELEASE to
36 matches
Mail list logo
