Re: [Bluez-devel] [BUG] rfcomm

2008-02-20 Thread Stefan Seyfried
Dave Young schrieb:

>> Feb 16 23:41:33 alon1 BUG: unable to handle kernel NULL pointer dereference 
>> at virtual address 0008
>> Feb 16 23:41:33 alon1 printing eip: c01b2db6 *pde =  
>> Feb 16 23:41:33 alon1 Oops:  [#1] PREEMPT 
>> Feb 16 23:41:33 alon1 Modules linked in: ppp_deflate zlib_deflate 
>> zlib_inflate bsd_comp ppp_async rfcomm l2cap hci_usb vmnet(P) vmmon(P) tun 
>> radeon drm autofs4 ipv6 aes_generic crypto_algapi ieee80211_crypt_ccmp 
>> nf_nat_irc nf_nat_ftp nf_conntrack_irc nf_conntrack_ftp ipt_MASQUERADE 
>> iptable_nat nf_nat ipt_REJECT xt_tcpudp ipt_LOG xt_limit xt_state 
>> nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables snd_pcm_oss 
>> snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
>> snd_seq_device bluetooth ppp_generic slhc ioatdma dca cfq_iosched 
>> cpufreq_powersave cpufreq_ondemand cpufreq_conservative acpi_cpufreq 
>> freq_table uinput fan af_packet nls_cp1255 nls_iso8859_1 nls_utf8 nls_base 
>> pcmcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm nsc_ircc snd_timer 
>> ipw2200 thinkpad_acpi irda snd ehci_hcd yenta_socket uhci_hcd psmouse 
>> ieee80211 soundcore intel_agp hwmon rsrc_nonstatic pcspkr e1000 crc_ccitt 
>> snd_page_alloc i2c_i801 ieee80211_crypt pcmcia_core agpgart thermal b
a
>  ttery nvram rtc sr_mod ac sg firmware_class button processor cdrom unix 
> usbcore evdev ext3 jbd ext2 mbcache loop ata_piix libata sd_mod scsi_mod
>> Feb 16 23:41:33 alon1 
>> Feb 16 23:41:33 alon1 Pid: 4, comm: events/0 Tainted: P
>> (2.6.24-gentoo-r2 #1)
>> Feb 16 23:41:33 alon1 EIP: 0060:[] EFLAGS: 00010282 CPU: 0
>> Feb 16 23:41:33 alon1 EIP is at sysfs_get_dentry+0x26/0x80
>> Feb 16 23:41:33 alon1 EAX:  EBX:  ECX:  EDX: f48a2210
>> Feb 16 23:41:33 alon1 ESI: f72eb900 EDI: f4803ae0 EBP: f4803ae0 ESP: f7c49efc
>> Feb 16 23:41:33 alon1 hcid[7004]: HCI dev 0 registered
>> Feb 16 23:41:33 alon1 DS: 007b ES: 007b FS:  GS:  SS: 0068
>> Feb 16 23:41:33 alon1 Process events/0 (pid: 4, ti=f7c48000 task=f7c3efc0 
>> task.ti=f7c48000)
>> Feb 16 23:41:33 alon1 Stack: f7cb6140 f4822668 f7e71e10 c01b304d  
>>  fffe c030ba9c 
>> Feb 16 23:41:33 alon1 f7cb6140 f4822668 f6da6720 f7cb6140 f4822668 f6da6720 
>> c030ba8e c01ce20b 
>> Feb 16 23:41:33 alon1 f6e9dd00 c030ba8e f6da6720 f6e9dd00 f6e9dd00  
>> f4822600  
>> Feb 16 23:41:33 alon1 Call Trace:
>> Feb 16 23:41:33 alon1 [] sysfs_move_dir+0x3d/0x1f0
>> Feb 16 23:41:33 alon1 [] kobject_move+0x9b/0x120
>> Feb 16 23:41:33 alon1 [] device_move+0x51/0x110
>> Feb 16 23:41:33 alon1 [] del_conn+0x0/0x70 [bluetooth]
>> Feb 16 23:41:33 alon1 [] del_conn+0x19/0x70 [bluetooth]
>> Feb 16 23:41:33 alon1 [] run_workqueue+0x81/0x140
>> Feb 16 23:41:33 alon1 [] schedule+0x168/0x2e0

> Could you try patch below?

Works fine for me. Thanks. Together with the other two patches already taken
by davem, this fixes all my current BT problems :-)

> Defer hci_unregister_sysfs because hci device could be destructed
> while hci conn devices still there.
> 
> Signed-off-by: Dave Young <[EMAIL PROTECTED]>
> 
> ---
> net/bluetooth/hci_core.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff -upr linux/net/bluetooth/hci_core.c linux.new/net/bluetooth/hci_core.c
> --- linux/net/bluetooth/hci_core.c2008-02-20 18:27:28.0 +0800
> +++ linux.new/net/bluetooth/hci_core.c2008-02-20 18:28:34.0 
> +0800
> @@ -901,8 +901,6 @@ int hci_unregister_dev(struct hci_dev *h
>  
>   BT_DBG("%p name %s type %d", hdev, hdev->name, hdev->type);
>  
> - hci_unregister_sysfs(hdev);
> -
>   write_lock_bh(_dev_list_lock);
>   list_del(>list);
>   write_unlock_bh(_dev_list_lock);
> @@ -914,6 +912,8 @@ int hci_unregister_dev(struct hci_dev *h
>  
>   hci_notify(hdev, HCI_DEV_UNREG);
>  
> + hci_unregister_sysfs(hdev);
> +
>   __hci_dev_put(hdev);
>  
>   return 0;
-- 
Stefan Seyfried
R Team Mobile Devices|  "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Bluez-devel] [BUG] rfcomm

2008-02-20 Thread Stefan Seyfried
Dave Young schrieb:

 Feb 16 23:41:33 alon1 BUG: unable to handle kernel NULL pointer dereference 
 at virtual address 0008
 Feb 16 23:41:33 alon1 printing eip: c01b2db6 *pde =  
 Feb 16 23:41:33 alon1 Oops:  [#1] PREEMPT 
 Feb 16 23:41:33 alon1 Modules linked in: ppp_deflate zlib_deflate 
 zlib_inflate bsd_comp ppp_async rfcomm l2cap hci_usb vmnet(P) vmmon(P) tun 
 radeon drm autofs4 ipv6 aes_generic crypto_algapi ieee80211_crypt_ccmp 
 nf_nat_irc nf_nat_ftp nf_conntrack_irc nf_conntrack_ftp ipt_MASQUERADE 
 iptable_nat nf_nat ipt_REJECT xt_tcpudp ipt_LOG xt_limit xt_state 
 nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables snd_pcm_oss 
 snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
 snd_seq_device bluetooth ppp_generic slhc ioatdma dca cfq_iosched 
 cpufreq_powersave cpufreq_ondemand cpufreq_conservative acpi_cpufreq 
 freq_table uinput fan af_packet nls_cp1255 nls_iso8859_1 nls_utf8 nls_base 
 pcmcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm nsc_ircc snd_timer 
 ipw2200 thinkpad_acpi irda snd ehci_hcd yenta_socket uhci_hcd psmouse 
 ieee80211 soundcore intel_agp hwmon rsrc_nonstatic pcspkr e1000 crc_ccitt 
 snd_page_alloc i2c_i801 ieee80211_crypt pcmcia_core agpgart thermal b
a
  ttery nvram rtc sr_mod ac sg firmware_class button processor cdrom unix 
 usbcore evdev ext3 jbd ext2 mbcache loop ata_piix libata sd_mod scsi_mod
 Feb 16 23:41:33 alon1 
 Feb 16 23:41:33 alon1 Pid: 4, comm: events/0 Tainted: P
 (2.6.24-gentoo-r2 #1)
 Feb 16 23:41:33 alon1 EIP: 0060:[c01b2db6] EFLAGS: 00010282 CPU: 0
 Feb 16 23:41:33 alon1 EIP is at sysfs_get_dentry+0x26/0x80
 Feb 16 23:41:33 alon1 EAX:  EBX:  ECX:  EDX: f48a2210
 Feb 16 23:41:33 alon1 ESI: f72eb900 EDI: f4803ae0 EBP: f4803ae0 ESP: f7c49efc
 Feb 16 23:41:33 alon1 hcid[7004]: HCI dev 0 registered
 Feb 16 23:41:33 alon1 DS: 007b ES: 007b FS:  GS:  SS: 0068
 Feb 16 23:41:33 alon1 Process events/0 (pid: 4, ti=f7c48000 task=f7c3efc0 
 task.ti=f7c48000)
 Feb 16 23:41:33 alon1 Stack: f7cb6140 f4822668 f7e71e10 c01b304d  
  fffe c030ba9c 
 Feb 16 23:41:33 alon1 f7cb6140 f4822668 f6da6720 f7cb6140 f4822668 f6da6720 
 c030ba8e c01ce20b 
 Feb 16 23:41:33 alon1 f6e9dd00 c030ba8e f6da6720 f6e9dd00 f6e9dd00  
 f4822600  
 Feb 16 23:41:33 alon1 Call Trace:
 Feb 16 23:41:33 alon1 [c01b304d] sysfs_move_dir+0x3d/0x1f0
 Feb 16 23:41:33 alon1 [c01ce20b] kobject_move+0x9b/0x120
 Feb 16 23:41:33 alon1 [c0241711] device_move+0x51/0x110
 Feb 16 23:41:33 alon1 [f9aaed80] del_conn+0x0/0x70 [bluetooth]
 Feb 16 23:41:33 alon1 [f9aaed99] del_conn+0x19/0x70 [bluetooth]
 Feb 16 23:41:33 alon1 [c012c1a1] run_workqueue+0x81/0x140
 Feb 16 23:41:33 alon1 [c02c0c88] schedule+0x168/0x2e0

 Could you try patch below?

Works fine for me. Thanks. Together with the other two patches already taken
by davem, this fixes all my current BT problems :-)

 Defer hci_unregister_sysfs because hci device could be destructed
 while hci conn devices still there.
 
 Signed-off-by: Dave Young [EMAIL PROTECTED]
 
 ---
 net/bluetooth/hci_core.c |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 
 diff -upr linux/net/bluetooth/hci_core.c linux.new/net/bluetooth/hci_core.c
 --- linux/net/bluetooth/hci_core.c2008-02-20 18:27:28.0 +0800
 +++ linux.new/net/bluetooth/hci_core.c2008-02-20 18:28:34.0 
 +0800
 @@ -901,8 +901,6 @@ int hci_unregister_dev(struct hci_dev *h
  
   BT_DBG(%p name %s type %d, hdev, hdev-name, hdev-type);
  
 - hci_unregister_sysfs(hdev);
 -
   write_lock_bh(hci_dev_list_lock);
   list_del(hdev-list);
   write_unlock_bh(hci_dev_list_lock);
 @@ -914,6 +912,8 @@ int hci_unregister_dev(struct hci_dev *h
  
   hci_notify(hdev, HCI_DEV_UNREG);
  
 + hci_unregister_sysfs(hdev);
 +
   __hci_dev_put(hdev);
  
   return 0;
-- 
Stefan Seyfried
RD Team Mobile Devices|  Any ideas, John?
SUSE LINUX Products GmbH, Nürnberg | Well, surrounding them's out.

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote:
> Hi,
> sorry for reply again, this seems a diffrent issue ...

All that I do is running pppd over the rfcomm, suspending the system and resume.
I don't load any binary module.

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


Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote:
> On 11/5/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> > On 11/5/07, Dave Young <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > > I managed to produce this bug last weekend. I debugged it and found a
> > > rfcomm_dev refcnt BUG.
> > > please try the patch of attachment, sorry for attachement because of
> > > my gmail/mutt configuration problem.
> > >
> > > I post it in below thread:
> > > http://lkml.org/lkml/2007/11/4/207
> >
> > It actually worse... :(
>
Hi,
sorry for reply again, this seems a diffrent issue ...

Regards
dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/5/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> On 11/5/07, Dave Young <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I managed to produce this bug last weekend. I debugged it and found a
> > rfcomm_dev refcnt BUG.
> > please try the patch of attachment, sorry for attachement because of
> > my gmail/mutt configuration problem.
> >
> > I post it in below thread:
> > http://lkml.org/lkml/2007/11/4/207
>
> It actually worse... :(

could you tell me your usage steps of rfcomm?

Oct 23 19:41:42 alon1 EIP:0060:[]Tainted: PVLI
Your kernel seems tainted.

Regards
dave

>
> Best Regards,
> Alon Bar-Lev
>
> ---
>
> terrupt :02:01.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
> ieee80211_crypt: registered algorithm 'NULL'
> ieee80211: 802.11 data/management/control stack, git-1.1.13
> ieee80211: Copyright (C) 2004-2005 Intel Corporation <[EMAIL PROTECTED]>
> ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
> ipw2200: Copyright(c) 2003-2006 Intel Corporation
> Synaptics Touchpad, model: 1, fw: 5.9, id: 0x2c6ab1, caps: 0x884793/0x0
> serio: Synaptics pass-through port at isa0060/serio1/input0
> input: SynPS/2 Synaptics TouchPad as 
> /devices/platform/i8042/serio1/input/input2
> pnp: Device 00:0c activated.
> nsc-ircc, chip->init
> nsc-ircc, Found chip at base=0x02e
> nsc-ircc, driver loaded (Dag Brattli)
> IrDA: Registered device irda0
> nsc-ircc, Found dongle: HP HSDL-1100/HSDL-2100
> e1000: :02:01.0: e1000_probe: (PCI:33MHz:32-bit) 00:11:25:2e:e5:1f
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> Yenta: CardBus bridge found at :02:00.1 [1014:0552]
> Yenta: Using INTVAL to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket :02:00.1, mfunc 0x01d21b22, devctl 0x64
> Yenta: ISA IRQ mask 0x04b0, PCI irq 11
> Socket status: 3086
> pcmcia: parent PCI bridge I/O window: 0x4000 - 0x8fff
> pcmcia: parent PCI bridge Memory window: 0xc020 - 0xcfff
> pcmcia: parent PCI bridge Memory window: 0xe800 - 0xefff
> ACPI: PCI Interrupt :00:1f.5[B] -> Link [LNKB] -> GSI 11 (level,
> low) -> IRQ 11
> PCI: Setting latency timer of device :00:1f.5 to 64
> udev: renamed network interface eth0 to eth1
> usb 2-1: new full speed USB device using uhci_hcd and address 3
> usb 2-1: configuration #1 chosen from 1 choice
> usb 3-1: new full speed USB device using uhci_hcd and address 2
> usb 3-1: configuration #1 chosen from 1 choice
> Bluetooth: Core ver 2.11
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: HCI USB driver ver 2.9
> intel8x0_measure_ac97_clock: measured 50304 usecs
> intel8x0: clocking to 48000
> ACPI: PCI Interrupt :02:02.0[A] -> Link [LNKC] -> GSI 11 (level,
> low) -> IRQ 11
> ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
> usb 3-2: new full speed USB device using uhci_hcd and address 3
> usb 3-2: configuration #1 chosen from 1 choice
> usbcore: registered new interface driver hci_usb
> ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
> IBM TrackPoint firmware: 0x0e, buttons: 3/3
> input: TPPS/2 IBM TrackPoint as
> /devices/platform/i8042/serio1/serio2/input/input3
> EXT3 FS on loop5, internal journal
> NET: Registered protocol family 17
> Non-volatile memory driver v1.2
> thinkpad_acpi: ThinkPad ACPI Extras v0.16
> thinkpad_acpi: http://ibm-acpi.sf.net/
> thinkpad_acpi: ThinkPad BIOS 1RETDPWW (3.21 ), EC 1RHT71WW-3.04
> thinkpad_acpi: IBM ThinkPad T42
> input: ThinkPad Extra Buttons as /devices/virtual/input/input4
> hdaps: IBM ThinkPad T42 detected.
> hdaps: initial latch check good (0x01).
> hdaps: device successfully initialized.
> input: hdaps as /devices/platform/hdaps/input/input5
> hdaps: driver successfully loaded.
> ACPI: AC Adapter [AC] (on-line)
> ACPI: Battery Slot [BAT0] (battery present)
> input: Power Button (FF) as /devices/virtual/input/input6
> ACPI: Power Button (FF) [PWRF]
> input: Lid Switch as /devices/virtual/input/input7
> ACPI: Lid Switch [LID]
> input: Sleep Button (CM) as /devices/virtual/input/input8
> ACPI: Sleep Button (CM) [SLPB]
> ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
> ACPI: Processor [CPU] (supports 8 throttling states)
> ACPI: Thermal Zone [THM0] (57 C)
> Marking TSC unstable due to: possible TSC halt in C2.
> Time: acpi_pm clocksource has been installed.
> IBM machine detected. Enabling interrupts during APM calls.
> apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
> dazuko: loaded, version=2.3.4
> io scheduler cfq registered
> Module ioatdma cannot be unloaded due to unsafe usage in
> drivers/dma/ioatdma.c:805
> PPP generic driver version 2.4.2
> SCSI subsystem initialized
> Adding 1465120k swap on /dev/loop/4.  Priority:-1 extents:1 across:1465120k
> hda: selected mode 0x45
> hda: cache flushes supported
> hdc: selected mode 0x42
> hdc: host side 80-wire cable detection failed, limiting 

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/5/07, Dave Young <[EMAIL PROTECTED]> wrote:
> Hi,
> I managed to produce this bug last weekend. I debugged it and found a
> rfcomm_dev refcnt BUG.
> please try the patch of attachment, sorry for attachement because of
> my gmail/mutt configuration problem.
>
> I post it in below thread:
> http://lkml.org/lkml/2007/11/4/207

It actually worse... :(

Best Regards,
Alon Bar-Lev

---

terrupt :02:01.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <[EMAIL PROTECTED]>
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x2c6ab1, caps: 0x884793/0x0
serio: Synaptics pass-through port at isa0060/serio1/input0
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2
pnp: Device 00:0c activated.
nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Found dongle: HP HSDL-1100/HSDL-2100
e1000: :02:01.0: e1000_probe: (PCI:33MHz:32-bit) 00:11:25:2e:e5:1f
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Yenta: CardBus bridge found at :02:00.1 [1014:0552]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket :02:00.1, mfunc 0x01d21b22, devctl 0x64
Yenta: ISA IRQ mask 0x04b0, PCI irq 11
Socket status: 3086
pcmcia: parent PCI bridge I/O window: 0x4000 - 0x8fff
pcmcia: parent PCI bridge Memory window: 0xc020 - 0xcfff
pcmcia: parent PCI bridge Memory window: 0xe800 - 0xefff
ACPI: PCI Interrupt :00:1f.5[B] -> Link [LNKB] -> GSI 11 (level,
low) -> IRQ 11
PCI: Setting latency timer of device :00:1f.5 to 64
udev: renamed network interface eth0 to eth1
usb 2-1: new full speed USB device using uhci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.9
intel8x0_measure_ac97_clock: measured 50304 usecs
intel8x0: clocking to 48000
ACPI: PCI Interrupt :02:02.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
usb 3-2: new full speed USB device using uhci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hci_usb
ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
IBM TrackPoint firmware: 0x0e, buttons: 3/3
input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input3
EXT3 FS on loop5, internal journal
NET: Registered protocol family 17
Non-volatile memory driver v1.2
thinkpad_acpi: ThinkPad ACPI Extras v0.16
thinkpad_acpi: http://ibm-acpi.sf.net/
thinkpad_acpi: ThinkPad BIOS 1RETDPWW (3.21 ), EC 1RHT71WW-3.04
thinkpad_acpi: IBM ThinkPad T42
input: ThinkPad Extra Buttons as /devices/virtual/input/input4
hdaps: IBM ThinkPad T42 detected.
hdaps: initial latch check good (0x01).
hdaps: device successfully initialized.
input: hdaps as /devices/platform/hdaps/input/input5
hdaps: driver successfully loaded.
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
input: Power Button (FF) as /devices/virtual/input/input6
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /devices/virtual/input/input7
ACPI: Lid Switch [LID]
input: Sleep Button (CM) as /devices/virtual/input/input8
ACPI: Sleep Button (CM) [SLPB]
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU] (supports 8 throttling states)
ACPI: Thermal Zone [THM0] (57 C)
Marking TSC unstable due to: possible TSC halt in C2.
Time: acpi_pm clocksource has been installed.
IBM machine detected. Enabling interrupts during APM calls.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
dazuko: loaded, version=2.3.4
io scheduler cfq registered
Module ioatdma cannot be unloaded due to unsafe usage in
drivers/dma/ioatdma.c:805
PPP generic driver version 2.4.2
SCSI subsystem initialized
Adding 1465120k swap on /dev/loop/4.  Priority:-1 extents:1 across:1465120k
hda: selected mode 0x45
hda: cache flushes supported
hdc: selected mode 0x42
hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
hdc: UDMA speeds >UDMA33 cannot be set
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
eth0: Setting MAC to 00:a0:68:7c:46:06
fbcondecor: console 1 using theme 

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/5/07, Dave Young [EMAIL PROTECTED] wrote:
 Hi,
 I managed to produce this bug last weekend. I debugged it and found a
 rfcomm_dev refcnt BUG.
 please try the patch of attachment, sorry for attachement because of
 my gmail/mutt configuration problem.

 I post it in below thread:
 http://lkml.org/lkml/2007/11/4/207

It actually worse... :(

Best Regards,
Alon Bar-Lev

---

terrupt :02:01.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED]
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x2c6ab1, caps: 0x884793/0x0
serio: Synaptics pass-through port at isa0060/serio1/input0
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2
pnp: Device 00:0c activated.
nsc-ircc, chip-init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Found dongle: HP HSDL-1100/HSDL-2100
e1000: :02:01.0: e1000_probe: (PCI:33MHz:32-bit) 00:11:25:2e:e5:1f
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Yenta: CardBus bridge found at :02:00.1 [1014:0552]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket :02:00.1, mfunc 0x01d21b22, devctl 0x64
Yenta: ISA IRQ mask 0x04b0, PCI irq 11
Socket status: 3086
pcmcia: parent PCI bridge I/O window: 0x4000 - 0x8fff
pcmcia: parent PCI bridge Memory window: 0xc020 - 0xcfff
pcmcia: parent PCI bridge Memory window: 0xe800 - 0xefff
ACPI: PCI Interrupt :00:1f.5[B] - Link [LNKB] - GSI 11 (level,
low) - IRQ 11
PCI: Setting latency timer of device :00:1f.5 to 64
udev: renamed network interface eth0 to eth1
usb 2-1: new full speed USB device using uhci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.9
intel8x0_measure_ac97_clock: measured 50304 usecs
intel8x0: clocking to 48000
ACPI: PCI Interrupt :02:02.0[A] - Link [LNKC] - GSI 11 (level,
low) - IRQ 11
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
usb 3-2: new full speed USB device using uhci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hci_usb
ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
IBM TrackPoint firmware: 0x0e, buttons: 3/3
input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input3
EXT3 FS on loop5, internal journal
NET: Registered protocol family 17
Non-volatile memory driver v1.2
thinkpad_acpi: ThinkPad ACPI Extras v0.16
thinkpad_acpi: http://ibm-acpi.sf.net/
thinkpad_acpi: ThinkPad BIOS 1RETDPWW (3.21 ), EC 1RHT71WW-3.04
thinkpad_acpi: IBM ThinkPad T42
input: ThinkPad Extra Buttons as /devices/virtual/input/input4
hdaps: IBM ThinkPad T42 detected.
hdaps: initial latch check good (0x01).
hdaps: device successfully initialized.
input: hdaps as /devices/platform/hdaps/input/input5
hdaps: driver successfully loaded.
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
input: Power Button (FF) as /devices/virtual/input/input6
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /devices/virtual/input/input7
ACPI: Lid Switch [LID]
input: Sleep Button (CM) as /devices/virtual/input/input8
ACPI: Sleep Button (CM) [SLPB]
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU] (supports 8 throttling states)
ACPI: Thermal Zone [THM0] (57 C)
Marking TSC unstable due to: possible TSC halt in C2.
Time: acpi_pm clocksource has been installed.
IBM machine detected. Enabling interrupts during APM calls.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
dazuko: loaded, version=2.3.4
io scheduler cfq registered
Module ioatdma cannot be unloaded due to unsafe usage in
drivers/dma/ioatdma.c:805
PPP generic driver version 2.4.2
SCSI subsystem initialized
Adding 1465120k swap on /dev/loop/4.  Priority:-1 extents:1 across:1465120k
hda: selected mode 0x45
hda: cache flushes supported
hdc: selected mode 0x42
hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
hdc: UDMA speeds UDMA33 cannot be set
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
eth0: Setting MAC to 00:a0:68:7c:46:06
fbcondecor: console 1 using theme 'livecd-2007.0'
fbcondecor: 

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/5/07, Alon Bar-Lev [EMAIL PROTECTED] wrote:
 On 11/5/07, Dave Young [EMAIL PROTECTED] wrote:
  Hi,
  I managed to produce this bug last weekend. I debugged it and found a
  rfcomm_dev refcnt BUG.
  please try the patch of attachment, sorry for attachement because of
  my gmail/mutt configuration problem.
 
  I post it in below thread:
  http://lkml.org/lkml/2007/11/4/207

 It actually worse... :(

could you tell me your usage steps of rfcomm?

Oct 23 19:41:42 alon1 EIP:0060:[c01c575b]Tainted: PVLI
Your kernel seems tainted.

Regards
dave


 Best Regards,
 Alon Bar-Lev

 ---

 terrupt :02:01.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11
 ieee80211_crypt: registered algorithm 'NULL'
 ieee80211: 802.11 data/management/control stack, git-1.1.13
 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED]
 ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
 ipw2200: Copyright(c) 2003-2006 Intel Corporation
 Synaptics Touchpad, model: 1, fw: 5.9, id: 0x2c6ab1, caps: 0x884793/0x0
 serio: Synaptics pass-through port at isa0060/serio1/input0
 input: SynPS/2 Synaptics TouchPad as 
 /devices/platform/i8042/serio1/input/input2
 pnp: Device 00:0c activated.
 nsc-ircc, chip-init
 nsc-ircc, Found chip at base=0x02e
 nsc-ircc, driver loaded (Dag Brattli)
 IrDA: Registered device irda0
 nsc-ircc, Found dongle: HP HSDL-1100/HSDL-2100
 e1000: :02:01.0: e1000_probe: (PCI:33MHz:32-bit) 00:11:25:2e:e5:1f
 e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
 Yenta: CardBus bridge found at :02:00.1 [1014:0552]
 Yenta: Using INTVAL to route CSC interrupts to PCI
 Yenta: Routing CardBus interrupts to PCI
 Yenta TI: socket :02:00.1, mfunc 0x01d21b22, devctl 0x64
 Yenta: ISA IRQ mask 0x04b0, PCI irq 11
 Socket status: 3086
 pcmcia: parent PCI bridge I/O window: 0x4000 - 0x8fff
 pcmcia: parent PCI bridge Memory window: 0xc020 - 0xcfff
 pcmcia: parent PCI bridge Memory window: 0xe800 - 0xefff
 ACPI: PCI Interrupt :00:1f.5[B] - Link [LNKB] - GSI 11 (level,
 low) - IRQ 11
 PCI: Setting latency timer of device :00:1f.5 to 64
 udev: renamed network interface eth0 to eth1
 usb 2-1: new full speed USB device using uhci_hcd and address 3
 usb 2-1: configuration #1 chosen from 1 choice
 usb 3-1: new full speed USB device using uhci_hcd and address 2
 usb 3-1: configuration #1 chosen from 1 choice
 Bluetooth: Core ver 2.11
 NET: Registered protocol family 31
 Bluetooth: HCI device and connection manager initialized
 Bluetooth: HCI socket layer initialized
 Bluetooth: HCI USB driver ver 2.9
 intel8x0_measure_ac97_clock: measured 50304 usecs
 intel8x0: clocking to 48000
 ACPI: PCI Interrupt :02:02.0[A] - Link [LNKC] - GSI 11 (level,
 low) - IRQ 11
 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
 usb 3-2: new full speed USB device using uhci_hcd and address 3
 usb 3-2: configuration #1 chosen from 1 choice
 usbcore: registered new interface driver hci_usb
 ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
 IBM TrackPoint firmware: 0x0e, buttons: 3/3
 input: TPPS/2 IBM TrackPoint as
 /devices/platform/i8042/serio1/serio2/input/input3
 EXT3 FS on loop5, internal journal
 NET: Registered protocol family 17
 Non-volatile memory driver v1.2
 thinkpad_acpi: ThinkPad ACPI Extras v0.16
 thinkpad_acpi: http://ibm-acpi.sf.net/
 thinkpad_acpi: ThinkPad BIOS 1RETDPWW (3.21 ), EC 1RHT71WW-3.04
 thinkpad_acpi: IBM ThinkPad T42
 input: ThinkPad Extra Buttons as /devices/virtual/input/input4
 hdaps: IBM ThinkPad T42 detected.
 hdaps: initial latch check good (0x01).
 hdaps: device successfully initialized.
 input: hdaps as /devices/platform/hdaps/input/input5
 hdaps: driver successfully loaded.
 ACPI: AC Adapter [AC] (on-line)
 ACPI: Battery Slot [BAT0] (battery present)
 input: Power Button (FF) as /devices/virtual/input/input6
 ACPI: Power Button (FF) [PWRF]
 input: Lid Switch as /devices/virtual/input/input7
 ACPI: Lid Switch [LID]
 input: Sleep Button (CM) as /devices/virtual/input/input8
 ACPI: Sleep Button (CM) [SLPB]
 ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
 ACPI: Processor [CPU] (supports 8 throttling states)
 ACPI: Thermal Zone [THM0] (57 C)
 Marking TSC unstable due to: possible TSC halt in C2.
 Time: acpi_pm clocksource has been installed.
 IBM machine detected. Enabling interrupts during APM calls.
 apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
 dazuko: loaded, version=2.3.4
 io scheduler cfq registered
 Module ioatdma cannot be unloaded due to unsafe usage in
 drivers/dma/ioatdma.c:805
 PPP generic driver version 2.4.2
 SCSI subsystem initialized
 Adding 1465120k swap on /dev/loop/4.  Priority:-1 extents:1 across:1465120k
 hda: selected mode 0x45
 hda: cache flushes supported
 hdc: selected mode 0x42
 hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
 hdc: UDMA speeds UDMA33 cannot be set
 Bluetooth: L2CAP ver 2.8
 Bluetooth: L2CAP socket layer 

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/6/07, Dave Young [EMAIL PROTECTED] wrote:
 On 11/5/07, Alon Bar-Lev [EMAIL PROTECTED] wrote:
  On 11/5/07, Dave Young [EMAIL PROTECTED] wrote:
   Hi,
   I managed to produce this bug last weekend. I debugged it and found a
   rfcomm_dev refcnt BUG.
   please try the patch of attachment, sorry for attachement because of
   my gmail/mutt configuration problem.
  
   I post it in below thread:
   http://lkml.org/lkml/2007/11/4/207
 
  It actually worse... :(

Hi,
sorry for reply again, this seems a diffrent issue ...

Regards
dave
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/6/07, Dave Young [EMAIL PROTECTED] wrote:
 Hi,
 sorry for reply again, this seems a diffrent issue ...

All that I do is running pppd over the rfcomm, suspending the system and resume.
I don't load any binary module.

Alon.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Bluez-devel] [BUG] rfcomm]

2007-11-04 Thread Dave Young
On 10/24/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have this issue for long time (At least from linux-2.6.18).
> I think it is about time I report this... :)
>
> When coming out of suspend (uswsusp or suspend2) if rfcomm was
> active it creates this dump.
>
> If you need any more info I will be glad to provide.
>
> Best Regards,
> Alon Bar-Lev.
>
> ---
>
> Oct 23 17:51:33 alon1 acpid: received event "button/power PWRF 0080 
> 0001"
> Oct 23 17:51:33 alon1 acpid: notifying client 7903[0:0]
> Oct 23 17:51:33 alon1 acpid: notifying client 7804[0:0]
> Oct 23 17:51:33 alon1 acpid: executing action "/etc/acpi/default.sh 
> button/power PWRF 0080 0001"
> Oct 23 17:52:13 alon1 ntpd[8186]: synchronized to 192.115.25.179, stratum 2
> Oct 23 17:52:16 alon1 swsusp: Marking nosave pages: 0009f000 - 
> 0010
> Oct 23 17:52:16 alon1 swsusp: Basic memory bitmaps created
> Oct 23 19:41:22 alon1 pppd[25041]: Hangup (SIGHUP)
> Oct 23 19:41:22 alon1 pppd[25041]: Modem hangup
> Oct 23 19:41:22 alon1 pppd[25041]: Connect time 384.5 minutes.
> Oct 23 19:41:22 alon1 pppd[25041]: Sent 512470 bytes, received 1546102 bytes.
> Oct 23 19:41:22 alon1 pppd[25041]: Connection terminated.
> Oct 23 19:41:40 alon1 Stopping tasks ... done.
> Oct 23 19:41:40 alon1 Shrinking memory...   - \ | / - \ | / - \ | / - \ | / - 
> \ | / - \ | / - \ | / - \ | / - \ | / - \ | done (224831 pages freed)
> Oct 23 19:41:40 alon1 Freed 899324 kbytes in 14.70 seconds (61.17 MB/s)
> Oct 23 19:41:40 alon1 Suspending console(s)
> Oct 23 19:41:40 alon1 usbfs 2-2:1.0: no suspend for driver usbfs?
> Oct 23 19:41:40 alon1 pnp: Device 00:0c disabled.
> Oct 23 19:41:40 alon1 eth0: Going into suspend...
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :02:02.0 disabled
> Oct 23 19:41:40 alon1 ACPI handle has no context!
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :02:01.0 disabled
> Oct 23 19:41:40 alon1 ACPI handle has no context!
> Oct 23 19:41:40 alon1 radeonfb (:01:00.0): suspending for event: 1...
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1f.5 disabled
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.7 disabled
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.2 disabled
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.1 disabled
> Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.0 disabled
> Oct 23 19:41:40 alon1 swsusp: critical section:
> Oct 23 19:41:40 alon1 swsusp: Need to copy 126188 pages
> Oct 23 19:41:40 alon1 Intel machine check architecture supported.
> Oct 23 19:41:40 alon1 Intel machine check reporting enabled on CPU#0.
> Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.0[A] -> Link [LNKA] -> 
> GSI 11 (level, low) -> IRQ 11
> Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.0 to 64
> Oct 23 19:41:40 alon1 usb usb1: root hub lost power or was reset
> Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.1[B] -> Link [LNKD] -> 
> GSI 11 (level, low) -> IRQ 11
> Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.1 to 64
> Oct 23 19:41:40 alon1 usb usb2: root hub lost power or was reset
> Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.2[C] -> Link [LNKC] -> 
> GSI 11 (level, low) -> IRQ 11
> Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.2 to 64
> Oct 23 19:41:40 alon1 usb usb3: root hub lost power or was reset
> Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.7[D] -> Link [LNKH] -> 
> GSI 11 (level, low) -> IRQ 11
> Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.7 to 64
> Oct 23 19:41:40 alon1 usb usb4: root hub lost power or was reset
> Oct 23 19:41:40 alon1 ehci_hcd :00:1d.7: debug port 1
> Oct 23 19:41:40 alon1 PCI: cache line size of 32 is not supported by device 
> :00:1d.7
> Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1e.0 to 64
> Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1f.1[A] -> Link [LNKC] -> 
> GSI 11 (level, low) -> IRQ 11
> Oct 23 19:41:42 alon1 PM: Writing back config space on device :00:1f.5 at 
> offset 1 (was 297, writing 293)
> Oct 23 19:41:42 alon1 ACPI: PCI Interrupt :00:1f.5[B] -> Link [LNKB] -> 
> GSI 11 (level, low) -> IRQ 11
> Oct 23 19:41:42 alon1 PCI: Setting latency timer of device :00:1f.5 to 64
> Oct 23 19:41:42 alon1 radeonfb (:01:00.0): resuming from state: 1...
> Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.0 at 
> offset f (was 3c0010b, writing 5c0010b)
> Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.0 at 
> offset 3 (was 824008, writing 82a810)
> Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.0 at 
> offset 1 (was 2100107, writing 217)
> Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.1 at 
> offset f (was 3c0020b, writing 5c0020b)
> Oct 23 19:41:42 alon1 PM: Writing back config 

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-04 Thread Dave Young
On 10/24/07, Alon Bar-Lev [EMAIL PROTECTED] wrote:

 Hello,

 I have this issue for long time (At least from linux-2.6.18).
 I think it is about time I report this... :)

 When coming out of suspend (uswsusp or suspend2) if rfcomm was
 active it creates this dump.

 If you need any more info I will be glad to provide.

 Best Regards,
 Alon Bar-Lev.

 ---

 Oct 23 17:51:33 alon1 acpid: received event button/power PWRF 0080 
 0001
 Oct 23 17:51:33 alon1 acpid: notifying client 7903[0:0]
 Oct 23 17:51:33 alon1 acpid: notifying client 7804[0:0]
 Oct 23 17:51:33 alon1 acpid: executing action /etc/acpi/default.sh 
 button/power PWRF 0080 0001
 Oct 23 17:52:13 alon1 ntpd[8186]: synchronized to 192.115.25.179, stratum 2
 Oct 23 17:52:16 alon1 swsusp: Marking nosave pages: 0009f000 - 
 0010
 Oct 23 17:52:16 alon1 swsusp: Basic memory bitmaps created
 Oct 23 19:41:22 alon1 pppd[25041]: Hangup (SIGHUP)
 Oct 23 19:41:22 alon1 pppd[25041]: Modem hangup
 Oct 23 19:41:22 alon1 pppd[25041]: Connect time 384.5 minutes.
 Oct 23 19:41:22 alon1 pppd[25041]: Sent 512470 bytes, received 1546102 bytes.
 Oct 23 19:41:22 alon1 pppd[25041]: Connection terminated.
 Oct 23 19:41:40 alon1 Stopping tasks ... done.
 Oct 23 19:41:40 alon1 Shrinking memory...   - \ | / - \ | / - \ | / - \ | / - 
 \ | / - \ | / - \ | / - \ | / - \ | / - \ | done (224831 pages freed)
 Oct 23 19:41:40 alon1 Freed 899324 kbytes in 14.70 seconds (61.17 MB/s)
 Oct 23 19:41:40 alon1 Suspending console(s)
 Oct 23 19:41:40 alon1 usbfs 2-2:1.0: no suspend for driver usbfs?
 Oct 23 19:41:40 alon1 pnp: Device 00:0c disabled.
 Oct 23 19:41:40 alon1 eth0: Going into suspend...
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :02:02.0 disabled
 Oct 23 19:41:40 alon1 ACPI handle has no context!
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :02:01.0 disabled
 Oct 23 19:41:40 alon1 ACPI handle has no context!
 Oct 23 19:41:40 alon1 radeonfb (:01:00.0): suspending for event: 1...
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1f.5 disabled
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.7 disabled
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.2 disabled
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.1 disabled
 Oct 23 19:41:40 alon1 ACPI: PCI interrupt for device :00:1d.0 disabled
 Oct 23 19:41:40 alon1 swsusp: critical section:
 Oct 23 19:41:40 alon1 swsusp: Need to copy 126188 pages
 Oct 23 19:41:40 alon1 Intel machine check architecture supported.
 Oct 23 19:41:40 alon1 Intel machine check reporting enabled on CPU#0.
 Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.0[A] - Link [LNKA] - 
 GSI 11 (level, low) - IRQ 11
 Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.0 to 64
 Oct 23 19:41:40 alon1 usb usb1: root hub lost power or was reset
 Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.1[B] - Link [LNKD] - 
 GSI 11 (level, low) - IRQ 11
 Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.1 to 64
 Oct 23 19:41:40 alon1 usb usb2: root hub lost power or was reset
 Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.2[C] - Link [LNKC] - 
 GSI 11 (level, low) - IRQ 11
 Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.2 to 64
 Oct 23 19:41:40 alon1 usb usb3: root hub lost power or was reset
 Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1d.7[D] - Link [LNKH] - 
 GSI 11 (level, low) - IRQ 11
 Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1d.7 to 64
 Oct 23 19:41:40 alon1 usb usb4: root hub lost power or was reset
 Oct 23 19:41:40 alon1 ehci_hcd :00:1d.7: debug port 1
 Oct 23 19:41:40 alon1 PCI: cache line size of 32 is not supported by device 
 :00:1d.7
 Oct 23 19:41:40 alon1 PCI: Setting latency timer of device :00:1e.0 to 64
 Oct 23 19:41:40 alon1 ACPI: PCI Interrupt :00:1f.1[A] - Link [LNKC] - 
 GSI 11 (level, low) - IRQ 11
 Oct 23 19:41:42 alon1 PM: Writing back config space on device :00:1f.5 at 
 offset 1 (was 297, writing 293)
 Oct 23 19:41:42 alon1 ACPI: PCI Interrupt :00:1f.5[B] - Link [LNKB] - 
 GSI 11 (level, low) - IRQ 11
 Oct 23 19:41:42 alon1 PCI: Setting latency timer of device :00:1f.5 to 64
 Oct 23 19:41:42 alon1 radeonfb (:01:00.0): resuming from state: 1...
 Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.0 at 
 offset f (was 3c0010b, writing 5c0010b)
 Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.0 at 
 offset 3 (was 824008, writing 82a810)
 Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.0 at 
 offset 1 (was 2100107, writing 217)
 Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.1 at 
 offset f (was 3c0020b, writing 5c0020b)
 Oct 23 19:41:42 alon1 PM: Writing back config space on device :02:00.1 at 
 offset 3 (was 824008, writing 82a810)
 Oct 23 19:41:42 alon1 PM: Writing back config