Priinting problem - HP Deskjet on AMD 64-bit system

[Tim Frost]

I have a PC with an AMD Athlon CPU, and an HP Deskjet 670C printer
(attached via the parallel port to the PC).

If I install breezy i386 version, I have no problems with the printer.

However, if I install the amd64 version of breezy, I get some text
printed, then the printer starts feeding paper.  This continues until I
cancel the print job, AND reboot both the PC and the printer (clear
buffers on both sides).  For 64-but mode, the generic kernel (rather
than the -k8 version) has been installed:

tim at marvin:~$ uname -a
Linux marvin 2.6.12-10-amd64-generic #1 Fri Nov 18 11:51:07 UTC 2005
x86_64 GNU/Linux

If the printer is attached to another PC (P2-based), I can't print
across the network, because CUPS is configured to only listen on the
loopback address, 127.0.0.1.

When I moved the printer back to the Athlon-based PC, I did the
following:
1: Remove the network printer definition
2: Connect the printer to the parallel port on the Athlon PC
3: Reboot
4: Define the local printer
5: Send the Ubuntu test page to the printer

The text that was printed appears to have been a part of the references
line from a usenet article that I had looked at during the day (prior to
the reboot).  In other recent tests, the data that was printed appears
to have been part of a mail message (different messages for each test).
If the text being printed was on multiple lines, a line feed would
occur, but no carriage return was being sent to the printer.  Doing a
search as root, I only find the usenet text in the cache file that the
pan newsreader uses for that particular newsgroup. 

It isn't clear where the bug is (CUPS, HPLIP or kernel - or a
combination of all 3), but it is clear that it is specific to the 64-bit
AMD version of breezy.  

I do NOT want to trial dapper on this system, because it is my main
machine, and I want a stable working system.

Suggestions welcome on:
* how to get the P2-based system to accept printing from the network
* fixes to the AMD-64 behaviour

I am very tempted to go back to the i386 mode, because this is just the
worst of a number of issues in 64-bit mode (I have problems with
firefox, which seems to crash when the Blackdown java plugin is
activated)