You are not logged in.

#1 2010-04-11 15:07:32

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

[SOLVED] Address Space Collision

When I boot, the screen displays three arch logos and outputs the following:

:: Loading Initramfs
:: Starting udevd...
done.
ata3: softreset failed (device not ready)
ash: /dev/: unknown operand
Waiting 10 seconds for device  ...
ash: /dev/: unknown operand
ERROR: Unable to determine major/minor number of root device ''.
You are being dropped into a reovery shell
    Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]#

I can't do anything at this point (perhaps because my keyboard is USB).
Using the fallback image does not help.
Looking on Google I found that ata3: softreset failed (device not ready) is usually not a fatal error, but could find nothing else of apparent relevance.
I am using an AMD chipset with Arch x86_64, I have tried kernel 2.6.33, 2.6.32 and 2.6.31, and none of them work okay for me.
I use Ubuntu with kernel 2.6.31-20-generic on a separate partition and everything works fine.


Original Problem:
Originally I couldn't boot into Arch Linux because of an 'address space collision', this was the error I got:

[Linux-bzImage, setup=0x3400, size=0x1f9a20]
[Initrd, addr=0x37e3f000, size=0x1b0082]
pci 0000:00:00.0: address space collision: [mem 0xe0000000-0xffffffff 64bit] already in use
<system fails and drops into recovery shell>

I fixed this by downgrading:

pacman -U http://arm.konnichi.com/2010/03/01/core/os/x86_64/kernel26-2.6.32.9-1-x86_64.pkg.tar.gz

(the link is to an older version of the kernel)

And adding

ignorePkg = kernel26

to /etc/pacman.conf.

Last edited by Penguin Guy (2010-10-11 15:23:11)

Offline

#2 2010-04-11 23:19:39

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,217
Website

Re: [SOLVED] Address Space Collision

A quick Google seems to be an issue with 2.6.33 perhaps.... Can you boot the installation CD, chroot your installation and downgrade to 2.6.32 to see if that fixes it?

Offline

#3 2010-04-12 19:52:33

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

Re: [SOLVED] Address Space Collision

fukawi2 wrote:

A quick Google seems to be an issue with 2.6.33 perhaps.... Can you boot the installation CD, chroot your installation and downgrade to 2.6.32 to see if that fixes it?

I'm quite new to pacman, but as far as I understand I need to run:

pacman -U http://arm.konnichi.com/2010/03/01/core/os/x86_64/kernel26-2.6.32.9-1-x86_64.pkg.tar.gz

And then pacman will automatically install the package from that link and lock it so that it doesn't upgrade the next time I run pacman -u. Is this correct?

Offline

#4 2010-04-12 22:49:28

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,217
Website

Re: [SOLVED] Address Space Collision

Run that after you inside the chroot, and yes... Although it won't "lock" it -- next time you run -Syu it will want to upgrade it. To get it "locked" you need to add it to the IgnorePkg line in pacman.conf

Offline

#5 2010-04-13 15:44:54

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

Re: [SOLVED] Address Space Collision

Great! Old kernel installed fine and package locked okay. However I am now receiving a different error, something about a failed softreset?

The screen displays three arch logos and outputs the following:

:: Loading Initramfs
:: Starting udevd...
done.
ata3: softreset failed (device not ready)
ash: /dev/: unknown operand
Waiting 10 seconds for device  ...
ash: /dev/: unknown operand
ERROR: Unable to determine major/minor number of root device ''.
You are being dropped into a reovery shell
    Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]#

I can't do anything at this point (perhaps because my keyboard is USB).

Looking on Google I found that ata3: softreset failed (device not ready) is usually not a fatal error, but nothing else of apparent relevance.

Last edited by Penguin Guy (2010-04-13 15:52:00)

Offline

#6 2010-04-13 16:35:22

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: [SOLVED] Address Space Collision

Try booting with the fallback initramfs image.

Offline

#7 2010-04-13 18:02:40

Daenyth
Forum Fellow
From: Boston, MA
Registered: 2008-02-24
Posts: 1,244

Re: [SOLVED] Address Space Collision

As for three logos -- Do you have three cpus?

Offline

#8 2010-04-13 19:36:43

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

Re: [SOLVED] Address Space Collision

tomk wrote:

Try booting with the fallback initramfs image.

No change - the error appears and the system still won't boot.

Daenyth wrote:

As for three logos -- Do you have three cpus?

Yes - that explains it.

Offline

#9 2010-04-17 21:12:49

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

Re: [SOLVED] Address Space Collision

I've tried kernels 2.6.33, 2.6.32 and 2.6.31, and none of them work for me, however Ubuntu's 2.6.31-generic works fine. Any more suggestions?

Offline

#10 2010-04-23 19:32:32

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

Re: [SOLVED] Address Space Collision

Bump.

Offline

#11 2010-05-19 17:30:00

Penguin Guy
Member
Registered: 2009-05-12
Posts: 22

Re: [SOLVED] Address Space Collision

It looks like, for no apparent reason, the problem has solved itself. Thanks for all the help.

Offline

Board footer

Powered by FluxBB