On 2012-11-28 16:45, Riku Voipio wrote:
Is there any updates since early november? I have a Ivy bridge PC now
with PH8H77-V LE motherboard and 3570K cpu showing the mentioned
symptomps. I can work on bisecting the issue if nobody else is already
on it.
I have been running the kernel mentioned
On 2012-11-03 09:14, Jonathan Nieder wrote:
Could you try 3.3~rc6-1~experimental.1? (I expect it will also work
fine, but there's always a chance that we could get lucky and narrow
down the range by a lot.)
As you expected, two days without problems.
If it works ok, here are instructions
On 2012-10-24 02:39, Jonathan Nieder wrote:
Hi Per,
Per Foreby wrote:
Just to clear some confusion: In a previous comment you suggested trying
3.2.30-1 first (which seems to have been replaced by 3.2.32-1 a few days
ago).
So what should I try, and in what order? I have downloaded
On 2012-10-22 00:00, Jonathan Nieder wrote:
Oh, right --- I had forgotten. I think we should still move upstream
after the experiment with vesa, though, and just be sure to mention
which kernels were tried and what happened with each. Instructions
for reporting are here:
On 2012-10-23 22:10, Jonathan Nieder wrote:
Per Foreby wrote:
On 2012-10-22 00:00, Jonathan Nieder wrote:
Oh, right --- I had forgotten. I think we should still move upstream
after the experiment with vesa, though, and just be sure to mention
which kernels were tried and what happened
On 2012-10-23 23:45, Per Foreby wrote:
Thanks again for your help and patience. Could you try 3.3 next?
That would narrow down the search for the fix by quite a bit.
Just to clear some confusion: In a previous comment you suggested trying
3.2.30-1 first (which seems to have been replaced
On 2012-10-21 04:48, Jonathan Nieder wrote:
Per Foreby wrote:
Next thing to try is to blacklist the i915 module, but it doesn't seem to
work. This is what I did:
# echo blacklist i915 /etc/modprobe.d/i915-blacklist.conf
# depmod -ae -F /boot/System.map-3.2.0-3-amd64
# update
On 2012-10-21 21:02, Jonathan Nieder wrote:
Per Foreby wrote:
[22.177] (II) VESA(0): Total Memory: 1023 64KB banks (65472kB)
[22.200] (II) VESA(0): VESA VBE Total Mem: 65472 kB
Good, it looks like the vesa driver is loading instead of the i915
driver. Can you reproduce the bug
On 2012-10-20 00:39, Per Foreby wrote:
I noticed something strange with allocation of GPU RAM. In the old BIOS,
the default was 64 MB, but in the new bios, Auto was default. So I set
it explicitly to 64 MB. However, this is what the OS reports:
# lspci -vv
...
00:02.0 VGA compatible controller
New freeze after a few hours (vanilla kernel, 64 MB GPU Memory).
Next thing to try is to blacklist the i915 module, but it doesn't seem
to work. This is what I did:
# echo blacklist i915 /etc/modprobe.d/i915-blacklist.conf
# depmod -ae -F /boot/System.map-3.2.0-3-amd64
#
On 2012-10-18 12:37, Ingo wrote:
Per,
I am still watching this issue for interest (my case I do consider as
wrong BIOS setting which solved it for me).
Hmm, BIOS you said. I just check my BIOS version and found that the MB
was delivered with the initial BIOS version from February. Since then
On 2012-10-17 05:21, Jonathan Nieder wrote:
Per Foreby wrote:
However my computer has been running without any problems for 11
days, so whatever caused this bug seems to be fixed in the 3.5.5
kernel.
Drat. Ok.
To recap:
* Asus P8Z77-V LE.
* Newish system. Works fine under load (e.g
On 2012-10-18 00:02, Jonathan Nieder wrote:
Per Foreby wrote:
Correct, apart from the timing. It's been from a few hours to five days
between the freezes. But with very little interactive use during the
five days.
Right --- how much interactive use does it take?
Very little. I've had
On 2012-10-06 04:29, Per Foreby wrote:
New freeze. Last entry in the debug log was more than 10 minutes before
the freeze.
Now running 3.5-trunk-amd64 #1 SMP Debian 3.5.5-1~experimental.1 (still
with 256 MB iGPU Memory).
I was going to give it two weeks before reporting, but today we had
Ingo wrote:
With me all is still fine since 1 week, however that does not mean its
fixed. I am right now trying to stress my machine with high memory loads
and graphics to verify the workaround.
I have also tried the stress tactics, but it doesn't seem to have
anything to do with load.
On 2012-10-05 18:50, Jonathan Nieder wrote:
Javier Cantero wrote:
If it helps, I am using now linux-image-3.5-trunk-amd64
(3.5.2-1~experimental.1) kernel with no freezes since the change.
That's good to hear. Per, Ingo, does that work around trouble on
your machines, too?
I hade two
On 2012-10-05 23:53, Jonathan Nieder wrote:
Per Foreby wrote:
So far I'm running whith the default wheezy kernel but with the iGPU memory
set to 256 MB. My plan was to run with this setting, and if I had another
crash, try the experimental kernel.
That seems like a good plan.
New freeze
On 2012-10-04 13:30, Ingo wrote:
I just had a freeze, the first one sinc sunday. Actually while browsing
your comment :)
Jonathan: netconsole didn't log anything interesting.
These freezes happend most of the time when hitting a link in Iceweasel.
They are so severe that even the MoBo reset
Hi,
serial ports are rare these days, but I have netconsole running now
(logging to syslogd on my server).
So far the only log messages on the remote server are from netconsole
itself. Which leads me to this question: Are the default kernel
debugging options OK, or do I need to enable more
On 2012-10-01 19:52, Jonathan Nieder wrote:
So far the only log messages on the remote server are from netconsole
itself. Which leads me to this question: Are the default kernel debugging
options OK, or do I need to enable more debugging?
Does that mean it didn't capture the boot messages?
On 2012-10-01 23:29, Jonathan Nieder wrote:
Per Foreby wrote:
The debug logging from drm isn't forwarded via netconsole, so I suppose it
isn't supposed to?
Oh, that's because of the console_loglevel setting[1]. You can change
it by running dmesg -n 8 (or by adding the word debug
On 2012-10-02 00:45, Bjørn Mork wrote:
Per Foreby p...@foreby.se writes:
On 2012-10-01 23:29, Jonathan Nieder wrote:
Per Foreby wrote:
The debug logging from drm isn't forwarded via netconsole, so I suppose it
isn't supposed to?
Oh, that's because of the console_loglevel setting[1]. You
Package: src:linux
Version: 3.2.23-1
Severity: important
I'm using the built-in graphics (HD4000) on a i7 3770 Ivy Bridge
processor with Z77 chipset.
The computer has been runing just fine under heavy load (Folding at
Home) for some weeks, but a few days ago I started using it as a
One simple(?) questions before you close the bug:
- Which kernel should be upgraded to avoid this bug? dom0, domU or both?
/Per
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I'm also having this problem.
Dom0 running 2.6.26-2-xen-amd64, domU on 2.6.26-2-686-bigmem. All domU:s
are using all available processor cores.
I've been having problems on and off since the machine was installed
last summer. Typically it would be days or weeks between lockups.
I've been
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-5
Severity: important
On versions before 2.6.26 i have been getting lots of messages like
this:
eth0: too many iterations (6) in nv_nic_irq
Apart from filling up the log, the has been no noticable impact on the
system.
After upgrading to
Package: quota
Version: 3.16-4
Severity: normal
Had my first unclean shutdown on a computer with quotas enabled, and
quotacheck didn't work as expected on bootup. qoutacheck did run, but it
complained about not beeing able to rename the quota file. I got this
error message:
quotacheck: Cannot
Package: mirrors
Severity: wishlist
Submission-Type: new
Site: debian.lth.se
Aliases: ftp.ddg.lth.se
Type: leaf
Archive-architecture: ALL
Archive-ftp: /debian/
Archive-http: /debian/
IPv6: no
Mirrors-from: ftp.se.debian.org
Maintainer: Per Foreby [EMAIL PROTECTED]
Country: SE Sweden
On Sun, 7 Oct 2007, Simon Paillard wrote:
Maybe you can rename /debian/project/trace/linda.student.lth.se to
debian.lth.se
Done (and changed HOSTNAME in anonftpsync).
Don't know whether you use http://debian.org/mirrors/anonftpsync or not.
We do use anonftpsync.
We can provide you the
Package: lprng
Severity: wishlist
We need to use cups together with lprng since the lpr version in the
cupsys-bsd or lpr packages doesn't support -R or -Z. However, due to the
sysv support in lprng (lp, lpstat, cancel), there is a conflict with
cupsys-client.
I have so far solved our problem
30 matches
Mail list logo
