From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [BUG] 2.4.20-BK
Date: Sat, 7 Dec 2002 20:36:08 +0100 [thread overview]
Message-ID: <200212072036.08500.m.c.p@wolk-project.de> (raw)
In-Reply-To: <200212071434.11514.m.c.p@wolk-project.de>
On Saturday 07 December 2002 14:35, Marc-Christian Petersen wrote:
Hi Alan,
ok, just another bug I hit:
pdc202xx_new: static build, module build do not have Special FastTrack
features so the system will say neither IDE port enabled (BIOS) so it won't
work.
PDC20270: IDE controller at PCI slot 01:01.0
PDC20270: chipset revision 2
PDC20270: not 100% native mode: will probe irqs later
PDC20270: ROM enabled at 0xefdd0000
ide0: BM-DMA at 0x9400-0x9407, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x9408-0x940f, BIOS settings: hdc:pio, hdd:pio
ICH2: IDE controller at PCI slot 00:1f.1
ICH2: chipset revision 17
ICH2: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide3: BM-DMA at 0xffa8-0xffaf, BIOS settings: hda:pio, hdb:DMA
ide2: ports already in use, skipping probe
ide3: ports already in use, skipping probe
hda:
HANG! Nothing more happens. I wait for ~ 5 minutes.
same with disabled IRQ11 for PCI in BiOS:
PDC20270: IDE controller at PCI slot 01:01.0
PDC20270: chipset revision 2
PDC20270: not 100% native mode: will probe irqs later
PDC20270: ROM enabled at 0xefdd0000
ide0: BM-DMA at 0x9400-0x9407, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x9408-0x940f, BIOS settings: hdc:pio, hdd:pio
ICH2: IDE controller at PCI slot 00:1f.1
ICH2: chipset revision 17
ICH2: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide3: BM-DMA at 0xffa8-0xffaf, BIOS settings: hda:pio, hdb:DMA
ide2: ports already in use, skipping probe
ide3: ports already in use, skipping probe
hda:<3>hda: lost interrupt
hda: lost interrupt
hda1
<going ahead>
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
cramfs: wrong magic
Kernel panic: VFS: Unable to mount root fs on 03:03
<0> Rebooting in 60 seconds..
P.S.: Is this appreciated for -BK tree's to reports bugs? I assume yes :)
ciao, Marc
next prev parent reply other threads:[~2002-12-07 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 13:35 Marc-Christian Petersen
2002-12-07 19:36 ` Marc-Christian Petersen [this message]
2002-12-08 9:29 ` Henning P. Schmiedehausen
2002-12-08 12:37 ` Marc-Christian Petersen
2002-12-08 14:13 ` Alan Cox
2002-12-08 13:40 ` Marc-Christian Petersen
2002-12-08 14:27 ` Alan Cox
2002-12-08 1:51 ` Alan Cox
2002-12-08 1:16 ` Marc-Christian Petersen
2002-12-08 1:22 ` J.A. Magallon
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=200212072036.08500.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®