From: Jeremy Hall <jhall@maoz.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Andrew Morton <akpm@digeo.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.67-mm2
Date: Sat, 12 Apr 2003 23:03:46 -0400 (EDT) [thread overview]
Message-ID: <200304130303.h3D33kkr031006@sith.maoz.com> (raw)
In-Reply-To: <1050198928.597.6.camel@teapot.felipe-alfaro.com> from Felipe Alfaro Solana at "Apr 13, 2003 03:55:29 am"
I dunno about that, but mm2 locks in the boot process and doesn't display
anything to me through gdb even though it is supposed to. I have gdb
console=gdb but that doesn't make the messages flow.
_J
In the new year, Felipe Alfaro Solana wrote:
> On Sun, 2003-04-13 at 03:08, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.67/2.5.67-mm2/
> >
> > . Lots of misc saved-up things.
> >
> > . I've changed the 32-bit dev_t patch to provide a 12:20 split rather than
> > 16:16. This patch is starting to drag a bit and unless someone stops me I
> > might just go submit the thing.
>
> Any patches for CardBus/PCMCIA support? It's broken for me since
> 2.5.66-mm2 (it works with 2.5.66-mm1) probably due to PCI changes or the
> new PCMCIA state machine: if I boot my machine with my 3Com CardBus NIC
> plugged in, the kernel deadlocks while checking the sockets, but it
> works when booting with the card unplugged, and then plugging it back
> once the system is stable (for example, init 1).
>
> I have written to Russell King, but had no response from him. Maybe he
> is too busy. I'm stuck at 2.5.66-mm1 on my laptop.
>
> --
> Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
> See http://www.fsf.org/philosophy/no-word-attachments.html
> Linux Registered User #287198
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-04-13 3:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 1:08 2.5.67-mm2 Andrew Morton
2003-04-13 1:55 ` 2.5.67-mm2 Felipe Alfaro Solana
2003-04-13 3:03 ` Jeremy Hall [this message]
2003-04-13 3:10 ` 2.5.67-mm2 Andrew Morton
2003-04-13 3:54 ` 2.5.67-mm2 Jeremy Hall
2003-04-13 4:22 ` 2.5.67-mm2 Jeremy Hall
2003-04-13 4:32 ` 2.5.67-mm2 Andrew Morton
2003-04-13 3:14 ` 2.5.67-mm2 William Lee Irwin III
2003-04-13 3:50 ` 2.5.67-mm2 Jeremy Hall
2003-04-13 4:42 ` 2.5.67-mm2 Andrew Morton
2003-04-13 3:17 ` 2.5.67-mm2 Valdis.Kletnieks
2003-04-13 11:15 ` 2.5.67-mm2 Felipe Alfaro Solana
2003-04-13 8:11 ` 2.5.67-mm2 Russell King
2003-04-13 13:12 ` 2.5.67-mm2 Ingo Oeser
2003-04-13 14:54 ` 2.5.67-mm2 Arjan van de Ven
2003-04-14 6:24 ` 2.5.67-mm2 Denis Vlasenko
2003-04-14 8:49 ` 2.5.67-mm2 Arjan van de Ven
2003-04-14 17:48 ` 2.5.67-mm2 Joel Becker
2003-04-14 21:31 ` 2.5.67-mm2 Andrew Morton
2003-04-14 21:34 ` 2.5.67-mm2 Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200304130303.h3D33kkr031006@sith.maoz.com \
--to=jhall@maoz.com \
--cc=akpm@digeo.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox