linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
       [not found] <20060727015639.9c89db57.akpm@osdl.org>
@ 2006-07-29 17:58 ` Jiri Slaby
  2006-07-29 18:59   ` Rafael J. Wysocki
  0 siblings, 1 reply; 13+ messages in thread
From: Jiri Slaby @ 2006-07-29 17:58 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, pavel, linux-pm, linux-mm

Andrew Morton napsal(a):
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/

Hello,

I have problems with swsusp again. While suspending, the very last thing kernel
writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
Here is a snapshot of the screen:
http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif

It's SMP system (HT), higmem enabled (1 gig of ram).

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 17:58 ` swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1] Jiri Slaby
@ 2006-07-29 18:59   ` Rafael J. Wysocki
  2006-07-29 23:06     ` Jiri Slaby
  0 siblings, 1 reply; 13+ messages in thread
From: Rafael J. Wysocki @ 2006-07-29 18:59 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Andrew Morton, linux-kernel, pavel, linux-pm, linux-mm

Hi,

On Saturday 29 July 2006 19:58, Jiri Slaby wrote:
> Andrew Morton napsal(a):
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/
> 
> Hello,
> 
> I have problems with swsusp again. While suspending, the very last thing kernel
> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
> Here is a snapshot of the screen:
> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
> 
> It's SMP system (HT), higmem enabled (1 gig of ram).

Most probably it hangs in device_power_up(), so the problem seems to be
with one of the devices that are resumed with IRQs off.

Does vanila .18-rc2 work?

Rafael

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 18:59   ` Rafael J. Wysocki
@ 2006-07-29 23:06     ` Jiri Slaby
  2006-07-29 23:10       ` Rafael J. Wysocki
  2006-07-29 23:22       ` Pavel Machek
  0 siblings, 2 replies; 13+ messages in thread
From: Jiri Slaby @ 2006-07-29 23:06 UTC (permalink / raw)
  To: Rafael J. Wysocki
  Cc: Jiri Slaby, Andrew Morton, linux-kernel, pavel, linux-pm, linux-mm

Rafael J. Wysocki napsal(a):
> Hi,
> 
> On Saturday 29 July 2006 19:58, Jiri Slaby wrote:
>> Andrew Morton napsal(a):
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/
>> Hello,
>>
>> I have problems with swsusp again. While suspending, the very last thing kernel
>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
>> Here is a snapshot of the screen:
>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
>>
>> It's SMP system (HT), higmem enabled (1 gig of ram).
> 
> Most probably it hangs in device_power_up(), so the problem seems to be
> with one of the devices that are resumed with IRQs off.
> 
> Does vanila .18-rc2 work?

Yup, it does.

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:06     ` Jiri Slaby
@ 2006-07-29 23:10       ` Rafael J. Wysocki
  2006-07-29 23:59         ` Jiri Slaby
  2006-07-30  0:03         ` Jiri Slaby
  2006-07-29 23:22       ` Pavel Machek
  1 sibling, 2 replies; 13+ messages in thread
From: Rafael J. Wysocki @ 2006-07-29 23:10 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Andrew Morton, linux-kernel, pavel, linux-pm, linux-mm

On Sunday 30 July 2006 01:06, Jiri Slaby wrote:
> Rafael J. Wysocki napsal(a):
> > Hi,
> > 
> > On Saturday 29 July 2006 19:58, Jiri Slaby wrote:
> >> Andrew Morton napsal(a):
> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/
> >> Hello,
> >>
> >> I have problems with swsusp again. While suspending, the very last thing kernel
> >> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
> >> Here is a snapshot of the screen:
> >> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
> >>
> >> It's SMP system (HT), higmem enabled (1 gig of ram).
> > 
> > Most probably it hangs in device_power_up(), so the problem seems to be
> > with one of the devices that are resumed with IRQs off.
> > 
> > Does vanila .18-rc2 work?
> 
> Yup, it does.

Hm, in fact this may be a problem with any device driver.

Could you please boot the system with init=/bin/bash and try to suspend?

Rafael

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:06     ` Jiri Slaby
  2006-07-29 23:10       ` Rafael J. Wysocki
@ 2006-07-29 23:22       ` Pavel Machek
  2006-07-29 23:58         ` Jiri Slaby
  1 sibling, 1 reply; 13+ messages in thread
