[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#644174: DELL/Vostro 3750 fails to boot (Re: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI)

Hi Mathieu,

Mathieu Malaterre wrote:

> I am trying to install debian on my new DELL/Vostro 3750 laptop.
> This comes with another OS. I did shrink that partition and
> installed debian over the free partition.
> d-i went perfectly fine, asking the usual question, without any
> warning.
> Boot method: USB key, plug on USB 2.0 port (USB 3.0 port is not even seen
> from d-i)

Yeah, xhci support in squeeze is not so great.  After we deal with the
rest, it's probably worth looking into that.

> Kernel: debian- 

Hmm, so this d-i kernel worked ok.

> However upon reboot it keeps on failing with:
> Waiting for /dev to be fully populated
> [10.133655] ACPI I/O resource 0000:00:1f.3 [0xefa0-0xefbf] conflicts with ACPI region SMBI [0xefa0-0xefaf]
> When starting in rescue mode from grub, it seems to go a little
> further (well it is much more verbose), but still one of the last
> message is still about ACPI conflict and something like:

That resource conflict might not actually be the problem that's
causing the machine to fail to boot (searching online, I see lots of
people have that message, which also sounds worth fixing, true).

 - can you grab "dmesg" and "acpidump" output from the
   debian-installer environment?  I don't think the d-i disks include
   an acpidump udeb, so this would presumably transferring acpidump
   and all the libraries it requires (shown with "ldd
   /path/to/acpidump") over the network or by USB stick and using
   them in a rescue shell.

 - can you get logs with netconsole or a serial console, or take a
   photograph of the screen when it fails in rescue mode?

 - does booting with acpi=off on the kernel command line change
   anything?  (You can edit the kernel command line with "e" and by
   modifying the line that mentions "single" in grub2, then booting
   with ctrl-x.)

Hope that helps, 

Reply to: