From: Jason Williams <jason_williams@suth.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.43 and the VIA vt8233 IDE controller.
Date: 17 Oct 2002 09:13:29 -0400 [thread overview]
Message-ID: <1034860413.19730.91.camel@cermanius.suth.com> (raw)
In-Reply-To: <1034800703.12979.12.camel@cermanius.suth.com>
Just a small addendum to this post I made yesterday, I took the VIA IDE
controller code out of the kernel and it booted just fine. And again,
my Promise RAID controller was seen just fine by the kernel, so I am
leaning even more toward a problem in the VIA driver.
Jason
On Wed, 2002-10-16 at 16:38, Jason Williams wrote:
> I am suspecting something is amist with the via controller code in
> 2.5.43, because my promise controller goes through the same routines
> just fine. I started to try to back trace everything to hunt down the
> culperate myself, but alas, I couldn't find the cause. So if anyone can
> give me a hand here, I would be very grateful. What follows is the
> bottom snippet of kernel output. If you require anything further, let
> me know I will send it.
>
> Jason
>
>
>
>
> ----
>
>
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
> ide1: BM-DMA at 0x9008-0x900fUnable to handle kernel NULL pointer dereference at virtual address 00000650
> printing eip:
> c024a52b
> *pde = 00000000
> Oops: 0000
>
> CPU: 0
> EIP: 0060:[<c024a52b>] Not tainted
> EFLAGS: 00010202
> EIP is at ide_iomio_dma+0xbb/0x1c0
> eax: 00000000 ebx: c052cbb4 ecx: c03aa274 edx: 00000001
> esi: c052cbc4 edi: 00009008 ebp: 00000008 esp: dffcbeb4
> ds: 0068 es: 0068 ss: 0068
> Process swapper (pid: 1, threadinfo=dffca000 task=dffc8040)
> Stack: c0380d6f 00009008 00000008 c052cbc4 c1526000 c052cbb4 c03e7a50 c052cbb4
> c024a687 c052cbb4 00009008 00000008 00000089 c04195dd c1526000 00009008
> c0418a58 c052cbb4 00009008 00000008 c02488be c052cbb4 00009008 00000004
> Call Trace:
> [<c024a687>] ide_setup_dma+0x27/0x380
> [<c02488be>] ide_hwif_setup_dma+0x10e/0x150
> [<c0248bce>] do_ide_setup_pci_device+0x16e/0x330
> [<c0248dbb>] ide_setup_pci_device+0x2b/0x80
> [<c02388e8>] via_init_one+0x38/0x40
> [<c010507a>] init+0x3a/0x160
> [<c0105040>] init+0x0/0x160
> [<c0105641>] kernel_thread_helper+0x5/0x14
>
> Code: 8b 80 50 06 00 00 89 83 4c 06 00 00 c7 04 24 77 0d 38 c0 e8
> <0>Kernel panic: Attempted to kill init!
prev parent reply other threads:[~2002-10-17 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 20:38 2.5.43 and the VIA vt8233 IDE controller Jason Williams
2002-10-17 13:13 ` Jason Williams [this message]
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=1034860413.19730.91.camel@cermanius.suth.com \
--to=jason_williams@suth.com \
--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