From: Pavel Machek @ 2006-07-29 23:22 UTC (permalink / raw)
  To: Jiri Slaby
  Cc: Rafael J. Wysocki, Andrew Morton, linux-kernel, linux-pm, linux-mm

Hi!

> >> I have problems with swsusp again. While suspending, the very last thing kernel
> >> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
> >> Here is a snapshot of the screen:
> >> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
> >>
> >> It's SMP system (HT), higmem enabled (1 gig of ram).
> > 
> > Most probably it hangs in device_power_up(), so the problem seems to be
> > with one of the devices that are resumed with IRQs off.
> > 
> > Does vanila .18-rc2 work?
> 
> Yup, it does.

Can you try up kernel, no highmem? (mem=512M)?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:22       ` Pavel Machek
@ 2006-07-29 23:58         ` Jiri Slaby
  2006-07-30  0:06           ` Pavel Machek
  2006-07-30 11:36           ` James Courtier-Dutton
  0 siblings, 2 replies; 13+ messages in thread
From: Jiri Slaby @ 2006-07-29 23:58 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Jiri Slaby, Rafael J. Wysocki, Andrew Morton, linux-kernel,
	linux-pm, linux-mm

Pavel Machek napsal(a):
> Hi!
> 
>>>> I have problems with swsusp again. While suspending, the very last thing kernel
>>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
>>>> Here is a snapshot of the screen:
>>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
>>>>
>>>> It's SMP system (HT), higmem enabled (1 gig of ram).
>>> Most probably it hangs in device_power_up(), so the problem seems to be
>>> with one of the devices that are resumed with IRQs off.
>>>
>>> Does vanila .18-rc2 work?
>> Yup, it does.
> 
> Can you try up kernel, no highmem? (mem=512M)?

It writes then:
p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0
in endless loop when resuming -- after reading from swap.

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:10       ` Rafael J. Wysocki
@ 2006-07-29 23:59         ` Jiri Slaby
  2006-07-30  0:03         ` Jiri Slaby
  1 sibling, 0 replies; 13+ messages in thread
From: Jiri Slaby @ 2006-07-29 23:59 UTC (permalink / raw)
  To: Rafael J. Wysocki
  Cc: Jiri Slaby, Andrew Morton, linux-kernel, pavel, linux-pm, linux-mm

Rafael J. Wysocki napsal(a):
> On Sunday 30 July 2006 01:06, Jiri Slaby wrote:
>> Rafael J. Wysocki napsal(a):
>>> Hi,
>>>
>>> On Saturday 29 July 2006 19:58, Jiri Slaby wrote:
>>>> Andrew Morton napsal(a):
>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/
>>>> Hello,
>>>>
>>>> I have problems with swsusp again. While suspending, the very last thing kernel
>>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
>>>> Here is a snapshot of the screen:
>>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
>>>>
>>>> It's SMP system (HT), higmem enabled (1 gig of ram).
>>> Most probably it hangs in device_power_up(), so the problem seems to be
>>> with one of the devices that are resumed with IRQs off.
>>>
>>> Does vanila .18-rc2 work?
>> Yup, it does.
> 
> Hm, in fact this may be a problem with any device driver.
> 
> Could you please boot the system with init=/bin/bash and try to suspend?

No change.

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:10       ` Rafael J. Wysocki
  2006-07-29 23:59         ` Jiri Slaby
@ 2006-07-30  0:03         ` Jiri Slaby
  1 sibling, 0 replies; 13+ messages in thread
From: Jiri Slaby @ 2006-07-30  0:03 UTC (permalink / raw)
  To: Rafael J. Wysocki
  Cc: Jiri Slaby, Andrew Morton, linux-kernel, pavel, linux-pm, linux-mm

Rafael J. Wysocki napsal(a):
> On Sunday 30 July 2006 01:06, Jiri Slaby wrote:
>> Rafael J. Wysocki napsal(a):
>>> Hi,
>>>
>>> On Saturday 29 July 2006 19:58, Jiri Slaby wrote:
>>>> Andrew Morton napsal(a):
>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/
>>>> Hello,
>>>>
>>>> I have problems with swsusp again. While suspending, the very last thing kernel
>>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
>>>> Here is a snapshot of the screen:
>>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
>>>>
>>>> It's SMP system (HT), higmem enabled (1 gig of ram).
>>> Most probably it hangs in device_power_up(), so the problem seems to be
>>> with one of the devices that are resumed with IRQs off.
>>>
>>> Does vanila .18-rc2 work?
>> Yup, it does.
> 
> Hm, in fact this may be a problem with any device driver.

