On 2023-01-08 08:14, Sjoerd Mullender wrote:
and see the difference in behavior. When using "all", the second
round (IPv4) says that bind returns 1 unexpectedly, and the port is
also unexpected. When using "localhost", both IPv6 and IPv4 succeed
and listen to the same port, but using two di
On 08/01/2023 16:14, Sjoerd Mullender wrote:
On 07/01/2023 01.38, Gordon Messmer wrote:
On 2023-01-06 06:17, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically:
create new socket for IPv6
On 07/01/2023 01.38, Gordon Messmer wrote:
On 2023-01-06 06:17, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically:
create new socket for IPv6, set option IPV6_V6ONLY to off, bind,
listen;
On 2023-01-06 06:17, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically:
create new socket for IPv6, set option IPV6_V6ONLY to off, bind,
listen; then create a new socket for IPv4, and also
ng to [::]/0.0.0.0. In that case,
the second bind gets a different port number assigned to it. Moreover, the
second bind system call returns 1, which it is not supposed to do according to
the manual. Bind is supposed to return 0 on success and -1 on error.
What is going on? Is this a kernel bug,
hat
> case, the second bind gets a different port number assigned to it. Moreover,
> the second bind system call returns 1, which it is not supposed to do
> according to the manual. Bind is supposed to return 0 on success and -1 on
> error.
>
> What is going on? Is this
case, the second bind gets a different port number assigned to it.
Moreover, the second bind system call returns 1, which it is not
supposed to do according to the manual. Bind is supposed to return 0 on
success and -1 on error.
What is going on? Is this a kernel bug, or is this the future
aitra
> Date: Sun, 27 Nov 2022 22:02:56 -0600
> To: Community support for Fedora users
> Reply-To: Community support for Fedora users
> Subject: kernel bug? Was Re: mpv does not play videos on Fedora 36
>
> Hi,
>
> I have verified that mpv works fine with kernel 6.0.
Hi,
I have verified that mpv works fine with kernel 6.0.5-200.fc36.x86_64 (which is
what I booted into now) but not with kernel 6.0.9-200.fc36.x86_64 (which is
what I was using when I posted below). So, where should this bug go?
Thanks,
Ranjan
On Sat Nov26'22 02:57:20PM, Ranjan Maitra wrote:
On Sun, Jul 31, 2022 at 3:42 PM Michael Young wrote:
>
> On Sun, 31 Jul 2022, stan wrote:
>
> > On Sun, 31 Jul 2022 12:44:24 +0100
> > Andrew Wood wrote:
> >
> >> I have Fedora set up with Fedora 35 (workstation edition) using Gnome
> >> 41.6.
> >>
> >> I notice a (annoying!) bug which occurs whe
On Sun, 31 Jul 2022, stan wrote:
On Sun, 31 Jul 2022 12:44:24 +0100
Andrew Wood wrote:
I have Fedora set up with Fedora 35 (workstation edition) using Gnome
41.6.
I notice a (annoying!) bug which occurs when I try and cut and paste
from one window to another. What seems to happen is that the
On Sun, 31 Jul 2022 12:44:24 +0100
Andrew Wood wrote:
> I have Fedora set up with Fedora 35 (workstation edition) using Gnome
> 41.6.
>
> I notice a (annoying!) bug which occurs when I try and cut and paste
> from one window to another. What seems to happen is that the Gnome
> session closes
Hello,
I have Fedora set up with Fedora 35 (workstation edition) using Gnome 41.6.
I notice a (annoying!) bug which occurs when I try and cut and paste
from one window to another. What seems to happen is that the Gnome
session closes and it dumps me into terminal mode. If I type Ctrl-C then
G
On Sat, 24 Jul 2021 10:14:47 -0400
Sam Varshavchik wrote:
> Can anyone think of an even more meaningless kernel bug?
I've had my numlock light turned on at boot forever,
so I've got an /etc/X11/xinit script to turn it off with xset.
Maybe xset could turn off this light too :-).
There's also the built-in speaker mute button that works the same way, and
its behavior is unchanged under 5.13, its orange LED is on only when it
mutes the audio out.
Rebooting 5.12: both mute buttons' LED indicators work as advertised.
Can anyone think of an even more meaningle
Allegedly, on or about 13 October 2014, Gary Artim sent:
> memtest is a util that was, in the past, included on the boot screen.
> I think its been dropped but can be yum installed. check for it with
I don't ever recall seeing it installed by default. I've always had to
manually install it, on a
memtest is a util that was, in the past, included on the boot screen.
I think its been dropped but can be yum installed. check for it with
yum search memtest
it will test your memory out for any faulty locations by move data
patters in and out of all mem locations...
another possibility, but a p
Hi Gary,
Thanks! I also have updated my BIOS (as mentioned in a subsequent post) but I
have continued to have frequent error messages and lockups even with the
mainline vanilla kernel. I have filed bug reports on both kernel.org and fedora
-- hopefully it will be fixed soon.
Btw, what does run
I've had similar error messages and hang of the system (unresponsive,
but powered on). I would check if there is any firmware upgrade you
could apply to the motherboard and also run memtest for 24 hours. I
recently did flash my motherboard and haven't had a hang since, but
its a server/raid and the
On Wed, 24 Sep 2014 07:17:40 -0500 Ranjan Maitra
wrote:
> Hi,
>
> I have been having this issue sometimes (not always but quite
> frequently) upon wakeup from hibernate for the past few days (on a
> newly installed notebook) which is a Dell Precision M3800.
>
> I get the following message on my
Hi,
I have been having this issue sometimes (not always but quite
frequently) upon wakeup from hibernate for the past few days (on a
newly installed notebook) which is a Dell Precision M3800.
I get the following message on my consoles:
Message from syslogd@
kernel:BUG: soft lockup - CPU#1
On Aug 5, 2014, at 7:11 PM, JD wrote:
> On Tue, Aug 5, 2014 at 6:15 PM, Chris Murphy wrote:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1127022
>>
>
> One thing I would suggest is to edit
> /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
> /etc/systemd/system/multi-user
On Tue, Aug 5, 2014 at 6:15 PM, Chris Murphy wrote:
> I filed the nitty gritty details as this bug against NetworkManager even
> though I don't know that it's a Network Manager problem. I don't see any
> kernel messages at all that indicate the kernel is mad or confused.
> https://bugzilla.redhat.
I filed the nitty gritty details as this bug against NetworkManager even though
I don't know that it's a Network Manager problem. I don't see any kernel
messages at all that indicate the kernel is mad or confused.
https://bugzilla.redhat.com/show_bug.cgi?id=1127022
The gist is that if WiFi comes
When I try to run google-chrome after I start a KVM virtual
machine (not inside the VM, mind you, I just have the VM
running). I get this error when attempting to run chrome:
Failed to move to new PID namespace: Cannot allocate memory
This seems to indicate it is actually a kernel bug:
http
On 02/09/2012 01:51 AM, Adrian Sevcenco wrote:
Hi guys! I keep having some stops and blockages in the context of $subj..
Any idea about the problem?
It is not a software problem--it's a CPU or motherboard (mobo)
problem. We've had those on several of our servers (all of them
SuperMicro servers
Hi guys! I keep having some stops and blockages in the context of $subj..
Any idea about the problem?
Thanks!
Adrian
[91464.173992] BUG: soft lockup - CPU#2 stuck for 22s! [khugepaged:82]
[91464.173998] Modules linked in: binfmt_misc ppdev parport_pc lp
parport nf_conntrack_ipv6 nf_defrag_ipv6 i
On Tue, Aug 30, 2011 at 4:59 AM, linux guy wrote:
> You were right about timeout = 0 in grub.conf. I changed it to 15 and I
> can now select a kernel again.
>
> The kernel bug error message is appearing when I run kernel 2.6.40.3-o.fc15.
>
> The Duo runs nicely with kernel 2.
I've just found and followed the magical instructions
here: http://analogbit.com/fix_nvidia_edid to eradicate
the nvidia driver HDMI audio support by convincing it
the TV I'm using doesn't support HDMI audio.
It works great, but I'm wondering why having the HDMI
audio device exist prevented the on
> this is the stupid default timeout=0 in "grub.conf"
>
> hit cursor down multiple times from boot start
> and you should get it
>
> notice at developers:
> please stop hiding everything from the users by default
> this is not why most people using linux!
Hear, hear!
dlg
--
users mailing lis
You were right about timeout = 0 in grub.conf. I changed it to 15 and I
can now select a kernel again.
The kernel bug error message is appearing when I run kernel 2.6.40.3-o.fc15.
The Duo runs nicely with kernel 2.6.38.6-26.rc1.fc15
Its so nice to have the Duo booting again !
--
users
Am 28.08.2011 21:23, schrieb linux guy:
> Its also not displaying the grub kernel selection screen. It just boots.
this is the stupid default timeout=0 in "grub.conf"
hit cursor down multiple times from boot start
and you should get it
notice at developers:
please stop hiding everything from
On Sun, 2011-08-28 at 13:23 -0600, linux guy wrote:
> I get the following when I boot F15 on my Dell Duo.
>
> kernel BUG at drivers/media/media-entity.c 346!
> invalid opcode: [#1] SMP
> Modules linked in: snd_hda_codec_conexant uvcvideo(+) microcode(+)
> snd_hda_intel(+)..
I get the following when I boot F15 on my Dell Duo.
kernel BUG at drivers/media/media-entity.c 346!
invalid opcode: [#1] SMP
Modules linked in: snd_hda_codec_conexant uvcvideo(+) microcode(+)
snd_hda_intel(+)
It goes on from there, including a Call Trace.
My Duo won't boot becau
Does anyone know if the latest kernel for Fedora 15 has fixed the
problem with Advansys SCSI cards?
cpp4ever
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject
On Fri, Jul 15, 2011 at 6:57 AM, Reindl Harald wrote:
>
>
> Am 15.07.2011 15:53, schrieb James McKenzie:
>> On Fri, Jul 15, 2011 at 5:15 AM, Patrick O'Callaghan
>> wrote:
>>> On Fri, 2011-07-15 at 12:24 +0200, admin lewis wrote:
>>>> Hi,
>>&
On Fri, Jul 15, 2011 at 06:53:39 -0700,
James McKenzie wrote:
>
> If it truly is a Kernel bug, should it not be reported to the Kernel
> folks? If it is a bug with one of the kernels built by the project,
> yep it should be reported to the Fedora bugzilla.
There are advantages t
Am 15.07.2011 15:53, schrieb James McKenzie:
> On Fri, Jul 15, 2011 at 5:15 AM, Patrick O'Callaghan
> wrote:
>> On Fri, 2011-07-15 at 12:24 +0200, admin lewis wrote:
>>> Hi,
>>> where I have to post for a kernel bug ?
>>> thanks lewis.
>>
On Fri, Jul 15, 2011 at 5:15 AM, Patrick O'Callaghan
wrote:
> On Fri, 2011-07-15 at 12:24 +0200, admin lewis wrote:
>> Hi,
>> where I have to post for a kernel bug ?
>> thanks lewis.
>
> Instead posting it, report it to Bugzilla: http://bugzilla.redhat.com
If it
On 07/15/2011 01:15 PM, Patrick O'Callaghan wrote:
> On Fri, 2011-07-15 at 12:24 +0200, admin lewis wrote:
>> Hi,
>> where I have to post for a kernel bug ?
>> thanks lewis.
>
> Instead posting it, report it to Bugzilla: http://bugzilla.redhat.com
You should se
Am 15.07.2011 12:24, schrieb admin lewis:
> Hi,
> where I have to post for a kernel bug ?
> thanks lewis.
the same as for all other bugs
https://bugzilla.redhat.com/
signature.asc
Description: OpenPGP digital signature
--
users mailing list
users@lists.fedoraproject.org
To unsub
On Fri, 2011-07-15 at 12:24 +0200, admin lewis wrote:
> Hi,
> where I have to post for a kernel bug ?
> thanks lewis.
Instead posting it, report it to Bugzilla: http://bugzilla.redhat.com
poc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscriptio
Hi,
where I have to post for a kernel bug ?
thanks lewis.
--
my blog - http://predellino.blogspot.com/
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org
On 09/19/2010 01:18 AM, Gilboa Davara wrote:
> On Sat, 2010-09-18 at 21:08 -0400, Genes MailLists wrote:
>>
>>
>> The machine has 3 intel nic's -
>>
>> lspci | egrep -i ethernet
>> 04:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
>> Controller (rev 01)
>> 05:04.0 Ethernet
On Thursday, August 19, 2010 01:07:21 am Antonio Olivares did opine:
> Dear folks,
>
> I have downloaded/compiled and installed kernel 2.6.35.2 on one of my
> machines. I get the above bug with details following:
>
> I get the message that there is a kernel oops, but I can't report it
> since th
Dear folks,
I have downloaded/compiled and installed kernel 2.6.35.2 on one of my machines.
I get the above bug with details following:
I get the message that there is a kernel oops, but I can't report it since the
kernel is not a Fedora kernel and abrt does not work :(
Is there a way I can s
Robert Arkiletian wrote:
> Any chance this
> http://news.softpedia.com/news/Critical-Vulnerability-Silently-Patched-in-Linux-Kernel-152678.shtml
>
> will be fixed for F11? I know F11 is EOL but sometimes this has been
> overlooked if it's a really big bug, like this one.
>
>
Is there a particula
On Wed, 18 Aug 2010 14:16:07 -0700
Robert Arkiletian wrote:
> Any chance this
> http://news.softpedia.com/news/Critical-Vulnerability-Silently-Patched-in-Linux-Kernel-152678.shtml
>
> will be fixed for F11? I know F11 is EOL but sometimes this has been
> overlooked if it's a really big bug, like
Any chance this
http://news.softpedia.com/news/Critical-Vulnerability-Silently-Patched-in-Linux-Kernel-152678.shtml
will be fixed for F11? I know F11 is EOL but sometimes this has been
overlooked if it's a really big bug, like this one.
--
Robert Arkiletian
Eric Hamber Secondary, Vancouver, Cana
On 03/31/2010 04:58 PM, NoSpaze wrote:
> Hi. Yesterday I updated to kernel 2.6.32.10-90.fc12.i686. When booting,
> I got this BUG (likely reported by udev in the photo):
>
> http://otbits.blogspot.com/2010/03/bug-photo-20100331.html
>
> Now I'm booting by choosing previous kernel on Grub
> (2.6.3
Hi. Yesterday I updated to kernel 2.6.32.10-90.fc12.i686. When booting,
I got this BUG (likely reported by udev in the photo):
http://otbits.blogspot.com/2010/03/bug-photo-20100331.html
Now I'm booting by choosing previous kernel on Grub
(2.6.32.9-70.fc12.i686). At first, felt like a disk error,
51 matches
Mail list logo
