Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
CrustOffline
Post subject: Kernel panic with 3.1-0.slh.1-aptosid-686 for i5  PostPosted: 24.10.2011, 18:36



Joined: 2010-09-12
Posts: 30

Status: Offline
Hi everyone,

Updating to the new kernel caused kernel panics related to DMAR. Disabling all virtualization options in the bios allowed the kernel to boot. The latest 3.x kernels have all been quite unstable for me, but disabling the virtualization options seems to improve stability as well. There is talk about kernel options such as intel_iommu=off helping with this issue, but I haven't tried these options.

Here's some hardware info in case it helps:

Host/Kernel/OS "xxxxx" running Linux 3.1-0.slh.1-aptosid-686 i686 [ sidux 2010-01 Ύπνος - kde-lite - (201006131622) ]
CPU Info 4x Intel Core i5 M 520 @ 3072 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 1199.000 MHz ]
Videocard Intel Core Processor Integrated Graphics Controller X.Org 1.11.1.901 [ 1280x800@60.1hz ]
Network cards Intel 82577LM Gigabit
Intel Centrino Advanced-N 6200
Processes 144 | Uptime 5min | Memory 498.2/3477.0MB | HDD SAMSUNG SSD PM80 Size 256GB (39%used) | Client Shell | Infobash v3.37



-Crust
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Kernel panic with 3.1-0.slh.1-aptosid-686 for i5  PostPosted: 24.10.2011, 18:58



Joined: 2010-08-25
Posts: 749

Status: Offline
kernel-parameters.txt
      Code:
        intel_iommu=    [DMAR] Intel IOMMU driver (DMAR) option
                on
                        Enable intel iommu driver.
                off
                        Disable intel iommu driver.
                igfx_off [Default Off]
                        By default, gfx is mapped as normal device. If a gfx
                        device has a dedicated DMAR unit, the DMAR unit is
                        bypassed by not enabling DMAR with this option. In
                        this case, gfx device will use physical address for
                        DMA.
                forcedac [x86_64]
                        With this option iommu will not optimize to look
                        for io virtual address below 32-bit forcing dual
                        address cycle on pci bus for cards supporting greater
                        than 32-bit addressing. The default is to look
                        for translation below 32-bit and if not available
                        then look in the higher range.
                strict [Default Off]
                        With this option on every unmap_single operation will
                        result in a hardware IOTLB flush operation as opposed
                        to batching them for performance.
                sp_off [Default Off]
                        By default, super page will be supported if Intel IOMMU
                        has the capability. With this option, super page will
                        not be supported

Try the kernel parameters (off in particular), I don't have VT-d capable hardware for testing and can't debug it myself; therefore the panic message itself would be quite interesting as well.
 
 View user's profile Send private message  
Reply with quote Back to top
CrustOffline
Post subject: RE: Kernel panic with 3.1-0.slh.1-aptosid-686 for i5  PostPosted: 24.10.2011, 19:21



Joined: 2010-09-12
Posts: 30

Status: Offline
slh,

I've found that I can enable VT-d, but have to disable VT-d direct IO. I'll try the kernel parameters when I get a chance.

How do I pause the screen to write down the messages? The errors scroll too fast to check. Scroll lock does not work.

I believe the errors are the same as what is reported here:

http://www.spinics.net/lists/kernel/msg1252574.html

      Code:
DMAR:[DMA Read] Request device [??:??.?] fault addr ????????
DRHD: handling fault status reg ?


I put the question marks above because I'm not sure if the numbers are identical.

I'm not sure what changed, but 3.0.7 was unstable, but it still booted - had many random freezes, but 3.1.0 does not even boot -> disabling VT direct IO has stabilized everything.

I'll report back on findings when I get a chance.

I found this bug report which describes the problem (even though it has nothing to do with a Ricoh multifunctional device)

https://bugzilla.redhat.com/show_bug.cgi?id=605888
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Kernel panic with 3.1-0.slh.1-aptosid-686 for i5  PostPosted: 24.10.2011, 22:37



Joined: 2010-08-25
Posts: 749

Status: Offline
Pause or scroll lock might work, using a digital camera could also help.

That lkml message, well at least the referenced RedHat bugzilla, points quite a bit towards hardware (BIOS-) bugs (interestingly all reports seem to affect i5-520m CPUs as well) - are you running the newest BIOS version for your notebook?

Unless today's lkml post leads to new discoveries or patches, the only fix would be to disable VT-d support (DMAR) completely, the same you could already do now by supplying intel_iommu=off to your kernel. However VT-d is something not to give up easily, as it provides quite some functionality for capable hardware. Interestingly DMAR was already enabled on our i386 kernels for quite some time, without any according negative reports, therefore I'm currently soliciting internal feedback for i7-860, i7-920 and i7-2720QM , which should support VT-d as well. From the larger mainstream distros, at least RedHat/ Fedora appears to default to DMAR as well (at least since Fedora 13, iow for more than a year by now).
 
 View user's profile Send private message  
Reply with quote Back to top
diblOffline
Post subject: Re: RE: Kernel panic with 3.1-0.slh.1-aptosid-686 for i5  PostPosted: 25.10.2011, 00:41



Joined: 2010-09-12
Posts: 302
Location: Dayton, Ohio, USA
Status: Offline
      slh wrote:
I'm currently soliciting internal feedback for i7-860, i7-920 and i7-2720QM , which should support VT-d as well.


Core i7-950 here, on Asus P6X58D-E system board:

      Code:
Host/Kernel/OS  "aptosidbox" running Linux 3.1-0.slh.1-aptosid-amd64 x86_64 [ aptosid 2011-02 Ἡμέρα - kde-lite - (201107131633) ]         
CPU Info        8x Intel Core i7 950 @ 8192 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 1600.000 MHz ]                               
Videocard       nVidia GF100 [GeForce GTX 480]  X.Org 1.11.1.901  [ 1920x1200@50.0hz ]                                                     
Network cards   Marvell 88E8056 PCI-E Gigabit                                                                                             
Processes 287 | Uptime 3min | Memory 824.7/6030.9MB | HDD OCZ-REVODRIVE,OCZ-REVODRIVE,KINGSTON SS100S2 Size 138GB (45%used) | GLX Renderer GeForce GTX 480/PCI/SSE2 | GLX Version 4.1.0 NVIDIA 275.28 | Client Shell | Infobash v3.37


I have been running this system with Intel VT-d disabled. So tonight I enabled it and updated to the 3.1 kernel. I didn't get a panic, but it wasn't pretty, either. In the first shot, it hangs at this point for about 20 seconds (sorry for the bad focus):



then it goes on like this, and finishes booting:



I rebooted 3 times -- it is very consistent. Here is the relevant section of dmesg:

      Code:
[    0.954708] Unpacking initramfs...
[    1.132509] Freeing initrd memory: 11252k freed
[    1.134061] IOMMU 0 0xfbfff000: using Queued invalidation
[    1.134063] IOMMU 1 0xfbffe000: using Queued invalidation
[    1.134067] ------------[ cut here ]------------
[    1.134073] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:4024 intel_iommu_init+0x58c/0x9ec()
[    1.134074] Hardware name: System Product Name
[    1.134076] Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space.
[    1.134077] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134078] Modules linked in:
[    1.134081] Pid: 1, comm: swapper Not tainted 3.1-0.slh.1-aptosid-amd64 #1
[    1.134082] Call Trace:
[    1.134087]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134089]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134092]  [<ffffffff815976a8>] ? intel_iommu_init+0x58c/0x9ec
[    1.134095]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134097]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134100]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134103]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134106]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134108]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134111]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134116] ---[ end trace bb26011d21a2b1cd ]---
[    1.134129] IOMMU: hardware identity mapping for device 0000:00:1b.0
[    1.134146] IOMMU: Setting RMRR:
[    1.134155] IOMMU: Setting identity map for device 0000:00:1d.0 [0xbf7dc000 - 0xbf7dbfff]
[    1.134156] ------------[ cut here ]------------
[    1.134160] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134161] Hardware name: System Product Name
[    1.134163] Your BIOS is broken; RMRR ends before it starts!
[    1.134163] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134165] Modules linked in:
[    1.134166] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134168] Call Trace:
[    1.134170]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134172]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134174]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134177]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134179]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134181]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134183]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134185]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134187]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134190]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134192]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134193] ---[ end trace bb26011d21a2b1ce ]---
[    1.134200] IOMMU: mapping reserved region failed
[    1.134257] IOMMU: Setting identity map for device 0000:00:1d.1 [0xbf7dc000 - 0xbf7dbfff]
[    1.134259] ------------[ cut here ]------------
[    1.134261] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134263] Hardware name: System Product Name
[    1.134264] Your BIOS is broken; RMRR ends before it starts!
[    1.134265] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134266] Modules linked in:
[    1.134268] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134269] Call Trace:
[    1.134271]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134273]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134275]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134278]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134280]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134282]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134284]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134286]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134288]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134290]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134292]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134294] ---[ end trace bb26011d21a2b1cf ]---
[    1.134299] IOMMU: mapping reserved region failed
[    1.134355] IOMMU: Setting identity map for device 0000:00:1d.2 [0xbf7dc000 - 0xbf7dbfff]
[    1.134356] ------------[ cut here ]------------
[    1.134358] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134360] Hardware name: System Product Name
[    1.134361] Your BIOS is broken; RMRR ends before it starts!
[    1.134362] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134363] Modules linked in:
[    1.134365] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134366] Call Trace:
[    1.134368]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134370]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134372]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134375]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134377]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134379]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134381]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134383]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134385]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134388]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134390]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134391] ---[ end trace bb26011d21a2b1d0 ]---
[    1.134395] IOMMU: mapping reserved region failed
[    1.134451] IOMMU: Setting identity map for device 0000:00:1d.7 [0xbf7dc000 - 0xbf7dbfff]
[    1.134452] ------------[ cut here ]------------
[    1.134454] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134456] Hardware name: System Product Name
[    1.134457] Your BIOS is broken; RMRR ends before it starts!
[    1.134458] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134459] Modules linked in:
[    1.134461] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134462] Call Trace:
[    1.134464]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134466]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134469]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134471]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134473]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134475]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134477]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134479]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134481]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134484]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134486]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134487] ---[ end trace bb26011d21a2b1d1 ]---
[    1.134492] IOMMU: mapping reserved region failed
[    1.134556] IOMMU: Setting identity map for device 0000:00:1a.0 [0xbf7dc000 - 0xbf7dbfff]
[    1.134557] ------------[ cut here ]------------
[    1.134560] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134561] Hardware name: System Product Name
[    1.134563] Your BIOS is broken; RMRR ends before it starts!
[    1.134564] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134565] Modules linked in:
[    1.134566] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134568] Call Trace:
[    1.134570]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134572]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134574]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134577]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134579]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134581]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134583]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134585]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134587]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134589]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134592]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134593] ---[ end trace bb26011d21a2b1d2 ]---
[    1.134598] IOMMU: mapping reserved region failed
[    1.134653] IOMMU: Setting identity map for device 0000:00:1a.1 [0xbf7dc000 - 0xbf7dbfff]
[    1.134654] ------------[ cut here ]------------
[    1.134657] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134658] Hardware name: System Product Name
[    1.134660] Your BIOS is broken; RMRR ends before it starts!
[    1.134660] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134661] Modules linked in:
[    1.134663] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134664] Call Trace:
[    1.134666]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134668]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134671]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134673]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134675]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134677]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134679]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134681]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134684]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134686]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134688]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134689] ---[ end trace bb26011d21a2b1d3 ]---
[    1.134694] IOMMU: mapping reserved region failed
[    1.134749] IOMMU: Setting identity map for device 0000:00:1a.2 [0xbf7dc000 - 0xbf7dbfff]
[    1.134750] ------------[ cut here ]------------
[    1.134753] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134754] Hardware name: System Product Name
[    1.134756] Your BIOS is broken; RMRR ends before it starts!
[    1.134756] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134758] Modules linked in:
[    1.134759] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134760] Call Trace:
[    1.134762]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134764]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134767]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134769]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134771]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134773]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134775]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134777]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134780]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134782]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134784]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134785] ---[ end trace bb26011d21a2b1d4 ]---
[    1.134790] IOMMU: mapping reserved region failed
[    1.134845] IOMMU: Setting identity map for device 0000:00:1a.7 [0xbf7dc000 - 0xbf7dbfff]
[    1.134847] ------------[ cut here ]------------
[    1.134849] WARNING: at /tmp/buildd/linux-aptosid-3.1/debian/build/source_amd64_none/drivers/iommu/intel-iommu.c:2119 iommu_prepare_identity_map+0xf5/0x1a1()
[    1.134850] Hardware name: System Product Name
[    1.134852] Your BIOS is broken; RMRR ends before it starts!
[    1.134852] BIOS vendor: American Megatrends Inc.; Ver: 0602   ; Product Version: System Version
[    1.134854] Modules linked in:
[    1.134855] Pid: 1, comm: swapper Tainted: G        W   3.1-0.slh.1-aptosid-amd64 #1
[    1.134857] Call Trace:
[    1.134859]  [<ffffffff8103c46d>] ? warn_slowpath_common+0x78/0x8c
[    1.134861]  [<ffffffff8103c519>] ? warn_slowpath_fmt+0x45/0x4a
[    1.134863]  [<ffffffff81304d99>] ? iommu_prepare_identity_map+0xf5/0x1a1
[    1.134865]  [<ffffffff8159788e>] ? intel_iommu_init+0x772/0x9ec
[    1.134868]  [<ffffffff8156ba87>] ? memblock_find_dma_reserve+0x30/0x30
[    1.134870]  [<ffffffff8156ba95>] ? pci_iommu_init+0xe/0x37
[    1.134871]  [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c
[    1.134874]  [<ffffffff81565c21>] ? kernel_init+0xd8/0x152
[    1.134876]  [<ffffffff81309d34>] ? kernel_thread_helper+0x4/0x10
[    1.134878]  [<ffffffff81565b49>] ? start_kernel+0x3b8/0x3b8
[    1.134880]  [<ffffffff81309d30>] ? gs_change+0x13/0x13
[    1.134881] ---[ end trace bb26011d21a2b1d5 ]---
[    1.134886] IOMMU: mapping reserved region failed
[    1.134941] IOMMU: Setting identity map for device 0000:00:1d.0 [0xec000 - 0xeffff]
[    1.134971] IOMMU: Setting identity map for device 0000:00:1d.1 [0xec000 - 0xeffff]
[    1.134997] IOMMU: Setting identity map for device 0000:00:1d.2 [0xec000 - 0xeffff]
[    1.135022] IOMMU: Setting identity map for device 0000:00:1d.7 [0xec000 - 0xeffff]
[    1.135047] IOMMU: Setting identity map for device 0000:00:1a.0 [0xec000 - 0xeffff]
[    1.135070] IOMMU: Setting identity map for device 0000:00:1a.1 [0xec000 - 0xeffff]
[    1.135094] IOMMU: Setting identity map for device 0000:00:1a.2 [0xec000 - 0xeffff]
[    1.135117] IOMMU: Setting identity map for device 0000:00:1a.7 [0xec000 - 0xeffff]
[    1.135135] IOMMU: Prepare 0-16MiB unity mapping for LPC
[    1.135144] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[    1.135269] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
[    1.137080] audit: initializing netlink socket (disabled)
[    1.137087] type=2000 audit(1319502346.834:1): initialized


Another issue -- it totally lost the pair of SATA 6GB/s hard drives that are on the Marvell controller. They don't show up with fdisk at all.

Hope this helps -- I'm turning VT-d back off now.
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
slhOffline
Post subject: RE: Re: RE: Kernel panic with 3.1-0.slh.1-aptosid-686 for i5  PostPosted: 25.10.2011, 02:04



Joined: 2010-08-25
Posts: 749

Status: Offline
Please test 3.1-0.slh.2-aptosid-amd64 - and I'd also be very interested if "iommu=off" would work as well with 3.1-0.slh.2-aptosid-amd64 (so please don't delete it yet) .
 
 View user's profile Send private message  
Reply with quote Back to top
diblOffline
Post subject:   PostPosted: 25.10.2011, 13:03



Joined: 2010-09-12
Posts: 302
Location: Dayton, Ohio, USA
Status: Offline
After d-u, I turned VT-d on and booted 3.1-0.slh.2-aptosid-amd64, with no special boot codes. It was very fast and I saw no issues during boot. Here is the relevant section of dmesg:

      Code:
[    0.002930] CPU0: Thermal monitoring enabled (TM1)
[    0.002938] using mwait in idle threads.
[    0.003246] ACPI: Core revision 20110623
[    0.032162] DMAR: Host address width 39
[    0.032164] DMAR: DRHD base: 0x000000fbfff000 flags: 0x0
[    0.032173] IOMMU 0: reg_base_addr fbfff000 ver 1:0 cap c9008010e60262 ecap f0207a
[    0.032175] DMAR: DRHD base: 0x000000fbffe000 flags: 0x1
[    0.032182] IOMMU 1: reg_base_addr fbffe000 ver 1:0 cap c90780106f0462 ecap f020fe
[    0.032184] DMAR: RMRR base: 0x000000000ec000 end: 0x000000000effff
[    0.032186] DMAR: RMRR base: 0x000000bf7dc000 end: 0x000000bf7dbfff
[    0.032187] DMAR: ATSR flags: 0x0
[    0.032296] IOAPIC id 8 under DRHD base  0xfbffe000 IOMMU 1
[    0.032298] IOAPIC id 9 under DRHD base  0xfbffe000 IOMMU 1
[    0.032540] Enabled Interrupt-remapping
[    0.032544] Switched APIC routing to physical flat.
[    0.033054] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.043052] CPU0: Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz stepping 05
[    0.144745] Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
[    0.144751] ... version:     3




Leaving the VT-d enabled in BIOS, neither 3.1-0.slh.1-aptosid-amd64 nor 3.1-0.slh.2-aptosid-amd64 can boot with "iommu=off". I never saw "kernel panic" but I saw "IOMMU_MAP..." and "ATA_13..." errors flying by for 20 - 30 seconds and no progress on the boot.

So, 3.1-0.slh.2-aptosid-amd64 with plain vanilla boot codes is working well with VT-d enabled, on this hardware.
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
BodOffline
Post subject:   PostPosted: 25.10.2011, 16:37



Joined: 2011-04-18
Posts: 11

Status: Offline
With booting me writing this error:

Waiting for /dev to be fully populated...[ 5.685530] cfg80211: failed to add phy80211 symlink to netdev!

Kernel 3.1-0.slh.1-aptosid-686 and Kernel 3.1-0.slh.2-aptosid-686.

My workstation - Laptop HP Compaq nw8240
 
 View user's profile Send private message  
Reply with quote Back to top
snvvOffline
Post subject:   PostPosted: 25.10.2011, 16:54



Joined: 2010-09-13
Posts: 295

Status: Offline
Linux aptosidbox 3.1-0.slh.2-aptosid-amd64 #1 SMP PREEMPT Tue Oct 25 01:47:47 UTC 2011 x86_64 GNU/Linux

No problem at all, both in 64 and 32 bit PC's
Regards
snvv
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject:   PostPosted: 25.10.2011, 17:01



Joined: 2010-08-25
Posts: 749

Status: Offline
      Bod wrote:
With booting me writing this error:

Waiting for /dev to be fully populated...[ 5.685530] cfg80211: failed to add phy80211 symlink to netdev!

Kernel 3.1-0.slh.1-aptosid-686 and Kernel 3.1-0.slh.2-aptosid-686.

My workstation - Laptop HP Compaq nw8240
Please keep different issues separate (new topic) and go a bit more into depth (what are practical effects/ breakage, full dmesg, a little more about your hardware/ wlan card, etc. pp.), it's easier to follow the debugging it that way
 
 View user's profile Send private message  
Reply with quote Back to top
BodOffline
Post subject:   PostPosted: 25.10.2011, 17:09



Joined: 2011-04-18
Posts: 11

Status: Offline
      Quote:

Please keep different issues separate (new topic) and go a bit more into depth (what are practical effects/ breakage, full dmesg, a little more about your hardware/ wlan card, etc. pp.), it's easier to follow the debugging it that way


Thank you. I thought it was a problem the new kernel. Since the old (3.0) this problem did not exist.

dmesg: http://pastebin.com/WRMxndqP

WAN:
Broadcom NetXtreme BCM5751M Gigabit
Intel PRO/Wireless ipw2200BG

Sorry, I did not understand where to create a new topic. Produce branches in this section of the forum (Upgrade Warnings)?
 
 View user's profile Send private message  
Reply with quote Back to top
arwaOffline
Post subject:   PostPosted: 25.10.2011, 21:33



Joined: 2010-09-11
Posts: 183

Status: Offline
I did dare to update my system. It seems to boot and run fine (for the few minutes uptime now Wink ).
      Code:

infobash -v3
Host/Kernel/OS  "flupp" running Linux 3.1-0.slh.2-aptosid-amd64 x86_64 [ aptosid 2011-01 Γῆρας - xfce - (201102051540) ]       
CPU Info        8x Intel Core i7-2600K @ 8192 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 1600.000 MHz ]                   
Videocard       Intel 2nd Generation Core Processor Family Integrated Graphics Controller  X.Org 1.11.1.901  [ 1280x1024@60.0hz, 1280x1024@60.0hz ]                                                                                                             
Network cards   Realtek RTL8111/8168B PCI Express Gigabit                                                                       
Processes 236 | Uptime 2min | Memory 1078.1/7909.3MB | HDD Corsair CSSD-F11,ST31000524AS Size 1115GB (13%used) | Client Shell | Infobash v3.37                                                                                                                 
 
 View user's profile Send private message  
Reply with quote Back to top
detaosOffline
Post subject:   PostPosted: 25.10.2011, 23:06
Team Member


Joined: 2010-08-26
Posts: 166
Location: floating in the ether
Status: Offline
no problem here:
      Code:

$ infobash -v3
Host/Kernel/OS  "core" running Linux 3.1-0.slh.2-aptosid-amd64 x86_64 [ aptosid 2010-02 Κῆρες - kde-lite - (201009132215) ]
CPU Info        8x Intel Core i7 860 @ 8192 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 1200.000 MHz ]
Videocard       ATI Juniper XT [AMD Radeon HD 6000 Series]  X.Org 1.11.1.901  [ 1600x1200@60.0hz, 1280x1024@60.0hz ]
Network cards   Realtek RTL8111/8168B PCI Express Gigabit
Processes 188 | Uptime 2min | Memory 586.0/7982.4MB | HDD OCZ-VERTEX2,WDC WD1002FAEX-0 Size 1050GB (7%used) | GLX Renderer Gallium 0.4 on AMD JUNIPER | GLX Version Yes | Client Shell | Infobash v3.37

      Code:

$ dmesg | grep -i dmar
[    0.000000] ACPI: DMAR 00000000bf7880c0 00090 (v01    AMI  OEMDMAR 00000001 MSFT 00000097)
[    0.110577] DMAR: Host address width 36
[    0.110579] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
[    0.110588] DMAR: RMRR base: 0x000000000e4000 end: 0x000000000e7fff
[    0.110590] DMAR: RMRR base: 0x000000bf7ec000 end: 0x000000bf7fffff
[    0.110591] DMAR: No ATSR found

_________________
#aptosid-art ftw!
(what would cleary do?)
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
CrustOffline
Post subject:   PostPosted: 26.10.2011, 07:01



Joined: 2010-09-12
Posts: 30

Status: Offline
To the others posting in this thread:

I want to be clear that this bug report is very specific to sandy bridge processors with vt-d enabled. Please post details on the processor and whether virtualization is enable and especially if "VT for direct IO" is enabled. This is the specific setting that causes issues on my computer.

slh,

I've updated the bios - this has not changed the error.
pause or scroll lock didn't help, but the digital camera did.

Here is the output that is repeated constantly - I've tried leaving the computer to see if it would boot if left for hours - it doesn't boot.

      Code:

DMAR:[DMA Read] Request device [03.00.0]fault addr fffff000
DMAR:[fault reason 02] Present bit in context entry is clear
DRHD: handling fault status reg 3


The above errors keep on repeating so quickly I couldn't even read them without using my camera to freeze the screen.

I don't know if this helps.
 
 View user's profile Send private message  
Reply with quote Back to top
CrustOffline
Post subject:   PostPosted: 26.10.2011, 07:04



Joined: 2010-09-12
Posts: 30

Status: Offline
If found that the device that is causing the bug is:

      Code:

03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 03)


With the bug report in the original post and this bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=634135

Perhaps there is a big issue with Ricoh SD host controllers and VT-d
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio