I'm planning on submitting a bug, but thought I'd poll the population
first since I'm having trouble putting together a good bug report
(solid lockup).

It's been a while since I updated the kernel on my T61, was at
hardened-sources-3.2.1. Updating to 3.3.6 this week produced a viable
kernel, but when X starts the system locks hard. In trying different
kernels I've found that the regression is somewhere between the
3.2.2-r1 and 3.2.11 versions in the mainstream portage tree. The
following is the only dump I've been able to capture, as about 9/10
the system locks beyond SSH recovery; apologies for the zram/zcache
taint, it was captured before I started debugging and eliminated
those. It is, however, consistent with all subsequent ones I've seen
(same IP, same call trace). I do notice that 'make oldconfig' in the
3.2.11 tree with the config from 3.2.2-r1 comes up with a single new
option, CONFIG_KCOPY. Thoughts?

BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
IP: [<ffffffff81278070>] i915_gem_execbuffer_reserve.clone.10+0x14/0x330
PGD 7660e000
Oops: 0000 [#1] SMP
CPU 1
Modules linked in: af_packet xt_tcpudp nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables
ip6table_filter ip6_tables x_tables ipv6 xfs zcache(C) zram(C) loop
fuse fat kvm_intel kvm isofs tun snd_hda_codec_analog pcmcia arc4
sr_mod cdrom sdhci_pci firewire_ohci pcspkr i2c_i801 sdhci
yenta_socket mmc_core firewire_core iwl4965 pcmcia_rsrc pcmcia_core
crc_itu_t iwl_legacy snd_hda_intel mac80211 uhci_hcd ehci_hcd
snd_hda_codec cfg80211 snd_hwdep snd_pcm usbcore snd_page_alloc e1000e
usb_common snd_timer thinkpad_acpi nvram hwmon snd tpm_tis soundcore
wmi tpm rfkill battery ac tpm_bios evdev unix

Pid: 3272, comm: X Tainted: G C 3.2.11-hardened #2 LENOVO
7659C29/7659C29
RIP: 0010:[<ffffffff81278070>] [<ffffffff81278070>]
i915_gem_execbuffer_reserve.clone.10+0x14/0x330
RSP: 0018:ffff880075421b58 EFLAGS: 00010292
RAX: ffff88007584c200 RBX: ffff880075421c88 RCX: ffff880075421c88
RDX: ffff880075421c88 RSI: ffff880075421c88 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff88007671b070 R09: ffff8800756c4300
R10: 0000000000000002 R11: 0000000000000000 R12: ffff880075421da8
R13: ffff880074f39000 R14: ffff880075f86960 R15: 0000000000000000
FS: 0000032c1cd63880(0000) GS:ffff88007d500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000018 CR3: 00000000013aa000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process X (pid: 3272, threadinfo ffff8800754b2028, task ffff8800754b1c00)
Stack:
0000000000000020 ffff880075f869a0 0000007831f934b0 ffffffff81277d71
ffff88007a29cc00 0000000000000000 0000000000000000 ffff880075421da8
ffff880074f39000 ffff880075f86960 0000000000000002 ffffffff81278d7c
Call Trace:
[<ffffffff81277d71>] ? copy_from_user+0xf3/0x134
[<ffffffff81278d7c>] ? i915_gem_do_execbuffer.clone.12+0x9de/0x1256
[<ffffffff81279a24>] ? i915_gem_execbuffer2+0xe2/0x256
[<ffffffff810aebdd>] ? handle_pte_fault+0x61f/0x67f
[<ffffffff81254463>] ? drm_ioctl+0x39a/0x5c4
[<ffffffff81279942>] ? i915_gem_execbuffer+0x34e/0x34e
[<ffffffff810de7a6>] ? do_vfs_ioctl+0x62d/0x6d8
[<ffffffff8139efa0>] ? page_fault+0x30/0x40
[<ffffffff8139ed6e>] ? retint_swapgs+0xc/0x12
[<ffffffff810de88d>] ? sys_ioctl+0x3c/0x5f
[<ffffffff8139f47b>] ? system_call_fastpath+0x18/0x1d
Code: 48 39 c2 76 09 48 83 c4 08 e9 52 e2 e4 ff 48 83 c4 08 e9 71 1d
e4 ff 41 57 49 89 ff 41 56 41 55 41 54 55 53 48 89 f3 48 83 ec 28 <48>
8b 47 18 48 8b 80 30 03 00 00 48 8b 40 08 80 38 03 48 8d 44
RIP [<ffffffff81278070>] i915_gem_execbuffer_reserve.clone.10+0x14/0x330
RSP <ffff880075421b58>
CR2: 0000000000000018

On Wednesday 16 May 2012 10:54:12 RB wrote:
> I'm planning on submitting a bug, but thought I'd poll the population
> first since I'm having trouble putting together a good bug report
> (solid lockup).
>
> It's been a while since I updated the kernel on my T61, was at
> hardened-sources-3.2.1. Updating to 3.3.6 this week produced a viable
> kernel, but when X starts the system locks hard. In trying different
> kernels I've found that the regression is somewhere between the
> 3.2.2-r1 and 3.2.11 versions in the mainstream portage tree.

I'm running 3.2.12 and all is ok here. How about that version?
--
Agostino Sarubbo ago -at- gentoo.org
Gentoo/AMD64 Arch Security Liaison
GPG: 0x7CD2DC5D

On Wed, May 16, 2012 at 11:05 AM, Agostino Sarubbo <ago@gentoo.org> wrote:
> I'm running 3.2.12 and all is ok here. How about that version?

Unfortunately not, just tested hardened-sources-3.2.12 and it
exhibited the same behavior, if slightly more graceful than 3.2.11
(part of the oops got printed to the SSH terminal before locking
hard).

I don't like submitting bugs without having already determiend the
root cause, but I might have to make an exception in this case.

On Wed, May 16, 2012 at 9:06 PM, RB <aoz.syn@gmail.com> wrote:
> I don't like submitting bugs without having already determiend the
> root cause, but I might have to make an exception in this case.

Hi, you might want to try booting Liberté Linux 2011.2 for an
independent verification, since it uses hardened kernel 3.2.11, and is
very homogeneous (i.e., everything is built with the same hardened
gcc, there are no PaX markings (except /bin/fuser, of course, #394443,
*cough*), etc.). Add "root" to the kernel parameters to enable root
password: "liberte". Logging is done with metalog, so the logs are in
/var/log/everything. Kernel config:
https://github.com/mkdesu/liberte/blob/2012.1/src/root/config/linux-3.2.11-hardened.config.
Most of the packages are latest stable x86 (no amd64 build),
xf86-video-intel is 2.17.0-r3. See http://dee.su/liberte and
http://dee.su/liberte-install, you only need ~200 MiB free space on a
USB key. FWIW, I did not receive any report about issues with Intel
video cards so far.

--
Maxim Kammerer
Liberté Linux (discussion / support: http://dee.su/liberte-contribute)

On Wed, May 16, 2012 at 10:35 PM, Maxim Kammerer <mk@dee.su> wrote:
> Hi, you might want to try booting Liberté Linux 2011.2 for an
Sorry, meant 2012.1 — the latest release.

--
Maxim Kammerer
Liberté Linux (discussion / support: http://dee.su/liberte-contribute)

On Wed, May 16, 2012 at 1:42 PM, Maxim Kammerer <mk@dee.su> wrote:
> Sorry, meant 2012.1 — the latest release.

Well that's both encouraging and discouraging. It works, which means
there's something wonky with my kernel config or my environment, even
though I've not changed either. Will report back when I find what it
is - will start a 3.3.6 oldconfig from liberte's and go from there.

Regarding #394443 you find a fix there. No need for marking on x86.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057

2012.Május 16.(Sze) 21:35 idÅ‘pontban Maxim Kammerer ezt Ã*rta:
> On Wed, May 16, 2012 at 9:06 PM, RB <aoz.syn@gmail.com> wrote:
>> I don't like submitting bugs without having already determiend the
>> root cause, but I might have to make an exception in this case.
>
> Hi, you might want to try booting Liberté Linux 2011.2 for an
> independent verification, since it uses hardened kernel 3.2.11, and is
> very homogeneous (i.e., everything is built with the same hardened
> gcc, there are no PaX markings (except /bin/fuser, of course, #394443,
> *cough*), etc.). Add "root" to the kernel parameters to enable root
> password: "liberte". Logging is done with metalog, so the logs are in
> /var/log/everything. Kernel config:
> https://github.com/mkdesu/liberte/blob/2012.1/src/root/config/linux-3.2.11-hardened.config.
> Most of the packages are latest stable x86 (no amd64 build),
> xf86-video-intel is 2.17.0-r3. See http://dee.su/liberte and
> http://dee.su/liberte-install, you only need ~200 MiB free space on a
> USB key. FWIW, I did not receive any report about issues with Intel
> video cards so far.
>
> --
> Maxim Kammerer
> Liberté Linux (discussion / support: http://dee.su/liberte-contribute)
>
>

On Wed, May 16, 2012 at 3:54 PM, Torbjörn Svensson
<azoff@svenskalinuxforeningen.se> wrote:
> Just a thought, have you tried to rebuild x11-drivers/*, most notably
> x11-drivers/xf86-video-intel? I've had some strange craches and even
> lockups when the X11 driver somehow was out of sync with the running kernel.

I have. In fact, I've gone so far as to do the following:

# emerge -v1 $(qlist -ISLC -c x11)

What's the difference between your kernel konfig and Liberté Linux
2012.1's kernel konfig? Because you told it worked for you.

Regards:
Dw.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057

2012.Május 17.(Cs) 00:41 idÅ‘pontban RB ezt Ã*rta:
> On Wed, May 16, 2012 at 3:54 PM, Torbjörn Svensson
> <azoff@svenskalinuxforeningen.se> wrote:
>> Just a thought, have you tried to rebuild x11-drivers/*, most notably
>> x11-drivers/xf86-video-intel? I've had some strange craches and even
>> lockups when the X11 driver somehow was out of sync with the running
>> kernel.
>
> I have. In fact, I've gone so far as to do the following:
>
> # emerge -v1 $(qlist -ISLC -c x11)
>
>

On Wed, May 16, 2012 at 5:40 PM, "Tóth Attila" <atoth@atoth.sote.hu> wrote:
> What's the difference between your kernel konfig and Liberté Linux
> 2012.1's kernel konfig? Because you told it worked for you.

Quite a lot, not the least of which theirs is a 32-bit kernel and
mine's 64-bit. The 'diff -u' between them is 5k lines long, and
instead of going through that line-by-line my intent is to take the
quickest path first: start with Liberté's config on 3.3.6 and start
adding my own settings until it breaks. Plus, this "old" machine is
slow, it takes at least 30 minutes to compile a kernel, and given a
day job it's going to take a little while to test.