WARNING: at /build/buildd/linux-2.6.32/arch/x86/mm/ioremap.c:135 __ioremap_caller+0x398/0x3d0()

Bug #625134 reported by Karri Huhtanen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The external USB storage devices which worked with latest Ubuntu 8.04 LTS kernel with my Intel Atom motherboard D945GCLF do not and have not worked with any of the Ubuntu 10.04 LTS kernels.

The kernel or usb storage system seems to detect the disks:

[ 6.527082] usb-storage: device scan complete
[ 6.530626] scsi 4:0:0:0: Direct-Access Generic External 2.10 PQ: 0 ANSI: 4
[ 6.532067] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 6.540445] sd 4:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 6.541315] sd 4:0:0:0: [sdc] Write Protect is off
[ 6.541327] sd 4:0:0:0: [sdc] Mode Sense: 21 00 00 00
[ 6.541335] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 6.543197] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 6.543251] sdc: sdc1
[ 6.673254] usb-storage: device scan complete

but after a while it seems to have problems with the USB port, where the disk is connected:

[ 41.095765] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 44.180046] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 47.250043] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 50.320038] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 50.320334] usb 1-1: USB disconnect, address 2
[ 50.320371] sd 4:0:0:0: Device offlined - not ready after error recovery
[ 50.320397] sd 4:0:0:0: [sdc] Unhandled error code
[ 50.320405] sd 4:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK[ 50.320416] sd 4:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 00 3f 00 00 08 00
[ 50.320445] end_request: I/O error, dev sdc, sector 63
[ 50.320672] Buffer I/O error on device sdc1, logical block 0
[ 50.320908] Buffer I/O error on device sdc1, logical block 1
[ 50.321143] Buffer I/O error on device sdc1, logical block 2
[ 50.321382] Buffer I/O error on device sdc1, logical block 3
[ 50.321619] Buffer I/O error on device sdc1, logical block 4
[ 50.321853] Buffer I/O error on device sdc1, logical block 5
[ 50.322089] Buffer I/O error on device sdc1, logical block 6
[ 50.322319] Buffer I/O error on device sdc1, logical block 7
[ 53.420038] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 56.480034] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 59.540053] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 62.600045] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?

I tried already several different cables, disks and USB ports with the same result. After these messages the disk just does not seem to exist anymore. It did not seem to matter if the disk was connected at the boot time or after boot time, the result was the same.

This does not seem to be a hardware problem since by booting to Ubuntu 8.04 LTS from installation disk, those same USB devices work properly.

There however exists these kind of AGP related messages in the dmesg:

