From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751951AbaGSFDB (ORCPT ); Sat, 19 Jul 2014 01:03:01 -0400 Received: from valhalla.ausics.net ([27.33.160.23]:54864 "EHLO mail.ausics.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751124AbaGSFC6 (ORCPT ); Sat, 19 Jul 2014 01:02:58 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 19 Jul 2014 15:02:55 +1000 From: ressy66@ausics.net To: linux-kernel@vger.kernel.org Subject: 3.14.12 and =?UTF-8?Q?option=5Finstat=5Fcallback=20with=20=33G=20?= =?UTF-8?Q?DONGLE?= Message-ID: User-Agent: Roundcube Webmail Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log and dmesg are flooded with constant messages option1 ttyUSB0: option_instat_callback: error -2 The device still works, it sends and receives SMS's as well, I tried setting verbose usb debug to see if it offers any more explanations, but it shows nothing more. The device is Huawei E160, but is identified as (and always has been) an E620 ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem Did somthing break between 3.12 and 3.14? Rather annoying at how fast and large kernel.log is geting.