lkml.org 
[lkml]   [2006]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [linux-pm] swsusp regression [Was: 2.6.17-mm1]
On Fri, Jun 23, 2006 at 11:10:21AM +0200, Pavel Machek wrote:
> Hi!
>
> > > Frederik Deweerdt <deweerdt@free.fr> wrote:
> > >
> > > > Thu, Jun 22, 2006 at 12:46:48AM -0700, Andrew Morton wrote:
> > > > > I can bisect it if we're stuck, but that'll require beer or something.
> > > >
> > > > FWIW, my laptop (Dell D610) gave the following results:
> > > > 2.6.17-mm1: suspend_device(): usb_generic_suspend+0x0/0x135 [usbcore]() returns -16
> > > > 2.6.17+origin.patch: suspend_device(): usb_generic_suspend+0x0/0x135 [usbcore]() returns -16
> > >
> > > So it's in mainline already - hence it's some recently-written thing which
> > > was not tested in rc6-mm2.
> > >
> > > > 2.6.17: oops
> > > > 2.6.17.1: oops
> > >
> > > 2.6.17 wasn't supposed to oops. Do you have details on this?
> > >
> > For some reason, unknown to me, the oops won't display on the serial
> > link :(.
>
> Serial console is currently broken by suspend, resume. _But_ I have a
> patch I'd like you to try.... pretty please?
>
Sure :)... I applied it but the output went to the laptop's screen anyway...

> That is not an oops, rather a kernel BUG(). Can you just remove
> might_sleep line and see what happens?
>
> Unfortunately, backtrace does not tell me which notifier chain did
> that :-(. Are you using audit or something like that?
>
> /*
> * lock for reading
> */
> static inline void down_read(struct rw_semaphore *sem)
> {
> might_sleep();
> ~~~~~~~~~~~~~~~~~~~~~~
> rwsemtrace(sem,"Entering down_read");
> __down_read(sem);
> rwsemtrace(sem,"Leaving down_read");
> }
>
Here's the (hand copied) dump when the might_sleep is removed:

esi: 00000003 edit: 00000000 ebp: f6cb9eb8 esp: f6cb9ea4
ds: 007b es: 007b ss: 0068
Process bash (pid: 9402, threadinfo=f6cb8000 task=f7a5c570)
Stack: c0229b71 00000046 00000000 00000286 c0383ca7 f6cb9ecc c013b242 00000003
00000000 00000003 f6cb9ee0 c013b2e8 00000003 c0436890 f6c9a003 f6cb9f08
c013b481 00000003 00000003 00000246 c1788b00 00000003 c04368a0 c043692c
Call Trace:
<c0103eea> show_stack_log_lvl+0x92/0xb7 <c0104100> show_registers+0x1a3/0x21b
<c0104319> die+0x117/0x230 <c03627a6> do_page_fault+0x39c/0x72a
<c0103b2f> error_code+0x4f/0x54 <c013b242> suspend_enter+0x2f/0x52
<c013b2e8> enter_state+0x4b/0x8d <c013b481> state_store+0xa0/0xa2
<c01a5151> subsys_attr_store+0x37/0x41 <c01a53d2> flush_write_buffer+0x3c/0x46
<c01a5443> sysfs_write_file+0x67/0x8b <c0166bb6> vfs_write+0x1b9/0x1be
<c0166c7b> sys_write+0x4b/0x75 <c010300f> sysenter_past_esp+0x54/0x75

Code: 05 c4 42 43 c0 31 43 43 c0 c3 8b 2d 68 6e 54 c0 8b 1d 60 6e 54 c0 8b 35 6c 6e 54 c0 8b 3d 70 6d 54 c0 ff 35 74 6e 54 c0 9d c3 90 <e8> 6d 38 ea ff e8 a2 ff ff ff 6a 03 e8 ec b6 de ff 83 c4 04 c3
EIP: [c043431c>] do_suspend_lowlevel+0x0/0x15 SS:ESP 0068:f6cb6ea4

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

\
 
 \ /
  Last update: 2006-06-23 14:15    [W:0.178 / U:2.268 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site