[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#594095: marked as done (linux-2.6: address space collision on of device [0xfebe0000-0xfebe7fff])

Your message dated Fri, 27 Aug 2010 05:07:22 +0100
with message-id <1282882042.22839.846.camel@localhost>
and subject line Re: snapshot.debian.org: address space collision on of device [0xfebe0000-0xfebe7fff]
has caused the Debian Bug report #594095,
regarding linux-2.6: address space collision on of device [0xfebe0000-0xfebe7fff]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
594095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594095
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: snapshot.debian.org
Severity: normal


Soon after booting apears one error-message about "space collusion" or so.
It disappears so fast, that I can not report exatly.

In "dmesg" are the following lines

[    0.124063] system 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved
[    0.124073] system 00:0a: iomem range 0xffc00000-0xfff7ffff has been reserved
[    0.124081] system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved
[    0.124085] system 00:0b: iomem range 0xfee00000-0xfee00fff has been reserved
[    0.124095] system 00:0f: ioport range 0x290-0x29f has been reserved
[    0.124103] system 00:10: iomem range 0xe0000000-0xefffffff has been reserved
[    0.124112] system 00:11: iomem range 0x0-0x9ffff could not be reserved
[    0.124116] system 00:11: iomem range 0xc0000-0xcffff could not be reserved
[    0.124120] system 00:11: iomem range 0xe0000-0xfffff could not be reserved
[    0.124124] system 00:11: iomem range 0x100000-0x7f7fffff could not be reserved
[    0.158932] pci 0000:03:02.0: BAR 6: address space collision on of device [0xfebe0000-0xfebe7fff]

May be, there is the reason. No idea if that is important or not. I took one snapshot two or three weeks
bevor. The installation showed the same error message.- Whith debian stable (Lenny) these messages do not
appear.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Mon, 2010-08-23 at 19:00 +0200, Robert wrote:
> Package: snapshot.debian.org
> Severity: normal
> 
> 
> Soon after booting apears one error-message about "space collusion" or so.
> It disappears so fast, that I can not report exatly.
> 
> In "dmesg" are the following lines
> 
> [    0.124063] system 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved
> [    0.124073] system 00:0a: iomem range 0xffc00000-0xfff7ffff has been reserved
> [    0.124081] system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved
> [    0.124085] system 00:0b: iomem range 0xfee00000-0xfee00fff has been reserved
> [    0.124095] system 00:0f: ioport range 0x290-0x29f has been reserved
> [    0.124103] system 00:10: iomem range 0xe0000000-0xefffffff has been reserved
> [    0.124112] system 00:11: iomem range 0x0-0x9ffff could not be reserved
> [    0.124116] system 00:11: iomem range 0xc0000-0xcffff could not be reserved
> [    0.124120] system 00:11: iomem range 0xe0000-0xfffff could not be reserved
> [    0.124124] system 00:11: iomem range 0x100000-0x7f7fffff could not be reserved
> [    0.158932] pci 0000:03:02.0: BAR 6: address space collision on of device [0xfebe0000-0xfebe7fff]
> 
> May be, there is the reason. No idea if that is important or not. I took one snapshot two or three weeks
> bevor. The installation showed the same error message.- Whith debian stable (Lenny) these messages do not
> appear.

This indicates a bug in the firmware (BIOS), but it is probably
harmless.  If any devices have stopped functioning properly in this
kernel version, please reopen this bug report and describe the problem.
Otherwise I don't think there's anything to be done.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: