Hi!
I'm not shure but perhaps it isn't an XFS Bug.
Here is what i find out:
We've about 300 servers at the momentan and 5 of them are "old" Intel
Pentium 4 Machines with a DFI PM-12 Mainboard with VIA chipset. It only
happens on THESE Machines. Other P4 Machines with a Tyan Mainboard or a
I saw cpuhotplug operations on 32-bit mode of xeon-64bit processors
crashing the system. This happens on latest 2.6.20-rc5 kernel also. Same
(i386 cpuhotplug code) runs fine on xeon-32bit processors.
Steps to reproduce.
echo 0 > /sys/devices/system/cpu/cpu6/online
echo 1 >
On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>On Thu, Jan 18, 2007 at 06:00:40PM -0700, dann frazier wrote:
>Ah, think I see the problem now:
>
>--- kernel-source-2.4.27.orig/fs/smbfs/proc.c 2007-01-19 17:53:57.247695476
>-0700
>+++
My patch is based on my new idea to Linux swap subsystem, you can find more in
Documentation/vm_pps.txt which isn't only patch illustration but also file
changelog. In brief, SwapDaemon should scan and reclaim pages on
UserSpace::vmalist other than current zone::active/inactive. The change will
Hi folks,
It's time to start kicking off the 2007 Kernel Summit planning
process. This year, the Kernel Summit will be held in Cambridge,
England, at the DeVere University Arms Hotel, September 5-6 (with a
welcome reception on the 4th). The decision to move the Kernel Summit
to England
> "Tony" == Tony Foiani <[EMAIL PROTECTED]> writes:
Tony> How fast is your Ethernet port? 100Mbps or 95.37Mbps?
> "Jan" == Jan Engelhardt <[EMAIL PROTECTED]> writes:
Jan> Same lie like with harddrives. It's around 80, not 100. But it
Jan> depends on how you look at it. 80 for Layer3,
On Sun, Jan 21, 2007 at 12:29:51PM -0500, Justin Piszcz wrote:
>
>
> On Sun, 21 Jan 2007, Justin Piszcz wrote:
>
> >
> >
> > >
> > > Good luck,
> > > Jurriaan
> > > --
> > > > What does ELF stand for (in respect to Linux?)
> > > ELF is the first rock group that Ronnie James Dio performed
On Sun, Jan 21, 2007 at 01:30:15PM +0100, Stefan Priebe - FH wrote:
> Hello!
>
> I've 3 Servers which works wonderful with 2.6.16.X (also testet the
> latest 2.6.16.37)
>
> but with 2.6.18.6 i get these errors:
[ EIP is at xfs_bmap_add_extent_hole_delay+0x58d/0x59b ]
[ EIP is at
Douglas Gilbert wrote:
> Boaz Harrosh wrote:
>> - Introduce a new enum dma_data_direction data_dir member in struct request.
>> and remove the RW bit from request->cmd_flag
>> - Add new API to query request direction.
>> - Adjust existing API and implementation.
>> - Cleanup wrong use of
On Mon, Jan 22, 2007 at 01:21:28AM +0200, Boaz Harrosh wrote:
> - Introduce a new enum dma_data_direction data_dir member in struct request.
> and remove the RW bit from request->cmd_flag
Some architecture use 'enum dma_data_direction' and some 'int
dma_data_direction'. The consensus was to
Chris Rankin wrote:
> Hi,
>
> This patch writes the USB vendor and product IDs into the
> /sys/class/input/inputX/id/ files, so
> that udev can find them. A rule like this does the trick for me:
>
> KERNEL="event*", SYSFS{../id/vendor}=="2040", SYSFS{../id/product}=="9301",
>
Hi.
On Mon, 2007-01-22 at 16:16 +1100, Jean-Marc Valin wrote:
> >> I just encountered the following oops and general protection fault
> >> trying to suspend/resume my laptop. I've got a Dell D820 laptop with a 2
> >> GHz Core 2 Duo CPU. It usually suspends/resumes fine but not always. The
> >>
>> I just encountered the following oops and general protection fault
>> trying to suspend/resume my laptop. I've got a Dell D820 laptop with a 2
>> GHz Core 2 Duo CPU. It usually suspends/resumes fine but not always. The
>> relevant errors are below but the full dmesg log is at
>>
On 2007.01.18 23:16:51 +, Pavel Machek wrote:
> Hi!
>
> > > > Especially the PCI video_state trick finally got me a working resume on
> > > > 2.6.19-ck2 r128 Rage Mobility M4 AGP *WITH*(!) fully enabled and working
> > > > (and keeping working!) DRI (3D).
> > >
> > > Can we get whitelist
find attached a patch to update the rtc documentation a bit. i fixed a typo,
added a bunch of helpful pointers (thanks to Paul Mundt and the linux/sh guys
for holding my hand :D), and improved a bunch of the error messages in the
test program
hope this helps
-mike
pgprYOnYyYAXF.pgp
From: Robert P. J. Day <[EMAIL PROTECTED]>
Fix a number of kernel-doc entries for header files in
include/linux by making sure they begin with the appropriate '/**'
notation and use @var notation.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
Signed-off-by: Randy Dunlap <[EMAIL
i'm not looking to submit this as that'll be done with the rest of the
Blackfin stuff, i'm just looking for feedback from some bored people who know
the RTC framework :)
the attached driver implements full functionality for the Blackfin on-chip RTC
using the new RTC framework ... anyone mind
My initial idea was to execute only block device resume on the separate
thread, as it take almost 80% of the total device resume time ( I did
detailed profile of each device resume through rdtsc() counter) and rest
of them takes less than 20% in total( each device ( including char and
net)on its
Hello,
ris wrote:
and dmesg
Please report...
1. 'vmstat 1' result during file copy (w/ cpu 100%)
2. 'dmesg' result after file copy
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Randy Dunlap wrote:
On Sun, 21 Jan 2007 15:07:37 -0600 Jay Cliburn wrote:
[snip]
+ value = ioread16(hw->hw_addr + REG_PCIE_CAP_LIST);
+ return ((value & 0xFF00) == 0x6C00) ? 0 : 1;
Are there defines or enums for these?
Fewer magic numbers would be nice/helpful/readable.
[snip]
Hi.
On Mon, 2007-01-22 at 13:34 +1100, Jean-Marc Valin wrote:
> Hi,
>
> I just encountered the following oops and general protection fault
> trying to suspend/resume my laptop. I've got a Dell D820 laptop with a 2
> GHz Core 2 Duo CPU. It usually suspends/resumes fine but not always. The
>
Hi,
I just encountered the following oops and general protection fault
trying to suspend/resume my laptop. I've got a Dell D820 laptop with a 2
GHz Core 2 Duo CPU. It usually suspends/resumes fine but not always. The
relevant errors are below but the full dmesg log is at
Paolo Ornati wrote:
I don't know. It's a two years old ST380817AS.
# smartctl -a -d ata /dev/sda
smartctl version 5.36 [x86_64-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate
Hello,
Chr wrote:
Ok, you won't believe this... I opened my case and rewired my drives...
And guess what, my second (aka the "good") HDD is now failing!
I guess, my mainboard has a (but maybe two, or three :( ) "bad" sata-port(s)!
Or, you have power related problem. Try to rewire the
On Sun, 21 Jan 2007 15:07:37 -0600 Jay Cliburn wrote:
> This patch contains auxiliary C files for the Attansic L1 gigabit ethernet
> adapter driver.
>
> Signed-off-by: Jay Cliburn <[EMAIL PROTECTED]>
> Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
> ---
>
> atl1_ethtool.c | 436
Hi Pavel,
The /proc// approach doesn't have these demerits, and it
has an advantage that users can change the bitmask of any process
at anytime.
>>>
>>>Well... not sure if it is advantage.
>>
>>For example, consider the following case:
>> a process forks many children and system
On Thu, 18 Jan 2007 20:28:49 +0900 (JST), Atsushi Nemoto <[EMAIL PROTECTED]>
wrote:
> The commit was to fix spi_busnum_to_master(). Here is a patch fixes
> this function in other way, just searching children list of
> class_device.
Here is a revised version. The children list of
Jan Engelhardt <[EMAIL PROTECTED]> writes:
> Bleh. Except for storage, base 1024 was used for almost everything
> I remember. 4 MB memory meant 4096 KB, and that's still the case today.
> Most likely the same for transfer rates.
Nope, transfer rates were initially 1000-based: 9.6 kbps = 9600
At Sun, 21 Jan 2007 19:36:27 -0500,
Kyle Moffett wrote:
>
> On Jan 21, 2007, at 18:34:56, David Wagner wrote:
> > [1] In comparison, suidperl was designed to be installed setuid-
> > root, and it takes special precautions to be safe in this usage.
> > (And even it has had some security
Hello everyone,
This is a long thread about O_DIRECT surprisingly without a single
bugreport in it, that's a good sign that O_DIRECT is starting to work
well in 2.6 too ;)
On Fri, Jan 12, 2007 at 02:47:48PM -0800, Andrew Morton wrote:
> On Fri, 12 Jan 2007 15:35:09 -0700
> Erik Andersen <[EMAIL
"Horst H. von Brand" <[EMAIL PROTECTED]> writes:
> Junio C Hamano <[EMAIL PROTECTED]> wrote:
>> Willy Tarreau <[EMAIL PROTECTED]> writes:
>> > Anything you can do to make tester's life easier will always slightly
>> > increase the number of testers.
>> > ...
>> > Pre-release tar.gz and rpms
Greetings;
I am attempting to get into a wap11 radio through its usb port, because
that port offers a way to restore factory defaults and in the year its
been quiet, I've forgotten the uname/pw. To access it with snmp over
cat5, the uname & pw are a requirement.
I have rebuilt the 2.6.20-rc4
Hi,
I get this while running aiostress.
Jan 22 01:50:05 black-mamba kernel:
===
Jan 22 01:50:05 black-mamba kernel: [ INFO: possible circular locking
dependency detected ]
Jan 22 01:50:05 black-mamba kernel: 2.6.20-rc4-mm1 #1
Jan 22 01:50:05
At Mon, 22 Jan 2007 01:35:46 +0100,
Arjan van de Ven wrote:
> > the core of the problem are the cores which are customarily
> > dumped by lisps during the environment generation (or modification) stage,
> > and then mapped back, every time the environment is invoked.
>
> >
> > at the current
I am now pushing up against the i_ino (unsigned long) file limitation
when I use virtual inode numbers in DSFS. This field needs to be increased
to 64 bit to allow more than 4 billion unique inode numbers. I am
running out of inode address space with the current architecture.
Jeff
-
To
Following are 6 (large) patches that introduce support
for bidirectional requests in the kernel.
Since all this is going to interfere with everyone's
work, let us all comment on the implementation, naming,
and future directions. (or forever hold your peace).
The submitted work is against
David Wagner wrote:
> Samium Gromoff wrote:
> >[...] directly setuid root the lisp system executable itself [...]
>
> Like I said, that sounds like a bad idea to me. Sounds like a recipe for
> privilege escalation vulnerabilities. Was the lisp system executable
> really implemented to be
Chr wrote:
>> 7 Seek_Error_Rate 0x000f 083 060 030Pre-fail Always
>> - 204305750
>> 1 Raw_Read_Error_Rate 0x000f 059 049 006Pre-fail Always
>> - 215927244
>> 195 Hardware_ECC_Recovered 0x001a 059 049 000Old_age Always
On Sun, 21 Jan 2007 03:14:33 +0100 Bauke Jan Douma wrote:
> OnStream Di30 (using ide-scsi and osst drivers), when reading
> or writing I regularly get these kernel messages:
>
> <3>ide-scsi: CoD != 0 in idescsi_pc_intr
>
> Let's assume flaky hardware; nothing we can hold the kernel to
> blame
On Jan 21, 2007, at 18:34:56, David Wagner wrote:
[1] In comparison, suidperl was designed to be installed setuid-
root, and it takes special precautions to be safe in this usage.
(And even it has had some security vulnerabilities, despite its
best efforts, which illustrates how tricky this
> the core of the problem are the cores which are customarily
> dumped by lisps during the environment generation (or modification) stage,
> and then mapped back, every time the environment is invoked.
>
> at the current step of evolution, those core files are not relocatable
> in certain
Boaz Harrosh wrote:
> - Introduce a new enum dma_data_direction data_dir member in struct request.
> and remove the RW bit from request->cmd_flag
> - Add new API to query request direction.
> - Adjust existing API and implementation.
> - Cleanup wrong use of DMA_BIDIRECTIONAL
> - Introduce new
Björn Steinbrink wrote:
On 2007.01.21 13:58:01 -0600, Robert Hancock wrote:
Björn Steinbrink wrote:
All kernels were bad using that approach. So back to square 1. :/
Björn
OK guys, here's a new patch to try against 2.6.20-rc5:
Right now when switching between ADMA mode and legacy mode
Samium Gromoff wrote:
>[...] directly setuid root the lisp system executable itself [...]
Like I said, that sounds like a bad idea to me. Sounds like a recipe for
privilege escalation vulnerabilities. Was the lisp system executable
really implemented to be secure even when you make it setuid
On Mon, 22 Jan 2007 00:03:21 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
>Hi Grant !
>
>On Mon, Jan 22, 2007 at 09:52:44AM +1100, Grant Coady wrote:
>> On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>>
>> >On Thu, Jan 18, 2007 at 06:00:40PM -0700, dann frazier
On Thu, 18 Jan 2007 05:21:16 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
>Hi Grant !
>
>On Thu, Jan 18, 2007 at 11:09:57AM +1100, Grant Coady wrote:
>(...)
>> >} else {
>> >- mnt->file_mode = mnt->dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
>> >-
This patch is intended to provide a working example of a use case
for bidi and varlen CDBs. The actual patches will be sent via the
open-iscsi project.
- Use proposed SCSI implementation for iSCSI bidirectional commands.
- Use proposed block layer implementation for iSCSI extended CDBs.
-
- Add support for varlen CDBs or large vendor specific commands in
struct request.
- Add support for above at SCSI level API's and devices.
- Add the OSD device type.
Signed-off-by: Benny Halevy <[EMAIL PROTECTED]>
Signed-off-by: Boaz Harrosh <[EMAIL PROTECTED]>
---
block/ll_rw_blk.c
- Add bidi members to struct scsi_cmnd.
- Add API at the SCSI level for bidirectional commands.
- Implement support for BIDI requests in scsi_setup_blk_pc_cmnd() and
scsi_io_completion().
Signed-off-by: Benny Halevy <[EMAIL PROTECTED]>
Signed-off-by: Boaz Harrosh <[EMAIL PROTECTED]>
---
- Instantiate another request_io_part in request for bidi_read.
- Define & Implement new API for accessing bidi parts.
- API to Build bidi requests and map to sglists.
- Define new end_that_request_block() function to end a complete request.
Signed-off-by: Benny Halevy <[EMAIL PROTECTED]>
David Wagner wrote:
> Samium Gromoff wrote:
> >the core of the problem are the cores which are customarily
> >dumped by lisps during the environment generation (or modification) stage,
> >and then mapped back, every time the environment is invoked.
> >
> >at the current step of evolution, those
On Sun, 21 Jan 2007, Udo van den Heuvel wrote:
H. Peter Anvin wrote:
Greg KH wrote:
On Fri, Jan 19, 2007 at 04:40:34PM +0100, Udo van den Heuvel wrote:
I just tried my shiny new usb extension cable (repeater):
Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd
David Wagner wrote:
> Samium Gromoff wrote:
> >the core of the problem are the cores which are customarily
> >dumped by lisps during the environment generation (or modification) stage,
> >and then mapped back, every time the environment is invoked.
> >
> >at the current step of evolution, those
Hi Grant !
On Mon, Jan 22, 2007 at 09:52:44AM +1100, Grant Coady wrote:
> On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>
> >On Thu, Jan 18, 2007 at 06:00:40PM -0700, dann frazier wrote:
> >Ah, think I see the problem now:
> >
> >---
thx - I have added these to the cifs git tree.
Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench at-sign us dot ibm dot com
"Ahmed S. Darwish" <[EMAIL PROTECTED]> wrote on 01/06/2007 07:17:44 AM:
> Hi,
> A patch to remove two
Johannes Schindelin wrote:
> On Sun, 21 Jan 2007, Junio C Hamano wrote:
>> * Reflog
>>
>> - Reflog records the history of where the tip of each branch
>>was at each moment.
>
> It might make sense to reformulate that:
>
> Reflog records the history from the view point of the local
Samium Gromoff wrote:
>the core of the problem are the cores which are customarily
>dumped by lisps during the environment generation (or modification) stage,
>and then mapped back, every time the environment is invoked.
>
>at the current step of evolution, those core files are not relocatable
Björn Steinbrink wrote:
On 2007.01.21 23:08:11 +0100, Björn Steinbrink wrote:
On 2007.01.21 13:58:01 -0600, Robert Hancock wrote:
Björn Steinbrink wrote:
All kernels were bad using that approach. So back to square 1. :/
Björn
OK guys, here's a new patch to try against 2.6.20-rc5:
Right
On 2007.01.21 13:58:01 -0600, Robert Hancock wrote:
> Björn Steinbrink wrote:
> >All kernels were bad using that approach. So back to square 1. :/
> >
> >Björn
> >
>
> OK guys, here's a new patch to try against 2.6.20-rc5:
>
> Right now when switching between ADMA mode and legacy mode (i.e. when
Johannes Schindelin wrote:
> On Sun, 21 Jan 2007, Jakub Narebski wrote:
>> Johannes Schindelin wrote:
>>> On Sun, 21 Jan 2007, Bill Lear wrote:
>>>
Also (apologies for the ignorance), how do I get the 1.5.0-rc2 release?
>>>
>>> Direct your browser to
>>>
>>>
> > Talk about a cure worse than the disease! So you're
> > saying that 256MB flash
> > cards could be advertised as having 268.4MB? A 512MB RAM stick is
> > mislabelled and could correctly say 536.8MB? That's just plain
> > craziness.
> No, I meant to advertise it as a 256 MiB flash device and
On 2007.01.21 23:08:11 +0100, Björn Steinbrink wrote:
> On 2007.01.21 13:58:01 -0600, Robert Hancock wrote:
> > Björn Steinbrink wrote:
> > >All kernels were bad using that approach. So back to square 1. :/
> > >
> > >Björn
> > >
> >
> > OK guys, here's a new patch to try against 2.6.20-rc5:
> >
At Sun, 21 Jan 2007 03:16:04 +0100,
Arjan van de Ven wrote:
>
> On Sat, 2007-01-20 at 17:37 +0300, Samium Gromoff wrote:
> > This patch removes the dropping of ADDR_NO_RANDOMIZE upon execution of
> > setuid
> > binaries.
> >
> > Why? The answer consists of two parts:
> >
> > Firstly, there are
On 2007.01.21 13:58:01 -0600, Robert Hancock wrote:
> Björn Steinbrink wrote:
> >All kernels were bad using that approach. So back to square 1. :/
> >
> >Björn
> >
>
> OK guys, here's a new patch to try against 2.6.20-rc5:
>
> Right now when switching between ADMA mode and legacy mode (i.e. when
Eduard Bloch wrote:
> * Bodo Eggert [Sun, Jan 21 2007, 11:40:40AM]:
>> 2) No sane person would say kibibyte as required by the standard. You'd need
>>a sppech defect in order to do this, and a mental defect in order to try.
>>So why should anybody adhere to the rest of this bullshit?
>
>
On Sun, Jan 21, 2007 at 01:45:27PM -0800, Auke Kok wrote:
> Frederik Deweerdt wrote:
> >On Sun, Jan 21, 2007 at 09:17:41PM +0200, Andrei Popa wrote:
> >>It's the 10th resume and in /proc/interrupts eth0 appers 10 times.
> >The e100_resume() function should be calling netif_device_detach and
>
Very minor but
> Signed-off-by Hoang-Nam Nguyen <[EMAIL PROTECTED]>
should be
Signed-off-by: Hoang-Nam Nguyen <[EMAIL PROTECTED]>
(':' after the "-by")
Anyway, queued for 2.6.20, thanks.
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Hi,
On Sun, 21 Jan 2007, Jakub Narebski wrote:
> Johannes Schindelin wrote:
>
> > On Sun, 21 Jan 2007, Bill Lear wrote:
> >
> >> Also (apologies for the ignorance), how do I get the 1.5.0-rc2 release?
> >
> > Direct your browser to
> >
> >
Hi,
On Sun, 21 Jan 2007, Junio C Hamano wrote:
> - 'git pack-refs' appeared in v1.4.4;
You should probably mention that it is not necessary to run git-pack-refs
by hand: git-gc is what you want.
BTW have I praised y'all for inventing git-gc? It is _awesome_. I think I
will turn into a DWIM
Frederik Deweerdt wrote:
On Sun, Jan 21, 2007 at 09:17:41PM +0200, Andrei Popa wrote:
It's the 10th resume and in /proc/interrupts eth0 appers 10 times.
The e100_resume() function should be calling netif_device_detach and
free_irq. Could you try the following (compile tested) patch?
I just
On Thu, Jan 18, 2007 at 10:56:13PM +0100, Adrian Bunk wrote:
> This patch removes kernel 2.4 compatibility code.
Looks correct to me, thanks.
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Acked-by: Samuel Ortiz <[EMAIL PROTECTED]>
> ---
>
> drivers/net/irda/vlsi_ir.c | 16
At Sun, 21 Jan 2007 03:16:04 +0100,
Arjan van de Ven wrote:
> On Sat, 2007-01-20 at 17:37 +0300, Samium Gromoff wrote:
> > This patch removes the dropping of ADDR_NO_RANDOMIZE upon execution of
> > setuid
> > binaries.
> >
> > Why? The answer consists of two parts:
> >
> > Firstly, there are
Johannes Schindelin wrote:
> On Sun, 21 Jan 2007, Bill Lear wrote:
>
>> Also (apologies for the ignorance), how do I get the 1.5.0-rc2 release?
>
> Direct your browser to
>
> http://repo.or.cz/w/git.git?a=snapshot;h=eaf6459e4d482af51429f9464125621b805eb5f
Better URL is
On Jan 21 2007 02:29, S.Çağlar Onur wrote:
>After switching ext3 to xfs, i realize system starts to _really_
>unresponsive and extracting tarballs,
Please have a look at http://lkml.org/lkml/2006/5/22/278
-`J'
--
On Jan 21 2007 00:14, Ralf Baechle wrote:
>On Sat, Jan 20, 2007 at 11:42:37PM +, sathesh babu wrote:
>
>> I am trying to run Linux-2.6.18.2 ( with preemption enable)
>> kernel on FPGA board which has MIPS24KE processor runs at 12
>> MHZ. Programmed the timer to give interrupt at every
On Jan 21 2007 17:06, Heikki Orsila wrote:
>
>> 2) No sane person would say kibibyte as required by the standard. You'd need
>>a sppech defect in order to do this, and a mental defect in order to try.
>>So why should anybody adhere to the rest of this bullshit?
>
>I think I'm not sane
Hi,
On Sun, 21 Jan 2007, Bill Lear wrote:
> Also (apologies for the ignorance), how do I get the 1.5.0-rc2 release?
Direct your browser to
http://repo.or.cz/w/git.git?a=snapshot;h=eaf6459e4d482af51429f9464125621b805eb5f
BTW please don't top post. It uses bandwidth unnecessarily (both in terms
On Sun, Jan 21, 2007 at 09:17:41PM +0200, Andrei Popa wrote:
> It's the 10th resume and in /proc/interrupts eth0 appers 10 times.
>
Hi,
The e100_resume() function should be calling netif_device_detach and
free_irq. Could you try the following (compile tested) patch?
Regards,
Frederik
Dear all,
What is the status with respect to this problem? I see that in the
current -rt patch the problematic code piece is different. I personally
haven't tried to reproduce this myself on a more recent kernel, but I
just got a report from one of our users who experienced the same problem
>How fast is your Ethernet port? 100Mbps or 95.37Mbps?
Same lie like with harddrives. It's around 80, not 100.
But it depends on how you look at it. 80 for Layer3, possibly
a little more for Layer2/1.
-`J'
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
From: Jay Cliburn <[EMAIL PROTECTED]>
From: Chris Snook <[EMAIL PROTECTED]>
This patch contains auxiliary C files for the Attansic L1 gigabit ethernet
adapter driver.
Signed-off-by: Jay Cliburn <[EMAIL PROTECTED]>
Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
---
atl1_ethtool.c | 436
From: Jay Cliburn <[EMAIL PROTECTED]>
From: Chris Snook <[EMAIL PROTECTED]>
This patch contains the header files needed by the Attansic L1 gigabit
ethernet adapter driver.
Signed-off-by: Jay Cliburn <[EMAIL PROTECTED]>
Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
---
atl1.h| 288
From: Jay Cliburn <[EMAIL PROTECTED]>
From: Chris Snook <[EMAIL PROTECTED]>
This patch contains the build files for the Attansic L1 gigabit ethernet
adapter driver.
Signed-off-by: Jay Cliburn <[EMAIL PROTECTED]>
Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
---
Kconfig | 11
On Jan 19 2007 10:11, Pavel Machek wrote:
>
>> this is a new 2.6.20 module implementing a user inactivity trigger. Basically
>> it acts as an event sniffer, issuing an ACPI event when no user activity is
>> detected for more than a certain amount of time. This event can be
>> successively
>>
This is the latest submittal of the patchset providing support for the
Attansic L1 gigabit ethernet adapter. This patchset is built against
kernel version 2.6.20-rc5.
This version incorporates all comments from:
Christoph Hellwig:
http://lkml.org/lkml/2007/1/11/43
Ralf Baechle wrote:
On Sun, Jan 21, 2007 at 06:37:24PM +0200, S.Çağlar Onur wrote:
21 Oca 2007 Paz tarihinde şunları yazmıştınız:
RSS feed of the git tree:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=r
I already mailed to webmaster _at_ kernel.org 2 days ago but
On Sun, Jan 21, 2007 at 06:37:24PM +0200, S.Çağlar Onur wrote:
> 21 Oca 2007 Paz tarihinde şunları yazmıştınız:
> > RSS feed of the git tree:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=r
>
> I already mailed to webmaster _at_ kernel.org 2 days ago but still all
S.Çağlar Onur wrote:
21 Oca 2007 Paz tarihinde şunları yazmıştınız:
RSS feed of the git tree:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=r
I already mailed to webmaster _at_ kernel.org 2 days ago but still all RSS
feeds gaves "Internal Server Error"
We're
H. Peter Anvin wrote:
So write a kernel driver. It's not like we're locking anybody out.
There is certainly enough Amateur Radio/Linux crossover that a kernel
enhancement to support Amateur Radio is going to get frowned upon.
Argh! Not only did the message go out twice, but that should
On Sunday, 21. January 2007 20:25, Paolo Ornati wrote:
> On Sun, 21 Jan 2007 11:32:02 -0600
> Robert Hancock <[EMAIL PROTECTED]> wrote:
>
> > It looks like what you're getting is an actual NCQ write timing out.
> > That makes the bisect result not very interesting since obviously it
> >
On Sunday, 21. January 2007 19:01, Björn Steinbrink wrote:
> On 2007.01.21 18:34:40 +0100, Chr wrote:
>
> I run those two in parallel:
> while /bin/true; do ls -lR / > /dev/null 2>&1; done
> while /bin/true; do echo 255 > /proc/sys/vm/drop_caches; sleep 1; done
>
> Not sure if running them in
Junio C Hamano <[EMAIL PROTECTED]> wrote:
> BTW, as the upcoming v1.5.0 release will introduce quite a bit of
> surface changes (although at the really core it still is the old
> git and old ways should continue to work), I am wondering if it
> would help people to try out and find wrinkles before
Geert Uytterhoeven wrote:
Yeah, and Ethernet speed is measured in Mbps, not Mibps.
Indeed.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sunday 21 January 2007 13:09, Michael Tokarev wrote:
> Denis Vlasenko wrote:
> > On Saturday 20 January 2007 21:55, Michael Tokarev wrote:
> >> Denis Vlasenko wrote:
> >>> On Thursday 11 January 2007 18:13, Michael Tokarev wrote:
> example, which isn't quite possible now from userspace.
On Sat, 20 Jan 2007, H. Peter Anvin wrote:
> David Schwartz wrote:
> > Talk about a cure worse than the disease! So you're saying that 256MB
> > flash
> > cards could be advertised as having 268.4MB? A 512MB RAM stick is
> > mislabelled and could correctly say 536.8MB? That's just plain
Junio C Hamano <[EMAIL PROTECTED]> wrote:
> Willy Tarreau <[EMAIL PROTECTED]> writes:
> > Anything you can do to make tester's life easier will always slightly
> > increase the number of testers.
> > ...
> > Pre-release tar.gz and rpms coupled with a freshmeat announcement should
> > get you a
Jesper Juhl wrote:
On 15/11/06, William D Waddington <[EMAIL PROTECTED]> wrote:
I tried submitting a patch a while back:
"[PATCH] IRQ: ease out-of-tree migration to new irq_handler prototype"
to add #define __PT_REGS to include/linux/interrupt.h to flag the change
to the new interrupt handler
Björn Steinbrink wrote:
All kernels were bad using that approach. So back to square 1. :/
Björn
OK guys, here's a new patch to try against 2.6.20-rc5:
Right now when switching between ADMA mode and legacy mode (i.e. when
going from doing normal DMA reads/writes to doing a FLUSH CACHE) we
Junio C Hamano wrote:
One worry I had about releasing git-1.5.0-rc2-1.rpm and friends
just like the "official" ones was that people might have scripts
to automate downloading & updating of packages, and they may not
like to get "beta" installed for them.
I wonder if kernel.org machines are
On Sun, 21 Jan 2007, Nicholas Miell wrote:
> On Sun, 2007-01-21 at 05:03 -0500, Robert P. J. Day wrote:
> > Introduce the TRUE and FALSE boolean macros so that everyone can
> > stop re-inventing them, and remove the one occurrence in the
> > source tree that clashes with that change.
> If
1 - 100 of 338 matches
Mail list logo
