Debian Bug report logs - #644174
linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI

version graph

Package: linux-2.6; Maintainer for linux-2.6 is Debian Kernel Team <debian-kernel@lists.debian.org>;

Reported by: Mathieu Malaterre <malat@debian.org>

Date: Mon, 3 Oct 2011 16:21:02 UTC

Severity: important

Found in versions 3.7.1-1~experimental.1, 2.6.32-35squeeze2

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 03 Oct 2011 16:21:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 03 Oct 2011 16:21:05 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI
Date: Mon, 03 Oct 2011 18:18:28 +0200
Package: linux-2.6
Version: 2.6.32-35squeeze2
Severity: important


hi,

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.

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:

If an ACPI driver is available for this device, you should use it instead of the native driver

I can never get to a shell to dump the actual configuration. I am hoping this bug report is still somewhat usefull.

Please let me know if you need anything else.

Boot method: USB key, plug on USB 2.0 port (USB 3.0 port is not even seen from d-i)
Kernel: debian-6.0.2.1-amd64-netinst.iso 

-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35squeeze2) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Sep 9 20:23:16 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/hpdesk-root ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[DELETED since not appropriate]

** Model information
[DELETED since not appropriate]

** Loaded modules:
[DELETED since not appropriate]

** PCI devices:
[DELETED since not appropriate]


** USB devices:
[DELETED since not appropriate]

-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii  debconf [debconf-2.0]        1.5.36.1    Debian configuration management sy
ii  initramfs-tools [linux-initr 0.98.8      tools for generating an initramfs
ii  linux-base                   3.3~bpo60+1 Linux image base package
ii  module-init-tools            3.12-1      tools for managing Linux kernel mo

Versions of packages linux-image-2.6.32-5-amd64 recommends:
pn  firmware-linux-free           <none>     (no description available)

Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn  grub | lilo                   <none>     (no description available)
pn  linux-doc-2.6.32              <none>     (no description available)

Versions of packages linux-image-2.6.32-5-amd64 is related to:
pn  firmware-bnx2                 <none>     (no description available)
pn  firmware-bnx2x                <none>     (no description available)
pn  firmware-ipw2x00              <none>     (no description available)
pn  firmware-ivtv                 <none>     (no description available)
pn  firmware-iwlwifi              <none>     (no description available)
pn  firmware-linux                <none>     (no description available)
pn  firmware-linux-nonfree        <none>     (no description available)
pn  firmware-qlogic               <none>     (no description available)
pn  firmware-ralink               <none>     (no description available)
pn  xen-hypervisor                <none>     (no description available)

-- debconf information excluded




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 03 Oct 2011 16:51:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 03 Oct 2011 16:51:05 GMT) Full text and rfc822 format available.

Message #10 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Subject: Re: Bug#644174: Acknowledgement (linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI)
Date: Mon, 3 Oct 2011 18:49:13 +0200
[Message part 1 (text/plain, inline)]
Adding debug logs from d-i if that help.

Thanks
[hardware-summary (application/octet-stream, attachment)]
[syslog (application/octet-stream, attachment)]
[Xorg.0.log (text/x-log, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 03 Oct 2011 20:27:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 03 Oct 2011 20:27:03 GMT) Full text and rfc822 format available.

Message #15 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: 644174@bugs.debian.org
Subject: DELL/Vostro 3750 fails to boot (Re: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI)
Date: Mon, 3 Oct 2011 15:25:29 -0500
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-6.0.2.1-amd64-netinst.iso 

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, 
Jonathan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 03 Oct 2011 21:06:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 03 Oct 2011 21:06:04 GMT) Full text and rfc822 format available.

Message #20 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: 644174@bugs.debian.org
Subject: Re: DELL/Vostro 3750 fails to boot (Re: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI)
Date: Mon, 3 Oct 2011 16:03:30 -0500
Mathieu Malaterre wrote:

> Thanks for your help, very much appreciated. Do you have any
> reference, tutorial on netconsole within d-i. All I can find at the
> moment is:

The installer log you sent is already enough of a log from the d-i
side --- sorry I missed it before.  Where netconsole would be useful
is in getting a log from the installed system.  I think you understood
this; just repeating it for reference.

> http://www.debian-administration.org/articles/492
>
> I do not see how I can `modprobe netconsole` when booting my laptop machine.

Yeah, that article kind of misses the point. :)

Here's some quick documentation on netconsole[1] and serial console[2].
In many cases, a photo of the screen is just as good.

Cheers,
Jonathan

[1] https://raw.github.com/torvalds/linux/master/Documentation/networking/netconsole.txt
[2] https://raw.github.com/torvalds/linux/master/Documentation/serial-console.txt




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Tue, 04 Oct 2011 07:27:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 04 Oct 2011 07:27:04 GMT) Full text and rfc822 format available.

Message #25 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 644174@bugs.debian.org
Subject: Re: DELL/Vostro 3750 fails to boot (Re: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI)
Date: Tue, 4 Oct 2011 09:21:40 +0200
[Message part 1 (text/plain, inline)]
On Mon, Oct 3, 2011 at 11:03 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> I do not see how I can `modprobe netconsole` when booting my laptop machine.
>
> Yeah, that article kind of misses the point. :)
>
> Here's some quick documentation on netconsole[1] and serial console[2].
> In many cases, a photo of the screen is just as good.
>
[...]
> [1] https://raw.github.com/torvalds/linux/master/Documentation/networking/netconsole.txt
> [2] https://raw.github.com/torvalds/linux/master/Documentation/serial-console.txt

I tried following [1]. Reboot computer. Select 'recovery mode' from
grub. Edit. add:

 insmod netconsole netconsole=@/,@192.168.0.16/

Go to machine with IP: 192.168.0.16. Tried running:

$ nc -l -u 6666
UDP listen needs -p arg

Tried then:

$ netcat -u -l -p 6666

It would wait for something, so I I pressed 'Ctrl-x' from grub on my
laptop (IP:192.168.0.23). I did not see anything coming.

So here is a photo of the screen.

Thanks very much !
-- 
Mathieu
[IMG_0289.JPG (image/jpeg, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 07 Oct 2011 04:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ben Hutchings <ben@decadent.org.uk>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 07 Oct 2011 04:51:03 GMT) Full text and rfc822 format available.

Message #30 received at 644174@bugs.debian.org (full text, mbox):

From: Ben Hutchings <ben@decadent.org.uk>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>, 644174@bugs.debian.org
Subject: Re: Bug#644174: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI
Date: Fri, 07 Oct 2011 05:49:04 +0100
[Message part 1 (text/plain, inline)]
On Mon, 2011-10-03 at 18:18 +0200, Mathieu Malaterre wrote:
> Package: linux-2.6
> Version: 2.6.32-35squeeze2
> Severity: important
> 
> 
> hi,
> 
> 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.
> 
> 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),

It is probably just more verbose, as the standard boot entries reduce
kernel logging to the console (by default).

> but still one of the last message is still about ACPI conflict and
> something like:
> 
> If an ACPI driver is available for this device, you should use it instead of the native driver
[...]

These warnings are probably unrelated to the failure to boot.

Can you send a photo of the last messages, when you select the 'rescue'
boot entry?

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison
[signature.asc (application/pgp-signature, inline)]

Added tag(s) moreinfo. Request was from Ben Hutchings <ben@decadent.org.uk> to control@bugs.debian.org. (Fri, 07 Oct 2011 04:51:04 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 07 Oct 2011 06:54:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 07 Oct 2011 06:54:08 GMT) Full text and rfc822 format available.

Message #37 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 644174@bugs.debian.org
Subject: Re: Bug#644174: linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts with ACPI region SMBI
Date: Fri, 7 Oct 2011 08:48:56 +0200
On Fri, Oct 7, 2011 at 6:49 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Mon, 2011-10-03 at 18:18 +0200, Mathieu Malaterre wrote:
> Can you send a photo of the last messages, when you select the 'rescue'
> boot entry?

Hi Ben,

Thanks for taking the time to look into this issue. I did upload the photo here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#25

Let me know if you need anything else.

Thanks,
-- 
Mathieu




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Tue, 01 Nov 2011 11:34:45 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 01 Nov 2011 11:34:56 GMT) Full text and rfc822 format available.

Message #42 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Subject: Fwd: Debian 64-bit an Dell Vostro 3750 - freezes sometimes with message [Firmware Bug] ACPI(PEGP) dedefines _DOD but not _DOS
Date: Tue, 1 Nov 2011 12:32:11 +0100
> and then a lot of messages:
>
> Oct 30 20:27:48 WZLap kernel: [ 609.270026] xhci_hcd 0000:03:00.0: WARN: Stalled endpoint
> Oct 30 20:27:48 WZLap kernel: [ 609.274685] xhci_hcd 0000:03:00.0: WARN: Stalled endpoint
> Oct 30 20:27:48 WZLap kernel: [ 609.281701] xhci_hcd 0000:03:00.0: WARN: Stalled endpoint
> Oct 30 20:27:48 WZLap kernel: [ 609.285046] xhci_hcd 0000:03:00.0: WARN: Stalled endpoint
>
> Even though the device seems to work correctly.
>
> Probably I need to try to blacklist the USB 3.0 module...

I have read some reports (and not only in Debian) on this. E.g.,:

linux-image-2.6.38-2-amd64: xhci_hcd USB 3.0 not working properly
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623004

Blacklisting the involved module "xhci_hcd" is a workaround that could
solve your issue during a time but better if add your findings to a bug
report so the problem can be properly solved and other users can also
benefit from it :-)




Removed tag(s) moreinfo. Request was from Jonathan Nieder <jrnieder@gmail.com> to control@bugs.debian.org. (Mon, 14 Nov 2011 12:00:03 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 16 Dec 2011 09:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 16 Dec 2011 09:51:09 GMT) Full text and rfc822 format available.

Message #49 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Date: Fri, 16 Dec 2011 10:48:28 +0100
Some update. I left my laptop unattended the whole night. Windows did
perform a reboot after that. For some reason my USB mouse was
unplugged and this morning my laptop did boot successfully my debian
system.

So short story: just unplugged any USB device and it should boot nicely.

Let me know if I should just close this bug.

Thanks,
-- 
Mathieu




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 16 Dec 2011 10:30:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 16 Dec 2011 10:30:04 GMT) Full text and rfc822 format available.

Message #54 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: 644174@bugs.debian.org
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Fri, 16 Dec 2011 04:27:58 -0600
Mathieu Malaterre wrote:

> So short story: just unplugged any USB device and it should boot nicely.
>
> Let me know if I should just close this bug.

Thanks for the follow up.

No, we shouldn't close this --- it seems it's just another sign that
xhci support is a little broken in squeeze.  Nice to see that's the
*only* problem here. :)

What is the latest squeeze kernel you've tried and reproduced this
with?  ("cat /proc/version" will say the current version in
parentheses.)

To move forward:

 - Please attach "acpidump" output.  (I doubt it's relevant, but it's
   useful to have for reference.)

 - Please test a v3.2 release candidate from experimental.  The only
   packages from outside squeeze that should be needed for this, aside
   from the kernel image itself, are linux-base and initramfs-tools.

 - If it reproduces the problem, please blacklist the xhci_hcd
   module by writing

	blacklist xhci_hcd

   to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run

	update-initramfs -u -k all

   and reboot to try again without USB 3.0 support.  If we're very
   lucky, this will work around the problem.  In that case, please
   write a summary of the problem to upstream
   (linux-usb@vger.kernel.org, cc-ing Sarah Sharp
   <sarah.a.sharp@linux.intel.com> and either me or this bug log so we
   can track the resulting discussion).  Be sure to include:

    - steps to reproduce the problem
    - symptoms, and how they differ from what you expected
    - ways to avoid triggering the problem (maybe some USB ports
      trigger it and others don't? etc)
    - full "dmesg" output from booting, and a photo of the screen
      after reproducing the problem (ideally by running "modprobe
      xhci_hcd" in the very same run of Linux), as attachments
    - which kernel versions you've tested, and what happened with each
    - a link to this bug log for the full story
    - any other weird symptoms or observations

Thanks for your patience and hope that helps,
Jonathan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 14:54:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 14:54:03 GMT) Full text and rfc822 format available.

Message #59 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Date: Thu, 22 Dec 2011 15:51:56 +0100
Scenario 0: Nothing plugged to no USB 2.0/3.0 port:

- can boot 2.6.32-5-amd64
- can boot 2.6.39-bpo.2-amd64
- can boot 3.1.0-1-amd64

Scenario 1: Mouse plugged to USB 2.0 port:

- can not boot 2.6.32-5-amd64
- can boot 2.6.39-bpo.2-amd64
- can boot 3.1.0-1-amd64

Scenario 2: Mouse plugged to USB 3.0 port:

- can not boot 2.6.32-5-amd64
- can not boot 2.6.39-bpo.2-amd64
- can not boot 3.1.0-1-amd64


-- 
Mathieu




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 15:12:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 15:12:04 GMT) Full text and rfc822 format available.

Message #64 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Date: Thu, 22 Dec 2011 16:09:29 +0100
[Message part 1 (text/plain, inline)]
This is the screen when booting 3.2.0-rc4-amd64, mouse attached to USB 3.0. And

$ cat /etc/modprobe.d/mm-blacklist-xhci.conf
blacklist xhci_hcd

Once this file is uploaded to BTS, I'll use this link for further bug reporting.

Thanks
[IMG_0529.JPG (image/jpeg, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 15:15:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 15:15:04 GMT) Full text and rfc822 format available.

Message #69 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Date: Thu, 22 Dec 2011 16:13:20 +0100
[Message part 1 (text/plain, inline)]
dmesg output from 3.2.0-rc4-amd64 boot, mouse attached to USB 2.0 port.
[dmesg.txt (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 15:21:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 15:21:04 GMT) Full text and rfc822 format available.

Message #74 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 644174@bugs.debian.org, linux-usb@vger.kernel.org, sarah.a.sharp@linux.intel.com
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Thu, 22 Dec 2011 16:18:56 +0100
On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>  - Please test a v3.2 release candidate from experimental.  The only
>   packages from outside squeeze that should be needed for this, aside
>   from the kernel image itself, are linux-base and initramfs-tools.
>
>  - If it reproduces the problem, please blacklist the xhci_hcd
>   module by writing
>
>        blacklist xhci_hcd
>
>   to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run
>
>        update-initramfs -u -k all
>
>   and reboot to try again without USB 3.0 support.  If we're very
>   lucky, this will work around the problem.  In that case, please
>   write a summary of the problem to upstream
>   (linux-usb@vger.kernel.org, cc-ing Sarah Sharp
>   <sarah.a.sharp@linux.intel.com> and either me or this bug log so we
>   can track the resulting discussion).  Be sure to include:
>
>    - steps to reproduce the problem
>    - symptoms, and how they differ from what you expected
>    - ways to avoid triggering the problem (maybe some USB ports
>      trigger it and others don't? etc)
>    - full "dmesg" output from booting, and a photo of the screen
>      after reproducing the problem (ideally by running "modprobe
>      xhci_hcd" in the very same run of Linux), as attachments
>    - which kernel versions you've tested, and what happened with each
>    - a link to this bug log for the full story
>    - any other weird symptoms or observations

System: Dell System Vostro 3750 / Portable Computer

Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental.

No mouse plugged to USB 2.0/3.0 interface: boot is fine
Mouse plugged to USB 2.0 interface: boot is fine
Mouse plugged to USB 3.0 interface: boot simply stops

As suggested by Jonathan N. [1] here is what I did next:

$ cat /etc/modprobe.d/mm-blacklist-xhci.conf
blacklist xhci_hcd
$ update-initramfs -u -k all
$ sudo reboot

3.2.0-rc4-amd64 refuse to boot as soon as I plug my mouse to USB 3.0
port (screenshot at [2]). USB 2.0 and no mouse still boot fine.

I am attaching dmesg from a kernel boot, when mouse is attached to USB
2.0 port (see [3]).

I think I'll revert to 2.6.39-bpo.2-amd64 because kernel does not
seems to like my video card. When I suspend/resume, screen is
displayed on screen Ctrl+Shift+F8, while pointer stays on
Ctrl+Shift+F7. I can type fine from Ctrl+Shift+F7, since I can see
results on Ctrl+Shift+F8. I'll try to compile the nvidia kernel and
see if suspend/resume works.


Refs:
[1] http://bugs.debian.org/644174
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#64
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#69

Thanks,
-- 
Mathieu




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 15:24:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 15:24:03 GMT) Full text and rfc822 format available.

Message #79 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Date: Thu, 22 Dec 2011 16:21:19 +0100
[Message part 1 (text/plain, inline)]
Adding lspci + lshw output from 3.2.0-rc4-amd64, mouse on USB 2.0.
[lshw.txt (text/plain, attachment)]
[lspci.txt (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 19:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 19:51:03 GMT) Full text and rfc822 format available.

Message #84 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: 644174@bugs.debian.org, linux-usb@vger.kernel.org, sarah.a.sharp@linux.intel.com
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Thu, 22 Dec 2011 13:47:05 -0600
Hi,

Mathieu Malaterre wrote:

> Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental.
>
> No mouse plugged to USB 2.0/3.0 interface: boot is fine
> Mouse plugged to USB 2.0 interface: boot is fine
> Mouse plugged to USB 3.0 interface: boot simply stops
>
> As suggested by Jonathan N. [1] here is what I did next:
>
> $ cat /etc/modprobe.d/mm-blacklist-xhci.conf
> blacklist xhci_hcd
> $ update-initramfs -u -k all
> $ sudo reboot
>
> 3.2.0-rc4-amd64 refuse to boot as soon as I plug my mouse to USB 3.0
> port (screenshot at [2]). USB 2.0 and no mouse still boot fine.

So do I understand correctly, that blacklisting the xhci driver does
_not_ avoid trouble?  Can you confirm that the blacklisting worked,
by booting and checking that the xhci_hcd module is not loaded?

If so, this presumably has nothing to do with the xhci driver, and is
probably caused by something lower level.

Happy holidays,
Jonathan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Dec 2011 20:06:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Sarah Sharp <sarah.a.sharp@linux.intel.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Dec 2011 20:06:04 GMT) Full text and rfc822 format available.

Message #89 received at 644174@bugs.debian.org (full text, mbox):

From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, 644174@bugs.debian.org, linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Thu, 22 Dec 2011 11:52:43 -0800
On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote:
> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> >  - Please test a v3.2 release candidate from experimental.  The only
> >   packages from outside squeeze that should be needed for this, aside
> >   from the kernel image itself, are linux-base and initramfs-tools.
> >
> >  - If it reproduces the problem, please blacklist the xhci_hcd
> >   module by writing
> >
> >        blacklist xhci_hcd
> >
> >   to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run
> >
> >        update-initramfs -u -k all
> >
> >   and reboot to try again without USB 3.0 support.  If we're very
> >   lucky, this will work around the problem.  In that case, please
> >   write a summary of the problem to upstream
> >   (linux-usb@vger.kernel.org, cc-ing Sarah Sharp
> >   <sarah.a.sharp@linux.intel.com> and either me or this bug log so we
> >   can track the resulting discussion).  Be sure to include:
> >
> >    - steps to reproduce the problem
> >    - symptoms, and how they differ from what you expected
> >    - ways to avoid triggering the problem (maybe some USB ports
> >      trigger it and others don't? etc)
> >    - full "dmesg" output from booting, and a photo of the screen
> >      after reproducing the problem (ideally by running "modprobe
> >      xhci_hcd" in the very same run of Linux), as attachments
> >    - which kernel versions you've tested, and what happened with each
> >    - a link to this bug log for the full story
> >    - any other weird symptoms or observations
> 
> System: Dell System Vostro 3750 / Portable Computer
> 
> Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental.
> 
> No mouse plugged to USB 2.0/3.0 interface: boot is fine
> Mouse plugged to USB 2.0 interface: boot is fine
> Mouse plugged to USB 3.0 interface: boot simply stops

Does the boot stop when you have a non-HID USB device plugged into the
USB 3.0 port (e.g. hub or flash drive or USB speaker)?  It could be an
issue with a buggy BIOS trying to use the mouse and keyboard (HID
devices) attached to the USB 3.0 host.  Perhaps it changes the ACPI
tables when it tries to use the USB 3.0 host controller, and
accidentally overlaps the regions?  But if your keyboard and mouse were
under USB 2.0, maybe it will only map in the USB 2.0 host controller.

> As suggested by Jonathan N. [1] here is what I did next:
> 
> $ cat /etc/modprobe.d/mm-blacklist-xhci.conf
> blacklist xhci_hcd
> $ update-initramfs -u -k all
> $ sudo reboot

Were you blacklisting xhci only because of the "xhci_hcd 0000:03:00.0:
WARN: Stalled endpoint" messages?  Because those messages are harmless,
and don't mean anything is *wrong* with the host controller.

Even if there's no xHCI driver loaded, it seems that ACPI is noticing
the conflict between the PCI registers and another region.  So unloading
the xHCI driver won't help your system boot.  You'd need to get a fix
into the ACPI subsystem to work around the conflict.  I don't think any
xHCI driver modification can help here.

> 3.2.0-rc4-amd64 refuse to boot as soon as I plug my mouse to USB 3.0
> port (screenshot at [2]). USB 2.0 and no mouse still boot fine.
> 
> I am attaching dmesg from a kernel boot, when mouse is attached to USB
> 2.0 port (see [3]).
> 
> I think I'll revert to 2.6.39-bpo.2-amd64 because kernel does not
> seems to like my video card. When I suspend/resume, screen is
> displayed on screen Ctrl+Shift+F8, while pointer stays on
> Ctrl+Shift+F7. I can type fine from Ctrl+Shift+F7, since I can see
> results on Ctrl+Shift+F8. I'll try to compile the nvidia kernel and
> see if suspend/resume works.
> 
> 
> Refs:
> [1] http://bugs.debian.org/644174
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#64
> [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#69

Sarah Sharp




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Wed, 28 Dec 2011 17:15:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 28 Dec 2011 17:15:03 GMT) Full text and rfc822 format available.

Message #94 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, 644174@bugs.debian.org, linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Wed, 28 Dec 2011 18:11:14 +0100
On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp
<sarah.a.sharp@linux.intel.com> wrote:
> On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote:
>> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> >  - Please test a v3.2 release candidate from experimental.  The only
>> >   packages from outside squeeze that should be needed for this, aside
>> >   from the kernel image itself, are linux-base and initramfs-tools.
>> >
>> >  - If it reproduces the problem, please blacklist the xhci_hcd
>> >   module by writing
>> >
>> >        blacklist xhci_hcd
>> >
>> >   to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run
>> >
>> >        update-initramfs -u -k all
>> >
>> >   and reboot to try again without USB 3.0 support.  If we're very
>> >   lucky, this will work around the problem.  In that case, please
>> >   write a summary of the problem to upstream
>> >   (linux-usb@vger.kernel.org, cc-ing Sarah Sharp
>> >   <sarah.a.sharp@linux.intel.com> and either me or this bug log so we
>> >   can track the resulting discussion).  Be sure to include:
>> >
>> >    - steps to reproduce the problem
>> >    - symptoms, and how they differ from what you expected
>> >    - ways to avoid triggering the problem (maybe some USB ports
>> >      trigger it and others don't? etc)
>> >    - full "dmesg" output from booting, and a photo of the screen
>> >      after reproducing the problem (ideally by running "modprobe
>> >      xhci_hcd" in the very same run of Linux), as attachments
>> >    - which kernel versions you've tested, and what happened with each
>> >    - a link to this bug log for the full story
>> >    - any other weird symptoms or observations
>>
>> System: Dell System Vostro 3750 / Portable Computer
>>
>> Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental.
>>
>> No mouse plugged to USB 2.0/3.0 interface: boot is fine
>> Mouse plugged to USB 2.0 interface: boot is fine
>> Mouse plugged to USB 3.0 interface: boot simply stops
>
> Does the boot stop when you have a non-HID USB device plugged into the
> USB 3.0 port (e.g. hub or flash drive or USB speaker)?  It could be an
> issue with a buggy BIOS trying to use the mouse and keyboard (HID
> devices) attached to the USB 3.0 host.  Perhaps it changes the ACPI
> tables when it tries to use the USB 3.0 host controller, and
> accidentally overlaps the regions?  But if your keyboard and mouse were
> under USB 2.0, maybe it will only map in the USB 2.0 host controller.

I tried booting kernel 3.0.2 (debian/unstable 3.2.0-rc4-amd64) with a
USB key plugged into USB 3.0 and was stuck again. So I can confirm
that with a normal USB key (non-HID) plugged in USB 3.0 port, makes
the kernel refuse to boot.

After a normal boot, key appears as :
[  158.736727] usb 3-2: new high-speed USB device number 2 using xhci_hcd
[  158.755680] xhci_hcd 0000:03:00.0: WARN: short transfer on control ep
[  158.756522] xhci_hcd 0000:03:00.0: WARN: short transfer on control ep
[  158.757426] xhci_hcd 0000:03:00.0: WARN: short transfer on control ep
[  158.758299] xhci_hcd 0000:03:00.0: WARN: short transfer on control ep
[  158.758698] usb 3-2: New USB device found, idVendor=0951, idProduct=160f
[  158.758708] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  158.758714] usb 3-2: Product: DT Mini Slim
[  158.758719] usb 3-2: Manufacturer: Kingston
[  158.758723] usb 3-2: SerialNumber: 0019E06B07B5F9A1879A0D15
[  158.760294] scsi7 : usb-storage 3-2:1.0
[  159.760670] scsi 7:0:0:0: Direct-Access     Kingston DT Mini Slim
  1.00 PQ: 0 ANSI: 2
[  159.763089] sd 7:0:0:0: Attached scsi generic sg2 type 0
[  159.763655] sd 7:0:0:0: [sdb] 15654848 512-byte logical blocks:
(8.01 GB/7.46 GiB)
[  159.763834] sd 7:0:0:0: [sdb] Write Protect is off
[  159.763841] sd 7:0:0:0: [sdb] Mode Sense: 16 0f 09 51
[  159.764012] sd 7:0:0:0: [sdb] Incomplete mode parameter data
[  159.764019] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[  159.765193] sd 7:0:0:0: [sdb] Incomplete mode parameter data
[  159.765200] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[  159.765778]  sdb: sdb1
[  159.766855] sd 7:0:0:0: [sdb] Incomplete mode parameter data
[  159.766865] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[  159.766875] sd 7:0:0:0: [sdb] Attached SCSI removable disk


>> As suggested by Jonathan N. [1] here is what I did next:
>>
>> $ cat /etc/modprobe.d/mm-blacklist-xhci.conf
>> blacklist xhci_hcd
>> $ update-initramfs -u -k all
>> $ sudo reboot
>
> Were you blacklisting xhci only because of the "xhci_hcd 0000:03:00.0:
> WARN: Stalled endpoint" messages?  Because those messages are harmless,
> and don't mean anything is *wrong* with the host controller.

I simply blindly follow the suggestion.

> Even if there's no xHCI driver loaded, it seems that ACPI is noticing
> the conflict between the PCI registers and another region.  So unloading
> the xHCI driver won't help your system boot.  You'd need to get a fix
> into the ACPI subsystem to work around the conflict.  I don't think any
> xHCI driver modification can help here.

Is there a way to check if bug is related to ACPI or rather USB 3.0 ?

Thanks again,
-- 
Mathieu




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Wed, 28 Dec 2011 17:15:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 28 Dec 2011 17:15:05 GMT) Full text and rfc822 format available.

Message #99 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Date: Wed, 28 Dec 2011 18:13:55 +0100
[Message part 1 (text/plain, inline)]
Screenshot when booting
linux-image-3.2.0-rc4-amd64/3.2~rc4-1~experimental.1, with mouse
attached to USB 2.0 and USB Key attached to USB 3.0 port.

USB Key is: Bus 003 Device 002: ID 0951:160f Kingston Technology
[IMG_0530.JPG (image/jpeg, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Wed, 28 Dec 2011 17:21:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 28 Dec 2011 17:21:07 GMT) Full text and rfc822 format available.

Message #104 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Subject: Re: Bug#644174: Info received ()
Date: Wed, 28 Dec 2011 18:18:16 +0100
Some more info. Running linux 3.0.2 eventually leads to:


[  484.679306] BUG: scheduling while atomic: swapper/0/0x10000100
[  484.679315] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_storage uas
xhci_hcd ahci libahci libata scsi_mod ehci_hcd r8169 mii usbcore
usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
[  484.679466] CPU 0
[  484.679469] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_storage uas
xhci_hcd ahci libahci libata scsi_mod ehci_hcd r8169 mii usbcore
usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
[  484.679591]
[  484.679597] Pid: 0, comm: swapper Not tainted 3.2.0-rc4-amd64 #1
Dell Inc.          Dell System Vostro 3750/0VP036
[  484.679608] RIP: 0010:[<ffffffff811dc12d>]  [<ffffffff811dc12d>]
intel_idle+0xea/0x119
[  484.679625] RSP: 0018:ffffffff81601e88  EFLAGS: 00000202
[  484.679630] RAX: 0000000000000000 RBX: ffffffff811a5bfc RCX: 00000000000017b6
[  484.679636] RDX: 00000000000017b6 RSI: 0000000000000000 RDI: 00000000000003e8
[  484.679641] RBP: 0000000000000004 R08: 00000000000017ba R09: 00000000000017ba
[  484.679647] R10: ffffffff81780640 R11: ffffffff81601fd8 R12: ffff8801bfa0e700
[  484.679652] R13: ffff8801bfa0e710 R14: ffff8801ad3c3ac8 R15: ffff8801bfa0e7f0
[  484.679659] FS:  0000000000000000(0000) GS:ffff8801bfa00000(0000)
knlGS:0000000000000000
[  484.679666] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  484.679671] CR2: 000000000240b471 CR3: 0000000001605000 CR4: 00000000000406f0
[  484.679677] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  484.679683] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  484.679689] Process swapper (pid: 0, threadinfo ffffffff81600000,
task ffffffff8160d020)
[  484.679694] Stack:
[  484.679697]  0000000000000000 00000000000017b6 0000000000000000
0000000000000000
[  484.679708]  00000000000017b6 00000000005caf48 ffff8801bfa19870
ffffffff81644a80
[  484.679718]  00000000fffffff0 0000000000000004 ffffffff81644bc0
ffffffff8125bdf3
[  484.679728] Call Trace:
[  484.679741]  [<ffffffff8125bdf3>] ? cpuidle_idle_call+0xec/0x179
[  484.679753]  [<ffffffff8100d255>] ? cpu_idle+0xa1/0xe8
[  484.679764]  [<ffffffff816a8b3d>] ? start_kernel+0x3bd/0x3c8
[  484.679773]  [<ffffffff816a8140>] ? early_idt_handlers+0x140/0x140
[  484.679782]  [<ffffffff816a83c4>] ? x86_64_start_kernel+0x104/0x111
[  484.679787] Code: 29 f0 48 89 c7 e8 6b dc e6 ff 4c 69 e8 40 42 0f
00 48 89 04 24 48 89 54 24 08 48 89 44 24 18 48 89 54 24 20 49 01 d5
fb 66 66 90
[  484.679834]  66 90 85 1d b2 8b 46 00 75 0f 48 8d 74 24 2c bf 05 00 00 00
[  484.679858] Call Trace:
[  484.679866]  [<ffffffff8125bdf3>] ? cpuidle_idle_call+0xec/0x179
[  484.679874]  [<ffffffff8100d255>] ? cpu_idle+0xa1/0xe8
[  484.679882]  [<ffffffff816a8b3d>] ? start_kernel+0x3bd/0x3c8
[  484.679891]  [<ffffffff816a8140>] ? early_idt_handlers+0x140/0x140
[  484.679899]  [<ffffffff816a83c4>] ? x86_64_start_kernel+0x104/0x111
[  545.528641] BUG: scheduling while atomic: swapper/0/0x10000100
[  545.528649] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_storage uas
xhci_hcd ahci libahci libata scsi_mod ehci_hcd r8169 mii usbcore
usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
[  545.528795] CPU 0
[  545.528798] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_storage uas
xhci_hcd ahci libahci libata scsi_mod ehci_hcd r8169 mii usbcore
usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
[  545.528919]
[  545.528925] Pid: 0, comm: swapper Not tainted 3.2.0-rc4-amd64 #1
Dell Inc.          Dell System Vostro 3750/0VP036
[  545.528936] RIP: 0010:[<ffffffff811dc12d>]  [<ffffffff811dc12d>]
intel_idle+0xea/0x119
[  545.528953] RSP: 0018:ffffffff81601e88  EFLAGS: 00000206
[  545.528958] RAX: 0000000000000000 RBX: ffffffff81023a50 RCX: 0000000000007650
[  545.528963] RDX: 0000000000007650 RSI: 0000000000000000 RDI: 00000000000003e8
[  545.528969] RBP: 0000000000000004 R08: 0000000000007650 R09: 0000000000007650
[  545.528974] R10: ffff8801b7c53840 R11: ffffffff81601fd8 R12: ffffffff81064d21
[  545.528980] R13: 0000000000000221 R14: ffffffff8106491f R15: ffffffff8101356d
[  545.528987] FS:  0000000000000000(0000) GS:ffff8801bfa00000(0000)
knlGS:0000000000000000
[  545.528993] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  545.528998] CR2: 000000000240b471 CR3: 0000000001605000 CR4: 00000000000406f0
[  545.529004] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  545.529010] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  545.529017] Process swapper (pid: 0, threadinfo ffffffff81600000,
task ffffffff8160d020)
[  545.529021] Stack:
[  545.529025]  0000000000000000 0000000000007650 0000000000000000
0000000000000000
[  545.529035]  0000000000007650 0000000001ce2985 ffff8801bfa19870
ffffffff81644a80
[  545.529045]  00000000fffffff0 0000000000000004 ffffffff81644bc0
ffffffff8125bdf3
[  545.529055] Call Trace:
[  545.529068]  [<ffffffff8125bdf3>] ? cpuidle_idle_call+0xec/0x179
[  545.529081]  [<ffffffff8100d255>] ? cpu_idle+0xa1/0xe8
[  545.529092]  [<ffffffff816a8b3d>] ? start_kernel+0x3bd/0x3c8
[  545.529100]  [<ffffffff816a8140>] ? early_idt_handlers+0x140/0x140
[  545.529109]  [<ffffffff816a83c4>] ? x86_64_start_kernel+0x104/0x111
[  545.529114] Code: 29 f0 48 89 c7 e8 6b dc e6 ff 4c 69 e8 40 42 0f
00 48 89 04 24 48 89 54 24 08 48 89 44 24 18 48 89 54 24 20 49 01 d5
fb 66 66 90
[  545.529161]  66 90 85 1d b2 8b 46 00 75 0f 48 8d 74 24 2c bf 05 00 00 00
[  545.529184] Call Trace:
[  545.529192]  [<ffffffff8125bdf3>] ? cpuidle_idle_call+0xec/0x179
[  545.529201]  [<ffffffff8100d255>] ? cpu_idle+0xa1/0xe8
[  545.529209]  [<ffffffff816a8b3d>] ? start_kernel+0x3bd/0x3c8
[  545.529217]  [<ffffffff816a8140>] ? early_idt_handlers+0x140/0x140
[  545.529225]  [<ffffffff816a83c4>] ? x86_64_start_kernel+0x104/0x111




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Wed, 28 Dec 2011 17:27:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <mathieu.malaterre@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 28 Dec 2011 17:27:07 GMT) Full text and rfc822 format available.

Message #109 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: 644174@bugs.debian.org
Subject: Re: Bug#644174: Info received (Bug#644174: Info received ())
Date: Wed, 28 Dec 2011 18:24:12 +0100
Looks like this is a duplicate of 623004




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 29 Dec 2011 11:21:18 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 29 Dec 2011 11:21:20 GMT) Full text and rfc822 format available.

Message #114 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: 644174@bugs.debian.org, Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
Subject: DELL/Vostro 3750 fails to boot when devices plugged in USB 3.0 port
Date: Thu, 29 Dec 2011 05:17:48 -0600
Hi,

Thanks for your continued work on tracking this.  All I have to offer
are some administrivia this time.  (But as always, I'm still thinking
about ways to get to the heart of the thing.)

Mathieu Malaterre wrote:

> [Subject: Re: Bug#644174: Info received (Bug#644174: Info received ())]

Please keep in mind that this appears as the subject line in a crowded
inbox, so it can be a good place to put useful context.

> Looks like this is a duplicate of 623004

It's a duplicate of message#10 to bug 623004.  That message shares
warning messages with the original report at bug 623004, but it's not
clear to me that they are the same bug.  So let's continue to track it
as bug#644174.

Cheers,
Jonathan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 02 Jan 2012 18:27:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Sarah Sharp <sarah.a.sharp@linux.intel.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 02 Jan 2012 18:27:06 GMT) Full text and rfc822 format available.

