public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [boot hang] 2.6.7-rc2, VIA VT8237
Date: Fri, 04 Jun 2004 16:18:06 -0400	[thread overview]
Message-ID: <40C0D8FE.7040009@blue-labs.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

[snip]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0
VIA8237SATA: chipset revision 128
VIA8237SATA: 100% native mode on irq 11
    ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:pio, hdh:pio
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
PCI: IRQ 0 for device 0000:00:0f.1 doesn't match PIRQ mask - try 
pci=usepirqmask
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
hda: SAMSUNG SP1614N, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdd: 4X4X32, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, 
UDMA(100)
 /dev/ide/host0/bus0/target0/lun0:
[hard hang - HD LED on solid, machine locked up, should show p1 p2 p3]


This is a brand new mobo w/ an Opteron 148 on it.  SK8V.  The Gentoo 
LiveCD is a 2.6.5 kernel and it boots ok on it.  I'm starting to do 
tests to see what I can do to get it to function.

What I know at present.

1) Hard hang requiring reset switch
2) no known boot options affect it
3) no BIOS twiddling affects it, dma on/off, 32bit, whatever.
4) no generic or !generic IDE CONFIG_ options make a difference.

gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r5, ssp-3.3-7, pie-8.7.5.3)

Gnu C                  3.3.3
Gnu make               3.80
binutils               2.15.90.0.1.1
util-linux             2.12
mount                  2.12
module-init-tools      3.0
e2fsprogs              1.35
Linux C Library        2.3.3
Dynamic linker (ldd)   2.3.3
Net-tools              1.60
Kbd                    1.12
Sh-utils               5.2.1


[-- Attachment #2: config.bz2 --]
[-- Type: application/octet-stream, Size: 3638 bytes --]

[-- Attachment #3: 2.6.7-rc2-boothang.bz2 --]
[-- Type: application/octet-stream, Size: 7092 bytes --]

[-- Attachment #4: lspci.bz2 --]
[-- Type: application/octet-stream, Size: 2355 bytes --]

             reply	other threads:[~2004-06-04 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 20:18 David Ford [this message]
2004-06-04 20:38 ` [boot hang] 2.6.7-rc2, VIA VT8237 Bartlomiej Zolnierkiewicz
2004-06-04 20:42   ` David Ford
2004-06-04 23:12     ` David Ford
2004-06-12  0:53       ` [culprit found] " David Ford

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=40C0D8FE.7040009@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=linux-kernel@vger.kernel.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