I just imported some data from a SQL-Dump (GZip compressed) which included some "CREATE TABLE"s and many INSERTs.
Almost the complete dump was executed when this error occured:
#1153 - Got a packet bigger than 'max_allowed_packet' bytes
Ok, one of the INSERTs was too big, no problem.
But phpMyAdmin displayed this insert and that was a problem for my browser.
I think it's not very clever to display a command which is too big for the database.
I added a screenshot.
My suggestion is not to display the SQL when MySQL-Error #1153 occurs.
Screenshot
Logged In: YES
user_id=1383652
Originator: NO
that's how *PHP* reacts when the gzip buffer overflows.
use the "uploaddir" feature (see docs) and unzip the file (manually or by means of a php-script) before import.
Logged In: YES
user_id=210714
Originator: NO
Fixed for 2.11.6, see
http://phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin/branches/QA_2_11/phpMyAdmin/libraries/common.lib.php?r1=11082&r2=11150