linux-kernel - Re: 2.6.21-rc5-mm4

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]

Date:	Tue, 03 Apr 2007 10:19:14 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Jiri Kosina <jikos@...os.cz>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, e1000-devel@...ts.sourceforge.net
Subject: Re: 2.6.21-rc5-mm4

Jiri Kosina wrote:
> On Tue, 3 Apr 2007, Kok, Auke wrote:
> 
>> Also, it would help a lot if you knew what kind of settings your init 
>> scripts are trying to configure. It seems that something is setting 
>> multicast or promiscuous mode. Do you happen to know which command is 
>> being executed by the shell?
> 
> It's 100% reproducible by running dhclient on the interface.
> 
> The kernel also panics (with different stacktrace but the same wrong 
> address it tries to dereference - 0xffffffff) when I do this:
> 
> (none):/# modprobe e1000
> Intel(R) PRO/1000 Network Driver - version 7.4.35-k2-NAPI
> Copyright (c) 1999-2007 Intel Corporation.
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 
> 00:0e:0c:72:b8:ad
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> (none):/# ifconfig eth0 up
> BUG: unable to handle kernel paging request at virtual address ffffffff
>  printing eip:
> ffffffff
> *pde = 00005067
> *pte = 00000000
> Oops: 0000 [#1]
> SMP
> last sysfs file: power/resume
> Modules linked in: e1000 ext3 mbcache jbd edd sg fan generic ata_piix 
> libata thermal processor sd_mod scsi_mod ide_disk ide_core
> CPU:    0
> EIP:    0060:[<ffffffff>]    Not tainted VLI
> EFLAGS: 00010046   (2.6.21-rc5-mm4-default #3)
> EIP is at 0xffffffff
> eax: 00000000   ebx: 00000000   ecx: 00000000   edx: 00000000
> esi: 00000000   edi: c0462008   ebp: 00000080   esp: c0463f94
> ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
> Process swapper (pid: 0, ti=c0462000 task=c038d340 task.ti=c0462000)
> Stack: c0102297 00000060 00000246 00000000 c049f5a4 c1d095a4 c01023fa c0363b12
>        20070126 c1d11000 c0467ae7 c034a48a c04671b9 00000000 00000000 00000000
>        00000000 00010000 00000000 00000000 00000000 c04887c0 00020800 00099800
> Call Trace:
>  [<c0102297>] mwait_idle_with_hints+0x3b/0x3f
>  [<c01023fa>] cpu_idle+0xa6/0xbf
>  [<c0467ae7>] start_kernel+0x459/0x461
>  [<c04671b9>] unknown_bootoption+0x0/0x202
>  =======================
> INFO: lockdep is turned off.
> Code:  Bad EIP value.
> EIP: [<ffffffff>] 0xffffffff SS:ESP 0068:c0463f94
> Kernel panic - not syncing: Attempted to kill the idle task!
> 
> 
> Seeing "mwait" there, it seemed like ACPI might be involved. Booting with 
> acpi=off didn't improve the situation though.
> 
> I just pulled your e1000 git tree into vanilla 2.6.21-rc5 ytrr and I can't 
> reproduce the problem, so it might be caused by something else.

we're also having problems reproducing it on that same combination (2.6.21-rc4 + 
my tree), so it points to something in -mm. Since your trace is completely 
different right now it looks like something else is fuzzing it up.

Since the e1000 changes are in rc5-mm3 as well, that might help to narrow it 
down quickly.

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