Bug#644174: Twoje konto skrzynki e-mail musi zostać teraz zweryfikowane

[Jane Magoola Yoyeta]

WAŻNE POWIADOMIENIE MICROSOFT

Twoje konto skrzynki pocztowej musi zostać natychmiast 
zweryfikowane, w przeciwnym razie 
konto skrzynki pocztowej zostanie zawieszone, jeśli nie zostanie teraz 
zweryfikowane.


Dziękuję za Twoje zrozumienie


Zespół weryfikacyjny Microsoft

?




This e-mail and its attachments contain confidential information from UBOS, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
completely delete it!

Bug#644174: Twoje konto skrzynki e-mail musi zostać teraz zweryfikowane

[Rojas Lorena (SALTA)]

WAŻNE POWIADOMIENIE MICROSOFT

Twoje konto skrzynki pocztowej musi zostać natychmiast 
zweryfikowane, w przeciwnym razie 
konto skrzynki pocztowej zostanie zawieszone, jeśli nie zostanie teraz 
zweryfikowane.


Dziękuję za Twoje zrozumienie


Zespół weryfikacyjny Microsoft

Bug#644174:

[Mathieu Malaterre]

Control: tags -1 upstream

Just for reference. I have been using the work-around documented at:

https://bugs.debian.org/644174#232

And it is working just fine on my laptop.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174:

[Mathieu Malaterre]

Control: reassign -1 linux-image-3.2.0-4-amd64

$ apt-cache policy linux-image-3.2.0-4-amd64
linux-image-3.2.0-4-amd64:
  Installed: 3.2.60-1+deb7u3
  Candidate: 3.2.60-1+deb7u3
  Version table:
 *** 3.2.60-1+deb7u3 0
700 http://security.debian.org/ wheezy/updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.2.57-3 0
700 http://ftp.fr.debian.org/debian/ wheezy/main amd64 Packages


Still present on my machine.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Workaround "acpi_backlight=vendor" allows system to boot with USB device connected to the USB 3.0 port

[Wojtek Zabolotny]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Another report about the same, or very similar bug

[Wojtek Zabolotny]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Logs from the ACPI, when system freezes after "modprobe i915 modeset=1" in "nosmp" mode

[Wojtek Zabolotny]

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 :-(.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: 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

[Wojtek Zabolotny]

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 :00:02.0: fb0: inteldrmfb frame buffer device
[  384.308958] i915 :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 :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 :00:02.0: fb0: inteldrmfb frame buffer device
[  384.308958] i915 :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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Kernel 3.10.2 - still hangs on Vostro 3750 when something is connected to any USB 3.0 port

[Wojtek Zabolotny]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Linux kernel 3.9.2 - problem still exists :-(

[Wojtek Zabolotny]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Problem still exists in kernel version 3.8.2

[Wojtek Zabolotny]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174:

[Mathieu Malaterre]

Answering myself.

On Sat, Dec 29, 2012 at 11:58 AM, Mathieu Malaterre  wrote:
> On Sat, Dec 29, 2012 at 12:46 AM, Ben Hutchings  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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: 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

[wzabo...@elektron.elka.pw.edu.pl]

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174:

[Ben Hutchings]

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
Description: This is a digitally signed message part

Bug#644174:

[Mathieu Malaterre]

found 644174 3.7.1-1~experimental.1
thanks

I could reproduce the issue with latest kernel. Thx


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: DELL/Vostro 3750 fails to boot when devices plugged in USB 3.0 port

[Jonathan Nieder]

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Problem still persists in kernel 3.6-rc4

[Wojciech Zabolotny]

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 :-(.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Not solved yet...

[Wojtek Zabolotny]

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Another related bug...

[wzabo...@elektron.elka.pw.edu.pl]

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Probable cause of freeze of Dell Vostro 3750, when booting with device connected to USB 3.0 jack

[wzab]

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Wojtek Zabolotny]

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


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Jonathan Nieder]

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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Sarah Sharp]

