All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@drugphish.ch>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: Willy Tarreau <willy@w.ods.org>,
	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: Sat, 07 Jan 2006 10:19:01 +0100	[thread overview]
Message-ID: <43BF8785.2010703@drugphish.ch> (raw)
In-Reply-To: <Pine.LNX.4.64.0601061411350.24856@potato.cts.ucla.edu>

>> 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.

Your oops does not make much sense, could you enable following, please:

CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SLAB=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_FRAME_POINTER=y

> booting with "nosmp acpi=off" did not help.  The box hung as before, at

Could you boot with pci=noacpi and report again? The difference is that 
ACPI will still be used but not for IRQ routing. I have a few boxes out 
with 2.4.x kernels and Adaptec HBAs that need this to work reliably.

> hda: TEAC CD-ROM CD-224E, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: attached ide-cdrom driver.
> hda: ATAPI 24X CD-ROM drive, 128kB Cache
> Uniform CD-ROM driver Revision: 3.12
> SCSI subsystem driver Revision: 1.00
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36

What's the SCSI BIOS version?

>        <Adaptec 3960D Ultra160 SCSI adapter>
>        aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> 
> scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>        <Adaptec 3960D Ultra160 SCSI adapter>
>        aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
> 
> scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>        <Adaptec aic7899 Ultra160 SCSI adapter>
>        aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
> 
> blk: queue f7e46018, I/O limit 4095Mb (mask 0xffffffff)
>  
> I waited about 10 minutes to see if it would continue, then booted back 
> into 2.6.14.4.

What's the diff between /proc/interrupt and lspci -v on those kernels, 
when they've finished the booting sequence?

If you find time, send me your BIOS settings and your .config in private 
email. I didn't track this thread from the beginning, so I don't know if 
you've already done this.

It might also help to carry this problem over to the linux-scsi mailing 
list, since, I believe, most SCSI guys don't ready lkml too frequently.

Of course, if 2.6.x works for you and you need to go productive, then 
I'd switch to it if I was you.

Just my 2 cents,
Roberto Nibali, ratz
-- 
echo 
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc

  parent reply	other threads:[~2006-01-07  9:19 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
2006-01-06 22:14                   ` Chris Stromsoe
2006-01-06 22:16                     ` Chris Stromsoe
2006-01-07  9:19                     ` Roberto Nibali [this message]
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=43BF8785.2010703@drugphish.ch \
    --to=ratz@drugphish.ch \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cbs@cts.ucla.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.