mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Remi <remi.colinet@free.fr>
To: Fabio Coatti <cova@ferrara.linux.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc5-mm1 : probe of 0000:00:1f.2 failed with error -16
Date: Mon, 13 Nov 2006 16:20:18 +0100	[thread overview]
Message-ID: <1163431218.45588d325eddf@imp4-g19.free.fr> (raw)
In-Reply-To: <200611131452.13234.cova@ferrara.linux.it>

Selon Fabio Coatti <cova@ferrara.linux.it>:

> > ata_piix: probe of 0000:00:1f.2 failed with error -16
> > Kernel panic - not syncing: Attempted to kill init!
> >
> > I disabled most options in my .config file just keeping ata_piix enabled.
> > 2.6.19-rc5 still boots fine but 2.6.19-rc-mm1 gives the same previous
> > message.
>
>
> It seems exactly the same problem that is hitting me:
>
> http://lkml.org/lkml/2006/11/13/37
>
> If some patch comes out, I'll be willing to try it asap ;)
>

You are getting the same message

ata_piix 0000:00:1f.2: MAP [ P0 P1 IDE IDE ]
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17
PCI: Unable to reserve I/O region #1:8@1f0 for device 0000:00:1f.2
ata_piix: probe of 0000:00:1f.2 failed with error -16

But, your drives are driven by the sata_sil driver, which seems to be ok.
See your partition tables displayed below.

ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 19 (level, low) -> IRQ 18
ata1: SATA max UDMA/100 cmd 0xF8804080 ctl 0xF880408A bmdma 0xF8804000 irq 18
ata2: SATA max UDMA/100 cmd 0xF88040C0 ctl 0xF88040CA bmdma 0xF8804008 irq 18
scsi1 : sata_sil
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: ATA-7, max UDMA/133, 625142448 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 0
ata1.00: configured for UDMA/100
scsi2 : sata_sil
ata2: SATA link down (SStatus 0 SControl 310)
scsi 1:0:0:0: Direct-Access     ATA      Maxtor 6V320F0   VA11 PQ: 0 ANSI: 5
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 >

-- cut

VFS: Cannot open root device "821" or unknown-block(8,33)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(8,33)

Your root device seems to be wrong. Append the correct root=/dev/sda1 if it is
this partition.

Anyway, the first message indicates the same trouble as mine when trying to
reserve the I/O ports.

Remi

  reply	other threads:[~2006-11-13 15:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 13:44 Remi
2006-11-13 13:52 ` Fabio Coatti
2006-11-13 15:20   ` Remi [this message]
2006-11-13 15:54     ` Fabio Coatti
2006-11-13 16:27       ` Remi
2006-11-13 19:45         ` Fabio Coatti
2006-11-13 14:14 ` Alan
2006-11-13 14:59   ` Remi

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=1163431218.45588d325eddf@imp4-g19.free.fr \
    --to=remi.colinet@free.fr \
    --cc=cova@ferrara.linux.it \
    --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®