Bug#522773: linux-libc-dev: uses __unused as identifier, which is traditionally used by BSD as macro

2009-04-06 Thread Thorsten Glaser
Package: linux-libc-dev Version: 2.6.29-2 Severity: wishlist (mass filing with linux-libc-dev and libc6-dev) /usr/include/asm/stat.h:long__unused[3]; /usr/include/linux/icmp.h: __be16 __unused; /usr/include/linux/sysctl.h:unsigned long __unused[4]; These

Bug#522773: [issues] glibc uses '__unused' as identifier, which is traditionally used by BSD as macro

2009-09-09 Thread Thorsten Glaser
Moritz Muehlenhoff dixit: You need to get this changed upstream, we won't deviate from upstream for this. You probably have better contact to upstream, would you be so kind as to bring this forward with them? Thanks in advance. Sincerely, //mirabilos -- I believe no one can invent an

Re: [DRAFT v2] Policy for Linux kernel, initramfs, boot loader update process

2010-07-08 Thread Thorsten Glaser
Guillem Jover dixit: A bit of background info. For GNU/kFreeBSD the kernel images are named 'kfreebsd-image-*', for GNU/Hurd they are named 'gnumach'. (I should probably rename gnumach to match the current kernel naming convention.) I wonder if there will ever be packages like

Re: Debian/m68k kernel (preview)

2011-04-24 Thread Thorsten Glaser
Ben Hutchings dixit: You don't need to unset ECONET or X25 in debian/config/m68k/config; they OK. As I said, for the configs I just merged what was there in Debian’s 2.6.32 tree already, added one RTC option and made the others from m into y on atari. Feel free to twiddle them around in any way

Re: Debian/m68k kernel (preview)

2011-04-24 Thread Thorsten Glaser
that’s relevant to someone, based on my previous expe- rience with these two patches. I will, of course, mail back when I actually submit these to the Debian Kernel Team. +++ linux-2.6-2.6.38/debian/changelog + [ Thorsten Glaser ] + * [m68k] Disable staging drivers (taken from Debian 2.6.32

Re: Debian/m68k kernel

2011-04-24 Thread Thorsten Glaser
Dixi quod… Changes from the previous one: […] Dear Debian Linux Kernel team, please consider that patch (it was made against 2.6.38-4) for inclusion in your next upload. It’s lots better than everything we had before (i.e. Ethernet and the framebuf- fer console work and SLUB doesn’t panic).

Re: Debian/m68k kernel

2011-04-24 Thread Thorsten Glaser
Ben Hutchings dixit: Applied, with the exception of the debian/config/m68k/config change. A line of the form '# CONFIG_FOO is unset' really is the correct way to unset CONFIG_FOO; it is not just a comment. OK. Thanks a lot in any case. I’ll wait for your next upload (and my build of gcc-4.4 to

Re: [patch] m68k, mm: set all online nodes in N_NORMAL_MEMORY

2011-04-27 Thread Thorsten Glaser
by David Rientjes +rient...@google.com attempting to set node state immediately when +bringing the node online. Signed-off-by: Michael Schmitz schm...@debian.org -Tested-by: Thorsten Glaser t...@debian.org +Signed-off-by: Geert Uytterhoeven ge...@linux-m68k.org +CC: sta...@kernel.org --- arch

Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED

2011-05-12 Thread Thorsten Glaser
Ben Hutchings dixit: Anyway, I don't think the TPM drivers could be used on most non-x86 architectures. We should just disable them. Yes, these are good candidates for being left out. WLAN devices probably as well, but I’ll leave that to the platform experts to decide. (Most TPMs are included

Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED

2011-05-12 Thread Thorsten Glaser
Geert Uytterhoeven dixit: I suspect this list is also applicable to atari and amiga (?) Yeah, I should look into updating the defconfigs again. Mh. Debian provides their own configs as well though, I think Wouter/Stephen/cts should have a look at them. (You should have seen the comments by

Bug#522773: Fwd: [issues] glibc uses '__unused' as identifier, which is traditionally used by BSD as macro

2009-07-29 Thread Thorsten Glaser
Hi package maintainers, maybe you can do such a thing during package installation? This would tremendously help porting software (liberal in what one accepts), such as NetBSD® makefs (ITP: #538171 – for now I worked around the issue in it). -- Forwarded message -- From: Thorsten

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-02 Thread Thorsten Glaser
Source: linux-2.6 Version: 2.6.32-24 Severity: wishlist Tags: sid Please see to that -fno-omit-frame-pointer is used during compilation of a Debian m68k kernel as long as it is built with gcc-4.3 (I think defining CONFIG_FRAME_POINTER should be enough, I have yet to build any kernel at all though

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-03 Thread Thorsten Glaser
Dixi quod… Please see to that -fno-omit-frame-pointer is used during compilation of a Debian m68k kernel as long as it is built with gcc-4.3 (I think defining CONFIG_FRAME_POINTER should be enough, I have yet to build any kernel at all though and have not tested this). ARCH_WANT_FRAME_POINTERS

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-03 Thread Thorsten Glaser
+CONFIG_ARCH_WANT_FRAME_POINTERS=y +CONFIG_FRAME_POINTER=y Corresponding changelog entry: [ Thorsten Glaser ] * debian/config/m68k/config: define CONFIG_ARCH_WANT_FRAME_POINTERS and CONFIG_FRAME_POINTER to yes (Closes: #598893) Note that this *only* applies to the sid kernel

Bug#599121: linux-2.6: [m68k] nfeth driver vanished? no network connectivity!

2010-10-04 Thread Thorsten Glaser
Source: linux-2.6 Version: 2.6.32-24 Severity: important Tags: experimental sid After compiling an m68k kernel for ARAnyM using the atari platform, requiring the fix from Debian #598893 as well as a patch I've sub- mitted upstream¹ in order to allow inclusion into the Debian kernel, and getting

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-06 Thread Thorsten Glaser
Bastian Blank dixit: m68k is not a release architecture. Also all newer kernels uses gcc 4.4. It doesn’t happen in gcc-4.4 but the kernel currently in sid uses gcc-4.3. bye, //mirabilos -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-06 Thread Thorsten Glaser
Ben Hutchings dixit: On Wed, Oct 06, 2010 at 04:25:43PM +, Thorsten Glaser wrote: Bastian Blank dixit: m68k is not a release architecture. Also all newer kernels uses gcc 4.4. It doesnb But we aren't going to release with m68k, so why not concentrate on trunk/experimental? Makes

Bug#598893: eglibc sysroot

2010-10-13 Thread Thorsten Glaser
Finn Thain dixit: I guess you patched your compilers as discussed on linux-m68k? Interestingly enough, I was not hit by GCC PR/41302 because I built with CONFIG_ARCH_WANT_FRAME_POINTERS=y and CONFIG_FRAME_POINTER=y to work around GCC PR/37052 already which defines not only

Bug#522773: possible solutions for __unused problem

2011-06-19 Thread Thorsten Glaser
Robert Millan dixit: I can see they wouldn't be excited about it, but they might also accept You know that there are more than one BSD, but only one glibc, IIRC Drepper isn’t even its maintainer any more. Try persuading for example Theo de Raadt of anything which doesn’t have any immediate

Bug#522773: possible solutions for __unused problem

2011-06-19 Thread Thorsten Glaser
Ben Hutchings dixit: Honestly, when resolving this I’d go for “who has the older rights”. Maybe look at how CSUR resolves different claims to the same part of the Unicode PUA, or something like that. Nevertheless, thanks on picking this up. Debian GNU/Linux is the older system; the Debian

[m68k] Patches for 3.0 (was Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable)

2011-06-29 Thread Thorsten Glaser
: On Wed, Jun 29, 2011 at 19:38, Thorsten Glaser t...@mirbsd.de wrote: Geert Uytterhoeven dixit: I folded it into your previous patch and pushed it out for 3.1. Can you make a patch (series) on top of 3.0 and mail that to debian-kernel asking for inclusion in the next 3.0 upload, on the ground

Re: [m68k] Patches for 3.0

2011-06-29 Thread Thorsten Glaser
maximilian attems dixit: aboves confuses me, I don't see any m68k patches in the trunk branch heading for the next 3.0-rcX upload? Yes, they were in 2.6.38 but someone removed them before 2.6.39 in Debian. All but this one patch, replaced by (see below), were included in 2.6.39 upstream though,

Bug#632824: linux-image-2.6.39-2-686-pae: linux = 2.6.39 and spacefun splash screen don't mix: system fails to come up

2011-07-06 Thread Thorsten Glaser
Package: linux-2.6 Version: 2.6.39-2 Severity: important This is the laptop of a coworker which runs Debian testing, but I have observed this problem on a Linux kvm VM running Debian unstable as well previously. To enable the spacefun splash screen, I had to do the following, according to

Bug#632824: linux-image-2.6.39-2-686-pae: linux = 2.6.39 and spacefun splash screen don't mix: system fails to come up

2011-07-06 Thread Thorsten Glaser
Yves-Alexis Perez dixit: I don't know what graphic card you use but if supported you really Depends… one is kvm, so some kind of cirruz logic or generic vga, then we have laptops with intel, ati and nievida, so we need a generic solution. should use kernel mode setting. How does one use that?

Bug#632824: linux-image-2.6.39-2-686-pae: linux = 2.6.39 and spacefun splash screen don't mix: system fails to come up

2011-07-06 Thread Thorsten Glaser
Julien Cristau dixit: The generic solution is disable the splash screen pretty much. Which directly contradicts the goal of this exercise. bye, //mirabilos, who doesn’t *WANT* to go back to Kubuntu usplash -- ch you introduced a merge commit│mika % g rebase -i HEAD^^ mika sorry, no

Bug#632824: linux-image-2.6.39-2-686-pae: linux = 2.6.39 and spacefun splash screen don't mix: system fails to come up

2011-07-06 Thread Thorsten Glaser
Jonathan Nieder dixit: FYI: http://lists.freedesktop.org/archives/dri-devel/2011-April/010396.html Interesting, but of course limits us to versions supporting that. I’d prefer some generic VESA VBE method. This used to work (using vga= options), so this is a regression. bye, //mirabilos --

Bug#632824: linux-image-2.6.39-2-686-pae: linux = 2.6.39 and spacefun splash screen don't mix: system fails to come up

2011-07-06 Thread Thorsten Glaser
Jonathan Nieder dixit: Can you reproduce this with an upstream kernel? Can you bisect? Nope, won’t get paid for _that_ much effort. Sorry. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 52675-93 • Fax: +49 228 52675-25 HRB AG Bonn

[m68k] partial success but does not boot: 3.2~rc7

2012-01-01 Thread Thorsten Glaser
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:

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2012-01-01 Thread Thorsten Glaser
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

Re: [m68k] partial success but does not boot: 3.2~rc7

2012-01-01 Thread Thorsten Glaser
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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2012-01-02 Thread Thorsten Glaser
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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2012-01-02 Thread Thorsten Glaser
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,

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2012-01-02 Thread Thorsten Glaser
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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2012-01-02 Thread Thorsten Glaser
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

Re: [PATCHv2 1/2] cpu: Do not return errors from cpu_dev_init() which will be ignored; [PATCHv2 2/2] cpu: Register a generic CPU device on architectures that currently do not

2012-01-27 Thread Thorsten Glaser
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

Bug#660446: linux-image-3.2.0-1-4kc-malta: Should include built-in support for ext4

2012-02-22 Thread Thorsten Glaser
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

Bug#660446: linux-image-3.2.0-1-4kc-malta: Should include built-in support for ext4

2012-02-22 Thread Thorsten Glaser
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

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2011-11-16 Thread Thorsten Glaser
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

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2011-11-16 Thread Thorsten Glaser
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

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2011-11-16 Thread Thorsten Glaser
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 –

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2011-11-30 Thread Thorsten Glaser
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:

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2011-11-30 Thread Thorsten Glaser
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

aufs vs. m68k conflict, please advice

2011-12-16 Thread Thorsten Glaser
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

Re: aufs vs. m68k conflict, please advice

2011-12-16 Thread Thorsten Glaser
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

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Thorsten Glaser
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

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Thorsten Glaser
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

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Thorsten Glaser
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

Re: [PATCH] m68k/irq: don't use pr_crit in an header

2011-12-17 Thread Thorsten Glaser
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

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)

2011-12-18 Thread 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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2011-12-31 Thread Thorsten Glaser
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.

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2011-12-31 Thread Thorsten Glaser
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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2011-12-31 Thread Thorsten Glaser
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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2011-12-31 Thread Thorsten Glaser
*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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2011-12-31 Thread Thorsten Glaser
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

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2012-01-01 Thread Thorsten Glaser
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

Re: amd64 as default architecture

2012-05-22 Thread Thorsten Glaser
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

Bug#728392: linux: Please update m68k config

2013-10-31 Thread Thorsten Glaser
) 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

Bug#728392: linux: Please update m68k config

2013-11-10 Thread Thorsten Glaser
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.

Bug#728392: linux: Please update m68k config

2013-11-14 Thread Thorsten Glaser
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

Bug#734289: linux: please add CONFIG_EARLY_PRINTK=y on m68k

2014-01-05 Thread Thorsten Glaser
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

linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Thorsten Glaser
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

Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Thorsten Glaser
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

Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Thorsten Glaser
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,

Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-14 Thread Thorsten Glaser
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

Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-14 Thread Thorsten Glaser
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

Bug#715364: linux: severe virtualisation regression: cannot boot CentOS 5 guests

2013-07-08 Thread Thorsten Glaser
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

Bug#715364: Fwd: [Bug 965711] Can not boot CentOS 5 guests on Fedora 18

2013-07-16 Thread Thorsten Glaser
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

linux 3.10.1 with initrd (was Re: linux 3.8.12-1 (atari flavour) does not boot)

2013-07-20 Thread Thorsten Glaser
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

Re: [m68k] linux 3.10.1 with initrd

2013-07-20 Thread Thorsten Glaser
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

Re: [m68k] linux 3.10.1 with initrd

2013-07-20 Thread Thorsten Glaser
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

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
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

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
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

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
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

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
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

Re: Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Thorsten Glaser
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

Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Thorsten Glaser
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

Re: Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Thorsten Glaser
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

Re: Bug#717689: linux: please review and merge m68k patch

2013-07-26 Thread Thorsten Glaser
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

Re: Bug#717689: linux: please review and merge m68k patch

2013-07-27 Thread Thorsten Glaser
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

Re: Bug#717689: linux: please review and merge m68k patch

2013-07-27 Thread Thorsten Glaser
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?

Re: Bug#717689: linux: please review and merge m68k patch

2013-07-27 Thread Thorsten Glaser
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

Bug#718271: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.

2013-07-29 Thread Thorsten Glaser
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

Bug#718271: linux: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.

2013-07-29 Thread Thorsten Glaser
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

Bug#718271: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, KVERS line 2.

2013-07-29 Thread Thorsten Glaser
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

Re: linux 3.10.1 with initrd

2013-07-30 Thread Thorsten Glaser
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

Bug#719531: linux: please apply another m68k patch

2013-08-12 Thread 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

Bug#711304: nouveau: X terminates or freezes randomly, cannot be started again

2013-06-10 Thread Thorsten Glaser
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

Re: Problem with packages version(on m68k architecture, but also on amd64 and maybe somewhere else)

2014-04-01 Thread Thorsten Glaser
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

Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...

2014-04-11 Thread Thorsten Glaser
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

Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...

2014-04-14 Thread Thorsten Glaser
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

Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...

2014-04-14 Thread Thorsten Glaser
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

Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...

2014-04-15 Thread Thorsten Glaser
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

Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...

2014-04-30 Thread Thorsten Glaser
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

Bug#746618: linux-latest: actually build-depend on the linux version depended on

2014-05-01 Thread Thorsten Glaser
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

Bug#689962: linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y

2014-06-11 Thread Thorsten Glaser
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.

Re: I/O schedulers for m68k

2014-07-11 Thread Thorsten Glaser
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.

Re: Bug#755471: ifupdown: fails to bring up network: cannot access '/dev/net/tun': ENOENT

2014-07-21 Thread Thorsten Glaser
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

Bug#762836: linux-image-3.16-2-amd64: reg_process_hint call trace in dmesg

2014-09-25 Thread Thorsten Glaser
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

Re: [klibc] [PATCH 2/2] readlink: Add -f option

2014-09-28 Thread Thorsten Glaser
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

Bug#763614: m68k machines not coming up after last update

2014-10-02 Thread Thorsten Glaser
-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.

  1   2   >