I've attached a small snippet of dmesg output (produced by "dmesg > file"). It's from kernel 2.6.5-1.358. Notice that there are >130 spaces at the start of some lines, and those lines also have their data truncated. It looks as if some memcpy has a bad offset. Arjan and Steve, is this a known bug that's solved in the latest 2.6.6 kernel? -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Attachment:
dmesg.gz
Description: GNU Zip compressed data
