Boot fails with Out of Range Pointer error

Changing to grub2 due to the grub version from the bug.

Am Freitag, den 04.09.2009, 19:33 +0000 schrieb Launchpad Bug Tracker:
> You have been subscribed to a public bug:
>
> I booted up my laptop running the 32-bit Karmic Alpha this afternoon
> without issue and rebooted after applying the updates. After a reboot, I
> received the following error:
>
> --------------------
> Booting 'Ubuntu, Linux 2.6.31-9-generic'
>
> out of range pointer 0x400040
> Aborted. Press any key to exit.
> --------------------
>
> This happens with any kernel selected (2.6.31-9, 2.6.31-8, 2.6.31-5),
> with and without recovery mode. The Grub version is 1.97~beta1.
>

To workaround this problem, uncomment the GRUB_TERMINAL=console
in /etc/default/grub and run update-grub.
Then it should work again.
Does your laptop have some ATI chip?

Related Debian bugs are:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544155
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544639

--
Felix Zielcke
Proud Debian Maintainer

The Same for me here. I Have an Asus V6 Laptop with ATI 600m.

I got this too. Here is the info related to my video card.

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] [1002:5159]
 Subsystem: Connect Components Ltd Device [17ee:1001]
 Flags: bus master, stepping, 66MHz, medium devsel, latency 64, IRQ 11
 Memory at e8000000 (32-bit, prefetchable) [size=128M]
 I/O ports at d800 [size=256]
 Memory at e6000000 (32-bit, non-prefetchable) [size=64K]
 Expansion ROM at e7fe0000 [disabled] [size=128K]
 Capabilities: [58] AGP version 2.0
 Capabilities: [50] Power Management version 2
 Kernel modules: radeon, radeonfb

I have a IBM Thinkpad T42 with an ATI card. I edited the grub.cfg file by hand to remove the offending lines from within a Live session. I then fixed the defaults and updated grub file per the instructions above. It was still fixed after a reboot.

Here is the info from lspci:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50]
 Subsystem: IBM Device [1014:0550]
 Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11
 Memory at e0000000 (32-bit, prefetchable) [size=128M]
 I/O ports at 3000 [size=256]
 Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
 Capabilities: [58] AGP version 2.0
 Capabilities: [50] Power Management version 2
 Kernel modules: radeon, radeonfb

it fixed my problem, but we should run update-grub2 instead of update-grub.

Am Samstag, den 05.09.2009, 09:25 +0000 schrieb Dulmandakh Sukhbaatar:
> it fixed my problem, but we should run update-grub2 instead of update-
> grub.

That doestn't make any difference.
update-grub2 is just a stub which calls update-grub and does nothing
else.

--
Felix Zielcke
Proud Debian Maintainer

same problem after updating karmic to-day

when i re-boot
i got when grub started

"out of range pointer 0X400040
Aborted press any key to exit"

i can boot just with grub-rescue-cdrom-iso ( live-cd)

Dulmandakh Sukhbaatar and dominique: what video card is in your computer? Could you post the relevant output of 'lspci -vnn'? The VGA-related section should be enough.

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57]
 Subsystem: Acer Incorporated [ALI] Device [1025:0020]
 Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel, laten

I forgot this other related Debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544822

Now we have at least from one person a confirmation that this happens also with current squeeze version 1.96+20090808-1
I just don't get why this comes up now.
Between the previous karmic version 1.96+20090826 and beta1 there was only one commit related to gfxterm and someone on a Debian bug report said that reverting this patch doestn't help at all.

Got the same problem. The workaround described above solved the problem.
Output of lspci:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M6 LY [1002:4c59]
 Subsystem: IBM Device [1014:052f]
 Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11
 Memory at e0000000 (32-bit, prefetchable) [size=128M]
 I/O ports at 2000 [size=256]
 Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel modules: radeon, radeonfb

I also had this issue, uncommenting GRUB_TERMINAL worked for me as well.

Relevant `lspci` output:

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RC410 [Radeon Xpress 200M] [1002:5a62]
        Subsystem: Toshiba America Info Systems Device [1179:ff10]
        Flags: bus master, 66MHz, medium devsel, latency 66, IRQ 17
        Memory at d8000000 (32-bit, prefecthable) [size=128M]
        Memory at d0100000 (32-bit, prefecthable) [size=64K]
        [snip]
        Kernel modules: radeon, radeonfb

