* General Protection Fault with bcmsensors
@ 2005-08-08 17:31 ` Martin Drab
0 siblings, 0 replies; 9+ messages in thread
From: Martin Drab @ 2005-08-08 15:30 UTC (permalink / raw)
To: Yani Ioannou; +Cc: LM-Sensors Mailing List, Linux Kernel Mailing List
Hi,
I'm getting following general protection fault with bmcsensors and
i2c-ipmi obtained from today's CVS and with 2.6.13-rc6 kernel. After that
system doesn't seem to hang immediatelly (as I was able to do the dmesg
below), however it seems that the internal IPMI watchdog restarted the
system after a while (or perhaps it did it on its own?), since it did
reboot then.
---------------
[ 957.987401] bmcsensors.o
[ 957.998712] i2c-ipmi.o
[ 957.998719] i2c-ipmi.o: BMC access for i2c modules initialized.
[ 958.001767] ipmi device interface version v33
[ 958.004867] IPMI System Interface driver version v33, KCS version v33, SMIC version v33, BT version v33
[ 958.005264] ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca2, slave address 0x20
[ 959.172987] bmcsensors.o: Registered client, scanning for sensors...
[ 959.172995] i2c-ipmi.o: Registered IPMI interface 0 with version 1.5
[ 959.451432] IPMI Watchdog: Starting now!
[ 959.451445] IPMI kcs interface initialized
[ 987.802234] bmcsensors.o: all sensors detected
[ 987.802260] bmcsensors.o: registering sensor 0: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802264] bmcsensors.o: sensors.conf: label temp1 "Planar Temp 1"
[ 987.802267] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802270] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802279] bmcsensors.o: registering sensor 1: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802281] bmcsensors.o: sensors.conf: label temp2 "Planar Temp 2"
[ 987.802283] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802286] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802291] bmcsensors.o: registering sensor 2: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802294] bmcsensors.o: sensors.conf: label temp3 "CPU 2 Temp"
[ 987.802296] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802298] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802306] bmcsensors.o: registering sensor 3: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802309] bmcsensors.o: sensors.conf: label temp4 "CPU 1 Temp"
[ 987.802311] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802313] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802319] bmcsensors.o: registering sensor 4: (type 0x02) (fmt=0; m=63; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802321] bmcsensors.o: sensors.conf: label in1 "Planar 12V"
[ 987.802323] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802325] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802331] bmcsensors.o: registering sensor 5: (type 0x02) (fmt=0; m=12; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802334] bmcsensors.o: sensors.conf: label in2 "CPU 2 VCore"
[ 987.802336] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802338] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802344] bmcsensors.o: registering sensor 6: (type 0x02) (fmt=0; m=13; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802346] bmcsensors.o: sensors.conf: label in3 "CPU 2 2.5V"
[ 987.802348] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802350] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802356] bmcsensors.o: registering sensor 7: (type 0x02) (fmt=0; m=26; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802359] bmcsensors.o: sensors.conf: label in4 "Planar 5VSB"
[ 987.802361] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802363] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802369] bmcsensors.o: registering sensor 8: (type 0x02) (fmt=0; m=12; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802371] bmcsensors.o: sensors.conf: label in5 "CPU 1 VCore"
[ 987.802373] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802375] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802381] bmcsensors.o: registering sensor 9: (type 0x02) (fmt=0; m=13; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802384] bmcsensors.o: sensors.conf: label in6 "CPU 1 2.5V"
[ 987.802386] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802388] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802393] bmcsensors.o: registering sensor 10: (type 0x02) (fmt=0; m=26; b=0; k1=0; k2=13; cap=0x76; mask=0x003f)
[ 987.802396] bmcsensors.o: sensors.conf: label in7 "Planar 5V"
[ 987.802398] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802400] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802406] bmcsensors.o: registering sensor 11: (type 0x04) (fmt=0; m=29; b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802409] bmcsensors.o: sensors.conf: label fan1 "Fan 2 Tach"
[ 987.802411] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802413] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802418] bmcsensors.o: registering sensor 12: (type 0x04) (fmt=0; m=29; b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802421] bmcsensors.o: sensors.conf: label fan2 "Fan 4 Tach"
[ 987.802423] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802425] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802432] bmcsensors.o: registering sensor 13: (type 0x04) (fmt=0; m=29; b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802435] bmcsensors.o: sensors.conf: label fan3 "Fan 1 Tach"
[ 987.802437] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802439] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802444] bmcsensors.o: registering sensor 14: (type 0x04) (fmt=0; m=29; b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802447] bmcsensors.o: sensors.conf: label fan4 "Fan 3 Tach"
[ 987.802449] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802451] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802457] bmcsensors.o: registering sensor 15: (type 0x04) (fmt=0; m=29; b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802459] bmcsensors.o: sensors.conf: label fan5 "Fan 5 Tach"
[ 987.802461] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802463] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802468] bmcsensors.o: 0 reservations cancelled
[ 987.802470] bmcsensors.o: registered 4 temp, 7 volt, 0 current, 5 fan sensors
[ 987.802472] bmcsensors.o: bmcsensor thread done
[ 1007.059503] general protection fault: 0000 [1] SMP
[ 1007.059511] CPU 1
[ 1007.059514] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport
autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid
ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
[ 1007.059533] Pid: 3655, comm: sensors Not tainted 2.6.13-rc6
[ 1007.059535] RIP: 0010:[<ffffffff801fed50>] <ffffffff801fed50>{strcmp+0}
[ 1007.059547] RSP: 0018:ffff810071653cb0 EFLAGS: 00010246
[ 1007.059552] RAX: ffff000a36343735 RBX: ffff81003596f608 RCX: ffff8100328f96d0
[ 1007.059555] RDX: 0000000000000037 RSI: ffff8100710ac9cc RDI: ffff000a36343735
[ 1007.059560] RBP: ffff8100328f9680 R08: 000003fa892e45c7 R09: ffff81003535301c
[ 1007.059563] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8100710ac910
[ 1007.059567] R13: ffff810071653d48 R14: ffff810036776d70 R15: ffff810076d33bf0
[ 1007.059571] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:00000000627c2bb0
[ 1007.059574] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1007.059577] CR2: 00002aaaadb48000 CR3: 0000000071725000 CR4: 00000000000006e0
[ 1007.059581] Process sensors (pid: 3655, threadinfo ffff810071652000, task ffff810035c58a20)
[ 1007.059583] Stack: ffffffff801c59d1 ffff8100710ac910 ffff810071653ed8 ffff810071653d38
[ 1007.059590] ffff810071653d48 ffff810036776d70 ffffffff80192565 000001b600008001
[ 1007.059596] ffff810037ff7080 ffff810036776cb0
[ 1007.059599] Call Trace:<ffffffff801c59d1>{sysfs_lookup+81} <ffffffff80192565>{do_lookup+245}
[ 1007.059614] <ffffffff80193076>{__link_path_walk+2582} <ffffffff80193659>{link_path_walk+137}
[ 1007.059626] <ffffffff801818b3>{get_unused_fd+227} <ffffffff8014a509>{remove_wait_queue+25}
[ 1007.059640] <ffffffff80193c9d>{path_lookup+461} <ffffffff801951cc>{open_namei+172}
[ 1007.059649] <ffffffff8025867a>{tty_ldisc_deref+122} <ffffffff8018261d>{filp_open+45}
[ 1007.059660] <ffffffff80182712>{sys_open+82} <ffffffff8010dcf2>{system_call+126}
[ 1007.059673]
[ 1007.059678]
[ 1007.059678] Code: 0f b6 17 89 d0 2a 06 48 ff c6 84 c0 74 04 0f be c0 c3 48 ff
[ 1007.059687] RIP <ffffffff801fed50>{strcmp+0} RSP <ffff810071653cb0>
[ 1007.059693]
---------------
Martin
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] General Protection Fault with bcmsensors
@ 2005-08-08 17:31 ` Martin Drab
0 siblings, 0 replies; 9+ messages in thread
From: Martin Drab @ 2005-08-08 17:31 UTC (permalink / raw)
To: Yani Ioannou; +Cc: LM-Sensors Mailing List, Linux Kernel Mailing List
Hi,
I'm getting following general protection fault with bmcsensors and
i2c-ipmi obtained from today's CVS and with 2.6.13-rc6 kernel. After that
system doesn't seem to hang immediatelly (as I was able to do the dmesg
below), however it seems that the internal IPMI watchdog restarted the
system after a while (or perhaps it did it on its own?), since it did
reboot then.
---------------
[ 957.987401] bmcsensors.o
[ 957.998712] i2c-ipmi.o
[ 957.998719] i2c-ipmi.o: BMC access for i2c modules initialized.
[ 958.001767] ipmi device interface version v33
[ 958.004867] IPMI System Interface driver version v33, KCS version v33, SMIC version v33, BT version v33
[ 958.005264] ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca2, slave address 0x20
[ 959.172987] bmcsensors.o: Registered client, scanning for sensors...
[ 959.172995] i2c-ipmi.o: Registered IPMI interface 0 with version 1.5
[ 959.451432] IPMI Watchdog: Starting now!
[ 959.451445] IPMI kcs interface initialized
[ 987.802234] bmcsensors.o: all sensors detected
[ 987.802260] bmcsensors.o: registering sensor 0: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802264] bmcsensors.o: sensors.conf: label temp1 "Planar Temp 1"
[ 987.802267] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802270] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802279] bmcsensors.o: registering sensor 1: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802281] bmcsensors.o: sensors.conf: label temp2 "Planar Temp 2"
[ 987.802283] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802286] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802291] bmcsensors.o: registering sensor 2: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802294] bmcsensors.o: sensors.conf: label temp3 "CPU 2 Temp"
[ 987.802296] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802298] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802306] bmcsensors.o: registering sensor 3: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
[ 987.802309] bmcsensors.o: sensors.conf: label temp4 "CPU 1 Temp"
[ 987.802311] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802313] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802319] bmcsensors.o: registering sensor 4: (type 0x02) (fmt=0; mc; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802321] bmcsensors.o: sensors.conf: label in1 "Planar 12V"
[ 987.802323] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802325] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802331] bmcsensors.o: registering sensor 5: (type 0x02) (fmt=0; m\x12; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802334] bmcsensors.o: sensors.conf: label in2 "CPU 2 VCore"
[ 987.802336] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802338] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802344] bmcsensors.o: registering sensor 6: (type 0x02) (fmt=0; m\x13; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802346] bmcsensors.o: sensors.conf: label in3 "CPU 2 2.5V"
[ 987.802348] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802350] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802356] bmcsensors.o: registering sensor 7: (type 0x02) (fmt=0; m&; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802359] bmcsensors.o: sensors.conf: label in4 "Planar 5VSB"
[ 987.802361] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802363] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802369] bmcsensors.o: registering sensor 8: (type 0x02) (fmt=0; m\x12; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802371] bmcsensors.o: sensors.conf: label in5 "CPU 1 VCore"
[ 987.802373] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802375] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802381] bmcsensors.o: registering sensor 9: (type 0x02) (fmt=0; m\x13; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802384] bmcsensors.o: sensors.conf: label in6 "CPU 1 2.5V"
[ 987.802386] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802388] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802393] bmcsensors.o: registering sensor 10: (type 0x02) (fmt=0; m&; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
[ 987.802396] bmcsensors.o: sensors.conf: label in7 "Planar 5V"
[ 987.802398] bmcsensors.o: using upper critical threshold for upper limit
[ 987.802400] bmcsensors.o: using lower critical threshold for lower limit
[ 987.802406] bmcsensors.o: registering sensor 11: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802409] bmcsensors.o: sensors.conf: label fan1 "Fan 2 Tach"
[ 987.802411] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802413] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802418] bmcsensors.o: registering sensor 12: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802421] bmcsensors.o: sensors.conf: label fan2 "Fan 4 Tach"
[ 987.802423] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802425] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802432] bmcsensors.o: registering sensor 13: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802435] bmcsensors.o: sensors.conf: label fan3 "Fan 1 Tach"
[ 987.802437] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802439] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802444] bmcsensors.o: registering sensor 14: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802447] bmcsensors.o: sensors.conf: label fan4 "Fan 3 Tach"
[ 987.802449] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802451] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802457] bmcsensors.o: registering sensor 15: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
[ 987.802459] bmcsensors.o: sensors.conf: label fan5 "Fan 5 Tach"
[ 987.802461] bmcsensors.o: using lower critical threshold for upper limit
[ 987.802463] bmcsensors.o: using upper critical threshold for lower limit
[ 987.802468] bmcsensors.o: 0 reservations cancelled
[ 987.802470] bmcsensors.o: registered 4 temp, 7 volt, 0 current, 5 fan sensors
[ 987.802472] bmcsensors.o: bmcsensor thread done
[ 1007.059503] general protection fault: 0000 [1] SMP
[ 1007.059511] CPU 1
[ 1007.059514] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport
autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid
ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
[ 1007.059533] Pid: 3655, comm: sensors Not tainted 2.6.13-rc6
[ 1007.059535] RIP: 0010:[<ffffffff801fed50>] <ffffffff801fed50>{strcmp+0}
[ 1007.059547] RSP: 0018:ffff810071653cb0 EFLAGS: 00010246
[ 1007.059552] RAX: ffff000a36343735 RBX: ffff81003596f608 RCX: ffff8100328f96d0
[ 1007.059555] RDX: 0000000000000037 RSI: ffff8100710ac9cc RDI: ffff000a36343735
[ 1007.059560] RBP: ffff8100328f9680 R08: 000003fa892e45c7 R09: ffff81003535301c
[ 1007.059563] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8100710ac910
[ 1007.059567] R13: ffff810071653d48 R14: ffff810036776d70 R15: ffff810076d33bf0
[ 1007.059571] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:00000000627c2bb0
[ 1007.059574] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1007.059577] CR2: 00002aaaadb48000 CR3: 0000000071725000 CR4: 00000000000006e0
[ 1007.059581] Process sensors (pid: 3655, threadinfo ffff810071652000, task ffff810035c58a20)
[ 1007.059583] Stack: ffffffff801c59d1 ffff8100710ac910 ffff810071653ed8 ffff810071653d38
[ 1007.059590] ffff810071653d48 ffff810036776d70 ffffffff80192565 000001b600008001
[ 1007.059596] ffff810037ff7080 ffff810036776cb0
[ 1007.059599] Call Trace:<ffffffff801c59d1>{sysfs_lookup+81} <ffffffff80192565>{do_lookup+245}
[ 1007.059614] <ffffffff80193076>{__link_path_walk+2582} <ffffffff80193659>{link_path_walk+137}
[ 1007.059626] <ffffffff801818b3>{get_unused_fd+227} <ffffffff8014a509>{remove_wait_queue+25}
[ 1007.059640] <ffffffff80193c9d>{path_lookup+461} <ffffffff801951cc>{open_namei+172}
[ 1007.059649] <ffffffff8025867a>{tty_ldisc_deref+122} <ffffffff8018261d>{filp_open+45}
[ 1007.059660] <ffffffff80182712>{sys_open+82} <ffffffff8010dcf2>{system_call+126}
[ 1007.059673]
[ 1007.059678]
[ 1007.059678] Code: 0f b6 17 89 d0 2a 06 48 ff c6 84 c0 74 04 0f be c0 c3 48 ff
[ 1007.059687] RIP <ffffffff801fed50>{strcmp+0} RSP <ffff810071653cb0>
[ 1007.059693]
---------------
Martin
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
(?)
@ 2005-08-08 19:25 ` Yani Ioannou
-1 siblings, 0 replies; 9+ messages in thread
From: Yani Ioannou @ 2005-08-08 19:25 UTC (permalink / raw)
To: lm-sensors
On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> Hi,
>
> I'm getting following general protection fault with bmcsensors and
> i2c-ipmi obtained from today's CVS and with 2.6.13-rc6 kernel. After that
> system doesn't seem to hang immediatelly (as I was able to do the dmesg
> below), however it seems that the internal IPMI watchdog restarted the
> system after a while (or perhaps it did it on its own?), since it did
> reboot then.
>
> ---------------
> [ 957.987401] bmcsensors.o
> [ 957.998712] i2c-ipmi.o
> [ 957.998719] i2c-ipmi.o: BMC access for i2c modules initialized.
> [ 958.001767] ipmi device interface version v33
> [ 958.004867] IPMI System Interface driver version v33, KCS version v33, SMIC version v33, BT version v33
> [ 958.005264] ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca2, slave address 0x20
> [ 959.172987] bmcsensors.o: Registered client, scanning for sensors...
> [ 959.172995] i2c-ipmi.o: Registered IPMI interface 0 with version 1.5
> [ 959.451432] IPMI Watchdog: Starting now!
> [ 959.451445] IPMI kcs interface initialized
> [ 987.802234] bmcsensors.o: all sensors detected
> [ 987.802260] bmcsensors.o: registering sensor 0: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
> [ 987.802264] bmcsensors.o: sensors.conf: label temp1 "Planar Temp 1"
> [ 987.802267] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802270] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802279] bmcsensors.o: registering sensor 1: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
> [ 987.802281] bmcsensors.o: sensors.conf: label temp2 "Planar Temp 2"
> [ 987.802283] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802286] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802291] bmcsensors.o: registering sensor 2: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
> [ 987.802294] bmcsensors.o: sensors.conf: label temp3 "CPU 2 Temp"
> [ 987.802296] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802298] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802306] bmcsensors.o: registering sensor 3: (type 0x01) (fmt=0; m=1; b=0; k1=0; k2=0; cap=0x76; mask=0x003f)
> [ 987.802309] bmcsensors.o: sensors.conf: label temp4 "CPU 1 Temp"
> [ 987.802311] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802313] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802319] bmcsensors.o: registering sensor 4: (type 0x02) (fmt=0; mc; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802321] bmcsensors.o: sensors.conf: label in1 "Planar 12V"
> [ 987.802323] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802325] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802331] bmcsensors.o: registering sensor 5: (type 0x02) (fmt=0; m\x12; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802334] bmcsensors.o: sensors.conf: label in2 "CPU 2 VCore"
> [ 987.802336] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802338] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802344] bmcsensors.o: registering sensor 6: (type 0x02) (fmt=0; m\x13; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802346] bmcsensors.o: sensors.conf: label in3 "CPU 2 2.5V"
> [ 987.802348] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802350] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802356] bmcsensors.o: registering sensor 7: (type 0x02) (fmt=0; m&; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802359] bmcsensors.o: sensors.conf: label in4 "Planar 5VSB"
> [ 987.802361] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802363] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802369] bmcsensors.o: registering sensor 8: (type 0x02) (fmt=0; m\x12; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802371] bmcsensors.o: sensors.conf: label in5 "CPU 1 VCore"
> [ 987.802373] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802375] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802381] bmcsensors.o: registering sensor 9: (type 0x02) (fmt=0; m\x13; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802384] bmcsensors.o: sensors.conf: label in6 "CPU 1 2.5V"
> [ 987.802386] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802388] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802393] bmcsensors.o: registering sensor 10: (type 0x02) (fmt=0; m&; b=0; k1=0; k2\x13; cap=0x76; mask=0x003f)
> [ 987.802396] bmcsensors.o: sensors.conf: label in7 "Planar 5V"
> [ 987.802398] bmcsensors.o: using upper critical threshold for upper limit
> [ 987.802400] bmcsensors.o: using lower critical threshold for lower limit
> [ 987.802406] bmcsensors.o: registering sensor 11: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
> [ 987.802409] bmcsensors.o: sensors.conf: label fan1 "Fan 2 Tach"
> [ 987.802411] bmcsensors.o: using lower critical threshold for upper limit
> [ 987.802413] bmcsensors.o: using upper critical threshold for lower limit
> [ 987.802418] bmcsensors.o: registering sensor 12: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
> [ 987.802421] bmcsensors.o: sensors.conf: label fan2 "Fan 4 Tach"
> [ 987.802423] bmcsensors.o: using lower critical threshold for upper limit
> [ 987.802425] bmcsensors.o: using upper critical threshold for lower limit
> [ 987.802432] bmcsensors.o: registering sensor 13: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
> [ 987.802435] bmcsensors.o: sensors.conf: label fan3 "Fan 1 Tach"
> [ 987.802437] bmcsensors.o: using lower critical threshold for upper limit
> [ 987.802439] bmcsensors.o: using upper critical threshold for lower limit
> [ 987.802444] bmcsensors.o: registering sensor 14: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
> [ 987.802447] bmcsensors.o: sensors.conf: label fan4 "Fan 3 Tach"
> [ 987.802449] bmcsensors.o: using lower critical threshold for upper limit
> [ 987.802451] bmcsensors.o: using upper critical threshold for lower limit
> [ 987.802457] bmcsensors.o: registering sensor 15: (type 0x04) (fmt=0; m); b=0; k1=0; k2=9; cap=0x76; mask=0x003f)
> [ 987.802459] bmcsensors.o: sensors.conf: label fan5 "Fan 5 Tach"
> [ 987.802461] bmcsensors.o: using lower critical threshold for upper limit
> [ 987.802463] bmcsensors.o: using upper critical threshold for lower limit
> [ 987.802468] bmcsensors.o: 0 reservations cancelled
> [ 987.802470] bmcsensors.o: registered 4 temp, 7 volt, 0 current, 5 fan sensors
> [ 987.802472] bmcsensors.o: bmcsensor thread done
> [ 1007.059503] general protection fault: 0000 [1] SMP
> [ 1007.059511] CPU 1
> [ 1007.059514] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport
> autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid
> ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
> [ 1007.059533] Pid: 3655, comm: sensors Not tainted 2.6.13-rc6
> [ 1007.059535] RIP: 0010:[<ffffffff801fed50>] <ffffffff801fed50>{strcmp+0}
> [ 1007.059547] RSP: 0018:ffff810071653cb0 EFLAGS: 00010246
> [ 1007.059552] RAX: ffff000a36343735 RBX: ffff81003596f608 RCX: ffff8100328f96d0
> [ 1007.059555] RDX: 0000000000000037 RSI: ffff8100710ac9cc RDI: ffff000a36343735
> [ 1007.059560] RBP: ffff8100328f9680 R08: 000003fa892e45c7 R09: ffff81003535301c
> [ 1007.059563] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8100710ac910
> [ 1007.059567] R13: ffff810071653d48 R14: ffff810036776d70 R15: ffff810076d33bf0
> [ 1007.059571] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:00000000627c2bb0
> [ 1007.059574] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 1007.059577] CR2: 00002aaaadb48000 CR3: 0000000071725000 CR4: 00000000000006e0
> [ 1007.059581] Process sensors (pid: 3655, threadinfo ffff810071652000, task ffff810035c58a20)
> [ 1007.059583] Stack: ffffffff801c59d1 ffff8100710ac910 ffff810071653ed8 ffff810071653d38
> [ 1007.059590] ffff810071653d48 ffff810036776d70 ffffffff80192565 000001b600008001
> [ 1007.059596] ffff810037ff7080 ffff810036776cb0
> [ 1007.059599] Call Trace:<ffffffff801c59d1>{sysfs_lookup+81} <ffffffff80192565>{do_lookup+245}
> [ 1007.059614] <ffffffff80193076>{__link_path_walk+2582} <ffffffff80193659>{link_path_walk+137}
> [ 1007.059626] <ffffffff801818b3>{get_unused_fd+227} <ffffffff8014a509>{remove_wait_queue+25}
> [ 1007.059640] <ffffffff80193c9d>{path_lookup+461} <ffffffff801951cc>{open_namei+172}
> [ 1007.059649] <ffffffff8025867a>{tty_ldisc_deref+122} <ffffffff8018261d>{filp_open+45}
> [ 1007.059660] <ffffffff80182712>{sys_open+82} <ffffffff8010dcf2>{system_call+126}
> [ 1007.059673]
> [ 1007.059678]
> [ 1007.059678] Code: 0f b6 17 89 d0 2a 06 48 ff c6 84 c0 74 04 0f be c0 c3 48 ff
> [ 1007.059687] RIP <ffffffff801fed50>{strcmp+0} RSP <ffff810071653cb0>
> [ 1007.059693]
> ---------------
>
> Martin
>
>
Hi Martin,
I haven't had a chance to test the CVS version of bmcsensors yet on my
IPMI machines (hence why its not released), but it basically differs
in a patch submitted by someone to use the i2c_client addr instead of
the now defunct id.
What version of sensors are you using? It looks like its crashing
while trying to read the sysfs attributes, try cating the sysfs
entries the driver creates and see if you can see anything unusual.
Thanks,
Yani
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
(?)
(?)
@ 2005-08-08 21:51 ` Martin Drab
-1 siblings, 0 replies; 9+ messages in thread
From: Martin Drab @ 2005-08-08 21:51 UTC (permalink / raw)
To: lm-sensors
On Mon, 8 Aug 2005, Yani Ioannou wrote:
> On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> >
> > I'm getting following general protection fault with bmcsensors and
> > i2c-ipmi obtained from today's CVS and with 2.6.13-rc6 kernel. After that
> > system doesn't seem to hang immediatelly (as I was able to do the dmesg
> > below), however it seems that the internal IPMI watchdog restarted the
> > system after a while (or perhaps it did it on its own?), since it did
> > reboot then.
> >
> > ---------------
...
> > [ 1007.059503] general protection fault: 0000 [1] SMP
> > [ 1007.059511] CPU 1
> > [ 1007.059514] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport
> > autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid
> > ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
> > [ 1007.059533] Pid: 3655, comm: sensors Not tainted 2.6.13-rc6
> > [ 1007.059535] RIP: 0010:[<ffffffff801fed50>] <ffffffff801fed50>{strcmp+0}
> > [ 1007.059547] RSP: 0018:ffff810071653cb0 EFLAGS: 00010246
> > [ 1007.059552] RAX: ffff000a36343735 RBX: ffff81003596f608 RCX: ffff8100328f96d0
> > [ 1007.059555] RDX: 0000000000000037 RSI: ffff8100710ac9cc RDI: ffff000a36343735
> > [ 1007.059560] RBP: ffff8100328f9680 R08: 000003fa892e45c7 R09: ffff81003535301c
> > [ 1007.059563] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8100710ac910
> > [ 1007.059567] R13: ffff810071653d48 R14: ffff810036776d70 R15: ffff810076d33bf0
> > [ 1007.059571] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:00000000627c2bb0
> > [ 1007.059574] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 1007.059577] CR2: 00002aaaadb48000 CR3: 0000000071725000 CR4: 00000000000006e0
> > [ 1007.059581] Process sensors (pid: 3655, threadinfo ffff810071652000, task ffff810035c58a20)
> > [ 1007.059583] Stack: ffffffff801c59d1 ffff8100710ac910 ffff810071653ed8 ffff810071653d38
> > [ 1007.059590] ffff810071653d48 ffff810036776d70 ffffffff80192565 000001b600008001
> > [ 1007.059596] ffff810037ff7080 ffff810036776cb0
> > [ 1007.059599] Call Trace:<ffffffff801c59d1>{sysfs_lookup+81} <ffffffff80192565>{do_lookup+245}
> > [ 1007.059614] <ffffffff80193076>{__link_path_walk+2582} <ffffffff80193659>{link_path_walk+137}
> > [ 1007.059626] <ffffffff801818b3>{get_unused_fd+227} <ffffffff8014a509>{remove_wait_queue+25}
> > [ 1007.059640] <ffffffff80193c9d>{path_lookup+461} <ffffffff801951cc>{open_namei+172}
> > [ 1007.059649] <ffffffff8025867a>{tty_ldisc_deref+122} <ffffffff8018261d>{filp_open+45}
> > [ 1007.059660] <ffffffff80182712>{sys_open+82} <ffffffff8010dcf2>{system_call+126}
> > [ 1007.059673]
> > [ 1007.059678]
> > [ 1007.059678] Code: 0f b6 17 89 d0 2a 06 48 ff c6 84 c0 74 04 0f be c0 c3 48 ff
> > [ 1007.059687] RIP <ffffffff801fed50>{strcmp+0} RSP <ffff810071653cb0>
> > [ 1007.059693]
> > ---------------
>
> I haven't had a chance to test the CVS version of bmcsensors yet on my
> IPMI machines (hence why its not released), but it basically differs
> in a patch submitted by someone to use the i2c_client addr instead of
> the now defunct id.
None of the kernel patches work for recent kernels. I'm not entirely sure
since when exactly it began, but from a certain point those patches on
the sf.net cased to work properly and began to crash like that.
Recently there were some fixes that needed to be done in order to make
those patches on sf.net compile (changes in i2c structures), but though it
compiled, it crashed.
So I thought I'll try the CVS bmcsensors-26. Those compiled without a
problem (that's probably the patch you are referring to and perhaps
simillar that I was using), but it crashes the same way as well. So I
think there may be some other problem introduced somewhere else in recent
kernels. Tomorrow when I get a chance to safely reboot the server I may
try to find when it was last working. From what I can briefly see from the
past kernel logs, it seems to have been working with the kernel 2.6.12.2,
then I tried the 2.6.13-rc4-git4 and it crashed allready. (Both had to be
patched to compile and for both I used the same patch.)
> What version of sensors are you using? It looks like its crashing
It's
sensors version 2.8.8 with libsensors version 2.8.8
from the FC4's lm_sensors-2.8.8-5.x86_64.rpm. But I'm not so sure that
sensors have anything to do with the crash, since it's the kernel that
crashes, not the application. Kernel shouldn't crash no matter what the
application does.
> while trying to read the sysfs attributes, try cating the sysfs
> entries the driver creates and see if you can see anything unusual.
I'll try that tomorrow as well, but since from the trace above it seem
that the sensors were doing the sysfs inspection as well, I think it would
also produce the crash.
Martin
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
` (2 preceding siblings ...)
(?)
@ 2005-08-09 0:59 ` Yani Ioannou
-1 siblings, 0 replies; 9+ messages in thread
From: Yani Ioannou @ 2005-08-09 0:59 UTC (permalink / raw)
To: lm-sensors
On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> None of the kernel patches work for recent kernels. I'm not entirely sure
> since when exactly it began, but from a certain point those patches on
> the sf.net cased to work properly and began to crash like that.
>
> Recently there were some fixes that needed to be done in order to make
> those patches on sf.net compile (changes in i2c structures), but though it
> compiled, it crashed.
>
> So I thought I'll try the CVS bmcsensors-26. Those compiled without a
> problem (that's probably the patch you are referring to and perhaps
> simillar that I was using), but it crashes the same way as well. So I
> think there may be some other problem introduced somewhere else in recent
> kernels. Tomorrow when I get a chance to safely reboot the server I may
> try to find when it was last working. From what I can briefly see from the
> past kernel logs, it seems to have been working with the kernel 2.6.12.2,
> then I tried the 2.6.13-rc4-git4 and it crashed allready. (Both had to be
> patched to compile and for both I used the same patch.)
lol..indeed the problem is something that was introduced into the
kernel at 2.6.13-rc1 - a change by myself :-). The sysfs callbacks
need to be updated (you should have got warnings complaining of an
invalid function pointer when you compiled the module) for newer
kernels, I'll fix that now, and commit it to CVS so you can try it out
tomorrow, and I will try to test this out on my own machines tonight
too.
I'm not paying much attention to bmcsensors at the moment because I'm
busier trying to get changes into the kernel so that I can re-write
the driver (ipmi-sensors) and get it included in mainline.
Thanks,
Yani
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
` (3 preceding siblings ...)
(?)
@ 2005-08-09 1:26 ` Martin Drab
-1 siblings, 0 replies; 9+ messages in thread
From: Martin Drab @ 2005-08-09 1:26 UTC (permalink / raw)
To: lm-sensors
On Mon, 8 Aug 2005, Yani Ioannou wrote:
> On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> > None of the kernel patches work for recent kernels. I'm not entirely sure
> > since when exactly it began, but from a certain point those patches on
> > the sf.net cased to work properly and began to crash like that.
> >
> > Recently there were some fixes that needed to be done in order to make
> > those patches on sf.net compile (changes in i2c structures), but though it
> > compiled, it crashed.
> >
> > So I thought I'll try the CVS bmcsensors-26. Those compiled without a
> > problem (that's probably the patch you are referring to and perhaps
> > simillar that I was using), but it crashes the same way as well. So I
> > think there may be some other problem introduced somewhere else in recent
> > kernels. Tomorrow when I get a chance to safely reboot the server I may
> > try to find when it was last working. From what I can briefly see from the
> > past kernel logs, it seems to have been working with the kernel 2.6.12.2,
> > then I tried the 2.6.13-rc4-git4 and it crashed allready. (Both had to be
> > patched to compile and for both I used the same patch.)
>
> lol..indeed the problem is something that was introduced into the
> kernel at 2.6.13-rc1 - a change by myself :-). The sysfs callbacks
> need to be updated (you should have got warnings complaining of an
> invalid function pointer when you compiled the module) for newer
You're right. I should have paid more attention to it. (But since GCC 4.x
usually warns about lot's of things during kernel compilation, I didn't
even read it as long as there are no errors. :( I guess I should. :)
> kernels, I'll fix that now, and commit it to CVS so you can try it out
> tomorrow, and I will try to test this out on my own machines tonight
> too.
That would be great, thanks.
> I'm not paying much attention to bmcsensors at the moment because I'm
> busier trying to get changes into the kernel so that I can re-write
> the driver (ipmi-sensors) and get it included in mainline.
Excellent! So don't let me distract you too much from that. ;-)
BTW, just a silly question: Is there a reason why I can't get the limit
values for each sensor from the driver? I get just the immediate values of
temperatures, fan speeds, etc., but all the limits are just set to 0. Is
it that the server management card (MSI-9549) doesn't support/export them
(that would be quite odd), or is it that the function just isn't
implemented in the driver yet?
Martin
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
` (4 preceding siblings ...)
(?)
@ 2005-08-10 17:11 ` Martin Drab
-1 siblings, 0 replies; 9+ messages in thread
From: Martin Drab @ 2005-08-10 17:11 UTC (permalink / raw)
To: lm-sensors
On Mon, 8 Aug 2005, Yani Ioannou wrote:
> On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> > None of the kernel patches work for recent kernels. I'm not entirely sure
> > since when exactly it began, but from a certain point those patches on
> > the sf.net cased to work properly and began to crash like that.
> >
> > Recently there were some fixes that needed to be done in order to make
> > those patches on sf.net compile (changes in i2c structures), but though it
> > compiled, it crashed.
> >
> > So I thought I'll try the CVS bmcsensors-26. Those compiled without a
> > problem (that's probably the patch you are referring to and perhaps
> > simillar that I was using), but it crashes the same way as well. So I
> > think there may be some other problem introduced somewhere else in recent
> > kernels. Tomorrow when I get a chance to safely reboot the server I may
> > try to find when it was last working. From what I can briefly see from the
> > past kernel logs, it seems to have been working with the kernel 2.6.12.2,
> > then I tried the 2.6.13-rc4-git4 and it crashed allready. (Both had to be
> > patched to compile and for both I used the same patch.)
>
> lol..indeed the problem is something that was introduced into the
> kernel at 2.6.13-rc1 - a change by myself :-). The sysfs callbacks
> need to be updated (you should have got warnings complaining of an
> invalid function pointer when you compiled the module) for newer
> kernels, I'll fix that now, and commit it to CVS so you can try it out
> tomorrow, and I will try to test this out on my own machines tonight
> too.
I've tested the current CVS again. It seems to be updated, and it no
longer gives the compile warnings. But still it produces a crash. although
the system isn't frozen, unless the IPMI watchdog is enabled, which runs
out and reboots the comp. When I disable it, the system runs on. So,
perhaps just the IPMI part crashes and the watchdog is no longer
refreshed.
Anyway, the crash again occurs when you try to read the sensors
values (either directly through sysfs or using sensors) now produces this:
---------------
Aug 10 16:58:39 neutron kernel: [ 672.694754] Unable to handle kernel paging request at ffffffff89feb91c RIP:
Aug 10 16:58:39 neutron kernel: [ 672.694942] <ffffffff881e77cc>{:bmcsensors:show_sensor+44}
Aug 10 16:58:39 neutron kernel: [ 672.719842] PGD 103027 PUD 105027 PMD 0
Aug 10 16:58:39 neutron kernel: [ 672.719847] Oops: 0000 [1] SMP
Aug 10 16:58:39 neutron kernel: [ 672.719850] CPU 1
Aug 10 16:58:39 neutron kernel: [ 672.719852] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
Aug 10 16:58:39 neutron kernel: [ 672.719868] Pid: 3364, comm: sensors Not tainted 2.6.13-rc6
Aug 10 16:58:39 neutron kernel: [ 672.719870] RIP: 0010:[<ffffffff881e77cc>] <ffffffff881e77cc>{:bmcsensors:show_sensor+44}
Aug 10 16:58:39 neutron kernel: [ 672.719878] RSP: 0018:ffff810076ff9ea8 EFLAGS: 00010216
Aug 10 16:58:39 neutron kernel: [ 672.719881] RAX: 0000000001dfff88 RBX: ffff810037c65240 RCX: fffffffffffffff4
Aug 10 16:58:39 neutron kernel: [ 672.719885] RDX: 00000000001ffff8 RSI: ffff810037c65240 RDI: ffffffff881eac00
Aug 10 16:58:39 neutron kernel: [ 672.719888] RBP: ffff810075f954a0 R08: ffff810040000000 R09: 0000000000000282
Aug 10 16:58:39 neutron kernel: [ 672.719891] R10: 0000000000000000 R11: ffffffff881e77a0 R12: ffff81007f3f0000
Aug 10 16:58:39 neutron kernel: [ 672.719895] R13: ffff810076ff9f50 R14: ffffffff80438440 R15: ffffffff881ead00
Aug 10 16:58:39 neutron kernel: [ 672.719899] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:0000000061b80bb0
Aug 10 16:58:39 neutron kernel: [ 672.719902] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 10 16:58:39 neutron kernel: [ 672.719905] CR2: ffffffff89feb91c CR3: 000000003b70d000 CR4: 00000000000006e0
Aug 10 16:58:39 neutron kernel: [ 672.719908] Process sensors (pid: 3364, threadinfo ffff810076ff8000, task ffff81003c54c070)
Aug 10 16:58:39 neutron kernel: [ 672.719910] Stack: ffffffff881ead00 ffff810075f95480 0000000000001000 ffffffff801c48af
Aug 10 16:58:39 neutron kernel: [ 672.719916] 0000000000000000 00002aaaadb48000 ffff810037c65240 ffff81007df09180
Aug 10 16:58:39 neutron kernel: [ 672.719921] 0000000000000000 0000000000001000
Aug 10 16:58:39 neutron kernel: [ 672.719923] Call Trace:<ffffffff801c48af>{sysfs_read_file+175} <ffffffff8018342b>{vfs_read+219}
Aug 10 16:58:39 neutron kernel: [ 672.719942] <ffffffff80183bf3>{sys_read+83} <ffffffff8010dcf2>{system_call+126}
Aug 10 16:58:40 neutron kernel: [ 672.719952]
Aug 10 16:58:40 neutron kernel: [ 672.719957]
Aug 10 16:58:40 neutron kernel: [ 672.719958] Code: 0f b6 b8 94 b9 1e 88 48 8d b0 60 b9 1e 88 e8 11 fe ff ff 4c
Aug 10 16:58:40 neutron kernel: [ 672.719965] RIP <ffffffff881e77cc>{:bmcsensors:show_sensor+44} RSP <ffff810076ff9ea8>
Aug 10 16:58:40 neutron kernel: [ 672.719972] CR2: ffffffff89feb91c
---------------
Is it possible you forgot to update something? Or is it a different bug?
Martin
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
` (5 preceding siblings ...)
(?)
@ 2005-08-10 17:36 ` Yani Ioannou
-1 siblings, 0 replies; 9+ messages in thread
From: Yani Ioannou @ 2005-08-10 17:36 UTC (permalink / raw)
To: lm-sensors
Hi,
I tested it out with 2.6.13-rc1, but I'll try it out with 2.6.13-rc6
and get back to you.
Yani
On 8/10/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> On Mon, 8 Aug 2005, Yani Ioannou wrote:
> > On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> > > None of the kernel patches work for recent kernels. I'm not entirely sure
> > > since when exactly it began, but from a certain point those patches on
> > > the sf.net cased to work properly and began to crash like that.
> > >
> > > Recently there were some fixes that needed to be done in order to make
> > > those patches on sf.net compile (changes in i2c structures), but though it
> > > compiled, it crashed.
> > >
> > > So I thought I'll try the CVS bmcsensors-26. Those compiled without a
> > > problem (that's probably the patch you are referring to and perhaps
> > > simillar that I was using), but it crashes the same way as well. So I
> > > think there may be some other problem introduced somewhere else in recent
> > > kernels. Tomorrow when I get a chance to safely reboot the server I may
> > > try to find when it was last working. From what I can briefly see from the
> > > past kernel logs, it seems to have been working with the kernel 2.6.12.2,
> > > then I tried the 2.6.13-rc4-git4 and it crashed allready. (Both had to be
> > > patched to compile and for both I used the same patch.)
> >
> > lol..indeed the problem is something that was introduced into the
> > kernel at 2.6.13-rc1 - a change by myself :-). The sysfs callbacks
> > need to be updated (you should have got warnings complaining of an
> > invalid function pointer when you compiled the module) for newer
> > kernels, I'll fix that now, and commit it to CVS so you can try it out
> > tomorrow, and I will try to test this out on my own machines tonight
> > too.
>
> I've tested the current CVS again. It seems to be updated, and it no
> longer gives the compile warnings. But still it produces a crash. although
> the system isn't frozen, unless the IPMI watchdog is enabled, which runs
> out and reboots the comp. When I disable it, the system runs on. So,
> perhaps just the IPMI part crashes and the watchdog is no longer
> refreshed.
>
> Anyway, the crash again occurs when you try to read the sensors
> values (either directly through sysfs or using sensors) now produces this:
>
> ---------------
> Aug 10 16:58:39 neutron kernel: [ 672.694754] Unable to handle kernel paging request at ffffffff89feb91c RIP:
> Aug 10 16:58:39 neutron kernel: [ 672.694942] <ffffffff881e77cc>{:bmcsensors:show_sensor+44}
> Aug 10 16:58:39 neutron kernel: [ 672.719842] PGD 103027 PUD 105027 PMD 0
> Aug 10 16:58:39 neutron kernel: [ 672.719847] Oops: 0000 [1] SMP
> Aug 10 16:58:39 neutron kernel: [ 672.719850] CPU 1
> Aug 10 16:58:39 neutron kernel: [ 672.719852] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
> Aug 10 16:58:39 neutron kernel: [ 672.719868] Pid: 3364, comm: sensors Not tainted 2.6.13-rc6
> Aug 10 16:58:39 neutron kernel: [ 672.719870] RIP: 0010:[<ffffffff881e77cc>] <ffffffff881e77cc>{:bmcsensors:show_sensor+44}
> Aug 10 16:58:39 neutron kernel: [ 672.719878] RSP: 0018:ffff810076ff9ea8 EFLAGS: 00010216
> Aug 10 16:58:39 neutron kernel: [ 672.719881] RAX: 0000000001dfff88 RBX: ffff810037c65240 RCX: fffffffffffffff4
> Aug 10 16:58:39 neutron kernel: [ 672.719885] RDX: 00000000001ffff8 RSI: ffff810037c65240 RDI: ffffffff881eac00
> Aug 10 16:58:39 neutron kernel: [ 672.719888] RBP: ffff810075f954a0 R08: ffff810040000000 R09: 0000000000000282
> Aug 10 16:58:39 neutron kernel: [ 672.719891] R10: 0000000000000000 R11: ffffffff881e77a0 R12: ffff81007f3f0000
> Aug 10 16:58:39 neutron kernel: [ 672.719895] R13: ffff810076ff9f50 R14: ffffffff80438440 R15: ffffffff881ead00
> Aug 10 16:58:39 neutron kernel: [ 672.719899] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:0000000061b80bb0
> Aug 10 16:58:39 neutron kernel: [ 672.719902] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> Aug 10 16:58:39 neutron kernel: [ 672.719905] CR2: ffffffff89feb91c CR3: 000000003b70d000 CR4: 00000000000006e0
> Aug 10 16:58:39 neutron kernel: [ 672.719908] Process sensors (pid: 3364, threadinfo ffff810076ff8000, task ffff81003c54c070)
> Aug 10 16:58:39 neutron kernel: [ 672.719910] Stack: ffffffff881ead00 ffff810075f95480 0000000000001000 ffffffff801c48af
> Aug 10 16:58:39 neutron kernel: [ 672.719916] 0000000000000000 00002aaaadb48000 ffff810037c65240 ffff81007df09180
> Aug 10 16:58:39 neutron kernel: [ 672.719921] 0000000000000000 0000000000001000
> Aug 10 16:58:39 neutron kernel: [ 672.719923] Call Trace:<ffffffff801c48af>{sysfs_read_file+175} <ffffffff8018342b>{vfs_read+219}
> Aug 10 16:58:39 neutron kernel: [ 672.719942] <ffffffff80183bf3>{sys_read+83} <ffffffff8010dcf2>{system_call+126}
> Aug 10 16:58:40 neutron kernel: [ 672.719952]
> Aug 10 16:58:40 neutron kernel: [ 672.719957]
> Aug 10 16:58:40 neutron kernel: [ 672.719958] Code: 0f b6 b8 94 b9 1e 88 48 8d b0 60 b9 1e 88 e8 11 fe ff ff 4c
> Aug 10 16:58:40 neutron kernel: [ 672.719965] RIP <ffffffff881e77cc>{:bmcsensors:show_sensor+44} RSP <ffff810076ff9ea8>
> Aug 10 16:58:40 neutron kernel: [ 672.719972] CR2: ffffffff89feb91c
> ---------------
>
> Is it possible you forgot to update something? Or is it a different bug?
>
> Martin
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* [lm-sensors] Re: General Protection Fault with bcmsensors
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
` (6 preceding siblings ...)
(?)
@ 2005-08-13 7:22 ` Yani Ioannou
-1 siblings, 0 replies; 9+ messages in thread
From: Yani Ioannou @ 2005-08-13 7:22 UTC (permalink / raw)
To: lm-sensors
Hi Martin,
On 8/10/05, Yani Ioannou <yani.ioannou@gmail.com> wrote:
> Hi,
>
> I tested it out with 2.6.13-rc1, but I'll try it out with 2.6.13-rc6
> and get back to you.
>
> Yani
>
> On 8/10/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> > On Mon, 8 Aug 2005, Yani Ioannou wrote:
> > > On 8/8/05, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> > > > None of the kernel patches work for recent kernels. I'm not entirely sure
> > > > since when exactly it began, but from a certain point those patches on
> > > > the sf.net cased to work properly and began to crash like that.
> > > >
> > > > Recently there were some fixes that needed to be done in order to make
> > > > those patches on sf.net compile (changes in i2c structures), but though it
> > > > compiled, it crashed.
> > > >
> > > > So I thought I'll try the CVS bmcsensors-26. Those compiled without a
> > > > problem (that's probably the patch you are referring to and perhaps
> > > > simillar that I was using), but it crashes the same way as well. So I
> > > > think there may be some other problem introduced somewhere else in recent
> > > > kernels. Tomorrow when I get a chance to safely reboot the server I may
> > > > try to find when it was last working. From what I can briefly see from the
> > > > past kernel logs, it seems to have been working with the kernel 2.6.12.2,
> > > > then I tried the 2.6.13-rc4-git4 and it crashed allready. (Both had to be
> > > > patched to compile and for both I used the same patch.)
> > >
> > > lol..indeed the problem is something that was introduced into the
> > > kernel at 2.6.13-rc1 - a change by myself :-). The sysfs callbacks
> > > need to be updated (you should have got warnings complaining of an
> > > invalid function pointer when you compiled the module) for newer
> > > kernels, I'll fix that now, and commit it to CVS so you can try it out
> > > tomorrow, and I will try to test this out on my own machines tonight
> > > too.
> >
> > I've tested the current CVS again. It seems to be updated, and it no
> > longer gives the compile warnings. But still it produces a crash. although
> > the system isn't frozen, unless the IPMI watchdog is enabled, which runs
> > out and reboots the comp. When I disable it, the system runs on. So,
> > perhaps just the IPMI part crashes and the watchdog is no longer
> > refreshed.
> >
> > Anyway, the crash again occurs when you try to read the sensors
> > values (either directly through sysfs or using sensors) now produces this:
> >
> > ---------------
> > Aug 10 16:58:39 neutron kernel: [ 672.694754] Unable to handle kernel paging request at ffffffff89feb91c RIP:
> > Aug 10 16:58:39 neutron kernel: [ 672.694942] <ffffffff881e77cc>{:bmcsensors:show_sensor+44}
> > Aug 10 16:58:39 neutron kernel: [ 672.719842] PGD 103027 PUD 105027 PMD 0
> > Aug 10 16:58:39 neutron kernel: [ 672.719847] Oops: 0000 [1] SMP
> > Aug 10 16:58:39 neutron kernel: [ 672.719850] CPU 1
> > Aug 10 16:58:39 neutron kernel: [ 672.719852] Modules linked in: ipmi_si ipmi_devintf i2c_ipmi bmcsensors i2c_isa i2c_amd756 nfsd exportfs lockd nfs_acl parport_pc lp parport autofs4 sunrpc powernow_k8 freq_table binfmt_misc dm_mod video thermal processor hotkey fan container button battery ac ipv6 usbkbd usbhid ohci_hcd i2c_amd8111 i2c_core hw_random shpchp tg3 ide_cd cdrom sg usbcore ext3 jbd sd_mod
> > Aug 10 16:58:39 neutron kernel: [ 672.719868] Pid: 3364, comm: sensors Not tainted 2.6.13-rc6
> > Aug 10 16:58:39 neutron kernel: [ 672.719870] RIP: 0010:[<ffffffff881e77cc>] <ffffffff881e77cc>{:bmcsensors:show_sensor+44}
> > Aug 10 16:58:39 neutron kernel: [ 672.719878] RSP: 0018:ffff810076ff9ea8 EFLAGS: 00010216
> > Aug 10 16:58:39 neutron kernel: [ 672.719881] RAX: 0000000001dfff88 RBX: ffff810037c65240 RCX: fffffffffffffff4
> > Aug 10 16:58:39 neutron kernel: [ 672.719885] RDX: 00000000001ffff8 RSI: ffff810037c65240 RDI: ffffffff881eac00
> > Aug 10 16:58:39 neutron kernel: [ 672.719888] RBP: ffff810075f954a0 R08: ffff810040000000 R09: 0000000000000282
> > Aug 10 16:58:39 neutron kernel: [ 672.719891] R10: 0000000000000000 R11: ffffffff881e77a0 R12: ffff81007f3f0000
> > Aug 10 16:58:39 neutron kernel: [ 672.719895] R13: ffff810076ff9f50 R14: ffffffff80438440 R15: ffffffff881ead00
> > Aug 10 16:58:39 neutron kernel: [ 672.719899] FS: 00002aaaaaad9e40(0000) GS:ffffffff80541880(0000) knlGS:0000000061b80bb0
> > Aug 10 16:58:39 neutron kernel: [ 672.719902] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > Aug 10 16:58:39 neutron kernel: [ 672.719905] CR2: ffffffff89feb91c CR3: 000000003b70d000 CR4: 00000000000006e0
> > Aug 10 16:58:39 neutron kernel: [ 672.719908] Process sensors (pid: 3364, threadinfo ffff810076ff8000, task ffff81003c54c070)
> > Aug 10 16:58:39 neutron kernel: [ 672.719910] Stack: ffffffff881ead00 ffff810075f95480 0000000000001000 ffffffff801c48af
> > Aug 10 16:58:39 neutron kernel: [ 672.719916] 0000000000000000 00002aaaadb48000 ffff810037c65240 ffff81007df09180
> > Aug 10 16:58:39 neutron kernel: [ 672.719921] 0000000000000000 0000000000001000
> > Aug 10 16:58:39 neutron kernel: [ 672.719923] Call Trace:<ffffffff801c48af>{sysfs_read_file+175} <ffffffff8018342b>{vfs_read+219}
> > Aug 10 16:58:39 neutron kernel: [ 672.719942] <ffffffff80183bf3>{sys_read+83} <ffffffff8010dcf2>{system_call+126}
> > Aug 10 16:58:40 neutron kernel: [ 672.719952]
> > Aug 10 16:58:40 neutron kernel: [ 672.719957]
> > Aug 10 16:58:40 neutron kernel: [ 672.719958] Code: 0f b6 b8 94 b9 1e 88 48 8d b0 60 b9 1e 88 e8 11 fe ff ff 4c
> > Aug 10 16:58:40 neutron kernel: [ 672.719965] RIP <ffffffff881e77cc>{:bmcsensors:show_sensor+44} RSP <ffff810076ff9ea8>
> > Aug 10 16:58:40 neutron kernel: [ 672.719972] CR2: ffffffff89feb91c
> > ---------------
> >
> > Is it possible you forgot to update something? Or is it a different bug?
> >
> > Martin
> >
> >
>
Indeed with 2.6.13-rc6 I have the same problem, but I highly suspect
it has to do with the new hwmon patch. To move bmcsensors to hwmon
though I need a device struct in the IPMI subsystem to hang
device_attributes off and that brings us back to the same place the
re-write (ipmi-sensors) is stuck at right now (see my updated web page
at http://bmcsensors-26.sourceforge.net/).
I have quite a bit of work done on adding the driver model to the IPMI
subsystem, but it is not in any state to be submitted yet, and I won't
have the time to work on it for a week :-(.
Yani
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2005-08-13 7:22 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-08 15:30 General Protection Fault with bcmsensors Martin Drab
2005-08-08 17:31 ` [lm-sensors] " Martin Drab
2005-08-08 19:25 ` [lm-sensors] " Yani Ioannou
2005-08-08 21:51 ` Martin Drab
2005-08-09 0:59 ` Yani Ioannou
2005-08-09 1:26 ` Martin Drab
2005-08-10 17:11 ` Martin Drab
2005-08-10 17:36 ` Yani Ioannou
2005-08-13 7:22 ` Yani Ioannou
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.