lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BANLkTinm9Yydw_bSxj2s1=G3ayoJz8Ph7g@mail.gmail.com>
Date:	Mon, 18 Apr 2011 12:54:47 +0200
From:	Zdenek Kabelac <zdenek.kabelac@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>,
	Zdenek Kabelac <zdenek.kabelac@...il.com>,
	USB list <linux-usb@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-bluetooth@...r.kernel.org, padovan@...fusion.mobi
Subject: Re: Endless print of uhci_result_common: failed with status 440000

2011/4/12 Gustavo F. Padovan <padovan@...fusion.mobi>:
> * Alan Stern <stern@...land.harvard.edu> [2011-04-12 12:10:56 -0400]:
>
>> On Tue, 12 Apr 2011, Zdenek Kabelac wrote:
>>
>> > 2011/4/11 Alan Stern <stern@...land.harvard.edu>:
>> > > On Mon, 11 Apr 2011, Zdenek Kabelac wrote:
>> > >
>> > >> > I've created:
>> > >> >
>> > >> > https://bugzilla.kernel.org/show_bug.cgi?id=33062
>> > >> >
>> > >> > and I'm cc-ing linux-bluetooth.
>> > >> >
>> > >>
>> > >> In fact this Ooops might be related to:
>> > >>
>> > >> http://marc.info/?l=linux-kernel&m=130207593728273&w=2
>> > >
>> > > It might be. ?Did you try reverting the patch mentioned in that email?
>> > >
>> >
>> > Yep - it looks like the patch
>> > http://marc.info/?l=linux-bluetooth&m=130230770920378&w=2
>> > solved my problem with weird deadlocks.
>
> I pushed a patch that fixes this in a better way, it's on the bluetooth-2.6
> tree (should arrive to linus tree in some days).


hmm

Ok  - I assume you mean this patch:

http://git.kernel.org/?p=linux/kernel/git/padovan/bluetooth-2.6.git;a=commitdiff;h=b7d850641d2bc45b2320bfcb096f11406890ff3a

It seems to be detaching timer slightly differently as the one from
Keith probably.
Here is the trace I've got with older Keith's patch (which I've
believed was fine already)

iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
------------[ cut here ]------------
WARNING: at lib/list_debug.c:30 __list_add+0x8f/0xa0()
Hardware name: 6464CTO
list_add corruption. prev->next should be next (ffff88013b139390), but
was 2020203a6c61746f. (prev=ffff880137b63350).
Modules linked in: sunrpc ipt_REJECT xt_physdev xt_state
iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4
nf_conntrack nf_defrag_ipv4 ip_tables x_tables btusb bluetooth
snd_hda_codec_analog arc4 ecb crypto_blkcipher cryptomgr aead
crypto_algapi snd_hda_intel iwl3945 snd_hda_codec snd_seq iwl_legacy
snd_seq_device mac80211 snd_pcm thinkpad_acpi cfg80211 snd_timer
e1000e psmouse snd serio_raw wmi soundcore i2c_i801 snd_page_alloc
nvram iTCO_wdt iTCO_vendor_support evdev i915 dm_mirror dm_region_hash
dm_log dm_mod drm_kms_helper drm i2c_algo_bit i2c_core autofs4 usbhid
hid pcmcia sdhci_pci sdhci ehci_hcd uhci_hcd mmc_core sr_mod cdrom
yenta_socket usbcore video backlight
Pid: 44, comm: kworker/1:2 Not tainted 2.6.39-rc3-00236-g115ab9e #7
Call Trace:
 [<ffffffff810501df>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff810502d6>] warn_slowpath_fmt+0x46/0x50
 [<ffffffff812988ef>] __list_add+0x8f/0xa0
 [<ffffffff810602f3>] internal_add_timer+0xb3/0x140
 [<ffffffff81062bd2>] mod_timer+0x152/0x450
 [<ffffffff81117bb6>] ? refresh_cpu_vm_stats+0x106/0x170
 [<ffffffff81062ee8>] add_timer+0x18/0x20
 [<ffffffff8106df4f>] queue_delayed_work_on+0xbf/0x140
 [<ffffffff8106f0d1>] queue_delayed_work+0x21/0x40
 [<ffffffff8106f10b>] schedule_delayed_work+0x1b/0x20
 [<ffffffff81117c71>] vmstat_update+0x51/0x60
 [<ffffffff81070c38>] process_one_work+0x1c8/0x6f0
 [<ffffffff81070bd7>] ? process_one_work+0x167/0x6f0
 [<ffffffff81493c44>] ? retint_restore_args+0xe/0xe
 [<ffffffff81117c20>] ? refresh_cpu_vm_stats+0x170/0x170
 [<ffffffff81071539>] worker_thread+0x159/0x340
 [<ffffffff810713e0>] ? rescuer_thread+0x240/0x240
 [<ffffffff810760fb>] kthread+0x9b/0xa0
 [<ffffffff8149b9d4>] kernel_thread_helper+0x4/0x10
 [<ffffffff810367a4>] ? finish_task_switch+0x74/0x110
 [<ffffffff8149367b>] ? _raw_spin_unlock_irq+0x3b/0x60
 [<ffffffff81493c44>] ? retint_restore_args+0xe/0xe
 [<ffffffff81076060>] ? __init_kthread_worker+0x70/0x70
 [<ffffffff8149b9d0>] ? gs_change+0xb/0xb
---[ end trace 9184dc8969677db3 ]---

I'll see whether new version will not show this warning.

Zdenek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