| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 14 Jun 2013 10:53:42 -0500 From: Shawn Bohrer <sbohrer@...advisors.com> To: netdev@...r.kernel.org Cc: ogerlitz@...lanox.com, amirv@...lanox.com Subject: mlx4_core 0000:05:00.0: event 19 arrived I've been testing 3.10-rc5, and while I'm not sure what exactly I was running at the time or if there were any negative effects, but I just noticed my dmesg buffer is completely full of the following messages: ... [137475.687703] mlx4_core 0000:05:00.0: event 19 arrived [137475.688944] mlx4_core 0000:05:00.0: event 19 arrived [137475.689673] mlx4_core 0000:05:00.0: event 19 arrived [137475.697600] mlx4_core 0000:05:00.0: event 19 arrived [137475.699125] mlx4_core 0000:05:00.0: event 19 arrived ... This appears to come from drivers/net/ethernet/mellanox/mlx4/eq.c:473 $ ethtool -i eth4 driver: mlx4_en version: 2.0 (Dec 2011) firmware-version: 2.11.500 bus-info: 0000:05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no I'll see if I can figure out a workload that reproduced the message later today, but perhaps the message is enough to get some ideas from the Mellanox folks. -- Shawn -- --------------------------------------------------------------- This email, along with any attachments, is confidential. If you believe you received this message in error, please contact the sender immediately and delete all copies of the message. Thank you. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists