On Tue 14-05-13 20:36:59, Javier Domingo wrote:
I didn't get any reply, is this mailing list still valid, or should I
ask elsewhere? (this is a ping message)
This is a high traffic list so your message is likely to just go
unnoticed. It is good to find maintainers of the subsystem (MAINTAINERS
I didn't get any reply, is this mailing list still valid, or should I
ask elsewhere? (this is a ping message)
Javier Domingo
2013/5/2 Javier Domingo :
> Hi,
>
> I am currently having problems with the cpu scaling (something is
> touching the
I didn't get any reply, is this mailing list still valid, or should I
ask elsewhere? (this is a ping message)
Javier Domingo
2013/5/2 Javier Domingo javier...@gmail.com:
Hi,
I am currently having problems with the cpu scaling (something is
touching the
On Thu, Mar 14, 2013 at 09:38:02AM +0800, Hillf Danton wrote:
> [cc Russell]
> On Wed, Mar 13, 2013 at 11:04 PM, Mark Jackson wrote:
> > Can any help diagnose what my userspace task is doing to get the followings
> > oops ?
> >
> > [ 42.587772] Unable to handle kernel paging request at virtual
On Thu, Mar 14, 2013 at 09:38:02AM +0800, Hillf Danton wrote:
[cc Russell]
On Wed, Mar 13, 2013 at 11:04 PM, Mark Jackson mpfj-l...@mimc.co.uk wrote:
Can any help diagnose what my userspace task is doing to get the followings
oops ?
[ 42.587772] Unable to handle kernel paging request
[cc Russell]
On Wed, Mar 13, 2013 at 11:04 PM, Mark Jackson wrote:
> Can any help diagnose what my userspace task is doing to get the followings
> oops ?
>
> [ 42.587772] Unable to handle kernel paging request at virtual address
> bfac6004
> [ 42.595431] pgd = cf748000
> [ 42.598291]
[cc Russell]
On Wed, Mar 13, 2013 at 11:04 PM, Mark Jackson mpfj-l...@mimc.co.uk wrote:
Can any help diagnose what my userspace task is doing to get the followings
oops ?
[ 42.587772] Unable to handle kernel paging request at virtual address
bfac6004
[ 42.595431] pgd = cf748000
[
Sorry guys I was away due to personal emergency, however now I am back
and will check the reply ASAP.
On 28 July 2012 21:49, Alan Stern wrote:
> On Sat, 28 Jul 2012, Daniel Mack wrote:
>
>> Hmm, interesting. Thanks for sharing this. I personally never saw this
>> bug kicking in, but if I
Sorry guys I was away due to personal emergency, however now I am back
and will check the reply ASAP.
On 28 July 2012 21:49, Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 28 Jul 2012, Daniel Mack wrote:
Hmm, interesting. Thanks for sharing this. I personally never saw this
bug kicking
On Sat, 28 Jul 2012, Daniel Mack wrote:
> Hmm, interesting. Thanks for sharing this. I personally never saw this
> bug kicking in, but if I understand your findings correctly, we would
> need something like the following patch for snd-usb and the storage driver?
>
> Sarbojit, could you give this
On 28.07.2012 15:25, Bjørn Mork wrote:
> Daniel Mack writes:
>> On 28.07.2012 14:27, Bjørn Mork wrote:
>>
>>> The reason is this change:
>>>
>>> 0998d0631 device-core: Ensure drvdata = NULL when no driver is bound
>>>
>>>
>>> It will make bugs like this suddenly 100% reproducible. But the bugs
Daniel Mack writes:
> On 28.07.2012 14:27, Bjørn Mork wrote:
>
>> The reason is this change:
>>
>> 0998d0631 device-core: Ensure drvdata = NULL when no driver is bound
>>
>>
>> It will make bugs like this suddenly 100% reproducible. But the bugs
>> *are* in the drivers, and may have been
On 28.07.2012 14:27, Bjørn Mork wrote:
> Daniel Mack writes:
>> On 23.07.2012 16:47, Alan Stern wrote:
>>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
Daniel Mack writes:
> On 23.07.2012 16:47, Alan Stern wrote:
>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>>> That is why I provided two stacks,
>>>
>>> 1st one is when I tried to remove the USB hub (which connects a webcam
>>> + microphone)
>>> 2nd one is when I tried to remove an USB powered
On 23.07.2012 17:04, Sarbojit Ganguly wrote:
> On 23 July 2012 20:17, Alan Stern wrote:
>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>>
>>> Hello Daniel,
>>>
>>> That is why I provided two stacks,
>>>
>>> 1st one is when I tried to remove the USB hub (which connects a webcam
>>> + microphone)
On 23.07.2012 17:04, Sarbojit Ganguly wrote:
On 23 July 2012 20:17, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
Hello Daniel,
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+
Daniel Mack zon...@gmail.com writes:
On 23.07.2012 16:47, Alan Stern wrote:
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2nd one is when I tried to remove an USB powered
On 28.07.2012 14:27, Bjørn Mork wrote:
Daniel Mack zon...@gmail.com writes:
On 23.07.2012 16:47, Alan Stern wrote:
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2nd one is
Daniel Mack zon...@gmail.com writes:
On 28.07.2012 14:27, Bjørn Mork wrote:
The reason is this change:
0998d0631 device-core: Ensure drvdata = NULL when no driver is bound
It will make bugs like this suddenly 100% reproducible. But the bugs
*are* in the drivers, and may have been
On 28.07.2012 15:25, Bjørn Mork wrote:
Daniel Mack zon...@gmail.com writes:
On 28.07.2012 14:27, Bjørn Mork wrote:
The reason is this change:
0998d0631 device-core: Ensure drvdata = NULL when no driver is bound
It will make bugs like this suddenly 100% reproducible. But the bugs
*are*
On Sat, 28 Jul 2012, Daniel Mack wrote:
Hmm, interesting. Thanks for sharing this. I personally never saw this
bug kicking in, but if I understand your findings correctly, we would
need something like the following patch for snd-usb and the storage driver?
Sarbojit, could you give this a
On 23.07.2012 17:04, Sarbojit Ganguly wrote:
> On 23 July 2012 20:17, Alan Stern wrote:
> Yes the issue is in evict() api which gets called when USB disconnect
> is triggered.
>>
>> Alan Stern
>>
>
> Even I was confused in the beginning but after thorough check I
> confirmed its presence. I
On 23 July 2012 20:24, Daniel Mack wrote:
> On 23.07.2012 16:47, Alan Stern wrote:
>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>>> That is why I provided two stacks,
>>>
>>> 1st one is when I tried to remove the USB hub (which connects a webcam
>>> + microphone)
>>> 2nd one is when I tried to
On 23 July 2012 20:17, Alan Stern wrote:
> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>
>> Hello Daniel,
>>
>> That is why I provided two stacks,
>>
>> 1st one is when I tried to remove the USB hub (which connects a webcam
>> + microphone)
>> 2nd one is when I tried to remove an USB powered
On 23.07.2012 16:47, Alan Stern wrote:
> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>> That is why I provided two stacks,
>>
>> 1st one is when I tried to remove the USB hub (which connects a webcam
>> + microphone)
>> 2nd one is when I tried to remove an USB powered external HDD.
>>
>> Just to
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
> Hello Daniel,
>
> That is why I provided two stacks,
>
> 1st one is when I tried to remove the USB hub (which connects a webcam
> + microphone)
> 2nd one is when I tried to remove an USB powered external HDD.
>
> Just to make sure whether the
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
Hello Daniel,
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2nd one is when I tried to remove an USB powered external HDD.
Just to make sure whether the problem is
On 23.07.2012 16:47, Alan Stern wrote:
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2nd one is when I tried to remove an USB powered external HDD.
Just to make sure
On 23 July 2012 20:17, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
Hello Daniel,
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2nd one is when I tried to remove an USB
On 23 July 2012 20:24, Daniel Mack zon...@gmail.com wrote:
On 23.07.2012 16:47, Alan Stern wrote:
On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2nd one is when I tried to
On 23.07.2012 17:04, Sarbojit Ganguly wrote:
On 23 July 2012 20:17, Alan Stern st...@rowland.harvard.edu wrote:
Yes the issue is in evict() api which gets called when USB disconnect
is triggered.
Alan Stern
Even I was confused in the beginning but after thorough check I
confirmed its
-- Original message --
From: Marcel Holtmann <[EMAIL PROTECTED]>
> Hi Quel,
>
> > Bad news: I still cannot use the device.
> >
> > hcitool inq, hcitool scan, hcitool name and hcitool info
> >
> > commands work.
> >
> > hcitool cc , sdptool , rfcomm connect
-- Original message --
From: Marcel Holtmann [EMAIL PROTECTED]
Hi Quel,
Bad news: I still cannot use the device.
hcitool inq, hcitool scan, hcitool name btaddr and hcitool info
btaddr
commands work.
hcitool cc btaddr, sdptool btaddr, rfcomm
Hi Quel,
-- Original message --
From: Thomas Gleixner <[EMAIL PROTECTED]>
On Fri, 22 Feb 2008, David Woodhouse wrote:
On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
+ del_timer(>info_timer);
+
hcon->l2cap_data = NULL;
-- Original message --
From: Thomas Gleixner <[EMAIL PROTECTED]>
> On Fri, 22 Feb 2008, David Woodhouse wrote:
>
> > On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
> > >
> > > + del_timer(>info_timer);
> > > +
> > > hcon->l2cap_data =
-- Original message --
From: Thomas Gleixner [EMAIL PROTECTED]
On Fri, 22 Feb 2008, David Woodhouse wrote:
On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
+ del_timer(conn-info_timer);
+
hcon-l2cap_data = NULL;
Hi Quel,
-- Original message --
From: Thomas Gleixner [EMAIL PROTECTED]
On Fri, 22 Feb 2008, David Woodhouse wrote:
On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
+ del_timer(conn-info_timer);
+
hcon-l2cap_data = NULL;
On Fri, 22 Feb 2008, David Woodhouse wrote:
> On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
> >
> > + del_timer(>info_timer);
> > +
> > hcon->l2cap_data = NULL;
> > kfree(conn);
>
> Shouldn't that be del_timer_sync() ?
Hmm, probably yes.
tglx
--
To
On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
>
> + del_timer(>info_timer);
> +
> hcon->l2cap_data = NULL;
> kfree(conn);
Shouldn't that be del_timer_sync() ?
--
dwmw2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
+ del_timer(conn-info_timer);
+
hcon-l2cap_data = NULL;
kfree(conn);
Shouldn't that be del_timer_sync() ?
--
dwmw2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Fri, 22 Feb 2008, David Woodhouse wrote:
On Fri, 2008-02-22 at 08:23 +0100, Thomas Gleixner wrote:
+ del_timer(conn-info_timer);
+
hcon-l2cap_data = NULL;
kfree(conn);
Shouldn't that be del_timer_sync() ?
Hmm, probably yes.
tglx
--
To unsubscribe
Quel,
On Fri, 22 Feb 2008, Quel Qun wrote:
> $ addr2line -e vmlinux c012d51d
> /usr/src/linux-2.6.25-rc2-git5kk1/kernel/timer.c:770
>
> Crap, that is on the next list_for_each_entry in timer.c :(
>
> I tried to make a similar test loop as you did a few lines above:
Cool.
> I thought I got it
On Fri, Feb 22, 2008 at 02:40:41AM +, Quel Qun wrote:
>
> -- Original message --
> From: Thomas Gleixner <[EMAIL PROTECTED]>
> > On Thu, 21 Feb 2008, Quel Qun wrote:
> > > > > > Not that I'm aware off, but this might as well be some old use
> > > > > after
>
-- Original message --
From: Thomas Gleixner <[EMAIL PROTECTED]>
> On Thu, 21 Feb 2008, Quel Qun wrote:
> > > > > Not that I'm aware off, but this might as well be some old use after
> > > > > free bug which got exposed by some unrelated change. The good news is
On Thu, 21 Feb 2008, Quel Qun wrote:
> > > > Not that I'm aware off, but this might as well be some old use after
> > > > free bug which got exposed by some unrelated change. The good news is
> > > > that it is reproducible. I'll hack up some nasty debug patch which
> > > > lets us - hopefully
-- Original message --
From: "Dave Young" <[EMAIL PROTECTED]>
> On Wed, Feb 20, 2008 at 4:11 PM, Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> > On Wed, 20 Feb 2008, Thomas Gleixner wrote:
> > > On Tue, 19 Feb 2008, Marcel Holtmann wrote:
> >
> > > > I don't
-- Original message --
From: Dave Young [EMAIL PROTECTED]
On Wed, Feb 20, 2008 at 4:11 PM, Thomas Gleixner [EMAIL PROTECTED] wrote:
On Wed, 20 Feb 2008, Thomas Gleixner wrote:
On Tue, 19 Feb 2008, Marcel Holtmann wrote:
I don't really have any idea.
On Thu, 21 Feb 2008, Quel Qun wrote:
Not that I'm aware off, but this might as well be some old use after
free bug which got exposed by some unrelated change. The good news is
that it is reproducible. I'll hack up some nasty debug patch which
lets us - hopefully - decode where
-- Original message --
From: Thomas Gleixner [EMAIL PROTECTED]
On Thu, 21 Feb 2008, Quel Qun wrote:
Not that I'm aware off, but this might as well be some old use after
free bug which got exposed by some unrelated change. The good news is
that
On Fri, Feb 22, 2008 at 02:40:41AM +, Quel Qun wrote:
-- Original message --
From: Thomas Gleixner [EMAIL PROTECTED]
On Thu, 21 Feb 2008, Quel Qun wrote:
Not that I'm aware off, but this might as well be some old use
after
free bug
Quel,
On Fri, 22 Feb 2008, Quel Qun wrote:
$ addr2line -e vmlinux c012d51d
/usr/src/linux-2.6.25-rc2-git5kk1/kernel/timer.c:770
Crap, that is on the next list_for_each_entry in timer.c :(
I tried to make a similar test loop as you did a few lines above:
Cool.
I thought I got it on the
On Wed, Feb 20, 2008 at 4:11 PM, Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> On Wed, 20 Feb 2008, Thomas Gleixner wrote:
> > On Tue, 19 Feb 2008, Marcel Holtmann wrote:
>
> > > I don't really have any idea. Nothing has been changed in this area for a
> > > couple of years. The command TX
On Wed, 20 Feb 2008, Thomas Gleixner wrote:
> On Tue, 19 Feb 2008, Marcel Holtmann wrote:
> > I don't really have any idea. Nothing has been changed in this area for a
> > couple of years. The command TX timeout is the timeout that indicates a
> > missing answer to a command sent down to the
On Wed, 20 Feb 2008, Thomas Gleixner wrote:
On Tue, 19 Feb 2008, Marcel Holtmann wrote:
I don't really have any idea. Nothing has been changed in this area for a
couple of years. The command TX timeout is the timeout that indicates a
missing answer to a command sent down to the Bluetooth
On Wed, Feb 20, 2008 at 4:11 PM, Thomas Gleixner [EMAIL PROTECTED] wrote:
On Wed, 20 Feb 2008, Thomas Gleixner wrote:
On Tue, 19 Feb 2008, Marcel Holtmann wrote:
I don't really have any idea. Nothing has been changed in this area for a
couple of years. The command TX timeout is the
On Tue, 19 Feb 2008, Marcel Holtmann wrote:
> > > hci_cmd_task: hci0 command tx timeout
> > > BUG: unable to handle kernel paging request at 6b6b6b6b
> >
> > We got some more info ---
> > #define POISON_FREE 0x6b/* for use-after-free poisoning */
> >
> >
Hi Thomas,
Can you please enable CONFIG_SLUB_DEBUG=y and CONFIG_SLUB_DEBUG_ON=y
and give it another try?
If we can not catch it that way, I'll whip up a patch which points
us
to the code which added the offending timer.
Hi,
Note: I switched to 2.6.25-rc2. The only new thing I see is this
Hi Thomas,
Can you please enable CONFIG_SLUB_DEBUG=y and CONFIG_SLUB_DEBUG_ON=y
and give it another try?
If we can not catch it that way, I'll whip up a patch which points
us
to the code which added the offending timer.
Hi,
Note: I switched to 2.6.25-rc2. The only new thing I see is this
On Tue, 19 Feb 2008, Marcel Holtmann wrote:
hci_cmd_task: hci0 command tx timeout
BUG: unable to handle kernel paging request at 6b6b6b6b
We got some more info ---
#define POISON_FREE 0x6b/* for use-after-free poisoning */
So the timer is
On Mon, 18 Feb 2008, Quel Qun wrote:
Added bluetooth wizards to CC
> > Can you please enable CONFIG_SLUB_DEBUG=y and CONFIG_SLUB_DEBUG_ON=y
> > and give it another try?
> >
> > If we can not catch it that way, I'll whip up a patch which points us
> > to the code which added the offending timer.
* Quel Qun | 2008-02-18 00:01:21 [+]:
Please send me your .config file and process list (ps uax > ps_list)
after the crash. I have a dongle with the same usb id as yours and I
can't reproduce the crash. So it is either some .config magic or one of
your programs is accessing the dongle.
* Quel Qun | 2008-02-18 00:01:21 [+]:
Please send me your .config file and process list (ps uax ps_list)
after the crash. I have a dongle with the same usb id as yours and I
can't reproduce the crash. So it is either some .config magic or one of
your programs is accessing the dongle.
On Mon, 18 Feb 2008, Quel Qun wrote:
Added bluetooth wizards to CC
Can you please enable CONFIG_SLUB_DEBUG=y and CONFIG_SLUB_DEBUG_ON=y
and give it another try?
If we can not catch it that way, I'll whip up a patch which points us
to the code which added the offending timer.
Hi,
-- Original message --
From: Thomas Gleixner <[EMAIL PROTECTED]>
> On Sat, 16 Feb 2008, Quel Qun wrote:
> Unfortunately we only see that the list is corrupted but not which
> code caused it. This looks like something forgot to delete the timer
> before freeing the
-- Original message --
From: Thomas Gleixner [EMAIL PROTECTED]
On Sat, 16 Feb 2008, Quel Qun wrote:
Unfortunately we only see that the list is corrupted but not which
code caused it. This looks like something forgot to delete the timer
before freeing the
On Sat, 16 Feb 2008, Quel Qun wrote:
> > Please also enable CONFIG_DEBUG_LIST=y, which should catch the place
> > where a list corruption happens.
>
> Thank you for the hand holding. I must admit I do not anything
> about kernel debugging.
>
> With or without nohz=off, the crashes are very
-- Original message --
From: Thomas Gleixner <[EMAIL PROTECTED]>
> On Sat, 16 Feb 2008, Jiri Kosina wrote:
> > [ Ingo and Thomas added to CC, as this is apparently nohz stuff ]
>
> Well, it explodes there :) I can not exactly decode the source line,
> but it's
On Sat, 16 Feb 2008, Jiri Kosina wrote:
> [ Ingo and Thomas added to CC, as this is apparently nohz stuff ]
Well, it explodes there :) I can not exactly decode the source line,
but it's either list corruption or something is fiddling with an
enqueued timer.
> Quel, does the problem go away when
[ Ingo and Thomas added to CC, as this is apparently nohz stuff ]
Quel, does the problem go away when you boot with nohz=off?
Original message left below for reference.
On Sat, 16 Feb 2008, Quel Qun wrote:
> Hi,
>
> Since the rc's of 2.6.24, my machine crashes when I try to use the USB
>
[ Ingo and Thomas added to CC, as this is apparently nohz stuff ]
Quel, does the problem go away when you boot with nohz=off?
Original message left below for reference.
On Sat, 16 Feb 2008, Quel Qun wrote:
Hi,
Since the rc's of 2.6.24, my machine crashes when I try to use the USB
dongle.
On Sat, 16 Feb 2008, Jiri Kosina wrote:
[ Ingo and Thomas added to CC, as this is apparently nohz stuff ]
Well, it explodes there :) I can not exactly decode the source line,
but it's either list corruption or something is fiddling with an
enqueued timer.
Quel, does the problem go away when
-- Original message --
From: Thomas Gleixner [EMAIL PROTECTED]
On Sat, 16 Feb 2008, Jiri Kosina wrote:
[ Ingo and Thomas added to CC, as this is apparently nohz stuff ]
Well, it explodes there :) I can not exactly decode the source line,
but it's either list
On Sat, 16 Feb 2008, Quel Qun wrote:
Please also enable CONFIG_DEBUG_LIST=y, which should catch the place
where a list corruption happens.
Thank you for the hand holding. I must admit I do not anything
about kernel debugging.
With or without nohz=off, the crashes are very similar. It
On Tuesday 05 February 2008 07:57, Andrej Hocevar wrote:
> this has occured a couple of times. i was editing a unicode file with
> vim in the console. after a reboot, i immediately tried to do just that
> again and it crashed. it might have occured upon trying to select some
> text with the mouse
On Tuesday 05 February 2008 07:57, Andrej Hocevar wrote:
this has occured a couple of times. i was editing a unicode file with
vim in the console. after a reboot, i immediately tried to do just that
again and it crashed. it might have occured upon trying to select some
text with the mouse
On 09/01/2008, Stoyan Gaydarov <[EMAIL PROTECTED]> wrote:
> On Jan 8, 2008 9:02 PM, Alan Cox <[EMAIL PROTECTED]> wrote:
> > > Except this time when rebooting the machine i got a kernel oops
> > > message and it didn't boot completely. I could not copy it but I did
> > > take a picture and now I
On Jan 8, 2008 9:02 PM, Alan Cox <[EMAIL PROTECTED]> wrote:
> > Except this time when rebooting the machine i got a kernel oops
> > message and it didn't boot completely. I could not copy it but I did
> > take a picture and now I have re-written the screen here(sorry about
>
> That is interesting
> Except this time when rebooting the machine i got a kernel oops
> message and it didn't boot completely. I could not copy it but I did
> take a picture and now I have re-written the screen here(sorry about
That is interesting - that sort of error usually points at memory
corruption and early on
On Jan 7, 2008 5:30 PM, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Mon, 7 Jan 2008 17:15:01 -0600
> "Stoyan Gaydarov" <[EMAIL PROTECTED]> wrote:
>
> > Today I upgraded my kernel from 2.6.23.9 to 2.6.23.12 and in the past
> > 30 minutes I have had to restart my computer twice.
> > I believe its a
On Jan 7, 2008 5:30 PM, Alan Cox [EMAIL PROTECTED] wrote:
On Mon, 7 Jan 2008 17:15:01 -0600
Stoyan Gaydarov [EMAIL PROTECTED] wrote:
Today I upgraded my kernel from 2.6.23.9 to 2.6.23.12 and in the past
30 minutes I have had to restart my computer twice.
I believe its a kernel oops or a
Except this time when rebooting the machine i got a kernel oops
message and it didn't boot completely. I could not copy it but I did
take a picture and now I have re-written the screen here(sorry about
That is interesting - that sort of error usually points at memory
corruption and early on
On Jan 8, 2008 9:02 PM, Alan Cox [EMAIL PROTECTED] wrote:
Except this time when rebooting the machine i got a kernel oops
message and it didn't boot completely. I could not copy it but I did
take a picture and now I have re-written the screen here(sorry about
That is interesting - that
On 08/01/2008, Stoyan Gaydarov <[EMAIL PROTECTED]> wrote:
> Today I upgraded my kernel from 2.6.23.9 to 2.6.23.12 and in the past
> 30 minutes I have had to restart my computer twice.
> I believe its a kernel oops or a kernel panic because when the
> computer freezes it blinks the caps and scroll
On Mon, 7 Jan 2008 17:15:01 -0600
"Stoyan Gaydarov" <[EMAIL PROTECTED]> wrote:
> Today I upgraded my kernel from 2.6.23.9 to 2.6.23.12 and in the past
> 30 minutes I have had to restart my computer twice.
> I believe its a kernel oops or a kernel panic because when the
> computer freezes it
On Mon, 7 Jan 2008 17:15:01 -0600
Stoyan Gaydarov [EMAIL PROTECTED] wrote:
Today I upgraded my kernel from 2.6.23.9 to 2.6.23.12 and in the past
30 minutes I have had to restart my computer twice.
I believe its a kernel oops or a kernel panic because when the
computer freezes it blinks the
On 08/01/2008, Stoyan Gaydarov [EMAIL PROTECTED] wrote:
Today I upgraded my kernel from 2.6.23.9 to 2.6.23.12 and in the past
30 minutes I have had to restart my computer twice.
I believe its a kernel oops or a kernel panic because when the
computer freezes it blinks the caps and scroll lock
--- Raman Gupta <[EMAIL PROTECTED]> wrote:
> I just found this bug:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8198
>
> This seems to indicate the problem was resolved in 2.6.21.2.
>
> However, I also found this, where you reported the problem was back in
> 2.6.22.9 (which is what I am
--- Raman Gupta [EMAIL PROTECTED] wrote:
I just found this bug:
http://bugzilla.kernel.org/show_bug.cgi?id=8198
This seems to indicate the problem was resolved in 2.6.21.2.
However, I also found this, where you reported the problem was back in
2.6.22.9 (which is what I am currently
> We've come across an Oops, in what appears to NFS.
>
> 2.6.22.6 vanilla + realtime-lsm
> RHEL4 over PXE/NFS_ROOT
>
>
> Oct 9 14:26:13 WS15 gdm(pam_unix)[6038]: session opened for
> user mockj by (uid=0) Oct 9 14:26:48 WS15 gconfd
> (mockj-7583): starting (version 2.8.1), pid
> 7583 user
We've come across an Oops, in what appears to NFS.
2.6.22.6 vanilla + realtime-lsm
RHEL4 over PXE/NFS_ROOT
Oct 9 14:26:13 WS15 gdm(pam_unix)[6038]: session opened for
user mockj by (uid=0) Oct 9 14:26:48 WS15 gconfd
(mockj-7583): starting (version 2.8.1), pid
7583 user 'mockj'
Hi all,
On Fr, 28 Sep 2007, Mingming Cao wrote:
> i_block_alloc_info, it should be 0x14(20 bytes)...Are you running a
> vanilla 2.6.23-rc6?
Well yes, I add one patch for reducing the usb device resetting time,
but this was definitely not the problem, no usb device was attached.
> from the
Mingming Cao wrote:
BUG: unable to handle kernel paging request at virtual address 104b
printing eip:
c0195bd3
*pde =
Oops: [#1]
PREEMPT SMP
Modules linked in: vboxdrv binfmt_misc fuse coretemp hwmon gspca videodev v4l2_common v4l1_compat iwl3945 mac80211 tifm_7xx1
> BUG: unable to handle kernel paging request at virtual address 104b
> printing eip:
> c0195bd3
> *pde =
> Oops: [#1]
> PREEMPT SMP
> Modules linked in: vboxdrv binfmt_misc fuse coretemp hwmon gspca videodev
> v4l2_common v4l1_compat iwl3945 mac80211 tifm_7xx1 tifm_core
On Fri, 2007-09-28 at 06:54 +0200, Norbert Preining wrote:
> Hi Mingming,
>
> On Do, 27 Sep 2007, Mingming Cao wrote:
> > Could you please sent the objdump of the ext4_discard_reservation
> > function? It doesn't match what I see here.
>
> I assume you meant ext3_ I made
> objdump -x
On Fri, 2007-09-28 at 06:54 +0200, Norbert Preining wrote:
Hi Mingming,
On Do, 27 Sep 2007, Mingming Cao wrote:
Could you please sent the objdump of the ext4_discard_reservation
function? It doesn't match what I see here.
I assume you meant ext3_ I made
objdump -x -D -s
BUG: unable to handle kernel paging request at virtual address 104b
printing eip:
c0195bd3
*pde =
Oops: [#1]
PREEMPT SMP
Modules linked in: vboxdrv binfmt_misc fuse coretemp hwmon gspca videodev
v4l2_common v4l1_compat iwl3945 mac80211 tifm_7xx1 tifm_core joydev
Mingming Cao wrote:
BUG: unable to handle kernel paging request at virtual address 104b
printing eip:
c0195bd3
*pde =
Oops: [#1]
PREEMPT SMP
Modules linked in: vboxdrv binfmt_misc fuse coretemp hwmon gspca videodev v4l2_common v4l1_compat iwl3945 mac80211 tifm_7xx1
Hi all,
On Fr, 28 Sep 2007, Mingming Cao wrote:
i_block_alloc_info, it should be 0x14(20 bytes)...Are you running a
vanilla 2.6.23-rc6?
Well yes, I add one patch for reducing the usb device resetting time,
but this was definitely not the problem, no usb device was attached.
from the cache,
Hi,
Could you please sent the objdump of the ext4_discard_reservation
function? It doesn't match what I see here.
Thanks,
Mingming
On Thu, 2007-09-27 at 12:31 +0200, [EMAIL PROTECTED]
wrote:
> Hi all!
>
> (Please Cc)
>
> kernel 2.6.23-rc6
> Debian/sid
>
> kernel ooops:
>
> BUG: unable to
On Thursday, 27 September 2007 15:13, Norbert Preining wrote:
> On Do, 27 Sep 2007, Rafael J. Wysocki wrote:
> > Does it happen with 2.6.22?
>
> Hard to say. It didn't happen as long as I used -22, but it didn't
> happen for a long time (since I run -rc6), and it is not reproducible.
>
> What I
101 - 200 of 402 matches
Mail list logo
