lying around. I installed it in the server and
> > did
> > > PCI passthrough with it as well as the Intel in FreeBSD/bhyve.
> > > I get the same result in OpenBSD:
> > > bge0 at pci0 dev 5 function 0 "Broadcom BCM5720" rev 0x00, BCM5720 A0
> > > (0x572
functions, and it's not popular to do
>> >> > maintenance on it.
>> >> > I went ahead and rebooted it anyway since this is important ;-)
>> >> >
>> >> > I booted the OpenBSD 6.3 install media natively on the hardware.
>> >> > It foun
oard and four on the Intel card.
> >> > Broadcoms were found as bge and Intel as em. They all seemed to work.
> >> >
> >> > I had an extra bge card lying around. I installed it in the server and
> >> > did
> >> > PCI passthrough with it
ll six NICs that I have installed. There are two Broadcom on
>> > the
>> > mainboard and four on the Intel card.
>> > Broadcoms were found as bge and Intel as em. They all seemed to work.
>> >
>> > I had an extra bge card lying around. I installe
he same result in OpenBSD:
> > bge0 at pci0 dev 5 function 0 "Broadcom BCM5720" rev 0x00, BCM5720 A0
> > (0x572), APE firmware NCSI 1.4.12.0: couldn't map interrupt
> >
> > Conclusion:
> > The problem has to do with the fact that bhyve is between the ha
I installed it in the server and did
> PCI passthrough with it as well as the Intel in FreeBSD/bhyve.
> I get the same result in OpenBSD:
> bge0 at pci0 dev 5 function 0 "Broadcom BCM5720" rev 0x00, BCM5720 A0
> (0x572), APE firmware NCSI 1.4.12.0: couldn't map interrupt
>
> C
as the Intel in FreeBSD/bhyve.
I get the same result in OpenBSD:
bge0 at pci0 dev 5 function 0 "Broadcom BCM5720" rev 0x00, BCM5720 A0
(0x572), APE firmware NCSI 1.4.12.0: couldn't map interrupt
Conclusion:
The problem has to do with the fact that bhyve is between the hardware and
Ope
I boot the 6.3
> release installer I get this in dmesg:
> "em0 at pci0 dev 5 function 0 "Intel 82576" rev 0x01: couldn't map
> interrupt".
>
> The installation goes through without errors, but the Intel NIC is not
> visible during install or after r
ion 0 "Intel 82576" rev 0x01: couldn't map
interrupt".
The installation goes through without errors, but the Intel NIC is not
visible during install or after rebooting the installed system.
Man pages suggest that the problem is a fatal initialization error.
The NIC works without
their interrupts aren't mapped:
cbb0 at pci1 dev 2 function 0 Ricoh 5C476 CardBus rev 0x80: couldn't \
map interrupt
cbb1 at pci1 dev 2 function 1 Ricoh 5C476 CardBus rev 0x80: couldn't \
map interrupt
I've updated the BIOS to the latest version I can find, and am running
current (as of March 30th
interrupt
cbb1 at pci1 dev 2 function 1 Ricoh 5C476 CardBus rev 0x80: couldn't \
map interrupt
I've updated the BIOS to the latest version I can find, and am running
current (as of March 30th). This happens both with APM and with ACPI
(APM disabled); I've included both full dmesgs below
I've inherited an old notebook (Sony Vaio PCG-FX120) whose CardBus slots
are (presumably) unusable because their interrupts aren't mapped:
cbb0 at pci1 dev 2 function 0 Ricoh 5C476 CardBus rev 0x80: couldn't \
map interrupt
cbb1 at pci1 dev 2 function 1 Ricoh 5C476 CardBus rev 0x80: couldn't
On Thu, 1 Apr 2010, Dave Anderson wrote:
I've inherited an old notebook (Sony Vaio PCG-FX120) whose CardBus slots
are (presumably) unusable because their interrupts aren't mapped:
cbb0 at pci1 dev 2 function 0 Ricoh 5C476 CardBus rev 0x80: couldn't \
map interrupt
cbb1 at pci1 dev 2 function 1
And another wild shot in the dark. Do you have latest BIOS or is there
some newer for your laptop somewhere on net?
M forgout about it, just one BIOS available and you have
it http://esupport.sony.com/US/perl/swu-list.pl?mdl=PCGV505BC#div_pos_10
On Wed, Oct 21, 2009 at 4:11 AM,
And maybe game with acpidump and ASL may help you. I read about
situations when just changing Windows word for Linux in ASL helped in
some cases. I don't no so much about it, but maybe you will get some
idea and points from this text
. Townsend
Sent: Tuesday, October 20, 2009 9:12 PM
To: misc@openbsd.org
Subject: Re: couldn't map interrupt for fxp / intel PRO/100 VE after
upgrade to 4.6 (or 4.5)
The one difference on your machine between 4.4 and 4.5/4.6 is apm vs acpi
If you used the boot prompt to disable acpi, do you have access
Tomas Bodzar wrote:
And maybe game with acpidump and ASL may help you. I read about
situations when just changing Windows word for Linux in ASL helped in
some cases. I don't no so much about it, but maybe you will get some
idea and points from this text
(80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: irq 9
drm0 at radeondrm0
ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x42
pci2 at ppb1 bus 2
cbb0 at pci2 dev 5 function 0 Ricoh 5C475 CardBus rev 0xb8: couldn't map
interrupt
Ricoh 5C551
The one difference on your machine between 4.4 and 4.5/4.6 is apm vs acpi
If you used the boot prompt to disable acpi, do you have access to the
network card again?
Anathae
p.s. taking a wild shot in the dark.
at pci2 dev 8 function 0 Intel PRO/100 VE rev 0x42: couldn't
map interrupt
(this occurs when booting with the 4.5CD and, now, the upgraded system)
I took a look at the bios configuration, to see if there was some option
about interrupts, but, not surprisingly, there was not.
I am wondering what I
On Mon, Dec 8, 2008 at 9:52 PM, Daniel Melameth [EMAIL PROTECTED] wrote:
On Mon, Dec 8, 2008 at 11:28 AM, k z [EMAIL PROTECTED] wrote:
ne3 works but couldn't map interrupt errors do appear:
cbb0 at pci0 dev 19 function 0 Toshiba ToPIC97 CardBus rev 0x20:
couldn't map interrupt
cbb1 at pci0
Dear misc@,
ne3 works but couldn't map interrupt errors do appear:
cbb0 at pci0 dev 19 function 0 Toshiba ToPIC97 CardBus rev 0x20:
couldn't map interrupt
cbb1 at pci0 dev 19 function 1 Toshiba ToPIC97 CardBus rev 0x20:
couldn't map interrupt
Does this mean that there is still some limitations
On Mon, Dec 8, 2008 at 11:28 AM, k z [EMAIL PROTECTED] wrote:
ne3 works but couldn't map interrupt errors do appear:
cbb0 at pci0 dev 19 function 0 Toshiba ToPIC97 CardBus rev 0x20:
couldn't map interrupt
cbb1 at pci0 dev 19 function 1 Toshiba ToPIC97 CardBus rev 0x20:
couldn't map interrupt
vendor IDT, unknown product 0x8018 rev
0x04
pci3 at ppb2 bus 3
em0 at pci3 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map interrupt
em0: Allocation of PCI resources failed
em1 at pci3 dev 0 function 1 Intel PRO/1000 QP (82571EB) rev
: SMBIOS rev. 2.4 @ 0x3fc03000 (43 entries)
bios0: vendor Intel Corporation version
S3000.86B.02.00.0044.071120071047 date 07/11/2007
bios0: Intel S3000AHLX
: couldn't map interrupt
em0: Allocation of PCI resources failed
regards,
Thomas
[demime 1.01d removed an attachment of type application/x
bus 3
em0 at pci3 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map interrupt
em0: Allocation of PCI resources failed
em1 at pci3 dev 0 function 1 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map
now on version .44, but this dont solve my problem.
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x3fc03000 (43 entries)
bios0: vendor Intel Corporation version
S3000.86B.02.00.0044.071120071047 date 07/11/2007
bios0: Intel S3000AHLX
: couldn't map interrupt
em0: Allocation of PCI resources failed
Hi,
I got it!
I try to build a GENERIC.MP for Marco - and now its running.I cant
belive it. :)
Thank you people, for your help.
If you need some more tests with my hardware, let me know.
regards,
Thomas
# dmesg
OpenBSD 4.2-current (GENERIC.MP) #0: Mon Nov 12 08:00:48 MST 2007
now on version .44, but this dont solve my problem.
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x3fc03000 (43 entries)
bios0: vendor Intel Corporation version
S3000.86B.02.00.0044.071120071047 date 07/11/2007
bios0: Intel S3000AHLX
: couldn't map interrupt
em0: Allocation of PCI resources failed
at ppb1 bus 2
ppb2 at pci2 dev 0 function 0 vendor IDT, unknown product 0x8018 rev
0x04
pci3 at ppb2 bus 3
em0 at pci3 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map interrupt
em0: Allocation of PCI resources failed
em1 at pci3 dev 0 function 1
On Fri, 09 Nov 2007 16:45:58 +0700, Koenig, Thomas [EMAIL PROTECTED]
wrote:
Hi,
Hi,
I know what you feel.. I'm using s3000AH on release, got the
panic too. So I download -current using CVS, do compile on
GENERIC and GENERIC.MP, install them, enable acpi on UKC, and
it suddenly works :D
Hi,
I downloaded the sources from CVS and build a new GENERIC Kernel, with
the same result. :(
The Kernel panic, after enable acpi, is now: malloc: allocation too
large
regards,
Thomas
[demime 1.01d removed an attachment of type application/x-pkcs7-signature which
had a name of smime.p7s]
You need not to only enable ACPI, but also disable APM to make use of ACPI.
Koenig, Thomas wrote:
Hi,
Have you tried to enable acpi?
I try acpi with:
boot -c
enable acpi
quit
then I get a panic, with options for trace and ps - thats all. :(
maybe its a bug?
GENERIC.MP with acpi?
Showing the actual panic has more chances of something getting fixed.
On Thu, Nov 08, 2007 at 09:17:49AM +0100, Koenig, Thomas wrote:
You need not to only enable ACPI, but also disable APM to
make use of ACPI.
it takes no effekt if I disable apm or not - every time I enable acpi I
run
You need not to only enable ACPI, but also disable APM to
make use of ACPI.
it takes no effekt if I disable apm or not - every time I enable acpi I
run into a PANIC.
UKCdisable apm
UKCenable acpi
263 acpi0 enabled
UKCquit
-- PANIC :(
regards,
Thomas
[demime 1.01d removed an attachment of
Hello,
Showing the actual panic has more chances of something getting fixed.
ok - here is the panic output, I hope anyone found something:
acpi0: tables DSDT FACP APIC WDDT MCFG ASF! SSDT SSDT SSDT SSDT SSDT
acpitimer at acpi0 not configured
acpiprt0 at acpi0index.buf out of bounds: 6/6
What version of OpenBSD are you running ? Several fixes have recently
been added that made my machine suddenly support ACPI. You snipped
this (very important) piece of information. Maybe trying the latest
snapshot fixes your problem.
Please also add a full dmesg (without acpi) so we don't have to
0x8018 rev
0x04
pci3 at ppb2 bus 3
em0 at pci3 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map interrupt
em0: Allocation of PCI resources failed
em1 at pci3 dev 0 function 1 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line
On 2007/11/08 14:48, Koenig, Thomas wrote:
0706 Called: \_SB_.PCI0._CRS
panic: aml_die aml_derefvalue:1366
Stopped atDebugger+0x5: leave
ddb dmesg
OpenBSD 4.2 (GENERIC) #1179: Tue Aug 28 10:37:50 MDT 2007
Try a snapshot.
at pci2 dev 0 function 0 vendor IDT, unknown product 0x8018 rev
0x04
pci3 at ppb2 bus 3
em0 at pci3 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map interrupt
em0: Allocation of PCI resources failed
em1 at pci3 dev 0 function 1 Intel PRO/1000 QP
and em5.
dmesg shows me something like that:
em0 at pci3 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev
0x06pci_intr_map: bad interrupt line 128
: couldn't map interrupt
em0: Allocation of PCI resources failed
I think the Card itself is supported, because I have the low profile
version EXPI9404PTL
[EMAIL PROTECTED] wrote:
acpi at mainbus0 not configured
Have you tried to enable acpi? GENERIC.MP with acpi?
- Alexey.
Hi,
Have you tried to enable acpi?
I try acpi with:
boot -c
enable acpi
quit
then I get a panic, with options for trace and ps - thats all. :(
maybe its a bug?
GENERIC.MP with acpi?
Is this not the same as above?
regards,
Thomas
[demime 1.01d removed an attachment of type
43 matches
Mail list logo
