Bug#925919: Info received (RFT: linux with fix for VMware regression)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Kernel Team If you wish to submit further information on this problem, please send it to 925...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 925919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
RFT: linux with fix for VMware regression
I've uploaded a new version of linux to: https://people.debian.org/~benh/packages/jessie-security/ which I believe will fix this regression (bug #925919). Please let me know whether it works for you. I only included the amd64 linux-image package and sources there, but can add i386 linux-image packages if needed. Ben. -- Ben Hutchings Design a system any fool can use, and only a fool will want to use it. signature.asc Description: This is a digitally signed message part
Re: jessie-updates gone
On Fri, 2019-03-29 at 11:13 +0100, Pierre Fourès wrote: > The way I understand it, but I asked for clarification and > confirmation in my previous message [1], is that all « updates » goes > into -proposed-updates/, but the one who need to be quickly applied > into the distribution (but aren't security updates) are duplicated > from -proposed-updates/ into -updates/. Theses are the updates who > can't wait and must be applied between the point releases. Then, when > point releases occurs, all packages in -proposed-updates/ moves into > the stable repository of the distribution. They are automatically > removed from -proposed-updates/. This isn't true for the -updates/ > repository as it requires manual pruning. Nonetheless, all packages > in > -updates/ went into the stable repository (from the -proposed-updates > they originated from) when the point-release occurred. So nothing is > lost. But is that right ? Yes - see https://lists.debian.org/debian-devel-announce/2011/03/msg000 10.html , linked from every post to the debian-stable-announce list. (There will probably be a better URL somewhere on release.d.o once someone finds sufficient tuits to actually make it.) The removal of packages from p-u after adding them to stable is part of the actions performed by ftp-master during the point release (easily done as the package sets are the same). Technically, it is possible for an update from -updates / p-u to not be included in a point release, but that will usually be due to a regression being found before the point release, and in such cases there will likely be a follow-up update. Regards, Adam
Re: DLAs in the website: some updates and issues
Hi,
On 18/03/2019 15:56, Sylvain Beucler wrote:
> On Thu, Mar 07, 2019 at 08:02:18PM +0100, Laura Arjona Reina wrote:
>> El 5/3/19 a las 16:07, Markus Koschany escribió:
>>> thank your for your work on our website. Ideally we would like to make
>>> the whole process fully automatic without the need for any manual
>>> interaction.
>> This is being discussed in #859123: automate import of DLAs and DSAs in
>> www.debian.org
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859123
>>
>> In particular, I think this message from Lev Lamberov is relevant:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859123#20
>>
>>> Can you tell us more about the current work flow of our DSA
>>> announcements on the front page?
>> DSAs are manually imported by a web team member or a security team
>> member, using the parse_advisory.pl script.
>>
>>> Does someone from the webteam reviews
>>> the generation by hand?
>> Usually yes, but also, as it is noted in Lev's message, I think the
>> format of DSA is more standard.
> I had a look at parse-dla.pl / parse-advisory.pl, and let's face it:
> it's a bunch of ad-hoc regexps that happen to work. Most of the times.
>
> I couldn't find a satisfying way to fix the trailing
> recurring bug.
FYI I tracked down the difference ("For the (old)stable" vs. "For Debian
X") and adapted the regexp.
This confirms DLA formatting is on par with DSA's, the conversion script
is just fragile.
>>> I'm sure we can improve the current parse-dla.pl
>>> script and fix those markup bugs. We also thought about downloading the
>>> announcements from https://lists.debian.org/debian-lts-announce/ and
>>> then create the DLA on the web page automatically. Is this a viable plan?
>>>
>> I don't know.
>>
>> I guess that if the security team does not that already it's probably
>> because of a reason (or maybe because nobody in the web team could find
>> the time+skills+motivation needed to make it possible...).
> So the core issue is taking a text mail and automagically generate a
> HTML equivalent.
>
> Lev suggested 4 months ago that LTS and DebSec work on a common
> mark-up format. We could attempt to switch to MarkDown, but from
> experience it breaks easily, especially wrt newlines.
>
> Alternatively, a simple answer would be to keep the headers parsing
> (Package/Version/CVE ID/Debian Bug) but import the free-form
> description text verbatim as a monospace block (such as ).
> i.e. stop coping with ul/li, just auto-link https://... bits.
>
> I don't suggest merely linking the list archives, since AFAIU there is
> demand for advisories translations (if there isn't, though, a link
> would be enough IMHO).
>
> What do you think?
>
> Cheers!
> Sylvain
Re: jessie-updates gone
On 27.03.19 11:20, Bernie Elbourn wrote: I am very grateful for all the work done here. You are all heroes! Can I gently ask if we can just blank the stretch-updates archive next time round please. Otherwise every stable machine out there now will need a change. Am 27.03.19 um 12:50 schrieb Matus UHLAR - fantomas: That's what I meant too. I probably should have emphasized that. If it is possible to wiz up a blank jessie-updates this will save me visiting a bunch of systems throwing apt errors in next few days. I wonder if it wasn't blank already. All of its contents was supposed to be moved to jessie main archive with last point release and no content should be there after that. On 27/03/2019 13:33, Markus Koschany wrote: So the idea is to readd the empty jessie-updates directory to avoid apt errors when updating? Jörg is this possible? On 27.03.19 14:02, Emilio Pozuelo Monfort wrote: Yes, I talked to them earlier today and they agreed to bringing it back to avoid these problems on users that have jessie-updates on their sources.list. and when is this expected to happen? jessie-proposed-updates could also be brought back, though that's not enabled by default upon installation so it should be less problematic if it stays removed (though some people may have it so it wouldn't hurt to bring it back as well). I agree although I don't use it neither. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Posli tento mail 100 svojim znamim - nech vidia aky si idiot Send this email to 100 your friends - let them see what an idiot you are
Re: jessie-updates gone
Le ven. 29 mars 2019 à 10:11, Matus UHLAR - fantomas a écrit : > > >>On 27.03.19 11:20, Bernie Elbourn wrote: > >>>If it is possible to wiz up a blank jessie-updates this will save me > >>>visiting a bunch of systems throwing apt errors in next few days. > > >On 2019-03-27 11:50, Matus UHLAR - fantomas wrote: > >>I wonder if it wasn't blank already. All of its contents was > >>supposed to be > >>moved to jessie main archive with last point release and no content > >>should > >>be there after that. > > On 27.03.19 13:52, Adam D. Barratt wrote: > >Packages aren't moved from -updates to (old)stable, they're moved from > >p-u. Packages only get removed from -updates following manual action > >from a Release Team member. > > so, as I understand it, packages like clamav, spamassassin and others that > are in -updates may not get to main archive with a point release? > > Is there anything other needed to get them in? > > iirc, the -updates (formerly called volatile) was created to contain > packages that really need updates during distribution lifecycle, just like > antiviruses, spam filters and alike. > > They should not be lost. > The way I understand it, but I asked for clarification and confirmation in my previous message [1], is that all « updates » goes into -proposed-updates/, but the one who need to be quickly applied into the distribution (but aren't security updates) are duplicated from -proposed-updates/ into -updates/. Theses are the updates who can't wait and must be applied between the point releases. Then, when point releases occurs, all packages in -proposed-updates/ moves into the stable repository of the distribution. They are automatically removed from -proposed-updates/. This isn't true for the -updates/ repository as it requires manual pruning. Nonetheless, all packages in -updates/ went into the stable repository (from the -proposed-updates they originated from) when the point-release occurred. So nothing is lost. But is that right ? Pierre. [1] https://lists.debian.org/debian-lts/2019/03/msg00142.html
Re: Kernel 3.16.0-8-amd64 on vmware : corrupted page table
There is already a report in the BTS about this as well. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925918 smime.p7s Description: S/MIME Cryptographic Signature
Re: Kernel 3.16.0-8-amd64 on vmware : corrupted page table
Am 29.03.19 um 10:41 schrieb Bernhard Schmidt: Hi, > > sorry for not setting References correctly, I wasn't subscribed until now. > > We're hitting the same issue. Sometimes we see a backtrace in various > places, most of the times the machine just hangs (the cursor stops > blinking and it doesn't respond anymore). > > Rebooting into -7 seems to fix it. > > We're also on VMware ESXi 6.7. I don't think we have physical systems > with Jessie left, so I can't tell whether it only affects VMware. Attached the syslog of a machine that threw a lot of kernel Oops and broke the filesystem, but somehow still managed to write the log. We have some machines that are successfully running this kernel version on the same VMware infrastructure. Does not seem to be related to 1 vCPU vs. 2 vCPU. Bernhard syslog.gz Description: application/gzip smime.p7s Description: S/MIME Cryptographic Signature
Re: Kernel 3.16.0-8-amd64 on vmware : corrupted page table
Hi, sorry for not setting References correctly, I wasn't subscribed until now. We're hitting the same issue. Sometimes we see a backtrace in various places, most of the times the machine just hangs (the cursor stops blinking and it doesn't respond anymore). Rebooting into -7 seems to fix it. We're also on VMware ESXi 6.7. I don't think we have physical systems with Jessie left, so I can't tell whether it only affects VMware. Best Regards, Bernhard -- Bernhard Schmidt Netzbetrieb / IPv6 / DNSSEC Leibniz-Rechenzentrum Leibniz Supercomputing Centre Boltzmannstr. 1 D-85748 Garching b. Muenchen Tel: +49 89 35831-7885 E-Mail/Jabber: bernhard.schm...@lrz.de
Re: LTS packages changelogs on packages.d.o / metadata.ftp-master.d.o
Hi On Friday 29 March 2019 03:03 PM, Matus UHLAR - fantomas wrote: > Hello, > > trying to look at changelog of packages in LTS, it's not available on links > from packages.debian.org that point to metadata.ftp-master.d.o > > e.g. > https://packages.debian.org/jessie/linux-support-3.16.0-6 > https://packages.debian.org/jessie/linux-support-3.16.0-7 > https://packages.debian.org/jessie/linux-support-3.16.0-8 > all point to: > https://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_3.16.64-1_changelog > > > which does not exist. > can I find those changelogs in an easy way (without installing those > packages)? >From above packages.d.o pages click on the `Developer Information` link on the right side. It will take you to the new package tracker. From there you can find it. for eg: > https://packages.debian.org/jessie/linux-support-3.16.0-6 https://tracker.debian.org/media/packages/l/linux/changelog-3.16.64-1 --abhijith
LTS packages changelogs on packages.d.o / metadata.ftp-master.d.o
Hello, trying to look at changelog of packages in LTS, it's not available on links from packages.debian.org that point to metadata.ftp-master.d.o e.g. https://packages.debian.org/jessie/linux-support-3.16.0-6 https://packages.debian.org/jessie/linux-support-3.16.0-7 https://packages.debian.org/jessie/linux-support-3.16.0-8 all point to: https://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_3.16.64-1_changelog which does not exist. can I find those changelogs in an easy way (without installing those packages)? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. "Two words: Windows survives." - Craig Mundie, Microsoft senior strategist "So does syphillis. Good thing we have penicillin." - Matthew Alton
Re: jessie-updates gone
On 27.03.19 11:20, Bernie Elbourn wrote: If it is possible to wiz up a blank jessie-updates this will save me visiting a bunch of systems throwing apt errors in next few days. On 2019-03-27 11:50, Matus UHLAR - fantomas wrote: I wonder if it wasn't blank already. All of its contents was supposed to be moved to jessie main archive with last point release and no content should be there after that. On 27.03.19 13:52, Adam D. Barratt wrote: Packages aren't moved from -updates to (old)stable, they're moved from p-u. Packages only get removed from -updates following manual action from a Release Team member. so, as I understand it, packages like clamav, spamassassin and others that are in -updates may not get to main archive with a point release? Is there anything other needed to get them in? iirc, the -updates (formerly called volatile) was created to contain packages that really need updates during distribution lifecycle, just like antiviruses, spam filters and alike. They should not be lost. In the case of jessie, it appears there was still at least an old kernel package in there. luckily, nothing important. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Emacs is a complicated operating system without good text editor.
Kernel 3.16.0-8-amd64 on vmware : corrupted page table
Hi, Our Debian 8 servers have picked up the kernel security update linux-image-3.16.0-8-amd64 . Soon after reboot, problems started to appear, mainly various process crashes with messages like : Mar 28 11:07:35 server123 kernel: [16203.774877] java: Corrupted page table at address d58184a0 Processes become zombies or virtual machines start to grab all the CPU they can (and become unresponsive). It only affects our virtual machines, which are all on VMWare. We have a few hardware servers and no problems so far on that. Does anybody experiences something similar? We have configured Grub to boot on 3.16.0-7 while we investigate. Regards, -- Jérémie Pierson
