Think this is a new lockdep; seen after updating to 2432, on insertion of an
Orinoco PC Card.  Not immediately reproducible, and have been using other
kernels post-lockdep and haven't seen this before.

eth1: Station name "HERMES I"
eth1: ready
eth1: orinoco_cs at 0.0, irq 7, io 0xc100-0xc13f
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth1: New link status: Disconnected (0002)

======================================================
[ INFO: hard-safe -> hard-unsafe lock order detected ]
------------------------------------------------------
events/0/5 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
 (&skb_queue_lock_key){-+..}, at: [<c05aab55>] skb_queue_tail+0x14/0x32

and this task is already holding:
 (&priv->lock#2){++..}, at: [<e05ea32f>] orinoco_send_wevents+0x1e/0x7b [orinoco
]
which would create a new lock dependency:
 (&priv->lock#2){++..} -> (&skb_queue_lock_key){-+..}

but this new dependency connects a hard-irq-safe lock:
 (&priv->lock#2){++..}
... which became hard-irq-safe at:
  [<c043be8b>] lock_acquire+0x4b/0x6c
  [<c0607417>] _spin_lock_irqsave+0x22/0x32
  [<e05ea3ce>] orinoco_interrupt+0x42/0xe29 [orinoco]
  [<c044fa14>] handle_IRQ_event+0x20/0x4d
  [<c044fad5>] __do_IRQ+0x94/0xef
  [<c040674c>] do_IRQ+0xb9/0xcd
  [<c0404a49>] common_interrupt+0x25/0x2c
  [<c040662f>] do_softirq+0x5a/0xbe

to a hard-irq-unsafe lock:
 (&skb_queue_lock_key){-+..}
... which became hard-irq-unsafe at:
...  [<c043be8b>] lock_acquire+0x4b/0x6c
  [<c0607118>] _spin_lock_bh+0x1e/0x2d
  [<c05e5095>] udp_poll+0x49/0xce
  [<c05a6248>] sock_poll+0x12/0x15
  [<c048237a>] do_sys_poll+0x1f7/0x3c3
  [<c048257a>] sys_poll+0x34/0x36
  [<c0403faf>] syscall_call+0x7/0xb

Attaching full dmesg.