chrome crashing kernel in latest update

i’ve been running on tumbleweed for a while now, today i installed some updates and now every time i try to start chrome it runs for about a minute and then the kernel crashes, X drops me out to a console with the image below. I can get back into X by doing an alt-f7 but chrome pretty much is gimped and won’t load most pages. I thought one of the updates i installed was a kernel update. is there any way to revert to an earlier tumbleweed kernel? all i see in versions in software manager are the current tumbleweed one, and a bunch of 2.6.37 ones from the opensuse 11.4 branch.

Here is the image i get on crash and the trace from /var/log/messages

https://lh6.googleusercontent.com/_BYlYZfrDE8o/Tc11VItceuI/AAAAAAAABQ8/1DceBpdHILI/s640/IMAG0056.jpg

May 13 17:07:46 linux-6yv4 kernel:   190.161012] 
May 13 17:07:46 linux-6yv4 kernel:   190.161015] Pid: 3145, comm: chrome Not tainted 2.6.38.6-26-desktop #1 Dell Inc. Latitude E4310/012JJ4
May 13 17:07:46 linux-6yv4 kernel:   190.161021] RIP: 0010:<ffffffff811b238c>]  <ffffffff811b238c>] vma_stop+0xc/0x30
May 13 17:07:46 linux-6yv4 kernel:   190.161026] RSP: 0018:ffff880135f9de78  EFLAGS: 00010213
May 13 17:07:46 linux-6yv4 kernel:   190.161029] RAX: 00000000fffffff3 RBX: ffff8801aae20fa0 RCX: 0000000000000013
May 13 17:07:46 linux-6yv4 kernel:   190.161033] RDX: ffffffff81627f00 RSI: fffffffffffffff3 RDI: ffff8801aae20fa0
May 13 17:07:46 linux-6yv4 kernel:   190.161036] RBP: ffff88014e5825c0 R08: ffff8801d2e22240 R09: 0000000000000000
May 13 17:07:46 linux-6yv4 kernel:   190.161039] R10: 0000000000000022 R11: 0000000000000293 R12: fffffffffffffff3
May 13 17:07:46 linux-6yv4 kernel:   190.161043] R13: ffff88014e70ef00 R14: ffff880135f9ded0 R15: 0000000000000000
May 13 17:07:46 linux-6yv4 kernel:   190.161046] FS:  00007f52f1ccc700(0000) GS:ffff8800db440000(0000) knlGS:0000000000000000
May 13 17:07:46 linux-6yv4 kernel:   190.161050] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 13 17:07:46 linux-6yv4 kernel:   190.161053] CR2: fffffffffffffff3 CR3: 00000001f3dc5000 CR4: 00000000000006e0
May 13 17:07:46 linux-6yv4 kernel:   190.161057] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 13 17:07:46 linux-6yv4 kernel:   190.161060] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 13 17:07:46 linux-6yv4 kernel:   190.161064] Process chrome (pid: 3145, threadinfo ffff880135f9c000, task ffff8801d2d36180)
May 13 17:07:46 linux-6yv4 kernel:   190.161067] Stack:
May 13 17:07:46 linux-6yv4 kernel:   190.161069]  ffff8801aae20fa0 ffffffff811b317d ffff88014e70ef00 ffffffff81178c49
May 13 17:07:46 linux-6yv4 kernel:   190.161074]  0000000000000000 00000000fffffff3 0000000000010000 ffff880135f9df58
May 13 17:07:46 linux-6yv4 kernel:   190.161079]  ffff88014e5825f8 00007f52f1cbb0a0 ffff88014e70ef00 0000000000000000
May 13 17:07:46 linux-6yv4 kernel:   190.161084] Call Trace:
May 13 17:07:46 linux-6yv4 kernel:   190.161093]  <ffffffff811b317d>] m_stop+0xd/0x30
May 13 17:07:46 linux-6yv4 kernel:   190.161099]  <ffffffff81178c49>] seq_read+0x1f9/0x3c0
May 13 17:07:46 linux-6yv4 kernel:   190.161107]  <ffffffff811581d3>] vfs_read+0xc3/0x180
May 13 17:07:46 linux-6yv4 kernel:   190.161113]  <ffffffff811582de>] sys_read+0x4e/0x90
May 13 17:07:46 linux-6yv4 kernel:   190.161120]  <ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
May 13 17:07:46 linux-6yv4 kernel:   190.161126]  <00007f52f7ece0ad>] 0x7f52f7ece0ad
May 13 17:07:46 linux-6yv4 kernel:   190.161129] Code: 00 c3 0f 1f 44 00 00 b8 01 00 00 00 c3 66 90 31 c0 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 85 f6 53 74 22 48 39 77 10 74 1c <48> 8b 1e 48 8d 7b 60 e8 f8 ed ec ff 48 89 df 5b e9 2f 5b ea ff 
May 13 17:07:46 linux-6yv4 kernel:   190.161156] RIP  <ffffffff811b238c>] vma_stop+0xc/0x30
May 13 17:07:46 linux-6yv4 kernel:   190.161159]  RSP <ffff880135f9de78>
May 13 17:07:46 linux-6yv4 kernel:   190.161161] CR2: fffffffffffffff3
May 13 17:07:46 linux-6yv4 kernel:   190.275195] --- end trace ec5991ae068893a4 ]---

I have completed an update using tumbleweed today - which included a kernel update.

Chrome is working for me - although I see that there is an error message in var/log/warn - similiar to yours:-

Pid: 11406, comm: chrome Tainted:

I am just rolling back to the latest kernel packages in YOU to see if that solves it and as confirmation that the kernel update has caused the problem.

It is the kernel update causing the problem with chrome.

I just rolled back to the kernel from YOU 2.6.37.6-0.5.1 and there are no error messages for chrome in var/log/warn and it works fine.