Message #119 received at 644174@bugs.debian.org (full text, mbox):

From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, 644174@bugs.debian.org, linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Mon, 2 Jan 2012 10:14:30 -0800
On Wed, Dec 28, 2011 at 06:11:14PM +0100, Mathieu Malaterre wrote:
> On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp
> <sarah.a.sharp@linux.intel.com> wrote:
> > On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote:
> >> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> >> System: Dell System Vostro 3750 / Portable Computer
> >>
> >> Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental.
> >>
> >> No mouse plugged to USB 2.0/3.0 interface: boot is fine
> >> Mouse plugged to USB 2.0 interface: boot is fine
> >> Mouse plugged to USB 3.0 interface: boot simply stops
> >
> > Does the boot stop when you have a non-HID USB device plugged into the
> > USB 3.0 port (e.g. hub or flash drive or USB speaker)?  It could be an
> > issue with a buggy BIOS trying to use the mouse and keyboard (HID
> > devices) attached to the USB 3.0 host.  Perhaps it changes the ACPI
> > tables when it tries to use the USB 3.0 host controller, and
> > accidentally overlaps the regions?  But if your keyboard and mouse were
> > under USB 2.0, maybe it will only map in the USB 2.0 host controller.
> 
> I tried booting kernel 3.0.2 (debian/unstable 3.2.0-rc4-amd64) with a
> USB key plugged into USB 3.0 and was stuck again. So I can confirm
> that with a normal USB key (non-HID) plugged in USB 3.0 port, makes
> the kernel refuse to boot.

Please try a USB hub as well.  It's possible the BIOS is trying to read
from the flash drive (which is what I assume you mean by USB key).

> >> As suggested by Jonathan N. [1] here is what I did next:
> >>
> >> $ cat /etc/modprobe.d/mm-blacklist-xhci.conf
> >> blacklist xhci_hcd
> >> $ update-initramfs -u -k all
> >> $ sudo reboot
> >
> > Were you blacklisting xhci only because of the "xhci_hcd 0000:03:00.0:
> > WARN: Stalled endpoint" messages?  Because those messages are harmless,
> > and don't mean anything is *wrong* with the host controller.
> 
> I simply blindly follow the suggestion.

Yeah, don't try to blacklist xhci-hcd.  It's not useful.

> > Even if there's no xHCI driver loaded, it seems that ACPI is noticing
> > the conflict between the PCI registers and another region.  So unloading
> > the xHCI driver won't help your system boot.  You'd need to get a fix
> > into the ACPI subsystem to work around the conflict.  I don't think any
> > xHCI driver modification can help here.
> 
> Is there a way to check if bug is related to ACPI or rather USB 3.0 ?

The log messages seem to indicate that it's either an ACPI or a BIOS
issue.  I really can't suggest any other tests without some input from
the ACPI folks.  The best solution I can suggest is not boot with a USB
device plugged into your USB 3.0 port.

Sarah Sharp




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 02 Jan 2012 19:15:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 02 Jan 2012 19:15:07 GMT) Full text and rfc822 format available.

Message #124 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Mathieu Malaterre <mathieu.malaterre@gmail.com>, 644174@bugs.debian.org, linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org, Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Mon, 2 Jan 2012 13:11:58 -0600
Quick side question:

Sarah Sharp wrote:

> Yeah, don't try to blacklist xhci-hcd.  It's not useful.

How else do you suggest that people figure out whether symptoms are
produced by the xhci-hcd driver or something else?  However, I agree
that it's not useful _any more_, since Mathieu tried that test
already.

[...]
> The log messages seem to indicate that it's either an ACPI or a BIOS
> issue.  I really can't suggest any other tests without some input from
> the ACPI folks.  The best solution I can suggest is not boot with a USB
> device plugged into your USB 3.0 port.

Hm.  Mathieu, is it possible to suspend-to-disk ("echo disk >/sys/power/state")
and resume with a USB device plugged into the USB 3.0 port?

Please also attach output from "acpidump" after a successful boot.

Can you reproduce this when booting in recovery mode with
i915.modeset=0 appended to the kernel command line?

Thanks,
Jonathan




Changed Bug submitter to 'Mathieu Malaterre <malat@debian.org>' from 'Mathieu Malaterre <mathieu.malaterre@gmail.com>' Request was from Mathieu Malaterre <malat@debian.org> to control@bugs.debian.org. (Wed, 28 Mar 2012 13:54:39 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 16 Aug 2012 22:24:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 16 Aug 2012 22:24:03 GMT) Full text and rfc822 format available.

Message #131 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Fri, 17 Aug 2012 00:09:55 +0200
[Message part 1 (text/plain, inline)]
I don't know, if it helps to isolate the cause of the problem, but I've just stated that with kernel 3.5.2 my Vostro 3750 boots with USB device connected to USB 3.0 port, when I add the "pci=noacpi" 
parameter to the kernel commandline in grub.

Without that parameter booting hangs as previously.
I attach the acpidump after successfull booting enforced by adding of "pci=noacpi".
-- 
Regards,
Wojtek

[acpidump.gz (application/x-gzip, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 16 Aug 2012 22:24:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 16 Aug 2012 22:24:05 GMT) Full text and rfc822 format available.

Message #136 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Re: ACPI I/O resource conflicts with ACPI region SMBI
Date: Fri, 17 Aug 2012 00:17:37 +0200
I have also verified, that with 3.5.2 booted with "pci=noacpi"
the command "#echo disk>/sys/power/state" correctly suspends system to disk.
The operation is correctly resumed if I power on the system later on with the same kernel
and also with "pci=noacpi".

-- 
Regards,
Wojtek




Added tag(s) moreinfo. Request was from Ben Hutchings <ben@decadent.org.uk> to control@bugs.debian.org. (Mon, 20 Aug 2012 01:27:05 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Tue, 04 Sep 2012 06:45:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to wzab@ise.pw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 04 Sep 2012 06:45:06 GMT) Full text and rfc822 format available.

Message #143 received at 644174@bugs.debian.org (full text, mbox):

From: wzab <wzab@ise.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Probable cause of freeze of Dell Vostro 3750, when booting with device connected to USB 3.0 jack
Date: Tue, 04 Sep 2012 08:42:06 +0200
I have found some facts which hopefully may explain the problems with 
booting of Dell Vostro 3750.

1. The system hangs, when it attempts to service cooling devices 
controlled via SMBus
2. The SMBus controller and the USB 3.0 controller share the same IRQ 18 
line (is it a standard solution or design flaw?)
3. The interrupt service routine in the i2c-smbus.c driver seems not to
support shared interrupts.

All above findings are described in more detailed way in the bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=42844

particularly:
https://bugzilla.kernel.org/show_bug.cgi?id=42844#c11
https://bugzilla.kernel.org/show_bug.cgi?id=42844#c13
https://bugzilla.kernel.org/show_bug.cgi?id=42844#c15
https://bugzilla.kernel.org/show_bug.cgi?id=42844#c16

HTH & Regards,
Wojtek Zabolotny



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Tue, 04 Sep 2012 06:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to "wzabolot@elektron.elka.pw.edu.pl" <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 04 Sep 2012 06:51:03 GMT) Full text and rfc822 format available.

Message #148 received at 644174@bugs.debian.org (full text, mbox):

From: "wzabolot@elektron.elka.pw.edu.pl" <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Another related bug...
Date: Tue, 04 Sep 2012 08:46:42 +0200
If the diagnosis, that the problem is associated with sharing of IRQ 18 
between SMBus controller and XHCI controller, and with incorrect 
handling of shared interrupt by i2c-smbus.c driver is true,
then it could also explain the bug: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623004

Wojtek



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Tue, 04 Sep 2012 08:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 04 Sep 2012 08:51:03 GMT) Full text and rfc822 format available.

Message #153 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Not solved yet...
Date: Tue, 04 Sep 2012 10:49:16 +0200
Unfortunately my hope, that the problem is solved was too early.
The freeze problem seems to be associated not with the i2c-smbus
neither with i2c-i801 drivers, but with DRM drivers: i915 and nouveau.
-- 
Regards,
Wojtek



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 07 Sep 2012 20:21:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojciech Zabolotny <wzab01@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 07 Sep 2012 20:21:03 GMT) Full text and rfc822 format available.

Message #158 received at 644174@bugs.debian.org (full text, mbox):

From: Wojciech Zabolotny <wzab01@gmail.com>
To: 644174@bugs.debian.org
Subject: Problem still persists in kernel 3.6-rc4
Date: Fri, 7 Sep 2012 22:19:00 +0200
I've checked the newest version 3.6-rc4 and problem still exists.
System doesn't start when any USB device is connected to any USB 3.0 port :-(.



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 07 Sep 2012 22:09:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 07 Sep 2012 22:09:03 GMT) Full text and rfc822 format available.

