linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Stromsoe <cbs@cts.ucla.edu>
To: Willy Tarreau <willy@w.ods.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
Date: Fri, 6 Jan 2006 13:54:45 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601061352510.24856@potato.cts.ucla.edu> (raw)
In-Reply-To: <20060105054348.GA28125@w.ods.org>

On Thu, 5 Jan 2006, Willy Tarreau wrote:
> On Wed, Jan 04, 2006 at 07:52:36PM -0800, Chris Stromsoe wrote:
> 
>> I booted 2.4.32 with the aic7xxx patch you pointed me at last week. 
>> It's been up for a few hours.  I'll let it run for at least a week or 
>> two and will report back positive or negative results.  After that, 
>> I'll try 2.4.32 with nosmp and acpi=off.
>
> Thanks for your continued feedback, Chris. Your reports are very 
> helpful, they tend to prove that your hardware is OK and that there's a 
> bug in mainline 2.4.32 with SMP+ACPI+aic7xxx enabled. That's already a 
> good piece of information.

After a little more than one day up with 2.4.32 SMP+ACP+aic7xxx, I got 
another bad pmd and an oops this morning at 4:23am.  I'm going to boot 
vanilla 2.4.32 with nosmp and acpi=off.


-Chris

ksymoops 2.4.9 on i686 2.4.32-aic79xx.  Options used
      -V (default)
      -k /proc/ksyms (default)
      -l /proc/modules (default)
      -o /lib/modules/2.4.32-aic79xx/ (default)
      -m /boot/System.map-2.4.32-aic79xx (specified)

Unable to handle kernel paging request at virtual address c2deee80
c025b3d3
*pde = 02c001e3
Oops: 0002
CPU:    2
EIP:    0010:[alloc_skb+275/480]    Not tainted
EFLAGS: 00010282
eax: c2deee80   ebx: e0508880   ecx: 000006bc   edx: 00000680
esi: 000001f0   edi: 00000000   ebp: f6cf7df0   esp: f6cf7ddc
ds: 0018   es: 0018   ss: 0018
Process innfeed (pid: 523, stackpage=f6cf7000)
Stack: 000006bc 000001f0 f3023b80 00000000 d307e000 f6cf7e68 c027cd2b 00000680
        000001f0 000005a8 00000000 f6cf7e54 00000000 00000283 cb3f3000 c025a339
        c8083280 00000000 00000000 c43428a0 f6cf6000 461800d6 00009bc7 00010430 
Call Trace:    [tcp_sendmsg+2619/4512] [sock_wfree+73/80] [inet_sendmsg+65/80] [sock_sendmsg+102/176] [sock_readv_writev+116/176]
Code: c7 00 01 00 00 00 8b 83 8c 00 00 00 c7 40 04 00 00 00 00 8b 
Using defaults from ksymoops -t elf32-i386 -a i386


>>eax; c2deee80 <_end+2a0b300/3864e4e0>
>>ebx; e0508880 <_end+20124d00/3864e4e0>
>>ebp; f6cf7df0 <_end+36914270/3864e4e0>
>>esp; f6cf7ddc <_end+3691425c/3864e4e0>

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
    0:   c7 00 01 00 00 00         movl   $0x1,(%eax)
Code;  00000006 Before first symbol
    6:   8b 83 8c 00 00 00         mov    0x8c(%ebx),%eax
Code;  0000000c Before first symbol
    c:   c7 40 04 00 00 00 00      movl   $0x0,0x4(%eax)
Code;  00000013 Before first symbol
   13:   8b 00                     mov    (%eax),%eax


  reply	other threads:[~2006-01-06 21:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 16:58 bad pmd filemap.c, oops; 2.4.30 and 2.4.32 Chris Stromsoe
2005-12-28  0:10 ` Marcelo Tosatti
2005-12-29  2:52   ` Chris Stromsoe
2005-12-29  5:12     ` Willy Tarreau
2005-12-29  9:33       ` Chris Stromsoe
2005-12-29 10:08         ` Willy Tarreau
2005-12-29 12:01           ` Chris Stromsoe
2005-12-31  0:12     ` Chris Stromsoe
2005-12-31  1:48       ` Chris Stromsoe
2005-12-31  4:00         ` Chris Stromsoe
2005-12-31  7:25           ` Willy Tarreau
2005-12-31 11:06             ` Chris Stromsoe
2005-12-31  7:12         ` Willy Tarreau
2005-12-31 10:39           ` Chris Stromsoe
2005-12-31 10:56             ` Willy Tarreau
2005-12-31 12:08         ` Alan Cox
2005-12-31 13:01           ` Willy Tarreau
2006-01-05  3:52             ` Chris Stromsoe
2006-01-05  5:43               ` Willy Tarreau
2006-01-06 21:54                 ` Chris Stromsoe [this message]
2006-01-06 22:14                   ` Chris Stromsoe
2006-01-06 22:16                     ` Chris Stromsoe
2006-01-07  9:19                     ` Roberto Nibali
2006-01-09 18:28                       ` Chris Stromsoe
2006-01-09 20:16                         ` Roberto Nibali
2006-01-09 20:22                           ` Chris Stromsoe
2006-01-09 22:22                             ` Roberto Nibali
2006-01-10  0:59                               ` Chris Stromsoe
2006-01-15 11:29                                 ` Chris Stromsoe
2006-01-15 12:12                                   ` Willy Tarreau
2006-01-15 21:18                                     ` Chris Stromsoe
2006-01-15 22:38                                   ` Chris Stromsoe
2006-01-15 22:46                                     ` Willy TARREAU
2006-01-15 22:54                                       ` Chris Stromsoe
2006-01-16 20:52                                         ` Roberto Nibali
2006-01-16 21:32                                           ` Chris Stromsoe
2006-02-08  6:32                                         ` Chris Stromsoe
2006-02-08  6:37                                           ` Willy Tarreau
2006-01-08  9:45                   ` Willy Tarreau
2006-01-09 18:33                     ` Chris Stromsoe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0601061352510.24856@potato.cts.ucla.edu \
    --to=cbs@cts.ucla.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=willy@w.ods.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).