From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dave Young" Subject: Re: 2.6.24-rc8-mm1 : net tcp_input.c warnings Date: Tue, 22 Jan 2008 17:18:48 +0800 Message-ID: References: <20080121075548.GA22177@darkstar.te-china.tietoenator.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: LKML , "David Miller" , Netdev , "Andrew Morton" To: "=?ISO-8859-1?Q?Ilpo_J=E4rvinen?=" Return-path: Received: from ag-out-0708.google.com ([72.14.246.240]:50204 "EHLO ag-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756955AbYAVJSu convert rfc822-to-8bit (ORCPT ); Tue, 22 Jan 2008 04:18:50 -0500 Received: by ag-out-0708.google.com with SMTP id 23so1678097agd.10 for ; Tue, 22 Jan 2008 01:18:48 -0800 (PST) In-Reply-To: Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-ID: On Jan 22, 2008 5:09 PM, Dave Young wrote: > > On Jan 22, 2008 12:37 PM, Dave Young wrot= e: > > > > On Jan 22, 2008 5:14 AM, Ilpo J=E4rvinen wrote: > > > > > > On Mon, 21 Jan 2008, Dave Young wrote: > > > > > > > Please see the kernel messages following,(trigged while using s= ome qemu session) > > > > BTW, seems there's some e100 error message as well. > > > > > > > > PCI: Setting latency timer of device 0000:00:1b.0 to 64 > > > > e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI > > > > e100: Copyright(c) 1999-2006 Intel Corporation > > > > ACPI: PCI Interrupt 0000:03:08.0[A] -> GSI 20 (level, low) -> I= RQ 20 > > > > modprobe:2331 conflicting cache attribute efaff000-efb00000 unc= ached<->default > > > > e100: 0000:03:08.0: e100_probe: Cannot map device registers, ab= orting. > > > > ACPI: PCI interrupt for device 0000:03:08.0 disabled > > > > e100: probe of 0000:03:08.0 failed with error -12 > > > > eth0: setting full-duplex. > > > > ------------[ cut here ]------------ > > > > WARNING: at net/ipv4/tcp_input.c:2169 tcp_mark_head_lost+0x121/= 0x150() > > > > Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event= snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss eeprom e100 psmouse s= nd_hda_intel snd_pcm snd_timer btusb rtc_cmos thermal bluetooth rtc_cor= e serio_raw intel_agp button processor sg snd rtc_lib i2c_i801 evdev ag= pgart soundcore dcdbas 3c59x pcspkr snd_page_alloc > > > > Pid: 0, comm: swapper Not tainted 2.6.24-rc8-mm1 #4 > > > > [] ? printk+0x0/0x20 > > > > [] warn_on_slowpath+0x54/0x80 > > > > [] ? ip_finish_output+0x128/0x2e0 > > > > [] ? ip_output+0xe7/0x100 > > > > [] ? ip_local_out+0x18/0x20 > > > > [] ? ip_queue_xmit+0x3dc/0x470 > > > > [] ? _spin_unlock_irqrestore+0x5e/0x70 > > > > [] ? check_pad_bytes+0x61/0x80 > > > > [] tcp_mark_head_lost+0x121/0x150 > > > > [] tcp_update_scoreboard+0x4c/0x170 > > > > [] tcp_fastretrans_alert+0x48a/0x6b0 > > > > [] tcp_ack+0x1b3/0x3a0 > > > > [] tcp_rcv_established+0x3eb/0x710 > > > > [] tcp_v4_do_rcv+0xe5/0x100 > > > > [] tcp_v4_rcv+0x5db/0x660 > > > > > > Doh, once more these S+L things..., the rest are symptom of the f= irst > > > problem. > > > > What is the S+L thing? Could you explain a bit? > > > > > > > > What is strange is that it doesn't show up until now, the last TC= P > > > changes that could have some significance are from early Dec/Nov.= Is > > > there some reason why you haven't seen this before this (e.g., no= t > > > tested with similar cfg or so)? > > > > Hmm, don't know how to answer ... > > > > > > I'm a bit worried about its > > > reproducability if it takes this far to see it... > > > > > It's trigged again in my pc, just while using firefox. Maybe relate to the e100 error, I will apply jiri slaby's e100-iomap-mem-accesses patch to test. > > > > > > > -- > > > i. > > > > > >