public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USB Problems
Date: Sun, 12 Jun 2011 23:54:25 +0200	[thread overview]
Message-ID: <1314310.F05an9OY84@localhost> (raw)
In-Reply-To: <20110612153012.7b8bf4fa@arcticwolf.myzen.co.uk>

On Sunday 12 June 2011 15:30:12 john wrote:
> Gents
> 
> Whenever I insert external USB device my machine locks and I have to do
> a hard reset (sys req does not even work). I have tried this in a
> graphical environment and without. Machine boots up fine with USB
> keyboard and mouse but will not boot up with usb storage (memory stick
> - tried several)
> 
> I have recently upgrade kernel to 2.6.38-r6 when this error started
> (approx). Hav also tried 2.6.38-r7 (which according to bugzilla
> should fix an issue similar to this) the error still happens.
> 
> Any suggestions on kernel config options, debugging would be
> appreciated. And how to trap full error message.
> 
> Error message alongs these lines
> 
> Kernel panic not syncing - fatal exception in iterrupt
> ksoftirqd/1 Not tainted


have the same problem with 2.6.39 and 2.6.39.1

Whenever I disconnect my telephone from usb I have a 1 in 5 chance of a nice 
panic.

Since your is an always panic maybe you should recreate it with vanilla 
sources and report it on lkml.
-- 
#163933



  parent reply	other threads:[~2011-06-12 21:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 14:30 [gentoo-user] USB Problems john
2011-06-12 14:45 ` meino.cramer
2011-06-12 18:45   ` john
2011-06-12 19:20     ` meino.cramer
2011-06-12 20:50       ` Dale
2011-06-12 21:32         ` john
2011-06-12 21:57           ` Dale
2011-06-13  5:22             ` john
2011-06-13  5:44               ` Dale
2011-06-14  5:38                 ` john
2011-06-14  6:59                   ` Thanasis
2011-06-13  6:42               ` meino.cramer
2011-06-13 11:00                 ` Volker Armin Hemmann
2011-06-12 21:55         ` Volker Armin Hemmann
2011-06-12 22:04           ` Dale
2011-06-12 21:30       ` john
2011-06-12 23:35         ` Volker Armin Hemmann
2011-06-12 23:56         ` meino.cramer
2011-06-12 21:54 ` Volker Armin Hemmann [this message]
2011-06-15 23:34 ` Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2011-06-14  7:18 JDM
2011-06-14 11:52 ` Indi
2011-06-14 15:50   ` Dale
2011-06-14 15:56     ` Thanasis
2011-06-16  7:30 JDM
2014-08-26 20:29 siefke_listen
2014-08-27  5:54 ` Alexander Kapshuk
2014-08-27  6:04 ` Alexander Kapshuk
2014-08-28 18:49 ` siefke_listen
2014-09-03 23:25 ` siefke_listen
2014-09-04  4:58   ` J. Roeleveld
2014-09-06 16:52     ` siefke_listen
2014-09-06 17:38       ` Alexander Kapshuk
2014-09-06 18:35       ` J. Roeleveld
2014-09-06 23:11         ` siefke_listen
2014-09-07  7:42           ` J. Roeleveld
2014-09-07 15:54             ` siefke_listen
2014-09-08 19:03               ` J. Roeleveld
2014-09-08 20:04                 ` Neil Bothwick
2014-09-09  5:04                 ` Stroller

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=1314310.F05an9OY84@localhost \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.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