Bug#599161: TSC unstable clock problem, 35996 second time difference

2012-10-22 Thread Valentin Vidić
Here is a backtrace related to this problem, in case it helps:

[863910.147108] Clocksource tsc unstable (delta = -811538859723 ns)
[863910.149479] BUG: soft lockup - CPU#2 stuck for 32768s! [swapper:0]
[863910.149479] Modules linked in: hmac sha1_generic ipmi_devintf drbd 
lru_cache cn xen_evtchn xenfs ip6t_REJECT ipt_REJECT ip6t_LOG ipt_LOG 
xt_multiport xt_tcpudp xt_comment ip6table_filter ip6_tables iptable_filter 
ip_tables x_tables bridge bonding 8021q garp stp loop snd_pcm snd_timer radeon 
ttm snd drm_kms_helper soundcore drm snd_page_alloc i5000_edac psmouse 
i2c_algo_bit hpilo pcspkr ipmi_si edac_core evdev ipmi_msghandler rng_core 
serio_raw i2c_core i5k_amb hpwdt container shpchp pci_hotplug processor 
acpi_processor button ext3 jbd mbcache dm_mod usbhid hid sg sr_mod cdrom 
ata_generic uhci_hcd ata_piix ehci_hcd libata usbcore nls_base bnx2 hpsa cciss 
scsi_mod thermal thermal_sys [last unloaded: scsi_wait_scan]
[863910.149479] CPU 2:
[863910.149479] Modules linked in: hmac sha1_generic ipmi_devintf drbd 
lru_cache cn xen_evtchn xenfs ip6t_REJECT ipt_REJECT ip6t_LOG ipt_LOG 
xt_multiport xt_tcpudp xt_comment ip6table_filter ip6_tables iptable_filter 
ip_tables x_tables bridge bonding 8021q garp stp loop snd_pcm snd_timer radeon 
ttm snd drm_kms_helper soundcore drm snd_page_alloc i5000_edac psmouse 
i2c_algo_bit hpilo pcspkr ipmi_si edac_core evdev ipmi_msghandler rng_core 
serio_raw i2c_core i5k_amb hpwdt container shpchp pci_hotplug processor 
acpi_processor button ext3 jbd mbcache dm_mod usbhid hid sg sr_mod cdrom 
ata_generic uhci_hcd ata_piix ehci_hcd libata usbcore nls_base bnx2 hpsa cciss 
scsi_mod thermal thermal_sys [last unloaded: scsi_wait_scan]
[863910.149479] Pid: 0, comm: swapper Not tainted 2.6.32-5-xen-amd64 #1 
ProLiant DL360 G5
[863910.149479] RIP: e030:[8100922a]  [8100922a] 
hypercall_page+0x22a/0x1001
[863910.149479] RSP: e02b:8800034f4de8  EFLAGS: 0246
[863910.149479] RAX: 0004 RBX: 8800034f4ea0 RCX: 
8100922a
[863910.149479] RDX: 8800034f4ea0 RSI:  RDI: 

[863910.149479] RBP: 88001fd88000 R08: 00d9 R09: 
00fa
[863910.149479] R10: 88001fd59fd8 R11: 0246 R12: 
8800023128f8
[863910.149479] R13: 812cda42 R14: 0100 R15: 
88001fd59fd8
[863910.149479] FS:  7f75890ff700() GS:8800034f1000() 
knlGS:
[863910.149479] CS:  e033 DS: 002b ES: 002b CR0: 8005003b
[863910.149479] CR2: 7f7588cb45f0 CR3: 01001000 CR4: 
2660
[863910.149479] DR0:  DR1:  DR2: 

[863910.149479] DR3:  DR6: 0ff0 DR7: 
0400
[863910.149479] Call Trace:
[863910.149479]  IRQ  [8100e635] ? xen_force_evtchn_callback+0x9/0xa
[863910.149479]  [8100ecf2] ? check_events+0x12/0x20
[863910.149479]  [8100ec99] ? xen_irq_enable_direct_end+0x0/0x7
[863910.149479]  [8105b6e0] ? run_timer_softirq+0x196/0x268
[863910.149479]  [81054dbf] ? __do_softirq+0xdd/0x1a6
[863910.149479]  [811f2b93] ? __xen_evtchn_do_upcall+0x245/0x28d
[863910.149479]  [81012cac] ? call_softirq+0x1c/0x30
[863910.149479]  [8101422b] ? do_softirq+0x3f/0x7c
[863910.149479]  [81054c2f] ? irq_exit+0x36/0x76
[863910.149479]  [811f3384] ? xen_evtchn_do_upcall+0x33/0x42
[863910.149479]  [81012cfe] ? xen_do_hypervisor_callback+0x1e/0x30
[863910.149479]  EOI  [810093aa] ? hypercall_page+0x3aa/0x1001
[863910.149479]  [810093aa] ? hypercall_page+0x3aa/0x1001
[863910.149479]  [8100e6b3] ? xen_safe_halt+0xc/0x15
[863910.149479]  [8100bfc7] ? xen_idle+0x37/0x40
[863910.149479]  [81010e97] ? cpu_idle+0xa2/0xda
[863910.149479]  [8100ec99] ? xen_irq_enable_direct_end+0x0/0x7
[863910.149479]  [81302947] ? cpu_bringup+0x6d/0x72

-- 
Valentin


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121022075113.gd2...@gavran.carpriv.carnet.hr



Bug#691167: linux-image-3.5-trunk-amd64: please enable CONFIG_UPROBES

2012-10-22 Thread Timo Juhani Lindfors
Package: src:linux
Version: 3.5.5-1~experimental.1
Severity: wishlist

CONFIG_UPROBES lets systemtap place probes on user code just like
kprobes lets it to do with kernel code. Support was merged mainline in
3.5. Please consider enabling this option.


commit 654443e20dfc0617231f28a07c96a979ee1a0239
Merge: 2c01e7b 9cba26e
Author: Linus Torvalds torva...@linux-foundation.org
Date:   Thu May 24 11:39:34 2012 -0700

Merge branch 'perf-uprobes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Pull user-space probe instrumentation from Ingo Molnar:
 The uprobes code originates from SystemTap and has been used for
 years
  in Fedora and RHEL kernels.  This version is much rewritten,
 reviews
  from PeterZ, Oleg and myself shaped the end result.

  This tree includes uprobes support in 'perf probe' - but SystemTap
  (and other tools) can take advantage of user probe points as well.

  Sample usage of uprobes via perf, for example to profile malloc()
  calls without modifying user-space binaries.

  First boot a new kernel with CONFIG_UPROBE_EVENT=y enabled.

  If you don't know which function you want to probe you can pick
  one
  from 'perf top' or can get a list all functions that can be probed
  within libc (binaries can be specified as well):

$ perf probe -F -x /lib/libc.so.6




-- Package-specific info:
** Version:
Linux version 3.5-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-10) ) #1 SMP Debian 3.5.5-1~experimental.1

** Command line:
root=UUID=ee66b917-5151-4a4b-944a-99385b7d4d62 ro init=/bin/systemd 

** Not tainted

** Kernel log:
[0.022119] Grant table initialized
[0.022119] dummy: 
[0.022119] NET: Registered protocol family 16
[0.022119] PCI: setting up Xen PCI frontend stub
[0.022119] PCI: pci_cache_line_size set to 64 bytes
[0.022119] bio: create slab bio-0 at 0
[0.024052] ACPI: Interpreter disabled.
[0.024068] xen/balloon: Initialising balloon driver.
[0.024068] xen-balloon: Initialising balloon driver.
[0.024068] vgaarb: loaded
[0.024068] PCI: System does not support PCI
[0.024068] PCI: System does not support PCI
[0.024147] Switching to clocksource xen
[0.025496] pnp: PnP ACPI: disabled
[0.028530] NET: Registered protocol family 2
[0.028660] IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
[0.029267] TCP established hash table entries: 131072 (order: 9, 2097152 
bytes)
[0.029903] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[0.030169] TCP: Hash tables configured (established 131072 bind 65536)
[0.030178] TCP: reno registered
[0.030196] UDP hash table entries: 512 (order: 2, 16384 bytes)
[0.030208] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[0.030339] NET: Registered protocol family 1
[0.030353] PCI: CLS 0 bytes, default 64
[0.030386] Unpacking initramfs...
[0.061906] Freeing initrd memory: 30480k freed
[0.070084] platform rtc_cmos: registered platform RTC device (no PNP 
device found)
[0.070481] audit: initializing netlink socket (disabled)
[0.070500] type=2000 audit(1350907337.850:1): initialized
[0.080465] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[0.080779] VFS: Disk quotas dquot_6.5.2
[0.080806] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[0.080871] msgmni has been set to 1989
[0.081088] alg: No test for stdrng (krng)
[0.081141] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
252)
[0.081149] io scheduler noop registered
[0.081151] io scheduler deadline registered
[0.081176] io scheduler cfq registered (default)
[0.081219] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[0.081236] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[0.081240] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.197288] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.197583] Linux agpgart interface v0.103
[0.197659] i8042: PNP: No PS/2 controller found. Probing ports directly.
[0.198468] i8042: No controller found
[0.198627] mousedev: PS/2 mouse device common for all mice
[0.258333] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[0.258461] rtc_cmos: probe of rtc_cmos failed with error -38
[0.258535] drop_monitor: Initializing network drop monitor service
[0.258598] TCP: cubic registered
[0.258679] NET: Registered protocol family 10
[0.258835] mip6: Mobile IPv6
[0.258840] NET: Registered protocol family 17
[0.258852] Key type dns_resolver registered
[0.259007] PM: Hibernation image not present or could not be loaded.
[0.259013] registered taskstats version 1
[0.259030] XENBUS: Device with no driver: device/vbd/51712
[0.259033] XENBUS: Device with no driver: device/vif/0
[0.259120] 

Processed: blank

2012-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 block 690404 by 691167
Bug #690404 [systemtap] Please provide a newer version
690404 was blocked by: 688731 689278
690404 was not blocking any bugs.
Added blocking bug(s) of 690404: 691167
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
690404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13509121534876.transcr...@bugs.debian.org



Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

2012-10-22 Thread Ben Hutchings
On Sun, 2012-10-21 at 16:25 +0200, Ingo wrote:
 Am 21.10.2012 14:20, schrieb Per Foreby:
 
  Note that this is 1023 memory banks, not 1024, so it's not exactly 64 MB
  (65536 kB). Maybe the reason why it almost works with 256 MB is that the
  kernel always thinks that we have exactly 256 MB but the Mobo supplies
  one memory bank less. Just a theory..
 
 Per, me came another idea. Some postings up Ben Hutching stated:
 
 The driver calls ioremap_wc() which will enable write-combining through
 the PAT in recent processors.

 Isn't this address translation how I/O remapping (IOMMU) also called
 VT-d works?
[...]

PAT is a feature of the ordinary MMU, not an IOMMU.

(The last I heard, Intel's integrated GPUs were totally incompatible
with VT-d (partly because they are not normal PCIe devices).  Linux
therefore doesn't allow them to be in a VT-d remapping domain.)

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part


Processed: tagging 687567

2012-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 687567 + pending
Bug #687567 [linux-2.6] linux-image-3.2.0-2-amd64: Patch to support D-Link 
DUB-E100 variant
Ignoring request to alter tags of bug #687567 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
687567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135091363215793.transcr...@bugs.debian.org



Processed: tagging 689416

2012-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 689416 + pending
Bug #689416 [src:linux] Nonexistant files are asked for on Intel Centrino 
Ultimate-N 6300 (802.11 a/b/g/n 3X3) Half Mini Card
Ignoring request to alter tags of bug #689416 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
689416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135091363915866.transcr...@bugs.debian.org



Processed: tagging 661379

2012-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 661379 + pending
Bug #661379 [linux] Missing hid_logitech_dj module in D-I kernel
Ignoring request to alter tags of bug #661379 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
661379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135091364215882.transcr...@bugs.debian.org



Processed: tagging 588200

2012-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 588200 + pending
Bug #588200 [src:linux] linux-2.6: Please enable CONFIG_PROC_EVENTS
Ignoring request to alter tags of bug #588200 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
588200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135091364515904.transcr...@bugs.debian.org



Incomplete upload found in Debian upload queue

2012-10-22 Thread Debian FTP Masters
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
  linux_3.2.32-1.debian.tar.xz
  linux_3.2.32-1.dsc
  linux_3.2.32.orig.tar.xz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.

If no .changes file arrives within 23:27:43, the files will be deleted.

If you didn't upload those files, please just ignore this message.

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1tqiia-0004yp...@franck.debian.org



Fixing the commit hook

2012-10-22 Thread Ben Hutchings
Committing to SVN currently produces the following errors:

---
Committed revision 19453.

Warning: post-commit hook failed (exit code 255) with output:
Traceback (most recent call last):
  File /svn/kernel/bin/ciabot_svn.py, line 221, in module
SvnClient(sys.argv[1], sys.argv[2], config).main()
  File /svn/kernel/bin/ciabot_svn.py, line 126, in main
/message)
  File /svn/kernel/bin/ciabot_svn.py, line 110, in deliver
xmlrpclib.ServerProxy(server).hub.deliver(message)
  File /srv/svn.debian.org/svn/kernel/bin/xmlrpclib.py, line 986, in __call__
return self.__send(self.__name, args)
  File /srv/svn.debian.org/svn/kernel/bin/xmlrpclib.py, line 1239, in 
__request
verbose=self.__verbose
  File /srv/svn.debian.org/svn/kernel/bin/xmlrpclib.py, line 1027, in request
headers
xmlrpclib.ProtocolError: ProtocolError for cia.vc/RPC2: 404 Not Found
/srv/home/users/dannf/bts-mark-pending:3: DeprecationWarning: The popen2 module 
is deprecated.  Use the subprocess module.
  import popen2, sys, re, os
SOAP FAULT while talking to http://dam.homelinux.net:9418/
FAULT MESSAGE: Repository kernel is unknown

SOAP FAULT while talking to http://colleen.colgarra.priv.at:8080/
FAULT MESSAGE: Repository kernel is unknown

SOAP FAULT while talking to http://abhean.mine.nu:9418/
FAULT MESSAGE: Repository kernel is unknown
Unable to complete notification. All servers failed
---

I'm aware that CIA.vc went away and we need to use something else such
as FBI for IRC notification.  However it looks like there's some kind of
problem with other notifications as well.

Can someone volunteer to try to fix this?

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part


Processing of linux_3.2.32-1_multi.changes

2012-10-22 Thread Debian FTP Masters
linux_3.2.32-1_multi.changes uploaded successfully to localhost
along with the files:
  linux_3.2.32-1.dsc
  linux_3.2.32.orig.tar.xz
  linux_3.2.32-1.debian.tar.xz
  linux-support-3.2.0-4_3.2.32-1_all.deb
  linux-doc-3.2_3.2.32-1_all.deb
  linux-manual-3.2_3.2.32-1_all.deb
  linux-source-3.2_3.2.32-1_all.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1tqilo-0003ls...@franck.debian.org



Re: Uploading linux (3.2.32-1)

2012-10-22 Thread Ben Hutchings
On Fri, 2012-10-19 at 14:44 +0100, Ben Hutchings wrote:
 I intend to upload linux version 3.2.32-1 to unstable this weekend.
 This brings in various fixes from stable updates 3.2.{31,32} and
 elsewhere, and should fix the previous FTBFS on mips{,el}.

This is now done.

 (Also, I intend to upload version 3.6.2-1 or .3-1 to experimental.)

Not done, but I'm building 3.6.3-1 and hope to be able to upload
tonight.

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part


Re: Fixing the commit hook

2012-10-22 Thread maximilian attems
On Mon, Oct 22, 2012 at 03:29:16PM +0100, Ben Hutchings wrote:
   import popen2, sys, re, os
 SOAP FAULT while talking to http://dam.homelinux.net:9418/
 FAULT MESSAGE: Repository kernel is unknown
 
 SOAP FAULT while talking to http://colleen.colgarra.priv.at:8080/
 FAULT MESSAGE: Repository kernel is unknown
 
 SOAP FAULT while talking to http://abhean.mine.nu:9418/
 FAULT MESSAGE: Repository kernel is unknown
 Unable to complete notification. All servers failed
 ---
 
 I'm aware that CIA.vc went away and we need to use something else such
 as FBI for IRC notification.  However it looks like there's some kind of
 problem with other notifications as well.
 
 Can someone volunteer to try to fix this?

sorry for having done the first step without telling those guys.
i'll email them shortly so that we get this kgb properly wired up.

best,
max


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121022144557.gc31...@vostochny.stro.at



[bts-link] source package linux-2.6

2012-10-22 Thread bts-link-upstream
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #575648 (http://bugs.debian.org/575648)
# Bug title: Lots of udevd --daemon running 100% CPU all the time.
#  * https://bugs.freedesktop.org/show_bug.cgi?id=27941
#  * remote status changed: NEEDINFO - REOPENED
usertags 575648 - status-NEEDINFO
usertags 575648 + status-REOPENED

# remote status report for #575648 (http://bugs.debian.org/575648)
# Bug title: Lots of udevd --daemon running 100% CPU all the time.
#  * https://bugs.freedesktop.org/show_bug.cgi?id=27941
#  * remote status changed: NEEDINFO - REOPENED
usertags 575648 - status-NEEDINFO
usertags 575648 + status-REOPENED

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20121022163320.7386.22266.btsl...@sonntag.debian.org



Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev 12

2012-10-22 Thread Michael Chan
On Mon, 2012-10-22 at 10:52 +0300, Teodor MICU wrote:
 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
 Gigabit Ethernet (rev 11)

It is 5708 B1, and due to some hardware limitations, ethtool initiated
WoL is not supported.  Here's the code fragment in bnx2.c:

if ((CHIP_ID(bp) == CHIP_ID_5708_A0) ||
(CHIP_ID(bp) == CHIP_ID_5708_B0) ||
(CHIP_ID(bp) == CHIP_ID_5708_B1) ||
!(REG_RD(bp, BNX2_PCI_CONFIG_3)  BNX2_PCI_CONFIG_3_VAUX_PRESET)) {
bp-flags |= BNX2_FLAG_NO_WOL;
bp-wol = 0;
}


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1350946459.8764.145.ca...@ltirv-mchan1.corp.ad.broadcom.com



Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-22 Thread asronche...@libero.it
Hi,

`uptime ` is:
 02:47:34 up 6 days,  6:23,

and still no problem here.

the combination SSD + 4gB RAM is working great.

The only thing i changed was in /etc/fstab, i used noatime,discard  instead 
of default in the options column for the /home partition (ext4).

next test will start in the next days, with SSD + 8gB.

I think that probably the problem resides in how my installation is handling 
the 8gB ram.

Are there some special settings that i need to configure when switching from a 
4gB ram to 8gB ram?

ciao
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/33510800.4837651350953701205.JavaMail.defaultUser@defaultHost



Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-22 Thread Ben Hutchings
On Tue, 2012-10-23 at 02:55 +0200, asronche...@libero.it wrote:
 Hi,
 
 `uptime ` is:
  02:47:34 up 6 days,  6:23,
 
 and still no problem here.
 
 the combination SSD + 4gB RAM is working great.
 
 The only thing i changed was in /etc/fstab, i used noatime,discard  instead 
 of default in the options column for the /home partition (ext4).
 
 next test will start in the next days, with SSD + 8gB.
 
 I think that probably the problem resides in how my installation is handling 
 the 8gB ram.
 
 Are there some special settings that i need to configure when switching from 
 a 
 4gB ram to 8gB ram?

No change should be necessary.

One thing I should have thought of earlier is that a pair of different
memory modules might not be reliable.  In my personal experience, two
different modules will often work, but it's generally recommended to use
a matched set.

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part


Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev 12

2012-10-22 Thread Ben Hutchings
On Mon, 2012-10-22 at 15:54 -0700, Michael Chan wrote:
 On Mon, 2012-10-22 at 10:52 +0300, Teodor MICU wrote:
  08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
  Gigabit Ethernet (rev 11)
 
 It is 5708 B1, and due to some hardware limitations, ethtool initiated
 WoL is not supported.
[...]

Well we knew that much!  Is the problem that the system firmware 'owns'
the WoL control registers so the host can't safely change them?  Is it
possible to *read* the WoL configuration, if not to change it?

(If even that is not possible, the correct thing to do might be for
ETHTOOL_GWOL to return 'don't know' (EOPNOTSUPP) for this device.  But
since ethtool_ops::get_wol (and various other operations) can't return
an error, that would require you to define a separate instance of
ethtool_ops with get_wol = NULL.  I should look at fixing that...)

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part


Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev 12

2012-10-22 Thread Michael Chan
On Tue, 2012-10-23 at 02:45 +0100, Ben Hutchings wrote: 
 Well we knew that much!  Is the problem that the system firmware 'owns'
 the WoL control registers so the host can't safely change them?  Is it
 possible to *read* the WoL configuration, if not to change it? 

It's a hardware problem and I don't understand all the details.  There
is an internal PCIX to PCIE bridge on this chip and it gates the NIC's
PME event.  During S5 reset, the bridge gets reset by the BIOS and the
WoL setting done by the driver will no longer work.  Newer chip revs
have fixed the problem in hardware.

The driver reads the pre-boot WoL setting from NVRAM and it becomes the
ethtool WoL default setting.  Apparently, it is also not working in this
case.  I know that it doesn't work on some LOM designs as the setting is
actually in BIOS NVRAM as opposed to NIC NVRAM.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1350958687.8764.170.ca...@ltirv-mchan1.corp.ad.broadcom.com