Note 1: 2.6.18-rc1-mm2 was(is) working just fine.
Note 2: when I was going through these -mm diff, the culprit may be radeon
driver -- there are some PM changes... Or if you want to go on your own, here is
lspci output:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub
Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI
Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface
Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller
(rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon
9000] (rev 01)
01:00.1 Display controller: ATI Technologies Inc Radeon RV250 [Radeon 9000]
(Secondary) (rev 01)
02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
02:02.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a)
02:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000
Controller (PHY/Link)
02:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet
Controller (rev 02)

with -n:
00:00.0 0600: 8086:2570 (rev 02)
00:01.0 0604: 8086:2571 (rev 02)
00:1d.0 0c03: 8086:24d2 (rev 02)
00:1d.1 0c03: 8086:24d4 (rev 02)
00:1d.2 0c03: 8086:24d7 (rev 02)
00:1d.3 0c03: 8086:24de (rev 02)
00:1d.7 0c03: 8086:24dd (rev 02)
00:1e.0 0604: 8086:244e (rev c2)
00:1f.0 0601: 8086:24d0 (rev 02)
00:1f.1 0101: 8086:24db (rev 02)
00:1f.2 0101: 8086:24d1 (rev 02)
00:1f.3 0c05: 8086:24d3 (rev 02)
01:00.0 0300: 1002:4966 (rev 01)
01:00.1 0380: 1002:496e (rev 01)
02:02.0 0401: 1102:0002 (rev 0a)
02:02.1 0980: 1102:7002 (rev 0a)
02:05.0 0c00: 104c:8024
02:08.0 0200: 8086:1050 (rev 02)

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:58         ` Jiri Slaby
@ 2006-07-30  0:06           ` Pavel Machek
  2006-07-30  7:31             ` Rafael J. Wysocki
  2006-07-30 11:36           ` James Courtier-Dutton
  1 sibling, 1 reply; 13+ messages in thread
From: Pavel Machek @ 2006-07-30  0:06 UTC (permalink / raw)
  To: Jiri Slaby
  Cc: Rafael J. Wysocki, Andrew Morton, linux-kernel, linux-pm, linux-mm

Hi!

> >>>> I have problems with swsusp again. While suspending, the very last thing kernel
> >>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
> >>>> Here is a snapshot of the screen:
> >>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
> >>>>
> >>>> It's SMP system (HT), higmem enabled (1 gig of ram).
> >>> Most probably it hangs in device_power_up(), so the problem seems to be
> >>> with one of the devices that are resumed with IRQs off.
> >>>
> >>> Does vanila .18-rc2 work?
> >> Yup, it does.
> > 
> > Can you try up kernel, no highmem? (mem=512M)?
> 
> It writes then:
> p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0
> in endless loop when resuming -- after reading from swap.

Okay, so we have two different problems here.

One is "hang during suspend" with smp/highmem mode, and one is
probably driver problem with p16v (whatever it is).

