On Thu, Sep 29, 2005 at 11:52:34PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > > > > I believe it would happen with any other CF card, too. Can you
> > > > > > > hciattach it, unplug, hciattach again?
> > > > > >
> > > > > > actually I don't have any of them with me and I don't saw a problem with
> > > > > > my Casira of a serial port.
> > > > >
> > > > > Following patch seems to work around it. And yes, printk() triggers
> > > > > twice after
> > > >
> > > > What's the problem this patch is trying to address?
> > >
> > > I get oops after starting my bluetooth subsystem for second
> > > time. billionton_start, unplug CF, billionton_start will oops the
> > > system. That patch prevents it.
> >
> > More details please. I don't have the ability to run bluetooth myself.
>
> Unfortunately I do not know much about bluetooth. The card is
> basically CF serial with bluetooth chip attached to that. billionton
> start does setserial, then attaches bluetooth subsystem to that chip,
> and enables bluetooth.
How about showing the oops? The patch is definitely wrong btw - there's
no way state->info should be NULL here.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |