From: Heinz Diehl <htd@fancy-poultry.org>
To: unlisted-recipients:; (no To-header on input)
Cc: 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 20:11:00 +0200 [thread overview]
Message-ID: <20100920181100.GA12295@fancy-poultry.org> (raw)
In-Reply-To: <20100812164035.GB6761@fritha.org>
On 12.08.2010, Heinz Diehl wrote:
> > >>Could please those of you, who are able to reproduce the problem, verify
> > >>whether the patch below (completely untested) makes everything behave
> > >>again? Thanks.
> > >Yes, everything behaves again. Thanks Jiri.
> > Seconded. Works good. Thanks for your support Jiri.
> Thirded! This fixes the warning here.
Unfortunately, I have to take up this problem a second time.
I considered the issue fixed, and in fact it was using Jiris patch.
However, the same problem came back while testing 2.6.36-rc4 and the
following -git's. /var/log/warn shows the same warning as mentioned in
the first mail in this thread:
Sep 20 08:18:42 liesel apcupsd[5436]: apcupsd FATAL ERROR in linux-usb.c at line 609
Cannot find UPS device -- For a link to detailed USB trouble
shooting information, please see <http://www.apcupsd.com/support.html>.
Sep 20 08:18:42 liesel apcupsd[5436]: apcupsd error shutdown completed
No additional oops this time, only the warning, and my UPS is no longer
working.
Jiris patch obviously didn't made it into 2.6.36-rc4, and it doesn't
apply nay longer either.
Thanks,
Heinz.
next prev parent reply other threads:[~2010-09-20 18:11 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 [this message]
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
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=20100920181100.GA12295@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=alan@signal11.us \
--cc=arnd@arndb.de \
--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
Powered by JetHome