This mail is an automated notification from the bugs tracker
 of the project: GNU GRUB.

/**************************************************************************/
[bugs #9370] Latest Modifications:

Changes by: 
                Yoshinori K. Okuji <[EMAIL PROTECTED]>
'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:  [EMAIL PROTECTED]
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/





_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-grub

Reply via email to