On 02/15/2013 09:54 AM, Konstantin Khlebnikov wrote:
> Borislav Petkov wrote:
>> On Thu, Feb 14, 2013 at 10:17:46AM -0700, Bjorn Helgaas wrote:
>>> It's pretty late for v3.8, but let me know if you think they're
>>> critical.
>>
>> Ok, I meant those:
>>
>> http://marc.info/?l=linux-kernel&m=1359845
On 03/04/2013 11:46 AM, Mihai Donțu wrote:
> Hi,
>
> I apologize in advance for posting on two lists at once and for not
> even being subscribed to e1000-devel.
>
> Ever since upgrading to 3.8.x, I'm unable to use my wired connection
> (e1000e - Intel Corporation 82579LM Gigabit) immediately afte
On 03/05/2013 01:16 AM, Bjorn Helgaas wrote:
> [+cc e1000-devel, Jeff, Bruce]
>
> On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov wrote:
>> On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote:
>>> So it looks Bjorn has taken most of them and the e1000e one will go
>>> through the e100
On 03/05/2013 10:58 AM, Borislav Petkov wrote:
> Rafael, what's the state of those patches here:
> https://lkml.org/lkml/2013/2/4/185, are they ready to be tested or you
> still have issues with them?
Note there is a resend version:
https://lkml.org/lkml/2013/2/25/3
with a note from Jeff Kirsher:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/05/2013 11:01 AM, Jeff Kirsher wrote:
> On Tue, 2013-03-05 at 10:42 +0100, Jiri Slaby wrote:
>>> The e1000e changes didn't get merged, did they? I don't see
>>> the following changes mentioned at
>>> h
On 03/12/2013 06:17 PM, Borislav Petkov wrote:
> On Mon, Mar 11, 2013 at 09:25:37PM +0100, Borislav Petkov wrote:
>> Yeah, it is already upstream. And yeah, it did trigger with it.
>>
>> $ git describe
>> v3.9-rc2-112-g7c6baa304b84
>>
>> But it somehow doesn't trigger with that same kernel anymore
On 03/19/2013 11:27 AM, Konstantin Khlebnikov wrote:
> Jiri Slaby wrote:
>> On 03/12/2013 06:17 PM, Borislav Petkov wrote:
>>> On Mon, Mar 11, 2013 at 09:25:37PM +0100, Borislav Petkov wrote:
>>>> Yeah, it is already upstream. And yeah, it did trigger with it.
>
On 03/29/2013 07:04 PM, Allan, Bruce W wrote:
>> -Original Message-
>> From: Jiri Slaby [mailto:jirisl...@gmail.com] On Behalf Of Jiri Slaby
>> Sent: Tuesday, March 19, 2013 5:23 AM
>> To: Konstantin Khlebnikov
>> Cc: Borislav Petkov; Kirsher, Jeffrey T; Ra
On 04/15/2013 05:29 PM, Jiri Slaby wrote:
> On 03/29/2013 07:04 PM, Allan, Bruce W wrote:
>>> -Original Message-
>>> From: Jiri Slaby [mailto:jirisl...@gmail.com] On Behalf Of Jiri Slaby
>>> Sent: Tuesday, March 19, 2013 5:23 AM
>>> To: Konsta
On 06/12/2013 11:29 PM, Konstantin Khlebnikov wrote:
> Jiri Slaby wrote:
>>> pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e] returns -2
>>> pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e] returns -2
>>> pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e]
On 06/12/2013 11:29 PM, Konstantin Khlebnikov wrote:
> Jiri Slaby wrote:
>> On 04/15/2013 05:29 PM, Jiri Slaby wrote:
>>> On 03/29/2013 07:04 PM, Allan, Bruce W wrote:
>>>>> -Original Message-
>>>>> From: Jiri Slaby [mailto:jirisl...@gmail.
Any ideas on this?
On 07/05/2013 10:24 PM, Jiri Slaby wrote:
> On 06/12/2013 11:29 PM, Konstantin Khlebnikov wrote:
>> Jiri Slaby wrote:
>>> On 04/15/2013 05:29 PM, Jiri Slaby wrote:
>>>> On 03/29/2013 07:04 PM, Allan, Bruce W wrote:
>>>>>> --
Hi,
after some combination of the following:
ip link set up dev eth0
ip link set down dev eth0
ip link set addr ... dev eth0
rmmod e1000e
modprobe e1000e
I got the BUG below. It looks like some path forgot to free_irq and the
next attempt to request_irq (genirq error) or to reset_irq (th
ort-
SERR- One other thing to try is to see if the same issue reproduces with the latest
> driver from e1000.sourceforge.net.
I currently cannot change anything on that machine. As soon as I can, I
will try the driver. Is it enough to test some up-to-date -next tree?
>> -Original Me
There were 2 omitted readb's used on an iomap space. eliminate them
by using ioread8 instead.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
Cc: Jeff Kirsher <[EMAIL PROTECTED]>
Cc: Jesse Brandeburg <[EMAIL PROTECTED]>
Cc: Bruce Allan <[EMAIL PROTECTED]>
Cc: PJ Wask
Hi,
during bootup, I got ton of these:
WARNING: at drivers/net/e1000e/ich8lan.c:413
e1000_acquire_swflag_ich8lan+0x43/0xf0()
Hardware name: To Be Filled By O.E.M.
e1000e mutex contention. Owned by pid -1
Modules linked in:
Pid: 1, comm: swapper Tainted: GW 2.6.28-rc7-mm1_64 #490
Call Tra
Hi,
4a865905f685eaefaedf6ade362323dc52aa703b
(PCI PM: Make pci_set_power_state() handle devices with no PM support)
breaks e1000 after being kexec'ed. These reverts fix the problem:
Revert "PCI PM: Make pci_set_power_state() handle devices with no PM
support"
Revert "PCI PM: Introduce __pc
On 04/23/2009 04:10 PM, Thadeu Lima de Souza Cascardo wrote:
> On Thu, Apr 23, 2009 at 03:36:43PM +0200, Jiri Slaby wrote:
>> Hi,
>>
>> 4a865905f685eaefaedf6ade362323dc52aa703b
>> (PCI PM: Make pci_set_power_state() handle devices with no PM support)
>> breaks
On 04/23/2009 05:15 PM, Rafael J. Wysocki wrote:
> On Thursday 23 April 2009, Jiri Slaby wrote:
>> 4a865905f685eaefaedf6ade362323dc52aa703b
>> (PCI PM: Make pci_set_power_state() handle devices with no PM support)
>> breaks e1000 after being kexec'ed. These reverts fix
On 04/23/2009 04:41 PM, Thadeu Lima de Souza Cascardo wrote:
> On Thu, Apr 23, 2009 at 04:30:01PM +0200, Jiri Slaby wrote:
>> On 04/23/2009 04:10 PM, Thadeu Lima de Souza Cascardo wrote:
>>> Have you tried b43fcd7dc7b, found in v2.6.30-rc3?
>> I've tried 2.6.30-rc3-
On 04/24/2009 06:09 PM, Rafael J. Wysocki wrote:
> My understanding is that the commit pointed to by Jiri caused a problem
> if the current mainline kernel was kexeced from an older kernel (2.6.27.x from
> openSUSE-11.1 in this particular case), because the older kernel didn't
> have the recent net
21 matches
Mail list logo
