vice using systemd, but that instantly
> resulted in the following kernel panic:
[...]
> I don't know that this is the same bug at all, but I'm keeping it on
> this report for now as it seems at least related somehow.
The log messages don't look even slightly related, so please move this
to a separate
d imply
that older multi-socket systems with a shared memory controller would
not be affected, while some single-socket systems with multiple memory
controllers would be affected.
Ben.
--
Ben Hutchings
I say we take off; nuke the site from orbit. It's the only way to be
sure.
signatu
pdated until the next point release. See
https://lists.debian.org/debian-stable-announce/2017/12/msg2.html
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Description: This is a digitally signed message part
and I will upload them too.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
signature.asc
Description: This is a digitally signed message part
On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> There were several commits interspersed with sched/topology fixes
> upstream that I thought were cleanup and therefore didn't backport to
> the 3.16 stable branch. Now I suspect that at least some of them are
> needed.
>
they fix the regression for you?
If this doesn't help, I think we may just have to revert the
sched/topology fixes.
Ben.
--
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai
Stevenson
From: Peter Zijlstra <pet...@infradead.org>
Date: Fri, 14 Apr 2017 17:32:07
nding on which network configuration tools you use, you might need
to define additional dependencies for network-online.target or
remote-fs-pre.target.
Ben.
--
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.
signature.asc
Description: This is a digitally signed message part
deblobbing, seeing as the adaptor is
> functioning normally under a supposedly fully free system.
>
> I am worried there may be non-DFSG compliant firmware packaged in main.
[...]
There isn't, at least not in this instance. The log messages are a
little misleading.
Ben.
--
Ben Hutchings
Be
This isn't the first BUG message; please send the first one.
Also what extra modules you have added?
Ben.
--
Ben Hutchings
It is impossible to make anything foolproof because fools are so
ingenious.
signature.asc
Description: This is a digitally signed message part
On Sun, 2017-11-05 at 12:21 +0100, intrigeri wrote:
> Hi,
>
> Ben Hutchings:
> > My understanding was that enabling AppArmor shouldn't do very much
> > until a policy is loaded (which it won't be if you don't install the
> > userland tools). As you've found, that isn't
se they
> > have any input to provide.
>
> Can you try to set "lxc.aa_allow_incomplete = 1" in your config?
> LXC expects Ubuntus patched kernels when it comes to AppArmor, not the
> upstream ones :(
>
> And I think Debian enabled AppArmor by default in the lates
Package: libpam-runtime
Version: 1.1.8-3.6
Severity: grave
I performed a full-upgrade on a system with little space on the root
filesystem. This failed part way through due to running out of
space. A while after resolving this and completing the upgrade, I
found that:
1. The GNOME screensaver
er starts and some
> more as well.
Applications built for Linux are unrelated to Linux? I don't think so.
Ben.
--
Ben Hutchings
It is a miracle that curiosity survives formal education. - Albert
Einstein
signature.asc
Description: This is a digitally signed message part
On Thu, 2017-10-19 at 00:46 +0800, Liang Guo wrote:
> On Wed, Oct 18, 2017 at 9:25 PM, Ben Hutchings <b...@decadent.org.uk> wrote:
> > On Wed, 2017-10-18 at 14:21 +0200, Alexander Kurtz wrote:
> > > Ok, that's what I figured. Is there at least a solution to the "if th
On Wed, 2017-10-18 at 14:21 +0200, Alexander Kurtz wrote:
> On Wed, 2017-10-18 at 13:02 +0100, Ben Hutchings wrote:
> > > Please comment on bug #877925 [4] and/or #878922 [3] regarding on how
> > > to solve the "this package needs the current kernel's headers
> > &g
inal bug [4].
>
> Please comment on bug #877925 [4] and/or #878922 [3] regarding on how
> to solve the "this package needs the current kernel's headers
> installed" problem!
You cannot use package dependencies to do this. It has to be a run-
time check.
Ben.
--
Ben Hutchin
ich seems to be quite critical fixed
> anytime soon? :-)
>
> https://security-tracker.debian.org/tracker/CVE-2017-1000251
Probably less critical than you think, since we enable
CONFIG_CC_STACKPROTECTOR.
Ben.
--
Ben Hutchings
Kids! Bringing about Armageddon can be dangerous. Do not a
.11.0-2-amd64 installed and running (as in your report),
linux-headers-4.11.0-1-amd64 installed (as in your report)
Ben.
--
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.
signature.asc
Description: This is a digitally signed message part
h /usr/lib/debug/.build-id therefore have the same (hash-
based) name and *different* content.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
signature.asc
Description: This is a digitally signed message part
he exact same
code is ever built in two unrelated packages then their debug info
packages will conflict even if the regular binary packages don't.
Ben.
--
Ben Hutchings
Nothing is ever a complete failure; it can always serve as a bad
example.
signature.asc
Description: This is a digitally signed message part
that that has been fixed, as your report now
shows up in a list of bugs for the linux source package.
Were you ever able to determine how to trigger this data loss? Did you
find a fix?
Ben.
--
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.
signature.asc
On Mon, 2017-07-17 at 15:24 +0100, James Cowgill wrote:
> Hi,
>
> On 16/07/17 23:31, Ben Hutchings wrote:
> > Control: tag -1 upstream patch
> >
> > On Sun, 2017-07-16 at 23:21 +0100, Ben Hutchings wrote:
> > > On Thu, 2017-07-06 at 13:10 +0300, Adrian Bun
On Tue, 2017-07-25 at 07:33 -0400, Aaron Valdes wrote:
> Thanks Rene,
>
> I installed Debian 9 AMD64 on my Asus Laptop the other
> day. libreoffice writer (lowriter) did not crash on that system.
That's because this problem is specific to the Java implementation on
i386.
B
aders packages, which are architecture-dependent but depend on an
> identical *binary* version of the architecture-independent
> linux-headers-*-common package.
[...]
Oops, I missed this when making the latter arch-independent. This is
fixed in the git repo, and I should upload soon.
Ben.
--
B
had ethernet with a telephone)
>
> If you need some other extra infos, just ping me, i will give you the
> info next week.
>
> @Ben is the driver needinfo still actual? Sorry, for kernel issue i'm
> still a newbie :)
No, since I worked out what the driver is.
Ben.
--
Ben Hu
r and
not to work around it in the vmxnet3 driver, there is probably nothing
for us to do here.
Ben.
--
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.
signature.asc
Description: This is a digitally signed message part
Control: tag -1 upstream patch
On Sun, 2017-07-16 at 23:21 +0100, Ben Hutchings wrote:
> On Thu, 2017-07-06 at 13:10 +0300, Adrian Bunk wrote:
> > Control: reassign -1 src:linux 4.9.30-2
> > Control: retitle -1 mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
> >
his is actually a kernel bug:
> https://www.linux-mips.org/archives/linux-mips/2017-03/msg00580.html
That's now a 404, strangely. Did you mean "[PATCH 0/2] Fix indirect
syscall handler for syscalls with > 4 args"?
Ben.
--
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.
signature.asc
Description: This is a digitally signed message part
;
> Please fix LibreOffice Writer problem on 32bit Debian.
I've been discussing this regression with upstream develo[pers. It's
now understood and we have several possible fixes but we have not yet
settled on the best one.
You should also be able to work around it by temporarily disabling the
Stack
Control: tag -1 upstream patch moreinfo
On Fri, 30 Jun 2017 08:57:00 + Ximin Luo <infini...@debian.org> wrote:
> Ben Hutchings:
> > On Thu, 2017-06-29 at 17:45 +, Ximin Luo wrote:
> >> Ximin Luo:
> >>> [..]
> >>>
> >>> The
Package: src:linux-latest
Version: 80
Severity: serious
src:linux version 4.9.25-1 moved the debug info packages back to the
main archive and changed their name suffix from -dbgsym back to -dbg.
src:linux-latest needs to be changed accordingly.
Ben.
-- System Information:
Debian Release: 9.0
000-4000 rw-p 00:00 0
> [stack]
>
> Setting `ulimit -s 24576` still works, though.
Do you know how much stack space this function needs? Can you get the
page fault address? (I don't remember how to do that in gdb.)
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
his sound familiar?
No it doesn't.
> Should this issue be reassigned to the kernel?
[...]
Of course.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
at wheezy is new enough to run it.
Ben.
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
lugin <
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772>;,
> commons-daemon, ...).
Yes, that's what I worked out from bug #865303 and those merged with
it.
Ben.
> Can confirm that the updated patch fixes the problem (amd64).
--
Ben Hutchings
Sturgeon's Law: Ninety
distros applied an incorrect one.
Can you please test with this candidate fix?
https://people.debian.org/~benh/packages/CVE-2017-1000364/
Ben.
--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.
signature.asc
Description: This is a digitally signed message part
xed in unstable).
Right.
Ben.
--
Ben Hutchings
It is easier to change the specification to fit the program than vice
versa.
signature.asc
Description: This is a digitally signed message part
On Tue, 2017-06-06 at 01:24 +0100, Ben Hutchings wrote:
> On Tue, 2017-06-06 at 01:29 +0200, Axel Beckert wrote:
> > Hi,
> >
> > Ben Hutchings wrote:
> > > This includes many important bug fixes, including security fixes. It
> > > adds support for system
upstream.
>
> A proposed warning patch attached.
Haven't looked closely, but I'm OK with this in principle. I think we
should also taint the kernel (like we do for FAN_ALL_PERM_EVENTS).
Ben.
--
Ben Hutchings
Life would be so much easier if we could look at the source code.
signature.
On Mon, 2017-05-08 at 15:00 +0200, Thorsten Glaser wrote:
> Hi!
>
> I disagree with making this RC right now, for the following reasons:
[...]
I also disagree, and I like bugs for backported linux packages going to
the BTS as they are rarely specific to the backport.
Ben.
--
Ben Hut
On Sun, 2017-05-07 at 15:29 +0200, Ivo De Decker wrote:
> Hi Ben,
>
> On Thu, May 04, 2017 at 04:03:36AM +0000, Ben Hutchings wrote:
> > Files:
> > 6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional
> > rar_5.4.0+dfsg.1-0.1.dsc
> > d02b8742478d5e6
. That should be available on mirrors in a day or two. Let
us know if it works for you.
Ben.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
signature.asc
Description: This is a digitally signed message part
oday or tomorrow,
> unless someone else beats me to it.
[...]
Thanks for this information. I can reproduce the regression and am now
doing the bisection.
Ben.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
signature.asc
Description: This is a digitally signed message part
nel casues guests to crash. Is that correct? If so, can you check
whether the host kernel logs anything when this happens, and send that?
> I would like to do that once there is a newer kernel in proposed or
> security that needs to be tested anyway. Would that be OK, too?
[...]
But I can't fix
le a serial console, you can then use 'screen' or similar to view
and capture output on that serial port.
When I do this with virt-manager, the pty name is shown on the Details
tab once the VM is running. I don't know how to find it out in virsh.
Ben.
--
Ben Hutchings
All extremists s
n earlier BUG logged; please send that too.
Ben.
--
Ben Hutchings
All extremists should be taken out and shot.
signature.asc
Description: This is a digitally signed message part
ahead and made these changes. I
verified that they build on all release architectures except
mips/mipsel (porterboxes were down) and was able to test the result on
amd64, armhf, i386, powerpc, ppc64 (standing in for ppc64el) and s390x.
Ben.
--
Ben Hutchings
It is impossible to make anything foolproo
Package: rar
Version: 2:5.4.0-1
Severity: serious
Policy forbids executables statically linked to glibc (though other
C libraries such as dietlibc are allowed).
This is also a copyright violation. Proprietary programs can
generally be dynamically linked with glibc and distributed under the
Control: severity -1 important
Control: severity 824442 important
On Tue, 2017-04-11 at 23:20 +0200, Aurelien Jarno wrote:
> On 2017-04-11 03:35, Ben Hutchings wrote:
> > Control: tag -1 moreinfo
> >
> > On Mon, 10 Apr 2017 10:48:45 +0200 Aurelien Jarno <aurel...
x37c/0x570
> [usbcore]
[...]
Send the full oops message, not just the call trace.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Description: This is a digitally signed message part
e . The problem is
> that the __UAPI_DEF_IF_* constants are set to 1 in
> even if is not included.
[...]
Does this affect any real programs, or is this just theoretical (and
therefore should be downgraded)?
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Description: This
On Fri, 31 Mar 2017 09:18:06 +0200 Sebastian Andrzej Siewior wrote:
> On 2017-03-30 22:45:57 [+0100], Ben Hutchings wrote:
> > Upgrading severity as it would be pointless to release with this
> > version.
>
> Sure. And probably something for current stable, I don't know. Sho
On Sun, 2017-04-02 at 15:42 +0200, intrigeri wrote:
> Hi,
>
> Ben Hutchings:
> > How about "Breaks: busybox (<< 1:1.22.0-17~)"? I think that does the
> > job.
(I actually include busybox-static in the Breaks field too.)
> Yes :) At least it'll ensure
t need it, i.e. those that haven't cryptsetup
> installed, and haven't busybox already pulled by anything else.
[...]
How about "Breaks: busybox (<< 1:1.22.0-17~)"? I think that does the
job. I've actually committed that change but failed to upload yet.
Ben.
--
Ben Hutchings
On Sat, Mar 18, 2017 at 10:08:10PM +0100, Julien Aubin wrote:
> OK I did this. Does it have a huge impact on the system except mitigating
> the flaw ? (I don't think I have an HDLC hardware...)
If you don't know whether you have it, you don't have it. :-)
Ben.
--
Ben Hutchings
Life i
.]
Note that we already documented a mitigation for this in the DSA.
Ben.
--
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump
of a severed limb. - me, 29 June 1999
signature.asc
Description: This is a digitally signed message part
oordinate with the d-i maintainers,
thanks. We don't remove any packages; that happens automatically.
Ben.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be
development of an easy way to factor large prime numbers. - Bill Gates
signature.asc
De
On Wed, 2017-02-15 at 11:13 +, Simon McVittie wrote:
> On Sat, 26 Nov 2016 at 10:27:38 +0000, Ben Hutchings wrote:
[...]
> > The temporary workaround with /dev/ptmx could be made optional. It's
> > not OK to break the previously working configurations.
>
> If I'm unders
ntil I have discussed this with security@d.o.
...and the result was?
(I think this probably can be downgraded. At least on Linux, I expect
memory allocation to either succeed or kill the program. But this
should be fixed, anyway)
Ben.
--
Ben Hutchings
All the simple programs have been written, and all
Control: fixed -1 3.16.36-1
Control: fixed -1 4.0.2-1
signature.asc
Description: This is a digitally signed message part
p-kw.h
-rw-rw 1 ben ben 10382 Aug 2 03:01 locale/programs/locfile-kw.gperf
-rw-rw 1 ben ben 25742 Aug 2 03:01 locale/programs/locfile-kw.h
All the timestamps are equal in the upstream tarball, but if the .gperf
files are touched before building it will result in this build failure.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names
taken.
signature.asc
Description: This is a digitally signed message part
and fixes the test failures
with the older toolchain.
I made an NMU to fix this, and am attaching the debdiff.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names
taken.
diff -Nru sbsigntool-0.6/debian/changelog sbsigntool-0.6/debian/changelog
--- sbsigntool-0.6/d
be the severity of this bug report should be raised...
>
> Indeed, I think it should and am now raising it, and this should really
> be fixed for stretch.
>
> Unmounting /usr alongside other filesystems is problematic because:
>
> 1. Commands used after that might live or use a
is still an important bug, though.
Ben.
--
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get
out.
signature.asc
Description: This is a digitally signed message part
Package: gnome-settings-daemon
Version: 3.22.1-1
Severity: grave
I noticed that gnome-settings-daemon regularly crashes and restarts
on my system.
I investigated this with gdb and got the following backtrace:
#0 0x7f00e6aac261 in _g_log_abort (breakpoint=1) at
././glib/gmessages.c:487
#1
tten *and flushed* to
disk by the application, but was not readable afterward - this does not
count. Writes are buffered, and user space has to deal with that.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
Control: tag -1 upstream fixed-upstream pending
On Mon, 2017-01-02 at 02:38 +, Ben Hutchings wrote:
> On Mon, 2017-01-02 at 02:34 +0000, Ben Hutchings wrote:
> [...]
> > Let's try without that -pie:
> >
> > $ ld -m elf64lppc -T arch/powerpc/boot/zImage.lds -
works! So we need to filter out -pie here as well. (Or
disable building these wrappers, since we don't actually package them.
But that doesn't seem to be a kconfig option)
Ben.
--
Ben Hutchings
Q. Which is the greater problem in the world today, ignorance or
apathy?
A. I don't know and I couldn't care less.
signature.asc
Description: This is a digitally signed message part
On Mon, 2017-01-02 at 02:34 +, Ben Hutchings wrote:
[...]
> Let's try without that -pie:
>
> $ ld -m elf64lppc -T arch/powerpc/boot/zImage.lds -o
> arch/powerpc/boot/zImage.pseries arch/powerpc/boot/pseries-head.o
> arch/powerpc/boot/of.o arch/powerpc/boot/epapr.o .
This should be corrected in the next version.
Please report whether the next update to linux-signed-4.8.0-2-amd64
fixes this.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names
taken.
signature.asc
Description: This is a digitally signed message part
On Wed, 2016-12-21 at 22:49 -0500, Theodore Ts'o wrote:
> fixed 847575 1.43.3-1
> thanks
>
> On Wed, Dec 21, 2016 at 11:57:43PM +, Ben Hutchings wrote:
> > >
> > > I intended to prepare a patch but found that e2fsprogs no longer builds
> > > the stat
d.
Oops, sorry for the wrong version.
Ben.
--
Ben Hutchings
It is a miracle that curiosity survives formal education. - Albert
Einstein
signature.asc
Description: This is a digitally signed message part
On Mon, 2016-12-12 at 05:59 +, Ben Hutchings wrote:
> On Mon, 2016-12-12 at 13:51 +0800, Zheng Xu wrote:
[...]
> > mozjs1.8.5 -- The patch is different with the upstream one. Because in the
> > old js, there might be objects pass from C allocation, only modify the heap
&
d all the packages which depends on mozjs1.8.5
That's not an option as no library ABI changes can go into testing
before the release.
Ben.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
signature.asc
Description: This is a digitally signed message part
On Sun, 2016-12-11 at 03:24 +0100, John Paul Adrian Glaubitz wrote:
> On 12/11/2016 03:13 AM, Ben Hutchings wrote:
> > Looking at the patch that was added in -4: WTF? It changes the library
> > ABI, but you didn't bump the soname. Of course that breaks clients!
>
> That's o
oken in the same way.
At this point in the release cycle no more library transitions are
allowed, so libmozjs has to be fixed with a kluge like the patch that
Zheng Xu sent, not the upstream change.
Ben.
--
Ben Hutchings
Any sufficiently advanced bug is indistinguishable from a feature.
signature.
On Sat, 2016-12-10 at 11:24 +0200, Adrian Bunk wrote:
> On Thu, Dec 08, 2016 at 02:21:21AM +0000, Ben Hutchings wrote:
> > ...
> > > (2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
> > > 0.125)" which it will need even after #847340 is fixe
Package: util-vserver
Version: 0.30.216-pre3120-1.1
Severity: serious
Some binaries in util-vserver are statically linked to dietlibc which
is licensed under GNU GPL. util-vserver must have a Built-Using field
to record which version was used and ensure that the corresponding
source package is
Package: ngetty
Version: 1.1-3
Severity: serious
ngetty is statically linked to dietlibc which is licensed under GNU
GPL. ngetty must have a Built-Using field to record which version was
used and ensure that the corresponding source package is kept in the
archive.
Ben.
-- System Information:
Package: integrit
Version: 4.1-1
Severity: serious
integrit is statically linked to dietlibc which is licensed under
GNU GPL. integrit must have a Built-Using field to record which
version was used and ensure that the corresponding source package is
kept in the archive.
Ben.
-- System
Package: fgetty
Version: 0.7-1
Severity: serious
fgetty is statically linked to dietlibc which is licensed under GNU
GPL. fgetty must have a Built-Using field to record which version was
used and ensure that the corresponding source package is kept in the
archive.
Ben.
-- System Information:
Package: e2fsck-static
Version: 1.43.3-1
Severity: serious
e2fsck-static is statically linked to dietlibc which is licensed under
GNU GPL. e2fsck-static must have a Built-Using field to record which
version was used and ensure that the corresponding source package is
kept in the archive.
Ben.
hat (because
> important stuff like nginx need luajit), but presumably the transition
> freeze applies here?
They both build libluajit-5.1-2 so I don't see that there's any
transition needed.
Ben.
--
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky
signature.asc
Description: T
On Thu, 2016-12-08 at 15:34 +1300, Ben Caradoc-Davies wrote:
> On 08/12/16 15:21, Ben Hutchings wrote:
> > Doesn't apt-listbugs see bugs that 'affect' a package?
>
> I do not know. Does "affects" provide the version information that
> apt-listbugs needs to filter bugs
ls is fixed, so I'm assigning this bug
back.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
[...]
Missing firmware isn't a kernel bug, it's a bug in a firmware package.
(And X blowing up is probably an X driver bug.)
The missing firmware is fixed in the latest firmware-nonfree upload.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
processors should still be supported. We've only dropped
support for 586-class processors (like the original Pentium).
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
testing now has 4.8.7-1; please report whether it works for you.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
signature.asc
Description: This is a digitally signed message part
hem from the
> (non-free) sources.
>
> I guess a new upload should be done.
*sigh* I keep forgetting that non-free is special and this won't be
auto-built.
Ben.
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain
[ -x "$screen_bin" -a "$TERM_TYPE" != network -a "$TERM" != dumb ]
Is that really what we want?
Ben.
> # there's GNU/screen binary, run menu in it.
> > # call this script again with in GNU/screen, possibly in UTF-8
> > mode
> > SCREEN_OPT=""
>
--
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at
once.
signature.asc
Description: This is a digitally signed message part
Package: src:linux
Version: 4.7.8-1
Severity: serious
perf uses SHA1 and MD5 implementations from OpenSSL's libcrypto if it
is found at build time. Since perf is under GPLv2 without an OpenSSL
exception, this isn't allowed in Debian.
We need to disable this feature or substitute implementations
Control: severity -1 normal
On Tue, 2016-11-01 at 19:17 +0100, Santiago Vila wrote:
> On Tue, Nov 01, 2016 at 12:13:00PM -0600, Ben Hutchings wrote:
> > Do Debian buildds use overlayfs?
>
>
> Yes, I think so. Just look at any build log in buildd.debian.org
Do Debian buildds use overlayfs? If not then I don't see how this can
be serious.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, the real world is often a special
case.
signature.asc
Description: This is a digitally signed message part
686 in unstable, depending on the new image package
> linux-image-4.8.0-1-686, but instead I see that the unstable
> version is still identical to the testing one:
[...]
That is waiting for the same reason.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, th
Control: tag -1 moreinfo
I think this may be the same as bug #841850 which is fixed in version
4.8.5-1. Please let us know whether that works for you.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, the real world is often a special
case.
signature.asc
07)
>
> 4.7.6-1 is now running correctly again, 4.7.8-1 did not boot, see
> above!
> (So the first line does _not_ describe the problematic system!)
[...]
We're going to need some more information about where things went
wrong, which you should be able to get by replacing the 'qui
1 | unstable-debug | source
>
> You should be noted that building kernel from vanilla source isn't
> good idea in Debian.
[...]
It is absolutely supported (so long as you enable the necessary
features) and is common practice. However, any bugs in some other
version of t
ild kernel successfully.
>
> I'm currently looking for correct way to do this trick.
>
>
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
patch -p1'. But I haven't yet taken the
time to try it out.
Ben.
--
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.
signature.asc
Description: This is a digitally signed message part
nds I am not sure, the keybroad is useless. I can type nothing. And I
> find there are some words on the screen.
> NMI watchdog: BUG: soft lockup CPU#0 stuck for 23s ... And the mechine begins
> to beep.
Does this problem still occur when using Linux 4.7 (currently in
unstable)?
Ben.
--
201 - 300 of 1356 matches
Mail list logo
