localboot in pxelinux recurses back into pxelinux, and eventually crashes

Bug #625294 reported by Ronald McCollam
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
syslinux (Ubuntu)
Triaged
High
Canonical Foundations Team
Maverick
Invalid
High
Canonical Foundations Team

Bug Description

After installation on an IBM x3250 and an IBM x3650, the maverick daily images do not boot.

With image 20100826 I receive the following message when trying to boot:

It appears your computer has less than 277K of low ("DOS") RAM. Syslinux needs at least this amount to boot. If you get this message in error, hold down the Ctrl key while booting, and I will take your word for it.

Holding Ctrl does indeed allow the systems to boot and they seem to work correctly. However as these are servers this is not a workable long-term solution.

Revision history for this message
Ronald McCollam (fader) wrote :
Revision history for this message
Ronald McCollam (fader) wrote :
Revision history for this message
Ronald McCollam (fader) wrote :
Revision history for this message
Ronald McCollam (fader) wrote :
Revision history for this message
Ronald McCollam (fader) wrote :
Revision history for this message
Ronald McCollam (fader) wrote :
Ameet Paranjape (ameetp)
Changed in linux (Ubuntu):
importance: Undecided → High
status: New → Triaged
assignee: nobody → Ubuntu Installer Team (ubuntu-installer)
assignee: Ubuntu Installer Team (ubuntu-installer) → nobody
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Revision history for this message
Colin Watson (cjwatson) wrote :

Is this a regression from Lucid?

affects: linux (Ubuntu Maverick) → syslinux (Ubuntu Maverick)
Revision history for this message
Ronald McCollam (fader) wrote :

Yes, this is a regression from 10.04 LTS.

C de-Avillez (hggdh2)
tags: added: maverick regression-release
removed: regression-potential
Revision history for this message
Ameet Paranjape (ameetp) wrote :

FYI - There is a request open to verify BIOS and firmware levels on these systems are at the latest levels.

Revision history for this message
Colin Watson (cjwatson) wrote :

When I tell one of the systems in question to boot directly from the hard disk, this doesn't happen. It only happens when attempting to go through pxelinux and boot from the local disk. The output looks like this (with some boring bits elided):

  TFTP prefix: /cdimage.ubuntu.com/ubuntu-server/daily/current/maverick-server-i386/
  Trying to load: pxelinux.cfg/default ok
  Booting from local disk...

  Intel(R) Boot Agent GE v1.3.27
  Copyright (C) 1997-2008, Intel Corporation

  CLIENT MAC ADDR: ... GUID: ...
  CLIENT IP: ... MASK: ... DHCP IP: ...
  GATEWAY IP: ...

This repeats several times, and then the "It appears your computer has less than ..." message appears. I therefore suspect that the PXE stack's local boot function doesn't work properly, and as a result we are recursing through the PXE stack until it runs out of low memory.

summary: - Unable to boot maverick daily images -- RAM not detected
+ localboot in pxelinux recurses back into pxelinux, and eventually
+ crashes
Revision history for this message
JC Hulce (soaringsky) wrote :

This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached end-of-life and is no longer supported, so I am closing the bug task for Maverick. Please upgrade to a newer version of Ubuntu.
More information here: https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html

Changed in syslinux (Ubuntu Maverick):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.