for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: bdwrite: buffer is not busy
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc227e6f4
fault code = supervisor write, page not present
instruction pointer
.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: bdwrite: buffer is not busy
panic messages:
---
panic: bad pte
syncing disks... panic: bdwrite: buffer is not busy
Uptime: 3h37m11s
to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: bdwrite: buffer is not busy
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual add
I've been having inexplicable crashes for a while and finally got around
to getting a debug kernel and checking out what's going on, so here
goes (apologies for the ^M's and all, I scripted a gdb session and that's
what I got...):
panic: bdwrite: buffer is not busy
panic m
On Fri, Jul 12, 2002 at 22:18:35 +0100, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes:
> >I see this panic constantly during last month or two, UP machine, no
> >softupdates. Anybody else saw it too? Any ideas?
>
> The "buffer is not busy" panic is usually a secon
"Andrey A. Chernov" wrote:
> I see this panic constantly during last month or two, UP machine, no
> softupdates. Anybody else saw it too? Any ideas?
Lazy #$@&*% buffer!
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Ian Dowse writes:
> In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes:
> >I see this panic constantly during last month or two, UP machine, no
> >softupdates. Anybody else saw it too? Any ideas?
>
> The "buffer is not busy" panic is usually a secondary panic that
> occurs while t
In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes:
>I see this panic constantly during last month or two, UP machine, no
>softupdates. Anybody else saw it too? Any ideas?
The "buffer is not busy" panic is usually a secondary panic that
occurs while trying to sync the disks after a diffe
On Fri, Jul 12, 2002 at 10:25:35PM +0400, Andrey A. Chernov wrote:
> I see this panic constantly during last month or two, UP machine, no
> softupdates. Anybody else saw it too? Any ideas?
>
I've been seeing it, when I'm lucky :) I get weird issues when mplayer
is doing its thing with the sdl b
I see this panic constantly during last month or two, UP machine, no
softupdates. Anybody else saw it too? Any ideas?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 10 Feb 2002, Mikhail Teterin wrote:
> On 10 Feb, Bruce Evans wrote:
> > This is a well known bug in the device layer. I reported it on
> > 2001/12/26 and fixed it locally a little later. See the thread in
> > -current about "panic during fdisk'ing a md(4) device" for patches.
On 10 Feb, Bruce Evans wrote:
> On Sat, 9 Feb 2002, John Baldwin wrote:
>
>> On 09-Feb-02 Mikhail Teterin wrote:
>> > While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
>> > ``newfs_msdos fd0.1440'' with or without the floppy inside :-\ With
>> > todays or Jan 3rd kernel (my prev
While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
``newfs_msdos fd0.1440'' with or without the floppy inside :-\
With todays or Jan 3rd kernel (my previous upgrade).
IdlePTD at phsyical address 0x004ed000
initial pcb at physical address 0x00411560
panicst
On Sun, 10 Feb 2002, Mikhail Teterin wrote:
> On 10 Feb, Bruce Evans wrote:
> > This is a well known bug in the device layer. I reported it on
> > 2001/12/26 and fixed it locally a little later. See the thread in
> > -current about "panic during fdisk'ing a md(4) device" for patches.
On Sun, 10 Feb 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >On Sat, 9 Feb 2002, Julian Elischer wrote:
> >
> >> On Sun, 10 Feb 2002, Bruce Evans wrote:
> >> >
> >> > This is a well known bug in the device layer. I reported it on 2001/12/26
> >> > and fi
On 10 Feb, Bruce Evans wrote:
> On Sat, 9 Feb 2002, John Baldwin wrote:
>
>> On 09-Feb-02 Mikhail Teterin wrote:
>> > While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
>> > ``newfs_msdos fd0.1440'' with or without the floppy inside :-\ With
>> > todays or Jan 3rd kernel (my prev
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Sat, 9 Feb 2002, Julian Elischer wrote:
>
>> On Sun, 10 Feb 2002, Bruce Evans wrote:
>>
>> >
>> > This is a well known bug in the device layer. I reported it on 2001/12/26
>> > and fixed it locally a little later. See the thread in -current
On Sat, 9 Feb 2002, Julian Elischer wrote:
> On Sun, 10 Feb 2002, Bruce Evans wrote:
>
> >
> > This is a well known bug in the device layer. I reported it on 2001/12/26
> > and fixed it locally a little later. See the thread in -current about
> > "panic during fdisk'ing a md(4) device" for patc
On Sun, 10 Feb 2002, Bruce Evans wrote:
>
> This is a well known bug in the device layer. I reported it on 2001/12/26
> and fixed it locally a little later. See the thread in -current about
> "panic during fdisk'ing a md(4) device" for patches.
>
Can you commit the fix?
To Unsubscribe: s
On Sat, 9 Feb 2002, John Baldwin wrote:
> On 09-Feb-02 Mikhail Teterin wrote:
> > While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
> > ``newfs_msdos fd0.1440'' with or without the floppy inside :-\
> > With todays or Jan 3rd kernel (my previous upgrade).
>
> Only use fdisk on hard dis
ill it shouldn't panic. The bdwrite is just
extra garbage, the real panic is due to a NULL pointer dereference:
> IdlePTD at phsyical address 0x004ed000
> initial pcb at physical address 0x00411560
> panicstr: bdwrite: buffer is not busy
> panic messages:
> ---
> Fatal
While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
``newfs_msdos fd0.1440'' with or without the floppy inside :-\
With todays or Jan 3rd kernel (my previous upgrade).
IdlePTD at phsyical address 0x004ed000
initial pcb at physical address 0x00411560
panicst
22 matches
Mail list logo
