From: "François Valenduc" <francoisvalenduc@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: Kernel crash while copying big files since kernel 3.18
Date: Sun, 25 Jan 2015 20:38:42 +0100 [thread overview]
Message-ID: <54C54642.7000108@gmail.com> (raw)
In-Reply-To: <54B2AC1B.8030107@lwfinger.net>
Le 11/01/15 18:00, Larry Finger a écrit :
> On 01/11/2015 08:35 AM, François Valenduc wrote:
>> Do you still intend to remove the line about allocation failure in the
>> log ? I made a backup of my root partition compressed with pixz and that
>> line appeared 1350 times. So I removed the code which add this line. Is
>> it really expected that it occurs so often ? pixz use multithreading to
>> compress files and therefore at least 3 of the 4 CPU are used during
>> around 20 minutes, but are you sure there is no other problems ?
>
> Yes, I do intend to remove that line; however, I want to keep it for a
> while just in case there are other crashes. If this message never
> appears in that case, then there is another bug.
>
> You are, of course, free to remove it from your system. BTW, how much
> memory do you have?
>
> Larry
>
>
Sorry for having forgotten to answer. I have 4 Gb of RAM. Taking a
backup of a DVD with k9copy also produces so much messages (1479 with a
patch using rate_limit).
Is it really expected that skb allocation fails so often ? Could there
be another problem ?
François
next prev parent reply other threads:[~2015-01-25 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 7:12 Kernel crash while copying big files since kernel 3.18 François Valenduc
2015-01-05 16:13 ` François Valenduc
2015-01-05 17:25 ` Larry Finger
2015-01-05 18:46 ` François Valenduc
2015-01-05 19:25 ` Larry Finger
2015-01-11 14:35 ` François Valenduc
2015-01-11 17:00 ` Larry Finger
2015-01-25 19:38 ` François Valenduc [this message]
2015-01-25 20:24 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C54642.7000108@gmail.com \
--to=francoisvalenduc@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).