All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: ivo.g.dimitrov.75@gmail.com, khilman@kernel.org,
	tony@atomide.com, aaro.koskinen@iki.fi,
	"kernel list" <linux-kernel@vger.kernel.org>,
	sre@kernel.org, martijn@brixit.nl,
	"Filip Matijević" <filip.matijevic.pz@gmail.com>,
	abcloriens@gmail.com, pali.rohar@gmail.com,
	clayton@craftyguy.net, linux-omap@vger.kernel.org,
	patrikbachan@gmail.com,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	serge@hallyn.com
Subject: Re: v4.13 on nokia n900: oops during tethering
Date: Mon, 19 Feb 2018 20:04:54 +0100	[thread overview]
Message-ID: <20180219190454.GB19366@amd> (raw)
In-Reply-To: <20180213222412.GA1116@mara.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]

Hi!

> On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote:
> > Hi!
> > 
> > During tethering, I got oops in ssi_stop_tx(), followed by failure of
> > GPRS. I used GPRS tethering a lot with some older kernel, and it was
> > stable for hours.
> > 
> > It seems v4.12 has the same problem. In v4.15 usb networking does not
> > work at all, so I can't test... v4.10 seems to have similar problem. (Testing is
> > slighlty tricky, as my internet connection is ... tethering using
> > N900.)
> 
> Based on a quick look ssi_stop_tx() is called too many times (i.e. once
> more than ssi_start_tx()). This would appear to be an interal problem
> with the SSI codebase (or whatever lies there; I don't know the current
> codebase).

If I change BUG_ON in ssi_stop_tx() to warning and return, I see the
warning and system survives it.

> Did this work in the past? When? There appear to have been changes in IRQ
> handling some time in 2016...

Actually, I'm not sure any more :-(. I did have tethering running
overnight some time ago, but it was on slower mobile data, and over
wifi.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: v4.13 on nokia n900: oops during tethering
Date: Mon, 19 Feb 2018 20:04:54 +0100	[thread overview]
Message-ID: <20180219190454.GB19366@amd> (raw)
In-Reply-To: <20180213222412.GA1116@mara.localdomain>

Hi!

> On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote:
> > Hi!
> > 
> > During tethering, I got oops in ssi_stop_tx(), followed by failure of
> > GPRS. I used GPRS tethering a lot with some older kernel, and it was
> > stable for hours.
> > 
> > It seems v4.12 has the same problem. In v4.15 usb networking does not
> > work at all, so I can't test... v4.10 seems to have similar problem. (Testing is
> > slighlty tricky, as my internet connection is ... tethering using
> > N900.)
> 
> Based on a quick look ssi_stop_tx() is called too many times (i.e. once
> more than ssi_start_tx()). This would appear to be an interal problem
> with the SSI codebase (or whatever lies there; I don't know the current
> codebase).

If I change BUG_ON in ssi_stop_tx() to warning and return, I see the
warning and system survives it.

> Did this work in the past? When? There appear to have been changes in IRQ
> handling some time in 2016...

Actually, I'm not sure any more :-(. I did have tethering running
overnight some time ago, but it was on slower mobile data, and over
wifi.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180219/6c1dd7c4/attachment-0001.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: pali.rohar@gmail.com, sre@kernel.org,
	"kernel list" <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
	clayton@craftyguy.net, martijn@brixit.nl,
	"Filip Matijević" <filip.matijevic.pz@gmail.com>
Subject: Re: v4.13 on nokia n900: oops during tethering
Date: Mon, 19 Feb 2018 20:04:54 +0100	[thread overview]
Message-ID: <20180219190454.GB19366@amd> (raw)
In-Reply-To: <20180213222412.GA1116@mara.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

Hi!

> On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote:
> > Hi!
> > 
> > During tethering, I got oops in ssi_stop_tx(), followed by failure of
> > GPRS. I used GPRS tethering a lot with some older kernel, and it was
> > stable for hours.
> > 
> > It seems v4.12 has the same problem. In v4.15 usb networking does not
> > work at all, so I can't test... v4.10 seems to have similar problem. (Testing is
> > slighlty tricky, as my internet connection is ... tethering using
> > N900.)
> 
> Based on a quick look ssi_stop_tx() is called too many times (i.e. once
> more than ssi_start_tx()). This would appear to be an interal problem
> with the SSI codebase (or whatever lies there; I don't know the current
> codebase).

If I change BUG_ON in ssi_stop_tx() to warning and return, I see the
warning and system survives it.

> Did this work in the past? When? There appear to have been changes in IRQ
> handling some time in 2016...

Actually, I'm not sure any more :-(. I did have tethering running
overnight some time ago, but it was on slower mobile data, and over
wifi.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-02-19 19:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 20:10 v4.13 on nokia n900: oops during tethering Pavel Machek
2018-02-12 20:10 ` Pavel Machek
2018-02-13 22:24 ` Sakari Ailus
2018-02-13 22:24   ` Sakari Ailus
2018-02-14 10:27   ` Pavel Machek
2018-02-14 10:27     ` Pavel Machek
2018-02-19 19:04   ` Pavel Machek [this message]
2018-02-19 19:04     ` Pavel Machek
2018-02-19 19:04     ` Pavel Machek

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=20180219190454.GB19366@amd \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=abcloriens@gmail.com \
    --cc=clayton@craftyguy.net \
    --cc=filip.matijevic.pz@gmail.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=martijn@brixit.nl \
    --cc=pali.rohar@gmail.com \
    --cc=patrikbachan@gmail.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=serge@hallyn.com \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.