Re: OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-11 Thread Pavel Machek
Hi!

> today I experienced OOPS when connected via BT/GPRS to the internet, then 
> swsup and resumed with dongle in HID proxy mode. Please see details in dmesg 
> log:

I have had similar problems --but never quite repeatable. I believe I
even have patch somewhere, but I was not able to properly test it.

Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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: OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-11 Thread Pavel Machek
Hi!

 today I experienced OOPS when connected via BT/GPRS to the internet, then 
 swsup and resumed with dongle in HID proxy mode. Please see details in dmesg 
 log:

I have had similar problems --but never quite repeatable. I believe I
even have patch somewhere, but I was not able to properly test it.

Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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-users] OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-07 Thread CIJOML
Hi Stefan,

thanks for verification on not tainted kernel. I made same test with same 
error with/without tainted kernel too.

Michal

Dne pondělí 07 květen 2007 09:40 Stefan Seyfried napsal(a):
> On Mon, May 07, 2007 at 12:05:33AM +0200, CIJOML wrote:
> > Hi all,
> >
> > today I experienced OOPS when connected via BT/GPRS to the internet, then
> > swsup and resumed with dongle in HID proxy mode. Please see details in
> > dmesg log:
>
> I got two similar looking oopsen when my mobile phone crashed and thus
> went away while i was connected via BT/3G.
> The second oops happend when trying to reconnect.
>
>  BUG: unable to handle kernel NULL pointer dereference at virtual address
> 000c printing eip:
> c01a0dce
> *pde = 
> Oops:  [#1]
> SMP
> last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
> Modules linked in: xfrm_user xfrm4_tunnel af_key ppp_deflate bsd_comp
> ppp_async crc_ccitt rfcomm hidp l2cap hci_usb button r8169 pcmcia
> firmware_class yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd
> kqemu nfs lockd nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat usb_storage
> xfrm4_mode_tunnel deflate zlib_deflate camellia serpent blowfish xcbc
> crypto_null tunnel4 ipcomp esp4 ah4 aes des md5 sha1 sha256 autofs4
> michael_mic arc4 ecb ieee80211_crypt_tkip bluetooth i915 drm ppp_generic
> slhc af_packet ipv6 snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device
> cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave
> acpi_cpufreq speedstep_lib freq_table bay dock pcc_acpi battery ac apparmor
> cbc blkcipher twofish twofish_common usbhid hid ff_memless ohci_hcd
> dm_crypt ext2 loop dm_mod fuse generic rtc_cmos piix ieee80211
> ieee80211_crypt rtc_core rtc_lib ide_core ohci1394 ieee1394 snd_intel8x0
> snd_ac97_codec ac97_bus snd_pcm snd_timer snd soundcore iTCO_wdt iTCO_v
> endor_support snd_page_alloc i2c_i801 i2c_core usbcore joydev shpchp
> pci_hotplug intel_agp agpgart parport_pc lp parport ext3 mbcache jbd sr_mod
> cdrom sg edd fan ata_piix libata thermal processor sd_mod scsi_mod CPU:   
> 0
> EIP:0060:[]Tainted: G  N VLI
> EFLAGS: 00010282   (2.6.21-2-default #1)
> EIP is at sysfs_move_dir+0x3e/0x117
> eax:    ebx: f1e3db40   ecx: c6573e74   edx: dff9b840
> esi: dfc01cf0   edi:    ebp: dff9b840   esp: c6573e48
> ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
> Process pppd (pid: 30673, ti=c6572000 task=dfe3da90 task.ti=c6572000)
> Stack: c0300758 e54ff878  fff4 f1e3db40 e54ff878 fff4
> dff9b840 c01c4481 dff353c0 c030074a f1e3db40 dff353c0 dff353c0 
>  e54ff800  dff9b840 c02291a7 e54ff878 f1e3ddc0 f3caa800
>  Call Trace:
>  [] kobject_move+0xad/0xf8
>  [] device_move+0x49/0xd7
>  [] rfcomm_tty_close+0x23/0x76 [rfcomm]
>  [] release_dev+0x1df/0x5d4
>  [] do_notify_resume+0x4e3/0x5da
>  [] tty_release+0xf/0x18
>  [] __fput+0xac/0x162
>  [] filp_close+0x51/0x58
>  [] sys_close+0x6e/0xa5
>  [] sysenter_past_esp+0x5d/0x89
>  ===
> Code: 40 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 40 38 85 d2 89 44 24 08 74 05
> 8b 72 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 70 38 8b 7c 24 08 <8b> 47 0c 31
> ff 3b 46 0c 0f 84 c1 00 00 00 8b 54 24 08 8b 42 0c EIP: []
> sysfs_move_dir+0x3e/0x117 SS:ESP 0068:c6573e48
> NET: Unregistered protocol family 15
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 000c printing eip:
> c01a0dce
> *pde = 
> Oops:  [#2]
> SMP
> last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
> Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt rfcomm hidp
> l2cap hci_usb button r8169 pcmcia firmware_class yenta_socket
> rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd kqemu nfs lockd nfs_acl sunrpc
> nls_iso8859_1 nls_cp437 vfat fat usb_storage xfrm4_mode_tunnel deflate
> zlib_deflate camellia serpent blowfish xcbc crypto_null tunnel4 ipcomp esp4
> ah4 aes des md5 sha1 sha256 autofs4 michael_mic arc4 ecb
> ieee80211_crypt_tkip bluetooth i915 drm ppp_generic slhc af_packet ipv6
> snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative
> cpufreq_ondemand cpufreq_userspace cpufreq_powersave acpi_cpufreq
> speedstep_lib freq_table bay dock pcc_acpi battery ac apparmor cbc
> blkcipher twofish twofish_common usbhid hid ff_memless ohci_hcd dm_crypt
> ext2 loop dm_mod fuse generic rtc_cmos piix ieee80211 ieee80211_crypt
> rtc_core rtc_lib ide_core ohci1394 ieee1394 snd_intel8x0 snd_ac97_codec
> ac97_bus snd_pcm snd_timer snd soundcore iTCO_wdt iTCO_vendor_support
> snd_page_alloc i 2c_i801 i2c_core usbcore joydev shpchp pci_hotplug
> intel_agp agpgart parport_pc lp parport ext3 mbcache jbd sr_mod cdrom sg
> edd fan ata_piix libata thermal processor sd_mod scsi_mod CPU:0
> EIP:0060:[]Tainted: G  N VLI
> EFLAGS: 00010282   (2.6.21-2-default #1)
> EIP is at sysfs_move_dir+0x3e/0x117
> eax:    ebx: dfcda3c0   ecx: dde11e4c   edx: d05cc508
> esi: d338f7c8   edi:    ebp: 

Re: [Bluez-users] OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-07 Thread Stefan Seyfried
On Mon, May 07, 2007 at 12:05:33AM +0200, CIJOML wrote:
> Hi all,
> 
> today I experienced OOPS when connected via BT/GPRS to the internet, then 
> swsup and resumed with dongle in HID proxy mode. Please see details in dmesg 
> log:

I got two similar looking oopsen when my mobile phone crashed and thus
went away while i was connected via BT/3G.
The second oops happend when trying to reconnect.

 BUG: unable to handle kernel NULL pointer dereference at virtual address 
000c
 printing eip:
c01a0dce
*pde = 
Oops:  [#1]
SMP 
last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Modules linked in: xfrm_user xfrm4_tunnel af_key ppp_deflate bsd_comp ppp_async 
crc_ccitt rfcomm hidp l2cap hci_usb button r8169 pcmcia firmware_class 
yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd kqemu nfs lockd 
nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat usb_storage xfrm4_mode_tunnel 
deflate zlib_deflate camellia serpent blowfish xcbc crypto_null tunnel4 ipcomp 
esp4 ah4 aes des md5 sha1 sha256 autofs4 michael_mic arc4 ecb 
ieee80211_crypt_tkip bluetooth i915 drm ppp_generic slhc af_packet ipv6 
snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative 
cpufreq_ondemand cpufreq_userspace cpufreq_powersave acpi_cpufreq speedstep_lib 
freq_table bay dock pcc_acpi battery ac apparmor cbc blkcipher twofish 
twofish_common usbhid hid ff_memless ohci_hcd dm_crypt ext2 loop dm_mod fuse 
generic rtc_cmos piix ieee80211 ieee80211_crypt rtc_core rtc_lib ide_core 
ohci1394 ieee1394 snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer snd 
soundcore iTCO_wdt iTCO_vendor_support snd_page_alloc i2c_i801 i2c_core usbcore 
joydev shpchp pci_hotplug intel_agp agpgart parport_pc lp parport ext3 mbcache 
jbd sr_mod cdrom sg edd fan ata_piix libata thermal processor sd_mod scsi_mod
CPU:0
EIP:0060:[]Tainted: G  N VLI
EFLAGS: 00010282   (2.6.21-2-default #1)
EIP is at sysfs_move_dir+0x3e/0x117
eax:    ebx: f1e3db40   ecx: c6573e74   edx: dff9b840
esi: dfc01cf0   edi:    ebp: dff9b840   esp: c6573e48
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process pppd (pid: 30673, ti=c6572000 task=dfe3da90 task.ti=c6572000)
Stack: c0300758 e54ff878  fff4 f1e3db40 e54ff878 fff4 dff9b840 
   c01c4481 dff353c0 c030074a f1e3db40 dff353c0 dff353c0   
   e54ff800  dff9b840 c02291a7 e54ff878 f1e3ddc0 f3caa800  
Call Trace:
 [] kobject_move+0xad/0xf8
 [] device_move+0x49/0xd7
 [] rfcomm_tty_close+0x23/0x76 [rfcomm]
 [] release_dev+0x1df/0x5d4
 [] do_notify_resume+0x4e3/0x5da
 [] tty_release+0xf/0x18
 [] __fput+0xac/0x162
 [] filp_close+0x51/0x58
 [] sys_close+0x6e/0xa5
 [] sysenter_past_esp+0x5d/0x89
 ===
Code: 40 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 40 38 85 d2 89 44 24 08 74 05 8b 
72 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 70 38 8b 7c 24 08 <8b> 47 0c 31 ff 3b 46 
0c 0f 84 c1 00 00 00 8b 54 24 08 8b 42 0c 
EIP: [] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:c6573e48
NET: Unregistered protocol family 15
BUG: unable to handle kernel NULL pointer dereference at virtual address 
000c
 printing eip:
c01a0dce
*pde = 
Oops:  [#2]
SMP 
last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt rfcomm hidp l2cap 
hci_usb button r8169 pcmcia firmware_class yenta_socket rsrc_nonstatic 
pcmcia_core uhci_hcd ehci_hcd kqemu nfs lockd nfs_acl sunrpc nls_iso8859_1 
nls_cp437 vfat fat usb_storage xfrm4_mode_tunnel deflate zlib_deflate camellia 
serpent blowfish xcbc crypto_null tunnel4 ipcomp esp4 ah4 aes des md5 sha1 
sha256 autofs4 michael_mic arc4 ecb ieee80211_crypt_tkip bluetooth i915 drm 
ppp_generic slhc af_packet ipv6 snd_pcm_oss snd_mixer_oss snd_seq 
snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace 
cpufreq_powersave acpi_cpufreq speedstep_lib freq_table bay dock pcc_acpi 
battery ac apparmor cbc blkcipher twofish twofish_common usbhid hid ff_memless 
ohci_hcd dm_crypt ext2 loop dm_mod fuse generic rtc_cmos piix ieee80211 
ieee80211_crypt rtc_core rtc_lib ide_core ohci1394 ieee1394 snd_intel8x0 
snd_ac97_codec ac97_bus snd_pcm snd_timer snd soundcore iTCO_wdt 
iTCO_vendor_support snd_page_alloc i2c_i801 i2c_core usbcore joydev shpchp 
pci_hotplug intel_agp agpgart parport_pc lp parport ext3 mbcache jbd sr_mod 
cdrom sg edd fan ata_piix libata thermal processor sd_mod scsi_mod
CPU:0
EIP:0060:[]Tainted: G  N VLI
EFLAGS: 00010282   (2.6.21-2-default #1)
EIP is at sysfs_move_dir+0x3e/0x117
eax:    ebx: dfcda3c0   ecx: dde11e4c   edx: d05cc508
esi: d338f7c8   edi:    ebp: d05cc508   esp: dde11e20
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process pppd (pid: 32701, ti=dde1 task=f7be9a90 task.ti=dde1)
Stack: c0300758 e54ff878  fff4 dfcda3c0 e54ff878 fff4 d05cc508 
   c01c4481 dff35240 c030074a dfcda3c0 dff35240 dff35240  d05cc490 
   

Re: [Bluez-users] OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-07 Thread CIJOML
Hi Stefan,

thanks for verification on not tainted kernel. I made same test with same 
error with/without tainted kernel too.

Michal

Dne pondělí 07 květen 2007 09:40 Stefan Seyfried napsal(a):
 On Mon, May 07, 2007 at 12:05:33AM +0200, CIJOML wrote:
  Hi all,
 
  today I experienced OOPS when connected via BT/GPRS to the internet, then
  swsup and resumed with dongle in HID proxy mode. Please see details in
  dmesg log:

 I got two similar looking oopsen when my mobile phone crashed and thus
 went away while i was connected via BT/3G.
 The second oops happend when trying to reconnect.

  BUG: unable to handle kernel NULL pointer dereference at virtual address
 000c printing eip:
 c01a0dce
 *pde = 
 Oops:  [#1]
 SMP
 last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
 Modules linked in: xfrm_user xfrm4_tunnel af_key ppp_deflate bsd_comp
 ppp_async crc_ccitt rfcomm hidp l2cap hci_usb button r8169 pcmcia
 firmware_class yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd
 kqemu nfs lockd nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat usb_storage
 xfrm4_mode_tunnel deflate zlib_deflate camellia serpent blowfish xcbc
 crypto_null tunnel4 ipcomp esp4 ah4 aes des md5 sha1 sha256 autofs4
 michael_mic arc4 ecb ieee80211_crypt_tkip bluetooth i915 drm ppp_generic
 slhc af_packet ipv6 snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device
 cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave
 acpi_cpufreq speedstep_lib freq_table bay dock pcc_acpi battery ac apparmor
 cbc blkcipher twofish twofish_common usbhid hid ff_memless ohci_hcd
 dm_crypt ext2 loop dm_mod fuse generic rtc_cmos piix ieee80211
 ieee80211_crypt rtc_core rtc_lib ide_core ohci1394 ieee1394 snd_intel8x0
 snd_ac97_codec ac97_bus snd_pcm snd_timer snd soundcore iTCO_wdt iTCO_v
 endor_support snd_page_alloc i2c_i801 i2c_core usbcore joydev shpchp
 pci_hotplug intel_agp agpgart parport_pc lp parport ext3 mbcache jbd sr_mod
 cdrom sg edd fan ata_piix libata thermal processor sd_mod scsi_mod CPU:   
 0
 EIP:0060:[c01a0dce]Tainted: G  N VLI
 EFLAGS: 00010282   (2.6.21-2-default #1)
 EIP is at sysfs_move_dir+0x3e/0x117
 eax:    ebx: f1e3db40   ecx: c6573e74   edx: dff9b840
 esi: dfc01cf0   edi:    ebp: dff9b840   esp: c6573e48
 ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
 Process pppd (pid: 30673, ti=c6572000 task=dfe3da90 task.ti=c6572000)
 Stack: c0300758 e54ff878  fff4 f1e3db40 e54ff878 fff4
 dff9b840 c01c4481 dff353c0 c030074a f1e3db40 dff353c0 dff353c0 
  e54ff800  dff9b840 c02291a7 e54ff878 f1e3ddc0 f3caa800
  Call Trace:
  [c01c4481] kobject_move+0xad/0xf8
  [c02291a7] device_move+0x49/0xd7
  [f930048e] rfcomm_tty_close+0x23/0x76 [rfcomm]
  [c021202d] release_dev+0x1df/0x5d4
  [c01048fb] do_notify_resume+0x4e3/0x5da
  [c0212431] tty_release+0xf/0x18
  [c01695ef] __fput+0xac/0x162
  [c016718d] filp_close+0x51/0x58
  [c0168136] sys_close+0x6e/0xa5
  [c0104d14] sysenter_past_esp+0x5d/0x89
  ===
 Code: 40 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 40 38 85 d2 89 44 24 08 74 05
 8b 72 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 70 38 8b 7c 24 08 8b 47 0c 31
 ff 3b 46 0c 0f 84 c1 00 00 00 8b 54 24 08 8b 42 0c EIP: [c01a0dce]
 sysfs_move_dir+0x3e/0x117 SS:ESP 0068:c6573e48
 NET: Unregistered protocol family 15
 BUG: unable to handle kernel NULL pointer dereference at virtual address
 000c printing eip:
 c01a0dce
 *pde = 
 Oops:  [#2]
 SMP
 last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
 Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt rfcomm hidp
 l2cap hci_usb button r8169 pcmcia firmware_class yenta_socket
 rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd kqemu nfs lockd nfs_acl sunrpc
 nls_iso8859_1 nls_cp437 vfat fat usb_storage xfrm4_mode_tunnel deflate
 zlib_deflate camellia serpent blowfish xcbc crypto_null tunnel4 ipcomp esp4
 ah4 aes des md5 sha1 sha256 autofs4 michael_mic arc4 ecb
 ieee80211_crypt_tkip bluetooth i915 drm ppp_generic slhc af_packet ipv6
 snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative
 cpufreq_ondemand cpufreq_userspace cpufreq_powersave acpi_cpufreq
 speedstep_lib freq_table bay dock pcc_acpi battery ac apparmor cbc
 blkcipher twofish twofish_common usbhid hid ff_memless ohci_hcd dm_crypt
 ext2 loop dm_mod fuse generic rtc_cmos piix ieee80211 ieee80211_crypt
 rtc_core rtc_lib ide_core ohci1394 ieee1394 snd_intel8x0 snd_ac97_codec
 ac97_bus snd_pcm snd_timer snd soundcore iTCO_wdt iTCO_vendor_support
 snd_page_alloc i 2c_i801 i2c_core usbcore joydev shpchp pci_hotplug
 intel_agp agpgart parport_pc lp parport ext3 mbcache jbd sr_mod cdrom sg
 edd fan ata_piix libata thermal processor sd_mod scsi_mod CPU:0
 EIP:0060:[c01a0dce]Tainted: G  N VLI
 EFLAGS: 00010282   (2.6.21-2-default #1)
 EIP is at sysfs_move_dir+0x3e/0x117
 eax:    ebx: dfcda3c0   ecx: dde11e4c   edx: d05cc508
 esi: d338f7c8   edi:    

Re: [Bluez-users] OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-07 Thread Stefan Seyfried
On Mon, May 07, 2007 at 12:05:33AM +0200, CIJOML wrote:
 Hi all,
 
 today I experienced OOPS when connected via BT/GPRS to the internet, then 
 swsup and resumed with dongle in HID proxy mode. Please see details in dmesg 
 log:

I got two similar looking oopsen when my mobile phone crashed and thus
went away while i was connected via BT/3G.
The second oops happend when trying to reconnect.

 BUG: unable to handle kernel NULL pointer dereference at virtual address 
000c
 printing eip:
c01a0dce
*pde = 
Oops:  [#1]
SMP 
last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Modules linked in: xfrm_user xfrm4_tunnel af_key ppp_deflate bsd_comp ppp_async 
crc_ccitt rfcomm hidp l2cap hci_usb button r8169 pcmcia firmware_class 
yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd kqemu nfs lockd 
nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat usb_storage xfrm4_mode_tunnel 
deflate zlib_deflate camellia serpent blowfish xcbc crypto_null tunnel4 ipcomp 
esp4 ah4 aes des md5 sha1 sha256 autofs4 michael_mic arc4 ecb 
ieee80211_crypt_tkip bluetooth i915 drm ppp_generic slhc af_packet ipv6 
snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative 
cpufreq_ondemand cpufreq_userspace cpufreq_powersave acpi_cpufreq speedstep_lib 
freq_table bay dock pcc_acpi battery ac apparmor cbc blkcipher twofish 
twofish_common usbhid hid ff_memless ohci_hcd dm_crypt ext2 loop dm_mod fuse 
generic rtc_cmos piix ieee80211 ieee80211_crypt rtc_core rtc_lib ide_core 
ohci1394 ieee1394 snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer snd 
soundcore iTCO_wdt iTCO_vendor_support snd_page_alloc i2c_i801 i2c_core usbcore 
joydev shpchp pci_hotplug intel_agp agpgart parport_pc lp parport ext3 mbcache 
jbd sr_mod cdrom sg edd fan ata_piix libata thermal processor sd_mod scsi_mod
CPU:0
EIP:0060:[c01a0dce]Tainted: G  N VLI
EFLAGS: 00010282   (2.6.21-2-default #1)
EIP is at sysfs_move_dir+0x3e/0x117
eax:    ebx: f1e3db40   ecx: c6573e74   edx: dff9b840
esi: dfc01cf0   edi:    ebp: dff9b840   esp: c6573e48
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process pppd (pid: 30673, ti=c6572000 task=dfe3da90 task.ti=c6572000)
Stack: c0300758 e54ff878  fff4 f1e3db40 e54ff878 fff4 dff9b840 
   c01c4481 dff353c0 c030074a f1e3db40 dff353c0 dff353c0   
   e54ff800  dff9b840 c02291a7 e54ff878 f1e3ddc0 f3caa800  
Call Trace:
 [c01c4481] kobject_move+0xad/0xf8
 [c02291a7] device_move+0x49/0xd7
 [f930048e] rfcomm_tty_close+0x23/0x76 [rfcomm]
 [c021202d] release_dev+0x1df/0x5d4
 [c01048fb] do_notify_resume+0x4e3/0x5da
 [c0212431] tty_release+0xf/0x18
 [c01695ef] __fput+0xac/0x162
 [c016718d] filp_close+0x51/0x58
 [c0168136] sys_close+0x6e/0xa5
 [c0104d14] sysenter_past_esp+0x5d/0x89
 ===
Code: 40 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 40 38 85 d2 89 44 24 08 74 05 8b 
72 30 eb 0b a1 84 27 3e c0 8b 40 14 8b 70 38 8b 7c 24 08 8b 47 0c 31 ff 3b 46 
0c 0f 84 c1 00 00 00 8b 54 24 08 8b 42 0c 
EIP: [c01a0dce] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:c6573e48
NET: Unregistered protocol family 15
BUG: unable to handle kernel NULL pointer dereference at virtual address 
000c
 printing eip:
c01a0dce
*pde = 
Oops:  [#2]
SMP 
last sysfs file: devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt rfcomm hidp l2cap 
hci_usb button r8169 pcmcia firmware_class yenta_socket rsrc_nonstatic 
pcmcia_core uhci_hcd ehci_hcd kqemu nfs lockd nfs_acl sunrpc nls_iso8859_1 
nls_cp437 vfat fat usb_storage xfrm4_mode_tunnel deflate zlib_deflate camellia 
serpent blowfish xcbc crypto_null tunnel4 ipcomp esp4 ah4 aes des md5 sha1 
sha256 autofs4 michael_mic arc4 ecb ieee80211_crypt_tkip bluetooth i915 drm 
ppp_generic slhc af_packet ipv6 snd_pcm_oss snd_mixer_oss snd_seq 
snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace 
cpufreq_powersave acpi_cpufreq speedstep_lib freq_table bay dock pcc_acpi 
battery ac apparmor cbc blkcipher twofish twofish_common usbhid hid ff_memless 
ohci_hcd dm_crypt ext2 loop dm_mod fuse generic rtc_cmos piix ieee80211 
ieee80211_crypt rtc_core rtc_lib ide_core ohci1394 ieee1394 snd_intel8x0 
snd_ac97_codec ac97_bus snd_pcm snd_timer snd soundcore iTCO_wdt 
iTCO_vendor_support snd_page_alloc i2c_i801 i2c_core usbcore joydev shpchp 
pci_hotplug intel_agp agpgart parport_pc lp parport ext3 mbcache jbd sr_mod 
cdrom sg edd fan ata_piix libata thermal processor sd_mod scsi_mod
CPU:0
EIP:0060:[c01a0dce]Tainted: G  N VLI
EFLAGS: 00010282   (2.6.21-2-default #1)
EIP is at sysfs_move_dir+0x3e/0x117
eax:    ebx: dfcda3c0   ecx: dde11e4c   edx: d05cc508
esi: d338f7c8   edi:    ebp: d05cc508   esp: dde11e20
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process pppd (pid: 32701, ti=dde1 task=f7be9a90 task.ti=dde1)
Stack: c0300758 e54ff878  fff4 dfcda3c0 e54ff878 fff4 

Re: OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-06 Thread Adrian Bunk
On Mon, May 07, 2007 at 07:04:29AM +0200, CIJOML wrote:
> Hi Michal,
> 
> my kernel is tainted with madwifi opensource driver :). Only binary part is 
> ath_hal module, which doesn't have anythink to do with this part of kernel.

Any module can change any part of the kernel, e.g. a part of the code 
executed when loading the ath_hal module could accidentally corrupt a 
kernel data structure.

> Ath_hal is doing RF part of card to protect others tune/transmit in other 
> frequency than 2.5/5.8GHz (Wifi 802.11a/b/g).
> 
> My kernel is 100% opensource :)

That's wrong, the binary-only blob from ath_hal loaded into your kernel 
is not opensource.

> And BTW this happens also with madwifi kernel modules unloaded.

An Oops without any external module ever loaded since booting is 
strongly preferred.

> Best regards
> 
> Michal

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-
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: OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-06 Thread CIJOML
Hi Michal,

my kernel is tainted with madwifi opensource driver :). Only binary part is 
ath_hal module, which doesn't have anythink to do with this part of kernel.
Ath_hal is doing RF part of card to protect others tune/transmit in other 
frequency than 2.5/5.8GHz (Wifi 802.11a/b/g).

My kernel is 100% opensource :)

And BTW this happens also with madwifi kernel modules unloaded.

Best regards

Michal


Dne pondělí 07 květen 2007 00:34 jste napsal(a):
> Hi Michal,
>
> On 07/05/07, CIJOML <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > today I experienced OOPS when connected via BT/GPRS to the internet, then
> > swsup and resumed with dongle in HID proxy mode. Please see details in
> > dmesg log:
> >
> > Restarting tasks ... <6>usb 3-1: USB disconnect, address 3
> > done.
> > BUG: unable to handle kernel NULL pointer dereference at virtual address
> > 0008
> >  printing eip:
> > c018db5d
> > *pde = 
> > Oops:  [#1]
> > PREEMPT
> > Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async
> > ppp_generic slhc usbhid nls_iso8859_1 nls_cp437 vfat fat sg
> > sr_mod sd_mod usb_storage bnep rfcomm hidp l2cap lp fuse eeprom hci_usb
> > bluetooth 8250_pci 8250 serial_core snd_intel8x0 sn
> > d_intel8x0m snd_ac97_codec wlan_scan_sta ac97_bus ath_rate_sample
> > nsc_ircc snd_pcm ide_cd ath_pci wlan ath_hal(P) 8139too m
> > ii snd_timer snd irda ehci_hcd psmouse pcspkr i2c_i801 iTCO_wdt
> > iTCO_vendor_support rtc cdrom parport_pc parport snd_page_a
> > lloc uhci_hcd crc_ccitt
> > CPU:0
> > EIP:0060:[]Tainted: P   VLI
>
> You are using tainted kernel.
>
> "When you are using a binary driver, the kernel is "tainted",
> which means that the source
> of possible problems may be unrelated to the kernel code (see
> https://secure-support.
> novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html for more
> de- tails). You can check whether or not the kernel was tainted when the
> problem occured by
> looking at the corresponding error message. If can you see something
> similar to the following
> line:
> EIP:  0060:[] Tainted: P  VLI
> (the word Tainted is crucial here), the kernel was tainted and most
> probably the kernel
> developers will not be able to help you. In that case you should try
> to reproduce the problem
> without the binary driver loaded. Moreover, if the problem does not
> occur without it, you
> should send a bug report to the creators of the binary driver and ask
> them to fix it."
>
> -- Linux Kernel Tester's Guide
>
> > EFLAGS: 00010282   (2.6.21 #3)
> > EIP is at sysfs_move_dir+0x3e/0x117
> > eax:    ebx: efd7df40   ecx: f79a1e7c   edx: c1b88940
> > esi: c1b91e28   edi:    ebp: c1b88940   esp: f79a1e50
> > ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
> > Process pppd (pid: 6550, ti=f79a task=f29d6ab0 task.ti=f79a)
> > Stack: c03475a4 f7f86e68  fff4 efd7df40 f7f86e68 fff4
> > c1b88940 c01d27ec f12a5240 c0347596 efd7df40 f12a5240 f12a5240 
> >  f7f86e00  c1b88940 c023c984 f7f86e68 f7f36640 ef67b000
> >  Call Trace:
> >  [] kobject_move+0xaf/0xfa
> >  [] device_move+0x49/0xd7
> >  [] rfcomm_tty_close+0x23/0x7a [rfcomm]
> >  [] release_dev+0x1df/0x5e7
> >  [] inode_has_perm+0x66/0x6e
> >  [] __posix_lock_file_conf+0x44e/0x48b
> >  [] file_has_perm+0x89/0x91
> >  [] tty_release+0xf/0x18
> >  [] __fput+0x96/0x15e
> >  [] filp_close+0x51/0x58
> >  [] sys_close+0x75/0xbf
> >  [] syscall_call+0x7/0xb
> >  ===
> > Code: 40 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 40 38 89 44 24 08 85 d2 74
> > 05 8b 72 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 70 38
> > 8b 7c 24 08 <8b> 47 08 31 ff 3b 46 08 0f 84 c1 00 00 00 8b 54 24 08 8b 42
> > 08 EIP: [] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:f79a1e50
> >
> > Thanks for fixing this issue
> >
> > Michal
>
> Regards,
> Michal
-
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/


OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-06 Thread CIJOML
Hi all,

today I experienced OOPS when connected via BT/GPRS to the internet, then 
swsup and resumed with dongle in HID proxy mode. Please see details in dmesg 
log:

Restarting tasks ... <6>usb 3-1: USB disconnect, address 3
done.
BUG: unable to handle kernel NULL pointer dereference at virtual address 
0008
 printing eip:
c018db5d
*pde = 
Oops:  [#1]
PREEMPT
Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async ppp_generic 
slhc usbhid nls_iso8859_1 nls_cp437 vfat fat sg
sr_mod sd_mod usb_storage bnep rfcomm hidp l2cap lp fuse eeprom hci_usb 
bluetooth 8250_pci 8250 serial_core snd_intel8x0 sn
d_intel8x0m snd_ac97_codec wlan_scan_sta ac97_bus ath_rate_sample nsc_ircc 
snd_pcm ide_cd ath_pci wlan ath_hal(P) 8139too m
ii snd_timer snd irda ehci_hcd psmouse pcspkr i2c_i801 iTCO_wdt 
iTCO_vendor_support rtc cdrom parport_pc parport snd_page_a
lloc uhci_hcd crc_ccitt
CPU:0
EIP:0060:[]Tainted: P   VLI
EFLAGS: 00010282   (2.6.21 #3)
EIP is at sysfs_move_dir+0x3e/0x117
eax:    ebx: efd7df40   ecx: f79a1e7c   edx: c1b88940
esi: c1b91e28   edi:    ebp: c1b88940   esp: f79a1e50
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process pppd (pid: 6550, ti=f79a task=f29d6ab0 task.ti=f79a)
Stack: c03475a4 f7f86e68  fff4 efd7df40 f7f86e68 fff4 c1b88940
   c01d27ec f12a5240 c0347596 efd7df40 f12a5240 f12a5240  
   f7f86e00  c1b88940 c023c984 f7f86e68 f7f36640 ef67b000 
Call Trace:
 [] kobject_move+0xaf/0xfa
 [] device_move+0x49/0xd7
 [] rfcomm_tty_close+0x23/0x7a [rfcomm]
 [] release_dev+0x1df/0x5e7
 [] inode_has_perm+0x66/0x6e
 [] __posix_lock_file_conf+0x44e/0x48b
 [] file_has_perm+0x89/0x91
 [] tty_release+0xf/0x18
 [] __fput+0x96/0x15e
 [] filp_close+0x51/0x58
 [] sys_close+0x75/0xbf
 [] syscall_call+0x7/0xb
 ===
Code: 40 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 40 38 89 44 24 08 85 d2 74 05 8b 
72 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 70 38
8b 7c 24 08 <8b> 47 08 31 ff 3b 46 08 0f 84 c1 00 00 00 8b 54 24 08 8b 42 08
EIP: [] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:f79a1e50

Thanks for fixing this issue

Michal
-
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/


OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-06 Thread CIJOML
Hi all,

today I experienced OOPS when connected via BT/GPRS to the internet, then 
swsup and resumed with dongle in HID proxy mode. Please see details in dmesg 
log:

Restarting tasks ... 6usb 3-1: USB disconnect, address 3
done.
BUG: unable to handle kernel NULL pointer dereference at virtual address 
0008
 printing eip:
c018db5d
*pde = 
Oops:  [#1]
PREEMPT
Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async ppp_generic 
slhc usbhid nls_iso8859_1 nls_cp437 vfat fat sg
sr_mod sd_mod usb_storage bnep rfcomm hidp l2cap lp fuse eeprom hci_usb 
bluetooth 8250_pci 8250 serial_core snd_intel8x0 sn
d_intel8x0m snd_ac97_codec wlan_scan_sta ac97_bus ath_rate_sample nsc_ircc 
snd_pcm ide_cd ath_pci wlan ath_hal(P) 8139too m
ii snd_timer snd irda ehci_hcd psmouse pcspkr i2c_i801 iTCO_wdt 
iTCO_vendor_support rtc cdrom parport_pc parport snd_page_a
lloc uhci_hcd crc_ccitt
CPU:0
EIP:0060:[c018db5d]Tainted: P   VLI
EFLAGS: 00010282   (2.6.21 #3)
EIP is at sysfs_move_dir+0x3e/0x117
eax:    ebx: efd7df40   ecx: f79a1e7c   edx: c1b88940
esi: c1b91e28   edi:    ebp: c1b88940   esp: f79a1e50
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process pppd (pid: 6550, ti=f79a task=f29d6ab0 task.ti=f79a)
Stack: c03475a4 f7f86e68  fff4 efd7df40 f7f86e68 fff4 c1b88940
   c01d27ec f12a5240 c0347596 efd7df40 f12a5240 f12a5240  
   f7f86e00  c1b88940 c023c984 f7f86e68 f7f36640 ef67b000 
Call Trace:
 [c01d27ec] kobject_move+0xaf/0xfa
 [c023c984] device_move+0x49/0xd7
 [fcb54bb3] rfcomm_tty_close+0x23/0x7a [rfcomm]
 [c021957a] release_dev+0x1df/0x5e7
 [c01b8eb9] inode_has_perm+0x66/0x6e
 [c0166469] __posix_lock_file_conf+0x44e/0x48b
 [c01b8f4a] file_has_perm+0x89/0x91
 [c0219991] tty_release+0xf/0x18
 [c015a3c7] __fput+0x96/0x15e
 [c0157fba] filp_close+0x51/0x58
 [c0158f65] sys_close+0x75/0xbf
 [c0103cd8] syscall_call+0x7/0xb
 ===
Code: 40 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 40 38 89 44 24 08 85 d2 74 05 8b 
72 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 70 38
8b 7c 24 08 8b 47 08 31 ff 3b 46 08 0f 84 c1 00 00 00 8b 54 24 08 8b 42 08
EIP: [c018db5d] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:f79a1e50

Thanks for fixing this issue

Michal
-
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: OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-06 Thread CIJOML
Hi Michal,

my kernel is tainted with madwifi opensource driver :). Only binary part is 
ath_hal module, which doesn't have anythink to do with this part of kernel.
Ath_hal is doing RF part of card to protect others tune/transmit in other 
frequency than 2.5/5.8GHz (Wifi 802.11a/b/g).

My kernel is 100% opensource :)

And BTW this happens also with madwifi kernel modules unloaded.

Best regards

Michal


Dne pondělí 07 květen 2007 00:34 jste napsal(a):
 Hi Michal,

 On 07/05/07, CIJOML [EMAIL PROTECTED] wrote:
  Hi all,
 
  today I experienced OOPS when connected via BT/GPRS to the internet, then
  swsup and resumed with dongle in HID proxy mode. Please see details in
  dmesg log:
 
  Restarting tasks ... 6usb 3-1: USB disconnect, address 3
  done.
  BUG: unable to handle kernel NULL pointer dereference at virtual address
  0008
   printing eip:
  c018db5d
  *pde = 
  Oops:  [#1]
  PREEMPT
  Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async
  ppp_generic slhc usbhid nls_iso8859_1 nls_cp437 vfat fat sg
  sr_mod sd_mod usb_storage bnep rfcomm hidp l2cap lp fuse eeprom hci_usb
  bluetooth 8250_pci 8250 serial_core snd_intel8x0 sn
  d_intel8x0m snd_ac97_codec wlan_scan_sta ac97_bus ath_rate_sample
  nsc_ircc snd_pcm ide_cd ath_pci wlan ath_hal(P) 8139too m
  ii snd_timer snd irda ehci_hcd psmouse pcspkr i2c_i801 iTCO_wdt
  iTCO_vendor_support rtc cdrom parport_pc parport snd_page_a
  lloc uhci_hcd crc_ccitt
  CPU:0
  EIP:0060:[c018db5d]Tainted: P   VLI

 You are using tainted kernel.

 When you are using a binary driver, the kernel is tainted,
 which means that the source
 of possible problems may be unrelated to the kernel code (see
 https://secure-support.
 novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html for more
 de- tails). You can check whether or not the kernel was tainted when the
 problem occured by
 looking at the corresponding error message. If can you see something
 similar to the following
 line:
 EIP:  0060:[c046c7c3] Tainted: P  VLI
 (the word Tainted is crucial here), the kernel was tainted and most
 probably the kernel
 developers will not be able to help you. In that case you should try
 to reproduce the problem
 without the binary driver loaded. Moreover, if the problem does not
 occur without it, you
 should send a bug report to the creators of the binary driver and ask
 them to fix it.

 -- Linux Kernel Tester's Guide

  EFLAGS: 00010282   (2.6.21 #3)
  EIP is at sysfs_move_dir+0x3e/0x117
  eax:    ebx: efd7df40   ecx: f79a1e7c   edx: c1b88940
  esi: c1b91e28   edi:    ebp: c1b88940   esp: f79a1e50
  ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
  Process pppd (pid: 6550, ti=f79a task=f29d6ab0 task.ti=f79a)
  Stack: c03475a4 f7f86e68  fff4 efd7df40 f7f86e68 fff4
  c1b88940 c01d27ec f12a5240 c0347596 efd7df40 f12a5240 f12a5240 
   f7f86e00  c1b88940 c023c984 f7f86e68 f7f36640 ef67b000
   Call Trace:
   [c01d27ec] kobject_move+0xaf/0xfa
   [c023c984] device_move+0x49/0xd7
   [fcb54bb3] rfcomm_tty_close+0x23/0x7a [rfcomm]
   [c021957a] release_dev+0x1df/0x5e7
   [c01b8eb9] inode_has_perm+0x66/0x6e
   [c0166469] __posix_lock_file_conf+0x44e/0x48b
   [c01b8f4a] file_has_perm+0x89/0x91
   [c0219991] tty_release+0xf/0x18
   [c015a3c7] __fput+0x96/0x15e
   [c0157fba] filp_close+0x51/0x58
   [c0158f65] sys_close+0x75/0xbf
   [c0103cd8] syscall_call+0x7/0xb
   ===
  Code: 40 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 40 38 89 44 24 08 85 d2 74
  05 8b 72 30 eb 0b a1 a0 79 42 c0 8b 40 14 8b 70 38
  8b 7c 24 08 8b 47 08 31 ff 3b 46 08 0f 84 c1 00 00 00 8b 54 24 08 8b 42
  08 EIP: [c018db5d] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:f79a1e50
 
  Thanks for fixing this issue
 
  Michal

 Regards,
 Michal
-
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: OOPS when swsusp/resume when connected to the internet via BT and GPRS

2007-05-06 Thread Adrian Bunk
On Mon, May 07, 2007 at 07:04:29AM +0200, CIJOML wrote:
 Hi Michal,
 
 my kernel is tainted with madwifi opensource driver :). Only binary part is 
 ath_hal module, which doesn't have anythink to do with this part of kernel.

Any module can change any part of the kernel, e.g. a part of the code 
executed when loading the ath_hal module could accidentally corrupt a 
kernel data structure.

 Ath_hal is doing RF part of card to protect others tune/transmit in other 
 frequency than 2.5/5.8GHz (Wifi 802.11a/b/g).
 
 My kernel is 100% opensource :)

That's wrong, the binary-only blob from ath_hal loaded into your kernel 
is not opensource.

 And BTW this happens also with madwifi kernel modules unloaded.

An Oops without any external module ever loaded since booting is 
strongly preferred.

 Best regards
 
 Michal

cu
Adrian

-- 

   Is there not promise of rain? Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   Only a promise, Lao Er said.
   Pearl S. Buck - Dragon Seed

-
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: Oops in swsusp

2005-04-11 Thread Rafael J. Wysocki
Hi,

On Monday, 11 of April 2005 18:01, Andreas Steinmetz wrote:
> Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
> > 
> >>Pavel,
> >>during testing of the encrypted swsusp_image on x86_64 I did get an Oops
> >>from time to time at memcpy+11 called from swsusp_save+1090 which turns
> >>out to be the memcpy in copy_data_pages() of swsusp.c.
> >>The Oops is caused by a NULL pointer (I don't remember if it was source
> >>or destination).
> > 
> > 
> > It's quite important, however.  If it's the destination, it's probably a 
> > bug in
> > swsusp.  Otherwise, the problem is more serious.  Could you, please,
> > add BUG_ON(!pbe->address) right before the memcpy() and retest?
> 
> Here's the result:
> 
> BUG_ON(!pbe->address) hits, so is seems to be a swsusp problem.
> 
> So I added a BUG_ON(!to_copy) as shown below (mangled for mailing):
> 
> if (saveable(zone, _pfn)) {
>struct page * page;
>BUG_ON(!to_copy);
>page = pfn_to_page(zone_pfn + zone->zone_start_pfn);
>pbe->orig_address = (long) page_address(page);
>/* copy_page is not usable for copying task structs. */
>BUG_ON(!pbe->address);
>memcpy((void *)pbe->address, (void *)pbe->orig_address,
>   PAGE_SIZE);
>pbe++;
>to_copy--;
> }
> 
> The BUG_ON(!to_copy) hits, too.

Oh, I see.  You have discovered a bug in the code that was replaced
in 2.6.12-rc1. :-)  Please use 2.6.12-rc2 or the latest -mm for
testing/development of swsusp.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
-
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: Oops in swsusp

2005-04-11 Thread Andreas Steinmetz
Rafael J. Wysocki wrote:
> Hi,
> 
> On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
> 
>>Pavel,
>>during testing of the encrypted swsusp_image on x86_64 I did get an Oops
>>from time to time at memcpy+11 called from swsusp_save+1090 which turns
>>out to be the memcpy in copy_data_pages() of swsusp.c.
>>The Oops is caused by a NULL pointer (I don't remember if it was source
>>or destination).
> 
> 
> It's quite important, however.  If it's the destination, it's probably a bug 
> in
> swsusp.  Otherwise, the problem is more serious.  Could you, please,
> add BUG_ON(!pbe->address) right before the memcpy() and retest?

Here's the result:

BUG_ON(!pbe->address) hits, so is seems to be a swsusp problem.

So I added a BUG_ON(!to_copy) as shown below (mangled for mailing):

if (saveable(zone, _pfn)) {
   struct page * page;
   BUG_ON(!to_copy);
   page = pfn_to_page(zone_pfn + zone->zone_start_pfn);
   pbe->orig_address = (long) page_address(page);
   /* copy_page is not usable for copying task structs. */
   BUG_ON(!pbe->address);
   memcpy((void *)pbe->address, (void *)pbe->orig_address,
  PAGE_SIZE);
   pbe++;
   to_copy--;
}

The BUG_ON(!to_copy) hits, too.

So it seems that the result sum of saveable() increases between
count_data_pages() and copy_data_pages(). The problem seems to be
easiest hit when starting a larger GUI application and suspending during
application startup. It does ususally take a few suspend/resume
iterations to hit the bug.

Pavel,
the crypto stuff in swsusp.c starts in data_write() which is called
after copy_data_pages() if I'm right. In this case the crypto stuff
can't be the culprit.
-- 
Andreas Steinmetz   SPAMmers use [EMAIL PROTECTED]
-
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: Oops in swsusp

2005-04-11 Thread Andreas Steinmetz
Rafael J. Wysocki wrote:
> Hi,
> 
> On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
> 
>>Pavel,
>>during testing of the encrypted swsusp_image on x86_64 I did get an Oops
>>from time to time at memcpy+11 called from swsusp_save+1090 which turns
>>out to be the memcpy in copy_data_pages() of swsusp.c.
>>The Oops is caused by a NULL pointer (I don't remember if it was source
>>or destination).
> 
> 
> It's quite important, however.  If it's the destination, it's probably a bug 
> in
> swsusp.  Otherwise, the problem is more serious.  Could you, please,
> add BUG_ON(!pbe->address) right before the memcpy() and retest?

I'll try.

-- 
Andreas Steinmetz   SPAMmers use [EMAIL PROTECTED]
-
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: Oops in swsusp

2005-04-11 Thread Pavel Machek
Hi!

> during testing of the encrypted swsusp_image on x86_64 I did get an Oops
> from time to time at memcpy+11 called from swsusp_save+1090 which turns
> out to be the memcpy in copy_data_pages() of swsusp.c.
> The Oops is caused by a NULL pointer (I don't remember if it was source
> or destination).
> This Oops seems to be unrelated to the encrypted image addition as I
> didn't touch any code in that area.

Could you still try to reproduce without any patches? Alocating memory
at wrong moment may cause something like that, and crypto routines
might do that.
Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.
-
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: Oops in swsusp

2005-04-11 Thread Rafael J. Wysocki
Hi,

On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
> Pavel,
> during testing of the encrypted swsusp_image on x86_64 I did get an Oops
> from time to time at memcpy+11 called from swsusp_save+1090 which turns
> out to be the memcpy in copy_data_pages() of swsusp.c.
> The Oops is caused by a NULL pointer (I don't remember if it was source
> or destination).

It's quite important, however.  If it's the destination, it's probably a bug in
swsusp.  Otherwise, the problem is more serious.  Could you, please,
add BUG_ON(!pbe->address) right before the memcpy() and retest?

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
-
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: Oops in swsusp

2005-04-11 Thread Rafael J. Wysocki
Hi,

On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
 Pavel,
 during testing of the encrypted swsusp_image on x86_64 I did get an Oops
 from time to time at memcpy+11 called from swsusp_save+1090 which turns
 out to be the memcpy in copy_data_pages() of swsusp.c.
 The Oops is caused by a NULL pointer (I don't remember if it was source
 or destination).

It's quite important, however.  If it's the destination, it's probably a bug in
swsusp.  Otherwise, the problem is more serious.  Could you, please,
add BUG_ON(!pbe-address) right before the memcpy() and retest?

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll Alice's Adventures in Wonderland
-
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: Oops in swsusp

2005-04-11 Thread Pavel Machek
Hi!

 during testing of the encrypted swsusp_image on x86_64 I did get an Oops
 from time to time at memcpy+11 called from swsusp_save+1090 which turns
 out to be the memcpy in copy_data_pages() of swsusp.c.
 The Oops is caused by a NULL pointer (I don't remember if it was source
 or destination).
 This Oops seems to be unrelated to the encrypted image addition as I
 didn't touch any code in that area.

Could you still try to reproduce without any patches? Alocating memory
at wrong moment may cause something like that, and crypto routines
might do that.
Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.
-
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: Oops in swsusp

2005-04-11 Thread Andreas Steinmetz
Rafael J. Wysocki wrote:
 Hi,
 
 On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
 
Pavel,
during testing of the encrypted swsusp_image on x86_64 I did get an Oops
from time to time at memcpy+11 called from swsusp_save+1090 which turns
out to be the memcpy in copy_data_pages() of swsusp.c.
The Oops is caused by a NULL pointer (I don't remember if it was source
or destination).
 
 
 It's quite important, however.  If it's the destination, it's probably a bug 
 in
 swsusp.  Otherwise, the problem is more serious.  Could you, please,
 add BUG_ON(!pbe-address) right before the memcpy() and retest?

I'll try.

-- 
Andreas Steinmetz   SPAMmers use [EMAIL PROTECTED]
-
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: Oops in swsusp

2005-04-11 Thread Andreas Steinmetz
Rafael J. Wysocki wrote:
 Hi,
 
 On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
 
Pavel,
during testing of the encrypted swsusp_image on x86_64 I did get an Oops
from time to time at memcpy+11 called from swsusp_save+1090 which turns
out to be the memcpy in copy_data_pages() of swsusp.c.
The Oops is caused by a NULL pointer (I don't remember if it was source
or destination).
 
 
 It's quite important, however.  If it's the destination, it's probably a bug 
 in
 swsusp.  Otherwise, the problem is more serious.  Could you, please,
 add BUG_ON(!pbe-address) right before the memcpy() and retest?

Here's the result:

BUG_ON(!pbe-address) hits, so is seems to be a swsusp problem.

So I added a BUG_ON(!to_copy) as shown below (mangled for mailing):

if (saveable(zone, zone_pfn)) {
   struct page * page;
   BUG_ON(!to_copy);
   page = pfn_to_page(zone_pfn + zone-zone_start_pfn);
   pbe-orig_address = (long) page_address(page);
   /* copy_page is not usable for copying task structs. */
   BUG_ON(!pbe-address);
   memcpy((void *)pbe-address, (void *)pbe-orig_address,
  PAGE_SIZE);
   pbe++;
   to_copy--;
}

The BUG_ON(!to_copy) hits, too.

So it seems that the result sum of saveable() increases between
count_data_pages() and copy_data_pages(). The problem seems to be
easiest hit when starting a larger GUI application and suspending during
application startup. It does ususally take a few suspend/resume
iterations to hit the bug.

Pavel,
the crypto stuff in swsusp.c starts in data_write() which is called
after copy_data_pages() if I'm right. In this case the crypto stuff
can't be the culprit.
-- 
Andreas Steinmetz   SPAMmers use [EMAIL PROTECTED]
-
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: Oops in swsusp

2005-04-11 Thread Rafael J. Wysocki
Hi,

On Monday, 11 of April 2005 18:01, Andreas Steinmetz wrote:
 Rafael J. Wysocki wrote:
  Hi,
  
  On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
  
 Pavel,
 during testing of the encrypted swsusp_image on x86_64 I did get an Oops
 from time to time at memcpy+11 called from swsusp_save+1090 which turns
 out to be the memcpy in copy_data_pages() of swsusp.c.
 The Oops is caused by a NULL pointer (I don't remember if it was source
 or destination).
  
  
  It's quite important, however.  If it's the destination, it's probably a 
  bug in
  swsusp.  Otherwise, the problem is more serious.  Could you, please,
  add BUG_ON(!pbe-address) right before the memcpy() and retest?
 
 Here's the result:
 
 BUG_ON(!pbe-address) hits, so is seems to be a swsusp problem.
 
 So I added a BUG_ON(!to_copy) as shown below (mangled for mailing):
 
 if (saveable(zone, zone_pfn)) {
struct page * page;
BUG_ON(!to_copy);
page = pfn_to_page(zone_pfn + zone-zone_start_pfn);
pbe-orig_address = (long) page_address(page);
/* copy_page is not usable for copying task structs. */
BUG_ON(!pbe-address);
memcpy((void *)pbe-address, (void *)pbe-orig_address,
   PAGE_SIZE);
pbe++;
to_copy--;
 }
 
 The BUG_ON(!to_copy) hits, too.

Oh, I see.  You have discovered a bug in the code that was replaced
in 2.6.12-rc1. :-)  Please use 2.6.12-rc2 or the latest -mm for
testing/development of swsusp.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll Alice's Adventures in Wonderland
-
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/


Oops in swsusp

2005-04-10 Thread Andreas Steinmetz
Pavel,
during testing of the encrypted swsusp_image on x86_64 I did get an Oops
from time to time at memcpy+11 called from swsusp_save+1090 which turns
out to be the memcpy in copy_data_pages() of swsusp.c.
The Oops is caused by a NULL pointer (I don't remember if it was source
or destination).
This Oops seems to be unrelated to the encrypted image addition as I
didn't touch any code in that area.
-- 
Andreas Steinmetz   SPAMmers use [EMAIL PROTECTED]
-
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/


Oops in swsusp

2005-04-10 Thread Andreas Steinmetz
Pavel,
during testing of the encrypted swsusp_image on x86_64 I did get an Oops
from time to time at memcpy+11 called from swsusp_save+1090 which turns
out to be the memcpy in copy_data_pages() of swsusp.c.
The Oops is caused by a NULL pointer (I don't remember if it was source
or destination).
This Oops seems to be unrelated to the encrypted image addition as I
didn't touch any code in that area.
-- 
Andreas Steinmetz   SPAMmers use [EMAIL PROTECTED]
-
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/


2.6.11-rc4: oops in swsusp

2005-02-14 Thread John M Flinchbaugh
i saw the following oops when trying to swsusp (echo disk >
/sys/power/state) my thinkpad r40.  everything worked fine, except for
this debug message:
Stopping tasks:
=|
Freeing memory... done (101637 pages freed)
swsusp: Need to copy 13308 pages
Debug: sleeping function called from invalid context at mm/slab.c:2082
in_atomic():0, irqs_disabled():1
 [] dump_stack+0x17/0x20
 [] __might_sleep+0xac/0xc0
 [] kmem_cache_alloc+0x5e/0x60
 [] acpi_pci_link_set+0x44/0x1a1
 [] irqrouter_resume+0x1f/0x34
 [] sysdev_resume+0xf7/0xfc
 [] device_power_up+0x8/0xe
 [] swsusp_suspend+0x48/0x50
 [] pm_suspend_disk+0x26/0x70
 [] enter_state+0x68/0x70
 [] state_store+0xa3/0xaa
 [] subsys_attr_store+0x37/0x40
 [] flush_write_buffer+0x2e/0x40
 [] sysfs_write_file+0x6f/0x90
 [] vfs_write+0xa4/0x110
 [] sys_write+0x41/0x70
 [] syscall_call+0x7/0xb

kernel config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-rc4
# Mon Feb 14 10:12:27 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=""

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
CONFIG_ACPI_IBM=m
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m

2.6.11-rc4: oops in swsusp

2005-02-14 Thread John M Flinchbaugh
i saw the following oops when trying to swsusp (echo disk 
/sys/power/state) my thinkpad r40.  everything worked fine, except for
this debug message:
Stopping tasks:
=|
Freeing memory... done (101637 pages freed)
swsusp: Need to copy 13308 pages
Debug: sleeping function called from invalid context at mm/slab.c:2082
in_atomic():0, irqs_disabled():1
 [c01035a7] dump_stack+0x17/0x20
 [c0113f3c] __might_sleep+0xac/0xc0
 [c013c66e] kmem_cache_alloc+0x5e/0x60
 [c0201899] acpi_pci_link_set+0x44/0x1a1
 [c0201d38] irqrouter_resume+0x1f/0x34
 [c0226647] sysdev_resume+0xf7/0xfc
 [c022a9d8] device_power_up+0x8/0xe
 [c0131708] swsusp_suspend+0x48/0x50
 [c0131af6] pm_suspend_disk+0x26/0x70
 [c0130188] enter_state+0x68/0x70
 [c01302c3] state_store+0xa3/0xaa
 [c0189ba7] subsys_attr_store+0x37/0x40
 [c0189e0e] flush_write_buffer+0x2e/0x40
 [c0189e8f] sysfs_write_file+0x6f/0x90
 [c0151ec4] vfs_write+0xa4/0x110
 [c0151fe1] sys_write+0x41/0x70
 [c010304f] syscall_call+0x7/0xb

kernel config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-rc4
# Mon Feb 14 10:12:27 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y

#
# General setup
#
CONFIG_LOCALVERSION=
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
CONFIG_ACPI_IBM=m
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y