Re: Kernel 2.6.3-1 issue with Debian sarge upgrade (32 bit i386)
On Mon, Jun 13, 2005 at 04:51:21PM -0000, valentin_nils@be-known-online.com wrote:
> Hello Debian fans,
>
> I tried to update my Debian sarge and got the bellow messages in my
> /var/log/messages. can anyone pinpoint me with an educated guess what I am
> looking at ?
>
> Which driver does the kernel chock on, and perhaps why ? ;-(
>
> The system basically hangs ina loop during startup at the place when it
> supposed to load the pcmcia, net, usb drivers.
>
> Any feedback appreciated.
>
> Best regards
>
> Nils Valentin
>
> ...
> Jun 13 21:18:45 ns3 kernel: tg3: eth1: Link is up at 100 Mbps, full duplex.
> Jun 13 21:18:45 ns3 kernel: tg3: eth1: Flow control is on for TX and on
> for RX.
> Jun 13 21:18:45 ns3 kernel: NET: Registered protocol family 10
> Jun 13 21:18:45 ns3 kernel: Disabled Privacy Extensions on device
> c02ba900(lo)
> Jun 13 21:18:45 ns3 kernel: IPv6 over IPv4 tunneling driver
> Jun 13 21:18:51 ns3 kernel: printing eip:
> Jun 13 21:18:51 ns3 kernel: c018c079
> Jun 13 21:18:51 ns3 kernel: Oops: 0002 [#1]
> Jun 13 21:18:51 ns3 kernel: CPU: 0
> Jun 13 21:18:51 ns3 kernel: EIP: 0060:[kobject_add+103/176] Tainted: P
> Jun 13 21:18:51 ns3 kernel: EFLAGS: 00010292
> Jun 13 21:18:51 ns3 kernel: EIP is at kobject_add+0x67/0xb0
> Jun 13 21:18:51 ns3 kernel: eax: c02b3040 ebx: f8d3243c ecx: f8d75a98
> edx: f8d32458
> Jun 13 21:18:51 ns3 kernel: esi: c02b3048 edi: f8d32424 ebp: 00000000
> esp: f1c9bedc
> Jun 13 21:18:51 ns3 kernel: ds: 007b es: 007b ss: 0068
> Jun 13 21:18:51 ns3 kernel: Process modprobe (pid: 1660,
> threadinfo=f1c9a000 task=f2864080)
> Jun 13 21:18:51 ns3 kernel: Stack: f8d3243c ffffffea f8d32424 c018c0dd
> f8d3243c f8d3243c f8d3243c c02b2fe0
> Jun 13 21:18:51 ns3 kernel: c01d0ee7 f8d3243c f8d3243c f8d2eb6d
> f8d32400 00000000 f8d32498 f8d325c0
> Jun 13 21:18:51 ns3 kernel: c01d113f f8d32424 00000678 fffffffd
> ffffffff 00000000 c0193b07 f8d32424
> Jun 13 21:18:51 ns3 kernel: Call Trace:
> Jun 13 21:18:51 ns3 kernel: [kobject_register+27/61]
> kobject_register+0x1b/0x3d
> Jun 13 21:18:51 ns3 kernel: [bus_add_driver+48/97] bus_add_driver+0x30/0x61
> Jun 13 21:18:51 ns3 kernel: [driver_register+45/49]
> driver_register+0x2d/0x31
> Jun 13 21:18:51 ns3 kernel: [pci_register_driver+78/107]
> pci_register_driver+0x4e/0x6b
> Jun 13 21:18:51 ns3 kernel: [__crc_pm_idle+3883623/5541136]
> parport_pc_find_ports+0x27/0x40 [parport_pc]
> Jun 13 21:18:51 ns3 kernel: [__crc_pm_idle+3883794/5541136]
> parport_pc_init+0x92/0xa3 [parport_pc]
> Jun 13 21:18:51 ns3 kernel: [__crc_pm_idle+4316224/5541136]
> init_module+0xf6/0x11f [parport_pc]
> Jun 13 21:18:51 ns3 kernel: [sys_init_module+234/472]
> sys_init_module+0xea/0x1d8
> Jun 13 21:18:51 ns3 kernel: [syscall_call+7/11] syscall_call+0x7/0xb
> Jun 13 21:18:51 ns3 kernel:
> Jun 13 21:18:51 ns3 kernel: Code: 89 11 89 4a 04 8b 43 28 8b 00 83 c0 48
> e8 67 11 00 00 89 73
> Jun 13 21:18:51 ns3 kernel: <6>lp: driver loaded but no devices found
Given the time stamps, I almost suspect the parport/parport_pc/lp
drivers as the most likely. Rather odd really.
What motherboard/chipset/cpu/kernel version?
Len Sorensen
Reply to: