After I recently (finally) upgraded my main machine to RELENG_8, I
tried to rip a CD today, using abcde, and got
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
(I've got a coredump of the kernel, so I could analyze it if
someone has got an idea
on 24/05/2011 08:54 Joerg Wunsch said the following:
After I recently (finally) upgraded my main machine to RELENG_8, I
tried to rip a CD today, using abcde, and got
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
(I've got a coredump of the
As Andriy Gapon wrote:
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
Backtrace would be a first thing.
OK, here we go (the core has been dumped from within a serial console
BREAK DDB entry, I'm omitting the frames related to that):
#16
on 24/05/2011 10:26 Joerg Wunsch said the following:
As Andriy Gapon wrote:
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
Backtrace would be a first thing.
OK, here we go (the core has been dumped from within a serial console
BREAK DDB
On Tue, May 24, 2011 at 09:26:18AM +0200, Joerg Wunsch wrote:
As Andriy Gapon wrote:
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
Backtrace would be a first thing.
OK, here we go (the core has been dumped from within a serial
I am planning on some changes in head and would like to see if people use the
following features:
- machdep.hyperthreading_allowed tunable and sysctl
- machdep.hlt_logical_cpus tunable and sysctl
- mp_watchdog kernel option
If you are using any of the above, please let me know - better via a
Hello,
I'm trying to setup a MBR partition with a BSD slice in it using gpart on
FreeBSD 8.1 RELEASE. From the fixit console in the install i try to do
gpart create -s MBR ad0
gpart add -t freebsd ad0
gpart create -s BSD ad0s1
gpart add -t freebsd-ufs ad0s1
gpart set -a active -i 1 ad0
For
On 24/05/2011 15:21, Andriy Gapon wrote:
I am planning on some changes in head and would like to see if people use the
following features:
- machdep.hyperthreading_allowed tunable and sysctl
- machdep.hlt_logical_cpus tunable and sysctl
- mp_watchdog kernel option
If you are using any of the
On 24.05.2011 17:20, Victor Balada Diaz wrote:
Ie, no 16 sector offset in it. So my question is... What's the proper way of
doing a MBR + BSD label partition and where is it documented? what are the
different
bootcodes and when is needed each one?[1]
gptboot is used for GPT scheme. It
On Tue, May 24, 2011 at 06:46:01PM +0400, Andrey V. Elsukov wrote:
On 24.05.2011 17:20, Victor Balada Diaz wrote:
also, how do i know about offsets each partitioning scheme needs? shouldn't
GEOM
take care of it without user needing to know anything about it?
Usually you do not need to
On 24.05.2011 19:09, Victor Balada Diaz wrote:
On Tue, May 24, 2011 at 06:46:01PM +0400, Andrey V. Elsukov wrote:
On 24.05.2011 17:20, Victor Balada Diaz wrote:
also, how do i know about offsets each partitioning scheme needs? shouldn't
GEOM
take care of it without user needing to know
Whatever you do, please leave at least some way (at least a tunable) to
enable/disable HTT - some workloads are better with, and some without it,
and some BIOSes are unreliable in enabling/disabling it :)
I noticed that disabling HTT via the machdep.hyperthreading_allowed
tunable resulted in
On Tue, May 24, 2011 at 08:05:15PM +0400, Andrey V. Elsukov wrote:
On 24.05.2011 19:09, Victor Balada Diaz wrote:
On Tue, May 24, 2011 at 06:46:01PM +0400, Andrey V. Elsukov wrote:
On 24.05.2011 17:20, Victor Balada Diaz wrote:
also, how do i know about offsets each partitioning scheme
On 24.05.2011 21:27, Victor Balada Diaz wrote:
So the 16 sector offset in BSD label is really needed or isn't?
First 8 KBytes of the freebsd partition are reserved for the boot code
(/boot/boot). The table of BSD partitions itself is located in the
second sector. So, if you plan to create
On 5/22/2011 7:58 AM, Lars Eighner wrote:
It seems increasing unlikely that uart will ever support the only internal
hardware modem recently available in the US (PR kern/155196), so what are
the chances of sio (which works in 7.x reasonably well and better with a
one-line hack) being brought
Am 24.05.2011 10:53, schrieb Jeremy Chadwick:
On Tue, May 24, 2011 at 09:26:18AM +0200, Joerg Wunsch wrote:
As Andriy Gapon wrote:
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
Backtrace would be a first thing.
OK, here we go (the core has
16 matches
Mail list logo