Dan Williams wrote:
> On 11/8/07, Bill Davidsen <[EMAIL PROTECTED]> wrote:
>> Jeff Lessem wrote:
>>> Dan Williams wrote:
>>>> The following patch, also attached, cleans up cases where the code
>>> looks
>>>> at sh->ops.pending when it s
Dan Williams wrote:
> The following patch, also attached, cleans up cases where the code looks
> at sh->ops.pending when it should be looking at the consistent
> stack-based snapshot of the operations flags.
I tried this patch (against a stock 2.6.23), and it did not work for
me. Not only did I/
In your message of: Fri, 15 Apr 2005 02:15:13 +0300, you write:
>On Thu, Apr 14, 2005 at 06:40:16PM -0400, abonilla wrote:
>> On Thu, 14 Apr 2005 23:20:19 +0200 (CEST), Jesper Juhl wrote
>> > On Thu, 14 Apr 2005, Alejandro Bonilla wrote:
>...
>> > > This is located in my home PC, Won't be the fast
nto a logfile.
--
Thanks,
Jeff Lessem.
-
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
Please read the FAQ at http://www.tux.org/lkml/
e
disk IO, but I will detail that in another message (look for "kswapd,
kupdated, and bdflush at 99%").
Any advice to alleviate this problem would be appreciated, and I will
provide any more information I can upon request.
--
Thanks,
Jeff Lessem.
-
To unsubscribe from this lis
In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write:
>
>Careful, you're overwriting ACPI data now (and using it as normal RAM).
Hmm, I guess that would be bad.
>Can you try one of a) LILO b) a fixed version of grub c) this patch ?
I tried LILO and the problem did indeed go away when us
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
>Jeff, are you using the e820 memory map at all ? In particular, are you
>using grub or some other buggy bootloader that insists on specifying a
>mem= option on the kernel command line ? There should be a kernel command
>line message
I wouldn't have even brought it to the
attention of linux-kernel, except that something that changed between
2.2.17 and 2.4.x has produced a regression in functionality. If
anybody thinks it would be useful, I would be willing to do a binary
search between 2.2.17 and 2.4.2 to find out at whi
In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write:
>Hmm.. You shouldn't be loading any i82365 module at all. You should load
>the "yenta_socket" module.
I had gone back to my old ways of useing the external PCMCIA stuff.
Here are the relevant lspci --vvxx listings using the yenta driv
In your message of: Thu, 22 Feb 2001 19:40:03 PST, you write:
>Can you do a full "lspci -vvxxx" (as root) both on a working and a
>non-working setup, and send the two files to the kernel list and cc to
>me?
No problem, the listings are below. Both listings were done on a
freshly booted system.
gged messages. Rebooting with 2.2.17 fixes the problem and
2.4.2 then works again. It looks to me like something in the PCI bus
isn't setup correctly by the 2.4 kernels, but chasing that down is way
beyond my ability, hence the post to linux-kernel.
--
Jeff Lessem.
-
To unsubscribe
problems during the first months I owned the machine when I only used
16-bit cards.
--
Thanks,
Jeff Lessem.
-
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
Please read the FAQ at http://www.tux.org/lkml/
th0 is 00 60 1d 1e 75 c0
And /proc/apm. The laptop is currently configured with two batteries,
and no mains power.
1.14 1.2 0x03 0xff 0xff 0xff -1% -1 ?
Sorry if this message is redundant, but I didn't see any other
responses at the time I sent this.
--
Jeff Lessem.
-
To unsubscribe
13 matches
Mail list logo