Message #163 received at 644174@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Wojciech Zabolotny <wzab01@gmail.com>
Cc: 644174@bugs.debian.org, Mathieu Malaterre <mathieu.malaterre@gmail.com>
Subject: Re: DELL/Vostro 3750 fails to boot when devices plugged in USB 3.0 port
Date: Fri, 7 Sep 2012 15:07:53 -0700
Hi Wojtek,

Wojciech Zabolotny wrote:

> [Subject: Problem still persists in kernel 3.6-rc4]

Please keep in mind that these appear as emails in a crowded inbox, so
the subject line can be a good place to put valuable context.

> I've checked the newest version 3.6-rc4 and problem still exists.
> System doesn't start when any USB device is connected to any USB 3.0
> port :-(.

Thanks for checking.  Please file a new bug, including the usual
hardware information plus "acpidump" output.  If your and Mathieu's
cases turn out to have the same cause, we can merge them, but at the
moment I do not think we know enough to avoid tracking them
separately.

Thanks for your patience, and hope that helps.

Sincerely,
Jonathan



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 27 Dec 2012 17:06:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <malat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 27 Dec 2012 17:06:03 GMT) Full text and rfc822 format available.

Message #168 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <malat@debian.org>
To: Control bugs server <control@bugs.debian.org>
Cc: 644174@bugs.debian.org
Subject: Re:
Date: Thu, 27 Dec 2012 18:03:10 +0100
found 644174 3.7.1-1~experimental.1
thanks

I could reproduce the issue with latest kernel. Thx



Marked as found in versions 3.7.1-1~experimental.1. Request was from Mathieu Malaterre <malat@debian.org> to control@bugs.debian.org. (Thu, 27 Dec 2012 17:06:08 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 28 Dec 2012 23:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ben Hutchings <ben@decadent.org.uk>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 28 Dec 2012 23:51:03 GMT) Full text and rfc822 format available.

Message #175 received at 644174@bugs.debian.org (full text, mbox):

From: Ben Hutchings <ben@decadent.org.uk>
To: Mathieu Malaterre <malat@debian.org>, 644174@bugs.debian.org
Subject: Re: Bug#644174:
Date: Sat, 29 Dec 2012 00:46:10 +0100
[Message part 1 (text/plain, inline)]
On Thu, 2012-12-27 at 18:03 +0100, Mathieu Malaterre wrote:
> found 644174 3.7.1-1~experimental.1
> thanks
> 
> I could reproduce the issue with latest kernel. Thx

You never answered Jonathan's last questions:

> Hm.  Mathieu, is it possible to suspend-to-disk ("echo disk >/sys/power/state")
> and resume with a USB device plugged into the USB 3.0 port?
> 
> Please also attach output from "acpidump" after a successful boot.
> 
> Can you reproduce this when booting in recovery mode with
> i915.modeset=0 appended to the kernel command line?

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.
[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Sat, 29 Dec 2012 11:03:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <malat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 29 Dec 2012 11:03:03 GMT) Full text and rfc822 format available.

Message #180 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <malat@debian.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 644174@bugs.debian.org
Subject: Re: Bug#644174:
Date: Sat, 29 Dec 2012 11:58:07 +0100
[Message part 1 (text/plain, inline)]
On Sat, Dec 29, 2012 at 12:46 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Thu, 2012-12-27 at 18:03 +0100, Mathieu Malaterre wrote:
>> found 644174 3.7.1-1~experimental.1
>> thanks
>>
>> I could reproduce the issue with latest kernel. Thx
>
> You never answered Jonathan's last questions:

Ooops !

>> Hm.  Mathieu, is it possible to suspend-to-disk ("echo disk >/sys/power/state")
>> and resume with a USB device plugged into the USB 3.0 port?

Indeed this works flawlessly. Went to shell typed:

$ sudo su -
# echo disk >/sys/power/state

Waited until the cursor fade away. Computer automatically turned off.
Switched USB mouse from USB 2.0 port to USB 3.0. Turned on, no issue !
Mouse was working as should from USB 3.0 port.

>> Please also attach output from "acpidump" after a successful boot.

Attached.

>> Can you reproduce this when booting in recovery mode with
>> i915.modeset=0 appended to the kernel command line?

See result.jpg. The message (at least the last line) really looks like
what I get when booting in recovery mode.

Steps:
- Sytem > Shut down > Restart
From GRUB menu:
- select second line (recovery on a 3.2 bpo kernel)
- 'e'
- select line with "ro single"
- appended "915.modeset=0" right after the 'single' word (space separated).
- Ctrl+x


HTH
[result.jpg (image/jpeg, attachment)]
[acpidump.bin (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Sat, 19 Jan 2013 23:15:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to "wzabolot@elektron.elka.pw.edu.pl" <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 19 Jan 2013 23:15:03 GMT) Full text and rfc822 format available.

Message #185 received at 644174@bugs.debian.org (full text, mbox):

From: "wzabolot@elektron.elka.pw.edu.pl" <W.Zabolotny@elka.pw.edu.pl>
To: w.zabolotny@elka.pw.edu.pl
Cc: 644174@bugs.debian.org
Subject: Re: My system resumes from "suspend to disk" with FLASH disk connected to the USB 3.0 port, and starts with that disks if i915.modest=0 is given
Date: Sun, 20 Jan 2013 00:13:09 +0100
On 20.01.2013 00:01, Wojciech Zabołotny wrote:
> Hi,
>
> I've performed tests suggested by Jonathan in my system.
>
> 1st test:
>
> I have started the system, connected the FLASH disk to the USB 3.0 port
> and suspended it by "echo disk > /sys/power/state".
>
> Then I pressed the POWER button to switch the system on again, and it
> has resumed!
>
> Similarly, the system resumed after "Hibernate" triggered from the KDE
> menu.
>
>
> 2nd test:
>
> With "i915.modeset=0" my system started with FLASH disk connected to the
> USB 3.0 port
>
>
> I attach logs (dmesg) and acpidumps after both tests.

I've forgotten to add, that the tests were performed with the newest 
3.7.3 kernel.

-- 
Regards,
Wojtek




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Sat, 19 Jan 2013 23:15:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to w.zabolotny@elka.pw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 19 Jan 2013 23:15:06 GMT) Full text and rfc822 format available.

Message #190 received at 644174@bugs.debian.org (full text, mbox):

From: Wojciech Zabołotny <w.zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: My system resumes from "suspend to disk" with FLASH disk connected to the USB 3.0 port, and starts with that disks if i915.modest=0 is given
Date: Sun, 20 Jan 2013 00:01:45 +0100
[Message part 1 (text/plain, inline)]
Hi,

I've performed tests suggested by Jonathan in my system.

1st test:

I have started the system, connected the FLASH disk to the USB 3.0 port
and suspended it by "echo disk > /sys/power/state".

Then I pressed the POWER button to switch the system on again, and it 
has resumed!

Similarly, the system resumed after "Hibernate" triggered from the KDE menu.


2nd test:

With "i915.modeset=0" my system started with FLASH disk connected to the 
USB 3.0 port