[ 7.162541] agpgart-intel 0000:00:00.0: Intel 945G Chipset
[ 7.162723] resource map sanity check conflict: 0x88180000 0x881bffff 0x88180000 0x8819ffff 0000:00:02.0
[ 7.162730] ------------[ cut here ]------------
[ 7.162744] WARNING: at /build/buildd/linux-2.6.32/arch/x86/mm/ioremap.c:135 __ioremap_caller+0x398/0x3d0()
[ 7.162751] Hardware name:
[ 7.162754] Info: mapping multiple BARs. Your kernel is fine.
[ 7.162759] Modules linked in: intel_agp(+) serio_raw output wire parport xfs exportfs raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov usb_storage raid6_pq async_tx floppy e1000 raid1 raid0 multipath linear
[ 7.162802] Pid: 399, comm: modprobe Not tainted 2.6.32-24-server #41-Ubuntu
[ 7.162807] Call Trace:
[ 7.162821] [<ffffffff81066dab>] warn_slowpath_common+0x7b/0xc0
[ 7.162830] [<ffffffff81066e51>] warn_slowpath_fmt+0x41/0x50
[ 7.162839] [<ffffffff81041358>] __ioremap_caller+0x398/0x3d0
[ 7.162855] [<ffffffffa01aa1f6>] ? intel_i915_create_gatt_table+0x86/0x150 [intel_agp]
[ 7.162866] [<ffffffff812c97d9>] ? pci_bus_read_config_dword+0x79/0x90
[ 7.162875] [<ffffffff810414a7>] ioremap_nocache+0x17/0x20
[ 7.162887] [<ffffffffa01aa1f6>] intel_i915_create_gatt_table+0x86/0x150 [intel_agp]
[ 7.162897] [<ffffffff81349f39>] agp_backend_initialize+0x119/0x3e0
[ 7.162905] [<ffffffff8134a2d5>] agp_add_bridge+0xa5/0x260
[ 7.162916] [<ffffffffa01ab9a4>] agp_intel_probe+0x2f2/0x31d [intel_agp]
[ 7.162926] [<ffffffff812d0757>] local_pci_probe+0x17/0x20
[ 7.162934] [<ffffffff812d0a79>] __pci_device_probe+0xe9/0xf0
[ 7.162944] [<ffffffff812b55ea>] ? kobject_get+0x1a/0x30
[ 7.162954] [<ffffffff81368b39>] ? get_device+0x19/0x20
[ 7.162962] [<ffffffff812d18a7>] pci_device_probe+0x37/0x60
[ 7.162971] [<ffffffff8136cc15>] really_probe+0x65/0x170
[ 7.162979] [<ffffffff8136cd65>] driver_probe_device+0x45/0x70
[ 7.162987] [<ffffffff8136cd90>] ? __driver_attach+0x0/0xa0
[ 7.162995] [<ffffffff8136ce2b>] __driver_attach+0x9b/0xa0
[ 7.163004] [<ffffffff8136cd90>] ? __driver_attach+0x0/0xa0
[ 7.163012] [<ffffffff8136c078>] bus_for_each_dev+0x68/0x90
[ 7.163020] [<ffffffff8136ca8e>] driver_attach+0x1e/0x20
[ 7.163028] [<ffffffff8136c34e>] bus_add_driver+0xde/0x280
[ 7.163036] [<ffffffff8136d160>] driver_register+0x80/0x150
[ 7.163046] [<ffffffff8155d966>] ? notifier_call_chain+0x56/0x80
[ 7.163054] [<ffffffff812d1b36>] __pci_register_driver+0x56/0xd0
[ 7.163064] [<ffffffff8108a475>] ? __blocking_notifier_call_chain+0x65/0x80
[ 7.163075] [<ffffffffa01b2000>] ? agp_intel_init+0x0/0x2e [intel_agp]
[ 7.163086] [<ffffffffa01b202c>] agp_intel_init+0x2c/0x2e [intel_agp]
[ 7.163096] [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1a0
[ 7.163107] [<ffffffff810a14ff>] sys_init_module+0xdf/0x260
[ 7.163116] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[ 7.163123] ---[ end trace 5f58de49491212f5 ]---

but I am unsure this is related to the usb storage problem.

I have been waiting to see if some kernel or other upgrade would have fixed the problem, but decided now to report it since I could not find a similar enough bug or a fix from the database.

If you have some suggestions I can test them. I was thinking of checking those mainline kernel builds next, if there are not any suggestions for using for example different kernel parameters?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-server 2.6.32-24.41
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.41-server 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-server x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Fri Aug 27 09:01:07 2010
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-server root=UUID=33611c05-f20c-4571-bb22-1c4c22c1f109 ro splash quiet
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 04/14/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LF94510J.86A.0278.2010.0414.2000
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D945GCLF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27042-305
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLF94510J.86A.0278.2010.0414.2000:bd04/14/2010:svn:pn:pvr:rvnIntelCorporation:rnD945GCLF:rvrAAE27042-305:cvn:ct3:cvr:

Revision history for this message
Karri Huhtanen (khuhtanen) wrote :
Revision history for this message
Michael Lueck (mlueck) wrote :

I was sifting through dmesg output just now on my 10.04 server with an Intel Atom D945GCLF MB and came upon the same "ioremap.c:135 Warning" as reported here.

@Karri Huhtanen: lsusb "wakes up" Linux to the presence of the USB storage device on my server, using IOGear boxes. Another work-around is needed to wake up a client's near identical server / the client has different USB drives.

Seems to be we are reporting the same thing. My bug is:

"USB HDD and Flash Drives no longer recognized"
https://bugs.launchpad.net/bugs/645211

BTW: When 10.04 first came out USB storage was working. Somewhere along the way it broke. I backleveled my server all the way back to the kernel that was installed at the time USB storage last worked, and was unable to get it to work again. My thought is that something besides the kernel along has caused this problem.

Revision history for this message
Karri Huhtanen (khuhtanen) wrote :

I managed to get the USB drives working when I upgraded to 10.10 version of Ubuntu Server. It seems that there is somekind of better combination of kernel, usb libraries or whatever.

Revision history for this message
Michael Lueck (mlueck) wrote :

I was able to come up with a script workaround to correct this problem. I posted the script here in #23

"USB HDD and Flash Drives no longer recognized"
https://bugs.launchpad.net/bugs/645211

So I run that EACH TIME I attach a USB storage device to our server, THEN the server will detect it.

Also there have been comments in that thread that supposedly the problem has been fixed in the x64 version of Ubuntu 10.04, however yet remains in the x86 version.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Karri Huhtanen, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

summary: - external usb storage does not work with intel D945GCLF motherboard
+ WARNING: at /build/buildd/linux-2.6.32/arch/x86/mm/ioremap.c:135
+ __ioremap_caller+0x398/0x3d0()
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.