i2c-core.o: i2c core module version 2.8.1 (20031005)
i2c-isa.o version 2.8.1 (20031005)
i2c-proc.o version 2.8.1 (20031005)
w83781d.o version 2.8.1 (20031005)
eeprom.o version 2.8.1 (20031005)
i2c-nforce2.o version 2.8.1 (20031005)
i2c-nforce2.o: nForce2 SMBus adapter at 0x5000
i2c-nforce2.o: nForce2 SMBus adapter at 0x5040
i2c-dev.o: i2c /dev entries driver module version 2.8.1 (20031005)
i2c-dev.o: Registered 'ISA main adapter' as minor 0
i2c-dev.o: Registered 'SMBus nForce2 adapter at 5000' as minor 1
i2c-dev.o: Registered 'SMBus nForce2 adapter at 5040' as minor 2
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
e0a5a216
*pde = 00000000
Oops: 0000
i2c-dev i2c-nforce2 eeprom w83781d i2c-proc i2c-isa i2c-core nvaudio
ac97_codec
soundcore parport_pc lp parport iptable_filter ip_tables autofs nfs lockd
sunr
CPU: 0
EIP: 0060:[<e0a5a216>] Tainted: P
EFLAGS: 00010246
EIP is at nforce2_access [i2c-nforce2] 0x1b6 (2.4.20-13.9)
eax: 00000000 ebx: 00005000 ecx: c17baa00 edx: 00000001
esi: c17baa00 edi: 00000000 ebp: c17baa00 esp: d82a3e78
ds: 0068 es: 0068 ss: 0068
Process i2cdump (pid: 3542, stackpage=d82a3000)
Stack: d82cd340 dffd2400 00000296 c25a6bb8 dffd2400 003462b0 00500000
c17baa40
00000000 00000001 c17baa04 e0a40cc9 c17baa04 00000050 00000000
00000000
00000000 00000001 00000000 e0a5af20 d8277420 d83ec180 420ac6a0
00000050
Call Trace: [<e0a40cc9>] i2c_smbus_xfer_R935cccc0 [i2c-core] 0x89
(0xd82a3ea4)
)
[<e0a5af20>] smbus_algorithm [i2c-nforce2] 0x0 (0xd82a3ec4))
[<e0a5c14c>] i2cdev_ioctl [i2c-dev] 0x0 (0xd82a3ef0))
[<e0a5c5af>] i2cdev_ioctl [i2c-dev] 0x463 (0xd82a3ef4))
[<c01186c0>] schedule [kernel] 0x170 (0xd82a3f40))
[<c01254d7>] schedule_timeout [kernel] 0x67 (0xd82a3f64))
[<e0a5c14c>] i2cdev_ioctl [i2c-dev] 0x0 (0xd82a3f90))
[<c0153d4c>] sys_ioctl [kernel] 0xbc (0xd82a3f94))
[<c010939f>] system_call [kernel] 0x33 (0xd82a3fc0))
Code: 8a 07 8d 53 04 ee e6 80 83 ce 04 e9 a3 fe ff ff 8b 9d f0 00
-----Original Message-----
From: Mark Studebaker [mailto:mds at paradyne.com]
Sent: Wednesday, November 26, 2003 3:41 PM
To: sensors at Stimpy.netroedge.com
Cc: william.mcclintock at schriever.af.mil; frdurso at yahoo.com.br
Subject: Re: unknown eeprom type (65) [ticket #1449]
does dmesg have anything about a module going oops?
Jean Delvare wrote:
>>>[root at workstation1 cvs2]# i2cdump 1 50 c
>>> WARNING! This program can confuse your I2C bus, cause data loss
>>> and worse! I will probe file /dev/i2c-1, address 0x32, mode byte
>>> consecutive read You have five seconds to reconsider and press
>>> CTRL-C!
>>>
>>>Segmentation fault
>
>
> Still this needs fixing. Mark, any idea about that? Could it be caused
> by the i2c-nforce2 driver? Doing the same here (i2c-i801) exits cleanly:
> Error: Write start address failed, return code -1
>
