Discussion:
kernel woes
Steven Willis
2007-06-18 23:30:39 UTC
Permalink
I'm getting this error as well. I recently did a fresh re-install on
my laptop with Ubuntu and I started noticing this error on startup. I
don't think I had been getting it before. I was using 64 bit last
time, 32 this time. These seem to be the relevant lines from dmesg:

dmesg | grep 0000:02:04.[01]
[ 13.972112] PCI: Failed to allocate mem resource
#10:***@ec000000 for 0000:02:04.0
[ 13.972170] PCI: Failed to allocate mem resource
#10:***@ec000000 for 0000:02:04.1
[ 13.972224] PCI: Bus 3, cardbus bridge: 0000:02:04.0
[ 13.972248] PCI: Bus 7, cardbus bridge: 0000:02:04.1
[ 13.972940] ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK1] ->
GSI 19 (level, low) -> IRQ 16
[ 13.973527] ACPI: PCI Interrupt 0000:02:04.1[B] -> Link [LNK2] ->
GSI 18 (level, low) -> IRQ 17
[ 27.656000] Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d]
[ 27.656000] PCI: Bus 3, cardbus bridge: 0000:02:04.0
[ 27.656000] Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl 0x64
[ 27.888000] Yenta: CardBus bridge found at 0000:02:04.1 [103c:006d]
[ 27.888000] Yenta TI: socket 0000:02:04.1, mfunc 0x01111d22, devctl 0x64

I don't really use my pcmcia card slots, but I hate seeing errors on
startup and would like to know if something is wrong.

-Steve
Hi everyone,
I'm running (and have been running) a stock kernel on an R3000 with
Ubuntu for quite some time without any trouble. I've encountered some
trouble in compiling my own kernel in order to use suspend2.
I've compiled kernels before, and don't have any trouble with that part
of it, but I get some strange messages on booting. (see the end of this
message for the start of the output from dmesg). I've read the
information online regarding the pci/cardbus stuff, but I've modified
config.opts without success. Is this issue related? I'm trying to use a
2.6.15.1 kernel, and I've used my own configuration, one from another
R3000 user's website, and the wonderfully-working config that Ubuntu so
kindly set up for me. Same result either way.
Please let me know if you have any ideas! Thanks.
Tom
ACPI: PCI Interrupt Link [LUS1] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [LMCI] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [LPID] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [LTID] (IRQs 20 21 22) *0, disabled.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
PCI-DMA: Disabling IOMMU.
PCI: Bus 3, cardbus bridge: 0000:02:04.0
IO window: 00003000-000030ff
IO window: 00003400-000034ff
PREFETCH window: 30000000-31ffffff
PCI: Bus 7, cardbus bridge: 0000:02:04.1
IO window: 00003800-000038ff
IO window: 00003c00-00003cff
PREFETCH window: 32000000-33ffffff
PCI: Bridge: 0000:00:0a.0
IO window: 3000-7fff
MEM window: e0100000-e17fffff
PREFETCH window: 30000000-33ffffff
PCI: Bridge: 0000:00:0b.0
IO window: disabled.
MEM window: e2000000-e2ffffff
PREFETCH window: f0000000-f80fffff
PCI: Setting latency timer of device 0000:00:0a.0 to 64
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 19
GSI 16 sharing vector 0xB1 and IRQ 16
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK1] -> GSI 19 (level,
low) -> IRQ 16
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 18
GSI 17 sharing vector 0xB9 and IRQ 17
ACPI: PCI Interrupt 0000:02:04.1[B] -> Link [LNK2] -> GSI 18 (level,
low) -> IRQ 17
_______________________________________________
LinuxR3000 mailing list
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
John Jason Jordan
2007-06-19 06:00:01 UTC
Permalink
On Mon, 18 Jun 2007 19:30:39 -0400
Post by Steven Willis
I'm getting this error as well. I recently did a fresh re-install on
my laptop with Ubuntu and I started noticing this error on startup. I
don't think I had been getting it before. I was using 64 bit last
dmesg | grep 0000:02:04.[01]
[ 13.972112] PCI: Failed to allocate mem resource
[ 13.972170] PCI: Failed to allocate mem resource
[ 13.972224] PCI: Bus 3, cardbus bridge: 0000:02:04.0
[ 13.972248] PCI: Bus 7, cardbus bridge: 0000:02:04.1
[ 13.972940] ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK1] ->
GSI 19 (level, low) -> IRQ 16
[ 13.973527] ACPI: PCI Interrupt 0000:02:04.1[B] -> Link [LNK2] ->
GSI 18 (level, low) -> IRQ 17
[ 27.656000] Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d]
[ 27.656000] PCI: Bus 3, cardbus bridge: 0000:02:04.0
[ 27.656000] Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl 0x64
[ 27.888000] Yenta: CardBus bridge found at 0000:02:04.1 [103c:006d]
[ 27.888000] Yenta TI: socket 0000:02:04.1, mfunc 0x01111d22, devctl 0x64
I don't really use my pcmcia card slots, but I hate seeing errors on
startup and would like to know if something is wrong.
That's very interesting. I used your command above and got identical
messages, except the numbers in the brackets were different. This is on
a Compaq R3240. I don't have any PCMCIA cards, so I have no idea if the
thing works or not.

More interesting is the first two lines "failed to allocate memory
resource." I've been seeing that right after the Grub menu for at least
a year. No one has ever been able to tell me what it means.

Everything works perfectly on this computer running Ubuntu Feisty
amd64, except for one annoying problem. For some reason I get summarily
logged out sometimes. It's just like I hit Ctrl-Alt-Bkspc. Most
commonly it happens when opening a new tab in Firefox, but occasionally
it will happen in other programs too. When I tell Linux gurus about it
they shake their head in amazement. How could something just log you
out?
Tom Corr
2007-06-19 12:09:19 UTC
Permalink
On Tuesday 19 June 2007 02:00, you wrote:
yeah I get this too with my laptop... I also get this message some lines
before...

PCI: Probing PCI hardware (bus 00)
PCI: Bus #03 (-#06) is hidden behind bridge #02 (-#02)
(try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
PCI: Bus #07 (-#0a) is hidden behind bridge #02 (-#02)
(try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
Post by John Jason Jordan
On Mon, 18 Jun 2007 19:30:39 -0400
Post by Steven Willis
I'm getting this error as well. I recently did a fresh re-install on
my laptop with Ubuntu and I started noticing this error on startup. I
don't think I had been getting it before. I was using 64 bit last
dmesg | grep 0000:02:04.[01]
[ 13.972112] PCI: Failed to allocate mem resource
[ 13.972170] PCI: Failed to allocate mem resource
[ 13.972224] PCI: Bus 3, cardbus bridge: 0000:02:04.0
[ 13.972248] PCI: Bus 7, cardbus bridge: 0000:02:04.1
[ 13.972940] ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK1] ->
GSI 19 (level, low) -> IRQ 16
[ 13.973527] ACPI: PCI Interrupt 0000:02:04.1[B] -> Link [LNK2] ->
GSI 18 (level, low) -> IRQ 17
[ 27.656000] Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d]
[ 27.656000] PCI: Bus 3, cardbus bridge: 0000:02:04.0
[ 27.656000] Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl
0x64 [ 27.888000] Yenta: CardBus bridge found at 0000:02:04.1
[103c:006d] [ 27.888000] Yenta TI: socket 0000:02:04.1, mfunc
0x01111d22, devctl 0x64
I don't really use my pcmcia card slots, but I hate seeing errors on
startup and would like to know if something is wrong.
That's very interesting. I used your command above and got identical
messages, except the numbers in the brackets were different. This is on
a Compaq R3240. I don't have any PCMCIA cards, so I have no idea if the
thing works or not.
More interesting is the first two lines "failed to allocate memory
resource." I've been seeing that right after the Grub menu for at least
a year. No one has ever been able to tell me what it means.
Everything works perfectly on this computer running Ubuntu Feisty
amd64, except for one annoying problem. For some reason I get summarily
logged out sometimes. It's just like I hit Ctrl-Alt-Bkspc. Most
commonly it happens when opening a new tab in Firefox, but occasionally
it will happen in other programs too. When I tell Linux gurus about it
they shake their head in amazement. How could something just log you
out?
_______________________________________________
LinuxR3000 mailing list
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
John Jason Jordan
2007-06-21 03:31:05 UTC
Permalink
On Tue, 19 Jun 2007 08:09:19 -0400
Post by Tom Corr
yeah I get this too with my laptop... I also get this message some lines
before...
PCI: Probing PCI hardware (bus 00)
PCI: Bus #03 (-#06) is hidden behind bridge #02 (-#02)
(try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
PCI: Bus #07 (-#0a) is hidden behind bridge #02 (-#02)
(try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
I decided to try pci=assign-busses. My R3240 with Feisty amd64 would
not start X. I got dumped to a command line.

I still get suddenly logged out about once a day. But it always happens
on a mouse click, and the more windows that are open, the more likely
it is to happen. Having multiple tabs open in Firefox is dangerous. I'm
suspecting something about the mouse driver and Gnome. If anyone has
any further suggestions, I'm all ears.
Frank Edwards
2007-06-22 00:41:07 UTC
Permalink
Post by John Jason Jordan
I decided to try pci=assign-busses. My R3240 with Feisty amd64 would
not start X. I got dumped to a command line.
I still get suddenly logged out about once a day. But it always
happens on a mouse click, and the more windows that are open, the
more likely it is to happen. Having multiple tabs open in Firefox is
dangerous. I'm suspecting something about the mouse driver and Gnome.
If anyone has any further suggestions, I'm all ears.
Here's the dmesg(1) dump from Ubuntu 6.10 on my R3000Z (output from
lshw(8) indicates an R3200 DP533AV as the product ID, motherboard has
Post by John Jason Jordan
[17179573.808000] PCI: Probing PCI hardware (bus 00)
[17179573.836000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:08.0
[17179573.836000] PCI: Bus #03 (-#06) is hidden behind bridge #02
(-#02) (try ' pci=assign-busses')
[17179573.836000] Please report the result to linux-kernel to fix
this permanent ly
[17179573.836000] PCI: Bus #07 (-#0a) is hidden behind bridge #02
(-#02) (try ' pci=assign-busses')
[17179573.836000] Please report the result to linux-kernel to fix
this permanent ly
Yet I'm not having any problems whatsoever. My kernel boot line is

kernel /boot/vmlinuz-2.6.17-11-generic root=/dev/hda3 ro quiet splash

You can see which version of the kernel I'm running, I guess. :) I'm
running the F.35 firmware (which will have an impact on the ACPI data
that the BIOS is storing, I think).

Based on the symptoms you describe, I would almost guess a memory
problem. You might try using a live CD and running the memory test
(Ubuntu, Knoppix, and Fedora have memtest86, I think?). If not, Google
for "memtest86+.bin", then add the following to
Post by John Jason Jordan
title memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
Of course, you'll need to adjust the "root" line to be the same as your
other "root" lines. And be sure to put the downloaded file into /boot
(again, as you would expect from the excerpt).

If you'd like a copy of my entire dmesg(1) output, send me a personal
email.
--
Frank J. Edwards
Edwards & Edwards Consulting, LLC
Voice: (813) 996-7954
Email: ***@eec.com
Large Attachments To: ***@gmail.com
Loading...