From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915: Cdclk related fixes and polish
Date: Wed, 27 Apr 2016 20:34:02 +0300 [thread overview]
Message-ID: <20160427173402.GT4329@intel.com> (raw)
In-Reply-To: <20160427172817.GR4329@intel.com>
On Wed, Apr 27, 2016 at 08:28:17PM +0300, Ville Syrjälä wrote:
> On Wed, Apr 27, 2016 at 06:19:15AM -0000, Patchwork wrote:
> > == Series Details ==
> >
> > Series: drm/i915: Cdclk related fixes and polish
> > URL : https://patchwork.freedesktop.org/series/6354/
> > State : warning
> >
> > == Summary ==
> >
> > Series 6354v1 drm/i915: Cdclk related fixes and polish
> > http://patchwork.freedesktop.org/api/1.0/series/6354/revisions/1/mbox/
> >
> > Test drv_module_reload_basic:
> > pass -> SKIP (skl-nuci5)
>
> Reloading i915.ko with
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> module successfully unloaded
> module successfully loaded again
> Reloading i915.ko with inject_load_failure=1
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> Reloading i915.ko with inject_load_failure=2
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> Reloading i915.ko with inject_load_failure=3
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> Reloading i915.ko with inject_load_failure=4
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> Reloading i915.ko with
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
>
> rmmod: ERROR: Module i915 is in use
> rmmod: ERROR: Module i915 is in use
> rmmod: ERROR: Module i915 is in use
> rmmod: ERROR: Module i915 is in use
> rmmod: ERROR: Module i915 is in use
>
> So it managed to unload once, and after that it was no longer possible
> to unload.
>
> [ 436.902443] Console: switching to colour dummy device 80x25
> ...
> [ 439.185816] [drm] Module unloaded
> [ 439.285377] [drm:intel_detect_pch] Found SunrisePoint LP PCH
> ...
> [ 440.671701] [drm] Initialized i915 1.6.0 20160425 for 0000:00:02.0 on minor 0
> [ 440.690772] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
> [ 440.719344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC283: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp
> [ 440.719352] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 440.719356] snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 440.719359] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
> [ 440.719362] snd_hda_codec_realtek hdaudioC0D0: inputs:
> [ 440.719366] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19
> [ 440.798836] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
> [ 440.801278] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
> [ 440.802905] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
> [ 440.804662] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
> [ 440.806351] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
>
> after that nothing related. No real idea who/what was supposedly using
> the module afterwards. Could have been snd-hda I suppose. It doesn't
> seem to leave any trace in dmesg when it unloads, so can't tell from the dmesg.
Oh there was actually
[ 440.936260] Console: switching to colour dummy device 80x25
afterwards, so at least the console unbind worked a second time.
>
> > Test kms_pipe_crc_basic:
> > Subgroup hang-read-crc-pipe-b:
> > incomplete -> PASS (snb-dellxps)
> >
> > bdw-nuci7 total:200 pass:188 dwarn:0 dfail:0 fail:0 skip:12
> > bdw-ultra total:200 pass:175 dwarn:0 dfail:0 fail:0 skip:25
> > bsw-nuc-2 total:199 pass:158 dwarn:0 dfail:0 fail:0 skip:41
> > byt-nuc total:199 pass:158 dwarn:0 dfail:0 fail:0 skip:41
> > hsw-brixbox total:200 pass:174 dwarn:0 dfail:0 fail:0 skip:26
> > skl-i7k-2 total:200 pass:173 dwarn:0 dfail:0 fail:0 skip:27
> > skl-nuci5 total:200 pass:188 dwarn:0 dfail:0 fail:0 skip:12
> > snb-dellxps total:200 pass:158 dwarn:0 dfail:0 fail:0 skip:42
> > snb-x220t total:200 pass:158 dwarn:0 dfail:0 fail:1 skip:41
> >
> > Results at /archive/results/CI_IGT_test/Patchwork_2080/
> >
> > e005db1cb2c60d18abe837ac683d8993ea77b239 drm-intel-nightly: 2016y-04m-26d-12h-51m-57s UTC integration manifest
> > b85d9d7 drm/i915: Fix comments about GMBUSFREQ register
> > f897835 drm/i915: Use cached cdclk value in i915_audio_component_get_cdclk_freq()
> > 4e443d4 drm/i915: Update CDCLK_FREQ register on BDW after changing cdclk frequency
>
> --
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-27 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 16:46 [PATCH 0/3] drm/i915: Cdclk related fixes and polish ville.syrjala
2016-04-26 16:46 ` [PATCH 1/3] drm/i915: Update CDCLK_FREQ register on BDW after changing cdclk frequency ville.syrjala
2016-04-27 8:19 ` Mika Kahola
2016-04-27 8:19 ` Mika Kahola
2016-04-26 16:46 ` [PATCH 2/3] drm/i915: Use cached cdclk value in i915_audio_component_get_cdclk_freq() ville.syrjala
2016-04-27 13:06 ` Mika Kahola
2016-04-26 16:46 ` [PATCH 3/3] drm/i915: Fix comments about GMBUSFREQ register ville.syrjala
2016-04-27 13:30 ` Mika Kahola
2016-04-27 13:56 ` Ville Syrjälä
2016-04-28 18:40 ` Ville Syrjälä
2016-04-27 6:19 ` ✗ Fi.CI.BAT: warning for drm/i915: Cdclk related fixes and polish Patchwork
2016-04-27 17:28 ` Ville Syrjälä
2016-04-27 17:34 ` Ville Syrjälä [this message]
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=20160427173402.GT4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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 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.