Bug 25402 - kernel (2.6.37-8-generic_amd64) panic on boot (with message "map_single: bounce buffer is not DMA'ble) - possible regression !!!
kernel (2.6.37-8-generic_amd64) panic on boot (with message "map_single: boun...
Status: CLOSED CODE_FIX
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64
All Linux
: P1 high
Assigned To: platform_x86_64@kernel-bugs.osdl.org
:
Depends on:
Blocks: 21782
  Show dependency treegraph
 
Reported: 2010-12-21 19:58 UTC by carlos
Modified: 2011-03-06 12:29 UTC (History)
7 users (show)

See Also:
Kernel Version: 2.6.37-rc1 to 2.6.38rc4
Tree: Mainline
Regression: Yes


Attachments

Description carlos 2010-12-21 19:58:49 UTC
I've detected this possible regression when upgrading from Ubuntu 10.10
(Kernel 2.6.35-24) to Ubuntu Natty A1 (2.6.37-rc1).
Kernel 2.6.36-2 also works perfectly, which could indicate that a possible regression exists between 2.6.36-2 and 2.6.37-rc1 (2.6.37-rc6 has the same problem).

The problem: 
The booting process crashes at the beginning (the PC simply doesn't respond) with the following Kernel Panic Msg (written by hand because none registered on log files):
 "map_single: bounce buffer is not DMA'ble"
 Network manager not Tainted ...
 ?panic+0xbf/0x200
 ?default_spin_lock_flags+0x9/0x10
 ?swiotlb_map_single+0x1ce/0x250
 ?map_single+0x46/0x60
 ?swiotlb_map_page++0x0/0xf0
...

A few interesting boot messages change between 2.6.36 and 2.637 are:
1) 
 2.6.36-2 (and prior): "Scanning 1 areas for low memory corruption"
 2.6.36-rc1 (and after): "Scanning 0 areas for low memory corruption"
2)
 RAMDISK gives <> quantities
3)
it stops logging data on last line bellow (ACPI: DSDT doesn't show in 2.6.37)
RAMDISK: 37571000 - 37ff0000
ACPI: RSDP 00000000000fbbf0 00024 (v02 DELL  )
ACPI: XSDT 00000000dfe6f200 0005C (v01 DELL    M08     27D80415 ASL  00000061)
ACPI: FACP 00000000dfe6f09c 000F4 (v04 DELL    M08     27D80415 ASL  00000061)
ACPI: DSDT 00000000dfe6f800 05658 (v02 INT430 SYSFexxx 00001001 INTL 20050624)

Could it be a DELL firmware problem (it already has last BIOS) ?
Also reported in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/688383

Machine (DELL Vostro 1700, 4GB RAM; Bios A07)
Comment 1 Rafael J. Wysocki 2010-12-21 23:18:36 UTC
Does it also happen with 2.6.37-rc7 ?
Comment 2 carlos 2010-12-22 00:24:01 UTC
N(In reply to comment #1)
> Does it also happen with 2.6.37-rc7 ?

Not yet tested.
But according to the new rc7 log,
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=log;h=90a8a73c06cc32b609a880d48449d7083327e11a)

these regression, introduced in 2.6.37-rc1
(according to bug: https://bugzilla.kernel.org/show_bug.cgi?id=16228),
will disappear in the new 2.6.37-rc7.

I will say something tomorrow.
Thanks, Rafael.
Comment 3 carlos 2010-12-22 20:22:36 UTC
(In reply to comment #1)
> Does it also happen with 2.6.37-rc7 ?

YES. With similar behavior. With slightly <> changes on the screen boot messages (I can send a photo if required).
Now even crashes before showing RAMDISK row as shown below part of the log (kern.log):


[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.37-11-generic (buildd@crested) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-1ubuntu2) ) #25-Ubuntu SMP Tue Dec 21 23:42:56 UTC 2010 (Ubuntu 2.6.37-11.25-generic 2.6.37-rc7)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=f14ffa00-1f27-4753-84de-c06aa7431a26 ro single splash vga=788
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[    0.000000]  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 00000000dfe6d800 (usable)
[    0.000000]  BIOS-e820: 00000000dfe6d800 - 00000000e0000000 (reserved)
[    0.000000]  BIOS-e820: 00000000f4000000 - 00000000f8000000 (reserved)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
[    0.000000]  BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
[    0.000000]  BIOS-e820: 0000000100002000 - 0000000120000000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI 2.4 present.
[    0.000000] DMI: 0HX767/Vostro 1700                     , BIOS A07 04/21/2008
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[    0.000000] No AGP bridge found
[    0.000000] last_pfn = 0x120000 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-CFFFF write-protect
[    0.000000]   D0000-EFFFF uncachable
[    0.000000]   F0000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
<< ...here kernel panic with a crash ... and hard reboot only >>
 
<>With Kernel 2.6.35 (and 2.6.36) is the same and continues ...up to the login>>
[    0.000000] Linux version 2.6.35-24-generic (buildd@yellow) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 (Ubuntu 2.6.35-24.42-generic 2.6.35.8)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=f14ffa00-1f27-4753-84de-c06aa7431a26 ro splash vga=788 vt.handoff=7 quiet splash
... 
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 000000000 mask F80000000 write-back
[    0.000000]   1 base 080000000 mask FC0000000 write-back
[    0.000000]   2 base 0C0000000 mask FE0000000 write-back
[    0.000000]   3 base 100000000 mask F00000000 write-back
[    0.000000]   4 base 0DFF00000 mask FFFF00000 uncachable
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] e820 update range: 00000000dff00000 - 0000000100000000 (usable) ==> (reserved)
[    0.000000] last_pfn = 0xdfe6d max_arch_pfn = 0x400000000
[    0.000000] e820 update range: 0000000000001000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] modified physical RAM map:
[    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
[    0.000000]  modified: 0000000000010000 - 000000000009f000 (usable)
[    0.000000]  modified: 000000000009f000 - 00000000000a0000 (reserved)
[    0.000000]  modified: 0000000000100000 - 00000000dfe6d800 (usable)
[    0.000000]  modified: 00000000dfe6d800 - 00000000e0000000 (reserved)
[    0.000000]  modified: 00000000f4000000 - 00000000f8000000 (reserved)
[    0.000000]  modified: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  modified: 00000000fed18000 - 00000000fed1c000 (reserved)
[    0.000000]  modified: 00000000fed20000 - 00000000fed90000 (reserved)
[    0.000000]  modified: 00000000feda0000 - 00000000feda6000 (reserved)
[    0.000000]  modified: 00000000fee00000 - 00000000fee10000 (reserved)
[    0.000000]  modified: 00000000fff00000 - 0000000100000000 (reserved)
[    0.000000]  modified: 0000000100002000 - 0000000120000000 (usable)
[    0.000000] initial memory mapped : 0 - 20000000
[    0.000000] init_memory_mapping: 0000000000000000-00000000dfe6d000
[    0.000000]  0000000000 - 00dfe00000 page 2M
[    0.000000]  00dfe00000 - 00dfe6d000 page 4k
[    0.000000] kernel direct mapping tables up to dfe6d000 @ 16000-1c000
[    0.000000] init_memory_mapping: 0000000100000000-0000000120000000
[    0.000000]  0100000000 - 0120000000 page 2M
[    0.000000] kernel direct mapping tables up to 120000000 @ 1a000-20000
[    0.000000] RAMDISK: 3683c000 - 37416000
[    0.000000] ACPI: RSDP 00000000000fbbf0 00024 (v02 DELL  )
[    0.000000] ACPI: XSDT 00000000dfe6f200 0005C (v01 DELL    M08     27D80415 ASL  00000061)
[    0.000000] ACPI: FACP 00000000dfe6f09c 000F4 (v04 DELL    M08     27D80415 ASL  00000061)
[    0.000000] ACPI: DSDT 00000000dfe6f800 05658 (v02 INT430 SYSFexxx 00001001 INTL 20050624)
[    0.000000] ACPI: FACS 00000000dfe7e000 00040
[    0.000000] ACPI: HPET 00000000dfe6f300 00038 (v01 DELL    M08     00000001 ASL  00000061)
[    0.000000] ACPI: APIC 00000000dfe6f400 00068 (v01 DELL    M08     27D80415 ASL  00000047)
[    0.000000] ACPI: MCFG 00000000dfe6f3c0 0003E (v16 DELL    M08     27D80415 ASL  00000061)
[    0.000000] ACPI: SLIC 00000000dfe6f49c 00176 (v01 DELL    M08     27D80415 ASL  00000061)
[    0.000000] ACPI: BOOT 00000000dfe6efc0 00028 (v01 DELL    M08     27D80415 ASL  00000061)
[    0.000000] ACPI: SSDT 00000000dfe6d97a 004CC (v01  PmRef    CpuPm 00003000 INTL 20050624)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
....
Comment 4 Rafael J. Wysocki 2010-12-30 22:52:06 UTC
On Thursday, December 30, 2010, carlos palma wrote:
> I can confirm that this "regression" still exists with the kernel 
> 2.6.37-rc8.
> The Call Trace is basically the same:
> 
> ...
> Kernel panic - not syncing: map_single ...
> Pid 935, comm: NetworkManager Tainted
> call trace
> panic+oxbf/0x200
> ? default_spin_lock_flags+0x9/0x10
> ?swiotlb_tlb_map_single+0x1ce/0x250
> ?map_single+0x46/0x60
> swiotlb_map_page+0xa6/0xf
> ... and then the FREEZE ... only a hard reset brings to live (with 
> 2.6.36-2) Linux.
Comment 5 carlos 2011-01-08 22:12:45 UTC
kernel 2.6.37 (stable) still have the same kernel boot panic/hang (with all kb lights blinking).

Kernel 2.6.36.3 works fine.

carlos
Comment 6 carlos 2011-01-19 00:07:21 UTC
Additional INFO:
I believe that is the driver b44 (Broadcom Corporation BCM4401-B0 Ethernet card)
that is giving boot kernel panic.
Same bug in (https://bugzilla.redhat.com/show_bug.cgi?id=668088)

I can boot 2.6.37 (stable) if the LAN card is deactivated on the BIOS.
carlos
Comment 7 carlos 2011-02-04 21:56:53 UTC
There is already a patch to this b44 regression 
Proposed in: http://groups.google.com/group/linux.kernel/browse_thread/thread/184c7cd190ae7b5a?pli=1
I hope this one goes to the next rc ...
Thanks.
Comment 8 Florian Mickler 2011-02-05 08:42:41 UTC
Do you mean the patch from FUJITA Tomonori (https://patchwork.kernel.org/patch/522971/)? Does it work for you?
Comment 9 Al 2011-02-06 19:58:29 UTC
I can confirm same panic with b43 which is resolved using the above patch.
Comment 10 carlos 2011-02-08 19:57:59 UTC
(In reply to comment #8)
> Do you mean the patch from FUJITA Tomonori
> (https://patchwork.kernel.org/patch/522971/)? Does it work for you?

Yes, that one.
I haven't checked yet on my DELL Vostro 1700 (the one using b44).
I am trying to get some free time to check it... soon.
Comment 11 Florian Mickler 2011-02-09 05:37:10 UTC
@carlos: Please do. 

Patch: https://patchwork.kernel.org/patch/522971/
Comment 12 carlos 2011-02-13 00:22:43 UTC
Finally some time ...
I also confirm that the FUJITA patch works perfectly (patch over the 2.6.38-rc4).
The b44 (Broadcom Corporation BCM4401-B0 card) is working like in the old (2.6.36) days.
thanks

cpalma@carlosLT:~$ uname -a
Linux carlosLT 2.6.38-rc4-custom+ #2 SMP Sun Feb 13 00:53:47 CET 2011 x86_64 x86_64 x86_64 GNU/Linux
cpalma@carlosLT:~$ grep -i b44 /var/log/dmesg
[    1.503623] b44 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    1.620939] b44: b44.c:v2.0
[    1.660844] b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:1c:23:98:eb:8e
cpalma@carlosLT:~$ grep -i b44 /var/log/kern.log
Feb 13 01:04:23 carlosLT kernel: [    1.503623] b44 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Feb 13 01:04:23 carlosLT kernel: [    1.620939] b44: b44.c:v2.0
Feb 13 01:04:23 carlosLT kernel: [    1.660844] b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT ...
 
(In reply to comment #11)
> @carlos: Please do. 
> 
> Patch: https://patchwork.kernel.org/patch/522971/
Comment 13 Rafael J. Wysocki 2011-02-21 22:24:23 UTC
Handled-By : FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Comment 14 Rafael J. Wysocki 2011-03-06 12:29:32 UTC
Fixed by commit fba99fa38b023224680308a482e12a0eca87e4e1 .

Note You need to log in before you can comment on or make changes to this bug.