On Mon, Nov 13, 2006 at 03:03:16PM -0700, Zan Lynx wrote:
> I have not checked if this is true, but it is a possible explanation:
>
> Perhaps the filesystem is not properly unmounted during a suspend? That
Of course not.
> would mean GRUB is reading from a incoherent filesystem on resume.
Exactly.
> GRUB's filesystem drivers are not very fancy. It could be it does
> something silly like check the journal before returning each block.
GRUB must not write to the fs, so it probably plays back the journal in
memory only and it does this for every file it reads (at least that's how
it feels :-)
> Maybe its a journal size thing, you could try "sync" before suspend and
> see if it helps.
We already sync inside the kernel, it does not help here, though.
Blockdev freezing might help.
> Another thing would be to create /boot as a separate partition.
Yes, that's what i always advise: /boot on separate ext2 partition. Then
GRUB resumes fast.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
