Hi, I get a warning from lockdep during boot; 2.6.18-rc3 don't have this warning. I see a similar report in the archive (I haven't found time to test the patch...): http://marc.theaimsgroup.com/?l=linux-netdev&m=115506258902757&w=2 but my stacktrace is a bit different, so I'm reporting this one too: ================================= [ INFO: inconsistent lock state ] --------------------------------- inconsistent {in-softirq-W} -> {softirq-on-W} usage. ifconfig/1812 [HC0[0]:SC0[0]:HE1:SE1] takes: (&ifa->lock){-+..}, at: [] inet6_addr_add+0xd9/0x160 [ipv6] {in-softirq-W} state was registered at: [] lock_acquire+0x5d/0x80 [] _spin_lock_bh+0x3a/0x50 [] addrconf_dad_timer+0x5b/0x100 [ipv6] [] run_timer_softirq+0x149/0x170 [] __do_softirq+0x62/0xc0 [] do_softirq+0x55/0x60 [] irq_exit+0x4b/0x50 [] do_IRQ+0x4c/0x90 [] common_interrupt+0x25/0x2c [] cpu_idle+0x41/0x70 [] rest_init+0x37/0x40 [] start_kernel+0x2ba/0x360 [] 0xb0100199 irq event stamp: 4501 hardirqs last enabled at (4501): [] local_bh_enable_ip+0x95/0x110 hardirqs last disabled at (4499): [] local_bh_enable_ip+0x2f/0x110 softirqs last enabled at (4500): [] ipv6_add_addr+0x3e/0x270 [ipv6] softirqs last disabled at (4488): [] _read_lock_bh+0xe/0x50 other info that might help us debug this: 1 lock held by ifconfig/1812: #0: (rtnl_mutex){--..}, at: [] mutex_lock+0x1c/0x20 stack backtrace: [] show_trace+0x12/0x20 [] dump_stack+0x19/0x20 [] print_usage_bug+0x23e/0x250 [] mark_lock+0x5a9/0x5c0 [] __lock_acquire+0x806/0xd20 [] lock_acquire+0x5d/0x80 [] _spin_lock+0x35/0x50 [] inet6_addr_add+0xd9/0x160 [ipv6] [] addrconf_add_ifaddr+0x69/0x80 [ipv6] [] inet6_ioctl+0x72/0x90 [ipv6] [] sock_ioctl+0xfe/0x1f0 [] do_ioctl+0x28/0x80 [] vfs_ioctl+0x57/0x2c0 [] sys_ioctl+0x39/0x60 [] syscall_call+0x7/0xb Luca -- Home: http://kronoz.cjb.net Il tempo speso a coltivare sogni non è sprecato.