On Sun, 31 Aug 2008, Michael Schmitz wrote:
On 2.6.27-rc5-m68k-atari-dirty I get:
| kobject (00cfb94c): tried to init an initialized object, something is
seriously wrong.
| Call Trace: [<0010eb64>] kobject_init+0x40/0x6a
| [<0010f104>] kobject_init_and_add+0x14/0x34
| [<00113706>] sprintf+0x0/0x26
| [<001083e6>] blk_register_filter+0x3c/0x52
| [<00107498>] add_disk+0x4c/0xa0
| [<0010744c>] add_disk+0x0/0xa0
| [<0028fe80>] atari_floppy_init+0x14c/0x6de
| [<0028fd34>] atari_floppy_init+0x0/0x6de
| [<00002008>] do_one_initcall+0x0/0x19e
| [<00289df2>] __alloc_bootmem+0x0/0x1a
| [<00002024>] do_one_initcall+0x1c/0x19e
| [<0009cab2>] sysfs_create_file+0x3e/0x44
| [<00143248>] sysdev_class_create_file+0x12/0x16
| [<0028fb5e>] cpu_dev_init+0x4e/0x6c
| [<00280ab2>] kernel_init+0x6e/0xc2
| [<0028fd34>] atari_floppy_init+0x0/0x6de
| [<00280a44>] kernel_init+0x0/0xc2
| [<000277f2>] printk+0x0/0x1a
| [<00002ade>] kernel_thread+0x3a/0x4e
|
| Atari floppy driver: max. HD, track buffering
Strange indeed. Does setting FD_MAX_UNITS = 2 help?
Actually that's the default.
But the kernel warning message does go away when #defining it to 1.
At first, I don't see something wrong, compared to
drivers/block/floppy.c.
[ checking lkml ]
Aha, mtd users see it to. I'll jump onto one of those threads...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html