From: David Brownell <david-b@pacbell.net>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, speedtouch@ml.free.fr
Subject: Re: [linux-usb-devel] Re: USB related oops in 2.6.6-rk2-bk3 (similar with 2.6.5)
Date: Wed, 28 Apr 2004 10:31:46 -0700 [thread overview]
Message-ID: <408FEA82.1040309@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0404281325250.5272@alpha.polcom.net>
Grzegorz Kulewski wrote:
> Is anybody going to look at it? It prevents my system from shuting down.
Looks like one of the problems already fixed in the latest bk-usb.patch
found in the MM kernels ...
- Dave
> On Tue, 27 Apr 2004, Grzegorz Kulewski wrote:
>
>
>>Hi,
>>
>>I experienced this oops. I have uhci-hcd and two devices. One is usb
>>camera (TC111 - probably not supported under linux?) and the
>>second is speedtouch modem. Everytime I shut down my system (Gentoo) with
>>2.6.5 and newer I get some oops but system log is down before that and I
>>have no time to hack start scripts to stop shuting syslog. It occures when
>>removing some usb modules. So I stopped speedtouch and removed the modules
>>manually (in stop scripts order I hope). But I have not removed uhci-hcd
>>module (this module is removed in other part of stop scripts). And...
>>nothing happened. So I unplugged speedtouch and replugged it back. And I
>>immendiatelly got atached oops. (I think that I should use ksymoops, but
>>it is searching for /proc/ksyms that is not present in 2.6 and it does not
>>like /proc/kallsyms... And it produces nothing but warnings. What options
>>should I use?)
>>
>>What can I do to help track the problem down?
>>
>>
>>thanks in advance
>>
>>Grzegorz Kulewski
>>
>>
>>PS. I am subscribbed only to LKML, so CC me, please.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> linux-usb-devel@lists.sourceforge.net
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
>
next prev parent reply other threads:[~2004-04-28 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 19:54 [ANNOUNCE] WOLK v2.3 for Kernel v2.6.4 Marc-Christian Petersen
2004-03-27 21:42 ` speedtouch and/or USB problem (2.6.4-WOLK2.3) Grzegorz Kulewski
2004-03-27 23:51 ` [linux-usb-devel] " Alan Stern
2004-03-31 9:21 ` Marc-Christian Petersen
2004-03-31 13:39 ` Grzegorz Kulewski
2004-04-02 13:27 ` [linux-usb-devel] speedtouch and/or USB problem (2.6.4-WOLK2.3 and 2.6.5-rc3-mm4) Grzegorz Kulewski
2004-04-04 11:56 ` Grzegorz Kulewski
2004-03-31 14:11 ` [linux-usb-devel] speedtouch and/or USB problem (2.6.4-WOLK2.3) Leopold Gouverneur
2004-03-31 15:28 ` Alan Stern
2004-04-26 23:30 ` USB related oops in 2.6.6-rk2-bk3 (similar with 2.6.5) Grzegorz Kulewski
2004-04-28 11:27 ` Grzegorz Kulewski
2004-04-28 11:40 ` Duncan Sands
2004-04-28 17:31 ` David Brownell [this message]
2004-04-28 20:02 ` [linux-usb-devel] " Duncan Sands
2004-04-28 13:05 ` Bill Davidsen
2004-04-28 14:14 ` Grzegorz Kulewski
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=408FEA82.1040309@pacbell.net \
--to=david-b@pacbell.net \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=speedtouch@ml.free.fr \
/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