Re: ip aliasing wierd in 2.1.126

Andi Kleen (ak@muc.de)
27 Oct 1998 08:09:17 +0100


In article <19981026182220.A21757@jasmine.psyber.com>,
Ted Deppner <ted@jasmine.psyber.com> writes:
> Hello, this'll be brief as I'm sure some it's been brought up somewhere, just
> adding my data point. I can provide more details or test stuff if needed.

> My box brings up eth0:0 on boot (which is up and working), however an ifconfig
> doesn't show any alias devices, and neither does /proc/net/dev. Running
> 2.1.123 (and every other kernel), they show up.

> Last boot something went wrong with the networking, requiring a reboot, I
> couldn't get the route commands to actually add back in the routes using the
> eth0:0 alias. Immediatly after the reboot things worked fine (still no
> aliases in /proc/net/dev though).

The latest net-tools from vger support 2.1 ip aliasing. They will never
show up in /proc/net/dev, because they're not real devices now but only
additional addresses for a single device.

> Unable to handle kernel paging request at virtual address 000e492a
current-> tss.cr3 = 03e60000, %cr3 = 03e60000
> *pde = 00000000
> Oops: 0000
> CPU: 1
> EIP: 0010:[<c0157186>]
> EFLAGS: 00010202
> eax: 00000064 ebx: c0984504 ecx: 00000014 edx: c0668c00
> esi: c27f5900 edi: 000e48d0 ebp: c0581e30 esp: c0581e20
> ds: 0018 es: 0018 ss: 0018
> Process junkbuster (pid: 12951, process nr: 60, stackpage=c0581000)
> Stack: c0984518 000e48d0 0000003c c3a48820 c27f59b0 c015da75 c0668c00 c27f5900
> c27f5930 c0668700 c27f59b0 c098453c 00339da9 00000000 00000001 c015edff
> c27f5900 c0668c00 c0668700 00000005 c0668700 c27f59b0 c27f5900 00000000
> Call Trace: [<c015da75>] [<c015edff>] [<c0160686>] [<c0167585>] [<c014aa64>] [<c015acaf>] [<c0166c96>]
> [<c014b0f1>] [<c014b8a8>] [<c0107b54>]
> Code: 0f b7 4f 5a 39 c8 7d 60 83 bf b0 00 00 00 00 74 57 8d 41 0f

Could you run this oops through ksymoops (see the README file on how) ?
It can be only debugged with the symbols filled in.

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/