Hello, > > > My x86_64 box is not willing to boot. > > > > > > http://tuxland.pl/tmp/s7300372.jpg (275kB) > > > > > > (gdb) p blk_lookup_devt > > > $1 = {dev_t (const char *, int)} 0xffffffff8032a430 <blk_lookup_devt> > > > (gdb) l *(0xffffffff8032a430+0x7f) > > > 0xffffffff8032a4af is in blk_lookup_devt (block/genhd.c:664). > > > 659 dev_t devt = MKDEV(0, 0); > > > 660 > > > 661 mutex_lock(&block_class_lock); > > > 662 list_for_each_entry(dev, &block_class.devices, node) { > > > 663 if (strcmp(dev->bus_id, name) == 0) { > > > 664 struct gendisk *disk = dev_to_disk(dev); > > > 665 > > > 666 if (part < disk->minors) > > > 667 devt = MKDEV(MAJOR(dev->devt), > > > 668 MINOR(dev->devt) + part); > > Having decoded the "Code:", what is happening here is that 'dev' is > clearly not embedded inside a 'disk'. > The address of 'dev' is in RBX and is ffff81007f270010. > disk->minors is at and offset of -0x60 from 'dev' (as 'dev' is assumed > to be a structure embeded in a 'struct gendisk' - dev_to_disk uses > container_of to find the gendisk that holds the device). But 0x60 from RBX > is in a different page, and presumably that memory doesn't exist. > > So the question is: how can a 'struct device' which is not part of > a 'struct gendisk' be on 'block_class.devices'. > > Unfortunately, I have no idea. 2.6.26-rc4 works fine :/ Am I lucky or not? I'll do some more tests on weekend. Thanks, Mariusz -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
