Re: PROBLEM: intelfb driver causes trace

Previous thread: commit 9630bdd9 changes behavior of the poweroff - bug? by Michal Hocko on Thursday, April 1, 2010 - 6:39 am. (30 messages)

Next thread: AGP force use of scratch page by Jerome Glisse on Thursday, April 1, 2010 - 7:54 am. (2 messages)
From: Troilo, Domenic
Date: Thursday, April 1, 2010 - 7:52 am

[1.] One line summary of the problem:     intelfb driver causes trace
[2.] Full description of the problem/report: upon boot of system, no
longer see data on console, as the intelfb driver abends
[3.] Keywords (i.e., modules, networking, kernel): modules, framebuffer,
intelfb
[4.] Kernel version (from /proc/version): Linux version 2.6.33.1
(root@upstairs) (gcc version 4.3.2 (Debian 4.3.2-1.1) )
[5.] Output of Oops.. message (if applicable) with symbolic information 
     resolved (see Documentation/oops-tracing.txt)
Mar 31 07:02:04 upstairs kernel: ------------[ cut here ]------------
Mar 31 07:02:04 upstairs kernel: WARNING: at
drivers/video/intelfb/intelfbhw.c:491 intelfbhw_active_pipe+0x52/0x55
[intelfb]()
Mar 31 07:02:04 upstairs kernel: Hardware name: DFDFGDF
Mar 31 07:02:04 upstairs kernel: Modules linked in: intelfb(+)
snd_intel8x0 snd_emu10k1_synth snd_emux_synth snd_seq_virmidi
snd_seq_midi_emul snd_emu10k1 snd_ac97_codec stv0299 ac97_bus
snd_pcm_oss rtl8187 snd_mixer_oss snd_pcm mac80211 led_class cfg80211
snd_util_mem eeprom_93cx6 snd_hwdep ati_remote snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event rtc_cmos rtc_core rtc_lib
snd_seq snd_timer snd_seq_device budget_ci 8250_pnp 8250 ir_common
budget_core serial_core snd dvb_core saa7146 ttpci_eeprom ehci_hcd
ir_core e1000 uhci_hcd parport_pc parport intel_agp usbcore pcspkr
psmouse soundcore i2c_i801 agpgart snd_page_alloc evdev
Mar 31 07:02:04 upstairs kernel: Pid: 1477, comm: modprobe Not tainted
2.6.33.1 #2
Mar 31 07:02:04 upstairs kernel: Call Trace:
Mar 31 07:02:04 upstairs kernel:  [<f87846a9>] ?
intelfbhw_active_pipe+0x52/0x55 [intelfb]
Mar 31 07:02:04 upstairs kernel:  [<f87846a9>] ?
intelfbhw_active_pipe+0x52/0x55 [intelfb]
Mar 31 07:02:04 upstairs kernel:  [<c10290b6>] ?
warn_slowpath_common+0x67/0xb0
Mar 31 07:02:04 upstairs kernel:  [<f87846a9>] ?
intelfbhw_active_pipe+0x52/0x55 [intelfb]
Mar 31 07:02:04 upstairs kernel:  [<c1029112>] ?
warn_slowpath_null+0x13/0x17
Mar 31 07:02:04 ...
From: Jiri Kosina
Date: Friday, April 2, 2010 - 3:02 am

[ adding some appropriate CCs ]



-- 
Jiri Kosina
SUSE Labs, Novell Inc.

--

From: Troilo, Domenic
Date: Sunday, April 4, 2010 - 6:23 am

I have built  Linux version 2.6.34-rc3-git2 and the problem still
occurs:

Here is a cut from syslog and some data before and after:

Apr  4 08:02:50 upstairs kernel: Intel ICH 0000:00:1f.5: setting latency
timer to 64
Apr  4 08:02:50 upstairs kernel: intel8x0_measure_ac97_clock: measured
50251 usecs (2422 samples)
Apr  4 08:02:50 upstairs kernel: intel8x0: clocking to 48000
Apr  4 08:02:50 upstairs kernel: Adding 546204k swap on /dev/sda2.
Priority:-1 extents:1 across:546204k 
Apr  4 08:02:50 upstairs kernel: EXT3-fs (sda1): using internal journal
Apr  4 08:02:50 upstairs kernel: intelfb: intelfb_init
Apr  4 08:02:50 upstairs kernel: intelfb: Framebuffer driver for
Intel(R)
830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM
chipsets
Apr  4 08:02:50 upstairs kernel: intelfb: Version 0.9.6
Apr  4 08:02:50 upstairs kernel: intelfb: intelfb_pci_register
Apr  4 08:02:50 upstairs kernel: intelfb 0000:00:02.0: PCI INT A -> GSI
16 (level, low) -> IRQ 16
Apr  4 08:02:50 upstairs kernel: intelfb: fb aperture:
0xd8000000/0x8000000, MMIO region: 0xd0000000/0x80000
Apr  4 08:02:50 upstairs kernel: intelfb: 00:02.0: Intel(R) 865G,
aperture size 128MB, stolen memory 32636kB
Apr  4 08:02:50 upstairs kernel: intelfb: fb: 0xd8000000(+
0x0)/0x1fdf000 (0xf8780000)
Apr  4 08:02:50 upstairs kernel: intelfb: MMIO: 0xd0000000/0x80000
(0xfd780000)
Apr  4 08:02:50 upstairs kernel: intelfb: ring buffer:
0xdb001000/0x10000 (0xfb781000)
Apr  4 08:02:50 upstairs kernel: intelfb: HW cursor: 0x0/0x0 (0x(null))
(offset 0x0) (phys 0x0)
Apr  4 08:02:50 upstairs kernel: intelfb: options: vram = 4, accel = 1,
hwcursor = 0, fixed = 0, noinit = 0
Apr  4 08:02:50 upstairs kernel: intelfb: options: mode = ""
Apr  4 08:02:50 upstairs kernel: intelfb: intelfb_set_fbinfo
Apr  4 08:02:50 upstairs kernel: intelfb: intelfb_init_var
Apr  4 08:02:50 upstairs kernel: intelfb: intelfb_check_var: accel_flags
is 0
Apr  4 08:02:50 upstairs kernel: intelfb: intelfb_var_to_depth: bpp: 32,
green.length is ...
From: Maciej Rutecki
Date: Wednesday, April 7, 2010 - 1:36 pm

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=15714
for your bug report, please add your address to the CC list in there, thanks!

-- 
Maciej Rutecki
http://www.maciek.unixy.pl
--

Previous thread: commit 9630bdd9 changes behavior of the poweroff - bug? by Michal Hocko on Thursday, April 1, 2010 - 6:39 am. (30 messages)

Next thread: AGP force use of scratch page by Jerome Glisse on Thursday, April 1, 2010 - 7:54 am. (2 messages)