Am Montag, 15. März 2004 16:57 schrieb Alan Stern:
> On Mon, 15 Mar 2004, Oliver Neukum wrote:
>
> > > > 2. Could you verify that the syslog gets everything?
> > >
> > > I think it gets everything. Had to type the last lines manually (from tty12).
> > > How can I verify?
> >
> > Make sure that
On Monday 15 March 2004 16:57, Alan Stern wrote:
> On Mon, 15 Mar 2004, Oliver Neukum wrote:
> > > > 2. Could you verify that the syslog gets everything?
> > >
> > > I think it gets everything. Had to type the last lines manually (from
> > > tty12). How can I verify?
> >
> > Make sure that klogd is
On Mon, 15 Mar 2004, Oliver Neukum wrote:
> > > 2. Could you verify that the syslog gets everything?
> >
> > I think it gets everything. Had to type the last lines manually (from tty12).
> > How can I verify?
>
> Make sure that klogd is at logging level 9. Hotplug is running, so the
> kernel ha
> > 2. Could you verify that the syslog gets everything?
>
> I think it gets everything. Had to type the last lines manually (from tty12).
> How can I verify?
Make sure that klogd is at logging level 9. Hotplug is running, so the
kernel has noticed the disconnect, yet there's nothing in the log
On Sunday 14 March 2004 23:17, Oliver Neukum wrote:
> Am Sonntag, 14. März 2004 21:57 schrieb Christian Hesse:
> > Oliver Neukum sagte:
> > > Am Sonntag, 14. März 2004 21:01 schrieb Christian Hesse:
> > > > On Sunday 14 March 2004 19:37, Oliver Neukum wrote:
> > > > > Could you enable debugging and
Am Sonntag, 14. März 2004 21:57 schrieb Christian Hesse:
> Oliver Neukum sagte:
> > Am Sonntag, 14. März 2004 21:01 schrieb Christian Hesse:
> > > On Sunday 14 March 2004 19:37, Oliver Neukum wrote:
> > > > Could you enable debugging and send in the log?
> > >
> > > Enabled CONFIG_USB_DEBUG, log is
Oliver Neukum sagte:
> Am Sonntag, 14. März 2004 21:01 schrieb Christian Hesse:
> > On Sunday 14 March 2004 19:37, Oliver Neukum wrote:
> > > Could you enable debugging and send in the log?
> >
> > Enabled CONFIG_USB_DEBUG, log is attached.
> >
> > device plugged at 20:21:07
> > hciconfig hci0 down
Am Sonntag, 14. März 2004 21:01 schrieb Christian Hesse:
> On Sunday 14 March 2004 19:37, Oliver Neukum wrote:
> > > I've just tested a bit more.
> > > I can plug in and unplug the device if all modules are loaded and no bt
> > > daemons are running.
> > > If hic0 is brought up by hcid I have to br
On Sunday 14 March 2004 19:37, Oliver Neukum wrote:
> > I've just tested a bit more.
> > I can plug in and unplug the device if all modules are loaded and no bt
> > daemons are running.
> > If hic0 is brought up by hcid I have to bring it down manually and then
> > can unplug the device. If the dev
> I've just tested a bit more.
> I can plug in and unplug the device if all modules are loaded and no bt
> daemons are running.
> If hic0 is brought up by hcid I have to bring it down manually and then can
> unplug the device. If the device is still up while unplugging the kernel
> oopses.
Cou
On Sunday 14 March 2004 11:50, Oliver Neukum wrote:
> Am Samstag, 13. März 2004 23:27 schrieb Christian Hesse:
> > Hello!
> >
> > I get an oops if I unplug my USB-bluetooth device. If I use "hciconfig
> > hci0 down" unplugging works, but the system hangs with the next plug in.
> > This one occured
Am Samstag, 13. März 2004 23:27 schrieb Christian Hesse:
> Hello!
>
> I get an oops if I unplug my USB-bluetooth device. If I use "hciconfig hci0
> down" unplugging works, but the system hangs with the next plug in. This one
> occured after I pluged and unplugged the device once, an plugged it a
Hello!
I get an oops if I unplug my USB-bluetooth device. If I use "hciconfig hci0
down" unplugging works, but the system hangs with the next plug in. This one
occured after I pluged and unplugged the device once, an plugged it again.
System hangs completely after that. This oops was with 2.6.4
13 matches
Mail list logo
