Issue 96154 in chromium: Google-Chrome causes kernel panic after debian update.
chro...@googlecode.com
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug Pri-2
New issue 96154 by parker.s...@gmail.com: Google-Chrome causes kernel panic
after debian update.
http://code.google.com/p/chromium/issues/detail?id=96154
Chrome Version : 14.0.835.159 (Official Build 100066) beta
OS Version: Linux 2.6.32-5-686 #1 SMP Fri Aug 26 09:15:47 UTC 2011 i686
URLs (if applicable) : www.google.com
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Open up Google Chrome
2. Browse to www.google.com
3. Search for something
What is the expected result?
The search comes back
What happens instead?
The search loads, and then there is a Kernel panic
Please provide any additional information below. Attach a screenshot if
possible.
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.057740] Oops: 0000 [#1] SMP
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.057746] last sysfs file:
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.057940] Process chrome (pid: 2982, ti=f398c000 task=f67f0440
task.ti=f398c000)
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.057944] Stack:
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.057983] Call Trace:
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.058034] Code: f0 ff 08 0f 94 c2 84 d2 74 09 8b 44 24 08 e8
12 b1 f4 ff 83 c4 38 89 f8 5b 5e 5f 5d c3 56 85 d2 53 8b 70 40 74 16 3b 56
08 74 11 <8b> 1a 8d 43 34 e8 1d 20 f6 ff 89 d8 e8 03 98 f4 ff 8b 4e 04 85
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.058100] EIP: [<c10e509f>] m_stop+0xe/0x3f SS:ESP
0068:f398df3c
Message from syslogd at Sep 10 11:06:59 ...
kernel:[ 1389.058109] CR2: 00000000fffffff3
This happened after installing these debian updates:
Start-Date: 2011-09-09 11:34:33
Upgrade: linux-image-2.6.32-5-686:i386 (2.6.32-35, 2.6.32-35squeeze1),
linux-libc-dev:i386 (2.6.32-35, 2.6.32-35squeeze1), linux-base:i386
(2.6.32-35, 2.6.32-35squeeze1)
End-Date: 2011-09-09 11:35:24
chro...@googlecode.com
Comment #1 on issue 96154 by jgrav...@gmail.com: Google-Chrome causes
http://code.google.com/p/chromium/issues/detail?id=96154
got same problem here on AMD/BRAZOS platform
Linux version 2.6.32-5-amd64 #1 SMP Wed Aug 31 16:50:35 UTC 2011 x86_64
GNU/Linux
Google Chrome 15.0.874.5 dev
only since last kernel update // only with chrome (no problem with
iceweasel at this point)
from syslog :
Sep 10 22:18:05 caboose kernel: [16230.135832] BUG: unable to handle kernel
paging request at fffffffffffffff3
Sep 10 22:18:05 caboose kernel: [16230.135843] IP: [<ffffffff8112f98d>]
m_stop+0x15/0x4c
Sep 10 22:18:05 caboose kernel: [16230.135857] PGD 1003067 PUD 1004067 PMD 0
Sep 10 22:18:05 caboose kernel: [16230.135864] Oops: 0000 [#2] SMP
Sep 10 22:18:05 caboose kernel: [16230.135868] last sysfs file:
/sys/devices/virtual/dmi/id/bios_vendor
Sep 10 22:18:05 caboose kernel: [16230.135874] CPU 1
Sep 10 22:18:05 caboose kernel: [16230.135877] Modules linked in:
cpufreq_conservative cpufreq_stats cpufreq_userspace cpufreq_powersave
binfmt_misc fuse ext3 jbd loop firewire_sbp2 snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer
snd_seq_device i2c_piix4 parport_pc pcspkr parport evdev snd i2c_core
fglrx(P) soundcore button snd_page_alloc processor ext2 mbcache sg sr_mod
sd_mod crc_t10dif cdrom usbhid ata_generic hid firewire_ohci ohci_hcd ahci
firewire_core pata_atiixp thermal r8169 crc_itu_t mii libata ehci_hcd
scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan]
Sep 10 22:18:05 caboose kernel: [16230.135944] Pid: 3222, comm: chrome
Tainted: P D 2.6.32-5-amd64 #1 System Product Name
Sep 10 22:18:05 caboose kernel: [16230.135948] RIP:
0010:[<ffffffff8112f98d>] [<ffffffff8112f98d>] m_stop+0x15/0x4c
Sep 10 22:18:05 caboose kernel: [16230.135956] RSP: 0018:ffff8801edf67e88
EFLAGS: 00010286
Sep 10 22:18:05 caboose kernel: [16230.135960] RAX: ffffffff8131fab0 RBX:
ffff8801edf67ed8 RCX: 000000d0e5a9c000
Sep 10 22:18:05 caboose kernel: [16230.135964] RDX: 00000000ffffff00 RSI:
fffffffffffffff3 RDI: ffff8801e2bf6a00
Sep 10 22:18:05 caboose kernel: [16230.135968] RBP: ffff8801e5562f40 R08:
ffff88023b669180 R09: 0000000000000002
Sep 10 22:18:05 caboose kernel: [16230.135972] R10: 0000000000000022 R11:
ffffffff811516f3 R12: fffffffffffffff3
Sep 10 22:18:05 caboose kernel: [16230.135976] R13: 00000000fffffff3 R14:
0000000000000000 R15: 0000000000010000
Sep 10 22:18:05 caboose kernel: [16230.135981] FS: 00007fe905065980(0000)
GS:ffff880008700000(0000) knlGS:0000000000000000
Sep 10 22:18:05 caboose kernel: [16230.135985] CS: 0010 DS: 0000 ES: 0000
CR0: 0000000080050033
Sep 10 22:18:05 caboose kernel: [16230.135989] CR2: fffffffffffffff3 CR3:
00000001eea77000 CR4: 00000000000006e0
Sep 10 22:18:05 caboose kernel: [16230.135993] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Sep 10 22:18:05 caboose kernel: [16230.135997] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Sep 10 22:18:05 caboose kernel: [16230.136001] Process chrome (pid: 3222,
threadinfo ffff8801edf66000, task ffff88021e48dbd0)
Sep 10 22:18:05 caboose kernel: [16230.136005] Stack:
Sep 10 22:18:05 caboose kernel: [16230.136007] 0000000000001000
ffff8801edf67ed8 ffff8801e2bf6a00 ffffffff81105aa9
Sep 10 22:18:05 caboose kernel: [16230.136013] <0> 0000000000001000
ffff8801edf67f50 00007fff56f8cf60 ffff8802222f2480
Sep 10 22:18:05 caboose kernel: [16230.136020] <0> ffff8801e2bf6a38
0000000000000001 0000000000000000 0000000000010000
Sep 10 22:18:05 caboose kernel: [16230.136027] Call Trace:
Sep 10 22:18:05 caboose kernel: [16230.136035] [<ffffffff81105aa9>] ?
seq_read+0x269/0x388
Sep 10 22:18:05 caboose kernel: [16230.136043] [<ffffffff810ef510>] ?
vfs_read+0xa6/0xff
Sep 10 22:18:05 caboose kernel: [16230.136048] [<ffffffff810ef625>] ?
sys_read+0x45/0x6e
Sep 10 22:18:05 caboose kernel: [16230.136055] [<ffffffff81010b42>] ?
system_call_fastpath+0x16/0x1b
Sep 10 22:18:05 caboose kernel: [16230.136058] Code: 48 89 df e8 e3 c2 f1
ff 31 c0 40 84 ed 49 0f 45 c4 5b 5d 41 5c c3 55 53 48 83 ec 08 48 85 f6 48
8b 6f 60 74 1a 48 3b 75 10 74 14 <48> 8b 1e 48 8d 7b 60 e8 dd 86 f3 ff 48
89 df e8 ac c2 f1 ff 48
Sep 10 22:18:05 caboose kernel: [16230.136106] RIP [<ffffffff8112f98d>]
m_stop+0x15/0x4c
Sep 10 22:18:05 caboose kernel: [16230.136112] RSP <ffff8801edf67e88>
Sep 10 22:18:05 caboose kernel: [16230.136114] CR2: fffffffffffffff3
Sep 10 22:18:05 caboose kernel: [16230.136119] ---[ end trace
4b547e98dbb0eac2 ]---
chro...@googlecode.com
Labels: Action-FeedbackNeeded
Comment #3 on issue 96154 by the...@chromium.org: Google-Chrome causes
kernel panic after debian update.
http://code.google.com/p/chromium/issues/detail?id=96154
If you run with --disable-seccomp-sandbox --no-sandbox, do you still get
the kernel panic? If not, can you figure out which of the two flags
prevents the kernel panic?
chro...@googlecode.com
Comment #4 on issue 96154 by parker.s...@gmail.com: Google-Chrome causes
http://code.google.com/p/chromium/issues/detail?id=96154
I don't know, Debian subsequently released another release that fixed the
problem.
chro...@googlecode.com
Status: WontFix
Comment #5 on issue 96154 by the...@chromium.org: Google-Chrome causes
kernel panic after debian update.
http://code.google.com/p/chromium/issues/detail?id=96154
Closing the bug report then.