linux-kernel - Re: Regression: sky2 kernel between 3.1 and 3.2.1 (last known good 3.0.9)

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <4F1999DC.3050308@majjas.com>
Date:	Fri, 20 Jan 2012 11:44:12 -0500
From:	Michael Breuer <mbreuer@...jas.com>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	Jarek Poplawski <jarkao2@...il.com>,
	David Miller <davem@...emloft.net>,
	Stephen Hemminger <shemminger@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Regression: sky2 kernel between 3.1 and 3.2.1 (last known good
 3.0.9)

On 1/20/2012 11:26 AM, Stephen Hemminger wrote:
> On Mon, 16 Jan 2012 11:39:13 -0500
> Michael Breuer<mbreuer@...jas.com>  wrote:
>
>> Synopsis:
>>
>> Receiving DMAR and other errors after approximately three days of
>> uptime. The symptoms exactly match errors seen and then fixed around
>> 2.6.32.4.
>>
>> While the system remains unaffected for too long to do a bisect, I was
>> able to confirm that the problem exists in the 3.1 stable branch (I
>> jumped from 3.0 to 3.2 when 3.2. was released).
>>
>> For now I reverted to the sky2.c from 3.0.9 and am running the rest of
>> the kernel from 3.1.2, but won't be certain that this works until later
>> in the week.
>>
>> Note that 20 seconds prior to the log extract below were DHCP renewal
>> attempts on eth1, the issue below was on eth0. Not sure it's relevant,
>> however back in 2010 a preceding DHCP event did turn out to be relevant
>> to the manifestation of the bug.
>>
>> The 3.2.1-dirty I'm running is from git with a single local patch - for
>> sidewinder force-feedback support (shouldn't be relevant to the sky2 issue).
>>
>> Log extract:
>>
>> Jan 16 05:49:46 mail kernel: [198230.628919] DRHD: handling fault status
>> reg 2
>> [snip]
>>
>>
>>
>
> Which exact chip version is this?
>    dmesg | grep sky2
>    lspci
[    9.927143] sky2: driver version 1.29
[    9.927166] sky2 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    9.927177] sky2 0000:06:00.0: setting latency timer to 64
[    9.927254] sky2 0000:06:00.0: Yukon-2 EC Ultra chip revision 3
[    9.927339] sky2 0000:06:00.0: irq 71 for MSI/MSI-X
[    9.927562] sky2 0000:06:00.0: eth0: addr 00:26:18:00:1c:3b
[    9.927578] sky2 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    9.927586] sky2 0000:04:00.0: setting latency timer to 64
[    9.927640] sky2 0000:04:00.0: Yukon-2 EC Ultra chip revision 3
[    9.927718] sky2 0000:04:00.0: irq 72 for MSI/MSI-X
[    9.927856] sky2 0000:04:00.0: eth1: addr 00:26:18:00:1c:3a
[   23.468135] sky2 0000:06:00.0: eth0: enabling interface
[   25.709668] sky2 0000:04:00.0: eth1: enabling interface
[   25.981841] sky2 0000:06:00.0: eth0: Link is up at 1000 Mbps, full 
duplex, fl    ow control both
[   27.418742] sky2 0000:04:00.0: eth1: Link is up at 100 Mbps, full 
duplex, flo    w control rx

04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E 
Gigabit Ethernet Controller (rev 14)
05:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II 
Controller (rev b2)
06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E 
Gigabit Ethernet Controller (rev 14)

--
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/