linux-kernel - Re: 2.6.20-mm2

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: <200702181344.54959.rjw@sisk.pl>
Date:	Sun, 18 Feb 2007 13:44:54 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Neil Brown <neilb@...e.de>,
	Jeff Garzik <jeff@...zik.org>, linux-ide@...r.kernel.org,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: 2.6.20-mm2

On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.20-mm2/
> 
> Will appear later at
> 
>  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/

Two problems:

1) A showstopper with the root partition on RAID1:

md: raid1 personality registered for level 1
[--snip--]
md: multipath personality registered for level -4
register_blkdev: failed to get major for mdp
[--snip--]
VFS: Cannot open root device "md1" or unknown-block(0,0)

At the moment I have no serial console attached to the box, so I had to rewrite
the messages manually.

2) On HPC nx6325 I get the following 100% of the time during the resume from
disk:

BUG: at drivers/pci/pci.c:823 pcim_enable_device()

Call Trace:
 [<ffffffff80325ff8>] pcim_enable_device+0x93/0xb3
 [<ffffffff803a974a>] ata_pci_device_do_resume+0x21/0x5e
 [<ffffffff803b5e6c>] sil_pci_device_resume+0x1c/0x51
 [<ffffffff8032800d>] pci_device_resume+0x22/0x53
 [<ffffffff8039ae58>] resume_device+0xca/0x131
 [<ffffffff8039af40>] dpm_resume+0x81/0xd3
 [<ffffffff8039afc2>] device_resume+0x30/0x45
 [<ffffffff802a0792>] snapshot_ioctl+0x245/0x63e
 [<ffffffff8023cfcc>] do_ioctl+0x5e/0x77
 [<ffffffff8022d2b3>] vfs_ioctl+0x25c/0x279
 [<ffffffff80246a80>] sys_ioctl+0x5f/0x82
 [<ffffffff80215586>] sys_write+0x47/0x70
 [<ffffffff8025711e>] system_call+0x7e/0x83

Nevertheless, the system seems to be fully functional after the resume.

[I've been observing it since 2.6.20-git10 and have reported it for a couple
of times, but apparently nobody cares. :-(]

Greetings,
Rafael
-
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/