[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bugs #9370] GRUB can't load Linux kernel 2.6 initrds with large memory
From: |
Yoshinori K. Okuji |
Subject: |
[bugs #9370] GRUB can't load Linux kernel 2.6 initrds with large memory |
Date: |
Mon, 21 Jun 2004 07:47:03 -0400 |
User-agent: |
Mozilla/5.0 (compatible; Konqueror/3.2; Linux; en_US, ja_JP, ja) (KHTML, like Gecko) |
This mail is an automated notification from the bugs tracker
of the project: GNU GRUB.
/**************************************************************************/
[bugs #9370] Latest Modifications:
Changes by:
Yoshinori K. Okuji <address@hidden>
'Date:
Mon 06/21/2004 at 11:41 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Wont Fix
Status | Open | Closed
------------------ Additional Follow-up Comments ----------------------------
There is no response from the reporter, even though I sent an e-mail in which I
asked him to confirm that this was due to Linux rather than GRUB. So I assume
that this bug is not related to GRUB.
/**************************************************************************/
[bugs #9370] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9370>
Project: GNU GRUB
Submitted by: 0
On: Thu 06/17/2004 at 17:07
Category: Booting
Severity: Major
Priority: 5 - Normal
Item Group: Software Error
Resolution: Wont Fix
Assigned to: None
Originator Name: Joshua Kwan
Originator Email: address@hidden
Status: Closed
Release: 0.93/0.94cvs
Reproducibility: Every Time
Planned Release:
Summary: GRUB can't load Linux kernel 2.6 initrds with large memory
Original Submission: This change in CVS:
http://savannah.gnu.org/cgi-bin/viewcvs/grub/grub/stage2/boot.c.diff?r1=1.44&r2=1.45
caused GRUB to complain that the image would not fit in memory. the problem was
worked around by:
http://bugs.debian.org/cgi-bin/bugreport.cgi/01-0.94-initrdmax.patch?bug=254798&msg=3&att=3
Does anyone have an opinion on the nature of why this happened? I am thinking
of adding debug statements...
Follow-up Comments
------------------
-------------------------------------------------------
Date: Mon 06/21/2004 at 11:41 By: okuji
There is no response from the reporter, even though I sent an e-mail in which I
asked him to confirm that this was due to Linux rather than GRUB. So I assume
that this bug is not related to GRUB.
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9370>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/