From: Oliver Neukum <oliver@neukum.org>
To: "Fabio Bas - Officine Informatiche"
<fabio.bas@officineinformatiche.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: freeze on ppp connection (using an usb "key" modem)
Date: Tue, 26 Jan 2010 15:23:21 +0100 [thread overview]
Message-ID: <201001261523.21656.oliver@neukum.org> (raw)
In-Reply-To: <4B5EF86D.6070109@officineinformatiche.net>
Am Dienstag, 26. Januar 2010 15:13:01 schrieb Fabio Bas - Officine Informatiche:
> On 26/01/2010 13:54, Oliver Neukum wrote:
> > Am Dienstag, 26. Januar 2010 13:53:08 schrieb Rafael J. Wysocki:
> >> On Tuesday 26 January 2010, Fabio Bas - Officine Informatiche wrote:
> >> ...
> >>> The last working kernel i'm aware of is kernel 2.6.30, the first showing
> >>> the problem 2.6.32.2
> >>
> >> Can you test 2.6.31.x please?
> I'll download, compile and test it asap
Yes, that's the best step now.
> >
> > Is there a bugzilla for this?
>
> I've just created it and attached all of my logs
> http://bugzilla.kernel.org/show_bug.cgi?id=15146
>
> > Sysrq-t?
>
> Here's my new crash log; sysrq-t output refers to the time after the
> connection was estabilished but before the freeze. I've tried to
> alt+sysrq+t dìseveral times when the box was freezed, but i had no reply
> from the kernel.
It is too early. Your kernel log suggests generic ppp, which is odd.
If the bug still happens with the newest stable kernel, it would be
a good idea to compile a kernel with lock verification enabled.
Regards
Oliver
prev parent reply other threads:[~2010-01-26 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 11:59 Fabio Bas - Officine Informatiche
2010-01-26 12:53 ` Rafael J. Wysocki
2010-01-26 12:54 ` Oliver Neukum
2010-01-26 14:13 ` Fabio Bas - Officine Informatiche
2010-01-26 14:23 ` Oliver Neukum [this message]
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=201001261523.21656.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=fabio.bas@officineinformatiche.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®