grep: memory exhausted

I am occasionally getting the following kernel message:

Sep 19 08:54:02 mach2 kernel: usbhid: probe of 3-2.4:1.1 failed with error -5

I did a grep to find all occurrences of usbhid in the logs, and this is what happened:

# cd /var/log
# grep usbhid *
anaconda.syslog:<6>usbcore: registered new driver usbhid
dmesg:usbcore: registered new driver usbhid
grep: memory exhausted

I found this unusual, as I have 2 GB of ram (not a lot these days, but more than I've ever had before).

Does anyone know why grep would be exhausting available ram?

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Relevant Pages

  • Re: grep: memory exhausted
    ... I did a grep to find all occurrences of usbhid in the logs, ... I found this unusual, as I have 2 GB of ram (not a lot these days, but more ...
    (RedHat)
  • RE: grep: memory exhausted
    ... bounces@xxxxxxxxxx] On Behalf Of Manuel Arostegui Ramirez ... I did a grep to find all occurrences of usbhid in the logs, ... Does anyone know why grep would be exhausting available ram? ...
    (RedHat)
  • Re: grep: memory exhausted
    ... bounces@xxxxxxxxxx] On Behalf Of Manuel Arostegui Ramirez ... I did a grep to find all occurrences of usbhid in the logs, ... Does anyone know why grep would be exhausting available ram? ...
    (RedHat)
  • Re: ata4294967295: failed to start port (errno=-19)
    ... I did grep the logs and found ... that it first appeared in 2.6.24-rc1 (+ some git mayve) on Nov 3. ... gets there first I'll give a go at tracing this next week. ...
    (Linux-Kernel)
  • Re: Best way to get max KVA setting?
    ... > I could probably grep for this, but what's the best way to get a hold of ... > autosize option, and I want to base it on min so that it ... for the 8G of RAM in his 2G KVA space, ...
    (freebsd-current)