| 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: Sun, 9 Nov 2014 20:44:48 +0100 From: devzero@....de To: netdev@...r.kernel.org Cc: "Jeff Garzik" <jgarzik@...ox.com>, "Mark Brown" <broonie@...nel.org> Subject: BUG ? - natsemi: Allow users to disable workaround for DspCfg reset Hi, i wanted to get rid of some heavy natsemi driver dmesg spamming like Apr 1 11:50:06 debian7 kernel: [ 4400.311000] eth0: possible phy reset: re-initializing Apr 1 11:50:06 debian7 kernel: [ 4400.311319] eth0: DSPCFG accepted after 0 usec. Apr 1 11:50:06 debian7 kernel: [ 4400.311433] eth0: Wake-up event 0x80000b Apr 1 11:50:06 debian7 kernel: [ 4400.311537] eth0: Setting full-duplex based on negotiated link capability. and was happy to find a module param - but i`m confused about dspcfg_workaround parameter usage. i can indeed disable the spamming by setting natsemi.dspcfg_workaround=0 at boot. but should`t /sys/devices/pci0000:00/0000:00:0f.0/dspcfg_workaround reflect the current state then and shouldn`t i be able to set this also via echo 0|1 or off|on >..... at runtime ? that does not seem to work. it always shows "off" and i cannot change the behaviour via this file. regards roland references: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1a14780960888c97371a9918f42c4dbe6957efb4 ps: jeff/mark - pardon, i sent the mail a second time because of mistyping mailinglist-adress due to marc.info list naming... -- 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