From: Roland Dreier <rdreier@cisco.com>
To: Tobias Winter <tobias@linuxdingsda.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64
Date: Wed, 23 Jan 2008 17:15:44 -0800 [thread overview]
Message-ID: <adaabmwowfz.fsf@cisco.com> (raw)
In-Reply-To: <4797D86B.3060202@linuxdingsda.de> (Tobias Winter's message of "Thu, 24 Jan 2008 01:14:35 +0100")
> drivers/acpi/pci_bind.c: In function 'acpi_pci_unbind':<built-in>:0:
> internal compiler error: Segmentation fault
> Depending on which kernel i build, it fails on different things.
Seems like a classic symptom of some sort of hardware fault/memory corruption...
> I tried disabling HPET and VT in the BIOS but that didn't help. I also
> ruled out any memory problems with memtest86+.Don't know what else to do.
So your memory may be OK... (memtest86 does miss some problem sometimes)
> [8.6.] SCSI information (from /proc/scsi/scsi)
> Attached devices:
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: IBM-PCCO Model: DDRS-34560W !# Rev: S97B
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
> Vendor: NEC Model: CD-ROM DRIVE:464 Rev: 1.14
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6V250F0 Rev: VA11
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi2 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6V250F0 Rev: VA11
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi3 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6V250F0 Rev: VA11
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi4 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6V250F0 Rev: VA11
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi5 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6V250F0 Rev: VA11
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi6 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6V250F0 Rev: VA11
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi7 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6L250R0 Rev: BAJ4
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi7 Channel: 00 Id: 01 Lun: 00
> Vendor: ATA Model: Maxtor 6L250R0 Rev: BAH4
> Type: Direct-Access ANSI SCSI revision: 05
That is a lot of hard drives... my guess would be that your power
supply is marginal, a cable/adapter card isn't seated perfectly
somewhere, something is overheating, or something like that.
next prev parent reply other threads:[~2008-01-24 1:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 0:14 kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64 Tobias Winter
2008-01-24 1:07 ` Stephen Hemminger
2008-01-24 14:45 ` Lennart Sorensen
2008-01-25 10:17 ` [resolved] " Tobias Winter
2008-01-25 14:25 ` Lennart Sorensen
2008-01-25 17:20 ` Valdis.Kletnieks
2008-01-24 1:15 ` Roland Dreier [this message]
2008-01-24 11:21 ` Tobias Winter
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=adaabmwowfz.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tobias@linuxdingsda.de \
/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.