linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fritha.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Heinz Diehl <htd@fancy-poultry.org>, Alan Ott <alan@signal11.us>,
	Markus Trippelsdorf <markus@trippelsdorf.de>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-input@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [BUG] object: is not initialized, yet kobject_put() is being called
Date: Tue, 21 Sep 2010 18:20:11 +0200	[thread overview]
Message-ID: <20100921162011.GA6720@fritha.org> (raw)
In-Reply-To: <20100921161107.GA6534@fritha.org>

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

On 21.09.2010, Heinz Diehl wrote: 

> Dmesg output is attached. 
 
> /dev/usb is not existent on my systems (opensuse 11.1 and 11.2).
> It doesn't exist with 2.6.35.4 either, which works perfectly.

And these are dmesg output and strace -f from the working 2.6.35.4
kernel. No /dev/usb here either.








[-- Attachment #2: 2.6.35.4-dmesg.txt.bz2 --]
[-- Type: application/octet-stream, Size: 12650 bytes --]

[-- Attachment #3: 2.6.35.4.output.txt.bz2 --]
[-- Type: application/octet-stream, Size: 12702 bytes --]

  reply	other threads:[~2010-09-21 16:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 21:09 [BUG] USB no longer works for APCUPS Heinz Diehl
2010-08-10 22:32 ` [BUG] object: is not initialized, yet kobject_put() is being called Markus Trippelsdorf
2010-08-12  9:11   ` Jiri Kosina
2010-08-12  9:16     ` Markus Trippelsdorf
2010-08-12 11:18       ` Jiri Kosina
2010-08-12 11:26         ` Alan Ott
2010-08-12 11:36         ` Markus Trippelsdorf
2010-08-12 11:45           ` Markus Trippelsdorf
2010-08-12 11:56             ` Markus Trippelsdorf
2010-08-12 12:07               ` Jiri Kosina
2010-08-12 12:57                 ` Jiri Kosina
2010-08-12 13:04                   ` Markus Trippelsdorf
2010-08-12 13:09                     ` Alan Ott
2010-08-12 13:11                       ` Jiri Kosina
2010-08-12 13:14                         ` Alan Ott
2010-08-12 13:17                         ` Markus Trippelsdorf
2010-08-12 16:40                       ` Heinz Diehl
2010-08-19  7:41                         ` Jiri Kosina
2010-09-20 18:11                         ` Heinz Diehl
2010-09-20 18:58                           ` Alan Stern
2010-09-20 19:39                             ` Heinz Diehl
2010-09-21 13:14                               ` Jiri Kosina
2010-09-21 14:55                           ` Jiri Kosina
2010-09-21 15:09                             ` Heinz Diehl
2010-09-21 15:14                               ` Jiri Kosina
2010-09-21 15:27                                 ` Heinz Diehl
2010-09-21 15:53                                   ` Jiri Kosina
2010-09-21 16:11                                     ` Heinz Diehl
2010-09-21 16:20                                       ` Heinz Diehl [this message]
2010-09-21 16:24                                   ` Jiri Kosina
2010-09-21 18:48                                     ` Heinz Diehl
2010-08-12 11:55           ` Jiri Kosina
2010-08-12 11:23     ` Alan Ott
2010-08-12 16:37     ` Heinz Diehl

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=20100921162011.GA6720@fritha.org \
    --to=htd@fritha.org \
    --cc=alan@signal11.us \
    --cc=arnd@arndb.de \
    --cc=htd@fancy-poultry.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    /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;
as well as URLs for NNTP newsgroup(s).