From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Ari Pollak <aripollak@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.10-rc3
Date: Sat, 04 Dec 2004 13:37:35 -0800 [thread overview]
Message-ID: <877jnxago0.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <1102195032.1560.58.camel@tux.rsn.bth.se> (message from Martin Josefsson on Sat, 04 Dec 2004 22:17:12 +0100)
Martin Josefsson <gandalf@wlug.westbo.se> writes:
> This has been discussed in an earlier thread, I was hoping the ALSA
> people would submit the patch but that hasn't happened.
> I'll submit it in a separate mail.
>
> Try the patch below, it should fix the problem.
>
> --- linux/sound/core/init.c 8 Nov 2004 11:37:08 -0000 1.48
> +++ linux/sound/core/init.c 12 Nov 2004 13:56:32 -0000
> @@ -782,12 +782,15 @@<br>
> int snd_card_pci_suspend(struct pci_dev *dev, u32 state)
> {
> snd_card_t *card = pci_get_drvdata(dev);
> + int err;
> if (! card || ! card->pm_suspend)
> return 0;
> if (card->power_state == SNDRV_CTL_POWER_D3hot)
> return 0;
> /* FIXME: correct state value? */
> - return card->pm_suspend(card, 0);
> + err = card->pm_suspend(card, 0);
> + pci_save_state(dev);
> + return err;
> }
>
> int snd_card_pci_resume(struct pci_dev *dev)
thank you. the laptop wakes up now but i get the following when it
resumes (this is the output from dmesg):
Back to C!
Warning: CPU frequency is 1600000, cpufreq assumed 600000 kHz.
MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Bank 1: f200000000000115
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.1 to 64
PCI: Setting latency timer of device 0000:00:1d.2 to 64
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 restarted, EHCI 1.00, driver 26 Oct 2004
ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 6 (level, low) -> IRQ 6
ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 4 (level, low) -> IRQ 4
psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
scheduling while atomic: sleepbtn.sh/0x00000001/3201
[<c0103557>] dump_stack+0x17/0x20
[<c030e4e2>] schedule+0x522/0x530
[<c030e97b>] schedule_timeout+0x5b/0xb0
[<c011fbaf>] msleep+0x2f/0x40
[<e1079387>] ehci_hub_resume+0xd7/0x1c0 [ehci_hcd]
[<e10cce6a>] hcd_hub_resume+0x1a/0x20 [usbcore]
[<e10c9ff2>] usb_resume_device+0xa2/0xc0 [usbcore]
[<c022c50a>] resume_device+0x1a/0x20
[<c022c5b7>] dpm_resume+0xa7/0xb0
[<c022c5d4>] device_resume+0x14/0x30
[<c012f27b>] suspend_finish+0xb/0x30
[<c012f2ed>] enter_state+0x4d/0x70
[<c01f6bd6>] acpi_suspend+0x3d/0x4b
[<c01f6cbb>] acpi_system_write_sleep+0x64/0x76
[<c014e042>] vfs_write+0xa2/0x100
[<c014e151>] sys_write+0x41/0x70
[<c0102ffb>] syscall_call+0x7/0xb
Restarting tasks... done
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Loading R200 Microcode
not sure if this means anything bad or not... i use acpi.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
next prev parent reply other threads:[~2004-12-04 21:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 0:19 Linus Torvalds
2004-12-04 9:06 ` Soeren Sonnenburg
2004-12-04 17:06 ` Alex Romosan
2004-12-04 17:24 ` Ari Pollak
2004-12-04 17:40 ` Alex Romosan
2004-12-04 19:21 ` Ari Pollak
2004-12-04 21:17 ` Martin Josefsson
2004-12-04 21:37 ` Alex Romosan [this message]
2004-12-04 21:42 ` Martin Josefsson
2004-12-04 23:48 ` Paul Ionescu
2004-12-04 21:47 ` Giridhar Pemmasani
2004-12-04 13:35 ` Linux 2.6.10-rc3 oops when 'modprobe -r dvb-bt8xx' Eyal Lebedinsky
2004-12-05 10:15 ` Cal Peake
2004-12-05 11:51 ` Eyal Lebedinsky
2004-12-05 12:50 ` Cal Peake
2004-12-07 18:03 ` Gerd Knorr
2004-12-07 20:34 ` Michael Hunold
2004-12-07 21:55 ` Andrew Morton
2004-12-07 23:08 ` Gerd Knorr
2004-12-06 17:23 ` FS Corruption [Re: Linux 2.6.10-rc3] Kristofer T. Karas
2004-12-06 19:20 ` Linux 2.6.10-rc3 (compile stats) John Cherry
2004-12-05 3:03 Linux 2.6.10-rc3 David Brownell
2004-12-05 4:07 ` Benjamin Herrenschmidt
2004-12-05 12:14 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877jnxago0.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=aripollak@gmail.com \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome