[opensuse-kernel] 3.2 kernel stuck in early boot on core-i7
Hi, hardware is a lenovo-T410 with Intel Core-i7 CPU both, kernel-desktop from factory (3.2-rc6) and kerneltest/HEAD (3.2-rc7) get stuck in early boot printing 2 alternating lines scrolling too fast to read, something about dma fault. kerneltest/stable (3.1.6 and 3.1.7) boot fine. kerneltest/linux-next vanilla 3.2-rc6 oopses somewhere in device_attach/device_add kerneltest/vanilla 3.2-rc7 shows the same thing as the other 3.2based ones playing with the mobile to get some screen shots I get to read: DRAD: handling fault status reg 3 DMAR: [DMA Read] Request device [0d:00.0] fault addr fffff000 Any hints ? -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@suse.com,ro@suse.de,bugfinder@t-online.de) GPG Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 04/01/12 12:39, Ruediger Oertel wrote:
Hi,
hardware is a lenovo-T410 with Intel Core-i7 CPU both, kernel-desktop from factory (3.2-rc6) and kerneltest/HEAD (3.2-rc7) get stuck in early boot printing 2 alternating lines scrolling too fast to read, something about dma fault.
kerneltest/stable (3.1.6 and 3.1.7) boot fine. kerneltest/linux-next vanilla 3.2-rc6 oopses somewhere in device_attach/device_add kerneltest/vanilla 3.2-rc7 shows the same thing as the other 3.2based ones
playing with the mobile to get some screen shots I get to read: DRAD: handling fault status reg 3 DMAR: [DMA Read] Request device [0d:00.0] fault addr fffff000
Any hints ?
Does booting with intel_iommu=off makes it boot ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Am Mittwoch, 4. Januar 2012, 12:43:21 schrieb Cristian Rodríguez:
On 04/01/12 12:39, Ruediger Oertel wrote:
Hi,
hardware is a lenovo-T410 with Intel Core-i7 CPU both, kernel-desktop from factory (3.2-rc6) and kerneltest/HEAD (3.2-rc7) get stuck in early boot printing 2 alternating lines scrolling too fast to read, something about dma fault.
kerneltest/stable (3.1.6 and 3.1.7) boot fine. kerneltest/linux-next vanilla 3.2-rc6 oopses somewhere in device_attach/device_add kerneltest/vanilla 3.2-rc7 shows the same thing as the other 3.2based ones
playing with the mobile to get some screen shots I get to read: DRAD: handling fault status reg 3 DMAR: [DMA Read] Request device [0d:00.0] fault addr fffff000
Any hints ?
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million! and now ? known issue ?
-- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@suse.com,ro@suse.de,bugfinder@t-online.de) GPG Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 04/01/12 12:51, Ruediger Oertel wrote:
Am Mittwoch, 4. Januar 2012, 12:43:21 schrieb Cristian Rodríguez:
On 04/01/12 12:39, Ruediger Oertel wrote:
Hi,
hardware is a lenovo-T410 with Intel Core-i7 CPU both, kernel-desktop from factory (3.2-rc6) and kerneltest/HEAD (3.2-rc7) get stuck in early boot printing 2 alternating lines scrolling too fast to read, something about dma fault.
kerneltest/stable (3.1.6 and 3.1.7) boot fine. kerneltest/linux-next vanilla 3.2-rc6 oopses somewhere in device_attach/device_add kerneltest/vanilla 3.2-rc7 shows the same thing as the other 3.2based ones
playing with the mobile to get some screen shots I get to read: DRAD: handling fault status reg 3 DMAR: [DMA Read] Request device [0d:00.0] fault addr fffff000
Any hints ?
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million!
and now ? known issue ?
No idea if it known, I would try a bios update if any and reporting a bug. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million!
and now ? known issue ?
No idea if it known, I would try a bios update if any and reporting a bug. I'll try the BIOS update as I get closer to the power-supply (at home ...)
thanks, -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@suse.com,ro@suse.de,bugfinder@t-online.de) GPG Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 04/01/12 12:56, Cristian Rodríguez wrote:
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million!
Does intel_iommu=igfx_off work as well? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Wednesday, January 04, 2012 02:44:32 PM Cristian Rodríguez wrote:
On 04/01/12 12:56, Cristian Rodríguez wrote:
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million!
Does intel_iommu=igfx_off work as well?
actually no, that does not help (and would surprise me, the device the error messages are about is the integrated SD cardreader, and I do not have intel graphics but an nvidia chip). but I've tried the bios update as well, updated from 1.28 to 1.40 released december'11 and that did not change the issue. -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@suse.com,ro@suse.de,bugfinder@t-online.de) ------------------------------------------------------------------------- Linux T410Rudi 3.2.0-rc6-1-desktop #1 SMP PREEMPT Thu Dec 22 15:05:54 UTC 2011 (c4246bf) x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 04/01/12 17:38, Ruediger Oertel wrote:
On Wednesday, January 04, 2012 02:44:32 PM Cristian Rodríguez wrote:
On 04/01/12 12:56, Cristian Rodríguez wrote:
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million!
Does intel_iommu=igfx_off work as well?
actually no, that does not help (and would surprise me, the device the error messages are about is the integrated SD cardreader, and I do not have intel graphics but an nvidia chip).
but I've tried the bios update as well, updated from 1.28 to 1.40 released december'11 and that did not change the issue.
IS there any BIOS options to turn on/off virtualization ? if so, try off or On whatever is not the current state. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Wednesday, January 04, 2012 05:43:33 PM Cristian Rodríguez wrote:
On 04/01/12 17:38, Ruediger Oertel wrote:
On Wednesday, January 04, 2012 02:44:32 PM Cristian Rodríguez wrote:
On 04/01/12 12:56, Cristian Rodríguez wrote:
Does booting with intel_iommu=off makes it boot ?
BINGO ... thanks a million!
Does intel_iommu=igfx_off work as well?
actually no, that does not help (and would surprise me, the device the error messages are about is the integrated SD cardreader, and I do not have intel graphics but an nvidia chip).
but I've tried the bios update as well, updated from 1.28 to 1.40 released december'11 and that did not change the issue.
IS there any BIOS options to turn on/off virtualization ? if so, try off or On whatever is not the current state.
yep, disabling VT-d ("directed I/O" sounds pretty close to iommu to me) did help, after having that setting disabled in BIOS the kernel runs without any extra options. -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@suse.com,ro@suse.de,bugfinder@t-online.de) ------------------------------------------------------------------------- Linux T410Rudi 3.2.0-rc6-1-desktop #1 SMP PREEMPT Thu Dec 22 15:05:54 UTC 2011 (c4246bf) x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 04/01/12 20:29, Ruediger Oertel wrote:
yep, disabling VT-d ("directed I/O" sounds pretty close to iommu to me)
That's why I asked.. ;)
did help, after having that setting disabled in BIOS the kernel runs without any extra options.
Either BIOSes are screwed or the kernel is, I actually think both ;-( THis is probably worth a bug report. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Wed, Jan 4, 2012 at 16:33, Cristian Rodríguez
On 04/01/12 20:29, Ruediger Oertel wrote:
yep, disabling VT-d ("directed I/O" sounds pretty close to iommu to me)
That's why I asked.. ;)
did help, after having that setting disabled in BIOS the kernel runs without any extra options.
Either BIOSes are screwed or the kernel is, I actually think both ;-(
THis is probably worth a bug report.
I have the same issue on my w520. The w520 has the nvidia optimus, so both intel and nvidia. If I set it to have both video cards enabled I don't have this issue, but if I set it to nvidia I see the problem. Turning off VT-d and enabling nvidia doesn't reproduce this issue. -Stephen -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 05/01/12 19:24, Stephen Shaw wrote:
I have the same issue on my w520.
I also have a similar problem ... but the box works booting with nointremap .
The w520 has the nvidia optimus,so both intel and nvidia. If I set it to have both video cards enabled I don't have this issue, but if I set it to nvidia I see the problem. Turning off VT-d and enabling nvidia doesn't reproduce this issue.
what happends if you enable Intel and keep vt-d on ? (optimus is not supported by the kernel anyway....) Having both cards enabled lead to a different problem, battery life goes to hell. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 01/05/2012 11:24 PM, Stephen Shaw wrote:
On Wed, Jan 4, 2012 at 16:33, Cristian Rodríguez
wrote: On 04/01/12 20:29, Ruediger Oertel wrote:
yep, disabling VT-d ("directed I/O" sounds pretty close to iommu to me)
That's why I asked.. ;)
did help, after having that setting disabled in BIOS the kernel runs without any extra options.
Either BIOSes are screwed or the kernel is, I actually think both ;-(
THis is probably worth a bug report.
I have the same issue on my w520. The w520 has the nvidia optimus, so both intel and nvidia. If I set it to have both video cards enabled I don't have this issue, but if I set it to nvidia I see the problem. Turning off VT-d and enabling nvidia doesn't reproduce this issue.
-Stephen
Same here with a Dell M4600 precision (after reading this threads I get hope to be able to run 3.2) I believe more in a regression inside the kernel, knowing that 3.1 was working without any trouble. At least I'm running only with the nvidia, but the trouble exist with nouveau and nvidia blob (even new 295.06) I've added manually iommu_intel=on on my bootline time ago, I will now remove it. ps for Christian Rodriguez, sorry I will never kill my nvidia chipset, and replace it by the intel one. except if I goes to a kernel hacker summit. I'm a big addicted of wobbling windows, and nouveau can't do it ... :D -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 01/06/2012 06:41 PM, Bruno Friedmann wrote:
On 01/05/2012 11:24 PM, Stephen Shaw wrote:
On Wed, Jan 4, 2012 at 16:33, Cristian Rodríguez
wrote: On 04/01/12 20:29, Ruediger Oertel wrote:
yep, disabling VT-d ("directed I/O" sounds pretty close to iommu to me)
That's why I asked.. ;)
did help, after having that setting disabled in BIOS the kernel runs without any extra options.
Either BIOSes are screwed or the kernel is, I actually think both ;-(
THis is probably worth a bug report.
I have the same issue on my w520. The w520 has the nvidia optimus, so both intel and nvidia. If I set it to have both video cards enabled I don't have this issue, but if I set it to nvidia I see the problem. Turning off VT-d and enabling nvidia doesn't reproduce this issue.
-Stephen
Same here with a Dell M4600 precision (after reading this threads I get hope to be able to run 3.2)
I believe more in a regression inside the kernel, knowing that 3.1 was working without any trouble. At least I'm running only with the nvidia, but the trouble exist with nouveau and nvidia blob (even new 295.06) I've added manually iommu_intel=on on my bootline time ago, I will now remove it.
ps for Christian Rodriguez, sorry I will never kill my nvidia chipset, and replace it by the intel one. except if I goes to a kernel hacker summit.
I'm a big addicted of wobbling windows, and nouveau can't do it ... :D
only working with iommu_intel=off and get kind of strange errors [ 391.753635] WARNING: at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.2.rc6/linux-3.2-rc6/net/sched/sch_generic.c:255 dev_watchdog+0x249/0x260() [ 391.753642] Hardware name: Precision M4600 [ 391.753647] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out [ 391.753651] Modules linked in: fuse rfcomm bnep nfs lockd fscache auth_rpcgss nfs_acl sunrpc af_packet cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq mperf quota_v2 quota_tree nvidia(P) snd_hda_codec_hdmi arc4 uvcvideo snd_hda_codec_idt videodev iwlwifi sdhci_pci dell_laptop snd_hda_intel mac80211 snd_hda_codec snd_hwdep snd_pcm snd_timer firewire_ohci v4l2_compat_ioctl32 sdhci firewire_core dcdbas kvm_intel joydev snd cdrom pciehp iTCO_wdt dell_wmi mmc_core btusb sg cfg80211 i2c_i801 bluetooth iTCO_vendor_support e1000e pci_hotplug mei(C) kvm soundcore crc_itu_t rfkill snd_page_alloc serio_raw sparse_keymap battery button video wmi ac microcode autofs4 sha256_generic dm_crypt dm_mod linear raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid10 raid1 raid0 xhci_hcd aesni_intel cryptd aes_x86_64 fan processor thermal thermal_sys [ 391.753796] Pid: 0, comm: swapper/0 Tainted: P C O 3.2.0-rc6-3-desktop #1 [ 391.753801] Call Trace: [ 391.753826] [<ffffffff810043da>] dump_trace+0xaa/0x2b0 [ 391.753841] [<ffffffff815a58ff>] dump_stack+0x69/0x6f [ 391.753857] [<ffffffff81055d1b>] warn_slowpath_common+0x7b/0xc0 [ 391.753869] [<ffffffff81055e15>] warn_slowpath_fmt+0x45/0x50 [ 391.753879] [<ffffffff814bcef9>] dev_watchdog+0x249/0x260 [ 391.753892] [<ffffffff81064b48>] call_timer_fn+0x48/0x1d0 [ 391.753902] [<ffffffff810655f5>] run_timer_softirq+0x125/0x2b0 [ 391.753914] [<ffffffff8105d2da>] __do_softirq+0xaa/0x280 [ 391.753927] [<ffffffff815c952c>] call_softirq+0x1c/0x30 [ 391.753936] [<ffffffff81004245>] do_softirq+0x65/0xa0 [ 391.753947] [<ffffffff8105d7ee>] irq_exit+0x8e/0xd0 [ 391.753960] [<ffffffff8101fdd8>] smp_apic_timer_interrupt+0x68/0xa0 [ 391.753972] [<ffffffff815c7d9e>] apic_timer_interrupt+0x6e/0x80 [ 391.753989] [<ffffffff81321d52>] intel_idle+0xf2/0x170 [ 391.754002] [<ffffffff8145d586>] cpuidle_idle_call+0xb6/0x330 [ 391.754016] [<ffffffff8100119d>] cpu_idle+0x7d/0xd0 [ 391.754028] [<ffffffff81d59baa>] start_kernel+0x3a6/0x3b1 [ 391.754038] [<ffffffff81d59434>] x86_64_start_kernel+0xd1/0xe0 [ 391.754047] ---[ end trace 4ea8e89b2e2b1309 ]--- [ 391.754080] e1000e 0000:00:19.0: eth0: Reset adapter [ 395.667720] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 857.596528] eth0: no IPv6 routers present I've never has been hit by that kind of error for the eth module -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 04.01.2012 17:39, Ruediger Oertel wrote:
Hi,
hardware is a lenovo-T410 with Intel Core-i7 CPU both, kernel-desktop from factory (3.2-rc6) and kerneltest/HEAD (3.2-rc7) get stuck in early boot printing 2 alternating lines scrolling too fast to read, something about dma fault.
kerneltest/stable (3.1.6 and 3.1.7) boot fine. kerneltest/linux-next vanilla 3.2-rc6 oopses somewhere in device_attach/device_add kerneltest/vanilla 3.2-rc7 shows the same thing as the other 3.2based ones
playing with the mobile to get some screen shots I get to read: DRAD: handling fault status reg 3 DMAR: [DMA Read] Request device [0d:00.0] fault addr fffff000
Any hints ?
A popular 3.2 problem: http://www.phoronix.com/scan.php?page=news_item&px=MTAzNzk -- Ozan Caglayan Pardus Linux http://www.pardus.org.tr/eng -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (5)
-
Bruno Friedmann
-
Cristian Rodríguez
-
Ozan Çağlayan
-
Ruediger Oertel
-
Stephen Shaw