Skip to contentSkip to conversation

new alsa power management completly broken

BUG 2.6.15-git5 Pavel Machek 2 participants 2 messages Jan 12, 2006 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 2 lines · Andrew Morton

swsusp problems...

Where? :-)

Quoted 6 lines

sorry for delay, however i tested it and works perfectly.

just 2 things to notice:
1) [unrelated to this bug] swsusp ram pages write and read is really slower than 2.6.14 one. i didn't follow changes, so don't know what happened

That's a feature. echo 0 > /sys/power/image_size should make it behave like 2.6.14.

Quoted 3 lines

2) when i suspend i continue to see errors 0x660 in my tty. The strange thing is that after resume they are no more in dmesg! strange. however, as i wrote before, it works.

That's not so strange. Messages that happen after memory snapshot are lost (of course).
Pavel

Signature · 1 line
Thanks, Sharp!
#2 lore raw

Pavel Machek ha scritto:

Quoted 10 lines · Andrew Morton
Quoted 5 lines

swsusp problems...

Where? :-)

nowhere now :)
i still have problems on my noteboot about irq 14 not cared...(since ages!) i'll try to do something, if i can't fix i'll report.
(stopping here cause going OT)

Quoted 11 lines
Quoted 10 lines

sorry for delay, however i tested it and works perfectly.

just 2 things to notice:
1) [unrelated to this bug] swsusp ram pages write and read is really slower than 2.6.14 one. i didn't follow changes, so don't know what happened

Quoted 5 lines

That's a feature. echo 0 > /sys/power/image_size should make it behave like 2.6.14.

ok, so i think i should check docs (i hope they are updated)

Quoted 11 lines
Quoted 5 lines

2) when i suspend i continue to see errors 0x660 in my tty. The strange thing is that after resume they are no more in dmesg! strange. however, as i wrote before, it works.

That's not so strange. Messages that happen after memory snapshot are lost (of course).
Pavel

ok, sure, but before this patch i had them in my dmesg.
the patch shouldn't have changed the saving sequence, so..why this happens? and, however some errors still occour.

alsa guys should judge if they are revelant to trace and fix the source of 0x660.

Thanks for support

--
Patrizio Bassi
www.patriziobassi.it