From: Heinz Diehl <htd@fritha.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Heinz Diehl <htd@fancy-poultry.org>, Alan Ott <alan@signal11.us>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Jiri Kosina <jkosina@suse.cz>,
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: Mon, 20 Sep 2010 21:39:13 +0200 [thread overview]
Message-ID: <20100920193913.GA6448@fritha.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1009201456260.2010-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On 20.09.2010, Alan Stern wrote:
> > Jiris patch obviously didn't made it into 2.6.36-rc4, and it doesn't
> > apply nay longer either.
> No, you're wrong. The patch _is_ in 2.6.36-rc4, and that's the reason
> why it doesn't apply any longer.
Yes, you're right.
> The error you see must have a different cause. Have you read this
> thread?
>
> http://marc.info/?t=128494644600005&r=1&w=2
No, not before until now. This problem seems not to be related to what I
see on my machines, and reverting commit 8fe294caf8c868edd9046251824a0af91991bf43 as
mentioned in there doesn't help either.
2.6.35.4 works, 2.6.36-rc4 does not. What can I do to help to find the
issue?
Attached are the dmesg output for both 2.6.35.4 and 2.6.36-rc4.
[-- Attachment #2: dmesg-2.6.35.4.txt.bz2 --]
[-- Type: application/octet-stream, Size: 12833 bytes --]
[-- Attachment #3: dmesg-2.6.36-rc4.txt.bz2 --]
[-- Type: application/octet-stream, Size: 12568 bytes --]
next prev parent reply other threads:[~2010-09-20 19:39 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 [this message]
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
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=20100920193913.GA6448@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 \
--cc=stern@rowland.harvard.edu \
/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).