From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 1/1] hso: fix problem with wrong status code sent by OPTION GTM601 during RING indication Date: Thu, 03 Oct 2013 16:00:49 -0400 (EDT) Message-ID: <20131003.160049.199880461500344692.davem@davemloft.net> References: <20131003.152907.2144013596237714581.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: j.dumon@option.com, marek.belisko@gmail.com, linux-usb@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: hns@goldelico.com Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: "Dr. H. Nikolaus Schaller" Date: Thu, 3 Oct 2013 21:40:34 +0200 > I have made the bug observation from debug log that this bit is set in a response > each time the modem has a RING message. It might be specific to this modem > and firmware version, i.e. a firmware bug. But we have no means to verify or even > change it in the firmware. > > I.e. the driver must handle it in a better way. > > Because the notification is rejected by the driver, the driver will hang up and the > whole modem connection breaks down. > > With this patch, the problem was never observed again in ~2 years. > > I'd hope the maintainer of this driver can shed some light on it. I think if you suspect the bit is set in response to RING messages then you should define a macro so that the number is not just magic, and put a descriptrive comment above the macro definition for that bit.