grub-mount assert failure: *** glibc detected *** grub-mount: free(): invalid next size (fast): 0x08d25b98 ***

Bug #775377 reported by furukazu on 2011-05-02
98
This bug affects 10 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: grub2

I use MacBook Pro 15inch model mid 2009. (5,3). . Want to install 3rd partition on HDD. ( sda3 )

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: grub-common 1.99~rc1-13ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
Architecture: i386
AssertionMessage: *** glibc detected *** grub-mount: free(): invalid next size (fast): 0x08d25b98 ***
CrashCounter: 1
Date: Mon May 2 07:02:30 2011
ExecutablePath: /usr/bin/grub-mount
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: grub-mount /dev/sda2 /var/lib/os-prober/mount
ProcEnviron:
 LANGUAGE=ja_JP:en
 PATH=(custom, no user)
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: grub2
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
Title: grub-mount assert failure: *** glibc detected *** grub-mount: free(): invalid next size (fast): 0x08d25b98 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

furukazu (gbd02401) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x3c88ac "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=<value optimized out>, str=<value optimized out>, ptr=0x8d25b98) at malloc.c:6283

Changed in grub2 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in grub2 (Ubuntu):
status: New → Confirmed
visibility: private → public
Tofslar (terkani1) wrote :

Very strange bug ...

tags: added: precise
Alejandro R. Mosteo (mosteo) wrote :

I am suddenly seeing this in a Trusty 64 bits fully updated... the actual address is different, 0x0000000000deb700

jealie (jealie) wrote :

I reproduced this bug by adding an additional menuentry in file '/etc/grub.d/40_custom'.

Previous version of the file (no bug):

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

New version of the file, producing the bug:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry ‘Windows 10 msdos2′ {
set root='(hd0,msdos2)’
chainloader +1
}

Finally, I solved the bug by creating a new file '/etc/grub.d/42_custom' and put the new menuentry there...

Hope this helps.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers