Comment 8 for bug 316405

In my case, this bug hang Jaunty's boot for around 3 minutes !
(with both live-cd and « true » install)

Effectively, to blacklist saa7134 workaround the boot. It's not THE solution, but I think it can be worth to do nothing: it is easy to remove a blacklisted module if necessary and, in the other hand, a user can think that everything have crashed and may not wait a few minutes on each boot → he may give-up.

Here is an extract of my dmesg (it's very similar to syldeb35's one)

[ 95.692399] [<c0103f6b>] ? sysenter_do_call+0x12/0x2f
[ 95.692399] [<c0500000>] ? relay_hotcpu_callback+0x4d/0xbd
[ 95.692399] Code: 30 58 ec c7 8b 55 90 8b 82 2c 01 00 00 89 5c 24 04 c7 04 24 38 84 64 f8 89 44 24 08 e8 13 58 ec c7 66 90 8b 45 90 e8 40 fd ff ff <8b> 5d f4 31 c0 8b 75 f8 8b 7d fc 89 ec 5d c3 90 8b 4d 90 8b 71
[ 95.692399] EIP: [<f863b2c0>] saa7134_board_init2+0x140/0x710 [saa7134] SS:ESP 0068:f6001c58
[ 95.692399] ---[ end trace d21dcb8059f41868 ]---
[ 277.610090] Adding 1156640k swap on /dev/sda6. Priority:-1 extents:1 across:1156640k
[ 288.803273] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 288.803276] Bluetooth: BNEP filters: protocol multicast
[ 288.845507] Bridge firewalling registered
...

Thanks (and sorry for my English)