/data/l/linux/sound/pci/emu10k1/irq.c:
snd_printk(KERN_ERR "p16v: status: 0x%08x, mask=0x%08x, pvoice=%p,
use=%d\n", status2, mask, pvoice, pvoice->use);

...aha, so you may want to unload emu10k1 for testing.

Since you mention radeon in one of your other mails, just try it in
vesafb mode...
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-30  0:06           ` Pavel Machek
@ 2006-07-30  7:31             ` Rafael J. Wysocki
  2006-07-30  8:08               ` Jiri Slaby
  0 siblings, 1 reply; 13+ messages in thread
From: Rafael J. Wysocki @ 2006-07-30  7:31 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Jiri Slaby, Andrew Morton, linux-kernel, linux-pm, linux-mm

On Sunday 30 July 2006 02:06, Pavel Machek wrote:
> Hi!
> 
> > >>>> I have problems with swsusp again. While suspending, the very last thing kernel
> > >>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
> > >>>> Here is a snapshot of the screen:
> > >>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
> > >>>>
> > >>>> It's SMP system (HT), higmem enabled (1 gig of ram).
> > >>> Most probably it hangs in device_power_up(), so the problem seems to be
> > >>> with one of the devices that are resumed with IRQs off.
> > >>>
> > >>> Does vanila .18-rc2 work?
> > >> Yup, it does.
> > > 
> > > Can you try up kernel, no highmem? (mem=512M)?
> > 
> > It writes then:
> > p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0
> > in endless loop when resuming -- after reading from swap.
> 
> Okay, so we have two different problems here.
> 
> One is "hang during suspend" with smp/highmem mode,

That one is "interesting".  I've no idea why the restoration of highmem would
have caused the box to hang like that.  Jiri, could you please post the output
of dmesg after a fresh boot?

> and one is probably driver problem with p16v (whatever it is).
> 
> /data/l/linux/sound/pci/emu10k1/irq.c:
> snd_printk(KERN_ERR "p16v: status: 0x%08x, mask=0x%08x, pvoice=%p,
> use=%d\n", status2, mask, pvoice, pvoice->use);
> 
> ...aha, so you may want to unload emu10k1 for testing.
> 
> Since you mention radeon in one of your other mails, just try it in
> vesafb mode...

Yes.  Or just don't compile the radeon driver and see what happens.

Rafael

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-30  7:31             ` Rafael J. Wysocki
@ 2006-07-30  8:08               ` Jiri Slaby
  2006-07-30  9:28                 ` Rafael J. Wysocki
  0 siblings, 1 reply; 13+ messages in thread
From: Jiri Slaby @ 2006-07-30  8:08 UTC (permalink / raw)
  To: Rafael J. Wysocki
  Cc: Pavel Machek, Andrew Morton, linux-kernel, linux-pm, linux-mm

Rafael J. Wysocki napsal(a):
> On Sunday 30 July 2006 02:06, Pavel Machek wrote:
>> Hi!
>>
>>>>>>> I have problems with swsusp again. While suspending, the very last thing kernel
>>>>>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
>>>>>>> Here is a snapshot of the screen:
>>>>>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
>>>>>>>
>>>>>>> It's SMP system (HT), higmem enabled (1 gig of ram).
>>>>>> Most probably it hangs in device_power_up(), so the problem seems to be
>>>>>> with one of the devices that are resumed with IRQs off.
>>>>>>
>>>>>> Does vanila .18-rc2 work?
>>>>> Yup, it does.
>>>> Can you try up kernel, no highmem? (mem=512M)?
>>> It writes then:
>>> p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0
>>> in endless loop when resuming -- after reading from swap.
>> Okay, so we have two different problems here.
>>
>> One is "hang during suspend" with smp/highmem mode,
> 
> That one is "interesting".  I've no idea why the restoration of highmem would
> have caused the box to hang like that.  Jiri, could you please post the output
> of dmesg after a fresh boot?

higmem is ok. ioapic0 is the culprit -- its class resume dies:
        if (cls->resume)
                cls->resume(dev); <----
in __sysdev_resume

>> and one is probably driver problem with p16v (whatever it is).
>>
>> /data/l/linux/sound/pci/emu10k1/irq.c:
>> snd_printk(KERN_ERR "p16v: status: 0x%08x, mask=0x%08x, pvoice=%p,
>> use=%d\n", status2, mask, pvoice, pvoice->use);
>>
>> ...aha, so you may want to unload emu10k1 for testing.

Sure, this helped.

>> Since you mention radeon in one of your other mails, just try it in
>> vesafb mode...
> 
> Yes.  Or just don't compile the radeon driver and see what happens.

Doesn't matter. I do not use graphics (fb) in console -- radeon was not inited
at all, it was bad tip.

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-30  8:08               ` Jiri Slaby
@ 2006-07-30  9:28                 ` Rafael J. Wysocki
  0 siblings, 0 replies; 13+ messages in thread
From: Rafael J. Wysocki @ 2006-07-30  9:28 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Pavel Machek, Andrew Morton, linux-kernel, linux-pm, linux-mm

On Sunday 30 July 2006 10:08, Jiri Slaby wrote:
> Rafael J. Wysocki napsal(a):
> > On Sunday 30 July 2006 02:06, Pavel Machek wrote:
> >> Hi!
> >>
> >>>>>>> I have problems with swsusp again. While suspending, the very last thing kernel
> >>>>>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
> >>>>>>> Here is a snapshot of the screen:
> >>>>>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
> >>>>>>>
> >>>>>>> It's SMP system (HT), higmem enabled (1 gig of ram).
> >>>>>> Most probably it hangs in device_power_up(), so the problem seems to be
> >>>>>> with one of the devices that are resumed with IRQs off.
> >>>>>>
> >>>>>> Does vanila .18-rc2 work?
> >>>>> Yup, it does.
> >>>> Can you try up kernel, no highmem? (mem=512M)?
> >>> It writes then:
> >>> p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0
> >>> in endless loop when resuming -- after reading from swap.
> >> Okay, so we have two different problems here.
> >>
> >> One is "hang during suspend" with smp/highmem mode,
> > 
> > That one is "interesting".  I've no idea why the restoration of highmem would
> > have caused the box to hang like that.  Jiri, could you please post the output
> > of dmesg after a fresh boot?
> 
> higmem is ok. ioapic0 is the culprit -- its class resume dies:
>         if (cls->resume)
>                 cls->resume(dev); <----
> in __sysdev_resume

Ah, so my first guess was actually correct. :-)

> >> and one is probably driver problem with p16v (whatever it is).
> >>
> >> /data/l/linux/sound/pci/emu10k1/irq.c:
> >> snd_printk(KERN_ERR "p16v: status: 0x%08x, mask=0x%08x, pvoice=%p,
> >> use=%d\n", status2, mask, pvoice, pvoice->use);
> >>
> >> ...aha, so you may want to unload emu10k1 for testing.
> 
> Sure, this helped.

So, we have two different regressions here.

Please try to revert git-alsa.patch and see if the emu10k1-related problem
goes away.

As far as the first one is concerned, the genirq-* patches look suspicious.

Greetings,
Rafael

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
  2006-07-29 23:58         ` Jiri Slaby
  2006-07-30  0:06           ` Pavel Machek
@ 2006-07-30 11:36           ` James Courtier-Dutton
  1 sibling, 0 replies; 13+ messages in thread
From: James Courtier-Dutton @ 2006-07-30 11:36 UTC (permalink / raw)
  To: Jiri Slaby
  Cc: Pavel Machek, Rafael J. Wysocki, Andrew Morton, linux-kernel,
	linux-pm, linux-mm

Jiri Slaby wrote:
> Pavel Machek napsal(a):
>> Hi!
>>
>>>>> I have problems with swsusp again. While suspending, the very last thing kernel
>>>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all.
>>>>> Here is a snapshot of the screen:
>>>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif
>>>>>
>>>>> It's SMP system (HT), higmem enabled (1 gig of ram).
>>>> Most probably it hangs in device_power_up(), so the problem seems to be
>>>> with one of the devices that are resumed with IRQs off.
>>>>
>>>> Does vanila .18-rc2 work?
>>> Yup, it does.
>> Can you try up kernel, no highmem? (mem=512M)?
> 
> It writes then:
> p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0
> in endless loop when resuming -- after reading from swap.
> 
> regards,

The p16v chip is present on some creative sound cards, so this is an
ALSA snd-emu10k1 driver that is causing the endless loop. I will change
the code to force it to recover from the unexpected status 0xffffffff
value. The recovery will just consist of reducing the message to a
single message, instead of an endless loop. That value is never present
during normal operations, and the only case of it occurring that I know
about was during a pcmcia card unplug. If it occurs during insertion or
power resume, then I will have to think about some work around.
Is there any reason that an IRQ routine will be called before the
associated PCI IOPORTs have been configured. I did not think it was the
responsibility of the driver to redo all the initialisation PCI calls to
claim DMA and IOPORTs at power resume. To me it seems that the IRQ
routine is being called before PCI DMA and IOPORTs have been initialised.

James



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2006-07-30 11:36 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20060727015639.9c89db57.akpm@osdl.org>
2006-07-29 17:58 ` swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1] Jiri Slaby
2006-07-29 18:59   ` Rafael J. Wysocki
2006-07-29 23:06     ` Jiri Slaby
2006-07-29 23:10       ` Rafael J. Wysocki
2006-07-29 23:59         ` Jiri Slaby
2006-07-30  0:03         ` Jiri Slaby
2006-07-29 23:22       ` Pavel Machek
2006-07-29 23:58         ` Jiri Slaby
2006-07-30  0:06           ` Pavel Machek
2006-07-30  7:31             ` Rafael J. Wysocki
2006-07-30  8:08               ` Jiri Slaby
2006-07-30  9:28                 ` Rafael J. Wysocki
2006-07-30 11:36           ` James Courtier-Dutton

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox