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>] [day] [month] [year] [list]
Message-Id: <200703222005.06115.wpk@dst-labs.com>
Date:	Thu, 22 Mar 2007 20:05:06 +0100
From:	Witold Krecicki <wpk@...-labs.com>
To:	linux-kernel@...r.kernel.org
Subject: 2.6.21-rc4-git6 Console freezes

1. Hardware: HP Pavilion DV6150eu, AMD Turion 64 X2 TL-52, NVidia MCP51 
chipset, GeForce Go 7200
2. Problem: 
Console 'freezes' in random moments, showing no underscore cursor, nor GPM 
mouse cursor, it's not responding on network too. System works perfectly fine 
in graphics mode (with propertiary NVidia module loaded, those freezes are 
happening with and without it, so it's not the problem). Appeared on earlier 
kernels (for sure on 2.6.20-rc6, AFAIR I've tested 2.6.18 too), but it wasn't 
so annoying as it usually got to run KDM before freezing (not always) - on 
2.6.21-rc4-git6 it has freezed in:

[    0.000000] Linux version 2.6.21-rc4-git6 (wpk@...pie) (gcc version 4.2.0 
20070307 (prerelease) (PLD-Linux)) #2 SMP Thu Mar 22 19:09:09 CET 2007
[    0.000000] Command line: root=/dev/dm-0 resume2=swap:/dev/dm-0:0xd8098
(...)
[   12.596158] PCI: Found 0000:00:0d.0 [10de/0265] 000101 00
[   12.596176] 0000:00:0d.0: cannot adjust BAR0 (not I/O) <- this moment in ~ 
4/6 boot-ups
[   12.596234] 0000:00:0d.0: cannot adjust BAR1 (not I/O) 
[   12.596291] 0000:00:0d.0: cannot adjust BAR2 (not I/O) <- and one time here
[   12.596348] 0000:00:0d.0: cannot adjust BAR3 (not I/O)

After few tries, it boots up perfectly, passing that moment. 
Mentioned device is 
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
Though it might not be a problem with the device (as it happened before, in 
different moments, on earlier kernels).

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