[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug: DHCP initialization with RealTek 8139 net driver



Greetings.

I'm not sure which package or pseudo-package this would fall under, so
I'm sending it here per the Debian web site bug submission guidelines.
Basically, during installation of Debian 2.2r3 (Potato), I got the
following kernel panic (what I did is below the panic screen text if you
want to skip down):

-------------------------------------------
Unable to handle kernel paging request at virtual address c8000000
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c01605bd>]
EFLAGS: 00010216
eax: 000001a8 ebx: c77060b0 ecx: 3fd5806a edx: fffffffc
esi: c8000000 edi: c579f556 ebp: c75601ac esp: c02dbe84
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stacpkage=c02db000)
Stack: c4cff702 c75601ac c8821b7c c77060b0 c75601ac fffffffc 00000000
c4cff540
       c076d0e0 0000000a 00000001 c75601ac 00000046 fffffffc 00000000
c03201a8
       c7560000 0000ec00 c076d0e0 c8821404 c7f09870 c4cff540 04000001
0000000a
Call Trace: [<c8821b7c>] [<c8821404>] [<c010b1f9>] [<c010afb2>]
[<c011a8a9>] [<c010b30f>] [<c010aff8>]
            [<c010893d>] [<c0106000>] [<c0108960>] [<c010a1e0>]
[<c0106000>] [<c010607b>] [<c0106000>] [<c0100175>]
Code: f3 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5b 5e 5f 5d c3
Aiee, killing interrupt handler
kernel panic: Attempted to kill the idle task!
In swapper task - not syncing
-------------------------------------------
(apologies for any errors in the above, I had to handcopy it from the
Linux box to the Windows box via good ol' fashioned eyeballs)
-------------------------------------------

Basically, I'm installing the net driver rtl8139, and configuring it.
The first step is fine.  Then I get to the option "Next: Configure the
Network" and it asks for the name, I set it to "vertigo."  Then it says,
do you want to use DHCP/etc, and I choose Yes.  At this point, the first
time I went through this step, the machine spontaneously rebooted.  The
second and third time it paniced, yielding the above result.  The fourth
time it worked fine.

This is not a big problem as the fourth attempt worked fine, but
something that someone might be interested in looking into.  Thanks
guys.


-Mark Smith
xb95@yahoo.com
ICQ: 2903909


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




Reply to: