BUG: scheduling while atomic: update-manager/1962/0x10000500; RIP: 0033:[<00007f39977d0b33>] [<00007f39977d0b33>] 0x7f39977d0b33

[Franz Dietzmann]

BUG: scheduling while atomic: evolution/1970/0x10000500

I have a Option GT Fusion+ mobile broadband PCMCIA card (Qualcomm MSM6275), which in previous releases used the nozomi driver and worked pretty well.
Now after installing Maverick, the card was not recognised at all.
As there was not much information around I simply tried "sudo modprobe nozomi".
The card was then recognised and NetworkManager asked for a PIN, I set up the connection details and NM also established a connection.
The problem is, shortly after the connection is established, the computer completely freezes, no more key/mouse inputs are recognised, only a hard reset works.

This is on a fresh install (no upgrade) of Ubuntu 10.10 64bit.
Please let me know which further information or logs you need.

[Fabio Marconi (fabiomarconi)]

Hello
can you grab
/var/log/syslog
/var/log/dmesg
/var/log/kern.log
/var/log/Xorg.0.log
Thanks
Fabio

[Franz Dietzmann (tdk-le)]

Hi,
I booted a live-cd after reproducing the bug again, so the logs would be right until the freeze. One thing I noticed playing around a bit is, that the freeze only appears when I actually try to use the connection. I can load the module, enter the PIN and connect and the computer will work just fine. Just when I open a program that transfers data (Evolution, Pidgin, Firefox) the freeze will appear after a couple of seconds.

[Fabio Marconi (fabiomarconi)]

