Am 24.07.2016 um 22:07 schrieb Andreas Henriksson:
>
> Are you sure this is the correct syntax? I would expect that you
> should specify the mountpoint (target directory) rather than the
> source of the mount. eg. mount /home/ingo/leo.Bilder
> Do using that still give you the same
Some additional Information which probably helps to find the root cause:
The very same beheaviour (as in Jessie) is still shown in Stretch.
I already tried to assign that bug to package "mount", but this was not
accepted. The corresponding bug report demonstrates some more
possibilities of "how y
192.168.33.0/24
/etc/fstab entries on the clients (Jessi and Wheezy):
leo:/Bilder /home/ingo/leo.Bilder nfs4 noauto,rw,user,soft,relatime 0 0
In Wheezy all works as expected, in Jessie mount fails with:
$ LANG=en_US.UTF-8 mount leo:/Bilder
mount: leo:/Bilder: No such file or directory
192.168.33.0/24
/etc/fstab entries on the clients (Jessi and Wheezy):
leo:/Bilder /home/ingo/leo.Bilder nfs4 noauto,rw,user,soft,relatime 0 0
In Wheezy all works as expected, in Jessie mount fails with:
$ LANG=en_US.UTF-8 mount leo:/Bilder
mount: leo:/Bilder: No such file or directory
eo:/Bilder
~$ mount.nfs: no mount point provided
Adding the mountpoint works for both mount and umount:
~$ /sbin/mount.nfs leo:/Bilder /home/ingo/leo.Bilder
~$ /sbin/umount.nfs /home/ingo/leo.Bilder
So, the dead end lies in /sbin/mount which is unable to evaluate the
fstab and parse it properly to mount.nf
Am 01.08.2016 um 15:33 schrieb Andreas Henriksson:
> Hello again Ingo.
>
> On Mon, Jul 25, 2016 at 10:13:29AM +0200, Ingo wrote:
>> Am 24.07.2016 um 22:07 schrieb Andreas Henriksson:
>>>
>>> Are you sure this is the correct syntax? I would expect that you
>>
Here is a link for the Ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746
Attached is also the result of lshw for my system (in case it helps).
dicker
description: Computer
width: 32 bits
*-core
description: Motherboard
physical id: 0
Unbelievable but true, a recent update of a single package in Etch (I cannot
recall which) appears to have fixed all problems.
I have commented out the ehci_hcd from my /etc/modules/blacklist file and here
is my latest dmesg:
usb 3-1: new high speed USB device using ehci_hcd and address 2
usb 3
On Sat, 9 Jul 2022 10:36:40 +0200 Marcin Juszkiewicz
wrote:
On Sat, 11 Jun 2022 17:58:18 +0200 Diederik de Haas > wrote:
>> On Sun, 9 Jan 2022 23:20:49 +0100
Frode Severin Hatlevik >> wrote: >>> I just
updated my Debian amd64 system from Buster to Bullseye as >>> per >>>
https://www.debian.
Package: src:linux
Version: 6.9.8-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Regular upgrade of trixie.
* What exactly did you do (or not do) that was effective (or ineffective)?
sudo apt full-upgrade
* What was the outcome of this action?
On boot up the kernel reports
github:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/sound/usb/mixer.c?id=e182534d4bd3a779941f2868f35e1f66a8d36cea
Jessie kernel works fine and has the patched version of /sound/usb/mixer.c.
Please include the patch in next update of Wheezy kernel.
Regards,
Ingo
--
To UNSUBSCR
t in /etc/pulse/default.pa.
(Command not documented in 'man pactl')
The message "Unlikely big volume range" in syslog is just cosmetic.
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
comments.gmane.org/gmane.linux.kernel.cpufreq/11000
and a fix/patch was published here:
https://lkml.org/lkml/2013/7/11/661
/Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130927183449.3174.23177.report...@tux.home
gmane.org/gmane.linux.kernel.cpufreq/11000
and a fix/patch was published here:
https://lkml.org/lkml/2013/7/11/661
/Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5245d286.1010...@gmx.net
Delete me
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5245d785.6010...@gmx.net
Today I tried to gather further information and found:
before s2ram:
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
160
160
160
160
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
380
380
380
380
after resume from s2ram:
cat /sys/devices/sy
According to my tests this nasty bug (which I observed mainly with
VirtualBox and OS/2 guest) has been fixed with the recent kernel update
in Wheezy to 3.2.0-51.
My guess is this commit which cured the freezes:
commit 884020bf3d2a3787a1cc6df902e98e0eec60330b upstream.
After any "soft gfx res
~$ /sbin/mount.nfs leo:/Bilder /home/ingo/leo.Bilder
~$ /sbin/umount.nfs /home/ingo/leo.Bilder
That's why I assigned it also to Package: mount.
Today I checkes in Stretch: still the same issue.
Am 26.01.2013 19:06, schrieb Debian Bug Tracking System:
> Processing commands for cont...@bugs.debian.org:
>
>> severity 689268 important
> Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge)
> graphics freeze
> Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freez
l test as soon as headers
are available - please let me know.
/Ingo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlEFDI8ACgkQx2YcFfrwLxMAUACfQ/9YomlVoJk1V1+YBfrMo+Op
AckAnA1XiU/xGlRnoT+LV3cGhOtpK6XV
=I
I now tested Julien's kernel for 4 days under various conditions and all
ist solid so far. No freezes, everything works fine. I'll keep on
testing and report finally in bug #687442.
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubs
switch back to
standard Wheezy-kernel without beeing scared for my hardware.
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5113fc5a.6040...@gmx.net
Many THANKS to Julien and Ben for fixing this (and pending) bugs.
I have immediately switched from vanilla 3.4 kernel to Debian's
3.2.0-39-1 from unstable.
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
ake[2]: *** [_module_/var/lib/dkms/virtualbox/4.1.18/build] Fehler 2
make[1]: *** [sub-make] Fehler 2
make: *** [all] Fehler 2
make: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
I am back on kernel 3.2.39-2 and all works as expected.
Ingo
--
To UNSUBSCRIBE, email to debian-k
I checked the package from
http://ftp.debian.org/debian/pool/main/l/linux/linux-headers-3.2.0-4-common_3.2.41-1_amd64.deb
it is just 209k and almost empty, whereas it usually is 3-4M.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
@ colliar
I just checked with your syslog and found that system has resumed from
hibernate just a few minutes before the crash happened.
I did see also random cashes/freezes in Wheezy when system was suspended
before (s2ram). Since I no longer use suspend all the troubles have gone
away.
I must
I can confirm this bug here too and found a temporarly workaround.
Ivy-Bridge i5-3570K on Intel DH77EB MoBo (H77 chipset), latest BIOS
EB0089.BIO.
These freezes happend most of the time when hitting a link in Iceweasel.
They are so severe that even the MoBo reset button does not respond
immediate
>> But since then I have never obseved any cras/freeze for days now.
>
> Keeping my fingers crossed for the same outcome.
>
> /Per
>
Still ok here - good luck.
Me came up another thing which probably relates to that. As far as I
could extract from internet searches regarding this issue, I conc
nd
whether BIOS settings for videoRAM are respected by the i915 module.
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5070021a.4030...@gmx.net
able - which still holds right now.
However the "mtrr" setups (/proc/mtrr) are still identical with both
kernels. Seems the "write-combining area" has become obsolete - or
still not implemented in i915?
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debi
t of up to 1.7 GB Video Memory with 4 GB and above system memory
configuration
So these 1.7GB probably exceeds what the driver (or PAT) is capable?
Regards,
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
configurations.
Probably it ist worth to try this kernel parameter with Wheezy's
standard kernel:
"enable_mtrr_cleanup"
to allow kernel to re-arrange them and see if it has any influence in
your case?
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
ks?
Per's CPU i7-3770 should support VT-d (in case the motherboard offeres
it), while mine i5-3570K does not support VT-d (like all K-CPU's).
Worth to try to switch off VT-d in the BIOS, Per?
Ingo
P.S.: I am still assuming that Per's and mine obeservations have the
same root ca
Am 21.10.2012 14:20, schrieb Per Foreby:
> [22.177] (II) VESA(0): Total Memory: 1023 64KB banks (65472kB)
> [22.200] (II) VESA(0): VESA VBE Total Mem: 65472 kB
>
> Note that this is 1023 memory banks, not 1024, so it's not exactly 64 MB
> (65536 kB). Maybe the reason why it almost works w
12-07-26) - translated into English:
" ... to avoid *priodic freezes* I updated the kernel to 3.4.4-1 from
experimental ..."
Meanwhile the author has updated to kernel 3.5.5-1-amd64 and all appears
still fine.
Just my 2 cents,
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@list
I am back and join the injured.
today I again had the known freeze after 3 weeks of freedom with 256MB
GPU-RAM BIOS setting. So my remedy did not cure the root cause. I now
installed kernel 3.5.5-1 from experimental - let's see.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
s
patch according to 'modinfo i915'
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5095493c.6000...@gmx.net
Am 03.11.2012 22:11, schrieb Jonathan Nieder:
> Jonathan Nieder wrote:
>
>> Hi Ingo,
> [...]
>> There seem to be some differences in symptoms here, so please file a
>> separate bug. We can merge them later if they turn out to have the
>> same cause.
>
&
Am 04.11.2012 08:46, schrieb Jonathan Nieder:
> Ingo wrote:
>
>> -- Package-specific info:
> [...]
>
> Thanks much.
>
>> BOOT_IMAGE=/vmlinuz root=/dev/sda2 ro i915_enable_rc6=0 drm.debug=0x2
>
> There's a spelling mistake here: the kernel paramete
> I am currently running kernel 3.2.32-1 from Sid and intend to run till I
> get freezes.
That happened already 1 hour ago. I was watching a HTML5 video on
YouTube when machine froze totally, even SysRq doesn't work. Sound was
looping the last fraction of a second endlessly. Power consumtion up at
Line Out Surround as
/devices/pci:00/:00:1b.0/sound/card0/input13
input: HDA Intel PCH Line Out Front as
/devices/pci:00/:00:1b.0/sound/card0/input14
I'll report as soon as I get any freeze,
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject
ly by CPU heating up without proper fan
regulation.
Regards,
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/509bbc7c.1010...@gmx.net
Am 08.11.2012 16:55, schrieb Jonathan Nieder:
> Ingo wrote:
>
>> I have now been running kernel 3.3.0-rc6-amd64 for 4 days. I did even
>> try with different BIOS settings for "IGD DVMT Memory" especially with
>> "Maximum DVMT" which according to t
Some additional information, probably it helps:
As stated above, when system freezes power consumption rises by some 30
watts. I now checked under normal operating conditions and it turns out
that this value is precisely the same when 2 cores (out of 4) run under
full load (checked with seti@home)
Since 2 weeks I an running kernel 3.4 from kernel.org. I used config from
Debian's 3.4.4-1~experimental.1 with "make silentoldconfig" and accepted
defaults fo 5 new items. This is a long term kernel as well and thus
still maintained.
I started with 3.4.18, updated to 3.4.19 and now using 3.4.20.
A
t that version too.
Unfortunately I do need my PC for daily work with VirtualBox. However
that site does not supply any matching header packages, so it won't
support VBox.
Regards,
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscrib
I have now been running vanilla 3.4 from kernel.org for 4 weeks.
Starting with 3.4.18 I have continuosly updated as new builds were
released - recently 3.4.21 and now 3.4.23.
All versions ran smoothly without any problems. Also no
incompatibilities with other Wheezy packages have been noticed.
-
Am 15.12.2012 20:33, schrieb Ingo:
> All versions ran smoothly without any problems. Also no
> incompatibilities with other Wheezy packages have been noticed.
>
CORRECTION:
with vanilla kernel 3.4.23, I now had 2 freezes within 6 days!
I now switched back to 3.4.21 (which ran 8 day
kernel - power consumption remained normal
and reset button responded immediately.
I am now with vanilla kernel 3.4.24 from kernel.org and all is fine.
/Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
y describes the symptoms. Could it be that in the
Debian-kernel either the hangs are not detected securely, or that it
just fails to reset the module?
/Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
he crashing
server, but would like to be sure that it's not the kernel which is causing
this, of course. ;)
--
Ciao...// Fon: 0381-2744150
Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
--
To UNSUBSCRIBE
m my blog entry here as well.
Regards,
Ingo
--- System information. ---
Architecture: amd64
Kernel: Linux 4.4.0-1-amd64
Debian Release: stretch/sid
500 unstablewww.deb-multimedia.org
500 unstableftp.de.debian.org
500 unstabledownload.jitsi.org
--- Pack
mer
nor a kernel hacker. I just want this to get fixed… :-)
--
Ciao... //http://blog.windfluechter.net
Ingo \X/ XMPP: i...@jabber.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
signature.asc
Description: Message signed with OpenPGP using GPGMail
...// Fon: 0381-2744150
Ingo \X/ http://blog.windfluechter.net
Please don't share this address with Facebook or Google!
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
May 19 09:07:45 31.172.31.251 [300350.696476] BUG: unable to handle kernel
May 19 09:
ble debug build?
--
Ciao... //http://blog.windfluechter.net
Ingo \X/ XMPP: i...@jabber.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
On 02.08.2016 11:20, Wei Liu wrote:
On Fri, Jul 29, 2016 at 10:17:22PM +0200, Ingo Jürgensmann wrote:
What is also interesting is that you seem to be running some sort of
ip accounting software (pmacctd) which also segfault'ed.
Yeah, it is segfaulting, because the database (in a domU VM)
modversions changes in the past AFAIR - so I assumed it would be handled via
whatever path got the breakage upstream (turns out it was via the VFS tree?),
or via the kbuild tree.
> On Nov 24 finally Ingo responded, the discussion ended with you marking
> modversions as BROKEN.
Yeah, that
72.31.251 [39677.070892] Kernel Offset: disabled
If the log entries of the starting-up server is of interest as well, please
shout! ;-)
--
Ciao... //http://blog.windfluechter.net
Ingo \X/ XMPP: i...@jabber.windfluechter.net
gpg pubkey: http://www.juerge
't
remember all the details over so many moons).
Yes, indeed I have tried different kernels, but I can't remember details
as well... ;/
--
Ciao... // http://blog.windfluechter.net
Ingo \X/ XMPP: i...@jabber.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
Package: initrd-tools
Version: 0.81.1
Followup-For: Bug #318120
tags 318120 patch
Hello
atached youll find a small patch which fixes the mkinitrd-detection
of /dev/i2o/hdx on our testmachines, should work generally.
Regards
Ingo Steuwer
--
* Besuchen Sie uns auf dem LinuxTag06 in Wiesbaden
Hi,
Am Donnerstag, den 14.04.2005, 10:14 +0200 schrieb Ingo Strüwing:
...
> - Has this problem be passed to the Linux kernel developers? What is the
> kernel developers bug list in which to find the problem?
> bugzilla.kernel.org does not seem to know of it.
>
> - Does anyone kn
file system? Or is the file system always dependend
on the locale of the Windows version, which created the file system?
I'm so happy, that Unix is not case insensitive :-)
Regards
Ingo Oeser
pgpbZIcCvFbE9.pgp
Description: PGP signature
s me guess that it could have something to do with
the dual core CPU on the AMD64 X2 machine.
(a very short test on a dual Xeon i386 machine didn't show oopses, but really
not deeply tested.)
Regards,
Ingo
-- System Information:
Debian Release: 4.0
APT prefers testing
APT po
24 kernel:
Jan 21 03:54:39 s15222724 kernel:
Jan 21 03:54:39 s15222724 kernel: Code: 0f 0b 68 90 cd 40 80 c2 53 02 4c 39 62
28 74 0a 0f 0b 68 90
Jan 21 03:54:39 s15222724 kernel: RIP []
kmem_cache_free+0x58/0xca
Jan 21 03:54:39 s15222724 kernel: RSP
This is a single core machine (AMD Ath
Hi Josef,
> I have laptop-mode running, maybe it has something to do with it?
I doubt. The machines in question here at our side are dedicated server and
thus not running in laptop mode. ;)
--
Ciao...//Fon: 0381-2744150
Ingo \X/ SIP: [EM
ve that test for someone else.
You could copy that over to spice or vivaldi. Both are running 2.6.
--
Ciao...//Fon: 0381-2744150
Ingo \X/ SIP: [EMAIL PROTECTED]
gpg pubkey: http://www.juergensmann.de/ij/public_key.asc
--
To UNSUBSCRIBE, email to
ange anything, going to
1000 resulted in even less cache (what one would expect from the
documentation).
So I ask you to handle my bug report like usual. I hope that the problem
will be fixed one day.
With best wishes for the new year and kind regards,
Ingo
--
Ingo Strüwing, Senior Software Developer
MySQL AB, www.mysql.com
Office: +49 30 43672407
Are you MySQL certified? www.mysql.com/certification
y time and
immediately when I start the program GIMP from Debian package 'gimp
2.8.14-1+deb8u2'. The graphical desktop is frozen and the system is
completely unusable. This does not happen with the previous kernel
3.16.0-7-amd64.
Kind regards,
Ingo Jauer
-- Package-specific info:
** Version:
matically, but I can understand when you decide
>to refrain from doing so, of course. But at least you should issue a clear and
>prominent warning to the user during upgrade when there is a filesystem with
>nobarrier option in /etc/fstab.
Ingo
-- Package-specific info:
** Version:
Lin
I have additional information:
- The problem exists in 2.6.10 too. (BTW. should I report it there too?)
- The problem exists on ext3 filesystems too.
- The problem does not exist in 2.4.27.
Regards,
Ingo
--
Ingo Strüwing, Senior Software Developer
MySQL AB, www.mysql.com
Office: +49 30
Package: binutils
Version: 2.15-1
Severity: serious
After updating binutils to 2.15-1, building a new kernel results in an
error:
CC arch/ppc/kernel/ppc_htab.o
AS arch/ppc/kernel/l2cr.o
arch/ppc/kernel/l2cr.S: Assembler messages:
arch/ppc/kernel/l2cr.S:110: Error: Unrecognized opcod
ppc/Makefile
patch: malformed patch at line 5: LDFLAGS_vmlinux := -Ttext
$(KERNELLOAD) -Bstatic
Please supply a working patch file or try it yourself (untar
kernel-source-2.6.7 ; apply kernel-patch-powerpc-2.6.7 ; apply that patch ;
make zImage).
--
Ciao... //
Ingo \X/
ile.rej
Still doesn't work.
--
Ciao... //
Ingo \X/
I just wanted to investigate why the pwcx
module doesn't work anymore... ;))
But, thanks, your patch applies fine and it compiles fine as well:
CC arch/ppc/kernel/ppc_htab.o
AS arch/ppc/kernel/l2cr.o
AS arch/ppc/kernel/cpu_setup_6xx.o
:-)
--
Ciao... //
Ingo \X/
--
Ciao... //
Ingo \X/
elockingfailure
exit 0
;;
I hope this can be fixed in the package,
Thanks and best regards
Ingo Rauschenberg
-- Package-specific info:
-- /proc/cmdline
root=LABEL=ROOT ro vga=791
-- /proc/filesystems
ext3
-- lsmod
Module Size Used by
loop
find the Bug.
best regards
Ingo Rauschenberg
-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/VG_SYSTEM-LVROOT ro vga=791
-- /proc/filesystems
ext3
ext4
-- lsmod
Module Size Used by
vmnet 34699 3
parport_pc 18855 0
pa
roups don't span domain->span
> >
> > Hrm that smells like the architecture topology setup is wrecked, looks
> > like the NUMA setup is bonkers.
> [...]
>
> Right, that's what I thought. Question is whether the topology setup
> code should fix this up or whether the schedular init should (as it
> appears to have done before 2.6.32).
We definitely want to robustify scheduler init code to not crash and to (if
possible) print a warning about the borkage.
Thanks,
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101129180605.gc14...@elte.hu
me for the nvidia-kernel-source
package.
Don't know if the added file has to be removed by hand before upgrading
the linux-kbuild package in order not to entangle your package manager.
Regards
Ingo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subje
minconfig is absolutely useful, I'm glad it's being pursued
upstream as well...
So what you are arguing about is IMO irrelevant, it is
immaterial to the problem at hand and the concept works just
fine in practice.
Thanks,
Ingo
--
To UNSUBSCRIBE, email to debian-k
* da...@lang.hm wrote:
> On Wed, 18 Jul 2012, Ingo Molnar wrote:
>
> >* da...@lang.hm wrote:
> >
> >>>Anybody who says "I want to run Fedora without SELINUX
> >>>because I do my own security development" is by *definition*
> >>&
essage #10)
OTOH I do get the ICE with all Debians gcc-15 versions I tested (15.1.0-1 to
15.1.0-4).
Ingo
--
const_cast(Λ)
+0200, Matthias Klose wrote:
> - please check with the current upstream branch.
>
> - please check with the same configure options and build
> targets as found in Debian.
Thanks for your suggestions.
Ingo
--
const_cast(Λ)
extern const struct seq_operations cpuinfo_op;
struct se
On Wed, Jun 04, 2025 at 10:43:11PM +0200, Uwe Kleine-König wrote:
> Control: tag -1 + fixed-upstream
> Control: forwarded -1
> https://lore.kernel.org/r/20250530221824.work.623-k...@kernel.org
>
> Hello,
>
> On Mon, May 05, 2025 at 05:40:57PM +0200, Ingo Saitz wrote:
&
Am Mittwoch, den 23.02.2005, 12:28 +0900 schrieb Horms:
> On Fri, Feb 18, 2005 at 03:33:30PM +0100, Ingo Strüwing wrote:
> > Am Donnerstag, den 10.02.2005, 18:28 +0900 schrieb Horms:
> > > On Thu, Feb 10, 2005 at 09:07:00AM +0100, Ingo Strüwing wrote:
> > > > Am Don
Am Donnerstag, den 10.02.2005, 18:28 +0900 schrieb Horms:
> On Thu, Feb 10, 2005 at 09:07:00AM +0100, Ingo Strüwing wrote:
> > Am Donnerstag, den 10.02.2005, 10:33 +0900 schrieb Horms:
> > > On Wed, Feb 09, 2005 at 04:50:49PM +0100, Ingo Strüwing wrote:
> > > >
Am Donnerstag, den 10.02.2005, 10:33 +0900 schrieb Horms:
> On Wed, Feb 09, 2005 at 04:50:49PM +0100, Ingo Strüwing wrote:
> > I have additional information:
> >
> > - The problem exists in 2.6.10 too. (BTW. should I report it there too?)
> > - The problem exi
87 matches
Mail list logo