On Wed, Dec 28, 2011 at 06:11:14PM +0100, Mathieu Malaterre wrote:
> On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp
>  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  
> >> 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 :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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: DELL/Vostro 3750 fails to boot when devices plugged in USB 3.0 port

[Jonathan Nieder]

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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Info received (Bug#644174: Info received ())

[Mathieu Malaterre]

Looks like this is a duplicate of 623004



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Info received ()

[Mathieu Malaterre]

Some more info. Running linux 3.0.2 eventually leads to:


[  484.679306] BUG: scheduling while atomic: swapper/0/0x1100
[  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:[]  []
intel_idle+0xea/0x119
[  484.679625] RSP: 0018:81601e88  EFLAGS: 0202
[  484.679630] RAX:  RBX: 811a5bfc RCX: 17b6
[  484.679636] RDX: 17b6 RSI:  RDI: 03e8
[  484.679641] RBP: 0004 R08: 17ba R09: 17ba
[  484.679647] R10: 81780640 R11: 81601fd8 R12: 8801bfa0e700
[  484.679652] R13: 8801bfa0e710 R14: 8801ad3c3ac8 R15: 8801bfa0e7f0
[  484.679659] FS:  () GS:8801bfa0()
knlGS:
[  484.679666] CS:  0010 DS:  ES:  CR0: 8005003b
[  484.679671] CR2: 0240b471 CR3: 01605000 CR4: 000406f0
[  484.679677] DR0:  DR1:  DR2: 
[  484.679683] DR3:  DR6: 0ff0 DR7: 0400
[  484.679689] Process swapper (pid: 0, threadinfo 8160,
task 8160d020)
[  484.679694] Stack:
[  484.679697]   17b6 

[  484.679708]  17b6 005caf48 8801bfa19870
81644a80
[  484.679718]  fff0 0004 81644bc0
8125bdf3
[  484.679728] Call Trace:
[  484.679741]  [] ? cpuidle_idle_call+0xec/0x179
[  484.679753]  [] ? cpu_idle+0xa1/0xe8
[  484.679764]  [] ? start_kernel+0x3bd/0x3c8
[  484.679773]  [] ? early_idt_handlers+0x140/0x140
[  484.679782]  [] ? 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]  [] ? cpuidle_idle_call+0xec/0x179
[  484.679874]  [] ? cpu_idle+0xa1/0xe8
[  484.679882]  [] ? start_kernel+0x3bd/0x3c8
[  484.679891]  [] ? early_idt_handlers+0x140/0x140
[  484.679899]  [] ? x86_64_start_kernel+0x104/0x111
[  545.528641] BUG: scheduling while atomic: swapper/0/0x1100
[  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_stora

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Mathieu Malaterre]

On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp
 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  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-...@vger.kernel.org, cc-ing Sarah Sharp
>> >    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 :03:00.0: WARN: short transfer on control ep
[  158.756522] xhci_hcd :03:00.0: WARN: short transfer on control ep
[  158.757426] xhci_hcd :03:00.0: WARN: short transfer on control ep
[  158.758299] xhci_hcd :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 :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 

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Sarah Sharp]

On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote:
> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder  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-...@vger.kernel.org, cc-ing Sarah Sharp
> >    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 :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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Jonathan Nieder]

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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174:

[Mathieu Malaterre]

Adding lspci + lshw output from 3.2.0-rc4-amd64, mouse on USB 2.0.
maester
description: Computer
width: 64 bits
capabilities: vsyscall32
  *-core
   description: Motherboard
   physical id: 0
 *-memory
  description: System memory
  physical id: 0
  size: 5902MiB
 *-cpu
  product: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
  vendor: Intel Corp.
  physical id: 1
  bus info: cpu@0
  size: 800MHz
  capacity: 800MHz
  width: 64 bits
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts nopl 
xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
xsave avx lahf_lm ida arat epb xsaveopt pln pts tpr_shadow vnmi flexpriority 
ept vpid cpufreq
 *-pci
  description: Host bridge
  product: Sandy Bridge DRAM Controller
  vendor: Intel Corporation
  physical id: 100
  bus info: pci@:00:00.0
  version: 09
  width: 32 bits
  clock: 33MHz
  configuration: driver=agpgart-intel
  resources: irq:0
*-pci:0
 description: PCI bridge
 product: Sandy Bridge PCI Express Root Port
 vendor: Intel Corporation
 physical id: 1
 bus info: pci@:00:01.0
 version: 09
 width: 32 bits
 clock: 33MHz
 capabilities: pci normal_decode bus_master cap_list
 configuration: driver=pcieport
 resources: irq:40 ioport:4000(size=4096) memory:f000-f10f 
ioport:c000(size=301989888)
   *-display UNCLAIMED
description: VGA compatible controller
product: nVidia Corporation
vendor: nVidia Corporation
physical id: 0
bus info: pci@:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: vga_controller bus_master cap_list
configuration: latency=0
resources: memory:f000-f0ff memory:c000-cfff 
memory:d000-d1ff ioport:4000(size=128) memory:f100-f107
*-display
 description: VGA compatible controller
 product: Sandy Bridge Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:43 memory:f140-f17f 
memory:e000-efff ioport:5000(size=64)
*-communication UNCLAIMED
 description: Communication controller
 product: Cougar Point HECI Controller #1
 vendor: Intel Corporation
 physical id: 16
 bus info: pci@:00:16.0
 version: 04
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: latency=0
 resources: memory:f2b05000-f2b0500f
*-usb:0
 description: USB Controller
 product: Cougar Point USB Enhanced Host Controller #2
 vendor: Intel Corporation
 physical id: 1a
 bus info: pci@:00:1a.0
 version: 05
 width: 32 bits
 clock: 33MHz
 capabilities: ehci bus_master cap_list
 configuration: driver=ehci_hcd latency=0
 resources: irq:16 memory:f2b0a000-f2b0a3ff
*-multimedia
 description: Audio device
 product: Cougar Point High Definition Audio Controller
 vendor: Intel Corporation
 physical id: 1b
 bus info: pci@:00:1b.0
 version: 05
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:45 memory:f2b0-f2b03fff
*-pci:1
 description: PCI bridge
 product: Cougar Point PCI Express Root Port 1
 vendor: Intel Corporation
 physical id: 1c
 bus info: pci@:00:1c.0
 version: b5
 width: 32 bits
 clock: 33MHz
 capabilities: pci normal_decode bus_master cap_list
 configuration: driver=pcieport
 resources: irq:16 memory:f2a0-f2af
   *-network
description: Wireless interface
product: Intel Corporation
   

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Mathieu Malaterre]

On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder  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-...@vger.kernel.org, cc-ing Sarah Sharp
>    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



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174:

[Mathieu Malaterre]

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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Jonathan Nieder]

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-...@vger.kernel.org, cc-ing Sarah Sharp
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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174:

[Mathieu Malaterre]

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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#644174: Fwd: Debian 64-bit an Dell Vostro 3750 - freezes sometimes with message [Firmware Bug] ACPI(PEGP) dedefines _DOD but not _DOS

[Mathieu Malaterre]

> and then a lot of messages:
>
> Oct 30 20:27:48 WZLap kernel: [ 609.270026] xhci_hcd :03:00.0: WARN: 
> Stalled endpoint
> Oct 30 20:27:48 WZLap kernel: [ 609.274685] xhci_hcd :03:00.0: WARN: 
> Stalled endpoint
> Oct 30 20:27:48 WZLap kernel: [ 609.281701] xhci_hcd :03:00.0: WARN: 
> Stalled endpoint
> Oct 30 20:27:48 WZLap kernel: [ 609.285046] xhci_hcd :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 :-)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

[Mathieu Malaterre]

On Fri, Oct 7, 2011 at 6:49 AM, Ben Hutchings  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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

[Ben Hutchings]

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 :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
Description: This is a digitally signed message part

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)

[Jonathan Nieder]

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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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)

[Jonathan Nieder]

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 :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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

[Mathieu Malaterre]

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 :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) (da...@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.1Debian 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-tools3.12-1  tools for managing Linux kernel mo

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

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

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

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org