Re: [ck] [ANNOUNCE] Staircase Deadline cpu scheduler version 0.46

2007-05-17 Thread Ash Milsted
On Wed, 09 May 2007 17:28:41 -0400
Dan Williams [EMAIL PROTECTED] wrote:
 
 I've seen this _once_ before on an OLPC machine, but it was intermittent
 and I was not able to debug it all the way down.  If you can reproduce
 reliably, try running dbus-monitor --system and try to get it to
 reproduce, then save the output from dbus-monitor and send it along to
 the list.
 
 Thanks,
 Dan
 

Okay, finally got round to doing that. I can now reproduce the problem
with the up and coming CFS scheduler v12 (apparently with or without
its 'old yield behaviour' feature. Here are some logs, one of a working
negotiation, and one of the (more common) failing case.

Working:
signal sender=org.freedesktop.DBus - dest=:1.245 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameAcquired
   string :1.245
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=StateChange
   uint32 4
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=StateChange
   uint32 4
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=StateChange
   uint32 4
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceRemoved
   object path /org/freedesktop/NetworkManager/Devices/eth0
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceAdded
   object path /org/freedesktop/NetworkManager/Devices/eth0
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceCarrierOn
   object path /org/freedesktop/NetworkManager/Devices/eth0
signal sender=:1.14 - dest=(null destination) 
path=/org/freedesktop/NetworkManagerInfo; 
interface=org.freedesktop.NetworkManagerInfo; member=UserInterfaceActivated
signal sender=:1.14 - dest=(null destination) 
path=/org/freedesktop/NetworkManagerInfo; 
interface=org.freedesktop.NetworkManagerInfo; member=UserInterfaceActivated
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=StateChange
   uint32 4
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=StateChange
   uint32 4
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceActivationStage
   object path /org/freedesktop/NetworkManager/Devices/eth0
   uint32 1
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceActivationStage
   object path /org/freedesktop/NetworkManager/Devices/eth0
   uint32 1
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceActivationStage
   object path /org/freedesktop/NetworkManager/Devices/eth0
   uint32 2
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceActivationStage
   object path /org/freedesktop/NetworkManager/Devices/eth0
   uint32 4
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=StateChange
   uint32 2
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 
member=DeviceActivating
   object path /org/freedesktop/NetworkManager/Devices/eth0
signal sender=:1.219 - dest=(null destination) path=/com/redhat/dhcp; 
interface=com.redhat.dhcp.state; member=eth0
   byte 12
signal sender=org.freedesktop.DBus - dest=(null destination) 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; 
member=NameOwnerChanged
   string :1.246
   string 
   string :1.246
signal sender=org.freedesktop.DBus - dest=(null destination) 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; 
member=NameOwnerChanged
   string :1.246
   string :1.246
   string 
signal sender=org.freedesktop.DBus - dest=(null destination) 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; 
member=NameOwnerChanged
   string :1.247
   string 
   string :1.247
signal sender=org.freedesktop.DBus - dest=(null destination) 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; 
member=NameOwnerChanged
   string :1.247
   string :1.247
   string 
signal sender=:1.219 - dest=(null destination) path=/com/redhat/dhcp; 
interface=com.redhat.dhcp.state; member=eth0
   byte 2
signal sender=:1.5 - dest=(null destination) 
path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; 

Re: different icons if internet is available

2007-05-17 Thread yelo_3
sorry, but isn't the applet in the same project as NetworkManager??
if not where should I send a patch to implement this?

- Messaggio originale -
Da: Patrick Bogen [EMAIL PROTECTED]
A: yelo_3 [EMAIL PROTECTED]
Cc: network manager networkmanager-list@gnome.org
Inviato: Giovedì 17 maggio 2007, 23:44:29
Oggetto: Re: different icons if internet is available

On 5/17/07, yelo_3 [EMAIL PROTECTED] wrote:
 Hello, just a proposal: it would be great that NM-applet icon could add a 
 small world,located in a corner, if internet is reachable, checked every N 
 minutes...

This seems like it's out of the scope of NetworkManager, let alone
nm-applet. It's almost certainly better implemented as a standalone
applet, since this really has nothing at all to do with configuring
network interfaces.

-- 
- Patrick Bogen





  ___ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: 
http://it.docs.yahoo.com/nowyoucan.html
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: different icons if internet is available

2007-05-17 Thread Patrick Bogen
On 5/17/07, yelo_3 [EMAIL PROTECTED] wrote:
 sorry, but isn't the applet in the same project as NetworkManager??
 if not where should I send a patch to implement this?

Sorry, I misread. I thought you were asking for a seperate tray icon.
Nevertheless, I'm not sure if this is strictly in the scope of
NetworkManager (for one thing, how would you determine whether or not
you can access the internet?).

Now, as I see it, there are three ways to implement this that touch
NetworkManager or nm-applet:
(1) Implement it purely within nm-applet. This is, in my opinion,
wrong; nm-applet is purely a configuration and dbus interface to
NetworkManager. It shouldn't have any functionality on its own.
(2) Implement it within NetworkManager, and nm-applet gets the
information over dbus. This is better, but still: The focus of
NetworkManager is to configure your network, not necessarily to tell
you any information about your network. It doesn't map samba servers
or tell you if there's VPN available, why should it tell you if
there's a route to some arbitrary website?
(3) Write another dbus backend that does this task, and feeds
nm-applet the information. Well, maybe. But nm-applet is supposed to
only talk to NetworkManager (unless I've misunderstood its purpose),
and this would start to be a bit of feature creep.

So, the remaining option is a standalone tray icon (with whatever
architecture you want, dbus or otherwise). I honestly think this is
the best solution, as it tends towards keeping NetworkManager trimmed
down and focused, relatively speaking.

Now, as a disclaimer: I am not a dev. I have no sway over this
project, other than rhetorical. If you write a patch and submit it as
an RFE, it may well get accepted and integrated. Anything above is
*purely* my opinion, and does not necessarily reflect NetworkManager's
philosophy or policy.

I do sincerely believe, however, that writing a separate daemon would
be just as difficult or easy as modifying nm-applet and NetworkManager
to do this the correct way, and encourage you to choose this route, if
you choose to implement this yourself, rather than trying to tie your
work into NetworkManager.

-- 
- Patrick Bogen
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list