10.04 crashes during boot with magic jack connected

[Robert Schwemmer]

Binary package hint: ubuntu-docs

I have a dual boot PC and recently attempted upgrading from 9.1 to 10.04. 10.04 hung just after displaying the login GUI. I attempted re-installation of 10.04 (from CDs) several times with the same result. 9.1 re-installed with no problem.

The bottom line is that all of the above were done with a Magic Jack connected. With the Magic Jack disconnected 10.04 boots and runs just fine. And it does not seem to mind if the Magic Jack is connected, to the USB, after boot is complete.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rdschwem 1447 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd0600000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,8086d612,00100202'
   Controls : 27
   Simple ctrls : 16
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=8772b1df-f08e-4c7a-bde2-6ef7bad488c6
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic-pae root=UUID=20caad34-bbbb-4d7d-bbae-a7406f11d9b7 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic-pae 2.6.32.15+drm33.5
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: Yes
RfKill:

Tags: lucid regression-release needs-upstream-testing
Uname: Linux 2.6.32-24-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/26/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TYG4110H.86A.0031.2009.0626.1405
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41TY
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE47335-300
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrTYG4110H.86A.0031.2009.0626.1405:bd06/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-300:cvn:ct3:cvr:

[George Patterson (george-patterson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.

Please run the following command which will attach necessary information:

apport-collect 609507
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` BUGNUMBER
if you are using Jaunty Jackalope (9.04).

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):

First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

[Mitch Towner (kermiac)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

This appears to be related to the "Expired" Bug 548960. 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.

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

apport information

[Robert Schwemmer (rdschwemmer)]

I have tried booting 2 other PCs (with Ubuntu 10.04) with the MagicJack
connected. There was no crash. (Dell DIM4600/P4 & Intel
D945GCFL2D/Atom330)

On the problem PC I installed kernel 2.6.35-999-generic #201007300913.
That version does have the same problem, as 2.6.32-24.

On Sat, Jul 31, 2010 at 12:36 AM, Mitch Towner <
<email address hidden>> wrote:

> ** Tags removed: needs-kernel-logs
>
> --
> 10.04 crashes during boot with magic jack connected
> https://bugs.launchpad.net/bugs/609507
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ubuntu-docs
>
> I have a dual boot PC and recently attempted upgrading from 9.1 to 10.04.
> 10.04 hung just after displaying the login GUI. I attempted
> re-installation of 10.04 (from CDs) several times with the same result. 9.1
> re-installed with no problem.
>
> The bottom line is that all of the above were done with a Magic Jack
> connected. With the Magic Jack disconnected 10.04 boots and runs just fine.
> And it does not seem to mind if the Magic Jack is connected, to the USB,
> after boot is complete.
> ---
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: rdschwem 1447 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xd0600000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,8086d612,00100202'
> Controls : 27
> Simple ctrls : 16
> DistroRelease: Ubuntu 10.04
> HibernationDevice: RESUME=UUID=8772b1df-f08e-4c7a-bde2-6ef7bad488c6
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
> IwConfig:
> lo no wireless extensions.
>
> eth0 no wireless extensions.
> Package: linux (not installed)
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic-pae
> root=UUID=20caad34-bbbb-4d7d-bbae-a7406f11d9b7 ro quiet splash
> ProcEnviron:
> LANG=en_US.utf8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-24.38-generic-pae 2.6.32.15+drm33.5
> Regression: Yes
> RelatedPackageVersions: linux-firmware 1.34.1
> Reproducible: Yes
> RfKill:
>
> Tags: lucid regression-release needs-upstream-testing
> Uname: Linux 2.6.32-24-generic-pae i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> dmi.bios.date: 06/26/2009
> dmi.bios.vendor: Intel Corp.
> dmi.bios.version: TYG4110H.86A.0031.2009.0626.1405
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: DG41TY
> dmi.board.vendor: Intel Corporation
> dmi.board.version: AAE47335-300
> dmi.chassis.type: 3
> dmi.modalias:
> dmi:bvnIntelCorp.:bvrTYG4110H.86A.0031.2009.0626.1405:bd06/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-300:cvn:ct3:cvr:
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/609507/+subscribe
>

[nixomose (spamme-deadpelican)]

For what it's worth I have the same problem. Ubuntu 9.04 was flawless with magic jack under vmware xp guest.
I upgraded to 10.04 and the machine would boot fine, but as soon as gnome started up I'd get a kernel panic (keyboard lights flashing) 100 % of the time. As I had a raid0 drive that had to recover every time I booted it didn't give me much opportunity to look for problems in the logs, the one time I did get a shell nothing in kernel or dmesg or anything.
I gave up installed 10.10 from scratch. Now it's random, but 10.10 works flawlessly until I plug in the magic jack then when I run the vm to talk to it, machine freezes up.
Now I have no phone. :-(
Any info I can give you lemme know.

[penalvch (penalvch)]

Robert Schwemmer, 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? If so, with the magic jack connected directly to you PC with no hubs in between, 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 in the development release 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Robert Schwemmer (rdschwemmer)]

Christopher:

I no longer have a PC with Ubuntu installed.

On 7/24/2012 6:23 PM, Christopher M. Penalver wrote:
> Robert Schwemmer, 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? If so, with the magic jack connected directly to you PC with no
> hubs in between, 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 in the
> development release 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 . Please do
> not test the kernel in the daily folder, but the one all the way at the
> bottom. 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. As well, please comment
> on which kernel version specifically you tested.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream', and comment
> as to why specifically you were unable to test it.
>
> Please let us know your results. Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[penalvch (penalvch)]

Robert Schwemmer, this bug report is being closed due to your last comment regarding how you are no longer using Ubuntu. 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 feel free to submit any future bugs you may find.