vmap allocation errors after resuming

[Joshua Kugler]

Today, after resuming from hibernate, my USB devices were not working. Unplugging/plugging showed this in the syslog:

May 26 10:00:31 hosanna kernel: [151083.256100] usb 3-2: USB disconnect, address 4
May 26 10:00:33 hosanna kernel: [151084.984028] usb 3-2: new low speed USB device using uhci_hcd and address 5
May 26 10:00:33 hosanna kernel: [151085.160091] usb 3-2: configuration #1 chosen from 1 choice
May 26 10:00:33 hosanna kernel: [151085.185495] vmap allocation failed: use vmalloc=<size> to increase size.
May 26 10:00:33 hosanna kernel: [151085.185944] generic-usb: probe of 0003:046D:C404.0011 failed with error -12

I'm going to try to add vmap=256MB to the kernel boot options and see if that resolves it.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=f2b981aa-2494-46e3-89b0-0b6804954d14
MachineType: Dell Inc. MP061
Package: linux-image-2.6.28-12-generic 2.6.28-12.43
ProcCmdLine: root=/dev/mapper/kuglerlaptop-root ro splash
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-12.43-generic
SourcePackage: linux

[Joshua Kugler (jkugler)]

Hibernate/resume didn't help, and in addition got a message about __ratelimit:

May 26 10:10:45 hosanna kernel: [151602.816092] usb 3-2: USB disconnect, address 5
May 26 10:10:52 hosanna kernel: [151609.137032] usb 3-2: new low speed USB device using uhci_hcd and address 6
May 26 10:10:52 hosanna kernel: [151609.318165] usb 3-2: configuration #1 chosen from 1 choice
May 26 10:10:52 hosanna kernel: [151609.339708] __ratelimit: 1932 callbacks suppressed
May 26 10:10:52 hosanna kernel: [151609.339712] vmap allocation failed: use vmalloc=<size> to increase size.
May 26 10:10:52 hosanna kernel: [151609.339733] generic-usb: probe of 0003:046D:C404.0012 failed with error -12

Now going to try a full reboot. If it matters/helps: I rarely shut down my laptop all the way: I just hibernate/resume.

[Joshua Kugler (jkugler)]

A full reboot fixed the issue, *WITHOUT* the vmap=256MB added to the kernel boot line. Not to overstate the obvious, but this would appear to be some kind of resource consumption-not-being-freed issue.

[Joshua Kugler (jkugler)]

FYI, this also happens with 2.6.28-11-generic #42-Ubuntu so it does not appear to be a regression, but something that was already there.

[gene (eugenios)]

Hello everyone,
I did not find this bug earlier and filed another one #436665
I am not setting that one as the duplicate of the older bug yet. I have a little different way of solving the issue (partially) by killing X
Thanks

[Jeremy Foshee (jeremyfoshee)]

Hi Joshua,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 380696

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]