Same problem and solution with an IBM T42. Sadly I hadn't rebooted for quite some time, so can't pin down any particular version change. Thanks. :-)

----

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57]
        Subsystem: IBM Device [1014:0530]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+ DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 66 (2000ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 3000 [size=256]
        Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
                Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
                Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Kernel modules: radeon, radeonfb

Same here under my Medion 40653.
1/ Take daily-live iso (20090907)
2/ Install the system
3/ reboot
4/ bug in grub

I have a ATI RV350 [Mobility Radeon 9600 M10]

I have same problem with a Dell Latitude C540.

I solved the problem by comment this following line in /boot/grub/grub.cfg:

#if terminal_output gfxterm ; then true ; else
  # For backward compatibility with versions of terminal.mod that don't
  # understand terminal_output
     # terminal gfxterm
#fi

I too suffer from this bug my work around as follows;

You can also use an alpha 5 alternate cd

Boot CD

select Rescue System

Make sure you set the correct root ......./dev/sda in my case

Follow prompts until you reach Rescue Menu

choose first option Console Window Note this is root no need for sudo

Type nano /etc/default/grub Uncomment the GRUB_TERMINAL=console line
Save file

Type update-grub

Type exit

Choose reboot from Rescue Menu

as cedric ( thanks to him)

I solved too the problem by comment this following line in /boot/grub/grub.cfg:

#if terminal_output gfxterm ; then true ; else
  # For backward compatibility with versions of terminal.mod that don't
  # understand terminal_output
     # terminal gfxterm
#fi

however i have no choice on grub boot

Only the @Cedric F. workaround make my Karmic booting again.

Thank you

1/ launch ubuntu-live
2/ mount root partition
3/ edit partition/boot/grub/grub.cfg
4/ reboot

PS : no need to use update-grub

Am Dienstag, den 08.09.2009, 09:24 +0000 schrieb Patrice Vetsel:
> 1/ launch ubuntu-live
> 2/ mount root partition
> 3/ edit partition/boot/grub/grub.cfg
> 4/ reboot
>
> PS : no need to use update-grub

The problem with that method is, that gfxterm gets added again on the
next update-grub run.
Wich is either the update of the grub-pc package or a kernel
remove/install.
That's why I recommended to change /etc/default/grub and run update-grub
so that it's preserved.

--
Felix Zielcke
Proud Debian Maintainer

@Felix : indeed !

@ Felix i agree but was impossible for me to run update-grub because there was other errors when i try to do the update-grub on the chrooted mounted /dev/sda1 there are something wrong also in on the /boot/grub/device.map (it is empty) and i cannot create with sudo grub-mkdevicemap using the Ubuntu 8.10 live cd.

Now booting fine i was able to recreate the /boot/grub/device.map from the installed Ubuntu.

Thank you

Also applies to me in the server world, with a hp bl460c g6 blade which has this onboard graphics:

01:03.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

Workaround works, but it was a less than pleasant surprise when upgrading, and it does add an extra couple of manual steps to the install procedure.

The Bug is still existing after todays Grub2-Update (11.09.09).

Am Freitag, den 11.09.2009, 19:17 +0000 schrieb Thorsten Reinbold:
> The Bug is still existing after todays Grub2-Update (11.09.09).
>

If we think it has been fixed then this bug would have been marked Fix
released and not still kept Confirmed.
No need to tell us, we're making progress in fixing this.
Also look at the Debian reports I posted if you want more info on the
progress.

--
Felix Zielcke
Proud Debian Maintainer

I got hit by this bug yesterday. I used the netboot CD for booting into rescue mode and edited /boot/grub/grub.cfg file. The PC boots find since then.

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] [1002:5159] (prog-if 00 [VGA])
 Subsystem: PC Partner Limited Sapphire Radeon VE 7000 DDR [174b:7c28]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 32 (2000ns min), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at a000 [size=256]
 Region 2: Memory at ed000000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at ec000000 [disabled] [size=128K]
 Capabilities: [58] AGP version 2.0
  Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
  Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel modules: radeon, radeonfb

@Felix Zielcke: I'm really sorry for annoying you with nasty User-Comments. I won't bother you any longer.

The bug is also present on the Karmic Server 9.10 Alpha 5 AM64 ISO release. None of the suggested fixes above corrected the problem. I'm running on an Opteron based system, Asus M2N-LR mainboard with onboard ATI ES1000 graphics. Nothing else noteworthy in the system.

