lem.
Earlier, I was trying to keep the interface alive with "ping -i 60
xxx" instead of setting "/sys/usb/ power/control" to "on". Not
sure if that was not enough and $extif actually powered off in between
pings and avahi-daemon was simply reporting this in daemon
interface alive with "ping -i 60 xxx"
instead of setting "/sys/usb/ power/control" to "on". Not sure if
that was not enough and $extif actually powered off in between pings and
avahi-daemon was simply reporting this in daemon.log. However, kernel
reset the inte
Hi Ramesh,
There are numerous reports (mostly old, afaics) of the issue you describe, but
with various suggested reasons.
I suspect the avahi related part is a consequence rather than a cause - I didn't think
avahi was capable of disabling interfaces, the message looks like it's updating a
ta
On Thu 14 Jul 2022, at 01:03, Ram Ramesh wrote:
[...]
> I take back some of what I said. It is both - I mean usb
> autosupend+avahi_daemon. I need to keep the adaptor from autosuspending
> and tell avahi-daemon not to disable the interface in the OS.
>
> I also found the power/c
,
This is what I find in daemon.log
Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record
for fe80::daeb:97ff:febf:5ad0 on enxd8eb97bf5ad0.
Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record
for 192.168.1.124 on enxd8eb97bf5ad0.
After this happens, most of
) since debian
5.0.7. I have not upgraded that machine as it is working fine.
However that hardware is too old (10+ years) and I wanted to replace
it with something more modern running latest OS and that is why I
built the above machine.
My old machine does not seem have avahi-daemon. So, it runs
On Wed 13 Jul 2022, at 01:21, Ram Ramesh wrote:
> Do you know a simple way to disable autopowerdown of
> just this usb NIC? May be there is something that I can do with ethtool?
I wonder if powertop may be of use here.
It has a "tunables" section where (I think) power-saving features can be
that machine as it is working fine. However
that hardware is too old (10+ years) and I wanted to replace it with
something more modern running latest OS and that is why I built the
above machine.
My old machine does not seem have avahi-daemon. So, it runs fine.
However, my new machine has
hows
> some avahi-daemon messages about that interface being disabled/withdrawn or
> some such thing.
Hi Ramesh,
Please could you post some example daemon.log entries and any surrounding
entries that seem related?
Also is there anything in
/var/log/syslog
that seems to relate?
Perhap
. However
that hardware is too old (10+ years) and I wanted to replace it with
something more modern running latest OS and that is why I built the
above machine.
My old machine does not seem have avahi-daemon. So, it runs fine.
However, my new machine has this daemon running which notices that
ng log messages like these:
Mar 7 15:47:47 whio avahi-daemon[310]: Record
[Brother\032HL-2140\032\064\032whio._ipps._tcp.local#011IN#011SRV 0
0 631 whio.local ; ttl=120] not fitting in legacy unicast packet,
dropping.
Mar 7 15:47:47 whio avahi-daemon[310]: Record
[whio.local#011IN#011 fe80:
7:47 whio avahi-daemon[310]: Record
[Brother\032HL-2140\032\064\032whio._ipps._tcp.local#011IN#011SRV 0 0
631 whio.local ; ttl=120] not fitting in legacy unicast packet,
dropping.
Mar 7 15:47:47 whio avahi-daemon[310]: Record
[whio.local#011IN#011 fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not
fi
On 8/03/22 13:25, Richard Hector wrote:
Hi all,
I've recently set up a small box to run cups, to provide network access
to a USB-only printer. It's a 32-bit machine running bullseye.
I'm seeing log messages like these:
Mar 7 15:47:47 whio avahi-daemon[310]: Record
[Brother
Hi all,
I've recently set up a small box to run cups, to provide network access
to a USB-only printer. It's a 32-bit machine running bullseye.
I'm seeing log messages like these:
Mar 7 15:47:47 whio avahi-daemon[310]: Record
[Brother\032HL-2140\032\064\032whio._ipps._
Le 29/07/2019 à 13:08, Pascal Hambourg a écrit :
Prefix delegation is a DHCPv6 feature. The kernel does managed it.
Oops ! I meant "the kernel does NOT manage it".
Le 29/07/2019 à 11:07, Harald Dunkel a écrit :
question about IPv6 support in sid: Whose job is it to bother
about the IPv6 addresses dynamically bound to eth0?
It depends what dynamic configuration method is used.
SLAAC (using router advertisements) is in kernelspace. However some
informatio
the kernel sees the prefix delegation on eth0, sets the
> old IPv6 address to "deprecated" and registers the new one. How
> comes that avahi daemon and dhcpcd and possibly others interfere?
I won't say anything about the avahi (don't see the need to install it),
but I'
Hi folks,
question about IPv6 support in sid: Whose job is it to bother
about the IPv6 addresses dynamically bound to eth0?
AFAIU the kernel sees the prefix delegation on eth0, sets the
old IPv6 address to "deprecated" and registers the new one. How
comes that avahi daemon and
I'm getting the error
avahi-daemon: Failed to open /etc/resolv.conf: Invalid argument
chroot.c: open() failed: No such file or directory
at boot.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800643
Is the workaround mentioned above (and below) still valid (bug date Oct
> Yeah, and the best and most correct way to do that is to use the
> aforementioned:
>
> update-rc.d avahi-daemon disable
>
> avahi no longer uses a ENABLE flag in /etc/default/avahi-daemon. Those
> flags are a hack and the above menthod is much better.
Personally I disag
Am 24.05.2013 01:03, schrieb Wayne Topa:
> On 05/23/2013 04:46 PM, Sean Alexandre wrote:
>> On Thu, May 23, 2013 at 12:39:16PM -0700, David Guntner wrote:
>>
>> You should be able to disable it with:
>> update-rc.d avahi-daemon disable
>>
>
> Or just
On Jo, 23 mai 13, 12:39:16, David Guntner wrote:
>
> So, is avahi-daemon truly essential for the system?
No.
> If not, is there a
> way to remove it without removing other things such as Gnome?
Probably. See the reply I just wrote a few minutes ago to the "Remove
evolut
tv.deb...@googlemail.com grabbed a keyboard and wrote:
>
> Hi, if you don't use it (have no use for mdns/zeroconf stuff on your
> network) you can do without, I sure do. Few packages actually depend
> on it, most often it's a "suggest" or "recommend". If a metapackage
> depends on it (like Gnome)
t;> A question that I've been pondering for a while now: Is the
>> avahi-daemon *really* needed?
>
> I've disabled it, and haven't needed it. Here's more on what it's for:
> http://packages.debian.org/wheezy/avahi-daemon
>
> So it seems you'd
ency lookup on a package, similar to apt-cache's depends
>> and rdepends commands, but only shows installed packages.
>>
>> So to see all the packages you have installed that depend on
>> avahi, run: deborphan -a avahi-daemon or to see the packages
>> that depe
On Thu, May 23, 2013 at 12:39:16PM -0700, David Guntner wrote:
> I'm still running Squeeze for a while longer before I finally upgrade to
> Wheezy - want to let it shake out a bit before taking the plunge. :-)
>
> A question that I've been pondering for a while now: Is the
d rdepends commands, but only shows installed packages.
>
> So to see all the packages you have installed that depend on avahi, run:
>deborphan -a avahi-daemon
> or to see the packages that depend on or 'recommend' avahi, run:
>deborphan -an avahi-daemon
Thanks; good t
I'm still running Squeeze for a while longer before I finally upgrade to
Wheezy - want to let it shake out a bit before taking the plunge. :-)
A question that I've been pondering for a while now: Is the
avahi-daemon *really* needed? All it seems to do is spew the occasional
message to
On Thu, 14 Oct 2010, Jordan Metzmeier wrote:
> Anytime and subscribed :). That may even be an RC as full ipv6 was a
> release goal of squeeze. Also, if it really was corrupting your
It is clearly something that requires testing on UP, probably on a i486 to
reproduce (otherwise, our kernels would b
On 14 October 2010 12:52, Jordan Metzmeier wrote:
> Anytime and subscribed :). That may even be an RC as full ipv6 was a
> release goal of squeeze. Also, if it really was corrupting your
> filesystem, I would think that would be a "critical" RC.
That's harder to assert, I think. My FS got corrupt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/14/2010 12:32 AM, Jason Heeris wrote:
> On 14 October 2010 11:52, Jordan Metzmeier wrote:
>> Please do as .32 is what will ship in the next stable.
>
> Bug filed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600155
>
> My real solution t
On 14 October 2010 11:52, Jordan Metzmeier wrote:
> Please do as .32 is what will ship in the next stable.
Bug filed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600155
My real solution to all of this was to disable IPv6 altogether. Thanks
everyone for the help :) (Also, I learnt about a do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/13/2010 09:57 PM, Jason Heeris wrote:
> On 14 October 2010 09:34, Jordan Metzmeier wrote:
>> I would first check to see if the problem still occurs in .35 from the
>> experimental repos. I believe it is much easier for them to provide a
>> fix
On 14 October 2010 09:34, Jordan Metzmeier wrote:
> I would first check to see if the problem still occurs in .35 from the
> experimental repos. I believe it is much easier for them to provide a
> fix when it can be backported from a newer upstream.
Interesting, no crash with 2.6.36-rc6-486. I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/13/2010 08:58 PM, Jason Heeris wrote:
> So where should I report it, debian kernel bug tracker or upstream bug
> tracker? I figured the former, since it's not a bleeding edge kernel
> I'm running, but maybe I'm wrong.
>
> Cheers,
> Jason
I wo
On 13 October 2010 06:35, Jordan Metzmeier wrote:
> Disabling support for ipv6 can actually be done via a kernel parameter,
> so recompiling to remove ipv6 support should not be needed. Use the
> kernel parameter "ipv6.disable=1".
Yep, disabling IPv6 stops the crash!
So where should I report it,
On Wed, 13 Oct 2010, Jason Heeris wrote:
> On 12 October 2010 10:36, Henrique de Moraes Holschuh wrote:
> > On Sun, 10 Oct 2010, Jason Heeris wrote:
> >> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
> >> could be wrong
> >
> > Yikes. You really need to track this one down,
Jason Heeris writes:
> To save me more trouble, can anyone tell me what the key is to
> building a kernel exactly the same as what's in
> linux-image-2.6.32-5-486? I'm on a PC with amd64 arch, so I created a
> i386 chroot:
I have personally used
http://wiki.debian.org/HowToRebuildAnOfficialDebia
On 13 October 2010 22:35, Jordan Metzmeier wrote:
> The person responding indicates a kernel problem, which makes sense when
> you actually get a kernel panic as a result. This was also indicated on
> this list.
I'm trying to figure out if there's a simpler way to trigger it, but
haven't really f
On 10/13/2010 05:16 AM, Jason Heeris wrote:
> Before I go off to bugzilla, I just want to check that I've actually
> got debugging information here, since to me it doesn't look that
> different. Do I need to boot with a special kernel arg?
Looks like this bug was reported on the avahi upstream mai
ith a special kernel arg?
- Jason
Setting up avahi-daemon (0.6.27-2) ...
Reloading system message bus config...done.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon[ 206.608591] BUG: unable to
handle kernel NULL pointer dereference at 0004
[ 206.611182] IP: [] r6040_multicast_list+0x16d
On 13 October 2010 14:45, Jason Heeris wrote:
> To save me more trouble, can anyone tell me what the key is to
> building a kernel exactly the same as what's in
> linux-image-2.6.32-5-486?
More RTFMing required on my part, sorry. In the DEBIAN.Readme for the
linux-image source package:
Each
On 12 October 2010 19:49, Timo Juhani Lindfors wrote:
> Jason Heeris writes:
>> Yay. I'll build one on my PC.
>
> Ah.
To save me more trouble, can anyone tell me what the key is to
building a kernel exactly the same as what's in
linux-image-2.6.32-5-486? I'm on a PC with amd64 arch, so I created
On 12 October 2010 10:36, Henrique de Moraes Holschuh wrote:
> On Sun, 10 Oct 2010, Jason Heeris wrote:
>> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
>> could be wrong
>
> Yikes. You really need to track this one down, and find out whether it is
> any different from a reg
Jason Heeris writes:
> Yay. I'll build one on my PC.
Ah.
>> Qemu defaults to X. Copying the system image to some machine that runs
>> X is probably the safest solution, you can then run qemu without any
>> extra privileges..
>
> Done, but avahi-daemon inst
all
Yay. I'll build one on my PC.
> Qemu defaults to X. Copying the system image to some machine that runs
> X is probably the safest solution, you can then run qemu without any
> extra privileges..
Done, but avahi-daemon installs without a hitch (presumably because
the proces
[please keep this on the list]
Jason Heeris writes:
> Kernel: Linux 2.6.32-5-486
Please install linux-image-2.6.32-5-486-dbg
> Qemu won't start, it can't find a framebuffer:
>
> (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
> --> No such file or directory
Qemu defaults
On 11 October 2010 23:44, Jochen Schulz wrote:
> [ I guess Henrique's interpretation of the problem is better than mine,
> I just wanted to follow-up on this specific question. ]
>> How would I know?
>
> $ dmesg | grep "Write cache"
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, d
Jason Heeris writes:
> Should I recompile it with any kind of debugging information enabled,
> or does the Debian kernel already contain it?
It depends on the architecture and debian version. Please post a
proper bug report with reportbug that shows all the relevant version
information. Can you m
On 12 October 2010 10:59, Jason Heeris wrote:
>> 4. File a bug on bugzilla.kernel.org with all relevant information. This
>> does include the kernel config at the very least.
>
> It's just the Debian stock kernel config.
Should I recompile it with any kind of debugging information enabled,
or do
On 10/11/2010 10:11 PM, Jason Heeris wrote:
2010/10/12 Ron Johnson:
My 1st thought was whether you need IPv6...
Well, no, and if I can't sort this out then I'll recompile without it
and see if the crash goes away (or... can I black list it, or is IPv6
Sure.
http://blogs.koolwal.net/2009/10/
2010/10/12 Ron Johnson :
> My 1st thought was whether you need IPv6...
Well, no, and if I can't sort this out then I'll recompile without it
and see if the crash goes away (or... can I black list it, or is IPv6
compiled right in?). But this might be a good opportunity to find a
bug before I go dow
On 10/11/2010 09:59 PM, Jason Heeris wrote:
On 11 October 2010 18:36, Henrique de Moraes Holschuh wrote:
[snip]
The box objected VERY HEAVILY to the ipv6 multicast operations trigerred by
avahi.
Given this, can you think of another way I might be able to trigger
the bug? If so, I might be
On 11 October 2010 18:36, Henrique de Moraes Holschuh wrote:
> On Sun, 10 Oct 2010, Jason Heeris wrote:
t>> My system is a Helios single-board computer, with specs:
>>
>> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
>> could be wrong
>
> Yikes. You really need to track this
undetected by the sanity checks at
kernel startup.
> My problem started when I installed avahi-daemon - the system crashed,
> and I could not recover to a useable state. So I reinstalled the
> system and approached it a little more carefully.
1. Set up a serial console (to capture crash dat
to commence a destructive badblocks scan ("badblocks -b 4096
-s -w /dev/sdb1") - can badblocks be given an entire device instead of
a partition? Or does that not make sense?
>> Yep, every time. I just wonder if somehow the avahi-daemon package is
>> the only thing I'm
lem for some time now. I
> only find it curious that it can be reproduced when installing a
> particular package. Is the segfault reproducible after a reinstall as
> well?
Yep, every time. I just wonder if somehow the avahi-daemon package is
the only thing I'm trying to ins
after install;
this also happens with Emdebian)
Storage is a 4GB flash card (I don't have sdparm or hdparm, and I
can't install either to get more info. If there's another way, let me
know.) It was formatted ext2.
My problem started when I installed avahi-daemon - the system crashed,
Hi Debian users,
My /var/log/daemon.log is now being flooded with
avahi-daemon: Received response with invalid source port 44038 on
interface 'eth1.0'
Could someone tell me what's going on? I'm using the testing
distribution of Debian.
Ryo
--
To UNSUBSCRIBE, email
On 03/31/2008 10:08 AM, Douglas A. Tutty wrote:
On Sun, Mar 30, 2008 at 05:38:17PM -0500, Mumia W.. wrote:
My booting of Etch was being slowed by
/etc/network/if-up.d/avahi-daemon, so I removed execute permissions from
that file, and now my boots are 10 seconds faster.
[...]
If gnome
On Sun, Mar 30, 2008 at 05:38:17PM -0500, Mumia W.. wrote:
> My booting of Etch was being slowed by
> /etc/network/if-up.d/avahi-daemon, so I removed execute permissions from
> that file, and now my boots are 10 seconds faster.
>
> However, the avahi-daemon still starts. Wi
My booting of Etch was being slowed by
/etc/network/if-up.d/avahi-daemon, so I removed execute permissions from
that file, and now my boots are 10 seconds faster.
However, the avahi-daemon still starts. Will there be any adverse
consequences to disabling .../avahi-daemon on my system?
I
On Wed, 27 Feb 2008 16:51:39 +
michael <[EMAIL PROTECTED]> wrote:
Hello michael,
> but I'm unsure what 'avahi-daemon' is needed for... anybody care to
> illuminate me? or can I just uninstall it?
It's used for DNS service discovery. If you're on a loc
I seem to have messages in my SYSLOG such as
Feb 27 12:55:43 ratty avahi-daemon[2996]: Invalid legacy unicast query
packet.
Feb 27 12:55:44 ratty avahi-daemon[2996]: Invalid legacy unicast query
packet.
Feb 27 12:55:44 ratty avahi-daemon[2996]: Recieved repsonse with invalid
source port 4034 on
Hi,
as the package maintainer seems to ignore my complaint I forward the discussion
to debian-user mailing list.
On debian testing the rhythmbox suggested to install the avahi-daemon that
listens on all interfaces by default.
I think this kind of install behaviour is insecure even if the
Hi,
as the package maintainer seems to ignore my complaint I forward the discussion
to debian-user mailing list.
On debian testing the rhythmbox suggested to install the avahi-daemon that
listens on all interfaces by default.
I think this kind of install behaviour is insecure even if the
66 matches
Mail list logo
