All of lore.kernel.org
 help / color / mirror / Atom feed
From: "valerio.vanni@inwind.it" <valerio.vanni@inwind.it>
To: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <mchehab@infradead.org>, <alan@lxorguk.ukuu.org.uk>,
	<linux@rainbow-software.org>, <pavel@suse.cz>,
	<hverkuil@xs4all.nl>, <michael.opdenacker@free-electrons.com>
Subject: Re: SAA7134 warning during resume from S3: regression 3.8.13 -> 3.9.0
Date: Tue, 4 Mar 2014 04:57:26 +0100 (CET)	[thread overview]
Message-ID: <10502473.12963741393905446746.JavaMail.defaultUser@defaultHost> (raw)

>----Messaggio originale----
>Da: valerio.vanni@inwind.it
>Data: 14/02/2014 16.29

>The full report is on bugzilla:
>https://bugzilla.kernel.org/show_bug.cgi?id=69581

>[1.] One line summary of the problem:
>
>Kernel gives a oops warning during resume
>from S3 sleep.
>
>[2.] Full description of the problem/report:
>
>OS is Debian Lenny, with vanilla kernel. It happens the same after upgrade to
>Squeeze.
>I've tried with kernels over kernels to find the point and I've found:
>the latest working kernel is 3.8.13, the first failing is 3.9.0
>
>I suspend the machine with s2ram and it goes off.
>During the resume it writes that warning, then it seem to work normally,
>except for serial redirection of console.



>------------[ cut here ]------------
>WARNING: CPU: 0 PID: 7928 at kernel/kmod.c:148 __request_module+0x34/0x1ae()
>Modules linked in: vmnet(O) vsock(O) vmci(O) vmmon(O) lp fbcon font bitblit
>softcursor i915 drm_kms_helper fb fbdev cfbcopyarea video backlight cfbimgblt
>cfbfillrect bnep nfsd lockd sunrpc fuse saa7134_alsa snd_seq_dummy 
snd_seq_oss
>snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_seq_device cifs 
rfcomm
>bluetooth rfkill it87 hwmon_vid isofs zlib_inflate nls_utf8 nls_iso8859_1
>nls_cp850 nls_cp437 nls_ascii cpuid vfat ntfs msdos fat udf nls_iso8859_15
>softdog loop tda1004x saa7134_dvb videobuf_dvb dvb_core tda827x mousedev
>tda8290 tuner snd_hda_codec_realtek snd_hda_intel snd_hda_codec saa7134
>v4l2_common usb_storage videodev r8169 snd_hwdep parport_pc snd_pcm_oss
>snd_mixer_oss videobuf_dma_sg mii ehci_pci parport videobuf_core snd_pcm
>uhci_hcd firewire_ohci firewire_core evdev crc_itu_t ehci_hcd psmouse 
rtc_cmos
>tveeprom pcspkr intel_agp intel_gtt snd_timer snd_page_alloc
>CPU: 0 PID: 7928 Comm: kworker/u8:12 Tainted: G           O 3.13.2 #1
>Hardware name: Gigabyte Technology Co., Ltd. G33M-S2/G33M-S2, BIOS F7f
>04/02/2008
>Workqueue: events_unbound async_run_entry_fn
>00000000 00000000 c13534fe c103d476 c102e079 00000009 f13ede00 f534f1a4
>f80630d0 f534f024 c102e099 00000009 00000000 c103d476 ffffffff 01000282
>c1036a29 00000282 f13edda4 c155c680 c155c680 c1036a5c 003a8aba c1353657
>Call Trace:
>[<c13534fe>] ? dump_stack+0x3e/0x50
>[<c103d476>] ? __request_module+0x34/0x1ae
>[<c102e079>] ? warn_slowpath_common+0x66/0x7a
>[<c102e099>] ? warn_slowpath_null+0xc/0xf
>[<c103d476>] ? __request_module+0x34/0x1ae
>[<c1036a29>] ? try_to_del_timer_sync+0x3a/0x41
>[<c1036a5c>] ? del_timer_sync+0x2c/0x36
>[<c1353657>] ? schedule_timeout+0x147/0x15d
>[<c1036aa6>] ? del_timer+0x40/0x40
>[<f8062370>] ? v4l2_i2c_new_subdev_board+0x23/0xa7 [v4l2_common]
>[<f806243d>] ? v4l2_i2c_new_subdev+0x49/0x51 [v4l2_common]
>[<f831290b>] ? saa7134_board_init2+0x869/0xb58 [saa7134]
>[<c1036a29>] ? try_to_del_timer_sync+0x3a/0x41
>[<c1036a5c>] ? del_timer_sync+0x2c/0x36
>[<c1353657>] ? schedule_timeout+0x147/0x15d
>[<c1030003>] ? do_exit+0x51a/0x7ce
>[<f8313ca7>] ? saa7134_resume+0xbf/0x150 [saa7134]
>[<c11ef0a7>] ? pci_legacy_resume+0x23/0x2c
>[<c11ef19a>] ? pci_pm_thaw+0x62/0x62
>[<c12650d5>] ? dpm_run_callback+0x25/0x60
>[<c1265308>] ? device_resume+0x10f/0x12c
>[<c1265338>] ? async_resume+0x13/0x33
>[<c1048004>] ? async_run_entry_fn+0x52/0xf3
>[<c103fba7>] ? process_one_work+0x200/0x331
>[<c103fe83>] ? worker_thread+0x1ab/0x2e1
>[<c103fcd8>] ? process_one_work+0x331/0x331
>[<c1044120>] ? kthread+0xa1/0xaa
>[<c135b837>] ? ret_from_kernel_thread+0x1b/0x28
>[<c104407f>] ? kthread_freezable_should_stop+0x4d/0x4d
>---[ end trace d02ad8471166632e ]---


             reply	other threads:[~2014-03-04  3:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  3:57 valerio.vanni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-14 15:29 SAA7134 warning during resume from S3: regression 3.8.13 -> 3.9.0 valerio.vanni

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=10502473.12963741393905446746.JavaMail.defaultUser@defaultHost \
    --to=valerio.vanni@inwind.it \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=mchehab@infradead.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=pavel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.