linux-kernel - Re: 2.6.30-rc1: invalid opcode with call trace

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 for Android: free password hash cracker in your pocket

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

Message-ID: <49DC4E3A.6040809@gawab.com>
Date:	Wed, 08 Apr 2009 00:11:54 -0700
From:	Justin Madru <jdm64@...ab.com>
To:	Jens Axboe <jens.axboe@...cle.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Arjan van de Ven <arjan@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 2.6.30-rc1: invalid opcode with call trace

Jens Axboe wrote:
> On Wed, Apr 08 2009, Ingo Molnar wrote:
>   
>> * Ingo Molnar <mingo@...e.hu> wrote:
>>
>>     
>>> I too have an async hang/crash, on an old-style SCSI (aic7xxx) box 
>>> - hang log attached below.
>>> [...]
>>>
>>> ( Full bootlog attached below as well - i'm sending the config as a 
>>>   reply as this mail is close to lkml size limits already. )
>>>       
>> Config attached.
>>
>>  known bad  : v2.6.29-9854-gd508afb
>>  known good : v2.6.29
>>
>> Suspected commit introducing the regression:
>>
>>  9710794: async: remove the temporary (2.6.29) "async is off by default" code
>>
>> (i'll now try a revert of this.)
>>     
>
> That's what I figured was the culprit as well, but that does not really
> tell us anything about what part of async.c is buggy :-)
>
>   
In my case, the system doesn't hang or anything, it continues to boot 
into a working system (except for no wireless and usb).
The only thing is that shutting down doesn't work. I have to hold the 
power button because it hangs on shutdown.

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