Your message dated Tue, 1 Jun 2010 13:04:14 +0100
with message-id <[email protected]>
and subject line Re: [grub] grub: crashes frequently on boot
has caused the Debian Bug report #551319,
regarding [grub] grub: crashes frequently on boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
551319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551319
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub
Version: 0.97-59
Severity: serious
--- Please enter the report below this line. ---
The new grub package seems to be very unstable -- at least at my acer aspire
5630 Laptops:
I see the following behaviours:
- laptop reboots (just after the screen gets blank, ready to print "GRUB
loading"
- grub hangs just after telling "Loading GRUB"
- sometimes it displays something like "Corrupt End-Of-Free Marker found after
<some-hex-address>.
Next time I see that message, I will write it down to have it exactly
After several tries (average 5 tries) it will eventually succeed booting.
If you need more informations, please let me know what you need. In the mean
time I try grub-legacy too rule out hardware problems.
coldtobi
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.30-2-686
Debian Release: squeeze/sid
500 unstable ftp.uni-bayreuth.de
--- Package information. ---
Depends (Version) | Installed
==========================-+-===========
grub-pc | 1.97~beta4-1
debconf (>= 0.5) | 1.5.27
OR debconf-2.0 |
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On Mon, May 31, 2010 at 08:05:00PM +0200, Tobias Frost wrote:
> I retried this weekend and so far it looks quite good:
> It happended only one time that Grub did not manage to load itself,
> (this one time it just rebooted, so could be something different as
> well)
>
> So, also considering that it seems only my machine (type) which is/was
> affected, I think it would be appropiate to close this issue.
OK. I'll close this for now, but feel free to reopen it if you continue
to see it and manage to narrow it down any more.
Thanks,
--
Colin Watson [[email protected]]
--- End Message ---
