| 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
| ||
|
Message-Id: <20080307034155.A8C6EDBA2@gherkin.frus.com> Date: Thu, 6 Mar 2008 21:41:55 -0600 (CST) From: rct@...s.com (Bob Tracy) To: linux-kernel@...r.kernel.org CC: linux-alpha@...r.kernel.org Subject: [regression]2.6.25-rc4: boot panic on alpha The regression is relative to 2.6.25-rc1 + timer fixes (added when I reported the problems with 2.6.25-rc1 relative to 2.6.24). I haven't tried -rc2 or -rc3. Might be related to similar reports I've seen, but wanted to add the Alpha platform to the list. The -rc4 kernel boots, but at some point following initialization of the SCSI layer, there's a panic with enough diagnostic output that a 50-line screen can't hold it all. Unfortunately, the system logging isn't active, so nothing gets captured. The panic is completely reproducible. The "Code" line at the bottom of the panic output is 44220001 4821f621 4821b681 4821f62b f420004f 00000081 <0000009b> 0066c012 The first line of the "Trace" section is [<fffffc000031a41f>] iommu_arena_alloc+0x64/0xe0 Platform is an Alpha PWS 433au. gcc is version 4.1.2 (Debian 4.1.1-21). -- ------------------------------------------------------------------------ Bob Tracy | "I was a beta tester for dirt. They never did rct@...s.com | get all the bugs out." - Steve McGrew on /. ------------------------------------------------------------------------ -- 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/
Powered by blists - more mailing lists