From: Karsten Keil <[EMAIL PROTECTED]>
Date: Fri, 12 Oct 2007 16:05:22 +0200
> This is a followup to the previous ISDN alloc_netdev() patch.
> It removes the local copy of the device name to make sure
> that device renames work.
>
> Signed-off-by: Karsten Keil <[EMAIL PROTECTED]>
Applied, thanks
Hi Dave,
a follow up to the previous patch for net-2.6.24.
On Mon, Oct 08, 2007 at 08:37:33PM -0700, David Miller wrote:
> >
> > You could try following patch with 2.6.23-rc8-mm2, it change I4L to use
> > alloc_netdev().
> >
> > Signed-off-by: Karsten Keil <[EMAIL PROTECTED]>
>
> I've added th
Hi,
On Mon, Oct 08, 2007 at 05:58:36PM +0200, Karsten Keil wrote:
> You could try following patch with 2.6.23-rc8-mm2, it change I4L to use
> alloc_netdev().
I just did the horribly unthinkable:
I rebooted the production internet gateway *remotely*, and:
[EMAIL PROTECTED]:/home/andi# uname -a
Li
From: Karsten Keil <[EMAIL PROTECTED]>
Date: Mon, 8 Oct 2007 17:58:36 +0200
> On Sun, Oct 07, 2007 at 07:20:37PM +0200, Andreas Mohr wrote:
> > Hi,
> >
> > On Sun, Oct 07, 2007 at 03:17:24PM +0200, Andreas Mohr wrote:
> > > I thus decided to now try plain 2.6.23-rc8 whether it's "corrupted", too.
On Mon, 8 Oct 2007 13:48:44 +0200
Karsten Keil <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 07, 2007 at 02:06:53PM +0200, Andreas Mohr wrote:
> > [not necessarily a very recent regression, used 2.6.19 kernels before...]
> >
> > Hi all,
> >
> > wondered why my main internet server (headless!) didn't
On Sun, Oct 07, 2007 at 07:20:37PM +0200, Andreas Mohr wrote:
> Hi,
>
> On Sun, Oct 07, 2007 at 03:17:24PM +0200, Andreas Mohr wrote:
> > I thus decided to now try plain 2.6.23-rc8 whether it's "corrupted", too.
>
> OK, after 3 hours of compilation the ONLY datapoint I can give right now is:
> 1
On Sun, Oct 07, 2007 at 02:06:53PM +0200, Andreas Mohr wrote:
> [not necessarily a very recent regression, used 2.6.19 kernels before...]
>
> Hi all,
>
> wondered why my main internet server (headless!) didn't come up properly
> on a new 2.6.23-rc8-mm2
...
> as if it's the
>BUG_ON(!dev->n
Hi,
On Sun, Oct 07, 2007 at 03:17:24PM +0200, Andreas Mohr wrote:
> I thus decided to now try plain 2.6.23-rc8 whether it's "corrupted", too.
OK, after 3 hours of compilation the ONLY datapoint I can give right now is:
1 (one) boot on 2.6.23-rc8-mm2 had the BUG in /var/log/messages,
1 (one) boot
On Sun, Oct 07, 2007 at 08:24:45AM -0400, Jeff Garzik wrote:
> It definitely looks like ISDN is somehow to blame. Any chance you could
> try git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.24.git ?
I'm afraid I won't make it, since this server is not at my home
location, is a ""produ
Andreas Mohr wrote:
I intend to still try to get it up and running with 2.6.23-rc8-mm2 today
(with some workarounds hopefully, maybe even disabling ISDN completely)...
The last running kernel (I didn't have newer ones in between), up for some 110
days was 2.6.19-cks2 (IOW, I cannot quite say tha
[not necessarily a very recent regression, used 2.6.19 kernels before...]
Hi all,
wondered why my main internet server (headless!) didn't come up properly
on a new 2.6.23-rc8-mm2
(connections almost completely refused: firewalling not executed due to
earlier OOPS?).
Upon LILO emergency fallback i
11 matches
Mail list logo