Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)
> On 2011-09-10, Camaleón <email@example.com> wrote:
> > On Sat, 10 Sep 2011 09:19:52 +0000, Curt wrote:
> >> After installing a kernel security update yesterday, I'm getting random
> >> kernel oops when using Google Chrome. Anybody else seeing this
> >> phenomenon?
> > Yes, a couple of users in the Spanish mailing list are also reporting
> > this.
> > Can you explain what is the current issue? I mean, does the "oops" happen
> > when launching the browser? What's the content of the "oops"? I could not
> No, thus the word "random." Appears to happen randomly (without
> predicability) while surfing, effectively crashing the browser.
I am also seeing this, with Google Chrome Beta 14.0.835.159-r100066,
and the most recent kernel update, 2.6.32-35squeeze1, on 32-bit.
I am running some fairly flash-heavy stuff, and weirdly in one
instance, the browser reported that a page had become unresponsive
when the flash content on that page was still fine -- then the
browser exited, and I saw the kernel messages.
My kern.log entries are similar to those below, they begin with
"unable to handle kernel paging request at fffffff3" (I am on a 32-bit
Anecdotally, it seems that it doesn't happen if the browser is
the only thing running on the desktop, but I don't have a lot of data
on that, I only did the kernel update a few hours ago.
> Sep 9 17:40:12 einstein kernel: [22866.749031] BUG: unable to handle
> kernel paging request at fffffffffff ffff3
> Sep 9 17:40:12 einstein kernel: [22866.749043] IP: [<ffffffff8112f98d>]
> m_stop+0x15/0x4c Sep 9 17:40:12 einstein kernel: [22866.749060] PGD
> 1003067 PUD 1004067 PMD 0 Sep 9 17:40:12 einstein kernel: [22866.749070]
> Oops: 0000 [#1] SMP Sep 9 17:40:12 einstein kernel: [22866.749076] last
> sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scal ing_cur_freq
> Sep 9 17:40:12 einstein kernel: [22866.749083] CPU 0
> Sep 9 17:40:12 einstein kernel: [22866.749087] Modules linked in:
> powernow_k8 cpufreq_conservative cpufre q_stats cpufreq_powersave
> cpufreq_userspace parport_pc ppdev lp parport binfmt_misc fuse
> firewire_sbp2 loo p snd_hda_codec_realtek snd_hda_intel snd_hda_codec
> snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_mi di snd_rawmidi
> snd_seq_midi_event snd_seq snd_timer snd_seq_device acer_wmi snd rfkill
> led_class soundcore wmi psmouse i2c_nforce2 nvidia(P) k10temp pcspkr
> i2c_core edac_core evdev snd_page_alloc edac_mce_amd ser io_raw video
> output button processor ext3 jbd mbcache sg sd_mod sr_mod cdrom crc_t10dif
> usbhid ata_generic usb_storage hid ohci_hcd pata_amd ahci firewire_ohci
> firewire_core fan crc_itu_t libata ehci_hcd scsi_mod thermal thermal_sys
> forcedeth usbcore nls_base [last unloaded: scsi_wait_scan] Sep 9 17:40:12
> einstein kernel: [22866.749200] Pid: 2413, comm: chrome Tainted: P
> 2.6.32-5-amd6 4 #1 Aspire X1301
> > (searching...)
> > This can be related:
> > http://www.google.vu/support/forum/p/Chrome/thread?tid=51f63d2301865ceb&h
> > l=en
> > Which fianlly points to this:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966
> That's it. I guess the "kernel team" is working on it, God bless 'em.
Andrew Reid / firstname.lastname@example.org