Mailinglist Archive: opensuse-bugs (10049 mails)
| < Previous | Next > |
[Bug 211511] suspend to RAM hangs on resume on Dell, regression between 2.6.16.21-0.21 and -0.25
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 23 Jan 2007 22:34:01 -0700 (MST)
- Message-id: <20070124053401.B14D2D18@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=211511
------- Comment #18 from jimc@xxxxxxxxxxxxx 2007-01-23 22:34 MST -------
Just to throw an old boot into the pot, I booted the rescue system from the
SuSE 10.1 installation disc, and tried suspending (echo mem > /sys/power/state)
with various sets of modules loaded.
1. I attempted to rmmod each module in order from /proc/modules. It got
an error unloading sd_mod (afterward, /proc/modules showed the status as
"unloading") but the messages scrolled off the screen too fast to read. The
modules that didn't unload were usbcore loop cramfs sd_mod scsi_mod. On
suspend (echo mem > /sys/power/state), it printed "Stopping tasks" and then
hung solid. Not surprising.
2. Same except I didn't touch any of the five modules that previously
would not unload. There were no errors reported. But on suspend it got:
OOPS: 0000 [#1]
Last sysfs file: /power/state
Modules: usbcore loop cramfs sd_mod scsi_mod
CPU: 0
EIP: 0060:[<e0864193>] Not tainted VLI
EFLAGS: 00010246 (2.6.16.13-4-default #1)
EIP is at scsi_bus_suspend +0x1f/0x30 [scsi_mod]
eax: 0 ebx: e1088500 ecx: c019f4a0 edx: df74d7ac
esi: dea54000 edi: 2 ebp: 2 esp: dc1f1ef0
ds: 007b es: 007b ss: 0068
Process: bash
Stack: <0> dea54190 3 0 c02035b0 dea54254 dea54278 3 dea54190 2...
Call trace:
c02035b0 suspend_device +0xac/0xc5
c0203ba4 device_suspend +0x78/0x198
c012bb0a enter_state +0xd2/0x16c
c012bc2c state_store +0x88/0x95
c012bba4 state_store +0x0/0x95
c017b40a subsys_attr_store +0x1e/0x22
c017b505 sysfs_write_file +0x98/0xbe
3. Removed all modules except usbcore ata_piix ahci libata loop cramfs
sd_mod sr_mod scsi_mod cdrom. On suspend it got into S3. On resume it did
brief non-obvious activities with the hard disc and the CD (which had media),
then hung solid -- the behavior for this bug report.
4. Removed all modules except usbcore loop cramfs sd_mod sr_mod scsi_mod
cdrom. On suspend it got the identical oops as before except esp = dab39ef0
and the first stack cell was dea5a190.
Conclusion: there is something wacko in the SCSI subsystem. I don't know if
we're looking at 2 independent bugs, or whether ata_piix gets trashed when it
registers itself with SCSI and then exhibits various nastiness in connection
with software suspend depending on what other modules are loaded. Or whether
ata_piix is doing the trashing.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Comment #18 from jimc@xxxxxxxxxxxxx 2007-01-23 22:34 MST -------
Just to throw an old boot into the pot, I booted the rescue system from the
SuSE 10.1 installation disc, and tried suspending (echo mem > /sys/power/state)
with various sets of modules loaded.
1. I attempted to rmmod each module in order from /proc/modules. It got
an error unloading sd_mod (afterward, /proc/modules showed the status as
"unloading") but the messages scrolled off the screen too fast to read. The
modules that didn't unload were usbcore loop cramfs sd_mod scsi_mod. On
suspend (echo mem > /sys/power/state), it printed "Stopping tasks" and then
hung solid. Not surprising.
2. Same except I didn't touch any of the five modules that previously
would not unload. There were no errors reported. But on suspend it got:
OOPS: 0000 [#1]
Last sysfs file: /power/state
Modules: usbcore loop cramfs sd_mod scsi_mod
CPU: 0
EIP: 0060:[<e0864193>] Not tainted VLI
EFLAGS: 00010246 (2.6.16.13-4-default #1)
EIP is at scsi_bus_suspend +0x1f/0x30 [scsi_mod]
eax: 0 ebx: e1088500 ecx: c019f4a0 edx: df74d7ac
esi: dea54000 edi: 2 ebp: 2 esp: dc1f1ef0
ds: 007b es: 007b ss: 0068
Process: bash
Stack: <0> dea54190 3 0 c02035b0 dea54254 dea54278 3 dea54190 2...
Call trace:
c02035b0 suspend_device +0xac/0xc5
c0203ba4 device_suspend +0x78/0x198
c012bb0a enter_state +0xd2/0x16c
c012bc2c state_store +0x88/0x95
c012bba4 state_store +0x0/0x95
c017b40a subsys_attr_store +0x1e/0x22
c017b505 sysfs_write_file +0x98/0xbe
3. Removed all modules except usbcore ata_piix ahci libata loop cramfs
sd_mod sr_mod scsi_mod cdrom. On suspend it got into S3. On resume it did
brief non-obvious activities with the hard disc and the CD (which had media),
then hung solid -- the behavior for this bug report.
4. Removed all modules except usbcore loop cramfs sd_mod sr_mod scsi_mod
cdrom. On suspend it got the identical oops as before except esp = dab39ef0
and the first stack cell was dea5a190.
Conclusion: there is something wacko in the SCSI subsystem. I don't know if
we're looking at 2 independent bugs, or whether ata_piix gets trashed when it
registers itself with SCSI and then exhibits various nastiness in connection
with software suspend depending on what other modules are loaded. Or whether
ata_piix is doing the trashing.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |