Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic

2023-04-02 Thread Borislav Petkov
On Sun, Apr 02, 2023 at 03:13:05PM +0200, Guy Durrieu wrote: > Yes it does. Thanks for testing. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette

Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic

2023-04-02 Thread Borislav Petkov
On April 2, 2023 12:41:46 PM GMT+02:00, Guy Durrieu wrote: >My system worked fine with kernel 6.1.15, but stopped booting after >upgrading to 6.1.20 and resulted in a kernel panic: Does this fix it: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent Thx. -- Sent

Bug#752773: Bug report: the new listings.sty yields failures

2014-12-12 Thread Borislav Petkov
On Sun, 29 Jun 2014 10:07:31 +0900 Norbert Preining prein...@logic.at wrote: Dear Jobst, one more thing: On the TeX Live mailing list Qing Lee send a fix: **8 It seems that listings used brace trick in a wrong way since 2014/03/04 v1.5c: ... %

Bug#717473: [PATCH] adm64_edac: Fix single-channel setups

2013-07-29 Thread Borislav Petkov
of a sudden a second channel appears. Reported-and-tested-by: Roger Leigh rle...@debian.org Signed-off-by: Borislav Petkov b...@suse.de --- drivers/edac/amd64_edac.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c index

Bug#717473: [PATCH] adm64_edac: Fix single-channel setups

2013-07-29 Thread Borislav Petkov
On Mon, Jul 29, 2013 at 04:00:52PM +0100, Ben Hutchings wrote: There's a typo in the subject line. :-) Yep, looks like I've gradually gotten unnaccustomed to typing amd ... it's not in the fingers anymore. :-) Thanks, fixed. -- Regards/Gruss, Boris. Sent from a fat crate under my desk.

Bug#717473: BUG: Null pointer deref in amd64_edac_mod/amd64_probe_one_instance during boot

2013-07-24 Thread Borislav Petkov
On Wed, Jul 24, 2013 at 12:04:49AM +0100, Ben Hutchings wrote: This is absolutely stable material. Most of the people affected are not going to work out that they plugged their memory in wrong. (And maybe some of them only have one module.) Hmm, not from my experience. This is the first report

Bug#717473: BUG: Null pointer deref in amd64_edac_mod/amd64_probe_one_instance during boot

2013-07-23 Thread Borislav Petkov
On Mon, Jul 22, 2013 at 08:19:26PM +0100, Roger Leigh wrote: Ben's patch does allow me to boot the system with the memory in this configuration on a 3.10 kernel. Ok, I actually think we can fix it the way below. It should be equivalent to Ben's patch in current functionality with the difference

Bug#717473: BUG: Null pointer deref in amd64_edac_mod/amd64_probe_one_instance during boot

2013-07-23 Thread Borislav Petkov
On Tue, Jul 23, 2013 at 11:24:17PM +0100, Roger Leigh wrote: I've tested it against 3.10 and I can confirm that it works. I've booted the system with the DRAM on the same channel, and on separate channels, and it's working without problems in both cases. That's good news, thanks for testing

Bug#717473: BUG: Null pointer deref in amd64_edac_mod/amd64_probe_one_instance during boot

2013-07-21 Thread Borislav Petkov
On Sun, Jul 21, 2013 at 06:41:52PM +0100, Ben Hutchings wrote: On Sun, 2013-07-21 at 09:54 +0100, Roger Leigh wrote: If the bug is in amd64_edac_mod, there are only two possible commits which could cause the problem: 1eef12825 amd64_edac: Correct DIMM sizes 94c1acf2c amd64_edac: Add

Bug#700333: Stack trace

2013-04-28 Thread Borislav Petkov
On Sun, Apr 28, 2013 at 05:26:07PM +0400, vita...@yourcmc.ru wrote: When you do a suspend/resume cycle. OK, yes, I've found it there. The bug says The photo shows a BUG in hrtimer_interrupt() after making the hibernation image and while resuming the non-boot CPUs. so I'm guessing with

Bug#700333: Stack trace

2013-04-27 Thread Borislav Petkov
On Sat, Apr 27, 2013 at 07:08:42PM +0400, vita...@yourcmc.ru wrote: Looks like we can't do anything about that in the HPET code itself. Vitaliy, could you try that patch ? Thanks, I've tried it several days ago (and still using a patched kernel :)) - the box survives. But at which moment

Bug#700333: Stack trace

2013-04-20 Thread Borislav Petkov
+ tglx. On Sun, Apr 21, 2013 at 01:38:33AM +0400, vita...@yourcmc.ru wrote: Stack trace picture is here: http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg Vitaliy reported that his system crashes when suspending to disk. This was a regression from 3.2 to 3.7, and remains in 3.8. Some

Bug#700422: wdm shouldn't use /dev/mem

2013-02-14 Thread Borislav Petkov
On Thu, Feb 14, 2013 at 04:15:55PM +0100, Agustin Martin wrote: I have prepared a personal package and put it in my personal Debian repo under http://people.debian.org/~agmartin/debian-store/misc. Changes file is signed with my Debian gpg key, available from the Debian keyring. Tested with

Bug#700421: wdm shouldn't use /dev/mem

2013-02-12 Thread Borislav Petkov
-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=08_do_not_use_dev_mem.patch Author: Borislav Petkov b...@alien8.de Description: Do not use /dev/mem as a randomFile diff --git a/debian/man/wdm.1x b/debian/man/wdm.1x index 5f468d5fcc36..968acf293f2f 100644 --- a/debian/man/wdm.1x

Bug#700422: wdm shouldn't use /dev/mem

2013-02-12 Thread Borislav Petkov
Package: wdm Version: 1.28-13 Severity: normal Tags: upstream patch Hi, this is my first reporting a bug against a debian package so I very well might've missed something in the process. Here's the deal: wdm still uses /dev/mem in genauth.c to generate a tmp key and it shouldn't. The kernel

Bug#700422: wdm shouldn't use /dev/mem

2013-02-12 Thread Borislav Petkov
Hi Agustin, On Tue, Feb 12, 2013 at 07:17:53PM +0100, Agustin Martin wrote: Thanks for your contribution. Nice to see a way to get rid of the program wdm tried to access /dev/mem ... messages. Yeah, it was about time. :-) wdm is currently orphaned and no maintainer is explicitly caring of