I attach logs (dmesg) and acpidumps after both tests.
-- 
Regards,
Wojtek
[acpidump.after.resume.gz (application/x-gzip, attachment)]
[acpidump.after.start.with.modeset=0.gz (application/x-gzip, attachment)]
[logs.after.resume.gz (application/x-gzip, attachment)]
[logs.after.start.with.modeset=0.gz (application/x-gzip, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Mon, 21 Jan 2013 08:27:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mathieu Malaterre <malat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Mon, 21 Jan 2013 08:27:04 GMT) Full text and rfc822 format available.

Message #195 received at 644174@bugs.debian.org (full text, mbox):

From: Mathieu Malaterre <malat@debian.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 644174@bugs.debian.org
Subject: Re: Bug#644174:
Date: Mon, 21 Jan 2013 09:24:44 +0100
Answering myself.

On Sat, Dec 29, 2012 at 11:58 AM, Mathieu Malaterre <malat@debian.org> wrote:
> On Sat, Dec 29, 2012 at 12:46 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
>> On Thu, 2012-12-27 at 18:03 +0100, Mathieu Malaterre wrote:
>>> found 644174 3.7.1-1~experimental.1
>>> thanks
>>>
>>> I could reproduce the issue with latest kernel. Thx
>>
>> You never answered Jonathan's last questions:
>
> Ooops !
>
>>> Hm.  Mathieu, is it possible to suspend-to-disk ("echo disk >/sys/power/state")
>>> and resume with a USB device plugged into the USB 3.0 port?
>
> Indeed this works flawlessly. Went to shell typed:
>
> $ sudo su -
> # echo disk >/sys/power/state
>
> Waited until the cursor fade away. Computer automatically turned off.
> Switched USB mouse from USB 2.0 port to USB 3.0. Turned on, no issue !
> Mouse was working as should from USB 3.0 port.
>
>>> Please also attach output from "acpidump" after a successful boot.
>
> Attached.
>
>>> Can you reproduce this when booting in recovery mode with
>>> i915.modeset=0 appended to the kernel command line?
>
> See result.jpg. The message (at least the last line) really looks like
> what I get when booting in recovery mode.
>
> Steps:
> - Sytem > Shut down > Restart
> From GRUB menu:
> - select second line (recovery on a 3.2 bpo kernel)
> - 'e'
> - select line with "ro single"
> - appended "915.modeset=0" right after the 'single' word (space separated).

If I append "i915.modeset=0" then everything is fine on my side.,
sorry for the typo.

Thanks



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Wed, 06 Mar 2013 19:30:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 06 Mar 2013 19:30:08 GMT) Full text and rfc822 format available.

Message #200 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Problem still exists in kernel version 3.8.2
Date: Wed, 06 Mar 2013 20:11:53 +0100
i have just compiled and tested kernel 3.8.2.
It still hangs with a device connected to the USB 3.0 connector,
unless you use  "i915.modeset=0" as a kernel parameter

Booting with the above option is also not a viable workaround,
as it badly affects video performance...
-- 
Regards,
Wojtek



Removed tag(s) moreinfo. Request was from Ben Hutchings <ben@decadent.org.uk> to control@bugs.debian.org. (Mon, 11 Mar 2013 00:15:05 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Sun, 12 May 2013 09:12:09 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sun, 12 May 2013 09:12:09 GMT) Full text and rfc822 format available.

Message #207 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Linux kernel 3.9.2 - problem still exists :-(
Date: Sun, 12 May 2013 09:51:41 +0100
I have just compiled the newest 3.9.2 kernel.
Dell Vostro 3750 still doesn't boot when anything is connected to one of USB 3.0 connectors :-(.
-- 
WZab




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 25 Jul 2013 22:51:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 25 Jul 2013 22:51:04 GMT) Full text and rfc822 format available.

Message #212 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Kernel 3.10.2 - still hangs on Vostro 3750 when something is connected to any USB 3.0 port
Date: Fri, 26 Jul 2013 00:31:06 +0200
I have tried to switch to the newest stable kernel - 3.10.2
Unfortunately it still doesn't start when anything is connected to one of USB 3.0 ports...

-- 
Wojtek




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Fri, 16 Aug 2013 21:18:09 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 16 Aug 2013 21:18:09 GMT) Full text and rfc822 format available.

Message #217 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Some new details - system hangs when i915 module is loaded with modeset=1, after a device was connected to USB 3.0 port during boot
Date: Fri, 16 Aug 2013 23:15:21 +0200
Hi,

I've performed a few experiments (please see https://bugzilla.kernel.org/show_bug.cgi?id=42844 , comments 24-27), and found, that the system hangs when I load the i915 module with modeset=1, after any
device was connected to the USB 3.0 port during boot.

When I boot the system with i915.modeset=0 it starts always.
Later on I can reload the i915 module with modeset=1 to obtain full graphics performance.
( rmmod i915; modprobe i915 modeset=1)

However it any USB device WAS connected to one of USB 3.0 ports during the boot, the system hangs.
If no such device was present, the module gets loaded and the following messages are displayed and written to the system log:

[  384.308957] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[  384.308958] i915 0000:00:02.0: registered panic notifier
[  384.309174] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[  384.312570] acpi device:28: registered as cooling_device8
[  384.312637] ACPI: Video Device [PEGP] (multi-head: yes  rom: yes  post: no)
[  384.312741] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:27/LNXVIDEO:00/input/input15
[  384.340254] acpi device:2b: registered as cooling_device9
[  384.340447] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[  384.340537] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input16
[  384.340692] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[  385.088108] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

If the USB device was present, the last displayed messages are (of course time values may be different):

[  384.308957] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[  384.308958] i915 0000:00:02.0: registered panic notifier
[  384.309174] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS

I've compared results of acpidump, /proc/interrupts, /proc/iomem, /proc/ioports  and hanven't
found any significant difference between state of the system after booting with USB device in USB3.0 port and without such device...

-- 
Regards,
Wojtek




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Sun, 18 Aug 2013 09:51:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sun, 18 Aug 2013 09:51:05 GMT) Full text and rfc822 format available.

Message #222 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Logs from the ACPI, when system freezes after "modprobe i915 modeset=1" in "nosmp" mode
Date: Sun, 18 Aug 2013 11:46:43 +0200
Hi,

I've recorded (via netconsole) logs from the ACPI layer, when system was booted in the "nosmp" mode.
More details are provided at: https://bugzilla.kernel.org/show_bug.cgi?id=42844
and logs themselves are at: https://bugzilla.kernel.org/attachment.cgi?id=107235

-- 
Regards,
Wojtek

PS. On Dell community: http://en.community.dell.com/support-forums/laptop/f/3518/p/19461885/20163787.aspx
somebody has suggested that "The problem seems to be in the DSDT table, which can be fixed with updating the firmware Dell...", however she/he has not suggested which firmware should be updated. I run
my Vostro 3750 with newest version of all firmwares (in fact my USB3.0 controller uses even the newest version available from Renesas, newer than offered by Dell), and problem still persists :-(.




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Sun, 18 Aug 2013 22:00:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sun, 18 Aug 2013 22:00:05 GMT) Full text and rfc822 format available.

Message #227 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Another report about the same, or very similar bug
Date: Sun, 18 Aug 2013 23:56:08 +0200
Very similar problem related to hang if anything is connected to the USB 3.0 capable port
is reported here:  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/978891

It seems, that there are also other types of laptops affected (see comments #31, #34, #37 and #41)
-- 
Regards,
Wojtek




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#644174; Package linux-2.6. (Thu, 22 Aug 2013 22:57:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 22 Aug 2013 22:57:04 GMT) Full text and rfc822 format available.

Message #232 received at 644174@bugs.debian.org (full text, mbox):

From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: 644174@bugs.debian.org
Subject: Workaround "acpi_backlight=vendor" allows system to boot with USB device connected to the USB 3.0 port
Date: Fri, 23 Aug 2013 00:54:32 +0200
Hi,
I've checked old workarounds suggested in https://bugzilla.kernel.org/show_bug.cgi?id=42844
and have found, that the kernel parameter "acpi_backlight=vendor"  given by Lan Brown in https://bugzilla.kernel.org/show_bug.cgi?id=42844#c4 allows my system to boot with different USB devices
connected to the USB 3.0 port, with kernels 3.10.2 and 3.10.7 (probably it may also work for earlier kernels).

-- 

Regards,
Wojtek




Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Thu Apr 17 06:44:54 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.