Don't want to be screaming 'me too', but perhaps the info that this problem also affects my ancient ATI 7000 card is somewhat usefull...

Got the same problem on an HP Proliant DL380 G5, which had been certified for 8.04.

cloudmaster@eucalyptus-walrus:~$ lspci | grep VGA
01:03.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

This bug was fixed in the package grub2 - 1.97~beta3-1ubuntu1

---------------
grub2 (1.97~beta3-1ubuntu1) karmic; urgency=low

  * Resynchronise with Debian. Remaining changes:
    + debian/default/grub:
      - Adjust for default Ubuntu boot options.
      - Use GRUB_CMDLINE_LINUX_DEFAULT option to set "quiet splash" for
        default items only. These options won't be set in single user mode.
      - Default to hiding the menu; holding down Shift at boot will show it.
    + debian/templates.in:
      - Change default value of grub2/linux_cmdline_default to "quiet
        splash".
    + debian/config.in, debian/postinst.in, debian/grub-pc.templates.in:
      - Migrate timeout settings from menu.lst.
    + debian/grub.d/05_debian_theme:
      - Set a monochromatic theme for Ubuntu.
    + debian/legacy/update-grub:
      - Apply Ubuntu branding: title, recovery mode, quiet option, and tweak
        how memtest86+ is displayed.
      - Use UUIDs where appropriate.
    + debian/patches/03_ubuntu_grub_standards:
      - Remove GNU/Linux from default string.
    + debian/patches/10_crashkernel.patch:
      - Add crashkernel= options if kdump and makedumpfile are available.
    + debian/patches/951_quick_boot.diff:
      - If other operating systems are installed, then automatically unhide
        the menu.
      - Otherwise, if GRUB_HIDDEN_TIMEOUT is 0, then use keystatus if
        available to check whether Shift is pressed. If it is, show the
        menu, otherwise boot immediately. If keystatus is not available,
        then fall back to a short delay interruptible with Escape.
    + debian/patches/952_sleep_shift.diff:
      - Allow Shift to interrupt 'sleep --interruptible'.
    + debian/patches/954_normal_quiet.diff:
      - Don't display introductory message about line editing unless we're
        actually offering a shell prompt. Don't clear the screen just before
        booting if we never drew the menu in the first place.
    + debian/patches/955_really_quiet.diff:
      - Remove some verbose messages printed before reading the
        configuration file.
    + debian/patches/956_linux_quiet.diff:
      - If the environment variable "quiet" is set to something other than
        1, suppress progress messages as the kernel and initrd load. Set
        this for non-recovery kernel menu entries.
    + debian/patches/957_savedefault.diff, debian/rules:
      - Add GRUB_DEFAULT=saved, as well as grub-set-default and grub-reboot
        utilities. Provides functionality essentially equivalent to GRUB
        Legacy's savedefault.
    + debian/patches/959_loopback_root.diff:
      - Keep the loopback file open so that subsequent changes to the "root"
        environment variable don't affect it.
  * debian/patches/960_test_invalid_fs.diff: Fix test crash if loopback
    device does not contain a filesystem.

grub2 (1.97~beta3-1) unstable; urgency=high

  * New upstream beta release.
    - Make it more clear how to use /etc/grub.d/40_custom. (Closes: #545153)
    - fix a serious memory corruption in the graphical subsystem.
      (Closes: #545364, #544155, #544639, #544822, LP: #424503)
    - patches/003_grub_probe_segfault.diff: Remove (...

after the very last upgrade ( 09-15) my PC don't boot
i get this message

failed to connect to socket /var/run/dbus/system_bus_socket

the only way to boot again for me was to re-install an old karmicdailybuild iso and upgrade all packages except grub packages

but in the same time th dbus versions changed so i don"t know the source of the bug

Acer travelmate 65O

@dominique ,

Grub has nothing to do with dbus. You should file a bug against dbus.

hi onkar
sure

so I searched what dbus package was upgraded : dbus-X11 and after test dbus is not the source of the bug

so i did this

1.format all and complete re-installation in ext3 or ext2

same bug , same solution ( upgrade except grub packages)
therefore when i shutdowned , many reboot with running manually fsck

2.format all and complete re-installation in ext4

same bug , same solution ( upgrade except grub packages)

But when I shutdown no fsck needed at reboot

so i think the bug is probabely done by grub