From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: 2.6.38-rc5 tcp_connect oops: EIP = 0x0 Date: Fri, 18 Feb 2011 07:32:15 +0100 Message-ID: <1298010735.2642.9.camel@edumazet-laptop> References: <20110218050321.10415.qmail@science.horizon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, netdev To: George Spelvin Return-path: In-Reply-To: <20110218050321.10415.qmail@science.horizon.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Le vendredi 18 f=C3=A9vrier 2011 =C3=A0 00:03 -0500, George Spelvin a =C3= =A9crit : > But wonder of wonders, kernel mode switching worked so I got to see t= he > oops on the text-mode console. It happened just as I tried to ssh ou= t. >=20 CC netdev (removed linux-netdev) I'll take a look this morning, thanks for the report. > It's a Core 2 duo laptop (Dell E1405), 2 GB RAM, running a 32-bit ker= nel. > It's worth noting that I was using wired internet (b44 driver) and > not wireless. >=20 > I've been having a lot of weird lockups with 2.6.38-rcX, quite a chan= ge > from the very stable 2.6.36, but this is the first time I booted -rc5= =2E > Also, the symptoms are very different; before the lockup did not seen > correlated with any particular activity, but the "lockup" was more li= ke > something getting wedged in the kernel that more and more tasks would > get stuck on until everything stopped responding. >=20 > I should mention that this is transcribed by hand from the screen. > Oh, and also, it is far from the first time I ran ssh this boot. > (I re-tested it ater rebooting, just to be sure. Not a consistent > crash.) >=20 > Anyway, jumping to address 0 looks "interesting", so it seems worth r= eporting. >=20 > BUG: unable to handle kernel NULL pointer dereference at (null) > IP: [< (null)>] (null) > *pde =3D 00000000 > Oops: 0000 [#1] SMP > last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0= :0/0:0:0:0/block/sda/uevent > Modules linked in: rfcomm btusb sco l2cap crc16 bluetooth b43 mac8021= 1 cfg80211 [last unloaded: sha256_generic] >=20 > Pid: 12178, comm: ssh Not tainted 2.6.38-rc5 #227 Dell Inc. MXC061 = /0MG532 > EIP: 0060:[<00000000>] EFLAGS: 0021246 CPU: 0 > EIP is at 0x0 > EAX: f5947e00 EBX: f5982f80 ECX: 00000024 EDX: c148fe00 > ESI: f5947e00 EDI: ebf29e54 EBP: ebf29ee0 ESP: ebf29dd0 > DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 > Process ssh (pid: 12178, ti=3Debf28000 task=3Debefc6c0 task.ti =3D eb= ef28000) > Stack: > c12c83ea 07e2427d 02000000 7b018f79 c117b827 0b996609 7b018f79 5f5f6= 644 > f5982f80 00000000 ebf29e58 ebf29ee0 c12cc0e0 00001600 00000000 00000= 001 > 03641600 00000000 00000000 00000000 00000000 036423c0 3e6423c0 00000= 000 > Call Trace: > [] ? tcp_connect+0xdd/0x3fd > [] ? secure_tcp_sequence_number+0x4f/0x65 > [] ? tcp_v4_connect+0x3c1/0x417 > [] ? inet_stream_connect+0x88/0x1fc > [] ? _copy_from_user+0x2b/0x10e > [] ? sys_connect+0x70/0x98 > [] ? get_empty_filp+0x9f/0x121 > [] ? alloc_file+0xf/0x85 > [] ? sock_alloc_file+0x97/0xeb > [] ? fd_install+0x1b/0x38 > [] ? sock_map_fd+0x1b/0x20 > [] ? sys_socketcall+0x9d/0x291 > [] ? sysenter_do_call+0x12/0x26 > Code: Bad EIP value > EIP: [<00000000>] 0x0 SS:ESP 0068:ebf29dd0 > CR2: 0000000000000000