wellll..... Somebody broke into my house (two weeks ago) and stole my lovely Debian machine...
So it is very hard for me to know ;-) I hope they did not remove the Debian install from it and that they are using it and enjoying it too (it was a good setup) some thing good might come out of this incident.after all. i will probably get some money from the insurance and get a new machine. I guess, if we see more activity (here) with this issue it is probably those who took the machine ;-) As you can read (see) i really needed to express my parting with this beautiful Debian machine but after all... i guess it is time to close this issue down. 2008/12/21 Moritz Muehlenhoff <j...@inutil.org> > On Mon, Jan 21, 2008 at 09:59:48PM +0200, Nadav Kavalerchik wrote: > > Package: linux-image-2.6.23-1-686 > > Version: 2.6.23-2 > > Severity: normal > > File: kernel > > > > after upgrading one of the two 256MB RAM sims i have (on my Compaq > presario > > 1500) to 1GB simm, i was starting to get these errors or warnings in the > > kernel's log file: > > PCI: Using ACPI for IRQ routing > > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a > report > > PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0 > > PCI: Cannot allocate resource region 9 of bridge 0000:00:01.0 > > PCI: Cannot allocate resource region 8 of bridge 0000:00:1e.0 > > PCI: Cannot allocate resource region 0 of device 0000:01:00.0 > > PCI: Cannot allocate resource region 2 of device 0000:01:00.0 > > PCI: Cannot allocate resource region 0 of device 0000:02:05.0 > > PCI: Cannot allocate resource region 1 of device 0000:02:05.0 > > PCI: Cannot allocate resource region 0 of device 0000:02:06.0 > > PCI: Cannot allocate resource region 0 of device 0000:02:08.0 > > PCI: Cannot allocate resource region 0 of device 0000:02:0e.0 > > PCI: Cannot allocate resource region 0 of device 0000:02:0e.1 > > PCI: Cannot allocate resource region 0 of device 0000:02:0e.2 > > > > i use the entire memory without any problem so i'm not sure if this and > error > > i am not aware of (yet) or just a warning ? > > Does this message still occur with more recent kernel versions? > > Cheers, > Moritz >
