public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: RE: cifs causes BUG: soft lockup detected on CPU
Date: Sun, 01 Apr 2007 14:38:43 -0500	[thread overview]
Message-ID: <46100A43.9040001@us.ibm.com> (raw)

"Valentin Zaharov"  wrote on 04/01/2007 03:02:07 AM:
 > Hi again,
 >
 > After applying changes manually to 2.6.20.4 according to the link that
 > Steven sent I still get those errors (attached below) but no crash so
 > far.
 > I am wondering if its ok or having errors still will cause freezes.
It is ok and I see no indication of lookup. You have two errors logged:
a) a missing entry in the kernel translation table for your default
codepage to UCS-16 (Unicode).
    "char2uni returned -22"  (EINVAL, presumably due to a missing character)
b) some access denied (-13) warnings on cifs_get_info_info (lookup).
This is probably harmless.

We could isolate the failing character by modifying the error log entry
but you may be able to guess at the problem by seeing which filenames
are requested with '?' in it ('?' is used when translation to Unicode
fails)

We could probably isolate the missing character by checking what
is logged to dmesag after this minor modification to the warning
message (we would also need to know which nls codepage
you are running).

diff --git a/fs/cifs/cifs_unicode.c b/fs/cifs/cifs_unicode.c
index d2a8b29..793c4b9 100644
--- a/fs/cifs/cifs_unicode.c
+++ b/fs/cifs/cifs_unicode.c
@@ -74,8 +74,8 @@ cifs_strtoUCS(__le16 * to, const char *f
         charlen = codepage->char2uni(from, len, &wchar_to[i]);
         if (charlen < 1) {
             cERROR(1,
-                   ("cifs_strtoUCS: char2uni returned %d",
-                charlen));
+                   ("strtoUCS: char2uni of %d returned %d",
+                (int)*from, charlen));
             /* A question mark */
             to[i] = cpu_to_le16(0x003f);
             charlen = 1;



 > Thanks in advance,
 >
 > Apr  1 04:23:49 UFR2 kernel:  CIFS VFS: cifs_strtoUCS: char2uni returned
 > -22
 > Apr  1 04:37:14 UFR2 last message repeated 30 times
 > Apr  1 04:38:53 UFR2 last message repeated 10 times
 > Apr  1 04:40:33 UFR2 last message repeated 10 times
 > Apr  1 04:45:31 UFR2 last message repeated 10 times
 > Apr  1 04:47:11 UFR2 last message repeated 10 times
 > Apr  1 05:00:32 UFR2 last message repeated 10 times
 > Apr  1 05:07:21 UFR2 last message repeated 10 times
 > Apr  1 05:21:50 UFR2 last message repeated 10 times
 > Apr  1 05:23:29 UFR2 last message repeated 10 times
 > Apr  1 05:29:07 UFR2 last message repeated 10 times
 > Apr  1 05:30:58 UFR2 last message repeated 10 times
 > Apr  1 05:30:58 UFR2 last message repeated 9 times
 > Apr  1 05:55:33 UFR2 kernel:  CIFS VFS: Error 0xfffffff3 on
 > cifs_get_inode_info in lookup of \nv322657
 > Apr  1 05:55:33 UFR2 kernel:  CIFS VFS: Error 0xfffffff3 on
 > cifs_get_inode_info in lookup of \nv322657
 > Apr  1 06:28:41 UFR2 kernel:  CIFS VFS: cifs_strtoUCS: char2uni returned
 > -22
 > Apr  1 07:24:36 UFR2 last message repeated 10 times
 > Apr  1 07:26:29 UFR2 last message repeated 10 times
 > Apr  1 07:28:17 UFR2 last message repeated 10 times
 > Apr  1 07:30:09 UFR2 last message repeated 10 times
 > Apr  1 07:35:45 UFR2 last message repeated 10 times
 > Apr  1 07:44:46 UFR2 last message repeated 10 times
 > Apr  1 08:23:10 UFR2 last message repeated 10 times
 > Apr  1 08:24:52 UFR2 last message repeated 10 times
 > Apr  1 10:04:37 UFR2 last message repeated 10 times
 > Apr  1 10:04:37 UFR2 last message repeated 8 times
 > Apr  1 10:36:17 UFR2 kernel:  CIFS VFS: Error 0xfffffff3 on
 > cifs_get_inode_info in lookup of \nv322657
 > Apr  1 10:36:18 UFR2 last message repeated 4 times
 > Apr  1 10:38:19 UFR2 kernel:  CIFS VFS: cifs_strtoUCS: char2uni returned
 > -22
 >
 >
 > Valentin Zaharov
 >
 > System Department
 >
 > NetVision Ltd.

             reply	other threads:[~2007-04-01 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 19:38 Steve French (smfltc) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01  8:02 cifs causes BUG: soft lockup detected on CPU Valentin Zaharov
2007-03-29 15:42 Valentin Zaharov
2007-03-29  9:35 Valentin Zaharov
2007-03-29  9:13 Valentin Zaharov
2007-03-29  9:21 ` Andrew Morton
2007-03-29  8:32 Valentin Zaharov
2007-03-28 18:35 Valentin Zaharov
2007-03-29  8:54 ` Andrew Morton
2007-03-29 15:06   ` Steven French

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=46100A43.9040001@us.ibm.com \
    --to=smfltc@us.ibm.com \
    --cc=linux-kernel@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