[09:02] <PaulePanter> Hi.
[09:02] <PaulePanter> cjwatson referred me to here from #grub-pc.
[09:02] <PaulePanter> Upgrading to 1.99-21ubuntu3.15 on Ubuntu precise (12.04.4 LTS) causes a segmentation fault.
[09:02] <PaulePanter> grub-setup[30142]: segfault at 400688d18 ip 0000000000438d44 sp 00007fffac5532d0 error 4 in grub-setup[400000+5b000]
[09:03] <PaulePanter> As I do not have my Launchpad credentials here right now, I am reporting this to you in here.
[09:04] <cjwatson> I'll need the full crash file.
[09:04] <cjwatson> I can't do anything with just that.
[09:04] <cjwatson> Please report it to the error tracker so that I get a retraced version.
[09:05] <PaulePanter> Here is the log http://paste.debian.net/107725/ .
[09:05] <PaulePanter> cjwatson: By error tracker do you mean Launchpad?
[09:05] <cjwatson> No, I mean errors.ubuntu.com - are you on a desktop system?  if so you should have had a dialog pop up about the crash
[09:06] <cjwatson> There should be a file in /var/crash/, at least
[09:06] <PaulePanter> cjwatson: No that is on a production server.
[09:07] <cjwatson> There should still be something in /var/crash/, then
[09:07] <PaulePanter> $ ls /var/crash
[09:07] <PaulePanter> ls: cannot access /var/crash: No such file or directory
[09:08] <PaulePanter> Do I need corekeeper or something like this?
[09:08] <cjwatson> No
[09:08] <PaulePanter> Some ulimit setting to store core dump files?
[09:08] <cjwatson> Can you figure out the grub-setup command being run (grub-install --debug <whatever> should help) and run it under gdb?
[09:09] <cjwatson> What does /etc/default/apport say?
[09:10] <cjwatson> Does it include a command for temporarily enabling apport?  If so, run that, then try again
[09:10] <cjwatson> (before trying gdb)
[09:11] <PaulePanter> /etc/default/apport does not exist.
[09:11] <PaulePanter> I’ll install apport.
[09:13] <cjwatson> There are a few crashes on the error tracker, but unfortunately none with tracebacks
[09:14] <PaulePanter> cjwatson: Apport installed and /var/crash/_usr_lib_grub_i386-pc_grub-setup.0.crash is there after running `aptitude reinstall grub-pc`.
[09:16] <PaulePanter> Hmm that is not a core dump file.
[09:16] <cjwatson> Expected.
[09:16] <cjwatson> Can I at least see the raw .crash file to start with?
[09:17] <cjwatson> (Also you can probably just use "dpkg --configure grub-pc", which I'm sure will be quicker.)
[09:17] <PaulePanter> cjwatson: Thanks.
[09:17] <PaulePanter> cjwatson: Do I have to log in on https://errors.ubuntu.com/ to post something?
[09:18] <cjwatson> There's a special client for posting things there, but could I please just have the crash file on a pastebin or something for now?
[09:18] <PaulePanter> http://paste.ubuntu.com/7735795/
[09:18] <PaulePanter> cjwatson: Sorry for taking so long. I am not used to the Ubuntu tools.
[09:21] <PaulePanter> cjwatson: With you highlighted: http://paste.ubuntu.com/7735795/
[09:22] <cjwatson> One moment.
[09:23] <PaulePanter> Sure. Just wanted to make sure you did not miss it.
[09:32] <cjwatson> Grr, this is really cumbersome in 12.04, because it's missing /usr/share/apport/whoopsie-upload-all.  Let me see if I can retrace this manually
[09:36] <PaulePanter> cjwatson: Please tell me if I can do something on my end.
[09:46] <cjwatson> Argh, why do we have no debugging symbols worth mentioning for grub2?  One of these days I must figure this out
[09:47] <cjwatson> PaulePanter: Please could you run "/usr/sbin/grub-setup --force --directory=/boot/grub --device-map=/boot/grub/device.map -vv /dev/md1" and show me the output?
[09:47] <cjwatson> (That's the command that grub-install was running, with -vv added.)
[09:50] <PaulePanter> cjwatson: http://paste.ubuntu.com/7735942/
[09:51] <PaulePanter> cjwatson: That did *not* crash with any segmentation fault.
[09:52] <cjwatson> Blink
[09:53] <cjwatson> PaulePanter: When will you have access to your Launchpad credentials so that you can file a bug about this?  I'll need a bug for stable update tracking once I get to the bottom of this, and it would be easiest if you filed it so that you can verify the fix.
[09:54] <PaulePanter> cjwatson: In 10 hours or so.
[09:54] <cjwatson> I've managed to get a gdb trace, at least, but it has no symbols so I'm going to need to do a local build in order to get something I can actually inspect sensibly
[09:54] <cjwatson> PaulePanter: OK, that would be helpful, thanks.  I probably have about as much information as I need at this point
[09:55] <PaulePanter> cjwatson: Without the switch `-vv` it crashes.
[09:55] <PaulePanter> $ sudo /usr/sbin/grub-setup --force --directory=/boot/grub --device-map=/boot/grub/device.map /dev/md1
[09:55] <cjwatson> How about with just -v
[09:55] <cjwatson> ?
[09:55] <PaulePanter> $ echo $?
[09:55] <PaulePanter> 139
[09:56] <PaulePanter> cjwatson: Sorry. That was wrong.
[09:56] <PaulePanter> It crashes in all three cases. I was just confused that I was not reported a crash on the console.
[09:56] <PaulePanter> Probably due to using `sudo`. No idea.
[09:56] <PaulePanter> Anyway, all crashes are logged in the Linux kernel ring buffer (dmesg).
[09:58] <PaulePanter> Also for whatever reason no crash files were created for these in `/var/crash/`.
[10:01] <cjwatson> Possibly just because one already existed.
[10:19] <cjwatson> Miracles will never cease.  I build this locally and get the same object code offsets.
[10:22] <cjwatson> #0  open (__oflag=0, __path=<error reading variable: Cannot access memory at address 0x400688d18>) at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:54
[10:22] <cjwatson> #1  grub_util_biosdisk_is_floppy (disk=0x179b9c0) at ../../grub-core/kern/emu/hostdisk.c:2093
[10:22] <cjwatson> #2  0x000000000040408c in setup (dir=0x1439390 "/boot/grub", boot_file=<optimized out>, core_file=0x4442e0 "core.img", root=<optimized out>, dest=<optimized out>, must_embed=0, force=1, fs_probe=1, allow_floppy=0) at ../../util/grub-setup.c:319
[10:22] <cjwatson> #3  0x0000000000402dda in main (argc=<optimized out>, argv=<optimized out>) at ../../util/grub-setup.c:1009
[10:24] <cjwatson> PaulePanter: What was the last version that worked?
[10:24] <cjwatson> As far as I can see, 1.99-21ubuntu3.15 didn't change any code that's run before this point.
[10:25] <cjwatson> Although 1.99-21ubuntu3.14 potentially did.
[10:27] <PaulePanter> cjwatson: I do not remember ever having seen that issue before. 1.99-21ubuntu3.14 was upgraded to before.
[10:29] <cjwatson> .15 only affected disk write code (and some unrelated terminal handling stuff); at the point of this crash grub-setup hasn't tried to write anything yet ...
[10:34] <cjwatson> I suspect http://git.savannah.gnu.org/gitweb/?p=grub.git;a=commitdiff;h=69915030942771f6813ebc238e86e05b5112f3b5 will fix this though.
[10:37] <PaulePanter> cjwatson: No idea if something changed since December. But to my knowledge there was only a restart.
[10:41] <cjwatson> PaulePanter: I'm building a test fix in a PPA for you.
[10:41] <cjwatson> The diff is http://paste.ubuntu.com/7736119/
[10:44] <cjwatson> It'll be built in https://launchpad.net/~cjwatson/+archive/grub/+packages later today.  I'll let you know
[10:46] <PaulePanter> cjwatson: Thanks a lot!
[12:45] <cjwatson> PaulePanter: That's built there now.  Please test.
[13:35] <zartoosh> Hi I am preseeding installation of ubuntu 14.04 , using expert_recipe I create 4 partitions. One partition I do not want to have mountpoint. But I always get asked for "No mount point assigned ..." for that partition. How could I by pass this? thx
[13:39] <PaulePanter> cjwatson: Thanks. There is no crash anymore.
[13:39] <PaulePanter> http://paste.ubuntu.com/7736818/
[13:39] <PaulePanter> … but still the scary warning. But I think I can ignore that.
[13:41] <cjwatson> PaulePanter: No worse than before, I expect.
[13:42] <cjwatson> PaulePanter: Thanks.  Let me know when you've filed the bug, and I can then upload the fix.
[13:42] <zartoosh> this is part of my expert_recipe: http://paste.ubuntu.com/7736832/
[13:43] <zartoosh> Need help please.
[13:46] <cjwatson> zartoosh: You can either mount it somewhere for the sake of the installer's sanity checking, and remove it from /target/etc/fstab in a preseed/late_command script; or you can preseed "d-i partman-basicfilesystems/no_mount_point boolean false" to suppress the warning, if you don't mind losing the check altogether.
[13:48] <zartoosh> cjwatson,  thx,
[16:13] <mikem_p250> when installing trusty is it possible for the kernel to be updated during the install
[16:13] <mikem_p250> ?
[16:14] <mikem_p250> I should say updated automatically w/o the user's knowledge
[20:18] <PaulePanter> cjwatson: Clicking *Report a bug* on https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=grub&search=Search+Bug+Reports&field.scope=project&field.scope.target=ubuntu
[20:18] <PaulePanter> forwards me to https://help.ubuntu.com/community/ReportingBugs .
[20:19] <PaulePanter> So I just run `ubuntu-bug /var/crash/_usr…` which did not require any credentials.
[20:19] <PaulePanter> Hopefully that works for you too.
[20:21] <PaulePanter> Looks like I would have to do that from <https://bugs.launchpad.net/ubuntu/+source/grub2/+filebug>.
[20:44] <cjwatson> PaulePanter: I don't see it.  Please use https://bugs.launchpad.net/ubuntu/+source/grub2/+filebug?no-redirect
[20:54] <PaulePanter> cjwatson: Ok.
[21:08] <PaulePanter> cjwatson: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1336946
[21:09] <cjwatson> thanks
[21:20] <PaulePanter> cjwatson: Thank you for your great support. I am leaving this channel again. You’ll find me in #grub if there is anything else.