[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081005210144.GA7980@1wt.eu>
Date: Sun, 5 Oct 2008 23:01:44 +0200
From: Willy Tarreau <w@....eu>
To: Klaus Ethgen <Klaus@...gen.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [KERNEL] Re: Kernel freeze on 2.4.36.7
On Sun, Oct 05, 2008 at 09:42:54PM +0100, Klaus Ethgen wrote:
> Am So den 5. Okt 2008 um 18:18 schrieb Willy Tarreau:
> > > 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.
> >
> > Does it happen everytime you unplug it or only once in a while ?
>
> Everytime.
OK, that's better (not for you of course).
> 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 wait a view seconds after the sync the freeze is reproducible.
Sounds like the application directly attaches to the device itself and
we have some internal pointer becoming NULL when the device disappears.
> > Also, have you ever been running and older 2.4 kernel not causing this
> > problem ?
>
> I did buy the scanner only days ago. I did not use older kernels since
> then. (I have to compile some if it is needed.)
OK, so we'll assume it's not a regression and has always been like that,
which is the most likely.
> > > The message when I unplug it:
> > > Unable to handle kernel NULL pointer dereference at virtual address 00000048
> > > ...
> >
> > Does the same problem happen when you plug/unplug a USB keyboard on the
> > same machine ?
>
> Yes. I just tested it and my machine was frozen.
Good too. It should be easier to reproduce.
> > > 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.
> >
> > 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.
>
> It should be on this mail.
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
to proceed to avoid the problem ? Eg: quit the application then X, etc...
> > If you want to more easily capture your messages, you can connect
> > another machine to your serial port and boot with "console=ttyS0".
>
> Thats not possible as I did not compile the serial console into the
> kernel.
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists