linux-kernel - Re: PROBLEM: oops

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1251209206.7538.1159.camel@twins>
Date:	Tue, 25 Aug 2009 16:06:46 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Paweł Gołaszewski <blues@....pl>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: PROBLEM: oops

On Tue, 2009-08-25 at 15:55 +0200, Paweł Gołaszewski wrote:
> No matter which kernel I'm using (2.6.27 - 2.6.30) it crashes. Works for 
> few minutes and crashes. Even SysRq doesn't work.
> 
> Dunno how to trigger it on other machine than mine (I have two, both 
> affected). If more info is required - just ask.
> [...]
> [24483.211036] BUG: unable to handle kernel NULL pointer dereference at 00000058
> [24483.211144] IP: [<c081cf9a>] pick_next_task_fair+0x6a/0x100
> [24483.211247] Oops: 0000 [#1] SMP 
> [24483.211300] Modules linked in: netconsole configfs dm_mod softdog sch_sfq xfs raid10 uhci_hcd eepro100 ppdev parport_pc floppy parport ehci_hcd e100 piix i2c_piix4 thermal psmouse e1000 container ide_core usbcore mii button pcspkr serio_raw processor i2c_core sg evdev ext3 jbd mbcache scsi_wait_scan sd_mod crc_t10dif ata_piix libata dock aic7xxx sym53c8xx scsi_transport_spi scsi_mod raid1 md_mod
> [24483.211878] 
> [24483.211910] Pid: 1677, comm: md2_raid10 Not tainted (2.6.27.31-1 #1)

So you're saying .30 crashes at the exact same place?


--
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/