11 21:10:06 Hamlet NetworkManager[1101]: <error> [1286824206.512924] [nm-device-wifi.c:3095] real_update_permanent_hw_address(): (eth1): unable to read permanent MAC address (error 0)
Oct 11 21:10:54 Hamlet kernel: [ 68.263698] Initializing Nozomi driver 2.1d (build date: Sep 19 2010 20:36:30)
Oct 11 21:10:54 Hamlet kernel: [ 68.263788] nozomi 0000:03:00.2: Init, new card found
Oct 11 21:10:54 Hamlet kernel: [ 68.263802] nozomi 0000:03:00.2: enabling device (0000 -> 0002)
Oct 11 21:10:54 Hamlet kernel: [ 68.263814] nozomi 0000:03:00.2: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Oct 11 21:10:54 Hamlet kernel: [ 68.263821] nozomi 0000:03:00.2: Card type is: 2048
Oct 11 21:10:54 Hamlet kernel: [ 68.264603] nozomi 0000:03:00.2: Version of card: 3
Oct 11 21:10:54 Hamlet kernel: [ 68.264838] nozomi 0000:03:00.2: Initialization OK!
Oct 11 21:10:54 Hamlet kernel: [ 68.266992] nozomi 0000:03:00.2: Device READY! <-----#####
Oct 11 21:10:54 Hamlet modem-manager: (noz0) opening serial device...
Oct 11 21:10:54 Hamlet modem-manager: (noz0): probe requested by plugin 'Generic'
Oct 11 21:10:54 Hamlet modem-manager: (noz1) opening serial device...
Oct 11 21:10:54 Hamlet kernel: [ 68.305978] noz: activated 0: ffff88009274e078
Oct 11 21:10:54 Hamlet modem-manager: (noz1): probe requested by plugin 'Generic'
Oct 11 21:10:54 Hamlet kernel: [ 68.313713] noz: activated 1: ffff88009274e218
Oct 11 21:10:54 Hamlet modem-manager: (noz2) opening serial device...
Oct 11 21:10:54 Hamlet modem-manager: (noz2): probe requested by plugin 'Generic'
Oct 11 21:10:54 Hamlet modem-manager: (noz3) opening serial device...
Oct 11 21:10:54 Hamlet modem-manager: (noz3): probe requested by plugin 'Generic'
Oct 11 21:10:54 Hamlet kernel: [ 68.321700] noz: activated 2: ffff88009274e3b8
Oct 11 21:10:54 Hamlet kernel: [ 68.321987] noz: activated 3: ffff88009274e558
Oct 11 21:10:57 Hamlet modem-manager: (noz0) closing serial device...
Oct 11 21:10:57 Hamlet kernel: [ 71.609939] nozomi 0000:03:00.2: No tty open? <------###
Oct 11 21:10:57 Hamlet kernel: [ 71.609948] noz: shutdown ffff88009274e078 <------#
Oct 11 21:10:57 Hamlet kernel: [ 71.611054] noz: activated 0: ffff88009274e078
Oct 11 21:10:57 Hamlet kernel: [ 71.611267] nozomi 0000:03:00.2: No tty open?
Oct 11 21:10:57 Hamlet kernel: [ 71.611272] noz: shutdown ffff88009274e3b8
Oct 11 21:10:57 Hamlet modem-manager: (noz0) opening serial device...
Oct 11 21:10:57 Hamlet modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:14.4/0000:02:04.0/0000:03:00.2 claimed port noz0
Oct 11 21:10:57 Hamlet modem-manager: Added modem /sys/devices/pci0000:00/0000:00:14.4/0000:02:04.0/0000:03:00.2
Oct 11 21:10:57 Hamlet modem-manager: (tty/noz0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:14.4/0000:02:04.0/0000:03:00.2
Oct 11 21:10:57 Hamlet modem-manager: (tty/noz1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:14.4/0000:02:04.0/0000:03:00.2
Oct 11 21:10:57 Hamlet modem-manager: (noz2) closing serial device...
Oct 11 21:10:57 Hamlet modem-manager: (noz3) closing serial device...
Oct 11 21:10:57 Hamlet kernel: [ 71.612198] n...

[Franz Dietzmann (tdk-le)]

I just tried the i386 Live-CD to check if this is an issue of the 64bit version. In the Live environment, the card was instantly recognised, I was asked for the PIN and could connect. I didn't even have to modprobe nozomi. As there was no freeze after starting Firefox and surfing a bit, I decided to install this instead of the 64 bit version.
Unfortunatly, after installation, the same problem as before. Ubuntu almost instantly freezes when I start Firefox or Evolution.
What is strange though is that it takes a lot longer until the freeze if I just use the terminal. I wanted to check for Updates, so I did apt-get update, which went fine and then apt-get upgrade, which downloaded the first 10-20MB fine before freezing again.

[jeawrong (jeawithlove)]

I have the same issue on a Kubuntu 10.10 fresh install.
And I have open a system monitor, and few seconds before the freeze, the process ksoftirqd/0 use more cpu, from 65% to 100%..., and this also without other software run, only a kppp (the card is not recognised from the network manager) connection.

[Imre Széll (konzerwe)]

I have the same issue on Kubuntu 10.10 on i386. First on after an upgrade from 10.04, now on a fresh install. In my case the freeze does not occur immediately after initiating data transfer, and is independent from the network usage (it happened while downoading and while working with remote ssh session too). In version 10.04, I had no problems.

[Kitsab (kitsab)]

Hello,

same problem here Vodafon (D2) Globetrotter 3G+ PCMIA card with Qualcomm MSM6275 chip. I'm able to connect to the internet and work a bit but after a short time the system freezes. No mouse movement no keyboard function.

Bastik

[menner (menner)]

Same problem on Natty 11.04
Same card (Option GT 3G+ EMEA by Vodafone D2)
When card is inserted, the thinkpad x21 trackpoint pointer starts to move for a while.
Shortly after using the established GPRS/UMTS connection, the notebook freezes.

On a terminal running tail -f /var/log/kern.log I once could see sort of kernel stack traces. But mostly it just freezes.

[menner (menner)]

When booting an old Lucid-like Kernel 2.6.32-31.61 (installed via dpkg from ppa:linrunner/thinkpad-extras / thinkpad-wiki.org), there's no problem with nozomi kernel module.

[menner (menner)]

again natty with lucid kernel: always when data are transmitted, the trackpoint is moving up and left. It's stopping when a page is transmitted fully.

But can't load many pages since transmission stucks. Need to reinsert UMTS card and reload network-manager to be able to dialup again.

[penalvch (penalvch)]

Franz Dietzmann, thank you for reporting this bug and helping make Ubuntu better. Maverick reached EOL on April 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

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 in a supported release? If so, could you please report the results following https://wiki.ubuntu.com/Kernel/DebuggingSchedulingWhileAtomic ? As well, 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 <replace-with-bug-number>

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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]