I then upgraded the 2nd Squeeze partition to Testing/Wheezy and the same
error occurred as above.

<SNIP>

Hi Wayne,
You reported is problem on Feb 27, right?
The IRQ 19 problem I reported then seems to disappear when I boot my
machine with the "irqpoll" parameter.
At least it has been up for 15 days with its /proc/irq/19/spurious
looking like this:
count 58513
unhandled 2
last_unhandled 1208748848 ms
the last unhandled IRQ being nearly 14 days ago.
Mark

Thanks Mark. Good to know it is working for you at least.
Did you do an upgrade or anything else before trying the irqpoll?
The irqpoll didn't work here, sadly, so I am still looking for the cause of
the problem.

Hi Wayne,
No, adding the irqpoll param was absolutely the only change I made.
Having trouble with the same IRQ number may just be a coincidence
given the different hardware; my system assigns IRQ 19 to my hard
disks and some USB ports. But still, that both problems should
originate from cpu idle...maybe I just don't understand the stack
trace.

From what I was able to glean from the net, these problems aren't

easily resolved and seem to be hardware related. Do you have another
wireless card you could try?

No I don't but, if it was hardware then I would expect that my Sid
partition, which I am using now, and my 5+ year old testing partition

would have the same error, which they don't.
4 partitions on the same drive and 2 are working and, 2 are not.

I just did an upgrade on the, wheezy/testing partition with the irq 19
problem. The kernel-image was upgraded to linux-image-2.6.32-5-amd
2.6.32-31. I had hopes that this would fix the problem. No Joy, the
problem remains. Note that I have 2 wireless connections so I was
upgradeing using the GSM Modem which is a PPP connection.

I tried to upgrade the Squeeze partition but the problem has esculated
and neither interface works on it so no net access at all now on Squeeze.