Hello, Have found this in dmesg (well earlier because of initcall_debug) I've never noticed that during boot (scrolls away too fast). Anyway -
[ 7.841871] NetLabel: Initializing [ 7.841983] NetLabel: domain hash size = 128 [ 7.842095] NetLabel: protocols = UNLABELED CIPSOv4 [ 7.842219] NetLabel: unlabeled traffic allowed by default [ 7.842338] BUG: at include/linux/slub_def.h:77 kmalloc_index() [ 7.842451] [ 7.842452] Call Trace: [ 7.842677] [<ffffffff8029215c>] get_slab+0x1cc/0x260 [ 7.842791] [<ffffffff8029229d>] __kmalloc+0xd/0x80 [ 7.842907] [<ffffffff802219ee>] cache_k8_northbridges+0x7e/0x100 [ 7.843024] [<ffffffff8062bd13>] gart_iommu_init+0x33/0x5b0 [ 7.843140] [<ffffffff8049f836>] netlbl_unlabel_acceptflg_set+0x86/0xf0 [ 7.843255] [<ffffffff80626f49>] pci_iommu_init+0x9/0x20 [ 7.843370] [<ffffffff806216d7>] kernel_init+0x157/0x330 [ 7.843485] [<ffffffff8020b0f8>] child_rip+0xa/0x12 [ 7.843601] [<ffffffff80373fd8>] acpi_ds_init_one_object+0x0/0x7c [ 7.843715] [<ffffffff80621580>] kernel_init+0x0/0x330 [ 7.843829] [<ffffffff8020b0ee>] child_rip+0x0/0x12 [ 7.843941] [ 7.844056] PCI-GART: No AMD northbridge found. Does this backtrace looks sane ? Hmm, netlabel code mixes with acpi_ds_init_one_object() ... Strange. On Wed, 2007-05-16 at 12:15 -0700, Andrew Morton wrote: > On Wed, 16 May 2007 21:00:41 +0300 > Zilvinas Valinskas <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > In short, on shutdown my laptop is always freezing now. I was able to > > capture the 'sysrq-P' (hit that several times), sysrq-T outputs. Please > > see .config and log messages at http://barclay.balt.net/~zilvinas/oops/ > > > > Kernel version I had built according git is : > > > > [EMAIL PROTECTED]:/projects/linux-amd64.git$ git describe HEAD > > v2.6.22-rc1-29-gfaa8b6c > > > > On top of that I have CFS v12 applied (no other changes otherwise). > > Please note that there is ''fglrx.ko'' loaded and kernel is tainted > > because of that (feel free to ignore the report ...). > > > > Anyway, 'sysrq-P' always show that PC is stuck at (NFS lockd?) and it is > > always the same backtrace is shown. 'sysrq-t' output is in > > 'kernel-nfs-freeze.log' file (did not want to post it here). > > > > Pid: 3652, comm: lockd Tainted: P 2.6.22-rc1-cfs-v12 #1 > > > > [<ffffffff8024a5a0>] wq_barrier_func+0x0/0x10 > > [<ffffffff8024a7e5>] destroy_workqueue+0x75/0xa0 > > [<ffffffff8833cd34>] :sunrpc:rpciod_down+0xf4/0x170 > > [<ffffffff8836dd74>] :lockd:lockd+0x244/0x300 > > [<ffffffff80233e1f>] schedule_tail+0x3f/0xb0 > > [<ffffffff8020b0f8>] child_rip+0xa/0x12 > > [<ffffffff8836db30>] :lockd:lockd+0x0/0x300 > > [<ffffffff8836db30>] :lockd:lockd+0x0/0x300 > > [<ffffffff8020b0ee>] child_rip+0x0/0x12 > > > > Hope this helps. Thanks in advance for any advice how to solve problem ! > > For now I am back to '2.6.21.1-cfs-v10'. > > > > Thanks for the report. I'm thinking "Oleg". - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
