-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I use the stable kernel tree 2.4 and have reproduce the following bug
with 2.4.36.2 and 2.4.36.7.

I got a new barcode scanner and plugged it into USB. The scanner works
well until I remove it. In that second I get a trace and the kernel
freeze.

The message when I plug in the scanner:
 hub.c: new USB device 00:1d.7-6.2, assigned address 5
 input: USB HID v1.10 Keyboard [Weltrend Bar Code Reader] on usb1:5.0

The message when I unplug it:
 Unable to handle kernel NULL pointer dereference at virtual address 00000048
 ...

Please pardon that I do not type the complete kernel dump as I know no
way to log it to a text file in this case where the system freeze. But
on request I can send the picture I made with my camera.

Regards
   Klaus Ethgen
- -- 
Klaus Ethgen                            http://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSOjgGZ+OKpjRpO3lAQL8cwf/ZyfKmgqXqMxIFa3yvTpLoDyUPq+Tmopb
A+sdoqb4F57r00YDsewZulGQ+gFlWHLu7RJENQ7HRtOVIIsW89TSniqVaWhBecKe
y7yZcEv8jCyI+RlGdyY8ZtcTDJSpLh9AY99q48PJLQ9Zxbe5FlOhELaJ1eVYAHHT
NhbeEiVk9BKo7MpsbiQeMr+lb2ePE7x0Ct1J2NBMCMnv9/BrYfPZQXf9ML9bhqgb
ZJC0gM4luJ3OCFP29ygCfyUES9D04KcFoI2S+bSG1nhFSSmYzrNNoDEk3+FO5+E2
e7bD5/nYWoCdRFFAhE08lGrx/cnrSBBZjaOwl1MhZSOCYjMDgLn9UA==
=owdm
-----END PGP SIGNATURE-----
--

[ message continues ]

Hello Klaus,


Does it happen everytime you unplug it or only once in a while ? Also,

Does the same problem happen when you plug/unplug a USB keyboard on the

Yes, it would help a lot. That along with your kernel config and an
lsmod and dmesg outputs before the problem. Ideally, you should pass
the messages output through ksymoops with all modules loaded as before
the problem happens. If you want to more easily capture your messages,
you can connect another machine to your serial port and boot with
"console=ttyS0".

Regards,
Willy

--

[ message continues ]

--jL2BoiuKMElzg3CS
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline


Everytime.

Well, thats not that true. It WAS everytime until I close all
applications and did sync several times before I unplug the device. When

I did buy the scanner only days ago. I did not use older kernels since



Thats not possible as I did not compile the serial console into the
kernel.

Regards
   Klaus Ethgen
-- 
Klaus Ethgen                            http://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B

--jL2BoiuKMElzg3CS
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: attachment; filename="lsmod.txt"

Module                  Size  Used by    Tainted: P  
keybdev                 2020   0  (unused)
agpgart                18792   3  (autoclean)
binfmt_misc             6088   1 
openafs               538240   3 
nfs                    73820   1 
audio                  43832   0  (autoclean) (unused)
nfsd                   72688   8 
lockd                  48616   1  [nfs nfsd]
sunrpc                 66784   1  [nfs nfsd lockd]
thermal                 6108   0 
fan                     1496   0  (unused)
button                  2596   0  (unused)
processor               8080   0  [thermal]
ac                      1688   0 
battery                 5016   0 
softdog                 1704   3 
blowfish                8844   2  (autoclean)
serial                 48420   0  (autoclean)
iptable_mangle          2168   0  (autoclean) (unused)
ip_tables              12416   1  [iptable_mangle]
af_packet              13192   0  (autoclean)
hid                    22180   0  (unused)
input                   3424   0  [keybdev hid]
ehci-hcd               19116   0  (unused)
usbcore                62796   1  [audio hid ehci-hcd]
ata_piix                4552   0  (unused)
libata                 41020   0  [ata_piix]
i810_audio             28700   1 ...
[ message continues ]

Sounds like the application directly attaches to the device itself and

OK, so we'll assume it's not a regression and has always been like that,


OK. I see an nvidia module. Would this machine happen to run under X ?
If so, did you configure X so that it directly references the HID devices ?

Also, could you tell us a bit more about the application, and how you have

OK. Before I ask you to do so, could you send me privately your System.map,
a copy of /proc/ksyms and your vmlinux (not vmlinuz) ? Oh, and if you're
running X, please also send your X config file, just in case.

Maybe we can find the faulty function there.

Regards,
Willy

--

[ message continues ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

             ^^^^


I'm not absolutely sure but when I remember correct I did use USB
keyboard before in older ages. But I do not be absolutely sure if I test

Yes. I need to use the nvidia module to use the machine. But I do not
use that crazy window manages than kde or gnome which do some special

What do you mean with "directly"? I use evdev for mouse but the keyboard

Just sync several times in front of unplugging the device helps. I can
reproduce the bug right after a boot without logging in under X (Just
kdm running). But if I use sync the problem is gone.

I imagine that it might be something to do with a incompatibility
between HID and one filesystem driver. I saw this issue in the past with
ext3 which was very dirty in the past.

Actually I use reiserfs, ext3, and ext2. Might it be that there is some
shared memory used between that both subsystems? Ah, and before I forget
to mention, I use the cryptoloop-jari patch to use encrypted swap and

Yup, I will send it later. But why vmlinuX and not vmlinuZ? I thought

Will follow too.

Regards
   Klaus Ethgen
- -- 
Klaus Ethgen                            http://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSOnJ+5+OKpjRpO3lAQL9OAf/TJe/wno/hADSMhU+euCxwZ/WjNb0rZ+J
iSv3GX7Kx7Yrk5Y6znVWmJVWOuDMrws2WCPo9mG1IvrCvIclAsoouj1nj68/TpT/
zsy14V+S/Va/2CDfDncJuucKHlXSOKB42IMDmWWJekoandarCBCPx0BgStukHcc4
jsFYKNr1nL8a77S9GDxZsvQU0L9Pxt4I0MxATI/1rrwTNnhMSLK6aMIHSZTvjBBm
7DBlnr8bzo9MzYOspMZHUddM6ZMWuYIheDiEh9s1OTNspsDlS6fKj1l75fXB6Ncz
klANfHMJXFoLOlWVEXxE/uX8/+vetMkD0wmwtWg/W2gXAivNXNeoQQ==
=38uU
-----END PGP SIGNATURE-----
--

[ message continues ]

Hi Klaus,


OK. I found a USB keyboard so if I find a theorical corner case, I might

OK. I was asking if there was anything such as Device "/dev/hid/..." or
Device "/dev/input/..." in the Keyboard section, but judging by your

That's the part I really don't get. It's quite amazing that finishing
writes onto a file system avoids kernel panics on USB keyboard. Oh,
could you check /proc/interrupts to ensure that your USB interrupts
are not shared with any block device, just in case ? It would constitute

Hmm interesting. Could you at least try to reproduce with swap turned off ?

No, vmlinuz is stripped and has some boot code prepended (reason why I
asked specifically). vmlinux has all symbols and may easily be disassembled.

BTW, I confirm that I've received them in another mail, thanks.

I don't have much time right now, but I have the files and will check
what can be found. I might get back to you for complementary information,
though I need to get a few ideas of the problem first.

Regards,
Willy

--

[ message continues ]