From: "Justin Mattock" <justinmattock@gmail.com>
To: "Pavel Machek" <pavel@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
marcel@holtmann.org, linux-bluetooth@vger.kernel.org
Subject: Re: hci_usb strikes again (was Re: BUG kmalloc-2048: Poison overwritten)
Date: Tue, 3 Jun 2008 08:30:20 +0000 [thread overview]
Message-ID: <dd18b0c30806030130j9273d8bq380bdea71e60250d@mail.gmail.com> (raw)
In-Reply-To: <20080603064359.GC18599@elf.ucw.cz>
On Tue, Jun 3, 2008 at 6:43 AM, Pavel Machek <pavel@suse.cz> wrote:
> Hi!
>> >> > cpufreq_performance cpufreq_powersave rfcomm hidp l2cap bluetooth fan
>> >> > ipmi_watchdog ipmi_msghandler uinput wlan_tkip ieee80211_crypt_tkip
>> >> > ieee80211_crypt arpt_mangle arptable_filter arp_tables
>> >> > nf_conntrack_ipv4 nf_conntrack iptable_mangle iptable_filter ip_tables
>> >> > x_tables intelfb i2c_i810 i2c_algo_bit coretemp eeprom acpi_cpufreq
>> >> > fglrx(P) applesmc joydev uvcvideo appletouch wlan_scan_sta
>> >> > ath_rate_sample firewire_ohci firewire_core snd_hda_intel ath_pci
>> >> > snd_pcm wlan ohci1394 intel_agp evdev ath_hal(P) snd_timer ieee1394
>> >> > pata_acpi thermal ehci_hcd uhci_hcd snd_page_alloc snd_hwdep agpgart
>> >> > video button processor
>> >> > [ 232.270800]
>> >> > [ 232.270802] Pid: 2690, comm: btdelconn Tainted: P
>> >> > (2.6.26-rc4-00033-g5463508 #4)
>> >
>> > ...and we get oops in bluetooth.
>> >
>> > Use btusb, instead.
>> >
>> > Actually, I guess we should mark hci_usb as broken. I don't see why we
>> > should debug the same problem over and over again.
>
>> Well; "shizzle my frizzle," The funny thing is, is I have not seen
>> this after performing more suspends,
>> maybe this is a every once in a while scenario.
>
> It was "one in three" in my tests; but you need usb actively in use
> while you are suspending for this to bite.
> Pavel
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>
Aahhhh the beast has been discovered.
That's pretty cool!! I quess from my side, I'll try what you had
suggested "btusb".
("I just have to allocate enough time to do so, ("come on people", get
out of my way!!"))
I'm finding myself in one of those days where I'm away from my laptop
(contingency or not).
regards;
--
Justin P. Mattock
next prev parent reply other threads:[~2008-06-03 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 23:13 BUG kmalloc-2048: Poison overwritten Justin Mattock
2008-06-01 23:25 ` Rafael J. Wysocki
2008-06-02 1:02 ` Justin Mattock
2008-06-02 22:21 ` hci_usb strikes again (was Re: BUG kmalloc-2048: Poison overwritten) Pavel Machek
2008-06-02 23:12 ` Justin Mattock
2008-06-03 6:43 ` Pavel Machek
2008-06-03 8:30 ` Justin Mattock [this message]
2008-06-02 2:01 ` BUG kmalloc-2048: Poison overwritten Arjan van de Ven
2008-06-02 3:53 ` Justin Mattock
2008-06-02 4:15 ` Arjan van de Ven
2008-06-02 4:44 ` Justin Mattock
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=dd18b0c30806030130j9273d8bq380bdea71e60250d@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®