Processed: Re: [wheezy] e1000 vlan not working
Processing commands for cont...@bugs.debian.org: > tags 690956 - moreinfo Bug #690956 [src:linux] linux-image-3.2.0-3-686-pae: e1000 vlan not working Removed tag(s) moreinfo. > forwarded 690956 http://thread.gmane.org/gmane.linux.network/246918 Bug #690956 [src:linux] linux-image-3.2.0-3-686-pae: e1000 vlan not working Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.network/246918'. > quit Stopping processing here. Please contact me if you need assistance. -- 690956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690956 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.135104183817408.transcr...@bugs.debian.org
Bug#690956: [wheezy] e1000 vlan not working
tags 690956 - moreinfo forwarded 690956 http://thread.gmane.org/gmane.linux.network/246918 quit Andrey Jr. Melnikov wrote: > Version linux-image-3.2.0-3-686-pae-3.2.23-1~e1000.0 sucessfuly > builds and working: Thanks for the quick testing. Passed upstream so hopefully everyone using 3.2.y-based kernels will benefit from this soon. -- 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/20121024012348.GB5634@elie.Belkin
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
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 the following > packages: > > linux-image-3.2.0-4-amd64_3.2.30-1_amd64.deb > linux-image-3.2.0-4-amd64_3.2.32-1_amd64.deb > linux-image-3.3.0-trunk-amd64_3.3.6-1~experimental.1_amd64.deb > linux-image-3.4-trunk-amd64_3.4.4-1~experimental.1_amd64.deb Good question, thanks. 3.3.6 first. If it works, the newest 3.2.y kernel available would come next. If it doesn't work, 3.4.4 would come next. Jonathan -- 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/20121024003932.GA5634@elie.Belkin
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
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 by 3.2.32-1 a few days ago). So what should I try, and in what order? I have downloaded the following packages: linux-image-3.2.0-4-amd64_3.2.30-1_amd64.deb linux-image-3.2.0-4-amd64_3.2.32-1_amd64.deb linux-image-3.3.0-trunk-amd64_3.3.6-1~experimental.1_amd64.deb linux-image-3.4-trunk-amd64_3.4.4-1~experimental.1_amd64.deb /Per -- 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/50872639.2070...@foreby.se
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Since your upgrade involved replacing the old 2*2GB modules with 2*4GB new modules, rather than adding a new 4GB module to an old 4GB module, I agree that there isn't any reason to suspect incompatibility. Ben. -- Ben Hutchings Humour is the best antidote to reality. signature.asc Description: This is a digitally signed message part
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
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 with each. [...] https://bugs.freedesktop.org/show_bug.cgi?id=56333 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. The upstream comments are just what I exepcted, and what I'm used to in my 25 years as a system manager: don't bother reporting anything unless you're on the latest and greatest release or have paid support. Which is very understandable. I'll give the suggested kernels a try to narrow down the problem. And I'll stay on 64 MB graphics memory since that seems to trigger the problem faster. /Per -- 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/50870fe4.5090...@foreby.se
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
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 with each. [...] > https://bugs.freedesktop.org/show_bug.cgi?id=56333 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. Sincerely, Jonathan -- 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/20121023201000.GA1521@mannheim-rule.local
Bug#690956: [wheezy] e1000 vlan not working
Hi Jonathan Nieder! On Fri, Oct 19, 2012 at 10:23:15AM -0700, Jonathan Nieder wrote next: > reassign 690956 src:linux 3.2.23-1 > tags 690956 + upstream patch moreinfo > quit > > Hi Andrey, > > Andrey Melnikov wrote: > > > In wheezy i386 with e1000 driver 7.3.21-k8-NAPI vlan's not working > > without switching off rx-vlan-offload. > > Backport patch e1000: fix vlan processing regression > > commit 52f5509fe8ccb607ff9b84ad618f244262336475 from upstream. > > Please test the attached patch. (See [1] for instructions.) Version linux-image-3.2.0-3-686-pae-3.2.23-1~e1000.0 sucessfuly builds and working: # ethtool -k eth0 | grep vlan-offload rx-vlan-offload: on tx-vlan-offload: on [fixed] Please include in distribution. -- Best regards, TEMHOTA-RIPN aka MJA13-RIPE System Administrator of POST Ltd. mailto:temn...@kmv.ru -- 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/20121023175137.ge27...@kmv.ru
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
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: http://intellinuxgraphics.org/how_to_report_bug.html When doing so, please let us know the bug number so we can track it. I hate to sound like a broken record, but I still have no reason to believe the mtrr stuff is not a red herring. https://bugs.freedesktop.org/show_bug.cgi?id=56333 /Per -- 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/5086d959.8010...@foreby.se
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
>Messaggio originale >Da: b...@decadent.org.uk >Data: 23-ott-2012 3.02 >A: "asronche...@libero.it" >Cc: <684...@bugs.debian.org>, >Ogg: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it. > >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. > Hi, (i'm still using SSD + 4gB , atm) thanks for your reply. dmidecode contains the string "Product Name: K52Jc" I 've bought the 8gB on crucial.com. The site says that the hw they sell is 100% compatiple for my notebook. It works like this: i went on their website and then i entered "K52Jc" in the search form and then the site presents me all available and compatible upgrades for my notebook (K52Jc). It showed me various SSD disks and only one RAM upgrade: 8gB. According to dmidecode my mobo supports a maximum of 16gB of RAM, but checking on asus.com it seems that the notebook only support a max of 8gB. So i bought and SSD and the 8gB RAM. I've the 8gB RAM in front of me and i can read on one of the two: "4GB DDR3 - 1333 (PC3 10600) SODI" It is very similar to what i can see via dmidecode about the 4gB that are mounted at the moment on my notebook: 4gB on dmidecode: Handle 0x0041, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 16 GB Error Information Handle: Not Provided Number Of Devices: 4 Handle 0x0042, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: SODIMM Set: None Locator: DIMM0 Bank Locator: BANK 0 Type: DDR3 Type Detail: Synchronous Speed: 1067 MHz Manufacturer: Kinston Serial Number: 923C7BB9 Asset Tag: Unknown Part Number: ASU1333D3S9DR8/2G Rank: Unknown Handle 0x0043, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x000 Ending Address: 0x0007FFF Range Size: 2 GB Physical Device Handle: 0x0042 Memory Array Mapped Address Handle: 0x004B Partition Row Position: Unknown Interleave Position: 1 Interleaved Data Depth: 1 Handle 0x0044, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM1 Bank Locator: BANK 1 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: [Empty] Serial Number: [Empty] Asset Tag: Unknown Part Number: [Empty] Rank: Unknown Handle 0x0045, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: SODIMM Set: None Locator: DIMM2 Bank Locator: BANK 2 Type: DDR3 Type Detail: Synchronous Speed: 1067 MHz Manufacturer: Kinston Serial Number: 923CDEB1 Asset Tag: Unknown Part Number: ASU1333D3S9DR8/2G Rank: Unknown Handle 0x0046, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x000 Ending Address: 0x0007FFF Range Size: 2 GB Physical Device Handle: 0x0045 Memory Array Mapped Address Handle: 0x004B Partition Row Position: Unknown Interleave Position: 2 Interleaved Data Depth: 1 Handle 0x004A, DMI type 17, 28 bytes Memory Device Array Handle: 0x0041 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None L
