Am 15.01.19 um 09:21 schrieb Sumantro Mukherjee:
> Hey All,
>
> Today 2019-01-15 will be Kernel 4.20 Test Day[0] Test Day! As Fedora 29
> will be getting 4.20, we want to test it across all arcs and different
> variants of F28 and F29.
>
> So this is an important Test Day! Test Day will focus
Am 08.01.19 um 23:54 schrieb Joseph D. Wagner:
> IIRC, there is major performance degradation (anti-Spectre) in 4.20 that
> will be turned off by default 4.21.
>
> Will it be turned off by default in the 4.20 rebase?
that is mostly reduced with 4.20 to begin with
not even talking that 4.19.x
55f6ca2fab48 CR3: 2242e003
CR4: 001606f0
Am 24.12.18 um 14:07 schrieb Reindl Harald:
> https://bugzilla.redhat.com/show_bug.cgi?id=1659706
>
> i triggered something similar as
> https://www.spinics.net/lists/netdev/msg533254.html recently with
> 4.19.12-200.fc28.x86_64
CR0: 80050033
[Mon Dec 24 13:49:01 2018] CR2: 564a46078000 CR3: 1951e005
CR4: 001606f0
Am 15.12.18 um 04:04 schrieb Reindl Harald:
> am i really the only one where 4.19.x up to 4.19.9 randomly crashes?
>
> on my homeserver it takes some hours, a to
am i really the only one where 4.19.x up to 4.19.9 randomly crashes?
on my homeserver it takes some hours, a ton of virtual machines on ESXi
6.5 are running stable all the time but on a NAT-Firewall guest it
survives just a few seconds until "kernel panic - Fatal exception in
interrupt" and a
Am 12.12.18 um 20:28 schrieb Chris Murphy:
> But upon reboot, total implosion. Piles of USB errors and disconnects
> (the boot device is a Samsung FIT USB stick which fits flush in an
> Intel NUC). I didn't have time to troubleshoot what's causing this
> problem, other than to plug the USB stick
Am 05.12.18 um 00:23 schrieb Laura Abbott:
> On 12/3/18 8:46 AM, Reindl Harald wrote:
>>
>> Am 03.12.18 um 17:42 schrieb Laura Abbott:
>>> On 12/2/18 6:20 AM, Reindl Harald wrote:
>>>> how does Fedora think to handle
>>>> https://bugzilla.ker
Am 03.12.18 um 17:42 schrieb Laura Abbott:
> On 12/2/18 6:20 AM, Reindl Harald wrote:
>> how does Fedora think to handle
>> https://bugzilla.kernel.org/show_bug.cgi?id=201685
>>
>> 4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs
>> fine
Am 03.12.18 um 08:56 schrieb Peter Robinson:
> On Sun, Dec 2, 2018 at 5:04 PM Sérgio Basto wrote:
>>
>> yeah yestarday my computer don't boot with kernel-4.18.20 , back to
>> kernel-core-4.18.19-100.fc27.x86_64.
>>
>> Thanks for the tip
>>
>> It might be related with [1] ?
>> "I see that a
how does Fedora think to handle
https://bugzilla.kernel.org/show_bug.cgi?id=201685
4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs
fine on F28 systems but given that bug upgrade to 4.19.x seems to be
just a lottery with your data - on some or even many systems all seems
to
after having a new firewall system with F28 running for over 3 weeks
without any issue last saturday at 9:30 crash with 4.18.15 (see
screenshot from VMware HA)
guilty conscience for holding back kernel updates -> 4.18.18
today at nearly the same time identical error
Am 07.09.18 um 06:11 schrieb Reindl Harald:
> https://www.phoronix.com/scan.php?page=news_item=Linux-4.18.6-Stable-Out
>
> https://koji.fedoraproject.org/koji/packageinfo?packageID=8
>
> kernel-4.18.6-300.fc29labbott 2018-09-06 01:05:35
> kern
Am 07.09.18 um 02:41 schrieb Laura Abbott:
> On 08/14/2018 09:14 AM, Laura Abbott wrote:
>> Hi,
>>
>> As you probably saw, 4.18 was released on Sunday. The 4.18 kernel was
>> built for rawhide yesterday. We will be following roughly the same
>> rebase schedule as in the past. F28 will get the
Am 15.08.2018 um 23:25 schrieb Laura Abbott:
> On 08/15/2018 01:21 PM, Reindl Harald wrote:
>> * Di Aug 14 2018 Justin M. Forbes -
>> 4.17.14-101
>> - Fix "Foreshadow" CVE-2018-3620 CVE-2018-3646 (rhbz 1585005 1615998)
>>
>> -
>>
>>
* Di Aug 14 2018 Justin M. Forbes - 4.17.14-101
- Fix "Foreshadow" CVE-2018-3620 CVE-2018-3646 (rhbz 1585005 1615998)
-
CentOS 6: 2.6.32-754.3.5.el6.x86_64
[root@honeypot:~]$ grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE
Am 14.08.2018 um 19:16 schrieb Justin Forbes:
> On Tue, Aug 14, 2018 at 11:14 AM, Laura Abbott wrote:
>> As you probably saw, 4.18 was released on Sunday. The 4.18 kernel was
>> built for rawhide yesterday. We will be following roughly the same
>> rebase schedule as in the past. F28 will get
Am 30.07.2018 um 18:02 schrieb stan:
> Then just a build with
> rpmbuild -bb kernel.spec
>
> I don't see where any config files that weren't in the src.rpm could
> come from, as the BUILD directory is recreated every time the -bb
> command is run. I have some other kernel-4.xx files in there
the list-footer has exactly two lines
just look at the second one
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
___
kernel
Am 05.02.2018 um 17:43 schrieb Justin Forbes:
On Sat, Feb 3, 2018 at 10:19 PM, Reindl Harald <h.rei...@thelounge.net
<mailto:h.rei...@thelounge.net>> wrote:
should i file a bug against the kernel or X11 here?
i have a new AOC 31.5" screen with 2560x1440 connectd via
Am 09.02.2018 um 17:53 schrieb Laura Abbott:
On 01/29/2018 02:32 AM, Laura Abbott wrote:
Hi,
4.15 was released on Sunday. Fedora will be following the same rebase
procedure that we have in the past: After a few stable releases,
typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26
how can it be that now after GCC with retpoline support is even
available for users the kernel builds suddenly using an old one?
__
4.14.16-300.fc27.x86_64
Kernel compiled with a retpoline-aware compiler: YES (kernel reports
full retpoline compilation)
should i file a bug against the kernel or X11 here?
i have a new AOC 31.5" screen with 2560x1440 connectd via display port
to a i7-3770 which works fine after boot and as long as i don't try to
switch to a VT also continues to work as expected
but wehn the screen is longer powered of and you
Am 29.01.2018 um 11:32 schrieb Laura Abbott:
4.15 was released on Sunday. Fedora will be following the same rebase
procedure that we have in the past: After a few stable releases,
typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26
rebased shortly there after. I would expect this
Am 29.01.2018 um 11:32 schrieb Laura Abbott:
4.15 was released on Sunday. Fedora will be following the same rebase
procedure that we have in the past: After a few stable releases,
typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26
rebased shortly there after. I would expect this
does the running build
https://koji.fedoraproject.org/koji/buildinfo?buildID=1019102 already
use GCC 7.2.1-7 build
(https://koji.fedoraproject.org/koji/buildinfo?buildID=1017750) which is
needed to get the full retpoline support in the kernel build?
* Wed Jan 17 2018 Jakub Jelinek
Am 14.11.2017 um 12:33 schrieb Reindl Harald:
Am 14.11.2017 um 12:22 schrieb Gerd Hoffmann:
This is really useful work. I'm already seeing ~20% battery
improvement with Fedora 27 + 4.14.0-0.rc8.git3.1.fc28.x86_64 on an HP
Spectre, and so far no regressions. I get better battery life
Am 14.11.2017 um 12:22 schrieb Gerd Hoffmann:
This is really useful work. I'm already seeing ~20% battery
improvement with Fedora 27 + 4.14.0-0.rc8.git3.1.fc28.x86_64 on an HP
Spectre, and so far no regressions. I get better battery life with
this combination than running Windows 10 with all
Am 20.06.2017 um 01:30 schrieb Laura Abbott:
Hi,
If you haven't seen it, a new kernel vulnerability was announced
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
Updates have been filed in bodhi with the fix
https://bodhi.fedoraproject.org/updates/FEDORA-2017-1225995344
ing-ssd-ephemeral-disks-in-ec2-part-2/
i really have no ieda what you try to tell me
please look again at the subject and the mdadm output because *they are*
set "writemostly" but there is way too much read-io on the HDD's
On 11.02.2017 15:16, Reindl Harald wrote:
/dev/sda: Samsung S
/dev/sda: Samsung SSD 850 EVO 2TB
/dev/sdb: Samsung SSD 850 EVO 2TB
/dev/sdc: ST2000DX002-2DV164
/dev/sdd: ST2000DX002-2DV164
normally i would expect that for heavy read-IO the two HDD drives would
sleep and the two SSD working more or less like a RAID0 but as example
running a btrfs-srub
Am 10.01.2017 um 17:16 schrieb Laura Abbott:
4.9.2 has been built in koji and filed as an update in bodhi for F25. Once
F25 gets some testing, F24 will be updated as well. As always, please test
and give appropriate karma.
thanks - it's running on my F24 testserver as well as that machine
Am 22.11.2016 um 12:06 schrieb Felix Miata:
I was looking at early portions of dmesg for anything resembling clues
and noticed that early microcode messages are not always reported for
every core present
well, i doubt that every *core* needs to get the microcode or different
cores can even
CTRL+ALT+F2 and the message below appears every 5 seconds on the VT and
in the syslog while when running the dsiplaymanager or GUI all is fine
over days
*what* does the kernel here?
nobody is taking away the mouse and it's working perfect on the GUI
Nov 21 08:59:47 srv-rhsoft kernel: usb
i would call that a regression within a stable release and this default
should be changed in the fedora kernel!
looks like iwth kernel 4.7 you need "net.netfilter.nf_conntrack_helper =
1" in sysctl.conf to continue things like PASV FTP or Hylafax (which
uses FTP as procotocol) working like
Am 17.04.2016 um 04:09 schrieb Marcelo Ricardo Leitner:
Cc'ing netfilter@ too
Thread:
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org/thread/CLNQ6O6OGNEJAFFSNV56KU6P2JAPM5YU/
Em 16-04-2016 10:52, Reindl Harald escreveu:
Am 15.04.2016 um 10:16 schrieb Reindl
Am 14.04.2016 um 23:53 schrieb Marcelo Ricardo Leitner:
Otherwise it won't be able to expect the new connection
sounds reasonable, on the other side the client yesterday had troubles
to make passive ftp connections with "connection refused" as far as the
admin was able to tell on the phone
"Disabling early microcode, because kernel does not support it.
CONFIG_MICROCODE_[AMD|INTEL]_EARLY!=y" seems to be back with all 4.4
kernels, i remember that message due update was fixed in the past
___
kernel mailing list
i see such messages in dmesg repeatly on several machines
most likely some form of attacks since it affects in random intervals
any machine with a public IP and seems to be pretty new at all
why is there no source IP logged?
[501585.285984] conntrack: generic helper won't handle protocol
Am 19.02.2016 um 02:51 schrieb Laura Abbott:
4.4.2 is currently building and should be in updates-testing soon. As
usual,
please test and give karma appropriately (negative karma for new issues,
not existing issues)
i don't see a running build here
result is that the package is installed but nothing in /boot
/bin/kernel-install: Zeile 95: Syntaxfehler beim unerwarteten Wort `done'
/bin/kernel-install: Zeile 95: `done'
Warnung: %posttrans(kernel-core-4.4.0-0.rc0.git1.1.fc24.x86_64)
Scriptlet fehlgeschlagen,
i switched from noatime,nodiratime to relatime,nodiratime,lazytime
which seems to lead in unexpected mtime changes for a lot of files
leading in rkhunter alerts and likely rsync problems
May 15 13:35:51 Installed: kernel-core-4.0.3-201.fc21.x86_64
May 15 13:35:54 Installed:
Am 19.05.2015 um 17:25 schrieb Eric Sandeen:
On 5/19/15 4:14 AM, Reindl Harald wrote:
i switched from noatime,nodiratime to
relatime,nodiratime,lazytime which seems to lead in unexpected
mtime changes for a lot of files leading in rkhunter alerts and
likely rsync problems
The cargo-cult
Am 08.05.2015 um 16:51 schrieb Don Zickus:
On Thu, May 07, 2015 at 04:29:11PM -0500, Ian Pilcher wrote:
On 05/06/2015 02:00 PM, Josh Boyer wrote:
On Wed, May 6, 2015 at 2:53 PM, Jarod Wilson ja...@redhat.com wrote:
One other thought: what happens when /boot is on the same file system as
/usr
Am 04.05.2015 um 19:22 schrieb har...@redhat.com:
From: Harald Hoyer har...@redhat.com
This patch is to install everything to /lib/modules/$KERNEL_VERSION
and only have %ghost files for /boot files.
Installation in %posttrans with kernel-install should work already.
F20: systemd = 208-31
Am 16.02.2015 um 17:03 schrieb Eric Sandeen:
On 2/16/15 10:00 AM, Reindl Harald wrote:
the corruption itself may come from
https://bugzilla.redhat.com/show_bug.cgi?id=1192834 which is also really strange
Let's continue the discussion in that bug, if this behavior is a result
Am 16.02.2015 um 12:47 schrieb Michael D. Setzer II:
On 16 Feb 2015 at 11:30, Reindl Harald wrote:
/dev/sda1 is a ordinary partition containing only /boot
why does the kernel report it is in use?
The kernel reports it as being mount
but why
since it normally is as part of the boot
Google around brings no clear statement
is there any drawback of boot with transparent_hugepage=always which
seems not to be the default currently - as far as i understand it should
recude the overhead of memory management (especially in virtual guests)
and seems to have been the default for
am i the only one which can't mount fuse as normal user with
3.16.6-203.fc20.x86_64?
__
[harry@rh:~]$ mount /mnt/arrakis
fuse: failed to open /dev/fuse: Permission denied
[harry@rh:~]$ mount /mnt/mail-gw
fuse: failed to open /dev/fuse: Permission
nevermind - seems to only affect the workstation in front of me and
somehow related to update systemd from koji without reboot because
weekly raid-check
the homeserver with the same systemd and kernel packages has 0666 as
expected
Am 30.10.2014 um 12:11 schrieb Reindl Harald:
am i the only
i wonder if 3.16.7 contains all the 3.16.3 CVE-fixes from
https://koji.fedoraproject.org/koji/buildinfo?buildID=587751 and the
previous 3.16.6 ones from Fedora because
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.16.7 dont
mention them?
Hi
i know there was 3.15.3 released today
however, i catched the 3.15.2-200 last night and liked to
say that it works fine on two phyiscal machines as well
as on 2 virtual servers here
IvyBdrige (HP Compaq Elite 8300)
SandyBridge (HP Compaq Elite 8200)
P.S.:
survived also a raid-check on 4 TB
Am 01.07.2014 17:30, schrieb Josh Boyer:
On Tue, Jul 01, 2014 at 05:12:13PM +0200, Reindl Harald wrote:
i know there was 3.15.3 released today
however, i catched the 3.15.2-200 last night and liked to
say that it works fine on two phyiscal machines as well
as on 2 virtual servers here
Am 23.06.2014 20:52, schrieb Bruno Wolff III:
On Mon, Jun 23, 2014 at 11:34:53 -0700,
Adam Williamson awill...@redhat.com wrote:
systemd doesn't just 'create init files', I don't think. It *does* have
a concept of dependencies, which could account for this effect.
Something is creating
Am 11.06.2014 00:00, schrieb poma:
On 08.06.2014 11:11, Gilboa Davara wrote:
On Fri, Jun 6, 2014 at 1:28 AM, Reindl Harald h.rei...@thelounge.net wrote:
sadly both re-opened today, after some hours of
running shutdown and raid-check with 3.14 is a
pain and taht is *for sure* 3.14.x because
Am 06.06.2014 00:28, schrieb Reindl Harald:
sadly both re-opened today, after some hours of
running shutdown and raid-check with 3.14 is a
pain and taht is *for sure* 3.14.x because my
co-developer stayed at the last 3.13 until i
thought it's fine now, had never that problems
and both 3.14
:10, schrieb Reindl Harald:
https://bugzilla.redhat.com/show_bug.cgi?id=1096414
https://bugzilla.redhat.com/show_bug.cgi?id=1092937
*both* seems to be fixed with 3.14.5-200.fc20.x86_64
while i am unable to find the relevant change in
the kernel-upstream-changelog
would be nice to know
Am 12.05.2014 21:46, schrieb Josh Boyer:
On Mon, May 12, 2014 at 3:41 PM, Reindl Harald h.rei...@thelounge.net wrote:
Hi
* Tue May 06 2014 Josh Boyer jwbo...@fedoraproject.org
- CVE-2014-0196 pty race leading to memory corruption (rhbz 1094232 1094240)
is that only missing in the kernel
Am 07.05.2014 22:40, schrieb Chase Southwood:
On Wednesday, May 7, 2014, poma pomidorabelis...@gmail.com wrote:
bodhi, autoqa, hreindl, drago01, roshi, bradw, aleph, bojan, Anonymous
Tester, freddyw, dandim, amluto, csouth3, mstevens, abderrahman, amessina,
bitlord, xosevp, quickbooks,
Am 01.05.2014 15:06, schrieb Reindl Harald:
Am 01.05.2014 14:55, schrieb Bruno Wolff III:
The bug I reported to upstream is:
https://bugzilla.kernel.org/show_bug.cgi?id=68061
That was for 3.13, so if you were running into a varient of the problem I
was seeing, you should have seen
has anybody else faced complete freezes of a machine
due raid-check? today the same as last thursday while
the freeze seems not to happen by the raid-check itself
according to running smokepings from outside which are
green until i try to use the machine
* last thursday morining around 8:30 while
Am 01.05.2014 14:12, schrieb Bruno Wolff III:
On Thu, May 01, 2014 at 11:18:25 +0200,
Reindl Harald h.rei...@thelounge.net wrote:
has anybody else faced complete freezes of a machine
due raid-check? today the same as last thursday while
the freeze seems not to happen by the raid-check itself
Am 01.05.2014 14:55, schrieb Bruno Wolff III:
The bug I reported to upstream is:
https://bugzilla.kernel.org/show_bug.cgi?id=68061
That was for 3.13, so if you were running into a varient of the problem I was
seeing, you should have seen it in
3.13. I did not see the problem with 3.14 or
Hi
where is this dependency from?
after confirm you can happily yum remove linux-firmware without
any problems and the next kernel update pulls it again which is
not how a normal dependency works because it would not allow
to uninstall the dependency without remove the pulling package
hence why
Am 01.05.2014 19:28, schrieb Josh Boyer:
On Thu, May 1, 2014 at 1:24 PM, Reindl Harald h.rei...@thelounge.net wrote:
where is this dependency from?
From the explicit Requires(pre) in the kernel-core RPM.
after confirm you can happily yum remove linux-firmware without
any problems
Am 23.04.2014 09:37, schrieb Jóhann B. Guðmundsson:
On 04/22/2014 07:40 PM, Reindl Harald wrote:
so no - there is no need for a subpackage
Anything that requires manual setup on behalf of the
user/administrator to work or a half baked mod probing/calculating
script to decide how many
Am 23.04.2014 10:28, schrieb Jóhann B. Guðmundsson:
On 04/23/2014 08:18 AM, Reindl Harald wrote:
what is you problem?
I'm perfectly problem free I just happen to know how broken zram after having
to patch udev for a race condition it
had with swapon
* it's not enabled by default
Original-Nachricht
Betreff: does zram in fedora need any configuration
Datum: Thu, 27 Mar 2014 17:18:09 +0100
Von: Reindl Harald h.rei...@thelounge.net
Organisation: the lounge interactive design
An: Mailing-List fedora-kernel kernel@lists.fedoraproject.org
Hi
since 3.14
Am 22.04.2014 19:17, schrieb Jóhann B. Guðmundsson:
On 04/22/2014 01:38 PM, Josh Boyer wrote:
I have a rawhide VM here too, it has nothing related to zram
configuration, and the module isn't loaded.
Nor should it be it's going to take us sometime to implement this correctly
into the
Am 22.04.2014 20:34, schrieb Jóhann B. Guðmundsson:
On 04/22/2014 05:31 PM, Reindl Harald wrote:
why do you need a sub-package?
To add the files and configuration similar to what you are using.
Zram does not work out of the box as in it requires manual administrator or
user setup so
Hi
since 3.14 is not that far away zram becomes interesting
the article below maybe outdated, on a rawhide-VM exists
/dev/zram0 as well as a implicit systemd-unit, well
does that mean it is automagically configured and if
that is the case does systemd 212 that also or is
there handwork needed
in case of cloud / virtualization i wonder what is the
state of zram in the Fedora Kernel, zswap is available
and can be enabled with zswap.enabled=1 as boot paran
but zswap is more for a overcommited host to avoid disk paging
zram IMHO would be interesting for the guest systems and
both
Am 08.03.2014 21:00, schrieb Josh Boyer:
On Sat, Mar 8, 2014 at 1:26 PM, Reindl Harald h.rei...@thelounge.net wrote:
in case of cloud / virtualization i wonder what is the
state of zram in the Fedora Kernel, zswap is available
and can be enabled with zswap.enabled=1 as boot paran
but zswap
Am 06.03.2014 18:04, schrieb Don Zickus:
Maybe impose only xfs as the fs of choice or some other restrictions and
chop it further, but then we lose flexibility
hopefully a joke :-)
* i use a ton of virtual Fedora instances
* any of them is using ext4
* some may benefit from XFS but not that
Am 05.03.2014 16:02, schrieb Josh Boyer:
FWIW, the existing kernel package installed today (a debug kernel
even) is ~142 MB. 123MB of that is the /lib/modules content. ~6MB of
that is vmlinuz. The remaining 13MB is the initramfs, which is
actually something that composes on the system
Am 05.03.2014 17:28, schrieb Kevin Fenzi:
On Wed, 5 Mar 2014 10:16:21 -0500
Don Zickus dzic...@redhat.com wrote:
Also, I just arbitrarly threw out 100MB, if we should start higher,
say 150MB, then it doesn't matter to me. :-)
This entire disk size optimization seems kind of weird to
Am 05.03.2014 17:45, schrieb Kevin Fenzi:
On Wed, 05 Mar 2014 17:37:42 +0100
Reindl Harald h.rei...@thelounge.net wrote:
Am 05.03.2014 17:28, schrieb Kevin Fenzi:
On Wed, 5 Mar 2014 10:16:21 -0500
Don Zickus dzic...@redhat.com wrote:
Also, I just arbitrarly threw out 100MB, if we should
Am 04.03.2014 15:22, schrieb Peter Senna Tschudin:
I found a probable bug on this Kernel package related to Intel
graphics adapter and high resolution monitor. When booting with this
Kernel, my two screens never wake-up. What information should I gather
to fill an useful bug report?
which
Am 28.02.2014 16:49, schrieb Josh Boyer:
On Fri, Feb 28, 2014 at 10:39 AM, Kyle McMartin k...@redhat.com wrote:
On Fri, Feb 28, 2014 at 10:13:29AM -0500, Josh Boyer wrote:
It's been a while since I sent one of these. Mostly that's due to the
overlap between which upstream stable version
Am 27.02.2014 10:34, schrieb poma:
The last occurrences of the iwlagn,
- RHEL6.2
/lib/modules/2.6.32-220.23.1.el6.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
- F16
/lib/modules/3.1.5-6.fc16.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
replaced by the iwlwifi,
- F20
Feb 20 12:27:20 Installed: kernel-3.13.3-100.fc19.x86_64
installed a view hours ago on a storage VM with around
2 TB luks-encrypted disks, so far all fine
___
kernel mailing list
kernel@lists.fedoraproject.org
but not that big deal if machine
Am 20.02.2014 21:59, schrieb Justin M. Forbes:
Thanks, that was kind of a prebuild, the update for rebase should be
happening tonight with 3.13.4.
Justin
On Thu, 2014-02-20 at 19:12 +0100, Reindl Harald wrote:
Feb 20 12:27:20 Installed: kernel-3.13.3-100.fc19
Feb 21 01:20:09 Installed: kernel-3.13.4-100.fc19.x86_64
looks fine too, the daily backup on the 2 TB encrypted disk
starts within the next 10 minutes, so tomorrow fine for karma
Am 20.02.2014 22:11, schrieb Reindl Harald:
i guessed so, since i am watching koji regulary to get a picture what
Am 07.02.2014 15:21, schrieb James Harrison:
I remember the times when Redhat software releases (6.2, 7.3, 8, 9) had a
specific kernel for AMD and Intel CPUs.
times are changing
Now forward on to present day and Red Hat software has one kernel build for
AMD and Intel CPUs.
When was the
/mailman/listinfo/kernel
--
Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / CISO / Software-Development
m: +43 (676) 40 221 40, p: +43 (1) 595 3999 33
icq: 154546673, http://www.thelounge.net/
http://www.thelounge.net/signature.asc.what.htm
Am 26.01.2014 23:53, schrieb Ravindra Kumar:
Thanks Reindl for reporting the issue.
I have forwarded your message to the developers responsible for pvscsi driver.
Thanks,
Ravindra
thank you very much!
___
kernel mailing list
may somebody of VMware Inc. please take a look at
https://bugzilla.redhat.com/show_bug.cgi?id=926917
these messages appear in dmesg in case of debug-kernels for a long time
and given that we speak about the main storage driver that leaves a
bad taste
[ 15.641689] scsi2 : VMware PVSCSI storage
Hi
Am 21.01.2014 15:02, schrieb Josh Boyer:
I'll be starting the 3.14 merge window kernels sometime later today.
As usual, I'll do my best on the various arch configs and would
appreciate if people could look them over as the flow in.
For those wanting to get additional patches in, please
not sure if the depmod-message does any harm (not for me at least)
if i understand the message correctly hci_vhci may not be loaded
[harry@srv-rhsoft:~]$ rawhide
Last login: Mon Jan 20 20:33:24 2014 from 192.168.196.1
[root@rawhide ~]# yum update
Am 21.01.2014 01:43, schrieb Josh Boyer:
On Tue, Jan 21, 2014 at 12:26:47AM +0100, Reindl Harald wrote:
not sure if the depmod-message does any harm (not for me at least)
if i understand the message correctly hci_vhci may not be loaded
This has already been reported:
https
Hi
i recently installed the latest kernel-build from today
not i could say anything doe not work but maybe it's worth to look
at the dmesg-stacktrace at the bottom of my message, from my little
understanding it looks soundcard-related, however, MPD is playing
music fine - no visible regressions
Am 21.11.2013 18:23, schrieb Lance Lassetter:
If Fedora takes this route then why not cut out all server software
altogether and just make it a desktop OS
because people including me loving to have the same OS on their servers as on
their desktop machine to have F-1 in production and a few
please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1013054
especially the changes in 3.11.2 and that it happened exactly 24 hours
later again while my personal machine until yesterday was not affected
https://bugzilla.redhat.com/show_bug.cgi?id=1013054#c2
3.11.1-200.fc19.x86_64 works fine on my homeserver,
office-workstation and as VMware Workstation guest
* iptables NAT (LAN/WAN/WLAN/Bridge)
* openVPN gateway to company
* two WLAN AP's
* VMware Workstation NAT
* services like httpd/dbmail/postfix/mariadb
the bug from 3.11.0 as VMware guest to
Hi
since AFAIK in new fedora-releases the microocode is bundeled
with the kernel maybe relevant for the kernel-team in case
it is not already targeted
Intel processor microcode security update
http://lists.debian.org/debian-user/2013/09/msg00126.html
Am 08.09.2013 20:52, schrieb Josh Boyer:
On Sun, Sep 8, 2013 at 2:41 PM, Reindl Harald h.rei...@thelounge.net wrote:
since AFAIK in new fedora-releases the microocode is bundeled
with the kernel maybe relevant for the kernel-team in case
it is not already targeted
The microcode
95 matches
Mail list logo
