Hello, A trivial patch. My wifi stopped working recently, and the error message was not too informative (at least to me): kernel: wlp2s0: authenticate with 64:e5:99:74:dc:44 kernel: wlp2s0: send auth to 64:e5:99:74:dc:44 (try 1/3) kernel: wlp2s0: authenticated kernel: wlp2s0: associate with 64:e5:99:74:dc:44 (try 1/3) kernel: wlp2s0: RX AssocResp from 64:e5:99:74:dc:44 (capab=0x411 status=0 aid=1) kernel: wlp2s0: associated kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready dhclient[355]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67 kernel: DRBG: could not allocate digest TFM handle kernel: wlp2s0: deauthenticating from 64:e5:99:74:dc:44 by local choice (Reason: 1=UNSPECIFIED) kernel: cfg80211: Calling CRDA to update world regulatory domain an update error message DRBG: could not allocate digest TFM handle: hmac(sha256) is slightly more helpful (didn't have sha256 config enabled). Sergey Senozhatsky (1): crypto/drbg: report backend_cra_name when allocation fails crypto/drbg.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) -- 2.4.3.368.g7974889 -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html