linux-kernel - Re: next-20081126: x86_64: kernel BUG at kernel/params.c:637

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a4423d670811280458r6e905433xa31d8d67741d8406@mail.gmail.com>
Date:	Fri, 28 Nov 2008 15:58:54 +0300
From:	"Alexander Beregalov" <a.beregalov@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	"Ingo Molnar" <mingo@...e.hu>
Subject: Re: next-20081126: x86_64: kernel BUG at kernel/params.c:637

2008/11/26 Alexander Beregalov <a.beregalov@...il.com>:
> Brought up 4 CPUs
> Total of 4 processors activated (23949.39 BogoMIPS).
> khelper used greatest stack depth: 5712 bytes left
> net_namespace: 752 bytes
> NET: Registered protocol family 16
> ACPI FADT declares the system doesn't support PCIe ASPM, so disab
>
> ACPI: bus type pci registered
> PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> PCI: MCFG area at e0000000 reserved in E820
> PCI: Using MMCONFIG at e0000000 - efffffff
> PCI: Using configuration type 1 for base access
> PCI: Dell PowerEdge 1950 detected, enabling pci=bfsort.
> ------------[ cut here ]------------
> kernel BUG at kernel/params.c:637!
> invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
> last sysfs file:
> CPU 0
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.28-rc6-next-20081126 #24
> RIP: 0010:[<ffffffff806d7b25>]  [<ffffffff806d7b25>] param_sysfs_init+0x86/0xf3

Works again on next-20081128
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/