Package: linux-image-4.18.0-2-amd64
Version: 4.18.10-2
Severity: normal
Occasionally, my system begins freezing (processes doing a lot of
I/O enter D state). It is still somewhat usable for already cached
stuff (starting a new shell tab in GNU screen works, lynx does, …
but e.g. the debsums
Package: src:linux
Version: 4.18.10-2+b1
Severity: minor
I got the warning you see below, and the WLAN reset after a while.
-- Package-specific info:
** Version:
Linux version 4.18.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version
7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.10-2
Package: src:linux
Version: 4.17.17-1
Severity: minor
I exited X.org after a quick session and got the following backtrace,
also spit on the console.
-- Package-specific info:
** Version:
Linux version 4.17.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version
7.3.0 (Debian 7.3.0-28)) #1 SMP
forwarded 907911 https://bugs.freedesktop.org/show_bug.cgi?id=107824
thanks
Ben Hutchings dixit:
>Please can you also report this upstream as requested in the error
According to DevRef §3.1.4 that’s your job as maintainer, but, in
this instance, it was easy enough. I am not qualified enough
Package: src:linux
Version: 4.17.17-1
Severity: normal
When I zoom on the opencaching.de map in Firefox, the GPU crashes pretty
reliably.
I’m attaching the crash dump.
-- Package-specific info:
** Version:
Linux version 4.17.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version
7.3.0
Theodore Y. Ts'o dixit:
>that problems helps most of our users, and we shouldn't let the
>perfect be the enemy of the good.
Agreed. Start small, then enhance one bootloader at a time.
Or boot protocol, I assume.
>Also note that the bootloader has depend on userspace to refresh the
>seed
Adrian Bunk dixit:
>As an example, what happens if I debootstrap and deploy the resulting
>filesytem to a large number of identical embedded systems without
>entropy sources?
Just get into a habit of not doing so, for example by modifying the
image during each writing process.
Having the
Package: src:linux
Version: 4.14.13-1
Severity: minor
Ever since a recent kernel upgrade (I *think* 4.13 to 4.14; if
necessary, I can check), on each boot, my LCD brightness gets
reset to the minimum.
This is annoying; I currently work around it by putting
cat
Package: firmware-linux
Version: 20161130-3
Severity: normal
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.11.0-2-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for
module i915
W: Possible missing firmware
Finn Thain dixit:
>On Mon, 26 Jun 2017, John Paul Adrian Glaubitz wrote:
>> Which can be worked-around by adding
>> "initcall_blacklist=atari_scsi_driver_init" to the kernel command line.
>> The buildd "mama" is running 4.11 with that work around.
Looks like it:
Linux ara5.mirbsd.org
Package: src:linux
Version: 4.9.30-2
Severity: important
I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also failed,
but I had autoremoved that already.)
ARAnyM console log for failed build:
-cutting here may damage your screen surface-
ARAnyM 1.0.2
Using config file:
On Mon, 8 May 2017, Thorsten Glaser wrote:
> unusable; SSH to the system however still works.
Trying to shut it down kills the ssh session, but the system
doesn’t power off either, it just spins the fan a lot.
Holding the power button pressed for several seconds then does
turn it
Package: src:linux
Version: 4.9.25-1
Severity: normal
After dist-upgrading and rebooting into today’s kernel, running X
(using exec startx from the command line), locking the screen and
closing the lid, I get a trace log in the syslog and the TFT gets
unusable; SSH to the system however still
Package: firmware-linux-nonfree
Version: 20161130-2
Severity: normal
Related to #838476:
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module
i915
-- System Information:
Debian
Hello Ben,
>No, there will be no such meta-packages. The -unsigned packages are
>only meant for developer testing and as build dependencies for signed
>binary packages.
then, would you please kindly explain how you plan to address the
issue of not getting the security updates from newer kernel
On Tue, 17 Jan 2017, Julien Aubin wrote:
> ... or even better : the unsigned image is the default image (ends with
> -amd64) and the signed image (ends with -amd64-signed) provides the kernel
> unsigned package
That would be even better, yes.
bye,
//mirabilos
--
tarent solutions GmbH
Package: linux-image-amd64
Version: 4.9+78
Severity: wishlist
On Tue, 17 Jan 2017, Julien Cristau wrote:
> On 01/17/2017 02:16 PM, Julien Aubin wrote:
> > Signed linux kernel images tend to become the default as package
> > linux-latest is updated when linux-signed is updated.
> > So could you
Package: firmware-linux-nonfree
Version: 20160824-1
Severity: normal
Hi,
unsure about package and severity, please change if necessary.
I just upgraded my system (last upgrade was about 24 hours ago),
and now I get the following messages:
Unpacking firmware-linux-nonfree (20160824-1) over
Package: initramfs-tools-core
Version: 0.125
Severity: normal
During a package upgrade:
[…]
Setting up ffmpeg (7:3.0.2-2) ...
Processing triggers for libc-bin (2.22-9) ...
Processing triggers for initramfs-tools (0.125) ...
update-initramfs: Generating /boot/initrd.img-4.5.0-2-amd64
cp: cannot
Ben Hutchings dixit:
>> Instead of starting up, we get a kernel panic. ARAnyM console log:
>[...]
>
>Have you raised this with the upstream maintainers?
No, this is kinda your job (DevRef §3.1.4 first paragraph last sentence)
although I did put debian-68k@ on Cc, which I know upstream reads.
Source: linux
Version: 4.2.5-1
Severity: important
Control: notfound -1 4.1.6-1
Instead of starting up, we get a kernel panic. ARAnyM console log:
=== running aranym on Sat Nov 14 22:21:12 UTC 2015 ===
ARAnyM 0.9.16
tcgetattr error: 25!
Using config file: 'buildd.nym-x11'
>>> Missing
Version: 4.2.3-2
The BTS is down enough for reportbug at the moment, so a manual
follow-up: this also happens with linux-image-4.2.0-1-amd64:amd64
but seems to be SATA related. I seem to have a bad disc or cable
or mainboard port, and 4.1.0-2 and 4.2.0-1 seem to get hung up
over this while
Dixi quod…
> I’m trying now with linux-image-4.1.0-1-amd64:amd64 (= 4.1.3-1)
Linux tglase.lan.tarent.de 4.1.0-1-amd64 #1 SMP Debian 4.1.3-1 (2015-08-03)
x86_64 GNU/Linux
The problem indeed does not appear to happen here (up 6 days).
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4,
More info:
This happened three more times, the last of which I was actually
using the computer (as opposed to screensaver engaged and me afk).
I noticed, after reboot, that there was lots of I/O wait (three
or even all for CPUs) and extreme lag in starting new xterms or
other applications for
Package: linux-image-4.1.0-2-amd64
Version: 4.1.6-1
Severity: normal
Hi,
I’ve been hit twice by a weird sporadic freeze now. They both
were after upgrading to linux-image-4.1.0-2-amd64 from -1-,
but that may or may not have been the actual cause.
I usually start xlock when going away from the
firmware.
Oh well… apparently, the firmware setup screens don’t signal the
watchdog either, so you can’t use that one for five minutes while
the watchdog is enabled. This all points to buggy firmware. Again,
details would have to come from Nik.
bye,
//mirabilos
--
Thorsten Glaser
Teckids e.V. – Erkunden
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
#763614 causes our machines to no longer boot, since they usually
at most use klibc-utils to get small ramdisks. AIUI, the “fix” is
to install busybox or busybox-static. This is not enough, you have
to run “update-initramfs -u” manually afterwards.
John Paul Adrian Glaubitz dixit:
SCNR but to note that mksh has a realpath builtin and compiles
cleanly with klibc.
Yes, but unfortunately, most people agreed on using bash and often you
have no other choice but to use it. I'd also rather use zsh.
initrd uses klibc’s flavour of dash ☹ or some
Ben Hutchings dixit:
This is needed to support mounting non-root filesystems in
initramfs-tools.
As an alternative, you can use mksh (built against klibc)
which has a “realpath” builtin. It just takes one argument,
the path to resolve, and no flags.
bye,
//mirabilos
--
Wish I had pine to hand
Package: src:linux
Version: 3.16.3-2
Severity: minor
I have weird backtraces in dmesg I wanted to report, in case they are relevant.
Full dmesg attached.
-- Package-specific info:
** Version:
Linux version 3.16-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3
(Debian 4.8.3-11) ) #1
Andrew Shadura dixit:
Thorsten Glaser t...@mirbsd.de wrote:
I am not sure whether ifupdown is the correct package for this
bugreport. Please reassign to whatever is, if it isn't.
I'm not sure what causes this, but /dev/net/tun is missing, as the logs
say. Could be a kernel problem, or a bug
Ben Hutchings dixit:
I think this is a mistake and that cfq should be reverted to built-in so
it can be the default, as on other architectures. Any objection to me
doing that?
None from me, I was probably just saving space pre-initrd.
Which one is chosen, I will leave up to the experts, i.e.
On Sat, 13 Oct 2012, Vincent Bernat wrote:
In fact, as of 3.6, it is not possible to use virtconsole as an initial
console. I don't know if this will be fixed later but this makes the bug
It’s fixed. I just installed Ubuntu’s 3.15 on Debian wheezy and
booted with “console=hvc0” and it worked.
Source: linux-latest
Version: 57
Severity: wishlist
Hi,
would be really cool if src:linux-latest actually
build-depended on the architecture-specific binaries
of the sec:linux version its binaries are going to
depend on.
AFAICT, a versioned B-D on linux-libc-dev would do
the trick, in an
On Mon, 14 Apr 2014, Ben Hutchings wrote:
Do you mean that when there is a VM that won't shutdown cleanly,
rebooting the host consistently works but power-off consistently fails?
After quite some more test runs (although I admit not trying
without the nvidia nonfree module), I can confirm that
On Mon, 14 Apr 2014, Ben Hutchings wrote:
Do you mean that when there is a VM that won't shutdown cleanly,
rebooting the host consistently works but power-off consistently fails?
Sorry, no. I meant: without a VM that will not respond to ACPI
shutdown events, “sudo poweroff” works. I’ll test a
On Fri, 11 Apr 2014, Ben Hutchings wrote:
I typed “sudo poweroff” as usual on Debian… the system switched to
the text console and mostly hung.
Is this reproducible when not using the nvidia module?
Hrm. I’d have to try, but first a quick shot…
[.xxx] handle_exit: unexpected
On Mon, 14 Apr 2014, Thorsten Glaser wrote:
… I still had a VM running in kvm/libvirt, which would not
respond to normal ACPI shutdown commands. Maybe this is the
cause of this issue?
FWIW, I was able to reboot without a VM “hanging”, just fine.
bye,
//mirabilos
--
tarent solutions GmbH
Package: src:linux
Version: 3.13.7-1
Severity: normal
Hi *,
I had to reboot to cleanse my system of running KDE, dbus, etc. again
(since KDEPIM didn’t want to “see” new incoming eMails… this used to
work better in KDE 3… but offtopic for here), and since reboots heal
problems anyway, and since
Ondrej Riha dixit:
linux-headers-2.6-* and linux-image-2.6-* and linux-doc-2.6-*
These packages no longer exist, they have been removed from unstable.
Debian-Ports mini-dak does not generally follow this sort¹ of removals
automatically, so they will eventually be cleaned up manually.
The
Source: linux
Severity: wishlist
Tags: patch
Dear Maintainers,
please add the following patch to your next upload of src:linux,
as per discussion with upstream in… I’d include a link, but
article.gmane.org is currently down.
This option used to be always enabled, then the default changed
Dixi quod…
Ben Hutchings dixit:
One’s to add back CONFIG_BRK which is apparently needed to run a
popular ramdisk image used e.g. when testing the hardware or setting
up a completely new system.
You mean CONFIG_COMPAT_BRK. I don't like this but I doubt anyone cares
to write exploits for m68k
Ben Hutchings dixit:
One’s to add back CONFIG_BRK which is apparently needed to run a
popular ramdisk image used e.g. when testing the hardware or setting
up a completely new system.
You mean CONFIG_COMPAT_BRK. I don't like this but I doubt anyone cares
to write exploits for m68k any more.
) UNRELEASED; urgency=low
+
+ [ Thorsten Glaser ]
+ * Update m68k config:
+- enable BRK by explicit upstream (m68k maintainer) request
+- re-enable FPU emulation after discussion upstream, by popular request
+- disable ADB_MACIISI by upstream (Mac68k maintainer) request
+
+ -- Thorsten Glaser
.patch: patch from Andreas
+Schwab to handle do_div being called with a nōn-u32 second argument
+ * m68k: begin working on d-i kernel configs (just enough to not FTBFS)
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 09 Aug 2013 20:36:12 +
+
linux (3.10.5-1) unstable; urgency=low
* New
Geert Uytterhoeven dixit:
404
Sorry, bit slow ;-)
http://www.freewrt.org/~tg/dp/dists/hacks/clean/Notyet/linux-image-3.10-1-m68k_3.10.3-1_m68k.deb
bye,
//mirabilos
--
17:08⎜«Vutral» früher gabs keine packenden smartphones und so
17:08⎜«Vutral» heute gibts frauen die sind facebooksüchtig
Source: linux
Version: 3.10.3-1
Severity: important
Justification: fails to build from source (but built successfully in the past)
Hi,
the latest Linux kernel source package fails to build:
[…]
make[2]: Entering directory `/tmp/buildd/linux-3.10.3'
dh_testdir
dh_prep
kernel-wedge install-files
Sorry, of course I forgot the attachment…
bye,
//mirabilos
--
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and
Ben Hutchings dixit:
Well you gave us the new m68k configuration. I kind of hoped you'd at
least done a full build test.
I wasn’t quick enough, it all takes a lot of time. I literally
could not have finished before you uploaded.
The installer udeb configuration under debian/installer/m68k
Ben Hutchings dixit:
I've split it this time, but please separate your changes into a proper
patch series in future.
Okay, will do, if I’m aware what should be split of course.
Also it's not clear where the patch ethernat-kconfig.patch comes from.
I wondered why I couldn’t select it, looked at
Ben Hutchings dixit:
Also it's not clear where the patch ethernat-kconfig.patch comes from.
Here you are.
Geert, I’ve noticed that this particular bit seems to not have
made it into torvalds/linux.git yet, even though the remainder
of it has; can you please have a look at it and submit?
Michael Schmitz dixit:
There's no harm in including the Kconfig patch to enable building the smc91x
module, but there'd no gain in that either - you still need the patch to
smc91x.h to make it work.
Oh okay. From the presence of the new driver options in
the architecture config I thought it
Ben Hutchings dixit:
then I think it should be enabled for all architectures - as a separate
change from the m68k config update.
Sure, no complaints from me there. Is the patch I sent
enough (splitting it is easy)?
bye,
//mirabilos
--
“Having a smoking section in a restaurant is like having
On Wed, 24 Jul 2013, Ben Hutchings wrote:
[ ext2/3/4 ]
I think we may want to enable this at the top level later, but there is
no reason to override it now.
OK, will remove that.
+CONFIG_NFS_SWAP=y
Really?
Not? Is there something better?
Hm, Wouter would probably say swap over nbd :D
Dixi quod…
Another thing that puzzles me:
config SMC91X
depends on (ARM || M32R || SUPERH || MIPS || BLACKFIN || \
MN10300 || COLDFIRE || ARM64)
Maybe just an explicit || ATARI_ETHERNAT here?
Add || ATARI_ETHERNEC to NE2000 as well I’d say, so everyone
Ah this is
Ben Hutchings dixit:
Yes, but why should this be m68k-specific?
OK. I’ll resend a patch that makes CONFIG_NFS_SWAP global
and addresses the other things raised.
Will you also want the Macintosh codepages for HFS+ be
made global? (I assume so, since HFS+ is globally enabled.)
bye,
//mirabilos
Dixi quod…
Even if this may have some minor issues still, it’ll be better
than building kernel images that fail to boot at all, that’s why
Ah well. Of course it didn’t boot.
/lib/modules/3.10-0+m68k.2-m68k/kernel/arch/m68k/emu/nfblock.ko
is the “IDE” driver for ARAnyM machines (like
Bastian Blank dixit:
On Tue, Jul 23, 2013 at 09:26:28PM +, Thorsten Glaser wrote:
Which package is responsible for the inclusion of arch-specific
kernel modules into the initrd (for MODULES=most right now; I
have yet to try MODULES=dep)?
initramfs-tools
OK, thanks!
Doesn’t help though
Bastian Blank dixit:
On Tue, Jul 23, 2013 at 08:42:04PM +, Thorsten Glaser wrote:
+CONFIG_IOSCHED_DEADLINE=m
+CONFIG_IOSCHED_CFQ=m
Should be configured in the top config.
They’re =y there. I put them into modules to save space.
+# CONFIG_EXT2_FS_SECURITY is not set
Dixi quod…
This is merely what we had before. (I’m giving nfeth a chance here…)
“No such device” is what nfeth.ko says upon insmod.
I’ll report this as bug upstream and revert it to =y too:
--- debian/config/m68k/config 2013-07-23 22:38:05.519153764 +
+++ - 2013-07-23 22:38:28.394235256
Dixi quod…
I guess if it’s like that, I can have a go as well.
Did one now, and it boots. It uses initrd now, which
means one has to copy-out the initrd every time it is
regenerated, but also adds flexibility (root filesystem
not ext4fs, root on nfs, nbd, etc).
I disabled quite a lot of stuff
Ben Hutchings dixit:
For myself, I don't much care if non-release architectures have weird
configurations.
Right, but it’s still better if every Debian architecture
“feels” similar enough. I’m very much *not* knowledgeable
about Linux kernels other than 2.0.3x ;-) so I’d appreciate
feedback
Ben Hutchings dixit:
So you should minimise the per-architecture and per-flavour
configuration.
Yes, but how?
(I got rid of the flavours, btw.)
Did nobody script that yet? I can’t believe that.
Script what?
That “minimise” thing.
bye,
//mirabilos
--
Using Lynx is like wearing a really
New “other bugtracker” link:
https://bugzilla.redhat.com/show_bug.cgi?id=967652
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris
Package: src:linux
Version: 3.9.8-1
Severity: important
Also listed at https://bugzilla.redhat.com/show_bug.cgi?id=965711
I wanted to keep track of this problem in Debian:
There is a difference between
qemu-system-x86_64 -cdrom CentOS-5.9-x86_64-netinstall.iso
and
qemu-system-x86_64 -cdrom
FWIW,
Linux tglase.lan.tarent.de 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 i686 GNU/Linux
08:51:32 up 3 days, 22:24, 2 users, load average: 0.11, 0.27, 0.29
This one is stable.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393
Geert Uytterhoeven dixit:
I guess it can be extended, if really needed. Does it work if you
change the #4
above to #8?
I’ll have to try.
Note that 4 MiB kernels won't work on platforms where the first memory block
is smaller than the kernel size.
On those 4+n MiB Ataris the stock 3.x MiB
Christian T. Steigies dixit:
You saw Ingo's calculation yesterday, 2008? I tried to build an optimized
[…]
send me the config, I can have a look. But many of the options don't say
much to me anymore...
Hrm.
I guess if it’s like that, I can have a go as well.
It’s probably a bit tricky getting
Hi all,
ARAnyM cannot boot the latest kernel images (still compiling,
but I copied out vmlinux.gz):
tglase@tglase:~/stuff/aranym/vm2 $ ./run
Running Ara2 on X11: :2
ARAnyM 0.9.15
Using config file: 'aranym.config.x11'
Could not open joystick 0
ARAnyM RTC Timer: /dev/rtc: Permission denied
ARAnyM
Geert Uytterhoeven dixit:
Kernel images fail to boot on Atari if they're bigger than 4 MiB.
OK, thanks. What about the others (amiga, bvme*, mac, two mvme*)?
Who’s in charge of the Debian kernel configs (IIRC Stephen Marenka
and Wouter Verhelst)? Or otherwise, could the Debian Linux kernel
team
Ben Hutchings dixit:
As m68k is not a release architecture, I don't care much what goes
in debian/config/m68k (well, it had better not break gencontrol.py).
Whatever the m68k porters come up with is fine.
OK, thanks. I’d kinda like to have it somewhat in sync with
the rest of Debian of course,
Ben Hutchings dixit:
Eventually (wheezy+2? +3?) we would stop building a kernel package for
i386.
As in drop the i386 arch?
No, keep i386 userland only.
Oh, definitely not! Please keep this runnable on at least
machines such as Soekris (486-compatible), Pentium-M, etc.
have ppc64 and
Bastian Blank dixit:
m68k is also affected. No initramfs, but ext2/ext3 built-in. I'll change
that also.
Uhm, I politely disagree. Why? Why add ext4fs but not, say,
reiserfs? (I recently found myself in the situation of having
created an unbootable system, but that was easy to fix.)
On the
Jonathan Nieder dixit:
Thorsten Glaser wrote:
Why? Why add ext4fs but not, say,
reiserfs?
The rationale is that ext4 is what d-i defaults to in wheezy. Getting
Ah okay, that explains things. This sucks. OK, then that change
is probably the best in the very short
to be registered
[…]
Now that these are in the Debian Linux kernel package and a build has
been done, I can confirm the result boots on ARAnyM (m68k).
Tested-by: Thorsten Glaser t...@debian.org
bye,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens
sf...@users.sourceforge.net dixit:
This is the last version of my approach (documentations are omitted).
This doesn’t really differ from what I sent last,
does it?
Would you try on your m68k when you have time?
You _are_ aware that a kernel compile takes over a day, right?
Why don’t you use
sf...@users.sourceforge.net dixit:
You include aufs_name.h twice now, once in the Makefile,
once in the header. Shouldn=E2=80=99t one be enough?
No, because aufs_type.h is exported to userspace.
Then, why include it in the Makefile at all?
(Or, why include aufs_name.h from aufs_type.h?)
bye,
sf...@users.sourceforge.net dixit:
- AUFS_NAME is necessary for both of kernel-space and user-space.
- from userspace, users include aufs_type.h. to keep the consistency,
aufs_type.h should include aufs_name.h.
- for kernelspace, to put aufs_name.h _before_ all other headers.
Hrm, okay. I’ll
sf...@users.sourceforge.net dixit:
Hold it please.
OK.
I am going to make more changes. So it is better to git-pull and test
the aufs GIT repository.
Please send patches that _should_ apply against what’s in Debian.
I don’t have time to play the merge game at the moment.
I have the same
Hi,
I have good and bad news: I got 3.2~rc7 compiled with some
patches, but it’s panicking.
I’ve attached a .tgz with the following content:
a) patches against (a git copy of) the linux-2.6 trunk SVN:
• patches/0001-distinguish-level-of-xz-compression-to-use-for-packa.patch
This is for waldi:
Dixi quod…
So, please, compile the Linux kernel with -ffreestanding, too.
Just to keep this bugreport in the loop: that fixes the FTBFS error.
http://lists.debian.org/debian-68k/2012/01/msg0.html
bye,
//mirabilos
--
dileks ch: good, you corrected yourself. ppl tend to tweet such news
Ben Hutchings dixit:
It is quite possible that m68k kernel udebs have not been built for some
years, though the configuration has been updated along with other
architectures.
I don’t think that is it, as the last upload had this in .changes:
[…]
4b1a4046ca58561cc6c94d020a9f10f4 1997696
Geert Uytterhoeven dixit:
Sorry, static inline functions are preferred over macros, unless there's
Can I have reasons? (Also out of curiosity.)
a really good reason. Out-of-tree kernel code doing stupid things doesn't
I see it like this:
EVERY file that, directly or indirectly, includes
sf...@users.sourceforge.net dixit:
test this patch since I don't have m68k environment.
I can do that, but not too many patches at a time, since it takes
easily a whole day to compile it. (Also, my own hacking time is
limited atm.)
It introduces a new separated file include/linux/aufs_name.h.
Ben Hutchings dixit:
-ccflags-y +=
-D'pr_fmt(fmt)=AUFS_NAME\040%s:%d:%s[%d]:\040fmt,__func__,__LINE__,current-comm,current-pid'
+ccflags-y +=
-D'pr_fmt(fmt)=aufs\040%s:%d:%s[%d]:\040fmt,__func__,__LINE__,current-comm,current-pid'
Sadly, this doesn’t work either:
CC [M] fs/aufs/module.o
In
7431e1ffad6aafa36fa8dd0459c066fada25e1d6 Mon Sep 17 00:00:00 2001
From: Thorsten Glaser t...@mirbsd.org
Date: Sat, 31 Dec 2011 22:27:15 +
Subject: [PATCH] =?UTF-8?q?move=20AUFS=5FNAME=20and=20aufs=E2=80=99=20pr=5Ff?=
=?UTF-8?q?mt=20into=20their=20own=20header?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
*fsFrom fda2529371f8cc8879877ca3f3eb9dfbaafb9755 Mon Sep 17 00:00:00 2001
From: Thorsten Glaser t...@mirbsd.org
Date: Sat, 31 Dec 2011 22:48:52 +
Subject: [PATCH] replace inline ack_bad_irq with a block macro to avoid error
propagation
If any file including (directly or indirectly) hardirq.h
bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mkshFrom debdad28232a9c84f135fa1b7aa9d137b72ab4d8 Mon Sep 17 00:00:00 2001
From: Thorsten Glaser
Dixi quod…
I suspect gcc emitting a call to strFOO for __builtin_strFOO.
And indeed, it does; waldi just pointed me to the fact that the
Linux kernel, despite being a kernel and not a hosted environment,
does not use -ffreestanding in its CFLAGS. No surprise it does
that, then.
When I first
Ben Hutchings dixit:
why other architectures get away with it. Maybe they just don't use
pr_*() in headers.
Maybe something like this?
#define ack_bad_irq(irq) do { \
pr_crit(unexpected IRQ trap at vector %02x\n, \
(unsigned
Dixi quod…
Maybe something like this?
With that, aufs indeed compiles and module-links.
bye,
//mirabilos
--
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
-- Edward Burr
--
To
Uwe Kleine-K�nig dixit:
On Sat, Dec 17, 2011 at 02:28:35PM +, Thorsten Glaser wrote:
Maybe something like this?
[…]
Just an idea of the moment,
Well, it does make the thing compile with minimal effort.
IMHO the problem is that aufs provides an incomplete definition of
pr_fmt. Either
Uwe Kleine-König dixit:
so better use plain printk with KERN_CRIT directly.
Wasn’t it considered good style to switch f̲r̲o̲m̲ that t̲o̲ pr_crit?
In that case, my other patch from Message-ID
pine.bsm.4.64l.1112171426140@herc.mirbsd.org can still
be used. Feel free to assume a Signed-off on
Hi,
a build of linux-2.6 (3.2~rc4-1~experimental.1) with gcc-4.6 (to
check whether we can switch to it for the kernel, too) fails:
[…]
LD [M] fs/affs/affs.o
LD fs/aufs/built-in.o
CC [M] fs/aufs/module.o
In file included from
Ben Hutchings dixit:
Maybe, but it should work just as long as AUFS_NAME is also defined in
Right, looks like it.
advance. Not sure why that's not also provided on the command line, or
Hrm. Can you forward this to the aufs people then, and maybe get
us some fix?
why other architectures get
Still fails:
[…]
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
cp vmlinux vmlinux.tmp
strip vmlinux.tmp
gzip -9c vmlinux.tmp vmlinux.gz
rm vmlinux.tmp
Building modules, stage 2.
MODPOST 749 modules
ERROR: strlen [drivers/target/iscsi/iscsi_target_mod.ko] undefined!
ERROR:
Andreas Schwab dixit:
Thorsten Glaser t...@mirbsd.de writes:
ERROR: strlen [drivers/target/iscsi/iscsi_target_mod.ko] undefined!
ERROR: strcpy [drivers/target/iscsi/iscsi_target_mod.ko] undefined!
Missing linux/string.h.
No, these are generated by gcc. (See the debbugs context.)
bye
Jonathan Nieder dixit:
Linux 3.1 doesn’t build any more, Linux 3.0 built successfully
in all its versions. Full build log attached. “amiga” is the
first of the available (and needed/used) flavours, this might
thus affect more or all of them.
[...]
MODPOST 748 modules
ERROR: strlen
Jonathan Nieder dixit:
[1] http://thread.gmane.org/gmane.linux.kernel/680193/focus=680351
I think users of both strcpy and strncat should be shot, unquestioned…
(but then, GNU is still the only major vendor without strlc{py,at}…)
bye,
//mirabilos
--
dileks ch: good, you corrected yourself. ppl
Ben Hutchings dixit:
But there are no warnings in the log for use of these functions
without declarations. So if linux/string.h is not included
already (indirectly), where are they declared? I don't believe
I fear they might be correct and gcc replaces certain function
calls with others, or –
101 - 200 of 226 matches
Mail list logo
