Comment 9 for bug 261808

I have done more testing and have found the following:
1. Tested live CD on different machine - every thing works as expected.
2. Put a 3com net card in the problem machine - everything works as
expected.

This bug report started as a follow on bug from 256919. the fix to that one
was to upgrade to a new kernel that fixed the driver. I am wondering if the
skge driver is not completely fixed, as it doesn't seem to be interacting
with network-manager nicely.
For example with both net cards in the system, I can unplug from the working
3com and plug into the marvell and then the repeating messages start,
requiring network-manager to be restarted.

here is output from lspci showing the two cards.

00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
Ethernet Controller (rev 13)
00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 30)

On Tue, Sep 23, 2008 at 11:12 AM, Rob Snyder <email address hidden> wrote:

> Two other pieces of information.
> This is also present when running alpha6 live cd.
> If I boot with the net cable unplugged there are no repeating
> "nm_dbus_manager_start_service()" messaged until the net cable is plugged
> in, after plug in they start. It appears that it gets an ip address then
> drops it, then starts spewing error messages.
>
>
> On Tue, Sep 23, 2008 at 10:57 AM, Rob Snyder <email address hidden> wrote:
>
>> yep its still there. just did the update and reboot and still have to
>> restart network manager. see attached syslog. note there are several
>> restarts in there. look for the last one.
>>
>>
>> On Mon, Sep 22, 2008 at 6:19 PM, Alexander Sack <email address hidden> wrote:
>>
>>> can you still reproduce this issue with
>>> 0.7~~svn20080908t183521+eni0-0ubuntu3 ?
>>>
>>> ** Changed in: network-manager (Ubuntu)
>>> Status: New => Incomplete
>>>
>>> --
>>> NetworkManager crashed with SIGSEGV in
>>> dbus_connection_unregister_object_path()
>>> https://bugs.launchpad.net/bugs/261808
>>> You received this bug notification because you are a direct subscriber
>>> of a duplicate bug.
>>>
>>
>>
>